To transfer Facebook audiences into Google Ads RLSAs, tag every Facebook ad set with unique UTM parameters, route that traffic through Google Analytics audience builder, and apply the resulting list as a targeted audience in your Google Ads campaigns. The list requires a minimum of 1,000 users before it activates on the search network.

Combining Facebook’s demographic targeting depth with Google Ads’ intent-based search reach is one of the highest-leverage moves in paid digital strategy. Facebook tells you who your audience is. Google Ads captures them when they’re actively searching. Used together, these platforms let you layer identity-level precision onto purchase-intent moments.

This guide covers the foundational step: building a UTM-based audience transfer pipeline so your Facebook data informs your Google Ads RLSAs (Remarketing Lists for Search Ads). For teams already building operational workflows around automation, the same logic applies — structured data routing beats manual workarounds every time. If you’re thinking about how systematic process design applies beyond advertising, the same principle shows up in OpsMap discovery work and in pre-automation checklists.

Before you build any audience segment, it’s worth asking whether your current workflow infrastructure can support the data handoffs involved. The principles in automation-first thinking apply here just as much as in HR or operations contexts.

What Are RLSAs and Why Do They Matter for Cross-Platform Targeting?

RLSAs — Remarketing Lists for Search Ads — let you adjust your Google Ads bids, ad copy, or targeting based on whether a searcher is already in an audience list you’ve defined. Instead of bidding the same amount for every search query, you bid more aggressively (or use different messaging) for people who have already interacted with your brand or match a specific profile.

Standard Google Ads targeting relies on keyword intent. RLSAs add an audience layer on top of that intent signal. When you populate those audience lists with data sourced from Facebook — where you’ve already filtered by job title, industry, or seniority — you get something most advertisers never achieve: demographic precision combined with search intent.

The minimum threshold to activate an RLSA on Google’s search network is 1,000 users. Plan your Facebook campaign traffic targets accordingly before building the audience list.

Step 1: Set Up Unique UTM Tags for Every Facebook Ad Set

UTM parameters are the bridge between Facebook and Google Analytics. Without them, Google Analytics cannot distinguish Facebook campaign traffic from organic or other paid sources — and your audience segmentation collapses into noise.

For each Facebook ad set, create a unique UTM string using all five standard parameters:

• utm_source — always set to facebook
• utm_medium — set to cpc or paid-social
• utm_campaign — name the parent campaign (e.g., b2b-awareness-q3)
• utm_content — differentiate individual ad creatives
• utm_term — encode the audience segment (e.g., vp-finance or hr-director)

The more granular your UTM structure, the more precise your audience segmentation becomes downstream. A single generic UTM tag across all ad sets produces one undifferentiated audience. Unique tags per ad set produce multiple audiences — each corresponding to a specific demographic or targeting group you defined on Facebook.

Apply these UTM-tagged URLs to every destination URL in your Facebook campaign before the campaign goes live. Retroactive tagging does not capture traffic already sent.

Step 2: Build Audience Segments in Google Analytics Using Campaign UTMs

Once your UTM-tagged Facebook traffic begins flowing, open Google Analytics and navigate to the Audience Builder. This tool lets you define audience segments based on traffic source, medium, campaign, or any other dimension — including the UTM parameters you just set.

To build a segment for a specific Facebook ad set:

1. Go to Admin → Audience Definitions → Audiences in Google Analytics
2. Click New Audience and select Create New
3. Under conditions, filter by Campaign exactly matching the UTM campaign value from your Facebook ad set
4. Add a secondary filter for Source containing facebook to isolate the traffic source
5. Name the audience to reflect the Facebook targeting it represents (e.g., “FB — VP Finance — Q3 Awareness”)
6. Set the membership duration based on your sales cycle length
7. Publish the audience to your linked Google Ads account

Repeat this process for each UTM-tagged ad set you want to convert into a separate RLSA. The audience list will begin populating immediately, but it must reach 1,000 users before Google activates it for search targeting.

Step 3: Apply the Audience List to Your Google Ads Campaigns

With your Google Analytics audiences now published to Google Ads, you can apply them directly to search campaigns or ad groups.

There are two application modes:

