Plainflow Onboarding Checklist
In creating this checklist, we tried to rewind the tape to anticipate every question that you could have during the onboarding process.
Everything that lives in the table below is a task. For each of those tasks, you will have a reference link on this page and in other relevant sections of the documentation which will guide you through each step.
We are here to answer all your questions. Simply click that blue chat widget below 👇 to communicate with us. Whether it’s a migration issue, an unclear element in our documentation, or if you have a specific use case in mind, just reach out and we’ll reply as soon as possible.
Whether it’s a migrations issue, an unclear spot in our documentation or a question about a real case scenario that you are wondering if it could be easily implemented in Plainflow, just reach us out and we’ll reply you as soon as we can.
Let’s get started 👇
|Task name||Help Doc||Use cases|
|➡ Install the client JS||Link|
|➡ Install the SDK serverside||Link|
|➡ Configure your Email settings account||Link||See the use case|
|➡ Configure your Clearbit integration||Link||See the use case|
|➡ Configure your MadKudu integration||Link||See the use case|
|➡ Get inspired with new ideas from our recipes||Link|
|➡ Configure your default segments||Link|
|➡ Activate your first workflow||Link|
|➡ Import your old customer data||Link|
Installing plainflow.js on your product
It only takes a few minutes to install Plainflow on your website. Once installed, you’ll be able to send clickstream data to Plainflow.
(Here’s a detailed technical guide on how Plainflow.js works)
To install the library, just paste the following code into the
<head> section of your website.
Remember to replace
YOUR_PLAINFLOW_PUBLIC_KEY with your Plainflow Public Key, which you can find under API Keys
Once you have sent us your event clickstream data, you will be able to track customer data from your website and use that data to segment your users based on events they have or have not performed.
Done? Not yet!
Installing the plainflow SDK
You also need to send us your server-side events. Our server-side libraries let you send analytics data directly from your servers.
Choose one of the languages that we support:
If you are a developer, click on the help link of the SDK to learn how to get started. If you’re not a developer, just send the link of this page to your dev team.
Configure your Clearbit integration
If you are already using Clearbit in your stack, you’ll be able integrate in seconds. Just head to the Clearbit integration in the integrations area, and a new window will ask for your credentials. Click
authorize access to complete the process.
Configure your MadKudu integration
If you are already using MadKudu in your stack, you’ll be able integrate in seconds. Just head to the integration area, head to your MadKudu account, and click on API. Copy and paste your secret API key in the Plainflow text input and you’re done.
Get inspired with new ideas from our recipes
If you’re wondering what exactly Plainflow does that others just can’t, this your go-to section.
Are you looking for new ways to surprise your users in the onboarding process? Would you like be more relevant to your users? How can your touchpoints be more smooth?
As product managers and marketers, these are questions we ask ourself often, and sometimes we only need ideas.
If you have a use case in mind that is not currently listed in our recipes, just send us an email or write in the Drift livechat below to share your questions or ideas. 😍
Configure default segments
When you’re just getting started in a new Plainflow account, you will notice that some segments are already available.
Plainflow offers one default segment:
- Active users should include all the users that you consider Active Users.
Fill out the conditions to detail your definition of
If you have any questions while working with the segment editor, this is a relevant resource.
Activate your first workflow
Activating your first workflow is something special! Before performing any customer facing actions, we recommend that you first test it in house.
We recommend you to start creating a workflow that will not impact your users but could help you understand how the system works.
Import your old customer data
Importing your historical customer data is not mandatory to start using Plainflow. However, doing so will allow you to use Plainflow at its full potential.
Once you’ve had a chance to see Plainflow at work, you might want to back-fill your historical data. Here are a couple of options.
If you’re a developer, you may want to write a quick script to loop through all of the people in your database and add them to Plainflow. While this creates a lot of API requests, it won’t overload our system if you follow the API guidelines.
Choose a library for your language of choice.
Not using Plainflow yet? Get your free account here. 👈