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, or by way of an FTP automated process (see FTP Import Templates for more details). 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.
The Imports screen is used to perform a manual file import. From this screen you can browse to and select the import file, select or define a Data Map, set up email notifications, reviewing parsing results, and configure various options for how the platform should handle and process the data.
|
The Marigold Help Center provides access to a wide range of enablement videos on many Marigold solutions that you can take as needed. Click here to browse to the video on how to use Imports. |
Before proceeding to import data into the platform, the following required assets need to be created within Engage+:
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 (it is possible to create new fields "on the fly" when performing a manual import). 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. Data Maps can be created prior to defining the Import Template, or they can be created "on the fly" when performing a manual data import. See the Data Maps topic for more details.
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, but you'll need to define the Data Map separately; you can't create an "on the fly" Data Map if importing a fixed-width file. See the Data Maps topic for more details.
The import file may contain any information that is available, and will typically contain the Unique Identifier for the destination Table; it is possible to load an import file that doesn't have the Unique Identifier, through the use of a "Soft Match" instead.
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 Imports screen is accessible by the following method:
From the Main menu, select Data > Execution > Imports
Create a New Manual Import A Manual Import allows you to process a "one-off" file import. When creating a Manual Import, the steps in the import process will vary depending on which options you select. The following flowchart depicts these different options. To create a new Manual Import:
Upload FileThe "Upload File" section is used to select the file that you want to import, and to define various configuration options.
Map ColumnsThe "Map Columns" section is primarily used if you selected the Create a New Data Map option above. This section is used to map the columns in the import file to the correct fields in the destination Table, or to any joined Tables. If you selected an existing Data Map, then this section is "read only." You can view a preview of the import file contents, and view the selected Data Map, but you won't be able to make any changes to the column mapping. Note: If your import file contains a header row, the system will attempt to identify the columns in the import file by matching the values in the header row to the "Database Name" in the Table. If the system is able to find a match, that field be automatically be displayed within the drop-down menu in the "Map to" column on the screen. To define the "on the fly" column mapping for your Manual Import:
Note: In most cases, the Unique Identifier for the destination Table should be part of the Data Map (and it's required if you're importing data into a Load and Send table). If the Unique ID is composed of multiple fields, then all of those fields need to be mapped in order to successfully load the data. If the Unique Identifier is not in the import file, then you'll need to use the Soft Match feature, which is described below in more detail.
If the import file doesn't contain the Unique Identifier field for the destination Table, then you must use the Soft Match feature in order to successfully load the data. The Soft Match lets you match to the database using any fields with a Data Type of "Email" or "Phone." For example, let's say the Unique ID on your "Recipient" table is "Member ID," but you don't have Member ID data available in your import file. You could instead select some other field, such as "Email Address," that contains unique data, and match on that instead. Please note that this option isn't available if you're importing data into a Load and Send table. Define a Soft MatchDefine a Soft Match
If the soft-matched value in the import file matches an existing value in the database, then the platform will make the update to that record in the database. If the soft-matched value does not already exist in the database, the platform creates a "temporary" record. This temporary record can later be merged with a full record that contains the Unique Identifier.
Select NotificationsIf you checked the "Import Exceptions" check box above, an additional "Select 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.
Process FileWhen the platform has finished parsing your import file, the "Process File" section is populated with the results of the parsing step. This section shows how many records were on the file, and how many records encountered warnings or validation errors. This section also allow you to establish the Priority for your import file. The Priority you select determines the order in which your imports will be handled. Generally speaking, your imports with a higher priority will take precedence over your imports with a lower priority. If your imports have the same priority, they will be processed in the order in which they were added (older imports first). A few potential exceptions exist, which may impact the processing order of your imports:
To finalize the import process:
|
View a Completed Manual Import Once a Manual Import is finished, and the records have all been imported into the database, you can no longer make any changes to that Manual Import. However, you can still view the configuration settings that were used for the import process To view a completed Manual Import:
|
Edit a Manual Import A Manual Import consists of four main steps (Upload File, Map Columns, Select Notifications, and Process File). Once a given step is complete, you can no longer make any changes to the configuration options for that step. However, you can make changes to any subsequent steps that haven't yet been run. For example, let's say you finish the Upload File step for a Manual Import. You could leave the Import screen, then later come back and select that same Manual Import. You wouldn't be able to change any of the Upload File settings, but you could configure the next step in the process, Map Columns. If you find that you need to make changes to a completed step, you'll have to cancel the Manual Import (see "Cancel a Manual Import" below for more details), then start over with a brand new Manual Import. To edit a Manual Import:
|
Delete a Manual Import To delete an item:
Foldered items are moved to the Recycle Bin. Non-foldered items are permanently deleted.
|
Cancel a Manual Import A Manual Import consists of four main steps (Upload File, Map Columns, Select Notifications, and Process File). At each of these four points, you have the option of saving and continuing to the next step, or of cancelling the Manual Import. Once a Manual Import has proceeded all the way through the final "Process File" step, you can longer cancel it. Also, canceling a Manual Import is permanent, meaning that you can no longer make any changes do it, nor can you "un-cancel" it and continue on with the next step. To cancel a Manual Import:
|
Troubleshooting an Import If your import isn't correctly processing records, check the following:
If the problem persists, please contact Global Support for further assistance. |