Process
How an engagement runs: audit, track, build, launch, scale.
The order is the point. We do not touch budgets until the conversions feeding the bidding are correct, and we do not scale until reconciled numbers — not platform-reported ones — say the economics hold. Each stage has a written output and a decision at the end.
-
Audit
Week 1
Read-only access to the ad accounts, the tag container, analytics, and whatever holds revenue — a payment processor, a CRM, a store console. We trace a handful of real conversions end to end and compare what each platform claims against what you actually banked. Then we read the account the way a bidding algorithm reads it: goals, values, structure, signals.
Output
A written audit: measurement gaps ranked by impact, account issues ranked by wasted spend, target economics agreed with you, and a plan with a price. You can take it and leave.
-
Track
Weeks 2–3
The engineering stage. A server-side Google Tag Manager container on your subdomain, enhanced conversions sending hashed first-party data, consent mode configured for the markets you sell in, GA4 and the ad platforms agreeing on what a conversion is, and offline or payment-processor events imported with real values. Every change goes through a test plan: a conversion we trigger must land in every destination with the right value before anything is switched on.
Output
A measurement setup you own, with a tag map and a runbook, and a verified conversion feed for each platform.
-
Build
Weeks 3–4
Accounts are rebuilt or restructured for Smart Bidding: fewer, denser campaigns; conversion goals that mirror your margins; value rules by market, device, or product; audience signals that help rather than restrict. Ads and assets are written from search-term and CRM data, landing pages are checked for the things that quietly cost conversions, and Microsoft Ads and Meta are set up to report into the same place as Google.
Output
Structured accounts in your manager account, a shared dashboard reconciled to revenue, and a launch plan with initial budgets and targets.
-
Launch
Weeks 5–8
Controlled budgets while the bidding models learn on the new conversion feed. We resist the urge to change things daily: targets move in steps, experiments run long enough to read, and the weekly note tells you what we changed, why, and what we expect to see next week. Platform reports are read with skepticism and checked against the reconciled dashboard.
Output
Stable cost per conversion at the agreed target, learning periods completed, and a go / adjust / hold decision on scaling.
-
Scale
Monthly, ongoing
Budgets rise where payback holds and move between Google, Microsoft, and Meta as the reconciled numbers dictate. New markets launch one at a time with their own targets. The measurement is re-verified every month, because tags break quietly. Every month closes with an economics review: spend, conversions, revenue, payback — in your currency, against your targets.
Output
Monthly economics review, a change log you can audit, and a measurement health check with anything broken already fixed.
Working together
Logistics, so there are no surprises.
Your accounts, always
Ad accounts, tag containers, analytics properties, and dashboards are created under your ownership and linked to our manager account. Revoke access in a minute if you ever need to; nothing moves.
Time zones
Gulf Standard Time (UTC+4), Sunday through Thursday, with launches covered whenever they land. European clients share an afternoon with us; North American clients a morning.
Cadence
A written change note every week. A 30-minute call every two weeks during launch, monthly afterward. A shared dashboard that is always current. No surprise reports and no slideware.
Fees
Flat monthly fees agreed after the audit, tiered by scope and budget band — never a percentage of spend. Ad budgets are paid by you directly to the platforms.