Didomi - Developers documentation
  • Introduction
  • SDKs
    • Introduction
    • Web SDK
      • Getting started
      • Tags and vendors management
        • Tags management
          • Events & Variables
            • Deprecated
            • Custom events
          • Tag managers
            • Adobe Launch/DTM
            • Eulerian
            • Google Tag Manager
              • Configure the Didomi / GTM integration
              • Didomi's GTM template
            • Tealium
            • Other tag managers
        • Custom Didomi <script> tags
        • Third-party integrations
          • Google Ad Manager / AdSense
            • GDPR via Non-Personalized Ads
              • Share consent and load/refresh ads
              • Share consent without loading or refreshing ads
            • US states laws
          • Google Consent Mode V2
          • Kameleoon
          • Piano Analytics (AT Internet)
          • Prebid
            • GDPR via IAB TCF
            • US states laws
          • Salesforce DMP (Krux)
        • IAB frameworks
        • Programmatic API
      • Configuration
        • Bots (SEO & Performance tools)
        • Configuration by URL
        • Cookies and storage
        • Custom domains for events
        • Notice
          • Behavior
          • Interactions
          • Look and feel
        • Preferences
        • Theme
      • AB tests
      • Custom domain
        • Domain delegation
        • Reverse proxy
      • Share consents between domains
      • Share consents across devices
      • Pass user choices in query string
      • Serve Didomi assets from your domain
      • Reference
        • API
          • Deprecated
        • Events
      • Performance
    • Mobile and TV SDKs
      • Android and Android TV
        • Setup
        • Logging
        • Reference
          • API
            • Deprecated
          • Events
        • Versions
      • iOS and tvOS
        • Setup
        • Logging
        • App Tracking Transparency (iOS 14.5+)
        • Reference
          • API
            • Deprecated
          • Events
        • Versions
      • Unity
        • Setup
        • Reference
        • Versions
        • Troubleshooting
      • React Native
        • Setup
        • Reference
          • Deprecated
        • Versions
      • Flutter
        • Setup
        • Reference
        • Versions
      • Consent notice
        • Getting started
        • Customize the notice
        • Customize the preferences popup
        • Customize the theme & UI
        • Load notice by ID
      • Third-party SDKs
      • Share consents across devices
      • Share consent with WebViews
      • Google Consent Mode v2
      • FAQ
    • AMP SDK
      • Blocking Behaviors
        • Load immediately on page load
        • Load only after consent (positive or negative)
        • Load only after positive consent
      • Consent status for vendors
    • Help & Support
  • API
    • Introduction
      • Authentication
      • Errors
      • Pagination
      • Filters
      • Caching
      • Rate limiting
      • Quotas
      • Translations
    • Data Manager
      • Regulations
      • Configuration Tree
      • Purposes
        • Purposes & Vendors Numerical IDs
      • Preferences Library
      • User Rights
    • Widgets
      • Consent notices
        • Notices
        • Configurations
        • Multi-Regulation Configurations
          • Migration of Existing Notices and API Updates
        • Deployments
        • Tutorials
          • Create and publish a consent notice
          • Create and publish a multi-regulation consent notice
      • Privacy widgets
        • Create a widget
        • Retrieve widgets
        • Edit a widget
          • Content & Design
            • Themes & Shapes
            • Components
              • auth
              • dsar_form
              • footer
              • header
              • preference
              • preference_value
              • save
              • section
              • sections
            • Options
          • Purposes & preferences
          • Settings
        • Deploy a Widget
          • Use your own subdomain
          • Use your own domain
          • Implement an embeddable widget on your website
        • Authentication
          • Manage authentication providers
          • Authenticate your end-user
        • Archive a widget
        • Headless widgets
          • Public Methods
          • Custom elements
          • Custom events
          • Event listeners
        • Tutorial
          • Launch a Preference Center from a mobile app
    • Compliance Reports
      • Properties
      • Reports
      • CSV format reference
      • Websites
    • Consents and Preferences
      • Events
        • Generate IAB TCF consent string
      • Links
      • Proofs
      • Tokens
      • Secrets
      • Users
      • Tutorial
        • Collect and operate data
    • Privacy Requests
      • Requests
      • Notes
      • Links
      • Emails
  • Integrations
    • Introduction
      • Quotas
    • Generic integrations
      • Batch export
        • Destinations
          • AWS S3 Bucket (owned by Didomi)
          • GCP Storage Bucket
        • Exported data
          • Notices consents
        • Logs
      • Webhooks
      • Batch import
      • Analytics export
        • Destinations
          • AWS S3 Bucket (owned by Didomi)
          • GCP Storage Bucket
    • Third-party apps
      • CMP integrations
        • Didomi-mParticle integration for your CMP
        • Deploy Didomi’s SDK for your Adobe Commerce website
      • Preference Management Platform integrations
        • Actito
        • Adobe Campaign Classic
        • Adobe Experience Cloud
        • Adobe Marketo Engage
        • Adobe Source Connector
        • Braze
        • Dotdigital
        • Hubspot
        • Mailchimp
        • Microsoft Dynamics 365
        • Salesforce Marketing Cloud
        • Salesforce Sales & Service Cloud
        • Selligent
        • Brevo (ex Sendinblue)
    • Tutorials
      • Configure a HTTP webhook
      • Configure a batch export
      • Configure an analytics export
    • Emailing
      • Configurations
        • Actito Email
        • Actito SMS
        • Adobe Campaign Classic
        • Adobe Campaign Standard
      • Emails
        • Templates
        • Manage your templates
