Hi all,
I am wondering how manual CSV file mapping will work with the idSpecific object in the UI. Specifically, in some systems, we can only generate CSV consent for specific emails.
If the data comes in CSV format, how can we map the idSpecific using the UI? We need to use idSpecific because a user might have different email addresses and consent status for each of these emails.
For example, our data is in a table format like this:
membershipID | consent | |
abc123 | test_1@example.com | y |
abc123 | test_2@example.com | n |
How can we map this data in the UI as an idSpecific object like below? Wondering if we can use any wildcard char for this mapping works?
"idSpecific": {
"email": {
"test_1@example.com": {
"marketing": {
"email": {
"val": "y"
}
}
},
"test_2@example.com": {
"marketing": {
"email": {
"val": "n"
}
}
}
}
}
Thanks,
Imv
Solved! Go to Solution.
"consents": { "collect": { "_adobexxxxxx": { "Email": f"john.smith{i}@abc.com" }, "val": "y" }
"consents": { "collect": { "_adobeqxxxxxx": { "Email": f"john.smith11{i}@abc.com" }, "val": "n"}
similar post I found in community. this should help
Views
Replies
Total Likes
Views
Replies
Total Likes
@bestImv create a custom field group and pass multiple email address in an array, assuming membership id is primary key you can map multiple emails with consents.
Ideally you will create a custom consent field group and pass consent for other channels within the same field group
Hope that helps
Anil
"consents": { "collect": { "_adobexxxxxx": { "Email": f"john.smith{i}@abc.com" }, "val": "y" }
"consents": { "collect": { "_adobeqxxxxxx": { "Email": f"john.smith11{i}@abc.com" }, "val": "n"}
Thanks @Anil_Umachigi for the suggested solution, we are now implementing it.
Cheers,
Imv