Loading article introduction…
Loading article body…
No, ClickGuard doesn’t currently offer a public API or webhooks, so bad-click data can’t be sent to outside systems automatically. You can export bad clicks as a CSV from Click Forensics for your BI tool or Google Ads refund requests, and ClickGuard already blocks fraudulent traffic in Google Ads, Microsoft Ads and Meta Ads.
Not at the moment. ClickGuard doesn't offer public API access or outgoing webhooks, so bad-click data (IP address, classification reason, timestamp, website, campaign or event ID) can't be sent to outside systems automatically.
Export click data as a CSV. Go to Click Forensics, choose a date range, filter to Bad clicks and click Export in the top-right corner. The CSV opens in Excel or Google Sheets, or you can import it into your own database or BI tool.
Use the export for refund requests. The same CSV works as the click log Google asks for in a Click Quality Investigation request. See How to Request Refunds from Google Ads.
Let ClickGuard take action for you. Most teams want bad-click data so they can block it. ClickGuard does that automatically by excluding fraudulent IPs and IP ranges in Google Ads and Microsoft Ads and blocking visitors in Meta Ads. You can check every change in Google Ads → Change History.
We keep expanding how ClickGuard data can be used. If an API or webhook integration would help your workflow, contact our support team and tell us what you need. Requests go straight into our product planning.