Revenue attribution
Connect verified orders to the traffic and campaigns behind them.
Seean reports revenue using the landing page, converting page, source and campaign fields supplied with your orders. Missing attribution fields are shown as unattributed; they are not automatically reconstructed from a visitor’s history. The current order API accepts USD amounts in cents and full-order refunds. Partial refunds and other currencies are not supported.
Sending orders
Open your website’s revenue setup to create an order API secret. Use your server or payment webhook handler to send verified orders to the displayed endpoint. Keep the secret on your server; do not include it in browser code. This is a custom integration, not an automatic connection to every checkout provider.
The tracker exposes window.seean.attribution() with the visitor ID, landing path, converting path and campaign. Pass those fields to your server with the order. First source, last source, touch count and time to purchase must be supplied separately if you want to report them. Only forward payment events after verifying them with your provider.
What you see
- Attribution breakdown: supplied landing pages, converting pages, first source and last source
- Revenue by product: orders, revenue, share
- Touches before purchase: the touch count supplied with each order; absent counts do not establish the visitor’s actual journey
- Top purchase paths: the supplied landing and converting page pairs, not a reconstruction of every page visited
Revenue report
Open Revenue in the website sidebar. The top strip shows gross, refunds, net, attributed revenue, attribution rate and time to buy. Below it, inspect attribution breakdowns, products, supplied touch counts, purchase path pairs and the latest 20 orders. These values describe the order fields your integration sends.
Integration reference
Follow Order API and refunds for payloads, server-key handling, full refunds and retry behavior. Provider availability explains the distinction between a custom API integration and a native checkout connector.
Something unclear? Contact support.