Skip to main content

3. Connecting Additional Ad Accounts (optional)

L
Written by Lukas Jackson

For clients managing multiple ad accounts across different platforms, connecting additional accounts to Ads Defender is a critical next step. This guide is also relevant, when new accounts should be added to an already existing workspace in Ads Defender.


When to Connect Additional Accounts

Connecting additional accounts is typically done after the initial account setup is complete and:

  • The first ad account is successfully connected.

  • A Check-Up Call has been completed.

  • The tracking configuration on the website is fully operational.

By following this process, you avoid duplication of effort and leverage existing tracking configurations across accounts that share the same domain.


Step 1: Initiating the Account Connection

To connect additional ad accounts:

  1. Navigate to Workspace Management.

  2. Click the Add Account button.

  3. Select the Publisher (Google Ads, Microsoft Ads, or Meta Ads).

  4. Choose the appropriate Google/Microsoft/Meta User to authenticate the account.

  5. Grant the necessary permissions when prompted.

  6. Select one or more ad accounts to connect.


Step 2: Automatic Domain and Tracking ID Matching

Once the new account is connected, Ads Defender automatically checks whether:

  • The new account should inherit the existing tracking ID (for shared domains).

  • A new tracking ID needs to be generated (for new domains).

How it works:

  • Domain-Based Matching:

    • Ads Defender reviews the advertised domains in the new ad account.

    • If an existing tracking snippet with an ID is detected on the domain, the same tracking ID is assigned to the new account.

  • New Domains:

    • If Ads Defender identifies a new domain that hasn’t been tracked before, a new tracking ID is automatically generated.


Handling Country-Specific Domains

  • If the same brand operates on different country-level domains (e.g., company.de and company.it), Ads Defender:

    • Recognizes these domains as separate entities.

    • Assigns them the same tracking ID if overlap in user traffic is unlikely.

    • This ensures that cross-domain traffic is properly segmented but doesn’t create unnecessary tracking IDs.


Step 3: Reviewing and Configuring New Accounts

Once the new ad accounts are connected:

  1. Navigate to Click Fraud > Settings

    • Review the inherited tracking configuration.

    • In most cases, the following tags will automatically appear as active if the domain is already tracked:

      • Main Tag

      • Whitelisting Event

  2. Audience Event and Session Tag:

    • Both the Audience Event and the Session Tag must be accepted manually for each new ad account.

    • Ads Defender will recognize if these tags are already embedded, but the user must still confirm activation on the account level.

    • This ensures each account is individually authorized for comprehensive tracking.


Step 4. Offsite Tracking – Ensuring Full Coverage on Ad Platforms

In addition to onsite tracking tags, Ads Defender uses offsite tracking methods to ensure fraudulent traffic is detected and blocked directly on ad platforms.

  • Google Ads Tracking Template:

    • Apply the tracking template at the account level in Google Ads using the toggle in the Settings.

    • Important:

      • Ensure no existing tracking template is overwritten on campaign or ad group levels.

      • If campaign-level templates are in use, consult Ads Defender support to merge templates manually.

  • Microsoft Ads Tracking Template:

    • Similar to Google Ads, ensure that the tracking template is applied at the account level.

    • Verify that no lower-level templates (campaign or ad group) override the account template. If campaign-level templates are in use, consult Ads Defender support to merge templates manually.

  • Meta Ads – af_ext Parameter:

    • For Meta Ads, Ads Defender uses the af_ext custom parameter.

    • This parameter must be applied to all ads Manually at the ad level within Meta Ads Manager.

    • Review regularly to ensure the parameter is attached to all active ads. This can easily be done using the "Traffic Identification" Section in the Ads Defender Settings.

    • Without the af_ext parameter, tracking will not function properly on Meta Ads.


Step 5: Live View – Real-Time Tracking Validation

  • Navigate to Click Fraud > Live View within Ads Defender.

  • This section shows real-time data of clicks interacting with your ads and website.

  • Look for:

    • Unqualified clicks appearing in the live view.

    • This indicates that Ads Defender is actively detecting and categorizing invalid clicks.

    • Live View provides immediate confirmation that tracking is working, even before data appears in the main dashboard.


Step 6. Understanding Dashboard Refresh Cycles

  • Dashboard Data Refresh:

    • The main Ads Defender dashboard refreshes every 24 hours.

    • This means that even after full setup, the dashboard may appear empty for the first 24 hours.

  • Real-Time Alternative:

    • Use the Live View to verify that tracking is active and catching unqualified clicks in real time.

    • The dashboard will populate automatically during the next refresh cycle.


Key Points to Remember

  • Tracking Snippet and Whitelisting Event are automatically inherited for accounts advertising on the same domain.

  • Audience Event and Session Tag must be manually reviewed and activated for each new ad account.

  • If needed, assign existing Members to the new accounts in Workspace Management > Accounts by checking the new account and adding a member to it.


Summary of Steps:

  1. Go to Workspace Management and click Add Account.

  2. Choose the Publisher and authenticate with a Google/Microsoft/Meta user.

  3. Allow Ads Defender to assign or generate a tracking ID based on the domain.

  4. Review the new account’s tracking and protection settings.

  5. Manually accept the Audience Event and Session Tag for each new account.

  6. Apply or check the tracking template for Google and Microsoft Ads.

  7. Ensure the af_ext parameter is active for Meta Ads campaigns.

Did this answer your question?