Documentation

Quick start: website

Snippet in, revenue connected, spend connected. Roughly ten minutes.

1. Install the snippet

This is the website path. For an Android or iOS app, follow Quick start: mobile app instead -- it has five stages rather than three, and only two of them are code.

Paste this into the <head> of every page you want measured. No npm package, no build step.

html

<script
  async
  src="https://cdn.roassensor.com/roas.js"
  data-site="YOUR_PUBLIC_KEY"
></script>

Your public key is on Setup → Install.

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:

text

https://api.roassensor.com/api/tracking/webhooks/stripe/YOUR_PUBLIC_KEY

On anything else, your server reports the sale. See Reporting revenue for the full payload.

3. Connect ad spend

Open Integrations and connect each ad platform. Each one has a guided setup that says exactly what to copy from the platform and where it lives; Ad platforms has the same steps.

The first sync pulls the last three days, so yesterday's spend appears 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=1 to any URL and read the console. Usually a mistyped data-site.
Everything unattributed. The checkout is dropping the visitor id. See First-party delivery.