The visual builder is a great tool to help you map out and plan the logical flow of your Playbook, but we know that it's important to test your Playbooks before you deploy them on your site!
Two features within Drift lend themselves perfectly to testing Bot Playbooks - DriftLinks and Conversational Landing Pages (CLPs).
This document will cover
- Getting Started: Building something to Test
- Testing with DriftLinks
- Testing with Conversational Landing Pages
- Testing with Integrations
At a glance, use
- DriftLinks if you want to see how your Playbook will look within the context of your website
- Conversational Landing Pages (CLPs) if you want to focus on the flow of your Playbook.
Note: Testing won't influence any metrics that show up in your playbook reporting or Conversation analysis. So feel free to test as often as you'd like!
Plan availability:Bot Playbooks, DriftLinks, and Landing Pages are available on the Premium plan and above.
You have to build a Playbook before you can test one!
- Log into Drift and navigate to your Playbooks tab within the app
- Click the green "Create new Playbook" button on the top right corner
- Choose a Playbook type and hit the blue "Create my Playbook" button after naming your Playbook.
- Customize the Playbook's messages, questions, CTAs, etc..
Need some inspiration? Check out some live examples from our customers!
If you're looking for more clarification on how to build bot Playbooks, click here!
Now, onto the testing!
The easiest way to test a playbook is to utilize the Preview bot flow button on the Playbook Editor.
The Preview bot flow button will allow you to view your playbook on a URL as if it were live! However there are a few things to make note of if you find that your test link isn't working:
- Make sure Drift is installed on the site you are testing on or else the bot won’t fire.
- If you notice no URL is in the dropdown to test, add a quick "URL is [insert url here]" targeting condition and publish. This will then generate your test link! After you are done testing, you can remove this condition and publish again.
- Sometime test links are dead and will not work at first. If you add "www." to the beginning of the test link and hit enter again the link should work!
Please make sure that you follow these instructions closely to avoid rolling out Playbooks to your customers before they're ready!
If you are testing your playbook using the "Test" button on your flow builder page (shown above), it is important to note that the following skills will not happen in your test conversation for the following reasons:
- Email Capture and Phone Capture - These skills will not fire if Drift already has this information. To test it as a new site visitor, you can open the test link in a new incognito browser window, and the skills should fire.
- Book A Meeting - The user's calendar will not be dropped in the conversation. This is expected test link behavior.
- Team Availability - This bot skill will not happen even if you, as the tester, are waiting for a response. This is expected behavior.
These playbook features will fire as expected when the playbook is live on your site. If you are experiencing issues with this, please chat in to our Support Team with the URL link to the conversation.
Alternatively, you can test using DriftLinks
DriftLinks can be thought of as unique IDs for a Playbook preceded by a hashtag. When you append these to the end of a URL on your site domain, they trigger your widget to open a conversation from that specific Playbook.
DriftLinks are great for
- visualizing how the widget will open the conversation sidebar after a visitor actively clicks and engages with a bot greeting and question
- checking whether the chat is blocking any important content on your website
- essentially getting the "true" end user experience
OK, but how does this really work?
The DriftLink tab
Once you've built your Playbook, click on DriftLink along the top navigation bar. Make sure to check the box next to"Only fire when #DriftLink is present" toggle first, to ensure your Playbook does not show up on your website to everyone! Choose a unique DriftLink to use for this Playbook.
Using a DriftLink will override any and all targeting conditions you've set up within the "Audience" tab.
Testing with Conversational Landing Pages
This method of testing bot playbooks will only work for bot playbooks built before 2020. Landing page playbooks are now their own type of playbook!
Like DriftLinks, Conversational Landing Pages (CLPs) have specific URL triggers which are simple to fire and safe for testing when you're not ready to go live yet.
CLPs are focused landing pages that are meant to drive conversations with Leads who are interested in completing a single Call To Action, whether that be a webinar sign up, event registration, demo request, or content download. Because of this simple and focused format, Conversational Landing Pages are also ideal for testing.
Specifically, CLPs are great for
- testing without installing any code!
- stripping down the bot to just the messaging
- letting yourself focus on surfacing typos, awkward transitions between messages, and logical flow of the conversation itself
- not just testing! As stated before, a lot of customers use CLPs as actual branded landing pages for certain events and campaigns targeted at a specific customer base, where they really want a full-screen takeover to engage their leads.
OK, but how does this look?
Click Turn on to enable the landing page from any existing Bot Playbook you have.
If you see a "Test" tab instead of "Landing Page", your Playbook was created after we made Landing Pages their own Playbook type. The "Test" tab works in the same way!
For a more exhaustive doc on Conversational Landing Pages using the features and customization listed in the image below, check out this article!
Testing with Integrations
The following pieces of data will not sync to an outside MAP or CRM integration while testing your bot playbooks:
- Salesforce - Meeting booked with Drift events
- Salesforce - Drift Conversation Custom Object records
Our team is working on bringing better testing environments to Drift. If you have any concerns, please chat in to us and let us know!