Documentation
Quick start
Snippet in, revenue connected, spend connected. Roughly ten minutes.
1. Install the snippet
Paste this into the <head> of every page you want measured. No npm package, no build step.
<script
async
src="https://cdn.roassensor.com/roas.js"
data-site="YOUR_PUBLIC_KEY"
></script>data-site is your public key. It only names which site an event belongs to, so it is safe in page source.
Load any page, then check Setup → Install. It confirms the first beacon within a few seconds.
2. Connect revenue
On Stripe, add this endpoint in your dashboard and paste the signing secret into Setup → Revenue:
https://api.roassensor.com/api/tracking/webhooks/stripe/YOUR_PUBLIC_KEYOn anything else, your server reports the sale. See Reporting revenue for the full payload.
3. Connect ad spend
Open Integrations and authorise Meta, Google Ads or TikTok. Each is an OAuth flow; you never paste a password.
The first sync backfills recent history, so yesterday's numbers appear without waiting a day.
4. Check it worked
Give it one real sale, then open the dashboard.
- Revenue is there, attribution is empty. Normal for a sale whose journey started before you installed. Check again tomorrow.
- Nothing at all. Add
?roasdebug=1to any URL and read the console. Usually a mistypeddata-site. - Everything unattributed. The checkout is dropping the visitor id. See First-party delivery.

