Hubspot Integrations

Pre-quote Connections

The pre-quote connection pushes a contact entity into HubSpot on exit of the personal information page (generally, the second page of the funnel) or on the quote page (depending on your configuration – to change your configuration, please reach out to support).

 

The following data points are pushed:

• Email
• The Hubspot tracking cooking ID
• First Name
• Last Name
• Gender
• Phone number
• Postal code ('zip' in HubSpot)
• Province ('state' in HubSpot)
• Date of birth
• nude_source

 

The nude source property will be either “funnel lead – no quote” if the user has not reached the quote screen or “funnel lead” if they have.  

 

Additionally, you can pass the following parameters via query string and they will be pushed into the HubSpot contact:

• utm_source
• utm_campaign
• utm_medium
• utm_term
• utm_content
• gclid

 

Please note that all data is pushed in real time and is represents the last known state of the customer. If customer [email protected] gets a renters quote and makes it to the quote page, the source will be “funnel lead”. If the same email address, then goes to get a home quote and does not reach the quote screen it will be reset to “funnel lead – no quote”. It is recommended your workflows operate on a has ever been filter instead of a “is” filter.

 

Additionally, all identifiable information will represent the last known state of the customer. In the above example, if a name of ‘Sally Smith’ was used for the renters quote and ‘Joe Smith’ for the home quote the name will be updated to ‘Joe Smith’.

 

Quoting Connections

In addition to all the information in pre-quote, once the user reaches the quote screen the following data points will be populated:

• LatestRestoreUrl – this is the URL to restore the last quote by the given customer
• ReferralCode – the last referral code used during quoting if any
• ReferralCodeGroup - the last partner grouping using during quoting, if any (generally not used by anyone)
• LatestRestoredQuote - the last time the customer restored the quote from a quote restore email
• LatestEmailedQuote - the last time the customer intentionally emailed the quote to themselves by pressing the ‘email quote’ button. Note that all quotes are emailed automatically by the system as a drop off – those emails do not update this property

Policy Lifecycle Connections
The policy lifecycle connections are done using HubSpot lists.

Please note that Nude Solutions will not update the lifecycle_stage of the customer automatically. You can use a HubSpot automation to do this.

Policy Sold:

• The contact will be added to the Active_<policytype>_Policies list – IE Active_Home_Policies
• The MaxTermEndDate and MinTermStartDate will be updated. These dates represent the earliest and latest policy term start/end date the customer has. Remember there can be multiple policies!
   

Policy Cancelled:

• If this is the last active policy of that type, the customer is removed from the active list
• The MaxTermEndDate/MinTermStartDate properties will be updated. In the case of multiple policies this may not change!

 

Policy Changed:

• No change

 

Policy Renewed:

• MaxTermEnd/MinTermStartDate properties are updated

---

 

Google Tag Manager Integration

 

Google Tag Manager is fully supported by the Nude Solutions Platform. If you wish to use GTM, please pass your GTM Container ID to our relationships team and we will get it setup for you.

 

As the Nude Solutions platform is a single page react application fragment routing must be used. See this link for more information.

 

Additionally, the follow virtual page view events are raised by the platform:

 

• /<funnel>/quotewithemail – triggered when the customer leaves the personal information page. At this point the users email will also be pushed into the datalayer.
• /<funnel>/quotenocheckout – triggered when the customer reaches the quote page
• /<funnel>/quotewithcheckout – triggered when the customer reaches the payment page
• /<funnel>/purchasecomplete – triggered when the customer has completed their purchase. Note: Use this for all conversion tracking, otherwise a refresh of the registration page will cause duplicate sales to be logged.