Traffic quality
Traffic quality summarizes traffic risk on a scale from 0 to 100. Lower values mean less risky traffic. Use it to compare periods, sources and campaigns, then inspect the underlying identifications. Checks scoring 60 or more contribute full weight; checks scoring 30–59 contribute half weight. Checks below 30 add no weight but remain in the total count. A weighted sum equal to half the total number of checks reaches 100. The result is capped at 100 and rounded to a whole number; with no checks, it is 0. This measures risk concentration across identifications, not the percentage of dangerous visitors. See Traffic quality. The individual check still has its own Risk Score. Identity categories and event confidence are separate measurements.Channels, referrers and campaigns
Traffic attribution uses click identifiers, UTM parameters and referrers. The webhook’straffic_source contains channel, referrer_domain, landing_url, click_id_type and the five UTM fields.
On an identification card, Traffic source shows Channel, Referrer, Entry page, Click ID type and UTM parameters. These fields describe acquisition and do not affect the Risk Score.
Channels include Google Ads, Microsoft Ads, Meta, TikTok, LinkedIn, X, Pinterest, Organic Search, Search bot, Referral, Direct and Other. Social channels can contain organic referrals as well as ads; a channel name alone does not establish that a visit was paid.
Search bot describes the visit’s source here; it does not establish that the Search bot risk signal fired.
UTM values come from the URL and do not by themselves establish Channel. Missing values appear as dashes on the card.
Referrer stores a registrable domain without subdomains or a page path:
www.news.google.co.uk becomes google.co.uk. It can be absent on direct visits, because of browser or referring-site settings, or on a check without JavaScript. A missing referrer does not prevent Channel from being determined separately.
Entry page is the URL where the check ran, which is not necessarily the visit’s first page. URL query parameters are retained; the fragment after # is not. It is separate from the referring domain. The webhook calls it traffic_source.landing_url.
A History identification card groups attribution under traffic: traffic.channel, traffic.referrer_domain, traffic.entry_url, traffic.click_id_type and the five traffic.utm_* fields. The scored webhook instead uses data.traffic_source, with landing_url for the page address. See Traffic Source.
Reading a risky source
- Open Top channels in Overview, or filter Analytics by channel, source or campaign.
- Compare volume, the Traffic quality and the distribution of identification risk bands.
- Read the signals responsible for risky checks. A corporate VPN audience has a different interpretation from browser automation or device spoofing.
- Switch to Users or Devices and inspect repeated activity and High-Risk Events.
- Compare with your own signup, activation and payment outcomes before changing spend or payouts.
Export and backend analysis
The analytics dashboard exports identifications in the selected filter. Narrow large selections to fit the displayed export limit. History and exports do not use your identification quota. When aggregating scored webhooks, deduplicate byevent_id and maintain the latest result for each identification_id before counting checks. The value 999 means Banned IP and is separate from the normal score range. Preserve source fields with the check so you can join them to your application’s outcomes.
Next: Traffic quality use case, Affiliate fraud, Risk signals.