All Collections
Leads
Publishing MetaLocator leads to HubSpot
Publishing MetaLocator leads to HubSpot

When users submit leads, MetaLocator can publish the lead data directly to a HubSpot form

Michael Fatica avatar
Written by Michael Fatica
Updated over a week ago

Lead data captured in MetaLocator are saved in the control panel under Leads as shown below:

Leads can also be published to external email addresses, SalesForce and HubSpot.  This article discusses the HubSpot integration.

To enable HubSpot integration, update the following options under Lead Generation tab at the top of the Interface builder:

  1. Enable HubSpot integration:  This enables the publishing of lead data to HubSpot.  Set this to Yes to use this feature.

  2. HubSpot Hub/Portal ID:  This is the Hubspot-provided portal ID of your Hubspot account.   This is shown as described here.

  3. HubSpot Form ID:  This is the Hubspot-provided Form ID of your Hubspot Form.   This is shown as described here.

  4. HubSpot URL Template: This is the URL that is used to submit the lead data to HubSpot.  This provides the opportunity to specify how MetaLocator lead fields map to HubSpotfields.  The format of this URL is described here.  MetaLocator automatically includes the HubSpotcookie and the visitor's IP address.  The values in curly braces are replaced with the lead form values.  

The possible values for the URL Template correspond to the lead fields. This syntax is different than MetaLocator email and Twig templates.

{name}      This is the lead's name    
{from} This is the lead's email
{to} The email address of the lead recipient
{message} The contents of the comments field.
{cc} Any email addresses CC'd
{received} The date received. E.g. 2021-02-19 18:54:16
{custom1} Contents of any custom fields 1-40
{custom2}
{custom3} If provided, this will be set to the Hubspot pageUrl
{custom4} If provided, this will be set to the Hubspot pageName
{custom5}
{custom6}
{custom7}
{custom8}
{custom9}
{custom10}
{custom11}
{custom12}
{custom13}
{custom14}
{custom15}
{custom16}
{custom17}
{custom18}
{custom19}
{custom20}
{custom21}
{custom22}
{custom23}
{custom24}
{custom25}
{custom26}
{custom27}
{custom28}
{custom29}
{custom30}
{custom31}
{custom32}
{custom33}
{custom34}
{custom35}
{custom36}
{custom37}
{custom38}
{custom39}
{custom40}
{location_id} 1 The numeric ID of the target location
{item_id} 11111 The numeric ID of the Interface which initiated the lead

Did this answer your question?