As a part of Bizible’s integration with Drift, we’ve outlined some of the most frequently asked questions. If there are any questions not outlined below, please reach out to your Customer Success Manager or email@example.com.
How is the integration enabled?
For those using Google Tag Manager to load the Bizible Script, if you want to exclude your Drift Chats from being Touchpoint-eligible, you’ll need to add to following
<span> right after your Bizible Script:
<span id="bizible-settings" data-chatEnabled="false"></span>
What does the integration do?
The integration now allows Bizible to track when an end-user provides their email address in a Drift chat. From there we create touchpoints from these interactions with a Touchpoint Type of “Web Chat.” This integration allows marketers to understand the performance of their chat interactions, along with the channels/sub-channels/campaigns that drive people to interact with these chats.
What if I track Drift via campaign sync rules?
If there are any campaign sync rules in place to create touchpoints for Drift chat interactions, you’ll need to ensure you stop adding those particular end-users into the corresponding CRM Campaign. Otherwise once the feature bit is enabled we will create a CRM Campaign touchpoint and digital touchpoint for one Drift chat interaction.
What if I track Drift via CRM Campaigns?
If there are CRM campaigns in place to create touchpoints for Drift chat interactions, a Touchpoint End Date will need to be set on those specific campaigns (the Touchpoint End Date should be the date the Web Chat Integration feature bit is enabled).
What if I track Drift via Activities?
If there are activity rules in place to create touchpoints for Drift chat interactions, an additional piece of logic will need to be added to the rules. You’ll need to add logic using the Task Created Date field to prevent duplication of touchpoints from being created (IE CrmTask.CreatedDate is Less Than the date in which the feature bit was enabled). See screenshot below for example.