Customer Data Platform

Segment your customers by KYC status and on-chain behaviour, and pull a per-customer profile that combines identity, wallet activity, and KYC state into a single view. A customer-data layer that sits on top of the same regulated platform that handles your payments, treasury, and compliance.

Who this is for

Persona	Typical inbound
Marketing or growth team at a Studio merchant	”Can we segment our customers by on-chain behaviour or NFT holdings for targeted campaigns?”
Loyalty or membership team	”We want VIP tiers based on customer wallet activity.”
Operations and compliance	”Show me our organisation’s KYC funnel — how many customers are at each step, and where do they drop off?”
Account managers	”What is the full profile of customer X — KYC status, wallets, history — in one view?”

Not a fit if you need a full marketing-automation platform with email and SMS campaign sending (we surface the segment data; you action it through your existing marketing stack), require per-customer real-time event streams (the current surface is query and snapshot, not a continuous event bus), or expect a packaged Looker- or Metabase-style dashboard out of the box (the surface is API-led; visualisation is on the consumer side or via the Studio console).

What you can ship today

Capability	What it covers
Compliance funnel statistics	Organisation-level KYC funnel — counts and breakdowns by status — for operational dashboards
Per-customer profile	A combined view of identity, KYC status, and on-chain behavioural data for a single customer, looked up by user identifier
Audience segmentation	A paginated, sortable, filterable customer list. Filter by KYC status; free-text search across customer attributes

The same KYC status and identity model that powers the KYB and KYC Workflow feeds these surfaces — there is no separate import or sync to run.

How it works


1. Your customers complete KYC, hold wallets, and transact through
   the KryptoGO platform — payment acceptance, white-label wallet,
   payouts, or any combination.

2. Each customer accumulates a profile inside the platform:
   - Identity and KYC status from the compliance pipeline
   - Wallet addresses and on-chain activity
   - Behavioural attributes derived from transaction history

3. Your operations team queries the audience endpoint to list and
   filter customers — by KYC status, by free-text search across
   customer attributes — for use in dashboards, exports, or
   downstream marketing tooling.

4. Your account-management team opens the per-customer profile to
   see KYC state, wallets, and behavioural data side by side.

5. Your compliance team uses the funnel statistics to monitor the
   KYC pipeline — how many customers are pending, approved,
   rejected, or stuck mid-flow.

Custody model

The Customer Data Platform reads identity and on-chain data the platform already holds. No additional custody decisions are involved. If you operate a white-label wallet, your customers’ assets sit under embedded self-custody — see Custody Options. If you operate payment acceptance only, the on-chain data is from the customer’s external wallets.

Compliance posture

Customer profiles include personally-identifiable information that is encrypted at the application layer in the compliance database. Access is gated by the same role-based access control that governs the rest of Studio — see Team, roles, API keys, and risk limits. All data handling sits inside the platform’s ISO 27701-certified privacy management system. See Compliance and Certifications for the full posture.

Typical integration timeline

Path	Bucket
Use the Studio console for audience segmentation, profile lookup, and compliance funnel views	Under one month — available immediately once your organisation is provisioned
Pull data via API for an internal dashboard or a marketing-stack export	Under one month — typically one to two weeks for a backend team
Add custom segmentation criteria beyond the supported filter set	One to two months — scoped per integration

Current scope

Compliance funnel statistics, per-customer profile lookup, and audience segmentation by KYC status and free-text search are in production inside the Studio console and via API.
Currently deployed for select partner integrations; contact us to scope your specific segmentation needs — for example, segmentation by NFT holdings, balance thresholds, transaction patterns, or custom attributes.
Outbound marketing actions — email, SMS, push — are deliberately out of scope. The segment data integrates with your existing marketing stack via export.
Real-time event streams and segment-membership webhooks are roadmap items.
Subject-access-request and data-deletion processes are handled through our compliance team in line with our ISO 27701 controls. Partner-facing self-service tooling for these flows is on the roadmap; today they run as compliance tickets.

Talk to us

If you want to segment your customers, build VIP tiers, or feed a marketing stack with rich customer data sourced from KYC and on-chain behaviour, reach our partnerships team via the address on www.kryptogo.tw .

Where to go next

KYB and KYC Workflow — for how KYC status, the primary segmentation axis, is captured.
Team, roles, API keys, and risk limits — for the role gates that control who can read customer profiles.
Blockchain forensics and data — for the underlying on-chain data sources behind behavioural segmentation.
Compliance and Certifications — for the privacy posture behind customer-data handling.