Northridge Addiction Meta Pixel Tracking Recovery: conversions started counting again

What was broken

• Restricted Meta Pixel due to health-related content despite compliance
• Inconsistent tracking on Webflow and Elementor platforms
• Blocked events from main domain despite subdomain approval
• Need for precise SubmitApplication event tracking without over-firing

What we rebuilt

1. 01Implemented server-side tracking with Custom Server and Meta Conversion API
2. 02Captured user data on thank-you page post-Typeform submission for enhanced matching
3. 03Updated ad sets to use unrestricted pixel 1405345420657676
4. 04Optimized GTM to fire SubmitApplication only for qualified users

What started working again

• Achieved 95% tracking accuracy for SubmitApplication events
• Recovered 10.4% of events from ad blockers and 21.72% from tracking prevention
• Enabled accurate ad attribution for Florida, New Jersey, and California ad sets
• Setup compatible with new funnel using Typeform and thank-you page

“This setup is cooking! Great job, very excited with the results.”

K

Kelly Joseph

Marketing Manager

Delivery path

1. 01

   Onboarding & Audit

   Conducted onboarding with Kelly to understand tracking issues, audited existing Meta Pixel setup, and identified restrictions due to health-related content.

2. 02

   Access & Pixel Configuration

   Secured access to Meta Events Manager and Conversion API token for pixel 1385524702668280, updated Florida ad set to pixel 1405345420657676, and configured GTM for server-side tracking.

3. 03

   Server-Side Implementation

   Set up Custom Server server container, implemented Meta Conversion API, and captured user data (email, name) on thank-you page for enhanced event matching.

4. 04

   Testing & Optimization

   Tested SubmitApplication event to ensure no over-firing, removed unnecessary triggers for /sorry page, and verified setup for new funnel compatibility.