Skip to main content

Bulk Import Personas

File uploads let you quickly add or update Personas in bulk. This is useful for migrations, filling missing records, or creating targeted audiences. Uploaded customers automatically form an audience.

Updated over 3 weeks ago

Prerequisites:

Before getting started, ensure you have:

Required Permissions:

The Bulk Import feature is available to users with the following permissions:

  • Owner

The file imported into AIQ must:

  • Have only one tab

  • Be a .csv or .xlsx file


How to Import Personas

  • Navigate to Customers > Personas and click Add (+)

  • Click the button "Bulk Import Personas"

  • Here you can see which column headers you can use in your file.

    • Click All Headers to see all possible column headers

  • Click Upload File and select your import file

  • Review each column mapping to confirm it is correct. Automatically mapped columns will be marked with a checkmark.

  • Unmapped columns will be marked with an "X". If a column isn't mapped:

    • In the Property column, click the property dropdown and select the appropriate field.

    • Repeat for other unmapped columns as necessary.

  • Click the checkbox under the Ignore column to prevent that row from being imported entirely.

  • Once all column mappings are addressed, click Next.

  • On the Upload Details page you can customize the name of the import. There will also be an estimate of how many personas will be uploaded and how many fields have been mapped.

  • Import Options:

    • Opt-in all imported personas to email if turned on will override any opt in status provided within your import file and sets all personas included optin statuses to True.

    • Opt-in all imported personas to SMS if turned on will override any opt in status provided within your import file and sets all personas included optin statuses to True.

    • Agree to Alpine persona terms (required for import)

  • Click Import Personas


View Import History

In order to see import history, or previous files you've uploaded:

  1. Navigate to Customers > Personas

  2. Click on the more (...) icon in the top right corner of the personas table

  3. Click on "View Import History"

To re-download the CSV or view the file import as an audience:

  1. Navigate to "View Import History"

  2. Click on a file (row) in the table

  3. Click on the more (...) icon

  4. Click on "Download CSV" or "View Audience"


Import Examples

Below are common examples of how file uploads can be used to import and update Personas in AIQ.

Import Persona Templates

Use this template to import customers from a previous loyalty or marketing provider.

Sample file:

Set SMS Opt-In and Opt-Out Statuses

Use this template to manage SMS consent statuses for existing or new Personas.

Sample file:


aiq-import-sms-statuses.csv

Example behavior:

  • jane@company.com is currently opted in but needs to be opted out. Set the Explicit SMS Opt-out column to TRUE.

  • john@company.com and mburns@company.com already exist in AIQ but are not opted in. Use the Opt-in SMS column to opt them in and ignore the Explicit SMS Opt-out column.

Important notes:

  • Ensure you have proper consent before opting customers in to SMS.

  • Only Personas included in the file will have their SMS opt-in or opt-out status updated.

Add or Subtract Loyalty Points

Use this template to adjust loyalty point balances in bulk.

Sample file:


How it works:

  • The Points column adds to or subtracts from a Persona’s existing balance.

  • This upload does not overwrite or set the total point balance.

Example behavior:

Set Customer Type (Veteran, Police, Locals, etc.)

Use this template to assign customer types or special attributes.

Sample file:

How it works:

  • The Customer Type column is reserved for medical and recreational statuses.

  • Use Custom Attribute columns for all other customer types (for example, veteran or police).

  • Set custom attributes to TRUE to apply them to the Persona.


Bulk Import FAQs

How do I ensure I'm not creating duplicate personas on upload?

We match on phone or email, so a phone or email must be included in your file upload to address duplicate personas.

How long do persona imports take to make changes?

Imports take 24 hours to process. File deletions also take 24 hours to process. Generated audiences are not populated for the 24 hours.

Does the Points column in my spreadsheet add/subtract points to the persona's balance OR does it set the balance to the number in the spreadsheet?

It adds/subtracts points. It does NOT set the total balance.

If a retailer uploads a list of customer data and the data for that customer is different than whats getting pulled in from the POS, would the manual upload override the POS data?

Not by default. In general, the first value AIQ receives for a given customer attribute is the value that “wins” and is retained on the customer’s persona. A manual upload won’t overwrite POS-synced data automatically.

The exception is when the upload includes an explicit override field. For example, if the retailer includes a Signup Override Date column, that override value will take precedence over the existing signup date. If no override field is provided, the customer’s original signup date remains the signup date on their persona.

Do I need to add a "loyalty status:true/false" column?

You can add a “loyalty” column, but it’s not needed since the system will auto-enroll any profile that is having points added to it.

If there is a points balance not equal to 0 (zero), or a text opt-in value set to true on ANY persona within the file, they will automatically be opted into loyalty as well.

Additionally, setting loyalty = false, does not opt out the personas from loyalty if they are currently a loyalty member.

If I upload a file without names (only phone and/or email), can we still import their loyalty points?

Yes, we just need phone and/or email to create persona and import their points.

Need Help?

If you need help with your bulk import please reach out to AIQ Support through the chat widget in your dashboard.

Did this answer your question?