Skip to main content
Safari 26.2’s stricter tracking protections can hide attribution data and break tag-firing logic that depends on URL parameters. This article explains the impact and how to mitigate it.
With the release of iOS 26.2, Apple introduced stricter privacy protections for both regular and private browsing in Safari. These changes affect how marketing and analytics tools, including Invoca, capture attribution data from URL query strings.

​
What changed

Safari 26.2 enables advanced tracking protection by default for both regular and private browsing, affecting your data in three ways: Attribution loss, or the “Direct” spike. Safari now prevents the Invoca tag from reading URL query strings such as UTM parameters or click IDs. Calls will still route, transcribe, and signal normally, but the source may appear as “Direct” rather than “Google Ads” or “Social.” Safari may also hide user IP addresses, affecting some programmatic and CTV integrations. Reduced visibility in Private Browsing. Safari’s Intelligent Tracking Prevention (ITP) blocks tags originating from third-party domains in Private Browsing mode. The dynamic Invoca number may not load, showing your website’s fallback number instead — if that fallback isn’t an Invoca number, the call won’t appear in your reports. Functional impacts on routing and tag firing. If your account uses Intelligent Routing based on UTM parameters, that routing may fail or revert to a default. If your website only fires the Invoca tag when it detects a parameter like gclid, the tag may not fire at all, since Safari hides those parameter names.

​
Auditing your traffic

Before making changes, it helps to quantify how much of your traffic comes from Safari 26.2. If 30–40% of your traffic is Safari-based, that’s a strong case for implementing durable attribution solutions. Using Invoca reports:
NoteYour account must be configured to capture the “User Agent” field to generate this report.
  1. Go to Reports, then select Interactions.
  2. Set the Date Range filter to Last 30 days, then click Update.
  3. Select the app launcher (waffle icon) to access the detailed Call Reports view.
  4. Confirm “User Agent” is exposed in the report. If you don’t see it, click Edit Columns to enable it.
  5. Click Export to download the report.
  6. Open the file and filter the User Agent column for Safari and 26.2.
Using Google Analytics 4: Go to Reports > Tech > Tech Details, and set the dimension to Browser. Use Explore to filter further by device category if needed. Using Adobe Analytics: Go to Reports > Technology > Browser, and break down by operating system to identify iOS 26.2 users.
NoteThese privacy changes also apply to all subsequent versions, such as 26.3 and 26.3.1, and affect iOS, macOS, and iPadOS. Include all versions 26.2 and higher across these devices in your report filters.

​
Best practices to preserve attribution integrity

​
Summary checklist

  • Audit your traffic to quantify Safari 26.2 traffic and any “Direct” attribution spikes. Confirm “User Agent” tracking is enabled in the Invoca tag.
  • Secure your call volume by making sure your website’s fallback number is Invoca-controlled, so Private Browsing calls are still captured.
  • Update your data dictionary to capture newer ad-level identifiers like wbraid, gad_source, and gad_campaignid.
  • Review routing logic — if you use UTMs for Intelligent Routing, verify your catch-all routes are active for visitors with hidden parameters.
  • Deploy technical mitigations — consult your web developers about a Pass URL to Object script or a reverse proxy for long-term tracking stability.
  • Enable resiliency layers by activating Google Ads Enhanced Conversions for Phone Leads to recover missing attribution data.

​
Where to go next

Last modified on September 21, 2026