Use your existing account identity
Pass the stable application user ID your product already owns instead of creating another marketing identity silo.
For SaaS teams
Connect referred accounts, paid outcomes, renewals and refunds without making the browser or a mutable email address the source of financial truth.
Built for operating reality
Pass the stable application user ID your product already owns instead of creating another marketing identity silo.
Create conversions from the trusted system that receives checkout or billing confirmation.
Subscription and reversal events retain provider identity so repeat delivery remains one lifecycle.
SaaS acquisition
Validate or claim the referral at the product boundary, associate it with a stable account identity, then let trusted billing confirmation drive the commercial outcome.
Revenue lifecycle
Trials, paid conversions, renewals and refunds can be tied back to provider and application identities without allowing a later URL parameter to rewrite attribution.
Questions, answered
Use a stable application user ID owned by your product. Marketing attribution should not depend on a mutable email address.
Record the outcome after your trusted billing system confirms the event, using its stable transaction identity.
Reuse the same provider event and idempotency identity so the retry resolves to the canonical outcome.
Build the reliable path