Please note that this article refers to our Emarsys V2 integration. If you are using the Emarsys V1 integration, you can find the article for that here.
Emarsys allows you to store participant data and manage communication through channels such as email, SMS, and more. Through our built-in integration, you can automate the data transfer between Playable and Emarsys.
In this article, we'll explore the process of configuring the Emarsys integration in the platform. We will cover how to:
Add the Emarsys 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 until you find the Emarsys V2 option. Clicking it will start the setup process.
Emarsys connects to Playable through a Client ID and Client Secret. This means that, if you are adding the integration for the first time, you will need to insert this information from your Emarsys account.
If you have previously set up an Emarsys V2 integration in Playable, you can reuse the configuration.
You can create the API credentials in Emarsys by going to Management > Security settings > API credentials and clicking Create API credentials. The credentials should use OpenID (OAuth 2.0) for authentication in order to work with the Emarsys V2 integration. If you are using API credentials with WSSE authentication, you should use the Emarsys V1 integration instead.
You should ensure that the API user has the following permissions:
field.list
contactlist.list
externalevent.get
externalevent.trigger
contact.getdata
contact.create
contact.update
Further information on Emarsys API credentials can be found in their own documentation.
Configure the Emarsys integration
Once your Client ID and Client Secret have been added, you can start configuring what data should be sent from Playable to Emarsys. The first section is 'General integration settings.' Here, you can define what to do with duplicates by setting whether the user’s information should be updated or if a new contact should be created.
Select a Subscription list and set language for the fields
You will need to select which list within Emarsys the data should be sent to. This ensures that participant information is organized correctly and aligned with your existing workflows. Choose the appropriate list during the setup process to match the campaign’s goals.
If you need to create a new list, this can be done in Emarsys by going to Contacts > Contact Lists and clicking Create Contact List. For further information on creating contact lists in Emarsys, you can check out this guide.
Secondly you will need to select which language the fields within the campaign are to be read in.
Select Trigger
The trigger is the event that determines when data should be sent through the integration.
The triggers available depend on the placement of your registration form(s) and whether you have included prizes in the campaign.
Trigger Name | Event that Triggers Data Transfer |
Primary registration form submitted | Data is sent every time the primary registration form (containing the email field) is submitted |
Game completed | Data is sent as soon as the game status is known (winner or loser), only if the primary registration form has already been submitted. Note: this option is only available if registration form is placed BEFORE the game. |
Prize won | Data is sent when a regular prize has a winner assigned (whether or not the game has been completed) |
Bulk prize won | Data is sent when a bulk prize has a winner assigned (whether or not the game has been completed) |
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 Emarsys using drop-down menus. This drop-down is how you select where in Emarsys the data should be sent.
Generally, you should ensure to at least map e-mail as well as opt-in in order to allow e-mails to be sent from Emarsys.
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.
Trigger events
You can add events to trigger automations set up in Emarsys. You can choose to trigger this event based on certain conditions (such as having filled out a specific field in your registration form).
You can find your external events and create new ones in Emarsys by going to Management > External Events. If you need more information on external events in, you can find that in this guide.
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 playing through the game.
In the activity tab, you will be able to check if the data has successfully been transferred to Emarsys.
To learn more about how to test the integration, please read this Help Center article.
You can also find more information about troubleshooting integrations in our Help Center or Emarsys' own support resources.