Setup
Integration Guide
Start measuring visits, connect your ad platforms and review the results. Here are the steps for everyday use.
Return-visit measurement
Measure repeat clicks from the same browser to improve advertising-cost estimates. These IDs are not used for Bot verdicts, media decisions or billing.
Enabled by default. Measurement follows consent and privacy settings.
Where consent is required, connect your CMP’s permission and withdrawal signals to the tag. IDs are not used while consent is unknown. Browser privacy preferences are also respected.
The return-visit cookie has a seven-day lifetime, and ordinary server-side visit links follow a seven-day retention schedule. Copies of site-scoped browser-link information contained in Bot analysis archives instead follow archive retention. These stored copies are retained for fraud-prevention analysis and verification and improvement of classification accuracy, separately from return-visit measurement. Return-visit measurement itself is not used for individual Bot verdicts, media decisions or billing. Deleting or expiring a browser cookie does not delete these previously stored copies. Identifier-free daily return-visit snapshots are retained for 90 days. See the privacy policy for details.
window.adfraudMeasurementConsent = 'granted'; // granted | denied | pending
window.dispatchEvent(new Event('adfraud:measurement-consent'));Estimated advertising impact
An estimate assuming one prevented ad click per eligible Bot browser linked to an ad platform. Active exclusion settings in the platform are required.
No eligible media-link records are available yet. Estimates update hourly as records become available.
1. Installing the tracking tag
Place the measurement tag from Settings just before the closing body tag on each page of your site. If a web team handles installation, send them the tag as provided. Open a tagged page and check that the visit appears in your dashboard.
Never place two tracking tags on the same page (visits would be double-counted). When you enable CVR tracking, REPLACE your existing tag with the newly issued LP tag.
Connect your ad platforms
Choose a platform in Integrations, register its ID and switch the connection on (Pro and above). After detecting a Bot, connection settings and pauses are checked before connecting.
In your ad platform, add the Bot audience to the ads’ exclusion settings.
View setup instructions in IntegrationsSmartNews Ads
Connect detected Bots to SmartNews ad exclusions. AdFraud sends PageView events to a dedicated pixel; exclude that audience on Standard-targeting ads. Available on Pro and above.
- Log in to SmartNews Ads Manager
- Create a dedicated AdFraud pixel under Pixel. Keep it separate from your regular analytics pixel, and do not install the dedicated pixel tag across your website.
- Copy the Pixel ID shown
- In AdFraud, open Integrations, select SmartNews, and paste the Pixel ID under Register ID, then save.
- Audiences → Create custom audience → Website activity: choose this pixel, action type Page view, auto-update ON (it may take 24–48 hours to populate)
- In the ad groups of the target campaigns, set that audience as excluded
- Set the target campaigns to Standard targeting (with SMART targeting, ads may still be delivered to excluded custom audiences — SmartNews official)
Check audience status in SmartNews Ads Manager. In progress or Failed audiences are not applied to delivery. For Audience too narrow, check exclusion availability with SmartNews; once Available, you can record the exclusion confirmation in AdFraud.
View setup instructions in IntegrationsGoogle Ads IP exclusions
Available on Starter and above. Add your Google Ads customer ID in Settings and accept the connection invitation in Google Ads. IPs that meet the requirements are synced after checks designed to avoid affecting people on shared networks.
Start with the candidate count and latest sync status. If it says “Needs attention,” check the account connection on the Integrations page.
Sync counts refer to the latest registration, not Bot visits in the selected period. Acceptance does not confirm ad exclusion is applied.
Understand your report
Choose your site and date range, then review Normal traffic, Suspicious traffic and Bot counts. Bot detections and Bot visits with a recorded connection start are separate numbers.
Monthly comparison shows visits, Bot visits, Bot rate and Bot visits linked to media alongside the previous month. The current month runs through yesterday and is compared with the same number of days in the previous month. Completed months use the full calendar month. You can download a CSV or print the report.
The Bot traffic ad-cost equivalent is a reference amount based on Bot counts and current CPC. It is not measured savings.
See how the numbers are defined
Check ad exclusion settings in your ad platform.
Each Bot visit is counted once in the total, even when linked to multiple platforms. Platform counts may overlap. Unavailable records are shown separately.
Campaigns
Find campaigns with more Bot visits and inspect the underlying traffic.
Compare visits by campaign ID or name in the ad URL. Campaigns are listed separately by site and source, even when names match. Ad clicks, spend and conversions are not included.
Open a campaign’s details to go directly to its ad platform settings. When you add ads, check that your Bot exclusion audience is applied. Confirmation records show the date and scope your team checked.
Back to campaignsAbout these numbers
These visits could not be matched to a campaign. Add a campaign ID (such as utm_id) or name (utm_campaign) to your ad URLs to classify them. Do not include personal information.
Today and yesterday use current records; earlier days use daily totals. Daily totals are kept for 90 days and visit details for 7 days. Days with incomplete records show “No breakdown.” Different URL labels or identifiers may appear as separate campaigns.
More measurement options
2. Per-network click IDs (required for per-network reports)
Per-network verdicts and CVR are identified by the click ID appended to your URL when an ad is clicked. Most networks append it automatically — there is usually nothing to do.
| Network | Parameter | What you need to do |
|---|---|---|
| TikTok Ads | ttclid | Nothing (appended automatically on ad click) |
| Meta Ads (Facebook / Instagram) | fbclid | Nothing (appended automatically) |
| Google Ads | gclid | Confirm auto-tagging is ON (default ON — Settings → Account settings) |
| Yahoo! Ads | yclid | Turn ON auto-tagging in the ad console's account settings |
If a click ID is missing, the source is estimated from referral information and campaign labels in the URL. In-app browsers may omit this information, so check auto-tagging as well.
3. Enabling CVR tracking (Pro plan and above, optional)
Install the conversion tag to compare conversion rates for normal traffic and Bot or suspicious traffic, including a breakdown by platform.
- Open Settings → Edit the site → turn on CVR measurement
- Press Save — the toggle alone does not apply the change
- Replace the existing tag on every page with the newly issued LP tag (with data-cvr)
- Place the CV tag (with data-conversion) on your purchase-complete page
The LP tag and CV tag must live on the SAME domain. The tracking cookie is domain-scoped, so a setup where the article LP and the checkout page are on different domains cannot be linked.
CVR tracking uses one first-party cookie (7-day retention, never shared with third parties). Please make sure your privacy policy mentions cookie usage. Bot detection itself uses no cookies.
Test it: open your LP with a parameter such as ?ttclid=TEST123 and proceed to the purchase-complete page — the conversion appears on the dashboard CVR card with its network.