Issue:
Audience Protection is not adding users to audience lists, preventing Ads Defender from excluding or deprioritizing unqualified users across Google Ads, Microsoft Ads, and Meta Ads.
Cause Analysis and Solutions (Quick Overview):
Issue | Solution | Why This Happens |
Audience-Event not installed | Install the Audience-Event on all pages of the website. | Without the Audience-Event, no users are added to audience lists. |
Main Tag missing (Audience-Event dependency) | Ensure the Main Tag is installed on all pages. | The Audience-Event relies on the Main Tag to function properly. |
Audience-Event fires before user consent | Adjust tag firing rules to trigger after user consent. | Firing before consent risks ad account suspension for policy violations. |
Audience-Event not accepted in Ads Defender settings | Go to Click Fraud > Settings > Audience-Event and press "Accept". | Audience-Event will not trigger if not accepted for each ad account. |
Audience-Event not accepted for all ad accounts | Ensure the accept button is pressed for each connected ad account. | The Audience-Event must be individually accepted per account. |
Cross-Account-Conversions used (Google Ads only) | Connect the Google Ads Conversion Manager to Ads Defender. | Ads Defender cannot track audience events without linking the Conversion Manager. |
Content Security Policy (CSP) blocking the Audience-Event | Adjust the CSP to allow communication with Google and Ads Defender domains. | CSP restrictions can prevent the Audience-Event from firing properly. |
User connecting Ads Defender lacks sufficient permissions | Reconnect Ads Defender using an admin-level user. | Ads Defender cannot push audience data without admin or write permissions. |
Low consent acceptance rates | Monitor and optimize consent rates to increase audience capture. | Low consent rates limit the number of users eligible for Audience Protection. |
High volume of bounce clicks (short sessions) | For Google Ads, rely on IP-Protection as a fallback. | Short sessions prevent the Audience-Event from firing, resulting in no list population. |
Microsoft Ads – Slow audience growth | Continue monitoring as Microsoft Ads lists require only 300 users. | Microsoft Ads lists grow slowly but require fewer users for activation. |
Detailed Steps to Resolve:
1. Verify if the Audience-Event is Installed:
The Audience-Event must be installed on all pages of the website.
In Ads Defender, navigate to:
Click Fraud > Settings > Tracking Snippet.If the Audience-Event is missing:
Copy the snippet from Ads Defender and paste it right after the Ads Defender Main Tag
Alternatively, implement the Audience-Event through Google Tag Manager (GTM).
Ensure the Audience-Event fires after user consent.
2. Check for Main Tag Installation:
The Audience-Event depends on the Main Tag to function.
In Ads Defender, go to:
Click Fraud > Settings > Tracking Snippet.If the Main Tag is missing:
Copy and install the Main Tag across all pages.
3. Ensure Audience-Event Triggers After Consent:
The Audience-Event must not fire before user consent to comply with remarketing regulations.
If the tag fires before consent:
Adjust the consent management platform (CMP) to fire the Audience-Event only after consent is obtained.
Test by visiting the site in incognito mode, rejecting cookies, and verifying the tag does not fire.
4. Accept the Audience-Event in Ads Defender:
In Ads Defender, navigate to:
Click Fraud > Settings > Audience-Event.Look for the Accept button.
Press Accept to confirm awareness of the Audience-Event’s role and consent requirements.
Important: This must be done for each ad account in the workspace.
5. Resolve Cross-Account Conversions Issue (Google Ads Specific):
If the ad account uses Cross-Account Conversions in Google Ads, the Audience-Event requires additional configuration.
In Ads Defender, look for a warning message regarding Cross-Account Conversions.
To resolve:
Go to Click Fraud > Settings > Audience-Event.
Click Connect Conversion Manager.
Follow the setup assistant to authorize Ads Defender to link with Google Ads’ Conversion Manager.
6. Adjust Content Security Policy (CSP):
If Ads Defender detects a Content Security Policy (CSP) blocking the Audience-Event, a warning will appear on the dashboard.
Follow the provided instructions to modify the CSP
This ensures the Audience-Event can communicate with the necessary platforms.
7. Check User Permissions for Account Connection:
Ensure the user connecting Ads Defender to ad accounts has admin or write permissions.
Reauthorize Ads Defender using an account with the required permissions.
8. Address High Bounce Rates (Short Sessions):
If users bounce before the Audience-Event fires:
Google Ads: Rely on IP-Protection for blocking unqualified users.
Meta Ads: Enable Server-to-Server (S2S) integration to capture unqualified users directly.
Microsoft Ads: Continue monitoring – audiences build slower but require fewer users (300) for activation.
Important Notes:
Google Ads Fallback: IP-Protection compensates for low audience list population.
Meta Ads S2S: Provides an alternative method to populate lists even with short session durations.
Microsoft Ads: Requires smaller audience sizes (300 users) compared to Google and Meta.