Drip allows you to store participant data and manage communication across various channels like Email and SMS. By using the built-in integration with Playable, you can automate the data transfer between the two platforms.
In this article, we'll explore the process of configuring the Drip integration in the platform. We will cover how to:
Add the Drip Integration
To find the integration, go into the 'Integrations' tab on your campaign and select 'Add Integration'. In the following menu, select 'Email Provider' and scroll through the list till you find the Drip option. Clicking it will start the setup process.
Drip connects to Playable through an Account ID and API token. This means that, if you are adding the integration for the first time, you will need to insert this information from your Drip account.
If you have previously set up a Drip integration in Playable, you can reuse the configuration.
If you require further assistance in finding your API key, you can check out Drip's own documentation.
Configure the Drip Integration
Once your Account ID and API token has been added you can start configuring what data should be sent from Playable to Drip. The first section is 'General integration settings'. Here, you can define what to do with duplicates, exactly which registrations to transfer and how many lists you want to update in Drip.
Select trigger
The trigger is the event that determines when data should be sent through the integration.
Trigger Name | Event |
Primary registration form submitted | Data sent when the primary form with the email field is submitted. |
Game completed | Data sent after the game status is known, provided the form was submitted. |
Prize won | Data sent when a regular prize winner is assigned. |
Bulk prize won | Data sent when a bulk prize winner is assigned. |
The availability of triggers depends on the placement of your registration form(s) and the inclusion of prizes.
Add additional conditions
It is possible to add additional conditions to the trigger. Together with the trigger, these must be met in order for the data to be transferred.
Using the form field option you can define a specific field in the registration form(s) that must be filled out.
With the advanced option you have the option to set up a data flow based on more complex conditions. For example, the trigger could be based on performance in the game or a specific selection or data input in the registration form.
Map data fields
You will "map" each field from your campaign to a field in Drip using drop-down menus. This drop-down is how you select where in Drip the data should be sent.
β
For each datapoint you can select an existing field from Drip to parse the data to. If the field does not exist in Drip, you will not be able to push data to it. Therefore, you may have to add more fields to your list in Drip, before you're able to setup the integration fully.
β
For help on how to add extra fields in Drip, you can check out Drip's own documentation.
At the bottom of this section, you can add static information if you want to track something that is true for every player but is not collected in the campaign automatically.
For example, you can use static information if you want to track Playable as the user "source" in your database.
Once you enter a static value, you can map the field as you would with any other data field.
Test and troubleshoot the integration
We always advise that you test the integration by going through the actual campaign. The testing process will depend on what your triggers are, but we suggest that you test by submitting the registration form(s) and play through the game.
In the activity tab, you will be able to check if the data has successfully been transferred to Drip. To learn more about how to test the integration, please read this Help Center article.
You can also find more information about troubleshooting integrations.