Platform coverage
See what ClickReport automates, monitors, and leaves manual
Buyers should not have to infer platform coverage from scattered copy. This page shows the current public workflow by platform so you can see where ClickReport acts directly and where you still use the evidence trail to take manual steps.
ClickReport is positioned for a single-operator SMB, so this page reflects one operator's workflow rather than agency workspaces or client-management handoffs.
Current public scope
Direct ad-platform automation
Google Ads exclusions and response workflows inside the app.
Manual platform workflows
Microsoft Advertising exclusions and other non-Google platform actions.
Cross-platform monitoring
Tracked landing-page traffic, alerts, exports, and uptime monitoring where your campaigns reach instrumented pages.
Coverage matrix
Platform-by-platform workflow detail
The matrix below reflects the current public product. It separates direct ClickReport automation from monitoring and from the steps that still happen inside the destination ad platform.
| Platform | Automated in ClickReport | Monitored and reported | Manual or platform-native | Notes |
|---|---|---|---|---|
| Google Ads | Connected customer selection, fraud-scoring workflows, and in-app IP exclusion updates for approved campaigns. | Visitor, IP, referrer, keyword, landing-page, alert, and export data tied to tracked paid traffic. | Review thresholds, validate incidents, and decide which campaigns or customers should receive exclusions. | This is the current direct ad-platform automation surface published by ClickReport. |
| Microsoft Advertising | No direct in-app exclusion sync is published today. | Tracked landing-page visits, suspicious visitor patterns, referrer and campaign evidence, alerts, and exports. | Apply exclusions or other remediation steps inside Microsoft Advertising using the ClickReport evidence trail. | Coverage is investigation-first rather than direct blocking automation. |
| Other tagged paid traffic | No direct ad-platform sync or exclusion workflow is published today. | Landing-page traffic signals, visitor evidence, uptime checks, keyword or tag context, and exported reports when your campaigns hit tracked pages. | Use ClickReport findings in your ad platform or your own internal review process. | Useful when campaign tags and landing-page instrumentation are in place. |
| Landing pages | Five-minute uptime checks, incident alerts, and recovery notifications. | Response times, downtime history, affected landing paths, and related fraud context across the selected date range. | Fix the destination issue or pause traffic sources outside ClickReport when a page needs intervention. | Landing-page monitoring supports paid traffic regardless of the upstream ad platform. |
How to read it
Three coverage states, clearly separated
Automated in ClickReport
Actions the public product performs directly, including Google Ads exclusion workflows and landing-page monitoring.
Monitored and reported
Signals ClickReport captures, scores, alerts on, and exports so a single operator can review suspicious activity quickly.
Manual or platform-native
Steps that still happen outside ClickReport, such as applying exclusions in platforms without a published direct sync.
Next step
Compare coverage, then review pricing or setup
If you need direct platform automation beyond Google Ads, this page should make that limitation obvious. If your priority is investigation speed, evidence exports, and landing-page monitoring, the current workflow may still fit well.