Emarsys Integration

Owned by Graham Ralls (Unlicensed)
Last updated: May 16, 2024
5 min read

Introduction

preezie integrates directly with the Emarsys APIs to automatically pass all of your preezie lead form information to your Emarsys account. This allows you to store and send preezie shoppers their product recommendations via email and add them to any marketing flows you have.

There are three types of data available to send to Emarsys,

  1. (default) Pass Contact data only when submitting a journey lead form

  2. Pass Contact and Product recommendations data when submitting a journey lead form, this requires an external event set up in your Emarsys account

  3. (requires add-on) You can also use a hosted Emarsys relational database table to pass the questions & answer data in realtime

First, add your journey lead forms

The first step is to ensure you are capturing lead information at the end of your preezie journeys. If you haven’t already done this, see the Email Capture guide for more information. These are managed in your Journey Settings under the Signup Lead Form tab:

image-20240423-044648.png

Fields that can be passed to Emarsys are First name, Last name, Phone, and Email address:

image-20240423-045054.png

Contact and Recommendations data

1. Connect your Emarsys account to preezie

First, connect your Emarsys account to preezie.

  • If you only want to capture Contact data, change Data type to Contact data, you can ignore the Optional endpoint URL step below

    • If you want to capture Contact AND product recommendations data, change Data type to All data

  • In the Create Contact Endpoint Url paste this value:

2. Create an External Event for your Product Recommendations

This step is optional, if you purely want to store Contacts only jump to step 2 below and ignore the use of the Optional endpoint URL field

To store the production recommendations data you need to create an external event.

  • Management > External Events > Create External Event

  • Give it a name of preezie recommendations

This gives you an ID that we’ll use in the next step.

Events:: External events In the Optional endpoint URL field paste this, but update the number 1234 to your External Event ID created above:

Make sure Data type is set to All data.

Check Active then Save Emarsys API integration.

3. Add a List ID (optional)

If you want your leads to go into a specific List, add the List ID into the List ID (Optional) field

Check Active then Save Emarsys API integration.

4. Testing your set up

Once active you can test your integration by using the Preview in the Journey edit menu:

Complete your journey and submit the email capture form at the end, you should now be able to see your email within your Emarsys account and attached to your list (if applicable):

The product recommendations data will be available to use within your email templates, please speak to your Emarsys CSM for any help with that. The product fields available are:

    "name": test@preezie.com ,
    "productUniqueID": "<unique product id from preezie db>",
    "productLink": "<full product url from preezie db>",
    "productName": "<product name from preezie db>",
    "productImage": "<full url of image from preezie db>",
    "productPrice": "35.00",
    "scorePercentage": "<product match relevance score>",
    "rank": "1",
    "submit time": "2024-02-03 14:52:12",
    "session ID": "3295932085"

Passing question and answer data

To store the question and answer data in realtime against your Contacts, you can use an Emarsys Relational Database. Please contact your Emarsys CSM to discuss this set up:

https://help.emarsys.com/hc/en-us/articles/360002165413-Overview-Relational-Data-Overview

The fields passed in this API call are:

Field name

Format

Example

Field name

Format

Example

email

varchar (255)

test@preezie.com

page

int (11)

1 (this is the question number that was answered)

question

text

What is your budget?

answer

text

Over $500

category

varchar (255)

TV finder (this is the journey name)

submit_time

datetime

2023-05-03 14:52:12

session_id

varchar (255)

c6c2ab7d-10c8-47c1-b3db (this is the user’s journey session ID)

question_id

int (11)

1 (also the question number that was answered)

Once this has been set up you must add your custom RDS API url to the Custom Database Endpoint Urlfield field in the preezie CMS:

FAQs

I cannot see my test emails within Emarsys?

First double-check your integration values are correct within the Emarsys Integration tab in the preezie CMS. Then ensure you are testing with a new email address (Emarsys can reject already captured emails) and one that has any spam traits (preezie checks for obviously fake emails), if you want to turn off this filter for testing go to Settings > Tenant settings > General and check Opt-out of email filtering. This will bypass any quality filters:

Finally, the ‘Timeout…’ setting in Workflow edit means any repeat emails through preezie will not be sent to any email integration until this delay in hours has passed . You can set this to 0 to allow all duplicate emails to be sent immediately:

Can I use the q&a data if I don’t have a hosted Emarsys table?

Yes, you can always access what the lead answered from the preezie CMS, via 2 reports:

Â