Both email provider and storage integrations can automatically transfer player data to your own system so you don't have to manually export it from your campaign.
These two types of integrations have similarities and differences. To learn more about the differences between them, read this Help Center article.
In this article, you will learn about:
Which email provider and storage integrations Playable provides
The common steps you need to take to set up these integrations
What email provider and storage integrations are available?
Email provider integrations transfer data from Playable to your own CRM (Customer Relationship Management) or ESP (Email Service Provider).
We have pre-built API integrations with many of these services, including Agillic, Mailchimp, APSIS One, HubSpot and Salesforce.
If you do not use a CRM or ESP, you can use storage integrations to export player data to cloud storage providers. The are currently five storage integrations available: FTP/SFTP, Google Bucket, Google Sheet, Dropbox, and S3 Bucket.
You can also use a webhook to transfer data out of your campaign automatically, but this integration works slightly differently. Read more here about how to set up a webhook.
Setting up email provider & storage integrations
The process for setting up these integrations varies slightly depending on which CRM, ESP or cloud storage provider you are using.
However, there are some steps that are common to all of them. Typically, you will need to go through the following steps:
Grant Playable access to your system
Select an event that will trigger the data transfer
Choose which data fields you want to export
(optional) Add extra "static" information
Test the integration before going live with your campaign
Step 1: Connect Playable to your system
The first step you will take is to grant Playable access to the CRM, ESP or cloud storage provider you are using.
To do that, you typically need to insert authentication details from your system into the Playable integration settings. This is often an API key or a a Client ID and secret, but could be something else.
For example, to connect to Google Sheet (a storage integration), you will insert a link to the spreadsheet and also "share" the spreadsheet with the email generated by Playable.
Step 2: Set the integration's trigger event
Before you can edit the integration's settings, you need to decide which event will trigger the integration. This event is what needs to happen before Playable tries to send information through the integration.
The default setup is to use form fields. You choose one field from the registration form, and if that field is filled in when the form is submitted, the integration will be triggered.
Typically, we recommend selecting the checkbox your players use to accept terms and conditions. That way, the integration will only send data to your system after players accept your terms and conditions.
An advanced event trigger should only be used if you want to filter which players' data is sent through the integration. For example, you might send data only for players who have a specific game outcome (metric data) or who selected a specific response in the registration form (form field data).
Step 3: Map the data fields
Most of email providers and storage integrations allow you to send data from the following parts of your campaign:
Form fields: any details players enter in the registration form
Campaign information: general data about the campaign and the participation (e.g. campaign name, device used, date and time of registration)
Game flow information: metric data and other information about the game play (e.g. quiz answers, time used)
Bulk prizes: information about the prize won by the player, such as the prize code or ESP value.
* You have to turn on game flow and bulk prize data mapping at the top of your integration settings before you can use them.
You will "map" each field from your campaign to a field in your own system using drop-down menus. This drop-down is where you select where in your CRM or ESP or storage solution the data should be sent.
For example, in the Google Sheet integration, you will match each field with a column in your spreadsheet.
Step 4: Add static information (optional)
You can add static information when 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.
Step 5: Test the integration
We recommend testing the integration before going live. You can test integrations without publishing the campaign.
To test that your campaign includes game data, campaign information, and static information, you should play the game via the demo URL and submit a registration in the frontend.
After you register, go to the campaign backend. Under the Activity tab, you can see a status under each registration confirming whether or not the data was successfully sent through the integration.
If the integration fails, you can troubleshooting by looking at the log file. To learn more about troubleshooting your integration read here.