Hermesby WeDiscover

Maya clicked an ad on a Tuesday. Three weeks later she bought a kitchen.

Here’s how every system that needed to know found out. That means the ad platforms that optimise your campaigns, the analytics your reports run on and the warehouse your finance team trusts. One row, carried back by Hermes.

What Maya did · what the site captured

Day 0

Maya taps a Google ad on her phone.

Before she reads a word, the page saves the details that will matter in three weeks.

Captured on the page - the right data, in the right place

  • gclid - from the landing URL
  • client_id - GA4 _ga cookie
  • session_id - GA4 _ga_XXXX cookie
  • _fbp - set by the Meta pixel on load
  • utm_source=google · utm_medium=cpc
  • user agent · consent state

What each system knew

What each system knew

  • Google Adsclick ✓ (gclid issued)
  • Metapageview ✓ (_fbp set)
  • GA4session_start ✓ client_id 1823…
  • CRMnothing yet

Four systems, four different ideas of who Maya is. The only thing linking them is what the page just captured.

What Maya did · what the site captured

Day 014:06

She books a consultation.

She accepts cookies and fills in the form. Her details go to the CRM, and so do the identifiers. This step is what lets us link the sale on Day 24 back to the ad.

Persisted to the CRM with the lead

  • email · phone - hashed before they ever leave
  • gclid · _fbp · client_id · session_id
  • event_id 9f1c6d2e - the web event’s id, kept for dedup
  • consent_advertising ✓ · consent_analytics ✓

What each system knew

What each system knew

  • CRMlead ✓ ids stored · consent stored
  • Google Adsconversion: lead £0 ✓ - a proxy
  • MetaLead ✓ event_id 9f1c6d2e (pixel)
  • GA4generate_lead ✓ in Maya’s session

Every system saw the form. Left alone, the platforms will optimise for more forms. Hermes tells them what the form became.

What Maya did

Day 24

Maya signs. £12,400.

After a showroom visit, sales marks it won and finance sends the invoice. The sale happens outside the browser, so until Hermes runs, the ad platforms only know about the form.

What each system knew

What each system knew

  • CRMwon ✓ £12,400 · order ORD-88213
  • Google Ads- still a £0 lead
  • Meta- still a Lead
  • GA4- no purchase event

What left the warehouse

Day 2406:00

Overnight, one row leaves the warehouse.

The row - hashed at source · validated · 3 consent gates · routed

  • purchase · 2026-07-01T06:00Z · value 12400 GBP
  • email_hash 3a7bd3e2… · phone_hash 9c2f…
  • gclid · _fbp · client_id 1823… · session_id
  • event_id 9f1c6d2e · order_id ORD-88213
  • consent_advertising ✓ · consent_analytics ✓
  • platforms_to_fire: google_data_manager, meta, ga4

What each system knows now

What each system knows now

  • Google Adspurchase £12,400 ✓ matched on gclid + hashed email
  • MetaPurchase £12,400 ✓ deduped against the Lead on event_id
  • GA4purchase ✓ stitched to Maya’s session via client_id
  • BigQuerylogged ✓ every response, for audit and alerting

One row, three destinations, three jobs. Two ad platforms get a real conversion to bid on. Your analytics gets the event in the right session. The warehouse keeps the receipt.

What the business sees

Monday

The sale lands in the reports.

The purchase reached GA4 with Maya’s client_id and session. So it sits in the same reports as every web conversion, by channel, campaign and landing page, and in BigQuery for finance. Marketing and finance now work from one number.

GA4 · BI · finance

Revenue by channel · last 30 days · GA4 → Looker

  • Paid search£61,900
  • Paid social£33,200
  • Organic£24,100
  • Direct£14,600

incl. offline purchase · Maya · £12,400 · via Hermes. Also lands in GA4 explorations and audiences, BigQuery, and the finance model that reconciles ad spend to revenue.

From first touch to final sale, Hermes joins up the journey, so every system that needs to know, knows.

Connect your conversions