Home › Blog · Playbooks · 20 October 2026 · 6 min read

A tracking checklist before you scale ad spend

Eight checks to run before raising your ad budget: one tag, purchase value, order ID deduplication, consent, server delivery, UTMs, tests, alerts.

Before you raise your ad budget, confirm that every purchase reaches each platform once, with the right value, and only when the visitor has agreed. The eight checks below take an afternoon and protect every dollar you spend afterwards.

Why check before scaling

Automatic bidding learns from the conversions a platform receives. At a small budget, a tracking fault costs a little. At a large budget, the same fault costs a lot, because the algorithm spends more money following the same wrong signal.

A fault can push in either direction. Missing purchases make good campaigns look weak, and you cut them. Duplicate purchases make weak campaigns look strong, and you fund them. Both are easier to fix before the budget goes up.

The checklist

1. One tag, installed once

Sites collect tags over the years: a plugin here, a pasted snippet there, a container from a former agency. Two copies of the same platform's tag will each report the purchase.

How to check: open the checkout thank-you page with the browser's developer tools on the Network tab, place a test order, and count the purchase requests sent to each platform. There should be one per platform from the browser. Remove any old plugins and snippets that send the same event.

2. Purchase value and currency

A purchase event should carry the order's value and its currency code, such as USD or EUR. Without a value, the platform cannot optimize for revenue or report return on ad spend. A wrong currency turns every report into nonsense.

How to check: place a test order and compare the value in the platform's events tool with the order in your shop. Decide whether value includes tax and shipping, and keep the same rule everywhere. Check an order with a discount code and one with several items.

3. Order ID for deduplication

Thank-you pages get reloaded. Customers bookmark them, open the confirmation link from their e-mail, or press the back button. Each reload can fire the purchase again. Sending the order ID with the event lets the platform recognize a repeat and count it once.

The same ID does a second job when you send events from both the browser and a server. See Meta Conversions API explained for how the shared event ID works.

How to check: after a test order, reload the thank-you page twice. The platform should still show one purchase.

4. Consent

In the EEA, the UK and Switzerland, advertising tags are generally expected to wait until the visitor agrees. Requirements vary, so check what applies to you.

How to check: open the site in a private window as a visitor from one of those regions would see it. Before you touch the banner, no request should go to an ad platform. Refuse, and it should stay that way. Accept, and the tags should fire. Our article on consent mode and conversion tracking has the details.

5. Server-side delivery

Browser tags lose events to ad blockers, short-lived cookies and tabs closed too early. Sending the same events from a server recovers part of that loss. Before scaling is the right time to add it, because the platform will be learning from a larger volume of events.

How to check: in the platform's events tool, confirm that purchases arrive from both browser and server and are shown as deduplicated. If you see twice as many purchases as orders, deduplication is not working. What is server-side tracking explains the approach.

6. UTM parameters on every ad

UTM parameters label each visit with its source, campaign and ad. They let you build your own attribution from your own orders, independent of what each platform claims.

How to check: click a live ad, or its preview, on each platform. The address bar on your landing page should show utm_source, utm_medium, utm_campaign and utm_content, filled with real values. Templates for each platform are in UTM parameters that map to your campaigns.

7. A full test of the funnel

Checking the purchase alone is not enough. Platforms also use the steps before it, such as viewing a product, adding to cart and starting checkout, to find likely buyers.

How to check: use each platform's test tool and walk through the whole path yourself: landing page, product, cart, checkout, payment, thank-you page. Each step should produce one event with the right name. Do it once on a phone and once on a desktop. Pay with every payment method you offer, since external payment pages are where the return to your site most often fails.

8. An alert when tracking stops

Tracking breaks without warning. A theme update removes the tag. A new security rule blocks it, as described in when a Content Security Policy blocks your tag. An access token expires. The campaign keeps spending while the platform receives nothing, and bidding degrades day by day.

How to check: make sure someone is told within a day when events stop arriving. This can be an automatic alert or a fixed daily routine of comparing shop orders with platform purchases. An automatic alert is more reliable, because routines lapse during busy weeks.

The checklist as a table

CheckPasses when
One tagOne browser purchase request per platform on a test order
Value and currencyThe platform shows the same amount and currency as the shop
Order IDReloading the thank-you page does not add a purchase
ConsentNo ad platform requests before acceptance or after refusal
Server-side deliveryBrowser and server events both arrive and are counted once
UTMsAll four parameters appear, with real IDs, on every platform
Funnel testEach step fires once, on phone and desktop, for every payment method
AlertsSomeone is told within a day when events stop

The last check: reconcile one week

When all eight pass, compare totals. Take seven days and write down three numbers: the orders in your shop, the purchase events each platform received, and the revenue each platform recorded for those events.

The platform's count of received events will rarely equal your shop's order count. Some visitors refuse consent, and some arrive without any ad touch. What you are looking for is a gap you can explain and that stays stable from week to week. A platform showing more purchases than the shop has orders points to duplicates. A platform showing far fewer points to a blocked or missing tag.

Write the three numbers down. They are your baseline. After you raise the budget, run the same comparison again. If the ratio between shop orders and platform events holds, your tracking is keeping up with your spend. Our article on ROAS vs blended ROAS shows how to judge whether the added spend is paying.

Where Tagbreeze fits

Tagbreeze reads your site, proposes a tracking plan, and installs one tag for the whole site through a WordPress or WooCommerce plugin, a Shopify pixel, Google Tag Manager or a pasted snippet. It sends purchases with value, currency and deduplication, waits for consent where required, delivers to Meta and TikTok from its servers as well, and e-mails you when a site stops sending events.

In short

  • Tracking faults grow with budget, so check before you scale.
  • Confirm one tag, correct value and currency, order ID deduplication, consent, server-side delivery, UTMs, a full funnel test and an alert.
  • Reconcile a week of shop orders against platform events, and keep the result as your baseline.

To cover the list in one setup, add your site.

Know what your ads really bring in.

It takes a few minutes. Nothing is changed on your site until you install the tag.

Add your site
Hands on a laptop beside parcels ready to ship