Logo Help Portal
  • Başlarken

    Introduction

    • Onboarding overview
    • Project Initiation
    • Email compliance
    • Hesap Yönetimi

    Veri

    • Veri Alışverişi
    • Veri Uyumlamasına
    • Web data collection
    • Entegrasyonlar

    Channels

    • Email onboarding
    • Smart Insight
    • Predict
  • Eğitim Videoları

    Resources

    • Introduction
    • Online Self-learning
    • Onboarding Videoları

    Events

    • Instructor-led Training
    • Webinars
    • Seminars
    • Training Calendar
  • Kullanıcı Klavuzu

    Strateji

    • Kişiselleştirme
    • Otomasyon
    • Data Monitoring

    Channels

    • Email
    • Mobil Uygulamalar
    • Web
    • Ads
    • SMS

    Add-ons

    • Smart Insight
    • Predict
    • Incentive Recommendation
    • AIM
    • Relational Data
  • Destek Dokümanları
    Forrester Wave CCCM (Independent Platforms) Report Q4 2019

    Haberler

    • Emarsys Platformundaki Yenilikler
    • Updates from the CSA
    • Pilot özellikler
    • Verilerin Korunması ve GDPR Hakkında Makaleler

    Support

    • Nasıl yardım alabilirim?
    • Bir Kullanıcı Profilini Düzenleme
    • Preparing for Black Friday 2019
    • Black Friday 2019 - Best practices
  • |
  • Partners

    Enhance Partners

    • Getting Started as an Emarsys Partner
    • The Emarsys Integration Platform
    • Automation Center Integrations
  • Yazılımcılar
  • Sistem Durumu
Destek Hakkında
Türkçe Deutsch English Español Français Русский 简体中文 Test New Chat
Oturum aç
  • Veri Yönetimi
  • Open Data
  • 0 Veri Yönetimi Open Data

Bu bölümde:

  • Overview:: Open Data - Overview
  • End-user guides:: Open Data - End-user guide
  • End-user guides:: Open Data - Datasets
EDIT
Expand all

End-user guides:: Open Data - Datasets

Updated: 14 Kasım 2019 01:00
360000148313
End-user guides:: Open Data - Datasets

We may change the data structure by adding or removing table columns in Open Data at our own discretion. As these changes may break your exports and queries, we will always notify you in advance of such modifications, to give you time to update your configuration.

Please note, however, that Emarsys cannot be held responsible for any losses or damages resulting from such changes.

Contents

  • Email campaigns
  • Email campaigns v2
  • Email campaign category
  • Email sends
  • Email opens
  • Email clicks
  • Email bounces
  • Email cancels
  • Email complaints
  • Email unsubscribes
  • Push campaigns
  • Push sends
  • Push not sends
  • Push opens
  • Push custom events
  • Web session - categories
  • Web session - purchase
  • Web session - tags
  • Web session - views
  • Web sessions
  • SMS campaigns
  • SMS send reports
  • SMS sends
  • SMS unsubscribes

Email campaigns

This dataset contains all your email campaigns. By running a query, you can get information about all the campaigns that were created or modified in your account.

A campaign may have multiple versions depending on how many times you modified it.

This view contains data from August 1st, 2017 onwards.

Data Field Description Type
id The ID of the email campaign. integer
name The name of the email campaign. string
version_name The name of the campaign version. string
language The two-character language code. string
category_id The category ID. integer
parent_campaign_id The ID of the parent campaign. integer
type The email campaign type. Possible values are test, recurring, onevent, unknown and batch. string
sub_type The email campaign sub-type. Possible values are ab, multi_launch, external and unknown. string
program_id The ID of the Automation Center program, in which the campaign is used. integer
customer_id The unique ID of the account. integer
loaded_at Loading date to Data Platform (UTC). timestamp
event_time Campaign creation/modification time (UTC). timestamp

Email campaigns v2

This dataset contains all your email campaigns with a lot of additional information beyond the basic campaign data. By running a query, you can get information about all the campaigns that were created or modified in your account.

A campaign may have multiple versions depending on how many times you modified it.

This view contains data from August 1st, 2017 onwards.

