New vs returning customers
A repeat buyer often gives the cheapest conversion, so the panel likes chasing it. I steer bidding toward new customers, because that is where the business grows.
I put budget behind real sales, not panel noise.
Adding budget will not help if the algorithm gets the wrong signal. I fix the data first. I connect paid media, GA4, GTM, server-side tracking, imports, reports and automation into one working setup. The panel should see sales, leads and margin, not random events.
The panel will find a cheap conversion if you give it that target: a repeat customer, an empty form, revenue with no margin. I set the goal so budget follows new customers, quality and financial result. That needs data you can defend.
A repeat buyer often gives the cheapest conversion, so the panel likes chasing it. I steer bidding toward new customers, because that is where the business grows.
A cheap lead can take the most sales time. I connect CRM stages and quality, so the campaign learns from leads that close, not just from CPL.
Revenue-based ROAS can look falsely good. I pass margin and profit into the platform, so budget moves to what actually earns money.
In Shopping and PMax, the feed shapes the auction. Titles, attributes, GTIN, structure and rules are part of optimisation, not admin work.
Some conversions disappear on the way because of browsers, ITP and missing consent. Server-side GTM and CAPI move measurement to the server, recover lost events, deduplicate them and add what the pixel did not see. The algorithm gets fuller data for bidding.
Server-side GTM, CAPI and Consent Mode v2 recover conversions lost by browsers and missing consent. Usually a double-digit share of the signal returns to the platform, so the algorithm sees more than the pixel alone.
After CRM stages and quality are connected, the campaign stops looking for the cheapest CPL. It learns from leads that move toward sales, not just from submitted forms.
Ad costs, orders, leads, CRM and margin sit in one report. Without jumping between panels, you see where budget earns money and what to cut before the next reallocation.
I run campaigns on sales data, not only clicks and empty conversions.
I build measurement so the panel, GA4, store, CRM and database speak the same language.
I build reports, pipelines and automations that reduce manual work and show the decision faster.
stores, feeds, LTV
D2C, compliance, retention
multi-market, margin
lead gen and CRM
pipeline and lead quality
consent, sources, attribution
volume and control
The panel, GA4, store, CRM and database must agree on conversions, value and margin. I close the gaps before increasing budget.
Campaign, tag, consent, server, offline import and dashboard are one chain. I take the plan, build and tests myself, so the issue does not fall between people.
You end with a fixed tag, a conversion import, a pipeline, SQL, a report or a pacing rule. Every change has an owner, a test and a result.
Planners calculate budgets, alerts catch anomalies, agents collect data. Any panel change still goes through review and sign-off.
The panel reports a drop in conversion value? I do not cut budget first. I compare the panel with sales, CRM and the database. If the source does not show a drop, the signal is broken: tag, consent, import or deduplication.
Send what does not add up: ROAS, leads, conversion value or sales. I will tell you where I would start checking: tracking, campaign structure or data. If there is enough to work with, I will suggest a short signal audit. No sales deck.
My name is Vladyslav Iukhnovych. I have 10+ years in performance, measurement and data. I run SEM Rubicon myself, with Google Partner status. You work directly with me from audit to implementation.