This article explains how to export a contact list through the MAAC platform, and how to use the data mapping fields to organize data or prepare for an import update.
# Export the contact list
Path:
Audience > Contacts > "More Actions" in the upper-right corner > Export Contacts
Export format:
The export file is in
.csvformatUp to 100,000 contacts can be exported each time (depending on your contract plan)
Export options
Click 【Export】 in the upper-right corner of the contacts page to select the export scope as needed:
- Export all contacts
- Export reachable contacts
- Export not reachable contacts
- Export conflict contacts — download the list of contacts currently in an identity conflict state (for the fields and steps, see "Export the conflict contact list" below)
📌 The export scope follows the filters currently applied to the contact list. If you filter the list by the 【SMS】 channel first, the export contains SMS contacts.
Examples of exportable fields:
| Field name | Description |
|---|---|
| external_member_id | External platform identifier: may be a LINE UID, Facebook ID, or Instagram ID; for an SMS contact, it is that contact's phone number |
| name | Display name |
| phone | Contact phone |
| tags | Contact tags (comma-separated) |
| customer_id | Brand-defined contact ID |
| note | Note field |
| create_time | Created time |
| last_update_time | Last updated time |
| All custom fields | If custom fields have been created, they are displayed as well |
# Export the conflict contact list
When the system detects an identity conflict between contacts caused by inconsistent Customer IDs, an indicator appears on the 【Export】 button, and 【Export conflict contacts】 is offered in the menu. If there are currently no conflicts, no action is needed.
Conflict list CSV fields
The CSV downloaded via 【Export conflict contacts】 contains all contacts that are "currently still in a conflict state", including the following fields:
| Field | Description |
|---|---|
| unified_contact_id (UCID) | Unified Contact ID |
| platform_type | Channel platform type (for example, line) |
| platform_name | Channel platform name (for example, the Official Account name) |
| external_member_id | External platform identifier |
| customer_id | The customer identifier defined by the brand |
| display_name | Contact display name |
| phone | Contact phone |
| conflict_reason | Conflict reason (for example, customer_id_multiple) |
| conflict_cid | The other Customer ID where the conflict was detected (the Customer ID that is inconsistent with this record's customer_id and caused the contacts not to be merged automatically) |
👉 After obtaining the list, correct the wrong Customer ID or add the correct identifying data, then re-import: Tutorial | Import and Update Contact Data in MAAC. For the conflict detection mechanism, see: Feature Description｜Contact Field Definitions and Matching Logic.
# How to use exported data to map import fields
The export file can serve as a reference and import template source for updating contact data later. Please note the following:
1. external_member_id field mapping:
| external_member_id type | Mappable import Key value | Notes |
|---|---|---|
| LINE UID | line_uid |
Recommended for updating LINE contacts using this field |
| Facebook ID | Not supported | Facebook contacts cannot be imported for now |
| Instagram ID | Not supported | Instagram contacts cannot be imported for now |
| Phone number (SMS contact) | mobile | Select the SMS channel in the import flow to add or update SMS contacts |
2. How to organize it into the import format:
Using the exported data, keep the following fields, edit the content as needed, then save it as a .csv file to update contacts:
line_uid (or phone / customer_id)
name / email / phone / note / tags
Custom fields (the field names must match the back-end settings)
⚠️ If you use phone as the matching field, the system will update the contact that was created later (SMS contacts are uniquely identified by phone number, so one number never has more than one SMS contact)
⚠️ Avoid leaving import fields empty; empty fields will not overwrite the original data
# FAQs
Q1: Why are the custom fields I created not in the export file?
A: Please confirm whether the field has been applied to the contact data; if there is no content, it will not appear in the export result.
Q2: Is external_member_id the same as line_uid?
A: Not necessarily. external_member_id is a unified field; its actual content varies by source platform (line_uid for LINE, fb_id for Facebook, ig_id for Instagram, and the phone number for SMS).
For further details, see: Tutorial | Import and Update Contact Data in MAAC