Google Ads Remarketing · Standard, Dynamic & RLSA

Remarketing audiences are built from three primary sources:

Website tag (Google tag / gtag.js)

The Google Ads tag (or Google tag) placed on your website fires on every page visit, adding the visitor to a "All Website Visitors" audience automatically. Custom audiences can be created for specific URL patterns: product page visitors, checkout page visitors, thank you page (converters), specific category visitors.

<!-- Google tag fires on every page visit -->
<!-- Creates audiences based on URL rules in Google Ads interface -->
<!-- Example: visitors to /product/ URLs = "Product viewers" audience -->

Google Analytics 4 audiences

If Google Ads is linked to GA4, any GA4 audience can be imported into Google Ads as a remarketing list. GA4's audience builder supports complex conditions (event sequences, parameter values, user properties) that the Google Ads tag alone cannot replicate — for example: "Users who viewed a product, added to cart, but did not purchase within 7 days."

App users

Firebase SDK integration enables remarketing to mobile app users: app installers, users who completed specific in-app events, users who have not opened the app in 30 days.

Standard remarketing shows static or responsive display ads to users who have previously visited your website as they browse the GDN. Campaign structure for standard remarketing:

• Segment by page type. All visitors, product viewers, cart abandoners, and past purchasers should be separate audiences — they are at different funnel stages and require different messages and bids.
• Segment by recency. A user who visited 1 day ago is more valuable than one who visited 30 days ago. Create audience membership windows (1 day, 7 days, 30 days) and apply higher bids to more recent visitors.
• Exclude converters from acquisition campaigns. Add your "Converters" audience as an exclusion from prospecting campaigns — you typically do not want to show acquisition messaging to users who have already purchased.

Dynamic remarketing shows ads featuring the specific products or services a user viewed on your website — automatically pulling product information (image, name, price) from your Google Merchant Center feed. A user who viewed a specific pair of running shoes sees an ad featuring exactly those shoes (or similar products) as they browse the web.

Dynamic remarketing requires: (1) a Google Merchant Center product feed with accurate product data, (2) the Google Ads tag with custom parameters passing the product ID of viewed items to Google, (3) a Dynamic display campaign linked to the Merchant Center account.

Dynamic remarketing for e-commerce consistently outperforms standard remarketing for conversion campaigns because the ads are personalised to each user's expressed product interest — reducing the gap between the ad and the user's last known intent.

RLSA allows you to use remarketing audiences to modify your Search campaign bids or targeting. Unlike Display remarketing where you show ads across the GDN, RLSA modifies your Search ads — changing bids or enabling specific ads when a prior site visitor performs a relevant search.

Two RLSA modes

• Bid adjustment (Targeting and bid). Your ads still show to all searchers for your keywords, but you apply a bid modifier (e.g. +50%) for searches from your remarketing list. Prior visitors trigger a higher bid, competing more aggressively for their clicks.
• Targeting only. Your ads only show when a prior site visitor searches for your keyword. Effective for keywords too broad to target with open auction — "running" alone is too broad, but prior site visitors searching "running" are much more qualified than cold searchers.

Customer Match allows you to upload your own CRM data — email addresses, phone numbers, or physical addresses — and Google matches this data to Google accounts. Matched users can be targeted across Google Search, Display, YouTube, Shopping, and Gmail campaigns.

Use cases: target existing customers with upsell/cross-sell campaigns; exclude existing customers from acquisition campaigns; create Similar Segments based on your highest-value customers; target lapsed customers with re-engagement campaigns.

Customer Match requires compliance with Google's privacy policies — users must have consented to receive marketing communications and to their data being used for ad targeting. Enhanced Conversions (passing hashed email at conversion time) integrates with Customer Match to improve match rates and conversion measurement.

Frequency capping limits how many times a single user sees your ad within a given time period. Without frequency capping, remarketing campaigns can show the same ad to the same user dozens of times per day — producing ad fatigue, negative brand perception, and wasted spend on users who have already decided not to convert.

Recommended frequency caps for remarketing: 3–5 impressions per user per day for standard remarketing; 2–3 per day for cart abandonment campaigns; 1–2 per day for recent converters shown cross-sell messages. Set frequency caps at the campaign level (Campaign Settings > Frequency Management).

Smart campaigns with Target CPA or Target ROAS bidding manage frequency automatically — the algorithm reduces bids for users who have been shown the ad many times without converting, effectively self-regulating frequency based on performance data.

Authentic Sources