Our Tracking Isn't Set Up, So the Ads Can't Optimize

Why bad tracking makes campaigns worse

Modern ad platforms optimize automatically toward the conversion you give them. If that signal is wrong, the automation gets very good at the wrong goal.

The conversion event is too easy

A page view, a scroll or a newsletter signup happens often, so the platform learns fast and finds people who do that, not people who buy.

Events fire twice or not at all

A thank-you page that reloads, a form that fires on every step, or a tag that broke in the last site update. The platform sees a pattern that is not real.

The signal stops at the form

Nothing tells the platform which leads became qualified or paying. Without that feedback it cannot tell a good lead from a bad one.

Browser losses thin out the signal

Consent choices and blockers hide part of the conversions, so the platform learns from a smaller and less representative sample.

Six checks in your ad accounts

Open each ad account and your tag manager, and answer these.

• Write down which conversion each campaign optimizes to. Is it a lead, a qualified lead or a payment?
• Submit a test form and check the conversion fires once, and only once, in each platform.
• Compare last month's platform conversions with the matching records in your CRM.
• Check whether qualified or closed leads are sent back to the platforms as offline conversions.
• Check that you can see, per campaign, how many visits became demo requests.
• Look at the date of the last site or form change, and check that the tags still fire after it.

Clean events, then a closer goal

First, make the basic events trustworthy: one clean conversion per real action, tested from the form to each platform. Then choose the optimization goal closest to revenue that still happens often enough for the platform to learn, and send qualified or won leads back from the CRM so the platform can learn which leads matter.

Where browser tracking loses too much, server-side tracking recovers part of the signal. A tracking audit covers the full check, and the GA4 and GTM checker linked below is a quick first look.

Tracking rebuilt at Riverside.fm

At Riverside.fm my case study describes server-side tracking to recover the signal that iOS and consent changes had stripped out, and conversion events tied to actual subscription revenue rather than to lead capture. The case reports 337% Net MRR growth during my paid-acquisition work, alongside the work of Riverside's own teams; it does not isolate how much came from the tracking work.