The signal you feed the platform is the signal it learns

Smart Bidding, Advantage+, and every other ML-driven optimiser only optimises for what you tell it matters. If your conversion event is "form submitted" and half of those forms are bots or unqualified leads, the system will diligently find you more bots and unqualified leads. The fix is not better targeting; it is a cleaner signal.

Server-side first

We deploy server-side tracking on every account we manage. The browser pixel still fires for fast feedback, but the source of truth is a server-side container that captures the event after our backend has had a chance to validate it — bot filtering, basic deduplication, enrichment from the CRM where available. That validated event is what we forward to Google, Meta, and any other downstream platform.

The benefits compound. We lose less data to ad-blockers and ITP, we get cleaner attribution, and we can correct or suppress events after the fact when the CRM tells us a lead was junk.

Offline conversion imports

For lead-generation accounts the next step is offline conversion imports. Form fills are a leading indicator; what the business actually cares about is qualified pipeline and closed revenue. We push CRM stage changes — MQL, SQL, Opportunity, Closed Won — back to the platforms with the original click identifier attached, and we re-train Smart Bidding on the stage that correlates best with revenue.

The first thirty days after switching a lead-gen account from "form fill" to "SQL" optimisation usually look like a step backwards. CPL goes up. By day sixty the cost per qualified pipeline opportunity is lower, often by thirty to fifty percent, and the sales team starts noticing the difference in lead quality.

Events we always track

For ecommerce: page view, view content, add to cart, initiate checkout, purchase, and a dynamic value field on each. For lead-gen: page view, form view, form start, form submit, MQL, SQL, opportunity, closed won. For SaaS: page view, signup, activation, trial-to-paid, expansion. The exact list matters less than the discipline of mapping it once and not letting it drift.

Common failure modes

The mistake we see most often is firing both a browser-side and a server-side event with mismatched event IDs, which double-counts conversions inside the platform without anyone noticing for weeks. Deduplication at the platform level requires a stable, shared event ID. We test it on every deploy.

The second is forgetting that offline conversion imports require the original click identifier. If the form does not capture and persist the gclid or fbclid into the CRM record, the import will succeed and silently match nothing.

What good looks like

A healthy account has tracking that the marketing team can explain in one sentence, that the engineering team can audit in one afternoon, and that the platforms can use to optimise on the metric the business actually cares about. Anything else is a shaky foundation, and no amount of bidding strategy or creative work will make up for it.