Daily Google Ads sync
Bring in Google-reported campaign spend and click totals. Each click receives its campaign's average cost for the day, with a 90-day initial backfill.
Explore the connection ↗Skyfense identifies the paid campaign behind a visit, evaluates that session for automation and fraud, and records whether the click was valid. This connects ad performance to the same evidence used to protect checkout.
Click IDs persist in sessionStorage for the life of the tab, so a checkout page still knows the campaign that paid for the visit.
On landing, Skyfense reads click IDs such as gclid, fbclid, msclkid, and ttclid, plus campaign UTM values. If an ID is stripped, the referrer can identify the network.
The attribution follows the tab through the funnel. Bot, automation, ML, behavior, IP, and checkout signals are checked together rather than with a separate ad-fraud score.
Each attributed session receives a valid or invalid assessment with its network, campaign, click ID, and reasons. The dashboard aggregates those results by network. The full click log adds network and validity filters, pagination, and a campaign breakdown.
When enabled for a workspace, the guard loads before ad-network snippets and watches their event queues: Google dataLayer, Meta fbq, Microsoft uetq, and TikTok ttq.
If the session is blocked, calls that would report a click or conversion are silently suppressed. The page still works, while fraudulent behavior stays out of the optimization data used by the ad platform.
This safeguard is opt-in because a false positive can affect legitimate reporting. Merchants should validate detection before enabling it.
Known crawlers, fake Googlebot traffic, scrapers, scanners, and datacenter browsers are classified before the ad assessment.
Selenium, Puppeteer, Playwright, headless artifacts, and the behavioral model feed into click validity.
Review network, campaign, click ID, valid/invalid status, reasons, and linked session forensics. Pixel Guard status also breaks blocked ad-attributed visits down by all four supported networks.
Bring in Google-reported campaign spend and click totals. Each click receives its campaign's average cost for the day, with a 90-day initial backfill.
Explore the connection ↗Export monthly invalid-click evidence and track claims from pending to submitted to credited. You submit the claim; Google decides the credit.
See refund evidence ↗Consent-based IP sync and placement review help you act on recurring patterns. The beta applies changes across every account the connected login can access.
Review beta scope ↗What marketers ask about catching invalid clicks and protecting ad budget.
It reads the ad tracking code on the landing link, such as Google gclid, Meta fbclid, Microsoft msclkid, or TikTok ttclid. If that code is missing, it can recognize the ad network from the referring website.
The pixel guard only holds back events for sessions judged fraudulent, and it stays off until you switch it on. That way you can confirm the detection fits your traffic before anything is suppressed.
Yes. The Pro and Business beta syncs Google Ads daily with a 90-day initial backfill. Click costs use campaign-day averages, with your entered CPC as a fallback when synced data is unavailable. You can also prepare refund evidence and review exclusions.
No. The dashboard measures traffic risk and allocates spend to invalid clicks. The pixel guard controls reporting, not charges already billed by an ad network. You submit any Google Ads claim yourself, and Google decides whether to issue a credit.
Google Ads, Meta, Microsoft/Bing, and TikTok today, plus generic UTM campaign links from any source.