Do Ad Blockers Break Influencer and Affiliate Tracking Links? What Actually Gets Blocked

What an ad blocker actually blocks

"Ad blocker" isn't one thing — it covers browser extensions (Adblock Plus, uBlock Origin, AdGuard), built-in browser features (Brave, parts of Safari), and network- or DNS-level tools (Pi-hole, NextDNS, AdGuard Home), all of which lean on the same underlying filter lists. The most widely used is EasyList, supplemented by EasyPrivacy, which specifically strips out tracking scripts, web bugs and other data collectors. Per EasyList's own description of itself, its purpose is to remove adverts and tracking from international web pages — the list doesn't distinguish "good" tracking from "bad": if the domain, script or redirect call is on the list, it gets blocked, whether it belongs to an ad network or an affiliate network. According to a review of EasyList's coverage of affiliate marketing, most major affiliate networks appear on the list in some form, with Amazon Associates, ShareASale and Rakuten named specifically, and Awin, CJ, Impact, Partnerize and Tradedoubler described as similarly covered.

What actually happens technically is that the browser (or the DNS resolution) refuses to send a network request to a domain on the block list. If that's the domain a tracking link redirects through, the redirect itself never completes — the exact same symptom as when a cookie never gets set: the sale still happens in the store's own system, just with no creator attached to it. See how influencer tracking actually works for the rest of the same chain.

Which part of the tracking link is actually at risk

As covered in the article above, a tracking link has three layers: the destination address, a click ID or referral parameter, and usually a set of UTM parameters. It's the middle step — the redirect through the tracking system's own domain, where the cookie or click ID actually gets set — that's exposed to an ad blocker. The destination itself (the store's own domain) is rarely on any block list and loads normally. In most cases the customer notices nothing unusual at all: the page loads, and the purchase completes exactly as normal — it's only the tracking layer underneath that silently disappears, with no error shown to anyone.

Ad blocker, declined consent, ITP or in-app browser — four different causes of the same symptom

The Academy already covers three other mechanisms that stop a tracking cookie from ever being set. An ad blocker is a fourth, technically distinct cause of exactly the same symptom: a purchase that exists in the store's own system with no creator attached to it.

The practical, often-missed point: classic browser extensions like uBlock Origin or Adblock Plus don't run inside Instagram's or TikTok's own embedded browser at all — extensions require a full browser installation, which an app's WebView doesn't support. That means the ad-blocker mechanism this article describes mainly hits clicks that happen in a real browser — a link in a blog post, a YouTube description, or when a customer opens the link in Safari or Chrome themselves — and far less often the typical Instagram Story or TikTok bio click, which is already exposed to the separate in-app-browser mechanism instead. A DNS- or network-level tool like Pi-hole or NextDNS is the exception: because it blocks at the network connection itself, independent of which app made the call, it also catches traffic from an in-app browser or a mobile app — but that requires the customer (or the customer's network) to have actively set it up, which is far rarer than a plain browser extension.

What affiliate networks and advertisers actually do about it

Rakuten Advertising's own Publisher Help Center article on ad blockers and affiliate links describes two concrete countermeasures the network itself recommends to its advertisers: first, building an internal redirect — a link on your own site (e.g. yoursite.com/go/product) that forwards on to the actual tracking link, so the ad blocker sees your own domain instead of the tracking system's; and second, turning on ad-blocker detection, so a visitor with an active ad blocker is asked to disable it for the best experience. An independent review of EasyList and affiliate marketing describes the exact same first technique — but qualifies it immediately: if the ad blocker simply blocks the entire domain, an internal redirect still won't work, because the block happens at the network request itself rather than only on the visible element.

Beyond those two techniques, two structurally different countermeasures already covered elsewhere in the Academy exist: server-side tracking, where the confirmation is sent directly from your own server, bypassing the customer's browser and the ad blocker entirely, see server-side and cookieless tracking in influencer marketing; and a discount code, which isn't a technical tracking mechanism at all and so can't be blocked by any ad blocker whatsoever, see discount codes vs tracking links.

Why "cloaking" the link isn't a reliable fix

The internal redirect above is, in practice, a mild version of what's technically called domain cloaking, or "CNAME cloaking" — making a third-party domain present itself as your own. According to security researchers at Palo Alto Networks' Unit 42 group, the technique itself is widespread precisely because it currently evades most blocking mechanisms effectively — their own measurements found that DNS-based countermeasures from AdGuard and NextDNS combined covered less than 10% of the cloaked subdomains they were able to identify themselves. But "evades most blocking" isn't the same as "a guaranteed fix", and two things specifically work against relying on it: first, an ad blocker that matches on the URL pattern itself or on the content of the script being fetched — not only on the domain name — still catches the call regardless of which domain it's cloaked behind, exactly as the independent review above points out itself. Second, Safari's Intelligent Tracking Prevention already has its own, specific countermeasure: per WebKit's own documentation, already covered in server-side and cookieless tracking in influencer marketing, ITP specifically detects a domain set up as a CNAME-cloaked third party and caps the cookie it sets to 7 days — regardless of whether any ad blocker is even installed. The conclusion isn't that an internal redirect is worthless — it does catch some plain domain-based blocking — but it isn't, and won't become, a complete fix for any of the four mechanisms in the table above.

Worked example: what it actually costs (hypothetical)

The numbers below are illustrative only, built to demonstrate the mechanism — not a real Make Influence customer case, and not an actual measurement of how much traffic this affects.

