What Is Retargeting?

Retargeting shows ads to someone who already visited a site, opened a product page, or left a cart without paying, instead of chasing an entirely new audience. The logic is straightforward: that person already showed interest, so winning them back usually costs less than reaching someone who has never heard of the brand.

Technically, the campaign relies on an identifier logged when the user visits the page. That logging usually depends on a cookie or a tracking pixel placed on the site, which tell the ad network who was there and what they did. With that list, the platform decides who sees the ad again the next time they browse another site in the same network.

The term is often used as a synonym for remarketing, though not everyone agrees they're the same thing. Google Ads itself now prefers talking about "your data" or remarketing lists inside its own platform, while much of the industry still says retargeting for display ads aimed at past visitors.

In practice the two terms get used almost interchangeably, and even Google Ads folds them together under remarketing lists inside its own display advertising platform. The distinction carries more weight in marketing theory than in how the industry actually talks day to day.

The underlying mechanism isn't unique to retargeting: it relies on the same tracking pixel or the same cookie that measures any other campaign. When someone loads a page, that code drops an identifier the ad network ties to the visit, the product page viewed, or the abandoned cart. From there, the platform builds a list and decides which other sites within its network will show that same person the ad again. If that space on other sites is bought through automated auctions, the campaign is part of programmatic advertising. With dynamic retargeting, the identifier goes a step further and remembers exactly which product someone looked at, so the later ad shows that specific product instead of a generic banner.

This is where Chrome's back-and-forth on third-party cookies matters. Google confirmed in April 2025 that Chrome would keep them, and in October 2025 it retired most of the Privacy Sandbox APIs it had built as a replacement, after the industry barely adopted them. That means classic cookie-based retargeting keeps working in Chrome, without the block that had been announced for years.

That continuity doesn't carry over to every browser. Safari has blocked third-party cookies by default since 2020 through Intelligent Tracking Prevention, and Firefox has done the same since 2019 through Enhanced Tracking Protection. For a retargeting campaign, that means traffic browsing with Safari or Firefox stays out of reach from day one, regardless of whatever Chrome decides.

In the EU, a retargeting cookie needs the user's explicit consent, because it isn't strictly necessary for the site to work. That approval gets collected through the same banner that covers every other non-essential cookie, and without it the campaign can't set or read the identifier.

That's why interest has grown in alternatives that don't depend on a third-party cookie. First-party-data retargeting uploads a customer or subscriber list, already collected with consent, straight into the ad platform. Contextual targeting, which picks where an ad runs based on the page's content instead of who's visiting it, works as an option that doesn't depend on the browser at all.

One practical limit worth setting from the start is frequency capping: how many times, at most, the same person sees the same ad within a given period. Without that cap, the campaign tips into ad fatigue, the user starts ignoring the ad or gets annoyed with the brand, and the campaign's actual CTR drops instead of climbing.

• Set an explicit frequency cap in the ad platform; without one, the same person can see the ad dozens of times within a few days.
• Segment retargeting lists by the actual action taken, someone who only viewed a product page isn't the same as someone who abandoned a cart.
• Exclude anyone who already converted, instead of spending budget showing an ad to a customer you've already won.
• Combine cookie-based retargeting with your own contact list uploaded to the platform, so part of the campaign doesn't depend on which browser each visitor uses.
• Wire the identifier's loading to the consent banner technically, so no visit gets logged before the user has actually agreed.
• Test contextual targeting in parallel, especially for Safari and Firefox traffic, where classic retargeting starts out with limited reach anyway.

• Running the same ad with no frequency limit, until the user associates it with harassment rather than the brand.
• Assuming retargeting reaches the whole audience equally, when Safari and Firefox have blocked third-party cookies by default since 2020 and 2019.
• Loading the retargeting cookie or tracking pixel before the user has given consent.
• Still showing the ad to converted customers because the exclusion list wasn't updated in time.
• Treating retargeting and remarketing as identical in every context, when some platforms and sources distinguish them by channel and audience.