Skip to main content
ShieldLabs links each identification to its traffic source and risk signals. Use Traffic Analytics to find which channels and campaigns bring risky activity, then open the accounts and checks behind the totals.

​
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’s traffic_source contains channel, referrer_domain, landing_url, click_id_type and the five UTM fields. 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 is a traffic source in this view, not a risk signal. History uses flat source fields such as traffic_channel and entry_url. The scored webhook nests these under traffic_source.

​
Reading a risky source

  1. Open Top channels in Overview, or filter Analytics by channel, source or campaign.
  2. Compare volume, the Traffic quality and the distribution of identification risk bands.
  3. Read the signals responsible for risky checks. A corporate VPN audience has a different interpretation from browser automation or device spoofing.
  4. Switch to Users or Devices and inspect repeated activity and High-Risk Events.
  5. Compare with your own signup, activation and payment outcomes before changing spend or payouts.
A high Traffic quality does not by itself establish that every visitor is abusive or that a campaign has no value.

​
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 by event_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.