Data Field Description Type
campaign_id The ID of the campaign. integer
origin_campaign_id The ID of the original version of the campaign if it has been modified. integer
is_recurring If it is a recurring campaign or not. boolean
name The name of the campaign. string
timezone The timezone of the campaign. string
version_name The name of the campaign version. string
language The two-character language code. string
program_id The ID of the Automation Center program, in which the campaign is used. integer
program_version_id The version of the Automation Center program, in which the campaign is used. integer
suite_type The type of the campaign. string
suite_event The sub-type of the campaign. string
campaign_type The campaign type. Possible values are test, batch and transactional. string
defined_type The combination of suite_type, suite_event and campaign_type. string
category_name The category you defined. string
event_time Campaign creation/modification time (UTC). timestamp
customer_id The unique ID of the account. integer
loaded_at Loading date to Data Platform (UTC). timestamp

Email campaign category

This dataset contains all your campaign categories.

It contains data from January 1st, 2016 onwards.

Data Field Description Type
id The ID of the campaign category. integer
name The name of the campaign category. string
customer_id The unique ID of the account. integer
loaded_at Loading date to Data Platform (UTC). timestamp
event_time Category creation time (UTC). timestamp

Email sends

This dataset contains all your sent emails. By running a query, you can get data on which emails were sent in which campaign to which customers.

This view contains data from January 1st, 2016 onwards.

Data field Description Type
contact_id The unique identifier of the contact in the Emarsys platform. It cannot be used to personally identify individuals. integer
launch_id The unique ID of a launch. integer
campaign_type Whether it is batch or transactional. string_enum
domain The recipient's domain. string
campaign_id Unique campaign ID. integer
message_id The unique ID of the message in a given campaign. integer
customer_id The unique ID of the account. integer
loaded_at Loading date to Data Platform (UTC). timestamp
event_time Send time (UTC). timestamp

Email opens

This dataset contains data collected when your customers opened your emails. By running a query, you can get data on which email has been opened, how many times, by whom, in which campaign, where, and on what device type.

This view contains data from January 1st, 2016 onwards.

Data field Description Type
contact_id The unique identifier of the contact in the Emarsys platform. It cannot be used to personally identify individuals. integer
launch_id The unique ID of a launch. integer
domain The recipient's domain. string
email_sent_at Send time (UTC). timestamp
campaign_type Batch or transactional. string_enum
platform Identifies the platform (e.g. Iphone, Windows, etc.). string
md5 User_agent string md5 hash. string
is_mobile True if the email was opened on a mobile device. bool
is_anonymized True if the user_agent was anonymized. bool
uid User ID. string
ip The IP address of the device on which the email was opened. string
user_agent Device and browser info. string
campaign_id Unique campaign ID. integer
message_id The unique ID of the message in a given campaign. integer
customer_id The unique ID of the account. integer
loaded_at Loading date to Data Platform (UTC). timestamp
event_time Open time (UTC). timestamp
generated_from No info available on opens as the tracking pixel was not allowed to download. string
geo This record contains all geo-related information. record
geo.latitude Approximate latitude of the postal code / city / country associated with the IP address. float
geo.longitude Approximate longitude of the postal code / city / country associated with the IP address. float
geo.accuracy_radius The approximate accuracy radius in kilometres around the latitude and the longitude for the geographical entity. integer
geo.continent_code The code of the continent associated with the IP address. string
geo_country_iso_code The country associated with the IP address. string
geo.city_name The city associated with the IP address. string
geo.postal_code The postal code associated with the IP address. string
geo.time_zone The time zone associated with the location. string

Email clicks

This view shows all clicks related to your sent emails, including multiple clicks on the same link. If you are interested in campaign statistics by platform, this view also tells you on which platform your customers click the most.

It contains data from August 1st, 2018 onwards.

Data field Description Type
contact_id The unique identifier of the contact in the Emarsys platform. It cannot be used to personally identify individuals. integer
launch_id The unique ID of a launch. integer
domain The recipient's domain. string
email_sent_at Send time (UTC). timestamp
campaign_type Batch or transactional. string_enum
platform Identifies the platform (e.g. Iphone, Windows, etc.) string
md5 User agent string md5 hash. string
is_mobile True if the email was opened on a mobile device. bool
is_anonymized True if the user agent was anonymized. bool
uid User ID. string
ip The IP address of the device on which the user clicked a link. string
user_agent Device and browser info. string
section_id The ID of the section in the email. integer
link_id The ID of the link. integer
is_img True if the user clicked an image. bool
campaign_id Unique campaign ID. integer
message_id The unique ID of the message in a given campaign. integer
event_time Click time (UTC). timestamp
customer_id The unique ID of the account. integer
loaded_at Loading date to Data Platform (UTC). timestamp
category_id The ID of the link category. integer
geo This record contains all geo-related information. record
geo.latitude Approximate latitude of the postal code / city / country associated with the IP address. float
geo.longitude Approximate longitude of the postal code / city / country associated with the IP address. float
geo.accuracy_radius The approximate accuracy radius in kilometers around the latitude and the longitude for the geographical entity. integer
geo.continent_code The code of the continent associated with the IP address. string
geo_country_iso_code The country associated with the IP address. string
geo.city_name The city associated with the IP address. string
geo.postal_code The postal code associated with the IP address. string
geo.time_zone The time zone associated with the location. string