• Targeting mode — show ads only to users on the audience list. This restricts reach but maximizes precision. Use this when budget is limited and qualified leads are the priority.
• Observation mode — show ads to all searchers, but collect performance data segmented by audience membership. Use this to gather data before committing to full targeting restrictions.

For B2B campaigns targeting job-title-specific decision-makers, targeting mode is the right default. You’ve already paid for Facebook traffic to qualify these users demographically. Restricting Google Ads spend to that qualified pool prevents budget dilution on unqualified clicks.

Apply bid adjustments to boost visibility for high-value audience segments. A VP of Finance who visited your site after seeing a Facebook awareness ad and is now searching a relevant keyword warrants a significantly higher bid than an anonymous searcher with no prior engagement.

How to Use This to Reach B2B Decision-Makers via Search

The most direct application of this framework is targeting job-title-defined audiences from Facebook inside Google Ads search campaigns. Here’s the complete workflow:

1. Launch a Facebook awareness campaign targeting specific job titles — for example, HR Directors, CFOs, or Procurement Managers in your target industry
2. Tag every ad set with unique UTMs that encode the job title or audience segment (e.g., utm_term=hr-director)
3. Route all destination URLs through UTM-tagged links so Google Analytics captures demographic traffic from Facebook
4. Build Google Analytics audience segments filtered by each UTM campaign/ad set combination
5. Publish those audiences to Google Ads and wait for the 1,000-user threshold to activate
6. Apply the lists as RLSA targets in your Google search campaigns so only the job-title-qualified visitors see your search ads

The result: every dollar spent on Google Ads clicks goes toward people who are both actively searching a relevant query and match the demographic profile you defined on Facebook. This is a materially different outcome than keyword targeting alone.

How to Know It Worked

The audience transfer is working when you see these signals:

• RLSA list populates above 1,000 users within the expected timeframe based on your Facebook traffic volume
• Google Ads campaign shows audience segment data — you can see impressions, clicks, and conversions segmented by audience list membership
• Click-through rates increase for RLSA-targeted search campaigns compared to non-RLSA baselines — the audience has prior brand exposure
• Cost-per-conversion decreases because spend is concentrated on pre-qualified users rather than distributed across anonymous searchers
• UTM-sourced traffic in Google Analytics maps cleanly to the campaign names and ad sets you defined on Facebook

If your audience list stalls below 1,000 users, increase Facebook campaign reach or extend the membership window in Google Analytics. If click-through rates don’t improve over a non-RLSA baseline, audit whether your UTM tags are actually encoding meaningful demographic distinctions or whether all ad sets are landing in the same audience pool.

Common Mistakes to Avoid

Using the same UTM tag across multiple ad sets. This collapses demographically distinct audiences into a single undifferentiated list. Each ad set targeting a different job title or demographic must carry a unique UTM string.

Forgetting to link Google Analytics to Google Ads before publishing audiences. Audiences published to Google Ads from an unlinked Analytics property will not appear in your Ads account. Verify the property link before building any audiences.

Setting membership duration too short. If your Facebook awareness campaign runs for 30 days and your membership window is 14 days, users who visited early in the campaign may age out before the list reaches 1,000 users. Match membership duration to your campaign timeline.

Applying RLSAs to campaigns with mismatched keyword intent. A job-title-qualified audience from Facebook underperforms when paired with broad informational keywords. Use this audience layer with high-intent, bottom-of-funnel search terms to capture users at the decision stage.

Skipping observation mode entirely on new campaigns. Before fully restricting reach to the RLSA list, running a short observation period confirms the list is performing as expected before you cut off all non-list traffic.

Additional Reading

• Implement AI Workflow Automation: A Step-by-Step Business Guide
• 7 Questions to Ask Before You Automate Anything (The OpsMap Checklist)
• What Is OpsMap? The Discovery Step That Prevents Automation Mistakes
• What Is Automation-First? Why You Should Automate Before You Add AI
• Manual Data Entry: The Silent Killer of Business Productivity & Profit
• Data Synchronization: The Unseen Engine of B2B Growth and Profit
• Escape the Manual Workflow Trap: AI Automation for Unstoppable Growth
• Practical AI: Streamlining Operations for Tangible Business Growth
• Unifying Your Business Data: A Step-by-Step Guide to a Single Source of Truth