Skip to content

How iOS 17 Link Tracking Protection affects ad reporting

Apple's iOS 17 feature strips some ad click identifiers in Safari Private Browsing. This guide explains which parameters matter, when reporting breaks, and how UTM parameters preserve attribution.

What was tested

Apple introduced Link Tracking Protection with iOS 17. Early announcements did not specify exactly which URL parameters would be removed, making the reporting impact hard to judge. Beta testing was used to check which parameters survive and which disappear.

Which parameters are affected

UTM parameters such as utm_source and utm_medium were not stripped. In contrast, Safari removes network click IDs including GCLID for Google Ads and FBCLID for Facebook Ads when Private Browsing is enabled. Without those IDs, the ad network cannot tie a visit or conversion back to the specific campaign, ad group or keyword that generated the click.

Impact depends on your measurement setup

If your ads already carry UTM parameters and you measure visitors in a website analytics tool or leads and customers in a CRM, your reporting should continue. Safari leaves those UTM values in place, so your tools can still capture and report them. If you rely only on each ad network's built-in click and conversion reporting, those reports become less accurate for affected Safari private sessions.

Scope and timing

The effect is narrow: it requires Safari and Private Browsing mode, similar to Incognito in other browsers. Captured estimates suggested roughly 20% of browsing sessions in Safari and about 20% using private browsing, so the share of affected sessions is likely relatively small. iOS 17 was announced June 5, 2023, with developer beta in early July and a public launch expected around mid-September 2023.

How to protect reporting

Add UTM parameters behind your ads so analytics tools can always see where visitors, leads and customers originate. In Google Analytics, UTM values appear in acquisition reporting; in a CRM, they can be stored on the contact record so each lead shows its originating campaign. This also protects reporting as more browsers block network tracking parameters and third-party cookies. Checklist: 1) Add consistent UTMs to every paid URL. 2) Confirm analytics captures them on landing. 3) Store them on leads/customers in CRM. 4) Report by UTM rather than relying only on network click IDs.

Parameter impact summary
ParameterEffect in Safari Private BrowsingReporting consequence
UTM parameters (utm_source, utm_medium, etc.)Left intactAnalytics/CRM can still attribute visitors, leads and customers
GCLID (Google Ads)RemovedGoogle Ads cannot attribute that session/conversion to campaign/keyword
FBCLID (Facebook Ads)RemovedFacebook Ads cannot attribute that session/conversion to campaign/keyword

Based on beta testing described in captured evidence; MCCLKID/TWCLKD table values were not legible in capture and are omitted.

Frequently asked questions

Does iOS 17 remove UTM parameters?

Testing described here found UTM parameters were left intact, while ad-network click identifiers such as GCLID and FBCLID were removed in Safari Private Browsing. That distinction is why UTM-based analytics and CRM reporting can continue even when network-native attribution loses the click ID.

When does Link Tracking Protection affect reporting?

The change applies in Safari when Private Browsing is on. It does not affect every visit, so the overall reporting impact is likely limited, but affected sessions can lose campaign-level attribution in the ad network.

How can I keep accurate reporting?

Add UTM parameters to ad URLs and capture them in your analytics or CRM. Then you can report visitors, leads and customers by campaign without depending solely on GCLID, FBCLID or other network click IDs.