Integrations
Segment and Amplitude integration
Keep the reports your team already uses. DataCops sends every session into Segment and Amplitude marked clean or bot, with the reason, so any chart, funnel or audience can show real visitors only.
What it is
DataCops checks every session on your own domain for bots, VPNs, proxies, Tor and data-center traffic. This integration sends that verdict into Segment and Amplitude as one event per session, so your existing analytics can separate real people from bots.Nothing in your current Segment tracking plan or Amplitude project changes. DataCops only adds one event, next to the events you already send.
What arrives
Every session arrives as one event named DataCops Session Scored. Clean and flagged sessions are both sent, so your totals always add up. The event carries these properties:
| Property | What it means |
|---|---|
is_clean | true when the session is not a bot, VPN, proxy, Tor or data-center visit. The one field to filter on. |
is_bot | true when the session was flagged as automated. |
bot_reasons | The signals that fired, for example headless browser detected. |
is_vpn, is_proxy, is_tor, is_datacenter | The network checks, one true/false each. |
country, city | Where the visit came from. |
referrer, landing_url | Where the visitor arrived from and the first page they saw. |
session_id | The DataCops session. Also used as the anonymous ID when there is no user ID. |
source | Always datacops, so you can tell these events apart. |
Sessions are sent in small batches every two minutes through the official Segment and Amplitude APIs. For Amplitude, DataCops sends to the EU or US data center, matching your project.
Using it in your reports
- Real visitors only: filter any chart or audience on
is_clean = true. - How much traffic is fake: compare
is_clean = trueandfalseby channel, country or landing page. - Which sources send bots: group flagged sessions by
referrerand readbot_reasons. - Clean funnels: join the verdict to your existing events through the same user ID, and exclude flagged users from funnel and retention charts.
Identity and consent
When a visitor has consented and has a user ID, the event is sent with that user ID, so it lines up with your other events for the same person. Otherwise it is sent with the DataCops session ID as the anonymous ID.
DataCops follows your consent setup. A visitor who declines is only counted as an anonymous session, with no user ID and no device fingerprint.
Setup
The DataCops team sets this up for you. There is nothing to build on your side.
Install DataCops
Add the DataCops script on your own subdomain, as in getting started, so sessions are being scored.
Share your keys
For Segment, a write key from the source you want the events in. For Amplitude, the project API key and whether the project is in the EU or US.
DataCops connects and tests
We connect the keys, then check with you that the first
DataCops Session Scoredevents arrive where you expect them.
Good to know
- Only new sessions are sent, starting from when the connection is made. Past sessions can be pulled through the export API.
- Segment accepts events even if a write key is wrong, so we always confirm the first events arrive before calling setup done.
- Every send is logged on our side, so a missing event can be traced.