Step 1. Choose the import type
- Pick the import type — Customers.
- Pick the action:
- Edit existing — updates existing customers only. No new customers are created.
- Add and edit — updates existing customers and loads new ones too.
Step 2. Prepare and upload the file
Work out which fields you need. The file has to contain every required field.The file needs at least one customer identifier: email, phone, or an external ID. All other fields are optional.
Multi-brand accounts: if your account uses multi-brand, the global, channel, and topic subscription columns apply within the brand of the touchpoint. See How to subscribe customers to a brand.
- Format:
.csvor.txt. - Check that the values match the allowed formats.
Step 3. Map the file’s fields
Maestra Platform maps the file’s columns to its own fields automatically. Check the result and adjust it by hand if you need to:- In the Import column, tick the fields you want to load. Unticked columns are skipped.
- In the Maestra field column, map each file column to a field on the account. Optional fields left unmapped are skipped.
Step 4. Configure the import
This step sets extra parameters for the import action:- Data source — the integration point the data came through. Affects how the customer’s actions are attributed. Defaults to the Maestra admin panel.
- Touchpoint — the channel or integration the action is tied to. By default it’s detected automatically from the integration point. To tie customers to a specific website or store, pick the touchpoint manually.
- Segmentation — a static segmentation every customer in the file is added to.
- Comment — a description of the import. Makes it easier to find in the list later.
Set a touchpoint
If the touchpoint you need doesn’t exist yet, create it in advance or from the link on the import page. You can set the touchpoint in two ways:- Every customer in the file has the same touchpoint — pick the integration point with the touchpoint you need in the settings, or set the touchpoint explicitly.
- Customers in the file have different touchpoints — add a
LastUpdatePointOfContactcolumn with the touchpoints’ external IDs to the file. Then tick Take value from file in the settings.
Add to a segment
Pick a static segment. If there’s no suitable one yet, create a new one.Set an action template
You can only set the edit action in the file, and only with a template in the Personal action category. Otherwise, changes to the customer are saved without recording an action.
LastUpdateActionTemplate column with the templates’ system names to the file — this is the system name of the personal action for the customer data change. Then tick Take value from import file in the settings.
Use a different time
There’s no separate time setting. To set the time, add aLastUpdateDateTime column to the file with the date the customer’s data changed, in UTC.
If you leave this column out, the actions are recorded at the time the import task runs.
How to subscribe customers to a brand
On a multi-brand account, the integration point’s brand sets the brand of the customer’s subscription. The subscription is passed through the global subscription, channel subscription, and topic subscription columns. To subscribe customers to several brands at once, run the import again for each brand.1
Find your brand's integration point
Go to the Integrations section.
2
Pick the integration point for the import
Filter by brand and pick an integration point. For example, to subscribe customers to the Demo brand’s campaigns, use that brand’s website integration point.
3
Select that integration point in Step 4. Configure the import
Step 5. Review and start the import
Before you start, Maestra Platform shows the first rows of the file with the mapping already applied. Check that the data looks the way you expect — that the right values landed in the right fields. If everything’s correct, click Start import.How to track the import
Once started, the import appears in the list on the Import page. For each task you’ll see:- start date,
- import type,
- source file with its comment,
- load progress,
- rows imported and errors,
- who started it.
An edit action is issued only when the import actually changed the customer and the file included a
SourceActionTemplate column with a template in the Personal action category.