How to use this page
Tracking rarely fails loudly. It fails as a slow leak: fewer matched events, a lower Event Match Quality, a campaign that looks worse than it is. Each mistake below comes with the symptom you would see in DealOracle or the platform, and the fix. Work through them in order the first time you set up an account; afterwards, use the symptom column as a checklist.
1. The pixel is not on the page the ad lands on
Symptom: leads arrive with no click ID and no journey. Fix: install the pixel on every landing page and the thank-you page, not only the home page. Check the Tracking Pixel page's health view, which shows which domains and pages have fired recently.
2. The form is in an iframe that cannot see the URL
Symptom: leads from LeadConnector-hosted forms, some Typeform, Calendly and Jotform embeds carry no click ID even though the pixel fired. Fix: pass the identifiers into the frame. The GoHighLevel guide shows the hidden-field pattern; for other builders, append the click ID parameters to the iframe URL from the host page.
3. A redirect drops the query string
Symptom: click IDs present on the ad's URL, absent on the page where the pixel runs.
Fix: check every hop between the ad and the landing page (link shorteners, www redirects, HTTP to HTTPS, trailing-slash redirects). Each must preserve the query string.
4. Allowed domains not set
Symptom: the pixel loads but events are rejected. Fix: add every domain and subdomain you track to the pixel's allowed domains, using a wildcard for subdomains where the site uses them.
5. No event ID, so browser and server events double count
Symptom: the platform reports twice the conversions you have leads.
Fix: send the same event_id from the pixel and the server for the same action. DealOracle does this automatically for events it sends on both paths; if you also fire the platform's own pixel from a tag manager, either remove that event or share the ID.
6. Hashing done wrong, or not done
Symptom: Event Match Quality below 5 despite email and phone being present. Fix: normalize before hashing (lowercase, trimmed email; E.164 phone) and hash once with SHA-256. Never hash a hash. DealOracle does this for every event it sends.
7. Stage events mapped to the wrong platform event
Symptom: Meta shows hundreds of Purchases for an account that closed ten deals. Fix: map only the outcome stage to Purchase, and give it the deal value. Review the mapping in Event Streams against Lead to close.
8. Testing from your own team
Symptom: a cluster of leads from one IP, fake emails, and a low match quality average. Fix: use the platform's test-event tool with the test code, or mark internal leads as test in the CRM so they are excluded. Delete test leads before judging the numbers.
A weekly check
- Leads without a click ID, by landing page (Lead Manager filter). A page above 20 percent is leaking.
- Event Match Quality on the optimization event (Meta Events Manager). Below 7 means missing identifiers.
- Conversions in the platform versus outcomes in DealOracle for the same week. A gap of more than 15 percent points to windows or duplicates.
- Pixel health on the Tracking Pixel page. A domain that stopped firing usually means a site change.
The Troubleshooting section covers each platform's error messages.