Powered by GitBook
On this page
  • Introduction
  • Implementation
  • Connection
  • Options
  • Mapping
  • Configuration
  • Example
  1. Integrations
  2. Third-party apps
  3. Preference Management Platform integrations

Hubspot

PreviousDotdigitalNextMailchimp

Last updated 10 months ago

Introduction

Didomi allows you to synchronize your Hubspot contact properties with the preferences collected through Didomi consent events.

Implementation

Connection

Didomi connects to your Hubspot account through the Didomi Hubspot App. By installing the app and configuring the integration, you allow Didomi to update your Hubspot contact properties every time users change their preferences through the Didomi Platform.

Didomi Hubspot App

To get started using the Didomi Hubspot App, you can follow these steps:

  1. Go through the and grant access to the Didomi App on the Hubspot account you'd like to link with Didomi. This will grant access to Didomi to update your contacts as well as react to contact updates.

  2. After the installation, you'll be redirected to . The redirected link will contain a code parameter. This is the authorization_code to send as a configuration item on the following section.

The authorization_code expires within 1 hour. Please make sure of your Hubspot integration is done before the code expiration.

Options

Upsert mode

You can choose allowing Didomi to create contacts in Hubspot, by setting upsert_mode to true. Otherwise, when a consent is collected but the organization_user_id value does not match with any contact in Hubspot, the consent update will not be propagated to Hubspot.

Bidirectional flow

Didomi also supports a bidirectional flow by creating a Hubspot webhook to react to your contact changes and update your Didomi users accordingly. Didomi identifies your Hubspot contacts using the organization_user_id property.

Mapping

Didomi uses the entity contact of Hubspot and sends the attributes property when updating a contact. Hence consent events are mapped to the contact attributes.

Configuration

Didomi needs the following configuration items to set up the connection with Hubspot:

Property
Description
Required

Authorization code

Authorization code returned by the redirect URL after installing the Didomi Hubspot App

Yes

Portal ID

ID of your Hubspot portal

No (only required for bidirectional flow)

Mappings

List of contact properties to match between Didomi and Hubspot

Yes

Upsert mode

By setting upsert_mode to true you allow Didomi to create contacts in Hubspot

No Default value = false

Example

{
    "type_id": "hubspot",
    "authentication": {
        "code": "AUTH_CODE"
    },
    "properties": {},
    "mappings": [
        {
            "id": "hubspot_email_enabled",
            "value": "consents_preferences_newsletter_enabled"
        }
    ],
    "upsert_mode": true,
    "app_id": "YOUR_PORTAL_ID",
    "enable_webhooks": true
}

Didomi also creates a Didomi Changed property on your account that can be used on when you want to trigger an update from your Hubspot contact. For example, you can create a workflow that increments this property by 1 every time a contact update should be triggered on the Didomi Platform. This makes sure that your Didomi user is up to date with the changes performed by Hubspot.

The configuration of the Hubspot integration can be done in the . First please reach out to to get the integration's premium feature activated.

Learn how to configure Didomi-Hubspot integration in the Didomi Console .

Workflows
Didomi Console
support@didomi.io
in this help center documentation
Installation link
https://didomi.io
the configuration