Engage+ offers several different ways to bring data into the platform and load it into your marketing database. Data can be imported in a manual process through a file import (see Imports for more details), or by way of an FTP or Amazon S3 automated process. You can manually edit or enter records one at a time using the Record Lookup screen. Data can also be submitted to the platform through an API Post, or through Web Forms and Web Events. The best import method should be indicated by your business requirements and marketing strategy. If you have any questions about which import method best meets your needs, please speak with your Client Services Representative.
As with Export Templates, an Import process can be defined through the use of a repeatable template. An Import Template controls the schedule of when to run the import, as well as details about the file handling settings.
Before proceeding to import data into the platform, the following required assets need to be created within Messaging:
Tables: The destination Table where you want to load your import data should be created, and should include all the necessary fields and joins, as well a Unique Identifier. See the Tables topic for more details.
Data Map: Data Maps identify the correct Table into which the data needs to be loaded, as well as the fields in that Table where each column in the import file will be stored. See the Data Maps topic for more details.
Profiles: A Profile controls the location and login credentials for an FTP server, or S3 Bucket, from which import files are to be downloaded. See the FTP / S3 Profiles topic for more details.
NCOA Process: If you're importing data with consumer postal address information, you can optionally run that data through NCOA (National Change Of Address) processing. This process submits an address list to a service which in turn runs it against regulated lists that maintains updated addresses. From this, updated addresses are returned. See the NCOA Processes topic for more details.
Custom Stored Procedures: Custom procedures are typically used to perform additional data transformations on the import file. If you need a custom stored procedure created for your account, please contact your Client Services Representative.
Engage+ accepts database imports as Microsoft Excel files or as text files, with the data fields being delimited using any of the following characters: tab, comma (,), semicolon (;), pipe (|), or caret (^). The platform also supports the use of fixed-width import files.
Before importing data into the platform, make certain the data is clean and formatted properly. The following tips can be useful when creating text files from Microsoft Excel:
Whenever possible, try to avoid using a comma as the delimiter character for your import file, and instead use tab or pipe for a delimiter. Commas are used more frequently within data, and as such, are more difficult to discern when examining data. The tab or pipe characters are rarely found in data.
Preview the text file in a text editor, such as Notepad, using line numbers and visible spaces to review the file and ensure proper formatting.
The platform parses the import data to ensure that the values are clean, valid, and usable. Depending on the Data Type for a field, various methods of parsing and cleansing are utilized. The platform may adjust the import value for a field according to rules set for that type of field. For example, if a numeric value is being imported into a field identified as a "Phone Number," the platform will verify that this value is the correct length, and will remove any unnecessary and invalid characters. For more details on the Data Parsing rules utilized by Messaging, please see the Data Parsing Help topic.
The FTP / S3 Import Templates screen is also used to manage Import Templates used for the platform's Load and Send feature. Load and Send allows you to import "campaign-ready" files containing all the information needed to build and deploy the Campaign (such as personalization fields, and contact information like Email Address). This data is loaded into a special table dedicated specifically to the Load and Send feature, rather than into the regular relational database tables. Import Templates that are intended for use in Load and Send Campaigns differ slightly from regular Import Templates, as follows:
The "Ignore Update History" option will un-selected by default, without the option to select it.
The only supported "Hierarchy Option" is "Update Current Customer Only."
Postal processing isn't supported.
The FTP / S3 Import Templates screen is accessible by the following method:
From the Main menu, select Data > Integration > FTP / S3 Import Templates
Create a New FTP / S3 Import Template To create a new Import Template:
ScheduleThe "Schedule" section allows you to set a schedule for automatically executing the import process. To define the schedule frequency and duration:
FTP / S3 DownloadThe "FTP / S3 Download" section is used to define the details of the expected file location and name.
Note: Messaging will not pick up a file with the same exact file name more than once.
Files to ImportAn Import Template can optionally be used to import multiple files within the same ZIP file. You can choose to handle all of these files in the same manner, or you can select different configuration options and Data Maps for each file. Initially, this section displays a single item with the default file name (*.*), which indicates "all files." To configure the import file (or files):
Note: You can't adjust the priority of an in-progress import. The import priority you select in the "Files to Import" dialog box will be applied to this template from this point forward, and not to any in-progress imports.
Note: The "Postal" drop-down menu is not displayed if you selected a Load and Send table above in step 4.
The next option relates to the platform's "update history" functionality. Update history for a file means that the platform writes an update for every record that came in on the file, to denote that the record “came in on this file at this time.” This level of detail allows you to create Filters that can look for all records that came in on a specific file, or in a specified timeframe, and return all of those records. The default setting is to retain this information, in order to build an activity history for all records. If you don't need, or want, to store update history, you can turn this feature off. An example would be something like a Product table. Let's say you don't create Filters on Product records, but instead use that data only to personalize order confirmations. In this case you can ignore the update history, so that you have only the data, but not the unnecessary details of what records were updated, and when. The advantages to not storing update history are basically storage space and performance. Ignoring update history will give you a slight performance boost on import processing, and store less data on the backend.
Note: The "Ignore Update History" check box is automatically unchecked, but not displayed, if you selected a Load and Send table above in step 4. Also, the "Filter / Trigger" check box (described below) will be checked, and disabled.
NotificationsIf you checked the "Import Exceptions" check box above, an additional "Notifications" section is displayed on the screen. This section allows you to define email alerts if the contents of your import file surpass certain thresholds for a selected import metric or exception.
Note: If you want to delete an existing Template, select it from the "Template" drop-down menu, then click delete.
Note: You must check at least one of the above check boxes.
|
Copy an FTP / S3 Import Template To copy an existing item to use as the basis for a new item:
|
View or Edit an FTP / S3 Import Template To view or edit an FTP / S3 Import Template:
|
Review and Approve an Import The platform parses import data to ensure that the values are clean, valid, and usable. Depending on the Data Type for a field, various methods of parsing and cleansing are utilized. The platform may adjust the import value for a field according to rules set for that type of field. For example, if a numeric value is being imported into a field identified as a "Phone," the platform will verify that this value is the correct length, and will remove any unnecessary and invalid characters. For more details on the Data Parsing rules utilized by Messaging, please see the Data Parsing Help topic. When importing data via an Import Template, you have the option of automatically committing the data to the database without reviewing it, or of pausing the import process to allow for a manual review of the parsing results. To manually review and approve the parsing results for an import file:
|
Delete an FTP / S3 Import Template To delete an item:
Foldered items are moved to the Recycle Bin. Non-foldered items are permanently deleted.
|