HomeDev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunitySubmit a ticketLog In
GitHubNuGetDev CommunitySubmit a ticket

Connect for HubSpot

The Optimizely Connect for HubSpot add-on is part of Optimizely Connect for Marketing Automation, which connects HubSpot with Optimizely Forms, letting marketers collect visitor data, and pass that on to be used with HubSpot.


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


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


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 need to 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 an SHA256-computer hash based on the value of the key)
  • machineKey of the server in web.config.



For DXP instances, use MAICryptoKey.

If you choose to use machineKey configuration, you should specify a machineKey in the web.config of your site so that when you deploy it to a different server, the same machine key is used on the new server.



If you neglect to specify a machineKey in the web.config, the credentials are removed when the site on the new server is accessed for the first time, in which case you need to 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.

Similarly, if the encryption uses MAICryptoKey first and then you decide to use machineKey encryption (by deleting the MAICryptoKey setting), then the credentials are deleted and must be re-entered.

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