All features

Customer records for custom sites.

Keep visitor, customer, lead, and client data in one backend so custom frontends can still have a usable CRM layer behind them.

Best for

  • client portals
  • member sites
  • lead databases
  • customer history

Use it when the site needs memory: carts, conversations, form submissions, bookings, campaign activity, and admin notes.

What this module gives your project.

Profiles

Use this capability from your custom frontend while the operational side stays manageable in Arky admin.

Activities

Use this capability from your custom frontend while the operational side stays manageable in Arky admin.

Profile lists

Use this capability from your custom frontend while the operational side stays manageable in Arky admin.

Customer context

Use this capability from your custom frontend while the operational side stays manageable in Arky admin.

Admin notes

Use this capability from your custom frontend while the operational side stays manageable in Arky admin.

Custom UX without rebuilding backend state.

  • Profile sessions
  • List subscription flows
  • Access checks
  • Activity tracking

A client-facing back office for the same module.

  • Profile timelines
  • Lists and segments
  • Conversation context
  • Internal notes
  • Submission history

Code the frontend. Connect Arky underneath.

Start with the frontend stack the project deserves, then connect only the Arky modules it needs. The admin, API, SDK, and backend workflows stay behind the custom experience.

  1. Identify or create a profile
  2. Track important site actions
  3. Use lists and history for follow-up
import { createArkyStore } from "arky-sdk/storefront-store";

const arky = createArkyStore({
  baseUrl: "https://api.arky.io",
  storeId: "your-store-id",
  locale: "en",
});

await arky.setup({ hydrateCart: true });

// Use the module helpers your frontend needs.
// The client keeps full control over markup, routing, and UX.

Useful integration touchpoints.

  • POST /v1/storefront/{storeId}/profiles/session
  • POST /v1/storefront/{storeId}/profile-lists/{id}/subscribe
  • GET /v1/storefront/{storeId}/profile-lists/{id}/access
Talk to us

Early access for custom frontend teams.