Disclaimer: This website requires Please enable JavaScript in your browser settings for the best experience.

Dev GuideAPI ReferenceUser Guide
HomeDev GuideRecipesAPI Reference
Dev GuideAPI ReferenceUser GuideLegal TermsGitHubNuGetDev CommunityOptimizely AcademySubmit a ticketLog In
Dev Guide
Legal TermsGitHubNuGetDev CommunityOptimizely AcademySubmit a ticket

Connect for HubSpot

Connects HubSpot with Optimizely Forms, letting marketers collect visitor data, and pass that on to be used with HubSpot.

Suggest Edits

Prerequisites

An Optimizely Content Management System (CMS) installation with Optimizely Forms and the required Marketing Automation connector components. See Optimizely Connect for Marketing Automation.

Install

The Connect for HubSpot MA connector is installed through the NuGet package EPiServer.MarketingAutomationIntegration.HubSpot. See Add-ons platform compatibility for supported Optimizely versions.

Configure

To configure your Optimizely website to use HubSpot, you need a HubSpot license that provides you with a username, password, and company name. You also must configure the connection of form fields to HubSpot so that data from the specified fields can be sent to HubSpot.

These configurations are described in HubSpot connector in the Optimizely User Guide.

See also the documentation video: Personalization with HubSpot 

Encrypt credentials

Credentials are encrypted and saved based on one of the following options:

  • MAICryptoKey – AES encryption with a SHA256-computer hash based on the value of the key.
    This key should be specified at the root level of the appsettings.json file with any string as its value.
  • machineKey of the server.
    The machineKey encryption is used ONLY if MAICryptoKey is not specified. If you neglect to specify an MAICryptoKey in appsettings.json, the credentials are removed when the DXP instance is restarted
    because the machineKey is different and will fail to decrypt the credentials, so you must save credentials again through the configuration screen.

If the credentials are already encrypted using machineKey in an existing site, and the MAICryptoKey setting is added, then the credentials are deleted and must be re-entered.

📘

Note

The MAICryptoKey must be specified with the same value in ALL the DXP instances that are connected to the same database. If it is missing or the value is different in any of the instances, the credentials will be deleted and must be re-entered.

Related blog post: Creating multiple instances of the same connector by Jason Masterson.

Updated 11 months ago