Revenue attribution, without the guesswork

How a sale gets its source

The tracking script gives each visitor a first-party id on your domain. When that id reaches the payment, ownlytics knows which visit, source and campaign produced the sale. It gets there in one of three ways:

1. Payment links are tagged automatically (Stripe, Polar, Dodo).
2. Server-created checkouts pass the visitor and session ids as metadata.
3. Success pages: when the buyer lands back with the provider's checkout id, the script links it.

Which visit gets the credit

Set per website:

• Last non-direct (default): the most recent visit with a real source.
• First touch: the visitor's first visit ever.
• Last touch: the last visit before buying.

Subscriptions keep their source: renewals inherit the visitor of the first payment, and refunds come off the same source.

Sources you can read

• Channels from referrer, UTM tags or ad click ids: search, social, AI (ChatGPT, Claude, Perplexity), referral, email, paid, affiliate.
• In-app browsers that hide the referrer (Instagram, TikTok, Reddit, Telegram and more) are credited to the app.
• Direct, split into typed or bookmark, shared link and checkout return. A checkout return never takes credit from an earlier visit.

Lifetime value by first source

Customers are grouped by the source of their first attributed payment, with every renewal, upgrade and repeat purchase added since. Some channels send one-off buyers; others send customers who stay.

Privacy and attribution

First-party cookies keep a sale linked to a visit weeks earlier. Cookieless mode stores nothing in the browser and links sales to visits from the same day. Cookieless-until-consent switches when your banner says so. Pick per website. Details in the docs.

claude mcp add --transport http --scope user ownlytics https://ownlytics.xyz/api/mcp --header "Authorization: Bearer dbk_YOUR_KEY"