Dynamic Remarketing

Dynamic remarketing shows people who visited your site or app ads featuring the specific products or services they viewed. Google describes it as a way to bring previous visitors back to finish what they started. The ad is not designed by hand for each person. A feed holds your catalog, a tag on your site records which items each visitor looked at, and the platform assembles an ad from the matching feed rows: image, name, price, and a link to that product. Event parameters, such as product viewed, added to cart, and purchased, tell the platform where a person stopped, so you can create different lists for different stages.

Three parts must line up. First, a feed. Retailers use their Google Merchant Center feed, while other businesses upload a feed to the Business data section of the Shared library, in a supported file format such as .csv, .tsv, .xls, or .xlsx, with a unique ID, price, and image for each item. Second, a tag. Google's page says the dynamic remarketing tag adds visitors to remarketing lists and associates them with the unique IDs of the feed items they viewed, and it should sit on all pages of your site using custom parameters. Third, a campaign that uses those lists and the feed. For apps, Google says in-app conversion tracking must be enabled and the app must send event data through the SDK, and the tracking template is ignored in favor of parameters on the app URI.

The ID is the hinge. The value your site passes in the tag must match the ID in the feed exactly, character for character. When it does not, the platform cannot find the product and may fall back to a generic ad or show nothing. Dynamic remarketing also interacts with audience lists, since you can create segments such as cart abandoners or product viewers and set their membership duration. Bid strategy and attribution decide how its results look: view-through conversions and last-click credit change the numbers a lot. It also works with app campaigns, where the feed and SDK events are needed. Creative is assembled from templates, so give the platform a clean logo, a consistent color, and a short headline. The product image does most of the work.

The mistakes are consistent. An ID mismatch between tag and feed is the most common and often silent, since the campaign keeps running. Feeds that are out of date show products that are sold out or priced differently, which wastes clicks and erodes trust. No limits on recency or frequency means a person who bought a sofa last month still sees sofas for weeks. Failing to exclude purchasers wastes budget. Last, some businesses use it where a broad tag is not appropriate: some categories are restricted from remarketing under Google's advertising policies, so check the policy before building lists. Also check that feed prices and availability update often. A visitor who sees a price in the ad that differs from the page will leave.

Review it by audience: cart abandoners should convert at a higher rate than casual viewers, and recent visitors higher than older ones. Check the diagnostics in the platform for tag and feed errors, and look at impressions per list. This week, test a product page and a cart page with your tag helper tools to see the IDs being sent, compare them with the feed, exclude buyers from the last 30 days, and set a frequency cap so the same person does not see the same item every hour. Review the product-level report for items that earn impressions but no clicks, which often have poor images.