Email bounces

If you find that your open rate is below your expectations, your contact list is probably outdated and our mail sending system cannot deliver all your messages. In this view, you can run queries in order to have a look at the bounces, those messages which could not be delivered for various reasons.

This view contains data from January 1st, 2016 onwards.

Data field Description Type
contact_id The unique identifier of the contact in the Emarsys platform. It cannot be used to personally identify individuals. integer
launch_id The unique ID of a launch. integer
domain The recipient's domain. string
email_sent_at Send time (UTC). timestamp
campaign_type Batch or transactional. string_enum
bounce_type Bounce type. Possible values are block, soft and hard. string
campaign_id Unique campaign ID. integer
message_id The unique ID of the message in a given campaign. integer
event_time Bounce time (UTC). timestamp
customer_id The unique ID of the account. integer
loaded_at Loading date to Data Platform (UTC). timestamp

Email cancels

This dataset contains all your cancelled email sends. By running a query you can get data on those messages which could not be sent and they were cancelled. An email send can be cancelled by various reasons, for example the contact filed a spam complaint or the contact doesn't have a valid email address. Possible cancel reasons listed below.

This view contains data from November 20th, 2017 onwards.

Data field Description Type
contact_id The unique ID of the contact in the Emarsys platform. It cannot be used to personally identify individuals.
integer
launch_id The unique ID of a launch. integer
reason
See Possible cancel reasons. string
campaign_type Batch or transactional. String
suite_type The type of the campaign.
string
suite_event
The sub-type of the campaign.
string
campaign_id Unique campaign ID. integer
message_id The unique ID of the message in a given campaign. Integer
event_time Cancel time (UTC). timestamp
customer_id The unique ID of the account. integer
loaded_at Loading date to Data Platform (UTC). timestamp

Possible cancel reasons

Cancel reason Description
empty_address_error
Empty email address.
user_blocked
Contacts address is on a customer level blacklist. (e.g: Contact asked not to be disturbed by emails.)
system_blocked
Contacts address is on a global blacklist. (e.g. robinson list)
spamcomplaint_blocked
Contact is on the customer's spamcomplaint list.
email_duplication
This email is a duplicate, it was already sent to the contact.
html_error
Cannot generate html version of the email.
pers_error
Personalization error occured.
text_error
Cannot generate text version of the email.
alternative_text_error
Generation of alternative text failed.
missing_or_outdated_data_error
No data or outdated data available for Incentive Recommendation.
empty_mail
No content.
invalid_fax_number
Invalid fax number.
invalid_email_address_error
Email address doesn't contain “@".
frequency_cap_blocked
Sending blocked by frequency cap.
program_interrupted
Already scheduled emails canceled because AC program was interrupted.
opted_out
Contact opted-out before mail launch.
encoding_conversion_error
Converting from one charset to another failed.
invalid_email_address_rejected_by_pmta
SMTP server found the email address invalid.
attachment_missing
Attachment cannot be found.
triggered_email_blocked
Contact is on triggered email blacklist.

Email complaints

This dataset contains all complaint events. When a contact complains about a campaign by reporting it as a spam, a new row will be added to this dataset.

This view contains data from November 20th, 2017 onwards.

Data field Description Type
contact_id The unique ID of the contact in the Emarsys platform. It cannot be used to personally identify individuals.
integer
launch_id The unique ID of a launch. integer
domain
The recipient's domain.
string
email_sent_at
Send time (UTC).
timestamp
campaign_type
Batch or transactional.
string
campaign_id
Unique campaign ID.
integer
message_id
The unique ID of the message in a given campaign.
integer
event_time
Complaint time (UTC).
timestamp
customer_id
The unique ID of the account.
integer
loaded_at
Loading date to Data Platform (UTC).
timestamp

