HubSpot
Fidero writes your contacts to HubSpot through its Forms API, each mapped to your HubSpot contact properties and tied to the visitor's HubSpot cookie. The browser SDK loads HubSpot's tracking code so submissions resolve to the right contact.
| Channel | Browser + server |
| Consent category | essential |
| Deduplication | No event ID – HubSpot matches on the contact's email, so repeat submissions update one contact record rather than creating duplicates. |
| Identifiers | The contact's email (required), plus phone, first and last name, company, job title and city, the visitor's anonymous and known IDs, and the hubspotutk browser cookie with the client IP. Sent to HubSpot as-is, unhashed. |
What it delivers
- Contact records. Standard user traits – name, email, phone, company and job title – are written to HubSpot as contact properties through the Forms API
- Attribution and identity. The visitor's anonymous and known IDs and the
hubspotutkcookie are attached, so the contact ties back to its HubSpot record and its acquisition source - Native tracking. Where analytics consent allows, the browser SDK loads HubSpot's tracking script, so HubSpot's own page and session tracking runs alongside Fidero
What you provide
| Item | Detail |
|---|---|
| Portal ID | Your HubSpot account (hub) ID. |
| Private app access token | A HubSpot private-app access token authorised for the Forms API. |
That's everything. Mapping, formatting, hashing and deduplication are already built in – you switch the destination on by requesting it, and the flow is on the Destinations overview.
What's automatic
- Contact-property mapping. Standard traits are mapped to HubSpot's contact properties, and each event is routed to the HubSpot form you've nominated for it
- Identity stitching. The anonymous and known IDs and the
hubspotutkcookie are attached so submissions resolve to one HubSpot contact - Consent capture. Where configured, GDPR processing and communications consent are recorded on the submission through HubSpot's legal-consent options
Enrichment, consent enforcement, delivery monitoring and managed adapter updates apply to every third-party destination – what every destination receives covers the standard treatment.