Start with app-user identity
Connect a referral to the stable user ID already present in your app and subscription provider.
For subscription apps
Keep app-user identity, provider transactions, renewals and refunds connected across mobile and web subscription systems without relying on fingerprinting.
Built for operating reality
Connect a referral to the stable user ID already present in your app and subscription provider.
Provider webhooks carry purchases, renewals and refunds into an idempotent commercial record.
Sandbox credentials and provider connections let teams exercise the integration without mixing test events into live programme data.
Subscription identity
Use the application user and external subscription identifiers shared by your product and provider, then preserve that relationship through later lifecycle events.
Store-safe operations
A customer-facing code claim establishes attribution. Purchase, renewal and refund evidence arrives from the trusted server-side integration that owns the commercial event.
Questions, answered
No. Attribution uses explicit code and stable application identities rather than probabilistic cross-device tracking.
Provider subscription identity keeps later lifecycle events connected to the accepted user and attribution record.
Yes. Application environments isolate credentials, provider connections and event data for sandbox and production use.
Build the reliable path