Email Segmentation with User Attributes

Overview

This feature gives you the ability to segment triggered emails based on custom attributes in users' WKND-stored profiles. The data can also be dynamically added to email campaigns to reflect near real-time characteristics such as membership statuses, loyalty point totals, loyalty tiers, etc. This data is ingested into the Wunderkind platform via file drops with email addresses and the corresponding user attributes. 

Table of Contents

1. Use Cases
2. Ingestion Methods
3. File Requirements
4. Standard Attributes
5. Non-Standard Attributes

Use Cases

Example:

Your store utilizes a loyalty program that has not seen as much engagement as you would like. If you are able to provide Wunderkind with a recurring list of loyalty users:

1. Loyalty users can receive abandonment emails with offers based on their tier, point total, etc.
2. Non-loyalty users can receive a banner in their abandonment emails that encourages them to sign up for the loyalty program

Ingestion Methods 

Wunderkind can ingest files from a client-hosted SFTP/S3 bucket or Wunderkind-hosted GCP bucket. 

File Requirements 

• Files must be in CSV format
• Files are required to have email addresses in the first column 
  • The email and attribute column(s) should have headers
    • When receiving files from a client-hosted SFTP/S3 bucket, we can accept custom headers and map them to 'email' and an attribute name from the list below on our end, example below
    • When receiving files from a Wunderkind-hosted GCP bucket, the first column header must be 'email' and the following column header(s) must match the standard attribute names from the list below

Example:

Standard Attributes

Below is our list of standard user attributes and corresponding accepted types (string, boolean, stringlist). 

• String - any alphanumeric value e.g. “gold”, “cancelled_subscription”, “DD-MM-YYYY”

• Boolean - true/TRUE/false/FALSE

• Stringlist - a comma separate list of alphanumeric values

Non-Standard Attributes

Below is the list of user attributes covered via other folder uploads. If your team would like to send a single file containing multiple pieces of information e.g. subscriber status, customer status, and loyalty status, this can be utilized