How it works: pixel, cookies and customer lists
Remarketing needs to know who visited what, and it relies on three technical mechanisms that are usually combined.
The most common is the remarketing pixel, a snippet of code from Google Ads, Meta Ads or another platform, usually installed on the site through a tag manager. When someone visits a page, the pixel logs that visit and, if the user already has a cookie from that platform, links it to their identifier. From then on, the platform can show them ads while they browse other sites in its advertising network.
The second mechanism is cookies, either first-party (set by the site itself) or third-party. They store which pages a user visited, which products they viewed, or whether they added something to the cart without completing the purchase. As third-party cookies are gradually phased out in Chrome, the first scenario carries more weight: data a brand collects directly on its own site.
The third mechanism is uploading customer lists, also called customer match or personalised audiences: a file of email addresses or phone numbers, usually hashed, uploaded to the ad platform. This route doesn't depend on cookies and is mainly used to reach existing customers, for example past buyers who should be offered a complementary product.
All three methods feed the same thing: an audience, meaning a group of identified users the platform can serve ads to. The more specific that audience, the better the campaign tends to perform.
A special case is dynamic remarketing: instead of always showing the same ad, the platform combines the pixel with a product feed, the same catalogue that powers Google Shopping or Meta's catalogue, to automatically generate an ad featuring the exact product each user looked at. That's the mechanism behind ads that seem to "remember" the item someone was browsing in an online store. It takes more setup work upfront, but it usually performs noticeably better than one generic ad shown to everyone.
An additional technical detail is cross-device matching: if a user logs into their Google, Meta or store account, the platform can link the same browsing history across their phone, laptop and tablet instead of treating them as separate visitors. Without that login, each device generates its own cookie, and remarketing loses continuity if the user switches screens midway through the buying decision.
