The primary purpose of your Engage+ database is to store all of the data that you need to effectively plan and execute your marketing campaign strategy. Your database is composed of one or more tables, each of which is arranged into rows (i.e., "records") and columns (i.e., "fields"), similar to a spreadsheet. However, unlike a spreadsheet, the platform's tables are highly optimized for writing and reading large amounts of data.
Every Engage+ client database starts with a "Recipient" table that contains contact information about your customers. That table consists of more than thirty commonly-used fields such as "Email Address," First Name," "Last Name," "Home Address," Business Address," and so forth. The Recipient table (like all tables in Engage+) is completely customizable -- fields can be added as needed to support your marketing needs. Depending on the complexity of your data, your system may require additional tables other than the default Recipient table; creating additional tables can make managing the platform easier.
The Tables screen is used to manage the tables that make up your marketing database. This screen allows you create new tables and fields, and to manage your existing tables.
Note: If you need to build a table to support custom responses, please see the Custom Responses topic.
The Tables screen is accessible by the following method:
From the Main menu, select Data > Management > Tables
For more information on Tables, please see:
Create a New Table To create a new table:
|
View or Edit a Table To view or edit an existing table:
|
Set Record Lookup Fields The Record Lookup feature is a database query tool that lets you build simple queries for looking up records in your marketing database. From the Table detail screen, you can define what fields will be displayed on the Record Lookup screen, and in what sequence, when you query this particular table. To set the Record Lookup fields:
|
Grant Access to Child Systems If your Engage+ account has been set up with a Parent / Child relationship, the Tables screen allows you to manage specifically which fields are shared from the Parent down to a Child system. When you share data with a Child system, you make that data viewable and usable to that Child. Please note that while a Parent system will have access to all the data in the Child systems, the "sibling" systems can't interact or share data and information with each other unless permission has been established at the Parent level. For more information on Parent / Child systems, please see Multi-Division Client Accounts. Note: This feature is not available for Load and Send Tables. Once you grant access to a field to a Child system, you can't remove access to that field. You can optionally allow access to more fields from this table; see "View or Edit Access to Child Systems" below for more details. To share fields between a Parent and a Child system:
|
View or Edit Access to Child Systems If your Messaging account has been set up with a Parent / Child relationship, the Tables screen allows you to manage specifically which fields are shared from the Parent down to a Child system. When you share data with a Child system, you make that data viewable and usable to that Child. For more information on Parent / Child systems, please see Multi-Division Client Accounts. Once you grant access to a field to a Child system, you can't remove access to that field. Note: This feature is not available for Load and Send Tables. To view or edit the data access privileges that have been granted to a Child system:
|
Enable / Disable Sending Event Data to EDP For clients who use Engage+ in conjunction with Engage+'s Engagement Data Platform (EDP), you can decide whether or not to send Event data (such as sends, opens, clicks, unsubscribes and so forth) from Engage+ to EDP for Campaigns that use this table as the data source. This process of sending Event data from Engage+ to EDP is referred to as Real-Time Export, or RTX. Note: RTX is an optional feature that must be enabled in your account. Please speak to your support representative for additional details. At a table level, you can disable RTX if it's not needed. As an example, some clients send transactional Campaigns (like password resets or shipping notifications) from a separate sending table. The Event data generated by these Campaigns likely has little marketing value, so for this table, you could disable the RTX process. To disable Real-Time Export for a table:
To enable Real-Time Export for a table:
|