All recoveries

Implementation recovery

MyPati.my: conversions started counting again

Using a Stape-hosted GTM Server setup, the last 30 days show measurable recovery from tracking prevention and ad blockers. Key commerce and authentication events are disproportionately impacted by browser restrictions. The project focuses on hardening the sGTM implementation, enriching Meta CAPI payloads, improving event coverage and deduplication, and validating accuracy end-to-end.

30 daysSep 9, 2025Pro
Start 7-day trial
MyPati.my after recovery

What was broken

  • 15.56% of container activity affected by tracking prevention (ITP) in the current billing window.
  • 13.71% TP impact and 4.09% ad‑block impact on ScriptLoad events, indicating blocked client resources.
  • Purchase events show 25% tracking prevention impact (n=12).
  • Login events heavily impacted by ad blockers (41.38% ad‑block rate; n=58).
  • ViewItem events impacted by ad blockers (30.88% ad‑block rate; n=272).
  • SignUp events impacted by tracking prevention (50% TP; small sample, n=6).
  • CookieKeeper requests are 100% under TP context (expected behavior under Safari ITP).

What we rebuilt

  1. 01Reinforce first‑party sGTM endpoint and routing to minimize ad‑block patterns.
  2. 02Implement robust event_id deduplication and enrich Meta CAPI with fbp/fbc and hashed user parameters where consented.
  3. 03Capture key commerce events server-side (ViewItem, AddToCart, BeginCheckout, Purchase) with parameter parity to client.
  4. 04Harden consent passthrough (Consent Mode v2) and align GA4 and Meta payloads to consent state.
  5. 05Tune Cookie Keeper and link decoration for Safari to sustain first‑party identifiers.
  6. 06Set up validation workflows in Meta Events Manager and GA4 DebugView with automated anomaly alerts and a Looker Studio dashboard.

Before vs after in the tools that matter

Screens from the stack buyers already live in. Not a fake dashboard. Click either frame to enlarge.

Before · empty / blocked
After · counting again

What started working again

  • 30‑day baseline: 283,511 total server requests via sGTM.
  • Recovered from ad blockers: 5,174 requests (1.82%).
  • Recovered from tracking prevention: 38,985 requests (13.75%), driven primarily by Safari.
  • Ad‑block recovery by browser: Safari 0.91%, Chrome 1.86%, Other (Brave/Edge/Firefox) 2.83%.
  • GA4 event counts observed: PageView 46,409; ScriptLoad 42,194; Other 37,285; ViewItem 272; BeginCheckout 73; Purchase 12; Login 58; ViewCart 9; SignUp 6.
  • Event‑level impact: Purchase 25% TP; Login 41.38% ad‑block; ViewItem 30.88% ad‑block; ScriptLoad 13.71% TP and 4.09% ad‑block; SignUp 50% TP (n=6).
  • Server‑side captured +3 additional Purchase events vs client‑only (23.08% lift).
  • Consent integrity: 100% of GA4 requests marked opt‑in.
  • Low bot rates: GA 0.06% and Other 0.12%.
“Pending client testimonial”
Jason LeeJ

Jason Lee

Business Owner, MyPati.my

Delivery path

  1. 01

    Audit & Triage

    Review current sGTM server, clients, routes, consent, and Meta CAPI mappings. Identify event gaps and ad-block/ITP exposures.

  2. 02

    Server Container Hardening

    Validate Stape hosting, implement/confirm first-party subdomain routing, and optimize caching and header policies.

  3. 03

    Meta CAPI Enrichment & Deduplication

    Map web and server events with robust event_id strategy, add fbp/fbc and enhanced matching where consented.

  4. 04

    Consent & Identity Signals

    Ensure Consent Mode v2 signals are passed server-side, configure Cookie Keeper where applicable, and maintain 100% opt-in integrity.

  5. 05

    QA, Monitoring & Reporting

    Validate events in Meta Events Manager and GA4 DebugView, set up Looker Studio dashboards and anomaly alerts.

Stop another blind week

Phone ringing. Meta empty. Path clear after we name the restriction.

Start 7-day trial