Email unsubscribes

This dataset contains all unsubscribe events.

This view contains data from January 1st, 2017 onwards.

Data field Description Type
contact_id The unique ID of the contact in the Emarsys platform. It cannot be used to personally identify individuals.
integer
launch_id The unique ID of a launch. integer
domain
The recipient's domain.
string
email_sent_at
Send time (UTC).
timestamp
campaign_type
Batch or transactional.
string
campaign_id
Unique campaign ID.
integer
message_id
The unique ID of the message in a given campaign.
integer
event_time
Unsubscribe time (UTC).
timestamp
customer_id
The unique ID of the account.
integer
loaded_at
Loading date to Data Platform (UTC).
timestamp
Source See possible sources. string

Possible sources

Source Description
unsubscribe
Contact used the unsubscribe link in the email to unsubscribe from all marketing email communication.
list_unsubscribe
Contact used the unsubscribe button in their email client to unsubscribe from all marketing email communication.
unsubscribe_from_campaign
Contact unsubscribed from a specific campaign only.

Push campaigns

This view shows you all your push campaigns, including all language versions.

It contains data from November 29, 2017 onwards.

Data field Description Type
push_internal_campaign_id Push channel's internal campaign ID. integer
campaign_id The unique ID of the campaign. integer
name The name of the push campaign. string
status The status of the campaign. string
source Possible source options: ac, broadcast, segment, me_segment. string
title It always contains the language code. record
title.k Language code key. string
title.v Language key value. string
message It contains the message body. record
message.k Message language code. string
message.v Message body in the given language. string
application_id Application unique ID. integer
android_settings Any Android specific setting. record
android_settings.k Android setting key. string
android_settings.v Android setting value string
ios_settings Any iOS specific setting. record
ios_settings.k iOS setting key. string
ios_settings.v iOS setting value. string
segment_id The ID of the segment applied. integer
data Customer can add any data. record
target Possible values are push, deliver  and notificationinbox. string
launched_at The launch time of the campaign. timestamp
created_at Campaign creation date (UTC). timestamp
scheduled_at Scheduled time of sending. timestamp
deleted_at Time of deletion. timestamp
event_time The last update of the campaign. timestamp
customer_id Unique ID of the customer. integer
loaded_at Loading date to Data Platform (UTC). timestamp

Push sends

This view contains all your sent push messages. By running a query, you can get data on which messages were in which campaign to which customers.

This view contains data from May 31, 2017 onwards.

Data field Description Type
contact_id The unique ID of the related contact. integer
campaign_id The unique ID of the campaign. integer
push_token A device-related token. string
platform The name of the platform (android, ios, etc.). string
program_id The unique ID of the related Automation Center program. integer
target Represents the target of the message. The typical value is push. string
application_id The unique ID of the application. integer
application_code The unique ID of the application. string
hardware_id The unique ID of the device on which the message was displayed. string
customer_id The unique ID of the customer. integer
loaded_at Loading date to Data Platform (UTC). timestamp
event_time The send time of the message. timestamp
source Trigger of the event. record
source.id The unique ID of the source. string
source.type The type of the source. For example, ac or ui. string

Push not sends

This view shows which messages could not be sent to the target devices.

It contains data from May 31, 2017 onwards.

Data field Description Type
reason The reason for the not sent event. string
contact_id The unique ID of the related contact. integer
campaign_id The unique ID of the campaign. integer
push_token A device related token. string
platform The name of the platform (Android, iOS, etc.). string
program_id The unique ID of the AC program. integer
application_id The unique ID of the application. integer
application_code The unique ID of the application. string
hardware_id The unique ID of the device on which the message was displayed. string
event_time The time when the event occurred. timestamp
customer_id The unique ID of the customer. integer
loaded_at Loading date to Data Platform (UTC). timestamp
source Trigger of the event. record
source.id
The unique ID of the source.
string
source.type The type of the source. For example, ac or ui.
string

Push opens

This view shows which messages were opened and on what kind device types.

It contains data from May 31, 2017 onwards.

