Data note · not a diagnosis
Treat 14 July as a partial day, not a genuine data point
This report was pulled on 14 July itself, so that day is still in progress — sessions are still arriving, GA4 hasn't had the full 24 hours to classify
engagement (10+ seconds, 2+ pageviews, or a key event), and Google Ads conversions for the day are still being counted and attributed. That's why
engagement rate and conversions both read unusually low for 14 July specifically: it's an incomplete-day artefact, not a tracking break or a real
collapse in visitor quality. The 1–13 July trend is the reliable read; 14 July should be excluded from any MoM/YoY/PoP conclusions until it has
fully closed out (GA4 typically needs 24–48 hours to finalise a day's data).
Headline performance (all 4 cities combined)
Performance by city — consolidated
Each cell: current value (1–14 Jul '26), with % change vs MoM (1–14 Jun '26) and YoY (1–14 Jul '25) below. Head Terms + Categories combined per city.
Daily trend — 1–14 July 2026
Chart library did not load (offline preview). Data is in the table below the callout.
Reading the dip: conversions firmed up 7–9 July right after the EOFY→Christmas keyword switch, then fell away from 10 July onward.
Note 14 July is a partial day (see banner above) since this report was pulled today — its low reading is an incomplete-day artefact, not part of the real trend.
Impression share lost — Budget vs Rank (1–14 July 2026)
Impression-weighted average across each city's combined campaigns.
Impression share won
Lost to Ad Rank
Lost to Budget
Budget isn't the constraint. Budget-lost impression share is ~0% in every city this period — campaigns aren't being capped by spend.
The losses (56–66% of eligible impressions) are almost entirely Ad Rank driven, i.e. bid/Quality Score relative to competitors.
Change log — mapped to the review window
Competitive landscape — Auction Insights (1–14 July 2026)
Frequency a domain appeared alongside ATB in the auction, by city (Windsor.ai does not expose per-domain impression share/overlap rate for this connector, so counts are a frequency proxy, not a share metric).
Key insights — why is ATB performance down?
GA4 Engagement — Amazing Team Building property
Sessions attributed to ATB Google Ads campaigns (session_google_ads_campaign_name), matched to city the same way as the Ads tab. Period-over-period (PoP): 1–14 July 2026 vs the immediately preceding 14 days, 17–30 June 2026.
14 July is a partial day — this report was pulled on 14 July, so that day hasn't fully closed out yet. Engagement rate reads 4.8% that day
(vs 60–80% on every other day in the window) simply because GA4 hasn't had the full 24 hours to classify sessions as engaged, not because tracking broke.
Treat 14 July as incomplete and lean on 1–13 July for the real trend; re-check this once the day has fully processed (usually 24–48 hours).
Headline engagement (all 4 cities combined)
Engagement by city — consolidated
Each cell: current value (1–14 Jul '26), with % change vs the prior 14 days (17–30 Jun '26) below.
Daily engagement rate — 17 June to 14 July 2026
Chart library did not load (offline preview).