Assume a campaign generates 1,000 tracking-link clicks in a month, converting at an average rate of 8% — that is, 80 purchased orders in total. Assume further — purely for illustration — that 10% of the 1,000 clicks (100 clicks) come from a browser or network where an active ad blocker blocks the tracking domain in the link outright. Applying the same 8% conversion rate to that subset, 8 of those 100 clicks (100 × 8% = 8) would still have resulted in a purchase. Those 8 orders exist in the store's own system as entirely normal orders — just with no creator attached, because the network request that would have set the cookie never completed. That's 8 of the 80 total purchases (10%) lost to this one mechanism alone — a loss that stacks on top of, not instead of, the loss from ITP, declined consent and in-app browsers described elsewhere.

Decision framework

• IF your campaign is mainly linked from blog posts, YouTube descriptions, or other places where the customer clicks in a real browser → expect a genuine, if hard-to-measure, loss from ad blockers, and consider an internal redirect combined with a discount code as a backstop.
• IF your campaign is mainly linked from Instagram Stories or TikTok bios → the ad-blocker mechanism in this article plays a smaller role than the separate in-app-browser mechanic; see how influencer tracking actually works.
• IF you're considering "cloaking" the tracking link behind your own domain → go ahead, but don't promise yourself full coverage; pair it with a discount code wherever possible.
• IF you want the most robust coverage across ad blockers, consent, ITP and in-app browsers all at once → a discount code is the one mechanism in this article that can't be technically blocked at all, because it isn't a browser-based tracking technology.

Common mistakes

• Assuming an ad blocker also blocks the destination page itself. It usually doesn't — the store's own domain is rarely on any block list. The customer typically notices nothing.
• Assuming an internal redirect is a complete fix. It's a partial countermeasure against plain domain-based blocking — not against URL-pattern matching or Safari's ITP.
• Confusing this mechanism with declined cookie consent. The two look similar in symptom (the cookie never gets set), but an ad blocker is an installed third-party extension, not a deliberate "no" from the customer in your own banner.
• Assuming ad blockers affect all influencer traffic equally. The mechanism is far more relevant to browser-based clicks than to the typical Instagram or TikTok bio click, which opens in the app's own embedded browser instead.

Make Influence's operational perspective

Make Influence doesn't currently implement domain cloaking as a built-in part of its own tracking model — our tracking link runs through our own tracking domain, the same way most affiliate and influencer tracking systems described in this article do. That means our tracking link carries, in practice, the same ad-blocker exposure as the rest of the industry, if a customer clicks from a browser with an active extension or a DNS-level tool installed. In our experience, the biggest practical countermeasure isn't a technical cloaking fix, but pairing the tracking link with a discount code — exactly as recommended for the other three mechanisms in the table above. It's the only one of the four mechanisms that no ad blocker, no declined consent and no browser policy can break through.

FAQ

Does an ad blocker always break an influencer tracking link?

No. It depends on whether the specific tracking domain the link redirects through is on the filter list the ad blocker uses (typically a variant of EasyList or EasyPrivacy), and on whether the ad blocker is even running in the browser or app the customer uses to click.

Is this the same thing as Safari's Intelligent Tracking Prevention (ITP)?

No. ITP is a built-in policy inside the Safari browser itself that limits third-party cookie lifetimes regardless of whether any ad blocker is installed. An ad blocker is a separate, installed extension or service that actively blocks network requests to domains on a filter list. Both mechanisms can hit the same customer at the same time.

Can an internal redirect ("cloaking") fix the problem completely?

No. It catches the simple form of plain domain-based blocking, but doesn't work if the ad blocker matches on the URL pattern or the script content instead of just the domain name — and it doesn't change the fact that Safari's ITP already has its own, separate countermeasure against exactly this technique.

Do ad blockers hit Instagram and TikTok bio links the same way as blog or YouTube links?

Typically not to the same extent. Classic browser extensions require a full browser installation, which Instagram's and TikTok's own embedded in-app browser doesn't support. A DNS-level tool like Pi-hole or NextDNS is the exception, because it blocks at the network level independent of the app.

Is a discount code immune to ad blockers?

Yes. A discount code isn't a technical tracking mechanism — it's something the customer types in at checkout themselves — so it can't be matched or blocked by any filter list.

Should I ask customers to disable their ad blocker?

That's one of the two techniques Rakuten Advertising's own documentation itself recommends, via a visible ad-blocker-detection message. Be aware it can feel intrusive to the customer, and it's no guarantee the customer will actually disable it.

Can Make Influence guarantee a tracking link won't be hit by an ad blocker?

No. Like the rest of the industry, Make Influence's tracking link carries the same basic exposure as any other tracking domain, if the customer is using a browser or network with an active ad blocker.

Is a link-in-bio tool like Linktree the same risk as an ad blocker?

No. A link-in-bio tool forwards to the tracking link unchanged — the risk there is a UTM reporting collision, not a blocked network request. See do link-in-bio tools like Linktree break influencer tracking links for that separate mechanism.

Is a VPN the same risk as an ad blocker or a DNS-level tool like Pi-hole?

No. A DNS-level tool like Pi-hole or NextDNS in its standard mode blocks known tracking domains but doesn't change the IP address a destination sees. A VPN doesn't block anything on a filter list at all — it routes traffic through a remote server, which specifically breaks a different mechanism, IP-based fallback tracking, not the cookie-setting redirect this article covers. See do VPNs and private DNS tools break influencer tracking's IP fallback for that separate mechanism.

Is SponsorBlock the same risk as an ad blocker?

No. SponsorBlock doesn't block a network request at all — it's a crowdsourced tool that automatically skips a segment a creator has placed inside the video file itself, like a sponsored mention in a YouTube video, not YouTube's own ads or this article's tracking-link mechanism. See SponsorBlock and sponsor-skip extensions: do they undercut a paid YouTube placement for that separate mechanism.