Mixpanel

With Mixpanel on your site, every event the visitor sends carries da_class and the other da_* fields. You can filter any report to humans only, or see what agents do on your site. Nothing to add in code.

What Mixpanel gets

mixpanel.register({ da_class, da_agent, da_score, da_bucket, da_rec, da_verified, da_behavior, da_behavior_risk, da_authorization });
mixpanel.people.set({ /* the same fields */ });   // only after doubleagent.identify()

register makes them super properties, so every later event has them. The user profile gets them only when you call doubleagent.identify() for a signed-in user. Needs analytics consent. Field values: Verdict.

Use it

• Humans only: in any Insights or Funnels report, add the filter da_class equals human.
• What agents do: break down an event by da_agent, filtered to da_class equals agent.
• A cohort to exclude: create a cohort of users who did any event with da_class equals bot, and exclude it from

your dashboards.

Check it worked

Open your site, then in Mixpanel go to Events and open your latest event. Its properties should include da_class.

Fix labels after the page

When the server settles a different label for a session, it sends a da_final event through Mixpanel's /import API, joined on the visitor's distinct id. It sends one only when the class, behaviour label or authorization decision differs from what Mixpanel last got (the first time, from what the browser already sent), not on every check. Add your project token and API secret in Sites › your site › Settings › Server relabel credentials. See Relabel.

Next: Segment or How integrations work.