Customer data is used to create segmentation, reports, and personalized customer content. The import of customer data is typically broken into two parts - uploading historical data and syncing ongoing data. The historical upload is generally done via files and the ongoing sync via APIs; however, both approaches can be used for either data type.
- Customer fields reference: This will direct you to the Objects & Fields section of your account, where you can review your existing default and custom customer fields.
- Creating custom fields: An article outlining the creation and review of custom customer fields.
- Adding customers to lists: An article showing how to add customers to email lists, rather than adding attributes about a customer.
- Adding customer events: An article showing how to integrate customers events (actions) into your account.
Upload Historical Data
Import all customers and the metadata associated with them. This is especially important if your customer data is currently in a system that does not integrate directly with ODP, or if you have custom attributes key to your business.
The example below shows a correctly formatted customer import. File names for these imports begin with zaius_customers.
Importing Custom Information
You will need to create custom fields if your import contains information that does not align with existing ODP fields. Once you have created a suitable field, you can import the associated information by including the field name (home_store) as a header in your import. Do not use the display name (Home Store).
Importing Marketing Consent Information
In ODP, marketing consent is an attribute of each identifier (e.g., each email address), not the customer, and is not updated by the method above. If no value is provided for consent (null), consent is implied. To set an explicit consent value or learn more about consent in ODP, please reference this article.
Sync Ongoing Data
To capture ongoing customer data, you will want to track when a customer subscribes on a form, orders, logs in, registers for an account, etc. Essentially we recommend tracking any instance where a customer can identify themselves. This identification may be through identifiable information explicitly provided in the submission, such as an email, or it may be associated with their tracking information and the associated customer ID.
In either case, ODP will review the identifiable information when this data syncs to your account. If an email or customer ID is provided that is not already in your account, ODP will create a new customer profile. Meanwhile, if the email or customer ID already exists, ODP will update the appropriate fields and events on the existing customer profile instead.
Send customer data through the Customers API.
Send customer data using the JS method.