Estimate wasted ad spend from invalid traffic. Try the calculator

Connect your advertising platforms

See what ClicksArmor is designed to read and write on Google Ads, Meta Ads, and Microsoft Advertising—and where each network’s rules differ. Platform connect and sync capabilities are rolling out in stages; confirm what is live for your workspace with sales.

Advertising platforms and tracking tools

Coverage below is the intended product model—not a guarantee that every connect or sync action is live for every account today. Ad platforms are separate from setup and reporting tools. Depth covers planned reads, writes, and limits per network.

Advertising platforms

Google Ads

Google Ads

Campaign monitoring, click fraud detection, and supported IP exclusions.

Meta Ads

Meta Ads

Campaign monitoring, suspicious traffic detection, and eligible audience exclusions.

Microsoft Advertising

Microsoft Advertising

Campaign monitoring, click fraud detection, and supported IP exclusions.

Tracking & data tools

Google Tag Manager

Google Tag Manager

Deploy the ClicksArmor site tag through GTM without editing page templates.

ClicksArmor site tag

ClicksArmor site tag

Lightweight landing-page signals for detection—built to stay out of page performance.

Data & reporting

Data & reporting

Export threat and exclusion summaries for agencies and performance teams.

What each network supports

Meta custom audience exclusions are not the same as Google or Microsoft IP sync. Treat them separately.

Account authorization

Google Ads

Connect via Google Ads account authorization. Detection can cover Search, Display, Shopping, and Performance Max traffic on linked accounts. Monitoring does not imply every campaign type supports the same exclusion options.

  • •Reads: authorized campaign and performance data, including available click metrics, for traffic analysis and reporting
  • •Writes: supported IP exclusions where Google Ads allows, subject to account permissions and API access
  • •Limit: exclusion capabilities follow Google Ads IP exclusion rules and campaign-type restrictions

Custom audience exclusions

Meta Ads

Meta does not offer Google-style IP exclusion lists. ClicksArmor analyzes suspicious Meta traffic and, when eligible user identifiers are available, syncs custom audience exclusions. Platform ads data and site-tag signals are distinct inputs.

  • •Reads: authorized campaign delivery and performance data, combined with available site-tag signals for traffic analysis
  • •Writes: custom audience exclusions when eligible identifiers are available and supported by Meta
  • •Limit: audience matching depends on identifier availability, account permissions, and Meta policies

Account connect + supported exclusions

Microsoft Advertising

Connect Microsoft Advertising accounts for campaign analysis, suspicious traffic detection, and supported IP exclusion management.

  • •Reads: authorized campaign and performance data for detection and reporting
  • •Writes: supported IP address exclusions at campaign level
  • •Limit: IP exclusions follow Microsoft Advertising's supported formats, campaign-level limits, and account permissions

Authorize → configure → sync

How you connect platforms. How it works covers the product loop after accounts are linked.

Step 1

Authorize

Connect your advertising accounts through each platform’s authorization flow and grant the permissions required for supported actions.

Step 2

Configure

Select accounts, install the site tag or configure GTM, and set your initial protection thresholds.

Step 3

Sync

Analyze connected traffic and sync supported exclusions when enabled rules trigger an eligible action.

Access you grant and can revoke

Permission scope

ClicksArmor uses platform authorization to access the account data and protection capabilities required for connected features. Available actions depend on platform permissions, account roles, and API restrictions.

Revocation

Remove ClicksArmor from the ad platform’s connected apps anytime. Exclusions already pushed remain until you clear them in-platform.

Credentials

Connections use platform OAuth. We do not store your Google, Meta, or Microsoft login password.

Common connection issues

Connection fails

Confirm the connected user has sufficient permissions for the selected advertising account and the actions you want to perform, and that pop-up blockers are not stopping authorization.

Permission errors

Re-authorize with a user that can manage the required actions. For agency accounts, confirm that the manager account, Business Manager, or equivalent organization-level access includes the selected client account.

Sync delays or rejects

Platforms rate-limit or reject malformed lists. Check exclusion logs in the workspace and change history in the ad platform.

Connect the platforms you already run

Connect your ad accounts, review invalid traffic with clear reasons, and enable exclusions when you are ready.

Start free trial