Email_Engagement_Attributes Table

The Email_Engagement_Attributes table contains all fields from the Email_Engagement_Summary table, unique by Amperity ID and by email address. This table may be extended for related email engagement and transaction attributes.

Important

The Email_Engagement_Attributes, Email_Engagement_Summary, and Unified_Email_Events tables are used to enable email engagement workflows within Amperity.

The Email_Engagement_Summary and Unified_Email**Events tables are generated as Stitch output after applying email events semantic tags to data sources that contain email engagement data, such as opens, clicks, opt-in and opt-out preferences, or conversions, along with email summary if that data is available.

The Email_Engagement_Attributes table is built in your customer 360 database using a built-in SQL template. Some customization of this SQL template is necessary to align the behavior of this table to the data that exists in your tenant.

Note

The Email_Engagement_Attributes table relies on the Merged_Customers table and must be added to your customer 360 database using a SQL template.

Add table

The Email_Engagement_Attributes table is a table that contains one email address for each Amperity ID. This table may be used to apply email engagement data to campaigns. The Email_Engagement_Attributes table is built from a SQL template, is custommized for your tenant, and then applies a series of email-attribute semantic tags to the fields in the table.

To add the Customer360 table

1. From the Customer 360 tab, under All Databases, select the menu for the customer 360 database, and then click Edit.

2. From the Database Editor, click Add Table.

3. Name the table “Email Engagement Attributes”.

4. Set the build mode to SQL.

5. Click Apply template, and then select Email Engagement Attributes.

6. Step through the table, and then apply any necessary customizations.

7. Click Next. This opens the Database Table Definition page.

8. Add a table description. This enables a tooltip that is visible from other areas in Amperity.

9. Verify that the db/required and db/unique database field semantics were applied to the amperity_id column.

10. Verify that email-attribute semantic tags are applied to all fields.

11. Review picklists to ensure they have the desired sorting parameters.

12. Add friendly names for any field.

13. From the Table Semantics drop-down, select Email Engagement Attributes.

14. Click Save.

Apply semantic tags

Apply the following email attributes table semantics to the table that is created by the Email Attributes SQL template. Use the built-in list of semantics when building a table in your customer 360 database. Email attributes semantics are prefixed with email-attributes/ and are applied to database tables using the database editor.

Warning

Email attributes semantic tags must be applied to a SQL table in your customer 360 database. Email attributes semantic tags cannot be applied to raw email events data in the sources tab.

The following table lists the tags available to this semantic group (with required semantic tags noted by “ Required.” and recommended semantic tags noted by “ Recommended”):

Semantic Name	Datatype	Description
brand	String	Required. The brand or company from which an email was sent.
email	String	Required. The email address to which an email was sent.
email-clicks-last-x-days	Integer	The number of email clicks in the last 1, 3, 5, 7, or 14 days.
email-clicks-last-x-months	Integer	The number of email clicks in the last 3, 6, 9, or 12 months.
email-opens-last-x-days	Integer	The number of email opens in the last 1, 3, 5, 7, or 14 days.
email-opens-last-x-months	Integer	The number of email opens in the last 3, 6, 9, or 12 months.
engagement-frequency-last-15-months	String	A classification that measures engagement frequency click rates for email addresses that have received a low volume of emails. Possible values: Non-recipient (0 received emails) New (fewer than 5 received emails) Active (currently engaging with received emails) Inactive (not currently engaging with received emails) Important Send rates must be available.
engagement-status-last-15-months	String	A classification that measures click rates for email addresses that have received a low volume of emails. Possible values: Non-recipient (0 received emails) New (fewer than 5 received emails) Low (modeled open rate is in the lower third) Medium (modeled open rate is in the middle third) High (modeled open rate is in the upper third) Important Send rates must be available.
first-email-click-datetime	Datetime	The date and time at which an email was first clicked.
first-email-open-datetime	Datetime	The date and time at which an email was first opened.
first-email-send-datetime	Datetime	The date and time at which an email was sent.
most-recent-bounce-datetime	Datetime	The date and time for the most recent bounced email.
most-recent-email-click-datetime	Datetime	The date and time at which a customer most recently clicked a link or offer within an opened email.
most-recent-email-open-datetime	Datetime	The date and time at which a customer most recently opened an email.
most-recent-email-optin-datetime	Datetime	The date and time at which a customer most recently opted-in to receiving email.
most-recent-email-optout-datetime	Datetime	The date and time at which a customer most recently opted-out from receiving email.
most-recent-email-send-datetime	Datetime	The date and time at which an email was most recently sent.
purchase_before_signup	Boolean	Indicates when an Amperity ID is associated with a transaction that occurred before signing up with this email address. Important This semantic tag requires the Transaction_Attributes and Unified_Transactions tables to be joined to the Email_Engagement_Attributes table.
region	String	The region or location from which an email was sent. The region or location is typically associated to a single brand.
signup_to_purchase_days	Integer	The amount of time (in days) between using this email to sign up and the next transaction associated with this Amperity ID. This field is NULL if there has not been a transaction. Important This semantic tag requires the Transaction_Attributes and Unified_Transactions tables to be joined to the Email_Engagement_Attributes table.