Measurement and ads
Analytics, tag manager, ad tags and social pixels, per store.
Report section · e-commerce
Your rival takes Klarna. Do you?
Analytics, ad pixels, payment options, review widgets, email capture, loyalty. We detect them from the page code of your store and three rivals. You see what they offer that you do not, and what you may not be measuring.
Live Live as part of Intel loops for online stores, which is free and specialist-checked.
- No model guessing; pattern matches on the captured HTML
- Read from page code
- Source: src/lib/storefront/signals.ts · checked 2026-10-13
- Never reported as "missing"
- "Not detected"
- Source: src/lib/storefront/signals.ts (header) · checked 2026-10-13
- Yours and three rivals
- Four stores
- Source: src/app/intel-loops/StorefrontForm.tsx · checked 2026-10-13
What it is
What it is, and how it works.
Inside the online-store Intel loop: the analytics and ad tags, payment options, review widgets and retention tools detected on your store and three rivals, read from each store's page code.
A store's page code shows how it is run: whether it measures visits and sales, which ad platforms it feeds, which ways customers can pay, whether reviews are on the page, whether it captures email addresses, whether it runs a loyalty scheme. Line four stores up and the gaps show.
As part of Intel loops for online stores, we capture the raw page code of your homepage and a product page, and do the same for each of your three rivals. A fixed set of patterns then looks for known tools: Google Analytics, Google Tag Manager and Google Ads tags; the Meta, TikTok and Pinterest pixels; a consent tool; wallets and buy-now-pay-later options such as Apple Pay, Google Pay, PayPal, Klarna, Clearpay and Shop Pay; review widgets including Trustpilot; returns, guarantee and delivery wording; email capture, Klaviyo, loyalty and subscriptions; site search; and the store platform.
The detection is fixed pattern matching. No language model decides what is present. The results feed the comparison's scoring, appear beside it, and are checked by the specialist with everything else.
One caveat, printed in the report. Some tools are added after the page loads, by a tag manager, and are not in the captured code. So the report says "not detected", never "missing".
Who it is for
- Store owners checking their own measurement set-up
- Teams comparing payment and trust options against rivals
- Anyone about to change platform or add retention tools
What it does
What it reads, and what you see.
Payment options
Wallets and buy-now-pay-later options shown on each store.
Trust and retention
Review widgets, returns and delivery wording, email capture, loyalty and subscriptions.
By hand, or with it
The same job, two ways.
By hand
- View source on each rival's store and search for scripts
- Not know which payment options rivals offer until you buy
- Assume your own tags are firing
- No side-by-side view
With Tracking and tags check
- Tools detected on four stores at once
- Payment, trust and retention options compared
- "Not detected", never "missing"
- Checked by a specialist with the rest of the report
What you walk away with
What you keep.
A tools grid
What each of the four stores runs, side by side.
Gaps against rivals
Payment and trust options rivals show and you do not.
A measurement check
Whether your own analytics and ad tags were detected.
Input to the scores
The detected tools feed the comparison's scoring.
How it works
Three steps.
Request an Intel loop
Your store and three rivals.
We capture and detect
Page code is captured and checked against known tools.
Read it in your report
Released by the specialist with the full comparison.
Limits
What it does not do.
- It reads the homepage and one product page per store, not the whole site.
- Tools loaded later by a tag manager can be missed; "not detected" does not mean absent.
- It detects that a tool is present, not that it is configured correctly or firing on purchase.
- It is not available on its own, only within the online-store Intel loop.
Price
Request your comparisonPart of Intel loops for online stores, which is free.
FAQ
Tracking and tags check: questions
Can I run this on my store alone?
Not on its own. It runs as part of Intel loops for online stores, which is free.
It says a tag was not detected, but I have it. Why?
It may be loaded later by a tag manager, after the page code we captured. That is exactly why we say "not detected" rather than "missing".
Does it tell me if my tracking is working?
No. It shows what is present in the page code, not whether it is set up correctly.
Is a language model involved?
Not in the detection, which is fixed pattern matching. The comparison's overall scoring does use one, and a specialist checks it.
Run it on your own business.
Live as part of Intel loops for online stores, which is free and specialist-checked.