Audit for

Example Ltd

        
        www.example.co.uk
      

During our test we found 2 critical issues and 1 more worth fixing. Below is exactly what we saw, in plain English, including what a single scan can and can’t tell you.

Observed on page load

The tracking requests our browser recorded during the visit, in the order they happened, timed from the moment the page started loading.

+0.00s

Page load

www.example.co.uk/

+0.38s

Meta Pixel before consent

connect.facebook.net/en_US/fbevents.js

+0.41s

Meta Pixel before consent

www.facebook.com/tr

+0.64s

GA4/GTM

www.googletagmanager.com/gtag/js

+0.70s

Google Ads

www.googletagmanager.com/gtag/js

end

No consent interaction detected

Tracking began 0.38 seconds after the page started loading, before any consent choice had been made. The findings below explain what that means for you.

Critical finding 01

No consent option, but tracking ran anyway

What we found

During our test of www.example.co.uk, we didn't find a cookie banner or any other way to accept or refuse tracking, and advertising tracking requests were sent while the page loaded.

What it means

Under UK rules (PECR), advertising tracking such as the Meta Pixel or Google Ads generally needs a visitor’s agreement before it runs. On the evidence of this test, the site doesn’t offer visitors that choice.

Why it matters

Two things worth weighing. First, a potential compliance gap to review on its own terms. Second, Google and Meta increasingly rely on consent signals to decide how they use the data a website sends them, so tracking without those signals can leave your ad platforms with a less complete or less usable picture. A scan can’t measure the effect on your campaigns.

What fixing involves

Usually a case of installing and configuring a consent banner (free tools such as CookieYes work on most platforms) and making sure your tracking waits for it. The effort depends on how your tracking is installed.

Critical finding 02

The Meta Pixel ran before any consent choice

What we found

On www.example.co.uk, the Meta (Facebook) Pixel sent requests to Meta while the page loaded, before any consent choice had been made.

What it means

The Pixel is advertising tracking, so it would normally be set to wait for a visitor’s agreement. During this test, it didn’t wait.

Why it matters

A potential compliance gap, and data reaching Meta that may not reflect visitors’ choices. Meta increasingly takes consent into account in how it uses advertising data; the effect on your campaigns depends on your set-up and can’t be measured from a scan.

What fixing involves

Usually a settings change: making the Pixel wait for your banner’s "accept" signal, in Google Tag Manager, your banner tool, or your platform’s privacy settings. The exact steps depend on how the Pixel was installed, and it’s sometimes installed in more than one place.

Worth fixing finding 03

We didn’t see Google’s Conversion Linker working

What we found

www.example.co.uk loads Google Ads tracking, but during our visit, including after we accepted the cookie banner where there was one, we didn’t observe the cookie that Google’s Conversion Linker sets (_gcl_au).

What it means

The Conversion Linker helps Google Ads connect an ad click to a sale or enquiry that happens later, on another page. Not seeing it in this test may mean it isn’t set up, or that consent settings stop it running. The wider tag and conversion set-up should be checked before concluding that attribution is broken.

Why it matters

Where the linker isn’t working, conversions that happen after a visitor moves between pages may not be credited to the ad that brought them, which can skew Google Ads reporting and bidding. A scan can’t measure how many conversions are affected.

What fixing involves

Usually a small configuration change: adding or enabling the Conversion Linker in Google Tag Manager, or checking consent settings where it’s built into the Google tag.

Full Scan Goes further

See what happens where customers share their details

€29

Credited in full if you then choose Fix it for me (€220 instead of €249).

Your free audit of www.example.co.uk shows what loads as visitors arrive and browse. The Full Scan follows the rest of the journey: the cart, the checkout, your site search and your forms. It shows exactly which personal details leave your website, and where they go.

Because it submits your forms with made-up details, we only run it once you've confirmed the website is yours, by a link sent to an address on your own domain. No order is ever placed. Full refund if we can't run it.

Run the Full Scan →

What we check	Free audit	Full Scan
Homepage, before and after you accept cookies
One product page, with an item added to the basket
Your cart page	–
Your checkout: outside tools, including ones that can record what customers type	–
Your site search: are searches passed to ad platforms?	–
Your forms: do details typed in reach Google, Meta or others? Tested with made-up details	–

Three ways to get this fixed

No call needed. This audit works with any of them. The two paid options are fixed prices and end with a re-check using the same method as this audit, so you know it worked.

Pass it on

Free

Forward this audit to whoever looks after your website
It shows the exact requests we observed, with timings, and what each finding means
Need a hand later? Both paid options are still open to you

Forward this audit

Fix it myself

€49

Step-by-step guides for the problems on this audit, matched to your website’s platform
No coding needed
One free re-check to confirm it worked
Stuck? Switch to Fix it for me for €200 within 30 days

Get the guides

Fix it for me

€249

A vetted specialist fixes the problems on this audit, with the scope confirmed before any change
No passwords shared: you give access through a separate account
We re-scan your site and send you a before-and-after report
Fixed and verified, or your money back

Get it fixed

Fix it for me is the most hands-off option. See our Terms and Refund Policy, or read more about TrackWatch.