HubSpot
Events enter as HubSpot custom behavioral events, matched to the contact by email. The event name is your account's internal name (pe…_) — you define it there, map it here, and the contact carries the behavior.
Data delivered
Data delivered
- Custom behavioral events tied to contacts by email
- Event properties in the account format
- Real timestamps and unique id
What it is for
What you can do with it
- See on the contact card what the person did on site and checkout
- Trigger HubSpot workflows on real behavior
Why integrate
The business reason, not just the tech
Sales sees what marketing knows
The HubSpot contact gets the real timeline: visited pricing, abandoned checkout, purchased. The rep opens the card and understands the moment — without asking for a report.
Workflows with real triggers
Fire workflows on behavior that happened on the site and checkout, not just form fields.
Matched by email, no duplicate contacts
Events enter via the graph email and land on the existing contact — no orphan contacts born.
How to connect
Step by step
- Step 1
Create the behavioral event in HubSpot and copy the internal name (pe…).
- Step 2
Create a private app with the event-send scope and copy the token.
- Step 3
Create the destination and a Delivery mapping your event to the internal name.
Frequently asked questions
Why does the event name look like pe12345_?
It is the internal name HubSpot generates when you create the event in your account. Delivery must use exactly that name — the Delivery mapping does the translation.
Start measuring what actually becomes revenue
Create a free account, connect your first source and see your first lead timeline today. No card required.