Loyalty Data Maps are specialized data maps used for the integrated data import process service between Engage+ and Loyalty. This import process service is intended to be used only for users who also use Marigold Loyalty.The data to be imported are called Profile Attributes.
From the Loyalty User Interface, users have the ability choose the data (Profile Attributes) to be synced with Engage+. Based on the use case scenarios, the users can choose the Default Attributes, and if needed also include additional Attributes, which are called the “Custom Attributes.” This Loyalty Data Map will be used during the import process to know how to update the relevant tables in Engage+, when Custom Attributes are selected for the import.
For more details on Data Maps, refer Data Maps.
Once the Loyalty Data Map is setup and “Enabled” toggled ON on the Profile Stream page in Marigold Loyalty, your profile Attributes, Preferences and Metrics will be continually streaming, updating your recipient data any time a value changes in Marigold Loyalty. You can then create an email campaign using your Loyalty Profile Stream table as your data source.
The Data Maps screen is accessible by the following method:
From the Main menu, select Data > Integration > Loyalty Data Maps
Create a New Reusable Loyalty Data Map Data Maps can be defined as either a reusable asset, or as a one time-only asset that gets built "on the fly" when defining a Manual Import. To create a new reusable Data Map:
Note: You can never modify this Data Source Table after the Data Map is created.
As you add more fields, the system automatically increments the "Col #" value by one, but you can optionally enter a different value here, if needed. If you need to ignore a column in the import file, simply skip over that column number in the sequence. For example, if you want to ignore column #4 in your import file, the numbering sequence in your Data Map would go from Column #3 to Column #5, and leave out column #4. The important point to keep in mind is that the sequence you're defining here represents the column order from the input file, and the mapped field you select is the location in the database where that data is being inserted. You can also use negative values as the "Col #" in order to negatively map fields. When you negatively map a field, you're telling the system that you want to populate the specified "Map to" field in the database, but that you don't expect this value to be present in the import file. Instead, the value is going to come from some place other than the import file, such as a SQL script, for example. The Data Map must include the field (or fields) that make up the Unique Identifier for the Loyalty Profile Stream Table, even if you're not actually intending to import the Unique Identifier field. The user interface performs a validation on the Data Map that requires the Unique ID field (or fields) be present in the Data Map. If you're not actually providing the Unique ID value in the import file, you'll need to use the Soft Match feature (described below). In this situation, select the Unique ID field from the "Map to" drop-down menu, and enter a negative number for the column number. In this manner, the Unique ID is present in the Data Map (allowing you get past the screen validation), but you don't actually have to provide any values for it, and it won't interfere with the columns that you are importing.
Note: If you run a Calculated Field as part of an import process, the system derives and populates that field only for the records in the import file. Conversely, if you set up a Calculated Field schedule, the system derives and populates the field for every record in the table (see Tables for more details). Note: If you selected a Load and Send table above in step 3, the Calculated Fields option is not available.
If the import file doesn't contain the Unique Identifier field for the Source 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," "Phone," "Twitter," "Facebook ID," or "Push Registration ID." 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. 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. As described above, if you're using the Soft Match feature, you still must add the Unique Identifier field (or fields) to the Data Map, even if you're not actually intending on providing the Unique ID fields on the inbound data. The Unique ID must be part of the Data Map in order to save the Data Map.
Note: If you selected a Load and Send table above in step 3, the Soft Match feature is not available.
|
Copy a Loyalty Data Map To copy an existing item to use as the basis for a new item:
|
View or Edit a Loyalty Data Map To view or edit a Loyalty Data Map:
|
Delete a Loyalty Data Map To delete an item:
Foldered items are moved to the Recycle Bin. Non-foldered items are permanently deleted.
|