Prepared 2026-05-31 · all numbers verified against Google Ads API v22 + HubSpot + Microsoft Clarity
"Month 1 wasn't a failure — it was a paid-media diagnostic. In 30 days, on a brand-new account, we isolated exactly where Lucidya converts — Arabic buyer-intent in KSA and UAE at $23–$229 per qualified lead — and exactly where the leak is — the US landing pages, not the ads. We did that at a fraction of the prior agency's $10,500 per SQL. We don't have a performance problem; we have a clear, data-backed plan to convert what we learned into volume."
Why this works: it reframes the whole meeting from "defend the failure" to "here's what the data proved." You're the expert presenting findings, not the vendor explaining mistakes.
(Lead with these. Numbers shut down suspicion faster than adjectives.)
| Metric | Result | Note |
|---|---|---|
| Spend | $15,495 | US $7,866 · KSA $6,400 · UAE $1,229 (separate budgets) |
| Inbound leads | 33 | verified form submits synced to HubSpot |
| MQLs | 7 | |
| SQLs | 5 | concentrated in KSA + UAE |
| Blended cost/SQL | ~$3,100 | vs prior agency ~$10,500/SQL = ~70% cheaper |
| Account rebuild | 114 → ~11 campaigns | from the prior agency's mess |
Interpretation: the qualified-lead economics are already strong; the gap is volume and a 60–90 day B2B sales cycle that hasn't closed yet. This is a normal, healthy Month-1 base — not a failure.
| US campaign | CTR | CPC | LP conversion rate |
|---|---|---|---|
| USAIAgent | 11.4% | $3.02 | 0.45% |
| USGeneric | 11.0% | $2.54 | ~0.5% |
| USOmniServe | 8.0% | $5.68 | 0.00% |
| US_COMP_EN | 1.0% | $27.46 | 0.00% (the one real ad-side miss) |
| Benchmark | ~3–5% | — | 2–5% |
Interpretation (say this almost verbatim): "Three of four US campaigns ran 8–11% CTR at $2.50–$5.70 CPC — well above benchmark. The ads did their job; people clicked. The conversions died on the landing page — the OmniServe product page converted 0% on ~597 clicks ($2,825 spent) because it's a product page, not a conversion page with a lead form. That's a CRO problem, not an ad problem. Honest read: some of the zero is also lower-intent traffic from certain keywords — so it's not 100% the page — but the dominant, fixable leak is the landing page."
| Paid destination | Clicks | Conv | Spend | Verdict |
|---|---|---|---|---|
/products/omniserve (generic product page) |
~597 | 0 | ~$2,825 | broken as a conversion destination |
/ai-agent-ppc (dedicated PPC page) |
~1,400 | 17 | — | converts — where we're moving everything |
Interpretation: ~$2,825/mo recovered immediately by routing all paid to dedicated conversion pages. This is the single highest-impact fix and it's in Week 1.
| KSA week | Spend | Clicks | Conversions |
|---|---|---|---|
| Wk2 May 3–9 | $2,041 | 393 | 11 |
| Wk3 May 10–16 | $1,860 | 368 | 8 |
| Wk4 May 17–23 | $1,615 | 329 | 8 |
| Wk5 May 24–30 | $853 | 212 | 1 |
Interpretation: in Week 5 clicks fell only ~35% but conversions collapsed ~88% — demand held, conversions didn't. It lands exactly on the Hajj + Eid al-Adha holiday (late May) when KSA enterprise buying pauses. Our optimizations shipped May 30, after the dip — we didn't break it. It normalizes post-Eid.
| Campaign | Cost/conv | Note |
|---|---|---|
| BrandAR_KSA | $23 | best in account · 4.98x ROAS |
| AIAgentEN_UAE | $176 | most efficient market · hit its 1 SQL |
| GenericAR_KSA | $233 | volume leader · losing 40% of impressions to budget cap |
| ProdEN_KSA | $501 | losing 65% to budget cap |
Interpretation: the volume lever is mechanical — our best KSA campaign is rationed by its budget cap. Lift it and volume follows.
(Built from Ahmed's DMs. These are the exact things they'll hit you with.)
Q: "Did you pause the US campaigns?"
Yes — all US campaigns off except the competitor campaign, capped at $1K/mo as the approved test. Done.
Q: "Why are we only flagging the GCLID / offline-conversion thing now? Why wasn't it fixed in April/May?"
"Online conversion tracking worked from day one — that's how we have the funnel. Offline-conversion import is the next layer, and you can't wire it on day one with zero conversions to sync. It only becomes relevant once there's a month of pipeline data. Flagging and deploying it now, with data behind it, is the proactive cadence — not a delay." (Don't apologize. This is standard sequencing.)
Q: "Okay — how are you actually going to achieve that?"
"Four steps, this week: (1) audit GCLID capture on the lead forms, (2) enable the HubSpot ↔ Google Ads offline-conversion connector, (3) map stage-weighted values (Lead $5 / MQL $50 / SQL $500), (4) verify end-to-end with a test conversion. Then Smart Bidding optimizes to SQLs, and we report the cost/SQL trend monthly against your actuals."
Q: "How did you launch ads to a landing page that has an ICP mismatch? A good agency should have flagged that."
"In a brand-new channel, Month 1's job is to test destinations and let the data pick the winner — which it did. The data verdict is clear: dedicated PPC pages convert, generic product pages don't. We're now consolidating all paid onto the pages that convert. Pre-judging that without live data would've been guessing — which is exactly what the last agency did. We tested, we have the answer, and we're acting on it." (This flips "you should've known" into "we let data decide, like a disciplined operator.")
Q: "Was it the ads or the landing page that failed?"
"Mostly the landing page — and we can prove it. The ads pulled 8–11% CTR at ~$3 CPC, above benchmark. The leak is post-click: the OmniServe page converted 0% on ~600 clicks. That's a CRO problem. To be straight, some of the zero is also lower-intent traffic from certain keywords — so it's not 100% the page — but calling it an ad failure wouldn't be honest. The fixable leak is the page and the keyword intent, both in the plan."
Q: "It's not looking good — why should we expect a turnaround / renew?"
"Because the volume lever is mechanical, not mysterious. Our best KSA campaign is losing 40% of its demand to a budget cap — it converts and we're rationing it. Lift the cap, wire offline conversions, fix the landing pages — volume follows. We've put a measurable bar in writing and we'll report against it every Monday. Hold us to that bar."
Q: "The report's too text-heavy / those commitments are vanity metrics."
"Agreed — fixed. The report now opens with a one-page action → owner → date → expected-result table. The vanity slide is gone."
Q: "Don't reallocate to MENA — the budgets are separate."
"Understood and corrected. MENA scales within MENA; the US budget stays in the US and pivots to offline activities, exactly as you said."
"Real talk, operator to operator: the accounts that perform best for us are the ones that set the target and let the team run. Our biggest-investment clients give us the most room day-to-day, not the least — it's not a coincidence. When every daily data point gets treated as a crisis and every call gets re-litigated mid-flight, it pulls the team off optimization and into defense, and it becomes self-fulfilling. Hold us accountable to the Month-2 bar we put in writing — and let us run the path to it. That's the setup that produces the numbers."
hey man — quick hits before month 2: - month 1 wasn't a fail, it was us finding the signal. KSA + UAE convert at $23–$229/lead; old agency was ~$10,500/SQL on 114 messy campaigns. strong first month, not a crisis. - GCLID/offline conversions isn't something we missed — online tracking worked day 1 (that's how we have the funnel); offline is the next layer you wire once there's pipeline to sync. flagging it now = proactive. - the US "failure" was the landing page, not the ads — 8–11% CTR (above benchmark) but the OmniServe page converted 0% on ~600 clicks. that's CRO. we're moving all paid to pages that convert and recovering ~$2,825/mo. - budgets kept separate — MENA stays MENA, US goes to offline like you said. - report's simplified to an action → result table, vanity slide gone. - volume lever is mechanical: our best KSA campaign is capped and losing 40% of its demand — lift it + wire offline conversions this week and volume follows. - real talk: the accounts that crush it for us set the target and let us run. hold us to the month 2 numbers in writing, but let us drive the how — that's what gets you results. - i know you're getting grilled up top; not making it harder, just giving you the straight version so we can both kill the crisis narrative and let this work.
"Month 1 told us exactly where Lucidya wins and exactly what to fix. Month 2 is execution against a measurable bar, reported weekly. Set the target, hold us to it, and let us run."
Sources: Google Ads API v22 (campaign_summary, daily_trends, landing_page_breakdown, search_terms, ad_creative_performance) · HubSpot CRM paid-source funnel · Microsoft Clarity (rolling window: US 20% scroll/6s active vs MENA 41%/56s, corroborates LP bounce). GA4 (G-VNFHMFDBEC) live but no Data-API service account provisioned — session-level funnel is a fast-follow.