Will you know by Saturday morning if Black Friday is working?Get your free measurement plan →
Analytics Mates

Product Log

What we shipped — and the primary source behind every change.

Ad platforms and analytics schemas change constantly. When Google, Meta, or GA4 updates an API contract, we update The Helm and cite the exact specification that triggered the change.

Signal Dispatch
#2026-11-05-data-manager-v1-9

Google Data Manager API v1.9: Row-level async diagnostics, native call conversions & lead_id guardrail

Updated the Google Ads Data Manager dispatch and verification layer within 24 hours of Google’s v1.9 release to resolve asynchronous batch failures to exact Order IDs and support native call conversion timestamps.

What changed in The Helm

  • Preserves zero-based batch record order on every events:ingest call and maps v1.9 record_indices from requestStatus:retrieve back to individual transactionId / Order IDs.
  • Classifies asynchronous diagnostic reasons into terminal (e.g. TIMESTAMP_PRECEDES_CLICK, EXPIRED_CALL) vs. retryable warm-up states (RECENTLY_CREATED_CONVERSION_ACTION), plus automatic network-drop and 429/5xx backoff.
  • Adds call_info.start_timestamp support for native Google Ads call conversions matched via E.164 SHA-256 phone hashes.
  • Passes through ad_identifiers.lead_id when present alongside click or user identifiers while blocking lead_id-only events at pre-dispatch validation until Google enables lead_id attribution.

Why it matters for measurement integrity

Previously, a partial batch failure during Google’s asynchronous processing reported only aggregate reason counts. The Helm now pinpoints the exact rejected Order ID without re-sending accepted records or risking duplicate conversions.

Verifiable sources

Measurement Audit
#2026-11-04-audit-bidding-evidence-gate

Deterministic bidding-impact gate on GA4 & Google Ads audit scores

Separated hygiene checklist passes from bidding-critical findings so an audit never claims Smart Bidding or ROAS impact unless a conversion or ad-link check actually failed.

What changed in The Helm

  • Displays the 0–100 score and Smart Bidding impact verdict only when a run detects a confirmed bidding issue (missing key events, missing lead/purchase event, engagement metric marked as a key event, or unlinked Google Ads account).
  • Marks checks that timed out or lacked permission as Not verified rather than counting them as passed or failed.

Why it matters for measurement integrity

Eliminates false reassurance when a property passes surface-level hygiene checks while conversion signals or ad-platform links remain unverified.

Verifiable sources

Measurement Audit
#2026-10-28-bfcm-measurement-plan

Black Friday Measurement Plan & 63-account GA4 benchmark dataset

Launched a public pre-flight scanner for ecommerce stores plus anonymized Black Friday 2025 benchmarks across 63 GA4 properties.

What changed in The Helm

  • Scans public store pages, sitemaps, and tag containers to verify purchase event readiness, coupon tracking, and channel attribution before Black Friday.
  • Published store-normalized Fri–Mon lift benchmarks (+27% median revenue lift, −20% AOV, 1.2% conversion rate) paired with post-BFCM GA4 replay verification.

Why it matters for measurement integrity

Gives ecommerce operators and agencies a pre-holiday verification checklist grounded in real GA4 account baselines rather than generic holiday marketing advice.

Verifiable sources

Signal Dispatch
#2026-10-27-data-manager-cutover-and-normalization

Google Data Manager API `events:ingest` cutover & E.164 / Gmail canonical hashing

Completed migration from legacy Google Ads offline conversion uploads to the Google Data Manager API (`events:ingest`) with strict identifier normalization.

What changed in The Helm

  • Enforced canonical SHA-256 identifier formatting across all OCI builders: E.164 phone numbers with leading + (+1XXXXXXXXXX) and Gmail/Googlemail dot and +suffix stripping prior to hashing.
  • Added legacy EAIaIQob...BwE and modern Cj... GCLID validation while routing GBRAID-only leads through Enhanced Conversions for Leads (userData) rather than GCLID-mapped columns.
  • Enforced idempotent transactionId deduplication across Google Sheets and events:ingest cutovers.

Why it matters for measurement integrity

Daily delivery runs through Google’s API with a verifiable request status for every batch, and canonical hashing prevents silent match-rate loss caused by unnormalized phone or Gmail hashes.

Verifiable sources

Want your conversion pipeline governed with the same rigor?

See how Signal Dispatch and The Helm verify every conversion from CRM to Google Ads and Meta.

Explore Signal Dispatch → Book a Measurement Review →