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
From the Customer 360 tab, under All Databases, select the menu for the customer 360 database, and then click Edit.
From the Database Editor, click Add Table.
Name the table “Email Engagement Attributes”.
Set the build mode to SQL.
Click Apply template, and then select Email Engagement Attributes.
Step through the table, and then apply any necessary customizations.
Click Next. This opens the Database Table Definition page.
Add a table description. This enables a tooltip that is visible from other areas in Amperity.
Verify that the db/required and db/unique database field semantics were applied to the amperity_id column.
Verify that email-attribute semantic tags are applied to all fields.
Review picklists to ensure they have the desired sorting parameters.
Add friendly names for any field.
From the Table Semantics drop-down, select Email Engagement Attributes.
Click Save.