Data field Description Type
contact_id The unique ID of the related contact. integer
campaign_id The unique ID of the campaign. integer
source The place where the message was displayed. string
application_id The unique ID of the application. integer
application_code The unique ID of the application. string
hardware_id The unique ID of the device on which the message was displayed. string
event_time The time when it was opened. timestamp
customer_id The unique ID of the customer. integer
loaded_at Loading date to Data Platform (UTC) timestamp

Push custom events

This view contains all the custom push events.

It contains data from May 31, 2017 onwards.

Data field Description Type
event_name The name of the event (this is not unique). string
contact_id The unique ID of the related contact. integer
event_attributes Any custom attribute. record
event_attributes.k Attribute key. string
event_attributes.v Attribute value. string
application_id The unique ID of the application. integer
application_code The unique ID of the application. string
hardware_id The unique ID of the device on which the message was displayed. string
event_time The time when the custom event happened. timestamp
customer_id The unique ID of the customer. integer
loaded_at Loading date to Data Platform (UTC). timestamp

Web session - categories

This view shows the categories the user was browsing in a single session.

It contains data from November 20, 2017 onwards.

Data field Description Type
user_id The Predict user ID (can be an email hash or external ID). string
user_id_type The type of the user ID (email hash or external ID). string
user_id_field_id Which column contains this information in the Emarsys platform. integer
contact_id Emarsys internal unique contact ID. integer
category The name of the category the user browsed. string
event_time The exact time when the user browsed the category. timestamp
customer_id The unique ID (account ID) of the customer. integer
loaded_at Loading date to Data Platform (UTC). timestamp

Web session - purchase

This view shows the products purchased by the user in a single session.

It contains data from November 20, 2017 onwards.

Data field Description Type
user_id The Predict user ID (can be an email hash or external ID). string
user_id_type The type of user ID (email hash or external ID). string
user_id_field_id Which column contains this information in the Emarsys platform. integer
contact_id Emarsys internal unique contact ID. integer
items List of purchased items which include item ID, price, quantity. record
items.item_id The unique ID of the purchased item. string
items.price The price of the product at the time of purchase. float
items.quantity The number of the purchased items. float
order_id The unique ID of the order. string
event_time The exact time when the user bought the items. timestamp
customer_id The unique ID (account ID) of the customer. integer
loaded_at Loading date to Data Platform (UTC). timestamp

Web session - tags

This view shows the events that occurred during a single session.

It contains data from November 20, 2017 onwards.

Data field Description Type
user_id The predict user ID (can be an email hash or external ID). string
user_id_type The type of user ID (email hash or external ID). string
user_id_field_id Which column contains this information in the Emarsys platform. integer
contact_id Emarsys internal unique contact ID. integer
tag The tag sent by the website - It is the type of the event. string
attributes This list contains all the attributes related to the event. record
attributes.name The name of the attribute. string
attributes.string_value String values are stored here. string
attributes.number_value Number values are stored here. float
attributes.boolean_value Logical values are stored here. boolean
event_time The exact time when the event happened. timestamp
customer_id The unique ID (account ID) of the customer. integer
loaded_at Loading date to Data Platform (UTC). timestamp

Web sessions - views

This view shows the products which the user browsed in a single session.

It contains data from November 20, 2017 onwards.

Data field Description Type
user_id The Predict user ID (can be an email hash or external ID). string
user_id_type The type of user ID (email hash or external ID). string
user_id_field_id Which column contains this information in the Emarsys platform. integer
contact_id Emarsys internal unique contact ID. integer
item_id The unique ID of the item which was browsed by the user during the session. string
event_time The exact time when the user checked the item. timestamp
customer_id The unique ID (account ID) of the customer. integer
loaded_at Loading date to Data Platform (UTC). timestamp

Web sessions

This view contains all the information we have about a session. This view was divided into several smaller views, as shown above. It is recommended to use the smaller views in the queries as they are more efficient. 

This view includes all the data from those views as well as one extra piece of information: the list of the last cart items (Abandoned cart).

This view contains data from November 20, 2017 onwards.

