This article summarizes the elements to consider when importing contact opt-ins. It complements the article Importing Contacts With an External File, which provides the full process.
1. Opt-In Fields
Before importing, you must create opt-in fields. The opt-in fields are used to receive the consent status for a communication type (subscribed, unsubscribed or empty). You can check the opt-in fields created in your project by going to the project's field list. When you create an opt-in field, an opt-in date field is generated automatically for this opt-in (you won't see this field in the project list, but you will be able to select it during the field mapping).
2. Import File
The file to upload must contain a column for the consent status and it is strongly recommended to include another column for the opt-in/opt-out date.
How to indicate the consent status?
- 1 if the contact has subscribed.
- 0 if the contact has unsubscribed.
- Empty, meaning that no status exists for this contact (neither subscribed nor unsubscribed).
3. Field Mapping
In the field mapping, indicate which opt-in field will receive the consent status (1, 0 or empty) and the one that will receive the opt-in date:
In the field dropdown list, you must scroll down to find the OPT-INS section. In this section, you will see a field for the opt-in status and another for the opt-in date for each opt-in created in the project. The opt-in date field is generated automatically when an opt-in field is created in the project.
You haven't included the column for the opt-in dates in the imported file?
If there are no opt-in dates in the imported file, you will asked to provide a date to apply for all the opt-ins/opt-outs of the imported contacts.
If the date is different from the AAAA.MM.JJ format, you must select the format used in the import file:
Results
Once the mapping and the import are done, the opt-in data are shown in the contact's profile.