Iterable Integration

Iterable is a cross-channel marketing platform that powers unified customer experiences. It allows you to create complex distribution scenarios targeting your customers with personalized messages.

Voucherify can boost customer experience by adding a voucher with a unique coupon code to each message sent to a customer. This voucher can encourage the customer to make a purchase or distribute referral codes to referrers.

You can use Voucherify’s Publication request as a data feed in Iterable to track customers who received the voucher from you. You can use this action to start the validity period of the voucher or specify that only the voucher holders can use it.

In this article, you will learn how to configure the integration between Voucherify and Iterable.

The integration with Iterable uses API limits for Data Feed.

Contents

1. Configuration
2. Iterable templates with a data feed

Configuration

Voucherify offers different API requests that can be integrated with tools that understand REST APIs. Iterable works similarly: you can add the APIs as data feeds and use the feeds in a template. The data feeds must use Voucherify’s API keys for Iterable.

To generate the keys, go to the Project Settings. In the General tab, scroll down to Integration Keys and create a new integration API key for Iterable. In the Name field, enter the name for your key. In the drop-down lists, select User in Role and Iterable in Integration.

Once the API keys are generated, you can create data feeds in Iterable. Go to your Iterable account and select Content > Data feeds.

Select the CREATE NEW FEED button in the upper right part of the screen to create a new data feed.

The data feed will use Voucherify’s publication mechanisms that assign a voucher to a customer. To add this mechanism to Iterable send-outs, you need to combine:

• Voucherify’s publication endpoint URL,
• The application keys,
• A parameter that identifies the customer in Iterable,
• The Voucherify campaign that is the source of the vouchers.

To find your API endpoint in Voucherify, go to Project settings > General tab and scroll down to Application Information > API endpoint.

The structure of your API endpoint should look as follows:

YOUR API ENDPOINT/v1/publications/create

Use the table below to find your endpoint for publications.

https://api.voucherify.io/v1/publications/create
			

https://us1.api.voucherify.io/v1/publications/create
			

https://as1.api.voucherify.io/v1/publications/create
			

The API URL must contain not only the customer’s ID as a parameter but also the name of the campaign. In this section, you will see how to receive a voucher from the Welcome Codes campaign.

Here is an example of a URL:

https://api.voucherify.io/v1/publications/create?customer[source_id]={{#urlEncode}}{{source_id}}{{/urlEncode}}&campaign[name]=Welcome Codes

Each data feed has to be connected to a separate campaign.

You need to input the data accordingly as in the example:

Once the data feed is saved, you can use it in the templates.

Iterable templates with a data feed

When creating a new template, select Data feeds to find the data feed you have just created. If you want to use multiple data feeds, you can use aliases for your convenience to distinguish between them.

The data feed will trigger the API request every time you send a message to a customer. You can show the end result in the message by providing the voucher code from the data  feed. Since the goal is to show the voucher code to the customer and the alias is defined, add the following value to the message:

[[welcome_codes.voucher.code]]

The API requests return the complete definition of the coupon code, so if you have added any kind of information to the metadata, it can also be shown in the same way: 

[[welcome_codes.voucher.metadata.marketing_text]]

This is an example of a message to be sent:

As a result, the data feed will contain the information about the voucher, which has been assigned to the customer, including the voucher code and the marketing text.

In the image below, you can see how data is fed to the message: