Main Tag – The Foundation of User Tracking
The Main Tag is the core tracking script that must be embedded on every page of your website.
Purpose:
Tracks users across multiple sessions to gather insights into long-term behaviour patterns.
Identifies returning users to assess whether their behaviour aligns with qualified or unqualified patterns.
Implementation Requirements:
The Main Tag must fire without user consent.
This tag should load immediately when the page is accessed to ensure comprehensive tracking.
Where to Find the Main Tag:
Log into Ads Defender.
Navigate to the Click Fraud feature.
Open the Settings menu.
Locate the tracking snippet and copy the Main Tag.
Paste the snippet directly into the HTML of every page on your website, or use Google Tag Manager by embedding it as a Custom HTML tag.
A checkbox in the Settings page will indicate if the tag has been detected on your domain. Detection may take up to 24 hours after initial setup.
Important:
Without the Main Tag, no other Ads Defender tags will function.
The Main Tag alone provides broad user data but lacks session-specific insights to detect advanced bots or simulated devices.
Session Tag – Session-Based Real-Time Analysis
The Session Tag works in tandem with the Main Tag, focusing on deeper device data during individual sessions to detect unqualified devices, advanced bots or simulated devies.
Purpose:
Captures detailed device-level data during a single session.
Makes real-time decisions about device authenticity during that session.
Transmits only the final decision (qualified/unqualified) back to the Main Tag.
Implementation Requirements:
The Session Tag must also fire without user consent.
It must be embedded directly after the Main Tag on all pages.
The Session Tag cannot operate without the Main Tag. Both tags must work together.
Where to Find the Session Tag:
Log into Ads Defender.
Go to the Click Fraud feature and enter the Settings menu.
The Session Tag is located in the same Settings area but requires manual activation.
Accept the enhanced privacy conditions that come with enabling the Session Tag.
Once activated, copy the Session Tag and paste it on your website, directly following the Main Tag.
Like the Main Tag, a checkbox will show if the Session Tag has been detected on your domain. Detection can take up to 24 hours.
Key Limitations:
The Session Tag cannot recognize users from previous visits. It only analyzes data from the current session.
If the Session Tag is missing or blocked, session-specific analysis will not occur,limiting Ads Defender’s effectiveness.
Understanding Essential Events: Audience Event and Whitelisting Event in Ads Defender
Beyond the Main Tag and Session Tag, Ads Defender relies on key events that serve specific purposes in detecting and protecting against click fraud. These events enable key functionalities. Below is an overview of the essential events you need to implement.
Audience Event – Building Exclusion Lists
The Audience Event is critical for creating audience lists that can later be excluded from ad targeting on platforms like Google Ads, Microsoft Ads, and Meta Ads.
Purpose:
Adds users to audience lists used for exclusion from future ad campaigns.
Implementation Requirements:
The Audience Event should NOT fire without user consent.
It must be categorized as a marketing tag and only triggered if the user consents to marketing cookies or tracking.
This is necessary because the event uses remarketing functions in ad platforms, which require explicit consent under privacy regulations.
Where to Find the Audience Event:
Log into Ads Defender.
Navigate to the Click Fraud feature and open the Settings menu.
Locate the Audience Event snippet.
Manual activation is required – users must accept the Audience Event for every account individually.
After activation, copy the event snippet and paste it onto every page of your website, right after the Ads Defender Tags.
Troubleshooting the Audience Event – Common Issues and Solutions
The Audience Event plays a vital role in excluding unqualified users from future ad campaigns. However, due to its complexity and reliance on external platforms, several issues can prevent it from functioning correctly. Below are common problems and solutions to ensure the Audience Event operates as intended.
1. Content Security Policy (CSP) Blocking the Audience Event
Problem:
If your website has a Content Security Policy (CSP) enabled, it may block the Audience Event from sending requests to Ads Defender servers. This can prevent the event from firing and populating audience lists.
Signs of CSP Interference:
Ads Defender displays an error message indicating the Audience Event is being blocked.
Audience lists remain empty despite the event being implemented correctly.
Solution:
Ads Defender provides guidance on what to add to the CSP to resolve the issue.
Ensure this policy is updated and applied across all pages.
2. Audience Event Firing Without Consent
Problem:
The Audience Event should not fire without user consent because it leverages remarketing features from platforms like Google Ads, Microsoft Ads, and Meta Ads. If the event triggers without consent:
Audience lists will still populate.
Non-compliance with ad platform policies may result in penalties.
Worst-case scenario: Temporary or permanent account suspension by ad platforms.
Solution:
Ensure the Audience Event is placed behind user consent.
The event should be triggered only if the user has accepted marketing cookies or opted into advertising tracking.
Google Consent Mode is automatically integrated by Ads Defender – no manual setup is required. Ads Defender will push the user’s consent status with the Audience Event.
Check your consent management platform (CMP) to verify the Audience Event is gated behind consent.
3. Audience Event Not Activated in All Accounts
Problem:
The Audience Event requires manual activation for each account. If activation is skipped:
Audience lists will populate in some accounts but not others.
Users may notice inconsistencies in audience sizes across different ad platforms.
Solution:
Double-check that the Audience Event is activated for all relevant accounts.
Log into Ads Defender and:
Go to the Click Fraud feature.
Open the Settings menu.
Verify that the Audience Event is enabled and activated for each account.
If not activated, accept the enhanced privacy conditions and enable the Audience Event.
Summary of Troubleshooting Steps
Issue | Cause | Solution |
Audience Event blocked by CSP | Content Security Policy prevents requests | Update CSP to allow Ads Defender requests |
Audience Event fires without consent | Misplaced outside of consent workflow | Place behind consent – verify CMP configuration |
Audience lists inconsistent across accounts | Event not activated in all accounts | Activate manually in Ads Defender for each account |
By addressing these potential pitfalls, you ensure that the Audience Event functions properly, keeping your ad platforms compliant and your audience lists accurate.
Whitelisting Event – Identifying Positive Users
The Whitelisting Event distinguishes high-value users (such as converting customers) from unqualified traffic. By identifying valuable users, Ads Defender ensures these users are exempt from click fraud protection mechanisms.
Purpose:
Automatically whitelists users who demonstrate valuable or converting behavior.
Prevents legitimate users from being blocked by click fraud protection.
If a user’s IP is currently blocked, triggering this event removes the IP from blocklists immediately.
Implementation Requirements:
The Whitelisting Event should fire without user consent.
It should be placed on pages where positive user actions occur, such as:
Order confirmation pages
Thank you pages
Cart pages
Do not place the Whitelisting Event on all pages. Doing so results in Ads Defender whitelisting every visitor, leading to a 0% unqualified ratio and reduced effectiveness of click fraud protection.
Where to Find the Whitelisting Event:
Log into Ads Defender.
Go to the Click Fraud feature and enter the Settings menu.
Find the Whitelisting Event snippet.
Copy and paste the snippet into the appropriate pages on your website (e.g., checkout or order confirmation).
Placement Recommendations:
Implement the event on pages that reflect successful conversions or valuable actions.
Avoid placing it on general landing pages, as this could dilute its purpose and result in unwanted whitelisting of non-converting traffic.