Spotler (EN)

With the integration with Spotler you can synchronize your data between Squeezely and the Email Service Provider (ESP) Spotler. With this integration you can send audiences, profiles, triggers and product sets from Squeezely to Spotler.

Implementation

For implementing the Spotler integration:

https://squeezely.atlassian.net/wiki/spaces/SG/pages/2697789633

When the full integration is finished a one-time synchronization of all email addresses and consents will start between Spotler and Squeezely. Simultaneously the standard profile fields and the product catalog will be synchronized from Squeezely to Spotler.

The following data will be synchronized when the integration is complete:

Email addresses: new email addresses are send real-time from Squeezely to Spotler. When new email addresses are created in Spotler, they will be send daily to Squeezely (so there is some lag)
Consent: changes in consent will be send real-time form Squeezley to Spotler. When the consent status changes in Spotler, they will be send daily to Squeezely.

Note! Do not change the description of the Permissions ('Nieuwsbrief'). If it’s changed the consent will not be synchronized anymore.

Profile fields: with every API call the standard profile fields from Squeezely will be send and saved in Spotler. Squeezely has an hourly import to get the profile fields from Spotler. For a sync of (custom) profile fields between Squeezely and Spotler, please read:

https://squeezely.atlassian.net/wiki/spaces/SG/pages/2697789685

Product fields: the products and standard product fields are synced from Squeezely to Spotler with every product import. If you want to sync the custom product fields form Spotler, you can best read the following.

https://squeezely.atlassian.net/wiki/spaces/SG/pages/2697789737

Spotler Forms data: if you want to send your Spotler Forms data to Squeezely you can do this with the Spotler Forms Webhook:

The profile fields from Squeezely are saved by default in Spotler with the following mapping.

Squeezely profile field	Spotler field

Squeezely profile field	Spotler field
Birthdate	Date of birth
City	City
Customer Phase	Squeezely - Customer Phase
Email	Email Address
Fav. Category 1	Squeezely - Fav. Category 1
Fav. Category 2	Squeezely - Fav. Category 2
Fav. Category 3	Squeezely - Fav. Category 3
Favorite Brand	Squeezely - Favorite Brand
First Name	First Name
Gender	Gender
Last Name	Last Name
Last purchase date	Squeezely - Last purchase date
Last visit date	Squeezely - Last visit date
Phone	Phone
Postal Code	Postcode

The product fields from Squeezely are saved by default in Spotler with the following mapping.

Squeezely product field	Spotler field

Squeezely product field	Spotler field
SKU (with language code)	SKU
Name	Product name
Description	Description
Url	Link
Brand	Brand
Price (of Sale Price indien aanwezig)	Price
Language	Language

Audiences & Profiles

In the Audience Builder you can send Audiences to Spotler by adding Spotler as a Channel:

For the profiles that are added to the audience Squeezely sends two API calls to Spotler:

Contacts: with this API call the profile fields are send to Spotler and saved in contacts om Spotler. For saving custom profile fields, you need to map these first.

In Spotler the API call ‘Contacts’ is processed in ‘Contacts’:

Go to Lists > Contacts in Spotler
Search for the profile you synced, and click ‘View’

Look in ‘Personal Data' the synced data of this profile:

Dynamic lists: with this API call the audiences are send to Spotler.

In Spotler you can find the results of the API call ‘Dynamic lists’ in ‘Dynamic lists’:

Go in Spotler to Lists > Dynamic lists
Search for the audience and click on ‘View’

You’ll get an overview of the profiles that are added to the audience and some general information about the audience:

Note! When you delete an audience in Squeezely, it will remain in Spotler. This is by the design of Spotler. Automated deletion has no way to check if you are using the specific audience, which is why Spotler decided not to let Squeezely delete the audiences.

Triggers & Product sets

In the Journey Builder you can send triggers to Spotler with the email node:

In the email trigger you need to configure the next items:

Trigger: the campaign or automation that needs to be triggered
Products: the product set which will be sent with the trigger
Campaign Fields: if available, Squeezely will also send the campaign fields of the Journey entry event

It is possible to add extra personalization fields in the campaign message in Spotler. These will be filled by Squeezely in stead of Spotler. Spotler has called these fields ‘campaign fields’.

With the usage of Squeezely you can add the the fields of the journey entry event as campaign fields to Spotler. These are fields like;

visit_event
visit_url
visit_orderid
visit_email
visit_firstname
visit_lastname
visit_total_value
visit_value
visit_checkin_date
visit_checkout_date
visit_amount_nights
visit_custom_{...}

How do the campaign fields work?

In your message or template in Spotler you can add placeholders of the fields, so you can determine where and what information needs to be shown.

For example:

Order:

Order ID: [campaignfield:visit_orderid]
First name: [campaignfield:visit_firstname]
Shoe size: [campaignfield:visit_custom_shoesize]

An advantage of using the campaign fields is that you don’t save the data in the Spotler database. When you send the email the fields will be filled with the API data from the trigger form Squeezely. This will make sure you always have the last data for that campaign available and don’t overwrite previous data.

The placeholder names can be added to a message by adding [campaignfield:name], where ‘name’ is the name of the field.

Note: In a message you can add multiple campaign fields. There are three conditions:

The campaign field name needs to be unique
The campaign field name cannot have spaces
The campaign field name is case sensitive

The campaign is only visible in the Journey Builder when it is published in Spotler.

The default product sets of Squeezely, the language of the account determines the language for the product set in Spotler

The profiles that reach the email trigger in the journey and meet the set condition, will be send to Spotler with an API call:

Squeezely Trigger: with this API call a trigger for a Spotler campaign or automation is send for the profile with, if necessary, the configured product set.