HubSpot

With HubSpot tracking on your site, known contacts get da_class and the other da_* fields as contact properties. Use them to keep bot form fills out of your sales pipeline.

Set it up

HubSpot only stores properties that already exist, so create them first:

1. In HubSpot, click the settings icon, open Properties in the left menu, pick Contact properties and choose Create property.
2. Create these nine, with exactly these internal names. HubSpot makes the internal name from the label, so a label of da_class gives da_class. The internal name can't be changed later. Single-line text works for all of them:

The script then sends, on each new verdict:

_hsq.push(['identify', { da_class, da_agent, da_score, da_bucket, da_rec, da_verified, da_behavior, da_behavior_risk, da_authorization }]);

HubSpot holds an identify call in the tracker and sends it with its next page view or event. So the properties usually reach HubSpot on the visitor's next page, or at once if you also send the event below. HubSpot applies them only to a contact it already knows from the visitor's cookie, for example after a form submit. Needs analytics consent. Field values: Verdict.

Also send an event (optional)

To get a custom event as well, create one in HubSpot and pass its internal name. Custom events need a HubSpot Enterprise plan:

doubleagent.push('init', { integrations: { hubspot: { eventName: 'pe123456_da_classified' } } });

The event carries the nine fields as properties. Listing integrations runs only the tools you list, so add the others you use. See How integrations work.

Use it

Create an active segment (HubSpot's new name for an active list) of contacts where da_class is bot, and exclude it from workflows and lead scoring.

Check it worked

Submit a HubSpot form on your site with a test email. Open the contact in HubSpot: da_class should show human.

Next: Stripe or How integrations work.