Pixels & events
- No advertising or analytics tag was found
- The same Meta pixel is loaded twice, so PageView is counted double
- A Meta pixel loads but never sends PageView
- Your product page sends no ViewContent or view_item event
+3more in the report
Website tracking checker
Enter your store address. A real browser checks your pixels, server-side signal, cookies and consent in about 40 seconds, lists every problem with its fix and shows what it costs at your ad budget.
8problems found
+4more in the report
Monthly ad spend$10,000
Lost to wrong data, about $1,300 - $1,800 a month
13% to 18% of the budget
What it costs
Meta, Google and TikTok bid on the purchases they can see. A share of yours never arrives, so they pay for the wrong visitors and report a return your store never had.
Broken tracking costs about$1,300 - $1,800a month at this budget
The range is 13% to 18% of your budget, depending on your industry.
AxiTrace sends every order to the ad platforms from your server, so they stop bidding on half the picture.
of orders never reach the pixel
Ad blockers, Safari and consent banners cut the browser off before the purchase fires.
is how long Safari keeps a cookie set by JavaScript
A buyer who comes back after a week looks like a new visitor, so the ad that found them gets no credit. The scan measures every identity cookie on your store.
is when many tags already fire
Tags that ignore the banner pollute your data, and Google tags that never pass the consent state lose modelled conversions. The scan tests the page before any click and after Reject.
What the scan checks
A real browser loads your home page and one product page as a first-time visitor. These are the checks it runs on what it sees.
+3more in the report
+1more in the report
What you get
Sample report
6 things to fix today, 2 to improve, 12 already working.
Critical and high impact issues. Quick wins first.
Every event Meta, Google and TikTok receive from your store today goes through the visitor's browser. Ad blockers, Safari's tracking prevention, consent banners and slow pages stop a share of those events before they arrive, and nothing sends them again. The platforms then see fewer purchases than you make, optimise your campaigns on incomplete data and report a lower return on your ad spend. Server-side tracking (Meta Conversions API, Google enhanced conversions, TikTok Events API) is the standard fix, and an ad account without it is working with a blind spot.
Send your events from a server as well as from the browser, starting with Purchase, for every ad platform you pay for.
A scan sees what the browser sends, so a server feed that runs entirely behind your store does not show here. If you believe you already have one, open each platform's events manager and confirm that server events arrive for every event, not only for some.
With AxiTrace: AxiTrace sends your events to Meta, Google, TikTok and more from your server, next to the browser tags you already have.
| Platforms detected in the browser | Meta, Google Analytics, Google Ads, TikTok |
|---|---|
| First-party hosts we checked | none |
| Server-side patterns found | none |
Meta counted two PageView events for one visit. Double events inflate your numbers, confuse the algorithm about which visitors matter and make your cost per result look better than it is. This usually happens when a theme, an app and Google Tag Manager each install the pixel.
Keep one installation of the Meta pixel and remove the others.
| Pixel ID | 220011223344 |
|---|---|
| init calls on one page | 2 |
| Script that initialised it | https://connect.facebook.net/en_US/fbevents.js |
| Script that initialised it | https://northwind-outdoor.example/cdn/shop/t/7/assets/theme-meta-pixel.js |
| Script that initialised it | https://www.googletagmanager.com/gtm.js?id=GTM-NWO26 |
| PageView events on one page | 2 |
When someone clicks your Meta ad, the link carries an fbclid. The pixel should save it in the _fbc cookie so that later events can be matched to that click. We opened your site with a test fbclid and no _fbc cookie appeared, so conversions from ad clicks are harder for Meta to attribute.
Make sure the Meta pixel loads on landing pages before any redirect removes the fbclid.
With AxiTrace: AxiTrace saves the fbclid from the landing page in the _fbc cookie and sends it with the visitor's server events.
| Test URL we opened | https://northwind-outdoor.example/?fbclid=AxiTraceScannerTestSAMPLE&gclid=AxiTraceScannerTestSAMPLE |
|---|---|
| Redirects followed | The click ID was kept through redirects |
| _fbc cookie after load | not set |
We loaded your page and did not click anything on your consent banner. These tracking requests were sent anyway. If your banner is meant to ask first, the tags are not waiting for it. This is a technical observation, not a legal assessment.
Assign each listed tag to a consent category so it waits for the visitor's choice.
| Banner detected | CookieYes |
|---|---|
| Banner detected at | 1500 ms after the page started loading |
| Request before any click | Meta PageView to www.facebook.com at 1.2 s |
| Request before any click | Google Analytics page_view to www.google-analytics.com at 1.3 s |
Your Google tags send hits, but we found no Consent Mode default command and no consent parameters (gcs or gcd) on the hits. Google needs Consent Mode v2 signals for visitors in the European Economic Area to use their data for measurement and remarketing, so audiences and conversion modelling for those visitors can stop working without them.
Set Consent Mode defaults before your Google tags load, and update them when the visitor chooses.
| Google tags | G-NWO2026, AW-50011122 |
|---|---|
| Consent commands found | none |
| gcs and gcd on hits | absent |
Safari deletes cookies written by JavaScript after 7 days (24 hours when the visit comes from a link with a click ID). A returning Safari visitor then looks like a new person, so conversions after a week lose the link to the ad that brought them. About a third of ecommerce traffic is Safari.
Set your identity cookies from your own server with a Set-Cookie header.
With AxiTrace: When tracking runs through your own domain, AxiTrace sets its visitor cookie from your server, so Safari no longer cuts it to 7 days.
| Cookie | _fbp: set by JavaScript, expiry requested 90 days |
|---|---|
| Safari lifetime (computed) | _fbp: 7 dayscomputed |
| Cookie | _ga: set by JavaScript, expiry requested 400 days |
| Safari lifetime (computed) | _ga: 7 dayscomputed |
| Cookie | _ga_NWO2026: set by JavaScript, expiry requested 400 days |
| Safari lifetime (computed) | _ga_NWO2026: 7 dayscomputed |
| Cookie | _gcl_aw: set by JavaScript, expiry requested 90 days |
| Safari lifetime (computed) | _gcl_aw: 1 daycomputed |
| Cookie | _ttp: set by JavaScript, expiry requested 400 days |
| Safari lifetime (computed) | _ttp: 7 dayscomputed |
Medium and low impact issues worth fixing next.
Your product page sends ViewContent, but without a value or a currency. Meta uses them to learn which products and visitors are worth more, and to report the value of product views. Without them, value-based optimisation and catalogue ads work with less information.
Send value and currency with every ViewContent event.
| Product page we tested | https://northwind-outdoor.example/products/trailhead-2p-tent |
|---|---|
| Event | ViewContent |
| value | missing |
| currency | missing |
We checked your tracking requests against EasyPrivacy, the list most ad blockers use. Visitors with an ad blocker never send the matched requests, so their visits and sales are missing from your ad platforms. Ad blockers are common on desktop, especially with younger and tech-savvy audiences.
Send your most important events through your own domain or server, where the list does not match them.
With AxiTrace: When tracking runs through your own domain, AxiTrace collects events on a path the common ad-blocker list does not match and sends them to the ad platforms from your server.
| List checked | easyprivacy (202609280000) |
|---|---|
| Tracking requests checked | 10 |
| Requests on the list | 8 (80%) |
| Example of a matched request | Meta (www.facebook.com) |
| Example of a matched request | Google Analytics (www.google-analytics.com) |
| Example of a matched request | Google Ads (googleads.g.doubleclick.net) |
Fix times are estimates for someone who can edit your theme, tag manager or app settings.
Checks your store passed.
Advertising or analytics tags were found
Your Meta pixel sends PageView
Your product page sends a product view event
ViewContent carries content_ids and content_type
GA4 view_item carries an items array
25% of the score
20% of the score
15% of the score
15% of the score
15% of the score
10% of the score
These checks could not run on your site, so they count neither for nor against you.
Cookies come from a host on a different IP, so Safari caps them at 7 days
None of your identity cookies is set by a server, so this check does not apply.
Consent Mode is present but ad_user_data or ad_personalization is missing
Google Consent Mode was not detected, so its v2 signals could not be checked.
Customer story
One of the largest online furniture stores in Poland. Measured on 20,000+ orders.
Meta was crediting our orders to the wrong campaigns and the wrong creatives. 42% of the orders our Meta ads started came after Meta stopped counting, so the ads that really brought buyers in looked weak. AxiTrace shows you which campaign and ad generated every order - and recommends how to reallocate your budget.
Enter your store address. You get every problem in your tracking, a fix for each one and what they cost at your ad budget.
Something else on your mind? Ask us directly
Yes. The scan and the summary with your score and every issue we found are free and need no signup. To see why each issue matters, how to fix it and the evidence we recorded, enter your email and we send you a private link to the full report.
The calculator applies a range of 13% to 18% to the monthly ad budget you set, depending on your industry. That is the share of ad spend stores typically lose when ad platforms bid on missing or wrong conversion data. When a scan finds only smaller problems we count the low end of the range, and when it finds none we show no loss. It is an estimate for your budget, not a measurement of your ad account.
It opens your home page and one product page in a real Chromium browser, the way a first-time visitor would, tests your cookie banner before any click and after Reject, and records every tag, cookie and network request. It never submits a form, adds to cart or logs in.
No. Our browser stops every request to an analytics or advertising collection endpoint before it leaves the scanner, so no platform receives a page view or an event from us. If your store sends events from its own server when a page loads, that server may still see our visit; the header X-AxiTrace-Scanner: 1 lets you filter it.
Usually 30 to 45 seconds. If another scan is running, yours waits in a short queue and the progress card tells you roughly how long. You can leave the tab open and the report appears when it is ready.
Some stores challenge automated browsers, some have no product page reachable from the home page, and some cookie banners cannot be operated automatically. When that happens we report what we could see and mark the checks we could not run as not checked, never as passed.
Those extensions show what fires on one page in your own browser, with your own cookies and consent choices. This checker loads your store as a new visitor, compares what happens before and after Reject, measures cookie lifetimes as Safari would treat them and checks deduplication readiness across platforms, then turns it into a list of fixes.
AxiTrace records every order on your server and sends it to Meta, Google, TikTok and 6 more ad platforms. Free up to 10,000 visits a month.
An agency, or more than 3M visits a month? Talk to us