For subscription apps

Connect referral attribution to the full subscription lifecycle.

Keep app-user identity, provider transactions, renewals and refunds connected across mobile and web subscription systems without relying on fingerprinting.

01ReferralLink or code
02ConversionStable event
03CommissionRule evidence
Provider event IDsRenewal continuityEnvironment isolation

Built for operating reality

Clear contracts at every boundary.

01

Start with app-user identity

Connect a referral to the stable user ID already present in your app and subscription provider.

02

Process lifecycle events

Provider webhooks carry purchases, renewals and refunds into an idempotent commercial record.

03

Test end to end

Sandbox credentials and provider connections let teams exercise the integration without mixing test events into live programme data.

Subscription identity

Join product identity to provider identity once.

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

Let trusted provider events drive money decisions.

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

Know where the boundaries are before you integrate.

Does this rely on device fingerprinting?

No. Attribution uses explicit code and stable application identities rather than probabilistic cross-device tracking.

Can subscription renewals stay attributed?

Provider subscription identity keeps later lifecycle events connected to the accepted user and attribution record.

Can the integration be tested separately?

Yes. Application environments isolate credentials, provider connections and event data for sandbox and production use.

Build the reliable path

Make every referral decision traceable from click to payout.

Request sandbox access