How It WorksPricingIntegrationsAffiliatesDocsBlog
Log inGet Started
Back to Docstroubleshooting

iOS 14 & Ad Blockers

Why conversions from iPhones and blocked browsers go missing, what DealOracle still captures for them, and how to confirm the server path is carrying the load.

Table of contents

Symptoms

  • Meta or TikTok report far fewer conversions than the CRM shows, and the gap is worst on mobile.
  • Leads from Instagram or TikTok in-app browsers arrive with a click ID but no browser ID.
  • Events Manager shows most events arriving from the server and few from the browser.
  • A share of visitors never produce a page view at all, but their form still lands in the CRM.

None of these are DealOracle errors. They are what the modern browser landscape looks like, and the reason the server path exists.

What is happening

  • iOS App Tracking Transparency: the Facebook, Instagram and TikTok apps must ask permission to track; most people decline, so their in-app browsers pass less identity to pixels.
  • Safari Intelligent Tracking Prevention: cookies set by scripts last seven days, or 24 hours when the visitor arrived through a decorated link. Return visits look like new people.
  • Ad blockers and private browsers: third-party tracking scripts and known tracking domains are blocked outright. The platform pixel never loads.
  • DNS-level filtering: some networks block tracking hosts for every device on them.

Each of these removes browser events. None of them can remove a CRM stage change, and none of them can strip a click ID from a URL.

What DealOracle still captures

  1. The click ID. It arrives in the landing page URL regardless of the browser's tracking settings, and DealOracle stores it first-party.
  2. First-party pixel events. The pixel is served from and reports to a path on your own domain, which blockers do not classify as a tracking host. Most blocked-browser visitors still produce page views and form events this way.
  3. The CRM outcome. Qualified, booked and won events are sent from the server with the click ID and hashed contact details. Nothing on the visitor's device is involved.

The result is that a blocked browser loses the platform's own pixel, while DealOracle's server events still reach the platform with a click ID attached.

How to confirm the server path is working

  1. Meta Events Manager: open the pixel or dataset, choose the event, and look at the browser versus server split. Server events should be present for every stage you mapped, and deduplicated events should show for actions that fire on both paths.
  2. Google Ads: Conversions, the imported action, diagnostics. Recent uploads should list without errors.
  3. TikTok Events Manager: Events API tab; received and matched counts per event.
  4. DealOracle: the Tracking Pixel page shows pixel health per domain; the Lead Manager shows which leads carry a click ID; the Journey tab shows the touches DealOracle recorded.

If server events are missing entirely, check the ad platform connection under Integrations and the stage mapping in Event Streams. If they arrive but match poorly, see Match rates.