Free tracking audit
Enter your store's address. We load the page and check which pixels and tags it loads, whether they wait for consent, whether sales also reach the ad platforms server-side, and how heavy the page is.
The result appears here.
- Score
- Pixels and tags
- Page size
To fix
Looks good
ROASaurus sends every purchase to your ad platforms from the server, with consent respected.
{tag} is set up twice with the same ID ({id}), so events can be counted twice.
The {tag} library loads {count} times on this page.
{tag} sends to more than one ID ({ids}). Check that each one should be there.
No pixels or analytics tags were found in the page source. A tag manager may add them after the page loads.
No ad platform pixel was found in the page source.
No sign of server-side tracking. Browser pixels alone miss sales that ad blockers and browser privacy features hide.
No consent tool was found. In the EU and the UK, tracking needs consent first.
These tags load before the visitor gives consent: {tags}.
Google tags run without a Consent Mode default.
The page HTML alone is {kb} KB.
The page loads {count} external scripts.
The page loads files from {count} other domains.
The page is larger than 2 MB, so only the first {kb} KB were checked.
The page answered with HTTP status {status}.
A server-side tracking setup was found.
A consent tool is installed.
Tracking tags wait for consent.
Google Consent Mode has a default.
Enter a public web address, such as yourstore.com.
The store could not be reached. Check the address and try again.
You ran a lot of audits in a short time. Try again in a few minutes.
None found
Checking…
What the audit checks
- Pixels and tags in the page source: Meta, Google Ads, Google Analytics 4, Google Tag Manager, TikTok, Snapchat, Pinterest, Reddit, X, Microsoft, LinkedIn, Criteo, Taboola, Outbrain, Klaviyo, Hotjar and Clarity, with their IDs.
- Duplicates: the same pixel ID set up twice, or one library loaded twice, which counts events twice.
- Consent: which consent tool runs, whether tags load before the visitor agrees, and whether Google Consent Mode has a default.
- Server-side tracking: signs of ROASaurus, server-side Google Tag Manager, Stape, Elevar, Littledata and similar tools.
- Page weight: the size of the HTML, the number of external scripts and the other domains the page loads from.
What it cannot see
The audit reads the page as it arrives, before any script runs. Tags that a tag manager adds later and events your server sends straight to an ad platform do not show up in the source, so a missing tag here is a reason to check, not proof. Server-side tracking explains how ROASaurus sends every sale with the visitor's consent respected.
Every sale, traced to the ad that earned it
Server-side tracking, profit and lifetime value in one app. 14-day free trial, no credit card.
Start your free trial →