Link GA4 and DV360: Ad Ops Setup Guide
Linking Google Analytics 4 (GA4) and Display & Video 360 (DV360) lets you export complex web and app behavioral audiences directly into your demand-side platform (DSP) for immediate activation. This integration bypasses traditional data management platform (DMP) hop latencies, utilizing Google's native identity graph to match users across programmatic environments. By establishing this product link at the GA4 property level, programmatic traders can target high-intent custom segments, execute precise remarketing campaigns, and build cookieless lookalike models.
Key Takeaways
- Permission Match: You must hold Editor access in the GA4 property and Admin or Partner-level write access in DV360 to successfully link the accounts.
- Latency Reality: Expect a 24-to-48-hour delay for GA4 audiences to populate and scale in the DV360 targeting interface after initial creation.
- Consent is Hard: European Economic Area (EEA) targeting requires proper configuration of Consent Mode v2, specifically the
ad_personalizationparameter, to export audiences. - Zero Data Fees: Unlike third-party data onboarders, exporting first-party GA4 audiences to DV360 is entirely free and suffers zero data drop-off from third-party sync hops.
Technical Prerequisites and Access Matrices
Before initiating the linkage, you must align user permissions across both Google Marketing Platform (GMP) suites. Many setups fail because the administrator attempts the integration without matching access levels on a single Google account.
In GA4, you require the Editor or Administrator role at the Property level. In DV360, you must have Admin or Write permissions at either the Partner or Advertiser level. If your organization uses the Google Marketing Platform organization home, your user account should ideally be linked to both entities under the same unified organization profile.
Verify that your GA4 property is actively collecting data and that Google Signals is activated if you intend to target cross-device segments. Note that under modern privacy frameworks, Google Signals is no longer mandatory for standard web-based remarketing but remains highly beneficial for cross-device stitching.
Step-by-Step Integration Protocol
The actual connection is initiated from the GA4 interface. Follow these steps to establish the API handshake between the systems:
Step 1: Locate Product Links in GA4
Log in to Google Analytics. Navigate to the bottom-left corner and click the Admin gear icon. Ensure you have selected the correct Account and Property from the dropdown menus. In the Property column, scroll down to the Product Links section and select Display & Video 360 Links.
Step 2: Create the Link
Click the blue Link button in the top-right corner. If your Google account has the correct DV360 permissions, you will see a configuration option to Choose Advertisers. Click this link to open a list of DV360 Partners and Advertisers you have access to. Select the specific DV360 Advertiser you want to target with your GA4 audiences.
Step 3: Configure Settings and Data Sharing
This is the most critical technical step. You will be presented with two toggle switches:
- Enable Personalized Advertising: This must be toggled ON. If left off, your GA4 audiences will not export to DV360; the link will only serve read-only attribution and campaign reporting.
- Enable Campaign Attribution: Toggle this ON to allow DV360 campaign cost, click, and impression data to flow back into GA4 for multi-touch attribution modeling.
Step 4: Review and Submit
Click Next, review your configuration settings, and click Submit. The status in your GA4 Product Links table should now read "Linked".
Privacy Controls, Consent Mode v2, and PAIR
For programmatic campaigns running in or targeting the European Economic Area (EEA), regulatory compliance is strictly enforced via Google Consent Mode v2. If a user does not grant consent for personalized ads (specifically the ad_personalization='granted' parameter in the consent string), GA4 automatically filters that user out of any audience lists exported to DV360.
For brands managing stringent privacy rules, combining this with setting up Google PAIR in DV360 offers a secure, clean-room style solution for first-party data activation alongside standard GA4 audience links. PAIR allows you to securely upload encrypted first-party data directly to DV360, complementing the real-time behavioral streams generated by your GA4 property.
Additionally, review your GA4 Data Retention settings. By default, user and event data retention may be set to 2 months. For robust programmatic remarketing, change this setting to 14 months to ensure your audience pools remain deep and historical behaviors can be leveraged for targeting.
Creating and Provisioning High-Value Audiences
Once the link is active, any audience created in GA4 can be shared with your linked DV360 advertiser. To create an audience for programmatic targeting:
Navigate to Admin > Audiences in GA4 and click New Audience. You can build segments based on custom events, purchase thresholds, or predictive metrics. For example, a high-value programmatic remarketing segment could target users who have triggered a view_item event for a specific product category but have not triggered a purchase event within the last 30 days.
When saving the audience, ensure the Targeting Advertising option is active. Once saved, GA4 initiates the export process. Do not expect these audiences to appear in your DV360 line items immediately. The initial synchronization requires 24 to 48 hours to compile the user list and map the identities in the DSP.
Targeting GA4 Audiences in DV360
After the synchronization latency period, your GA4 audiences will appear in the DV360 interface under Audiences > All Audiences. They will be classified as First-Party lists, with the source labeled as "Google Analytics 4".
To assign these audiences to your programmatic tactics, navigate to your DV360 Advertiser, open the desired Campaign, and select the specific Insertion Order (IO) or Line Item (LI). Under the Targeting settings of the Line Item, select Audience Lists, search for your GA4 audience name, and include it in your targeting criteria.
If you are managing complex, multi-advertiser accounts, learning how to bulk edit DV360 line items can drastically speed up the targeting assignment process. This allows you to apply your newly synced GA4 audiences across dozens of line items simultaneously, bypassing manual UI click-paths.
Applying narrow GA4 audiences to private marketplace deals can severely restrict scale, often requiring deep diagnostic work like troubleshooting DV360 PMP deals that are not spending to verify if the audience size is choking delivery. Always ensure your GA4 audience pool meets minimum scale requirements before pairing it with highly restrictive PMP inventory.
Solving Audience Discrepancies and Data Drop-Off
A common friction point for ad ops teams is the discrepancy between user counts in GA4 and targetable cookie/ID counts in DV360. This discrepancy is natural and stems from several technical realities:
Identity Space Differences
GA4 counts "Users" based on a hierarchy of User ID, Google Signals, and Device ID (Client ID for web, Instance ID for apps). DV360 targets environments using Web Cookies (such as DoubleClick id cookies), Device Advertising IDs (IDFA and GAID), and Publisher Provided Identifiers (PPIDs). When GA4 exports an audience, the Google identity graph must match those GA4 identifiers with active, targetable programmatic identifiers. Match rates typically range from 60% to 85% depending on your audience's browser mix (Safari/Firefox vs. Chrome) and app usage.
Consent Frameworks and Global Settings
If Consent Mode v2 is implemented, a portion of your GA4 audience will be excluded from personalized targeting while still being tracked anonymously for reporting in Analytics. This creates a scenario where your GA4 reports show 10,000 active users, but your DV360 targeting interface shows an eligible pool of only 6,000 users.
Audience Exclusions and Recency
Keep in mind that GA4 dynamically updates audiences. If a user makes a purchase, they are immediately dropped from a "Cart Abandoner" list in GA4. However, that deletion can take up to 24 hours to sync to DV360. During this window, you may see slight targeting variances. If your audience size in DV360 is zero or fails to grow, check that the GA4 property has generated more than 100 active, consenting users in that specific segment within the last 30 days. DV360 enforces strict minimum-size thresholds to protect user privacy.
Frequently Asked Questions
Why can't I see my GA4 audience in DV360 after linking?
There is a standard 24-to-48-hour propagation delay before GA4 audiences sync to DV360. Additionally, ensure that "Personalized Advertising" was enabled during the link setup and that the audience has at least 100 active, consented users to meet privacy thresholds.
Do I need Google Signals enabled for GA4 audiences to work in DV360?
While Google Signals is highly recommended for cross-device stitching and building comprehensive user graphs, it is not strictly mandatory for standard web-based remarketing. However, disabling it will reduce your overall match rate and targetable list sizes in DV360.
What happens to my GA4 audiences in DV360 if a user revokes consent?
With Consent Mode v2, if a user changes their consent status to deny ad_personalization, GA4 instantly stops sharing that user's identifier with DV360. The user is automatically purged from active targeting lists in the DSP during the next sync cycle.