Documentation
Troubleshooting: website
The five things that actually go wrong on a website integration, and what each one means.
Common problems
For an app -- crashes, unsigned installs, (not set) referrers, purchases that never book -- see Mobile troubleshooting.
- No events arriving. Add
?roasdebug=1to any URL and check the console. The usual cause is a missing or mistypeddata-site. - Sales show as unattributed. The checkout is dropping the visitor id. Pass
vidon the Conversions API call, and read First-party delivery. - ROAS looks too low. Spend is connected but revenue is not, or your attribution window is shorter than your real sales cycle. A network can have its own window on the app's Partners tab.
- Spend is stale. The sync runs hourly and re-pulls a three day window, because platforms restate spend for up to 72 hours.
- Numbers moved after the fact. Late touchpoints and identity merges recompute hourly, and changing a window, the credit model or a matching switch re-attributes the last 90 days once. Older sales keep the credit they were booked with; today is still settling.
Still stuck? Talk to us; a real engineer answers.