Skip to main content
All CollectionsProduct GuidesIntegrationsEmarsys integration
Creating WhatsApp campaigns using Emarsys segments
Creating WhatsApp campaigns using Emarsys segments

This guide explains how to import contacts from a Emarsys segment into charles together with a field that can be used for segmenting the audience on charles.

Updated over a month ago

Before you begin:

High-level overview:

This guide explains how to import contacts from a Emarsys segment into charles together with a field that can be used for segmenting the audience on charles.

In the future, we'll also sync segments between Emarsys and charles so that you don't need to use a custom field.

Set up

For this example, let's assume you want to send a Christmas campaign.

On Emarsys

Determine the segment you want to use in charles

To be able to target, this campaign, we'll create a custom field, for example should_receive_wa_campaign

Create an Emarsys automation with the following nodes:

  • It triggers based on your segment, e..g Xmas campaign recipients

  • It uses the Set Value Node (Emarsys documentation) to set the value of should_receive_wa_campaign to "Yes".

On charles

Create the custom field by going to charles > settings > custom properties and add emarsys_should_receive_wa_campaign. Input type should be text.

Make sure the segment gets imported. Go to Settings > Integrations > Marketplace > Emarsys.

Make sure the custom field is imported by adding a field mapping as well.

Re-configure by clicking next till the end. The segment will be imported now.

You can see the import status by going to Audiences > Contact import.

Now, we can set up the campaign by creating a segment that refers to the custom property

The segment will be imported to charles every 12 hours.

To trigger an import manually, you can re-configure the integration from Settings > Integrations > Marketplace > Emarsys.

If you want to sync the custom field in near realtime, you can also set up an automation that triggers a charles flow and update the property using the Update Contact Node.

Did this answer your question?