Data field Description Type
start_time The start time of the user's session. timestamp
end_time The end time of the user's session. timestamp
purchases Record which includes the purchase time, items, price, quantity and order ID. record
purchases.event_time The time when the purchase happened. timestamp
purchases.items The list of purchased items with item id, price, quantity included. record
purchases.items.item_id The unique id of the purchased item. string
purchases.items.price The price of the product at the time of purchase. float
purchases.items.quantity The number of purchased items. float
purchases.order_id The unique order ID of the purchase. string
views This record contains those items which were viewed by the user during the session. record
views.event_time The exact time when the user viewed the item. timestamp
views.item_id The unique ID of the item which was viewed by the user during the session. string
tags A list which contains the custom events. record
tags.event_time This is the exact time when the event with this tag happened. timestamp
tags.tag This is the tag which was sent by the website. string
tags.attributes This list contains all the attributes related to the event. record
tags.attributes.name This is the name of the attribute. string
tags.attributes.string_value String values are stored here. string
tags.attributes.number_value Number values are stored here. float
tags.attributes.boolean_value Logical values are stored here. boolean
categories This involves all the categories which were browsed by the user during the session. record
categories.event_time The exact time when the user browsed the category. timestamp
categories.category The name of the category which was browsed by the user. string
last_cart All items added to the cart but not purchased and were still in the cart at the end of the session. record
last_cart.event_time This is the exact time when the last item was added to or removed from the cart. timestamp
last_cart.items The list of items that were added to the cart and were still there at the end of the session. record
last_cart.items.item_id The unique ID of the product which was in the cart at the end of the session. string
last_cart.items.price The price of the product at the end of the session. float
last_cart.items.quantity The quantity of the product at the end of the session. float
user_id The Predict user ID (can be an email hash or external ID). string
user_id_type The type of user ID (email hash or external ID). string
user_id_field_id Which column contains this information in the Emarsys platform. integer
contact_id Emarsys internal unique contact ID. integer
currency The currency of the purchase. string
customer_id The unique ID (account ID) of the customer. integer
loaded_at Loading date to Data Platform (UTC). timestamp

SMS campaigns

This view contains general information about your SMS campaigns.

It contains data from September 19, 2017 onwards.

Data field Description Type
name The name of the SMS campaign. string
sender_name The name of the sender. string
message The text of the SMS message. string
include_unsubscribe_link Unsubscribe link included or not. boolean
trigger_type Trigger type. Possible values are batch_now, ac and batch_later. string
campaign_id The ID of the campaign that contains this message. integer
event_time The time when the campaign was created/modified. timestamp
customer_id The unique ID (account ID) of the customer. integer
loaded_at Loading date to Data Platform (UTC). timestamp
business_unit The provider's name. string

SMS send reports

This view contains the SMS delivery information.

It contains data from September 19, 2017 onwards.

Data field Description Type
bounce_type The reason of the bounce. string
campaign_id The ID of the campaign that contains this message. integer
contact_id The ID of the contact who received the message. integer
customer_id The unique ID (account ID) of the customer. integer
event_time The time when the SMS message was sent. timestamp
loaded_at Loading date to Data Platform (UTC). timestamp
message_id The unique ID of the message. string
status The current status of the send. string

SMS sends

This view contains information about your sent SMS messages.

It contains data from September 19, 2017 onwards.

Data field Description Type
message_id The unique ID of the message. string
launch_id The unique ID of the related launch. integer
contact_id The ID of the contact who received the message. Integer
program_id The ID of the program which sent this message. integer
campaign_id The ID of the campaign that contains this message. integer
customer_id The unique ID (account ID) of the customer. integer
loaded_at Loading date to Data Platform (UTC). timestamp
event_time The exact time when the sms was sent (UTC). timestamp

SMS unsubscribes

This view contains the SMS-based subscription cancellation events.

It contains data from September 19, 2017 onwards.

Data field Description Type
contact_id The ID of the contact who unsubscribed from the SMS campaign. Integer
unsubscribe_type Type of cancellation. string
event_time The exact time when the subscription cancellation happened (UTC). timestamp
campaign_id The ID of the campaign that contains this message. integer
loaded_at Loading date to Data Platform (UTC). timestamp
customer_id The unique ID (account ID) of the customer. integer
Bu makale yardımcı oldu mu?

Başka sorularınız var mı? Bir talep gönder
Üste dön

Emarsys is a Leader

You may also be interested in:

İlgili makaleler

  • Overview:: Open Data - Overview
  • End-user guides:: Open Data - End-user guide
  • The Emarsys Product Roadmap
  • End-user guides:: Program summary
  • Relational Data onboarding for clients using Emarsys-hosted databases
Copyright © 2019 Emarsys eMarketing Systems. All rights reserved
Legal Notice Privacy Policy Master Services Agreement Anti-spam Policy