...
After uploading your file or creating your template, you will notice an option in the Category drop down called Product - Magazine. Just like the Product - Newsletter option, this will allow you to map magazine product, requested or active version for that product, and quantity. If you do not have the product included in the file, it is important to create a constant in this step for the magazine product to ensure the incoming data is mapped to the desired magazine product. NOTE: Currently, Data Loader only accepts incoming values of P, D, B, and A for Requested and Active Version. Soon to come: Version Mapping step that allows users to map incoming values for Requested Version and map those values to our Omeda Version values.
Once Product - Magazine is selected and the General Mapping step is saved, you will notice a few more steps added to the step drop down:
Product Class Mapping
Contact Mapping
Source Priority Mapping
Processing Rules
Version Mapping (if the Requested Version field for the Magazine is also mapped)
Product Class Mapping
Product Class Mapping allows you to map the incoming value from the file (or constant value seen in the example above) for the magazine subscription to the correct product, along with BPA Type and Class Definition. Using the Update columns, users can choose to only add new subscriptions, meaning if a customer on file already has a subscription, the existing subscription will not be updated. Or, users can select the “Update or Add Incoming” option which will update existing and add new subscriptions.
...
Product level processing rules will be applied to all files that have a specific product (with processing rules defined) mapped. Say I have a processing rule defined for product ABC. The processing rule will be applied to all files that include product ABC, if applicable.
Version Mapping
The Version Mapping step allows you to map the incoming values for the Requested Version field for a Magazine product to Omeda’s defined values.
To make mapping quicker and more efficient, this step will automatically map any incoming common values from you file to the associated Omeda value. These automatic mappings can be edited if need be.
For example:
The following incoming values will automatically be mapped to Omeda’s Print value:
P
Print
The following incoming values will automatically be mapped to Omeda’s Digital value:
D
Digital
Dig
The following incoming values will automatically be mapped to Omeda’s Both value:
B
Both
Print & Digital
P & D
Using the Update column, users can choose to only add the Requested Version to new subscriptions by selecting the “Add Incoming Only” option, meaning if a customer on file already has a subscription and Requested Version, the existing subscription will not be updated. Or, users can select the “Update or Add Incoming” option which will update existing and add the Requested Version to new subscriptions.
...