ODP data structure

At the core of ODP areCustomers.

Every customer has a record ofEvents that they have performed over time. Every event is classified by anEvent Type (such as order, product, email) andEvent Action (such as purchase, view, open) and additional metadata stored inFields (such as, product_id).

ODP considers customers and eventsObjects similar to a spreadsheet or a database table. Objects consist ofFields to store metadata and information about the data within the object.

📘

Example

The event object has ats (timestamp) field to store the time at which an event happened and the customer object has anemail field to store the last seen email for the customer.

ODP also supportsCustom Fields andCustom Objects to customize schema for your business needs (such as aConcert Tickets object).

ODP accounts

ODP segregates data viaAccounts and each account has a uniqueTracker ID (also referred to as a Public API Key) to separate its data from other ODP client data.

📘

Note

ODP APIs and SDKs use the Tracker ID to determine where to send data.

Common reasons to use multiple ODP accounts include:

• Multiple brands
• International stores
• Business uses multiple e-commerce instances (such as multiple Shopify stores)

Updated 25 days ago

• Customers
• Events