Auditing your ad tech (marketing pixels)

What Audit my adtech does

When a page loads, every marketing solution on it sends network requests (pixels, or hits) to its own servers. Audit my adtech captures these requests while you browse and compares them against the solution definitions configured in Tag Insight. The result tells you two things: whether each solution is present on the pages where you expect it, and whether the hits it sends match its definition.

Because the audit observes what the browser really sends, it does not depend on how your tags are deployed. The Tag Insight Chrome extension offers the same Audit My Ad Tech capability from your browser: it works without a TMS, though it requires a Tag Insight account.

Start an audit run

1. 1

   Sign in to Tag Insight and open the project you want to audit.

2. 2

   In the sidebar, open the Audit my adtech module.

3. 3

   Start a new run. From this point, Tag Insight captures the marketing pixel requests fired by the pages you visit.

Before starting, make sure the solutions you care about (GA4, Didomi, Piano and so on) have solution definitions available, since captured hits are validated against those definitions.

Browse your site

With the run active, navigate your site the way a visitor would. Cover the pages and journeys that matter: the homepage, key landing pages, product or article pages, and any conversion steps.

Each page you load triggers its marketing tags, and Audit my adtech records the resulting requests. The more representative your browsing session, the more meaningful the results, so take the time to visit every template you want covered.

Read the captured hits and the Presence rate

Back in the Audit my adtech module, review what was captured during the run. For each solution, Tag Insight shows a Presence rate: how consistently that solution's hits were detected across the pages you browsed.

A high Presence rate means the tag fired reliably wherever you went. A low Presence rate usually points to pages where the tag is missing, blocked, or firing only under certain conditions. Use it to spot gaps, then check the affected pages and the hits themselves to understand why a solution did not fire.

Inspect individual hits in the Live Debugger

To examine hits one by one, open the Live Debugger module in the sidebar. It lists the hits captured during an audit run so you can inspect each request in detail and check that the values sent match what you expect.

Keep in mind that the Live Debugger shows hits recorded during the run: it is a review tool for captured traffic, not a streaming view. Run an audit first, then use the Live Debugger to dig into what was collected.