01
Customer identity stays customer-owned
Only conversions carrying your external ID qualify for HubSpot. Nimriz never substitutes an internal account, touch, card, or user identifier.
CRM and lifecycle
LiveSend identified conversions to HubSpot
Turn attributed Nimriz outcomes into HubSpot custom event occurrences matched through the customer identifier your CRM already owns.
- Identified conversions
- Conversion value and currency
- Campaign context
Event flow
Async deliveryConversion APIAttributed conversionHubSpot custom event
Nimrizredact · filter · map
HubSpot
Bot traffic is excluded by default. Delivery runs off the redirect path with automatic retries.
Why HubSpot with Nimriz
Connect campaign outcomes to the CRM record your team already recognizes. Nimriz sends a defined HubSpot event only when your backend supplied the external customer identifier required by the matching rule.
02
Conversion context without anonymous activity
Send conversion type, value, currency, campaign context, and mapped properties without forwarding clicks, scans, raw IP, or complete User-Agent strings.
03
Verified before delivery starts
A real provider test confirms the current HubSpot configuration before live conversion delivery can be enabled.
Conversion bridge
From click to attributed conversion.
Conversions carry type, value, and currency, with deduplication through stable event identifiers and idempotency keys. Refunds, cancellations, and reversals reference the original sale instead of overwriting it.
- 01
Your backend reports a conversion
The signed Conversion API request includes a customer-supplied external ID and the outcome details you want to track.
- 02
Nimriz resolves attribution
The conversion joins its eligible link touch and keeps the customer identifier outside the canonical integration event.
- 03
Destination rules are applied
Filters and mapping shape the conversion while privacy rules remove identifiers that the destination does not need.
- 04
HubSpot receives the identified event
Delivery runs asynchronously with safe retries, stable identifiers, and customer-safe delivery health.
Under the hood
What Nimriz sends, and how.
Send managed-OAuth custom behavioral events using a fully qualified event name and configured matching property.
Plan note
HubSpot CRM sync is available on Professional and Enterprise plans.
- Authorization
- Managed OAuth with analytics.behavioral_events.send
- Event
- Fully qualified HubSpot custom behavioral event
- Identity
- Customer external ID in the configured event matching property
- Validation
- Healthy authorization plus a real event occurrence test
Guided setup
Connected in four reviewed steps.
- 01
Define the event
Create a HubSpot custom event and custom matching ID property.
- 02
Connect HubSpot
Authorize the account that owns the event definition.
- 03
Send a test event
Use a temporary sample external ID to create a real occurrence.
- 04
Enable delivery
Enable after authorization and the current event configuration pass.
Use cases
- CRM activity context
- Revenue outcome tracking
- Lifecycle qualification
Privacy notes
Privacy-aware delivery uses only the customer-supplied external ID for matching and omits anonymous activity, internal subject IDs, visitor hashes, raw IP, and complete User-Agent strings.
Nimriz never forwards raw IP addresses or complete User-Agent strings in integration payloads. Strict privacy mode omits visitor hashes and selected granular fields such as city.
Analytics privacy docsMore in CRM and lifecycle
Pair HubSpot with the rest of the catalog.
Live
Customer.io
Turn attributed link outcomes into Customer.io customer events using the external identifier your lifecycle programs already recognize.
Live
Klaviyo
Turn attributed link outcomes into Klaviyo profile events using the external identifier and metric your lifecycle flows expect.
Beta
Pipedrive
Create completed activities on exactly matched Pipedrive People.
Beta
Attio
Attach conversion notes to exactly matched existing Attio records.