Automations - Set Up Automatic Protection Rules
Set up automatic responses to fraud patterns.
Automations allow you to create custom rules that automatically respond to fraud patterns and suspicious activity. Define conditions and actions to protect your ad spend without manual intervention.
Automations require a connected Google Ads account. This feature is not available in demo mode.
Overview
Automations work by monitoring your click traffic in real-time and taking action when specific conditions are met. This enables proactive protection beyond ClickFortify's built-in detection.
How Automations Work
- Trigger — A condition is detected (e.g., fraud score exceeds threshold)
- Evaluation — Rule criteria are checked against the click data
- Action — Automated response is executed (e.g., add to exclusion)
- Logging — Activity is recorded for review
Creating an Automation
Step 1: Navigate to Automations
Click Automations in the Protection section of the sidebar.
Step 2: Click Create Rule
Start the automation creation wizard.
Step 3: Define Trigger Condition
Select what will trigger this automation:
| Condition Type | Description | Example |
|---|---|---|
| Fraud Score | Threshold-based scoring | Score > 80 |
| Click Velocity | Clicks per time period | > 10 clicks/minute |
| Bounce Rate | High bounce from same source | > 90% bounce rate |
| VPN/Proxy | Traffic through anonymizers | VPN detected = true |
| Geographic | Location-based rules | Country = [blocked list] |
| Device Type | Specific device patterns | Device = bot signature |
Step 4: Select Action
Choose what happens when the condition is met:
| Action | Description | Reversible |
|---|---|---|
| Add to Exclusion | Temporary block via Google Ads | Yes (expires) |
| Add to Blacklist | Permanent manual block | Yes (manual removal) |
| Send Alert | Email notification | N/A |
| Log Only | Record without blocking | N/A |
Step 5: Set Scope
Define where the automation applies:
| Scope | Applies To |
|---|---|
| All Websites | Every protected website |
| Specific Website | Single website only |
| All Campaigns | Every campaign in account |
| Specific Campaign | Single campaign only |
Step 6: Enable and Save
Review your rule and activate it.
Example Automations
High-Risk Auto-Block
Automatically block severe fraud attempts.
| Setting | Value |
|---|---|
| Condition | Fraud Score > 90 |
| Action | Add to Blacklist |
| Scope | All campaigns |
| Alert | Email notification |
Click Velocity Monitor
Catch rapid-fire clicking patterns.
| Setting | Value |
|---|---|
| Condition | Click Velocity > 10/minute from same IP |
| Action | Add to Exclusion + Send Alert |
| Scope | Website level |
| Duration | 30-day exclusion |
VPN Traffic Handler
Manage traffic from VPN/proxy sources.
| Setting | Value |
|---|---|
| Condition | VPN Detected = true AND Fraud Score > 50 |
| Action | Add to Exclusion |
| Scope | Search campaigns only |
| Duration | 7-day exclusion |
Geographic Restriction
Block traffic from specific regions.
| Setting | Value |
|---|---|
| Condition | Country in [blocked country list] |
| Action | Log Only (monitor) or Exclude |
| Scope | All campaigns |
| Alert | Weekly summary |
Bot Detection Response
React to identified bot traffic.
| Setting | Value |
|---|---|
| Condition | Bot Detected = true |
| Action | Add to Blacklist |
| Scope | All websites |
| Alert | Immediate notification |
Managing Automations
View All Rules
The Automations page displays all your rules with:
- Rule name and description
- Current status (enabled/disabled)
- Trigger count (how many times fired)
- Last triggered timestamp
Edit Rules
Click on any rule to modify:
- Adjust conditions and thresholds
- Change actions
- Modify scope
- Update alert settings
Enable/Disable
Toggle rules on or off without deleting them. Useful for:
- Testing new rules cautiously
- Temporarily pausing during investigations
- Seasonal adjustments
Delete Rules
Remove rules that are no longer needed. This action cannot be undone.
Automation History
View a log of all automation activity:
- When each rule was triggered
- What action was taken
- Which entity was affected
- Success/failure status
Best Practices
- Start conservative — Use high thresholds initially, then adjust
- Use alerts first — Test with "Log Only" before blocking
- Layer rules — Multiple rules with different thresholds
- Review regularly — Check trigger frequency and effectiveness
- Document rules — Use clear names and descriptions
- Avoid overlap — Ensure rules don't conflict with each other
Limitations
- Maximum of 50 active automations per account
- Some conditions require specific data availability
- Actions may take a few seconds to execute
- Google Ads API limits apply to exclusions
Test new automations with "Log Only" or "Send Alert" actions before enabling automatic blocking to avoid false positives.