Marketing data specification

Marketing data helps enrich profiles, and activate campaigns through various channels. After activation the Hub allows you to measure the impact of the campaign among different target segments.

The Lexer Marketing Data specification provides a standard format for your email and SMS event engagement to enrich your customer profiles into the CDXP. When data is provided using this API, this data will enrich your customer’s profiles with additional attributes. 

More detail about the attributes that can be created from this API are in the links below:

• Email 
• SMS 
• Engage 
• Activate 

For more information about these attributes you can find our full attribute list here.

Email Subscribe events

A sample of a email subscribe event record: 

Required fields

• link: Where a customer record is defined by a single identifying link (email, email_sha256, email_md5, mobile, customer_id or external_id). To add more links for unification purposes, you will need to provide Unification data
• action_at: The date and time the customer subscribed. 
• status: The customer's Subscription Status. This could include, "subscribed", "unsubscribed", "list_subscribed", "list_unsubscribed".

Email Send events

A sample of an email event record: 

Required fields 

• link: Where a customer record is defined by a single identifying link (email, email_sha256, email_md5, mobile, customer_id or external_id). To add more links for unification purposes, you will need to provide Unification data
• action_at: The date and time the Email was sent. 
• campaign_id: The marketing Campaign Identifier or Name.

Email Open events

A sample of an email event record: 

Required fields

• link: Where a customer record is defined by a single identifying link (email, email_sha256, email_md5, mobile, customer_id or external_id). To add more links for unification purposes, you will need to provide Unification data
• action_at: The date and time the Email was opened. 
• campaign_id: The marketing Campaign Identifier or Name.

Email Click events

A sample of a email click event record: 

Required fields

• link: Where a customer record is defined by a single identifying link (email, email_sha256, email_md5, mobile, customer_id or external_id). To add more links for unification purposes, you will need to provide Unification data
• action_at: The date and time the customer clicked through to the accompanied link within the email. 
• campaign_id: The marketing Campaign Identifier or Name.

Email Bounce events

A sample of a email bounce event record: 

Required fields

• link: Where a customer record is defined by a single identifying link (email, email_sha256, email_md5, mobile, customer_id or external_id). To add more links for unification purposes, you will need to provide Unification data
• action_at: The date and time the email bounced. 
• campaign_id: The marketing Campaign Identifier or Name.

SMS Subscribe events

A sample of an SMS subscribe event record: 

Required fields

• link: Where a customer record is defined by a single identifying link (email, email_sha256, email_md5, mobile, customer_id or external_id). To add more links for unification purposes, you will need to provide Unification data
• action_at: The date and time the customer subscribed. 
• status: The customer's Subscription Status. This could include, "subscribed", "unsubscribed", "list_subscribed", "list_unsubscribed".

SMS Send events

A sample of an SMS send event record: 

Required fields

• link: Where a customer record is defined by a single identifying link (email, email_sha256, email_md5, mobile, customer_id or external_id). To add more links for unification purposes, you will need to provide Unification data
• action_at: The date and time the SMS was sent. 
• campaign_id: The marketing Campaign Identifier or Name.

SMS Click events

A sample of an SMS click event record: 

Required fields

• link: Where a customer record is defined by a single identifying link (email, email_sha256, email_md5, mobile, customer_id or external_id). To add more links for unification purposes, you will need to provide Unification data
• action_at: The date and time the customer clicked through to the accompanied link within the SMS. 
• campaign_id: The marketing Campaign Identifier or Name.

That’s a wrap on Marketing data specifications

This page has covered some samples of the marketing data schema itself, and the requirements of the schema. If you have any questions, please reach out to your Success Manager.