Bidding algorithms are only as good as the conversion data feeding them.
Most agencies treat tracking as setup work that happens before the real campaign work begins. That is backwards. This practice concentrates on the seam where paid media meets measurement, because for a considered purchase that seam is usually the weakest part of the stack.
laurenmilligan.pro — SERVICESSeven areas. They are listed in the order they tend to matter, not the order they are usually sold. Each one below is a mechanism, drawn, because a mechanism you can see is a mechanism you can argue with.
Every chart on this page is a schematic of a mechanism, not a client result. Where numbers appear they are illustrative, chosen to make the shape of the problem legible, and labelled that way on the figure itself. This practice does not publish performance figures it has not measured, and does not quote industry-average recovery rates at prospects. What it will do is measure yours and show you the number.
Most analytics problems are architecture problems that only show up in a report.
A measurement stack is a chain. It is worth exactly what its weakest link is worth, and the weak link is almost never the reporting tool everyone is looking at.
- Container structure and a naming convention that a person who did not build it can read six months later.
- An event taxonomy decided once, up front, rather than accreted one tag at a time.
- Custom dimensions applied at the event level, so segments can be cut later without rebuilding reports.
- Consent configuration that is correct for compliance and correct for conversion modelling, which are related but not the same job.
- Versioned publishing with rollback, so a change to the container is a change you can undo.
- Looker Studio dashboards built against your own sources. No license cost, no reporting platform to keep paying for.
- Legacy tags still firing. Properties from a previous agency, a previous platform, or a previous decade.
- Debug and development artifacts left in production. Nobody put them there on purpose. Nobody removed them either.
- Duplicate measurement. The same event counted twice through two paths, inflating everything downstream of it.
- Untagged surfaces. Usually the highest-value one, because it is the one hosted somewhere else.
- Defaults nobody revisited. Attribution windows, session timeouts, internal traffic filters, and cross-domain settings left as installed.
Decide what counts as a conversion before deciding what to bid on it.
For brands that route buyers to dealers, distributors, or a sales conversation, ecommerce purchases alone rarely produce enough volume for Smart Bidding to work. The algorithm does not fail loudly when it is starved. It just quietly makes worse decisions.
View the values as a table
| Event | Per month | Role |
|---|---|---|
| Dealer locator search | 96 | Primary |
| Dealer detail opened | 58 | Primary |
| Phone number tapped | 41 | Primary |
| Technical download | 34 | Secondary |
| Contact form submitted | 21 | Primary |
| Online purchase | 14 | Primary, and the only one a default setup counts |
| Trade inquiry | 9 | Primary, highest value |
| Stability floor for automated bidding | ≈30 | Working threshold, per campaign, per 30 days |
Optimisation targets. Google Ads bids toward these, so each one has to represent a genuine business outcome. A dealer locator search is a real commercial event for a brand that sells through dealers, and it happens far more often than a direct online purchase.
Measured and reported, used for audience building and diagnostics, deliberately not bid targets. Optimising toward shallow engagement teaches the algorithm to buy cheap, low-quality traffic, which is a failure mode that looks like success for about six weeks.
Targets come after data, not before it. Proposing a cost per acquisition before anything has been measured is a sales tactic, not a strategy. The sequence is thirty days of clean baseline, then a joint target-setting session against known business economics, then quarterly review. See the full method.
Running paid media without it means paying for conversions you cannot see.
Standard tracking runs entirely in the visitor's browser, and that environment has become progressively hostile to measurement. Brands with long consideration cycles are hit hardest, because the gap between the click and the conversion is exactly where the data gets lost.
View the values as a table
| Stage | Change | Running total |
|---|---|---|
| Conversions the account earned | — | 100 |
| Tag blocked at the source | −11 | 89 |
| Cookie lifetime truncated by the browser | −18 | 71 |
| Identity broken across contexts | −9 | 62 |
| Consent or tag failure | −7 | 55 |
| Reported by browser-only tags | — | 55 |
| Recovered by a first-party endpoint | measured | measured |
- More of the conversions you actually earned get reported and credited.
- Attribution windows extend past what browser cookie lifetimes permit.
- Smart Bidding optimises on a fuller dataset, so identical budget buys better allocation.
- The setup is durable. It does not break with each browser privacy update.
- Offline and CRM conversions can be fed back in later, which is what section 04 is about.
- It is not a consent workaround. A visitor who declines is still not measured, by design.
- It does not recover data from before it was installed.
- It does not fix a conversion that was never defined. Section 02 has to come first.
- It runs on infrastructure this practice pays for. If the subscription ends it is decommissioned, and reported conversions should be expected to fall. The full exit position.
A lead that goes nowhere and a lead that becomes a customer are worth very different amounts.
Google Ads treats them identically unless it is told otherwise. Offline conversion import sends the outcome back once it is known, so bidding optimises toward the applications that turn into real relationships rather than toward raw form volume.
View the values as a table
| Inquiry | Counted by Google Ads | Revenue produced |
|---|---|---|
| Inquiry 6, became a dealer | 1 | 100 |
| Inquiry 12, became a dealer | 1 | 72 |
| Inquiry 3, small order | 1 | 6 |
| Inquiry 8, small order | 1 | 4 |
| Inquiry 15, small order | 1 | 3 |
| The remaining 11 inquiries | 11 | 0 |
| Total | 16 | 185 |
The engineering is a solved problem. The real work is agreeing which CRM stage counts as a conversion and what it is worth, which is a business decision with revenue consequences. That is why this is scoped as its own engagement rather than bolted onto a tracking build.
Google moved these uploads onto its Data Manager platform in June 2026, and the previous API path is closed. Much of the guidance still published online describes the older method, which no longer works. Any implementation has to target the current platform.
Separate campaigns, because the economics are not the same.
Brand, product, discovery, and competitor terms behave like four different businesses. Run them in one campaign and the cheap, high-intent traffic subsidises the expensive, speculative traffic, invisibly, and you lose the ability to kill or scale either one on its merits.
View the values as a table
| Campaign | Cost per click | Conversion rate | Budget share |
|---|---|---|---|
| Brand defence | 1.0× | 100 | 20% |
| Product and category | 3.4× | 42 | 45% |
| Non-brand discovery | 4.6× | 18 | 25% |
| Competitor conquesting | 6.1× | 9 | 10% |
- Account architecture across search, shopping, display, video, and remarketing.
- Match type policy and negative strategy, built before launch rather than patched after the first bad month.
- Ad copy written to qualify traffic, not just attract it. At a premium price point an unqualified click is pure cost.
- Budget allocation with floors, so the cheapest and most valuable campaign is never the one that runs dry.
- Built in your account, under your billing, readable by your team.
- Conquesting has legal edges. Bidding on a competitor's brand name is legal and common. Using their name in the ad copy is not safe. Targeting only.
- Conquesting is the slowest payback on the list. Highest cost per click, lowest conversion rate, longest consideration cycle. It gets its own campaign and its own budget precisely so performance data can decide whether it grows.
Changes you can read, review, and reverse.
Ongoing optimisation is where most accounts quietly become un-auditable. Someone changes something, performance moves, and nobody can reconstruct which of the eleven changes that week was responsible. The fix is process, and it is not complicated.
The practical consequence. "What changed in the account last month, why, who approved it, and what would it take to put it back" is a question with a written answer, not a question that starts an archaeology project.
Answer engines do not rank pages. They cite a handful of sources.
Which makes the optimisation target position-independent. It is not "be number three", it is "be the thing that gets quoted". Three mechanisms decide that, and they are not equally powerful.
- What the engines say about you today, verbatim, with the date and the prompt that produced it.
- What was changed, and when.
- Whether citation changed after the change, with the sample window stated on every figure.
- Tracking on a fixed query set, so the result is a trend rather than an anecdote.
- That a ranking or citation position is achievable.
- That any specific engine will cite you.
- A percentage improvement, quoted before your own data exists.
- Anyone who does promise those things is describing a mechanism that does not work the way they are saying it does.
The question is not what the API allows. It is what an agent should be trusted to do unattended.
Agents genuinely do useful work against a marketing stack. They also have a live credit card attached to the account, which is a category of mistake most software cannot make. So the interesting design work is authority, not capability.
- Account allowlist. Anything not explicitly listed is refused before a request is even built.
- Writes fail closed. The write path is off by default and has to be deliberately enabled.
- Mandatory dry run. Every mutation validates first. Any validation error and nothing is applied.
- Budget ceiling and delta cap. No single change can raise spend beyond a configured percentage, regardless of who asked for it.
- Operation ceiling. Large changesets have to be split and re-approved rather than applied in one swing.
- Provenance labels. Everything the agent creates is tagged with the run that created it, so it is findable and reversible in bulk.
- Append-only journal. Every mutation recorded with its inverse operation.
- Reporting and monitoring. The work that is genuinely repetitive, genuinely high-volume, and genuinely low-risk.
- Search term and negative keyword hygiene. Continuous rather than monthly, which is the whole difference.
- Anomaly detection. Noticing on the day, rather than in the monthly review.
- Workflow automation across your own tools, configured against your data rather than a generic template.
- Coaching your team, including the unfashionable half of the advice: where AI genuinely belongs in a marketing organisation, and where it does not.
The honest version. Most of what is sold as marketing AI right now is a wrapper with no audit trail and no way back. The value is not in letting an agent do more. It is in defining precisely what it may do, recording everything it did, and being able to undo any of it. That is unglamorous, and it is the part that makes the rest safe to use.
Build it, hand it over, stay reachable.
Engagements are shaped in three parts. Not every client needs all three, and the third one is designed so that it does not quietly become a permanent dependency.
1. A fast campaign, if there is a date to hold
A tightly scoped launch that gets brand, product, and competitor search live in days rather than weeks, with baseline conversion tracking pulled forward so the first traffic is measured rather than merely spent. Fixed fee, milestone billed.
2. The build
The real engagement. Account architecture, measurement infrastructure, dashboards, recorded training, and a written runbook. Fixed fee, three milestones: kickoff, infrastructure complete, training accepted. Deliverables are inspectable and inheritable. Nothing is built that only this practice can operate.
3. The subscription
After launch, a monthly base tier that holds the measurement infrastructure, keeps the dashboards current, runs a quarterly strategy workshop with a written plan, and keeps advisory access open. Campaign management is an add-on you choose, not a floor set for you.
The distinction matters. A build priced as counsel and a build priced as management look similar on paper and behave very differently after month three. If your team wants to run daily operations, the model should let them, and the price should reflect it.
Senior strategy, never delegated
Strategy is designed, approved, and directed by Lauren Milligan. That does not change partway through an engagement. Day-to-day execution may be supported by vetted subcontractors working under that direction, which holds delivery timelines during build phases without handing you to a junior team. laurenmilligan.pro remains fully liable for all work completed by any subcontractor, stated explicitly in the service agreement. Your contractual relationship is with this practice alone.
The handoff is the point.
A build you cannot inherit is not a deliverable, it is a subscription with extra steps. Everything below is yours from the day it is created, in your own accounts, and none of it is held back as leverage if the relationship ends.
| Asset | Where it lives | Yours |
|---|---|---|
| Campaigns, ad copy, keyword lists, audiences | Your Google Ads account, your billing | Permanent |
| GA4 property and reporting configuration | Your Google Analytics account | Permanent |
| Google Tag Manager container | Your GTM account | Permanent |
| Looker Studio dashboards | Your Google account, no license fee | Permanent |
| Strategy documentation and written runbook | Delivered as files | Permanent |
| Recorded training sessions | Delivered as files | Permanent |
| Server-side tracking container and endpoint | Our infrastructure, our cost | While subscribed |
The last row is the honest one, and it is stated here rather than discovered later. The server-side layer runs on infrastructure this practice pays for as part of the subscription. If the subscription ends, it is decommissioned and measurement reverts to standard browser-based tracking, which is what most accounts run on. Campaigns keep running. Nothing is switched off and nothing is deleted from your accounts. Reported conversions should be expected to fall, and that difference is precisely what the subscription pays for. The full exit position is here.
Boring, predictable billing.
A subscription model only works if the mechanics are dull. These are the mechanics.
- One subscription, one invoice, one charge. The base tier and every active add-on bill together. You are not reconciling six line items from six agreements.
- Charged on the 1st, in advance. A card or bank account on file, charged automatically. Nothing to route, approve, and pay each month, and therefore nothing to go past due.
- Add or drop any add-on by the 25th, effective the following 1st. Mid-month additions are prorated to the portion actually used. Removals take effect at the period boundary.
- Base subscription cancellable with 30 days written notice. No annual lock, no early termination fee.
- Receipts and payment details are self-serve. Every invoice is available on demand and card details can be updated without going through us.
- Build phases are separate. Invoiced at milestone, or converted to equal monthly payments over three or six months at the same total, with no financing charge. Ending one does not affect the other.
- No hourly billing. Project work is quoted as a fixed amount before it starts. No open-ended engagements where the number is only known afterward.
Media spend is paid directly to the ad platform on your own card. It does not pass through this practice, which keeps the invoice clean and keeps the account in your name.
Start with the homework, not the pitch.
Most proposals are written without having looked. A preliminary technical review of your site, its tag configuration, and its conversion paths comes before any recommendation, and it is not billed.
Request a technical review