SFMC Data Extension Mapping

Primary key mapping

The first decision for mapping is primary key mapping:

• Clutch cards have a card number as primary key
• SFMC Contacts have a ‘Contact key’ as primary key

The options to map them are:

1. Create a Clutch customer model field for ‘SFMC contact key’ (any naming is possible) and use this to map the Clutch cards to SFMC contacts.
2. Map based on email and use a random UUID as contact key if an SFMC contact was missing.

Option 1: Clutch customer model field for SFMC contact key

1. Create a customer model field to contain the SFMC contact key. This field will be populated through either VT, batch or API calls.
   • This field should NOT be the ‘externalId_sfmc’ field, that is an internal-only field that API clients should never write to
2. In the brand mapping, specify ‘linkingField’ as ‘custom.[internal field name of SFMC contact key field]’
3. In the brand mapping, specify a custom property mapping in customProperties for [internal field name of SFMC contact key field] to a LinkedDEProperty with data extension=’Contact’ and attribute name=’Contact Key’ and linking field = ‘Contact Key’
4. In the brand mapping, also specify a mapping from Clutch primary.email to SFMC data extension= ‘Email Addresses’ and attribute = ‘Email Address’, with linking field = ‘Member ID’. SFMC only allows contacts to be created if the email address is populated.

The Clutch sync process will automatically set HTML Enabled = true when creating new contacts – you don’t have to do anything with that setting.

Option 2: Map based on email address

1. Leave the linkingField empty in the brand mapping, or specify it as ‘primary.email’ (both have the same effect).
2. Add a mapping of Clutch primary.email to data extension ‘Email Addresses’, attribute ‘Email Address’ with linking field = ‘Member ID’

To do in UI mapping tool

1. Update sfmcapi maven module version in portal to 0.0.2-2018-09-20-0956
2. If Data Extension Table = ‘Contact’, automatically select Linking ID = ‘Contact ID’ and Marketing Cloud Data = ‘Contact ID’

• Normally you can’t select the same value for both Linking ID and Marketing Cloud Data, but for this particular Data Extension, you can:

3. Add a dropdown to ask ‘Field to link Clutch and SFMC’ and store the result in LinkingField, options:

a.) Email, in this case, set linkingField = ‘primary.email’
b.) SFMC Contact Key, in this case, show a dropdown to ask ‘Which customer model field contains the SFMC contact key?’

• In that dropdown, show all customer model fields except conflictState_sfmc and externalId_sfmc
• Once selected, save the selected field, e.g. sfmcId (if that is a customer model field internal field name for the test brand) into the linkingField in the format ‘custom.sfmcId’

4. Similar to the rest of the mappings, only allow changes to the new dropdown if the UI is ‘unlocked’ with the same brand setting.