What a pilot enables

What integrating the Swapnice SDK unlocks in the partner product.

A V1 pilot is a 60–90 day design-partner integration: one app, one consent flow, one or two event families, and limited API usage. The goal is to prove that consented events become usable profile intelligence the partner can read back into its own product.

What the partner can do after SDK integration

Capability	After V1 integrate	Notes
Connect a known user to Swapnice	Yes	Connection session + OAuth
Prove consent with a receipt	Yes	Purpose-limited, revocable
Send first-party product events	Yes	Ordered, idempotent ingest
Read a resolved profile for that user	Yes	Facts, confidence, alternatives
Read intent scores	Yes	Outcome, habit, affiliate, sentiment, activation
Suppress on revoke	Yes	Ingest and purpose-scoped reads fail closed
Build in-app personalization	Yes	From profile + intents

The partner does not automatically receive:

• Raw access to other apps’ users
• Wallet, payment, or consumer-app private fields
• The right to use personalization events for any purpose the user did not grant

How this improves the partner product

Concrete loop for a first slice:

1. Before. The partner app has orders and clicks, but no consented, purpose-scoped profile it can read back as facts and intents.
2. SDK is live. Users connect Swapnice and grant personalization (and optionally analytics). Product actions become claims and intents.
3. In the product. The partner backend reads profile and intents, then reorders shelves, highlights a collection in progress, or suppresses objects the user already completed.
4. On revoke. Purpose-scoped ingest and reads fail closed. The partner stops using that customer’s intelligence for the revoked purpose.

What the first pilot should implement

Keep the first slice small enough to finish.

Workstream	Pilot scope
Surfaces	One consumer app or checkout surface
Purposes	personalization and analytics
Events	purchase.completed plus one engagement event (collection.interacted or profile.selected)
Reads	Profile + intents in the partner backend
Suppression	Revoke path tested in sandbox before go-live

Design-partner scope (default)

Term	Default
Length	60–90 days
Scope	One app, one or two event families, one consent flow, limited API usage
Swapnice provides	SDK, sample consent copy, sandbox app, implementation support
Partner provides	SDK in a build, approved consent language, valid receipts
Data rights	Process only for granted purposes; aggregated de-identified metrics to evaluate the product

Partners do not own the consolidated cross-brand profile and do not get raw export of other apps’ users.

Success metrics we typically write into the order form:

• SDK live in a sandbox build, then a production build
• Minimum connected users or eligible accounts
• Consent-receipt coverage above an agreed threshold
• Event schema quality above an agreed threshold
• At least one measurable product outcome, such as better personalization or a completed suppression test

Next

• Sandbox and testing process
• Request walkthrough
• Example use cases
• Outputs and sample responses