[title] Ads
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Chord OMS/
### **x\_fct\_unions**
| Name | Description |
| --------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Account Name | The name of the ad account. |
| Account Source Account Id | The unique identifier of the ad account from the source dataset. |
| Account Updated At Date | The timestamp of when an ad account was last updated in the database - Universal Time Zone. |
| Account Updated At Month | The timestamp of when an ad account was last updated in the database - Universal Time Zone. |
| Account Updated At Quarter | The timestamp of when an ad account was last updated in the database - Universal Time Zone. |
| Account Updated At Time | The timestamp of when an ad account was last updated in the database - Universal Time Zone. |
| Account Updated At Week | The timestamp of when an ad account was last updated in the database - Universal Time Zone. |
| Account Updated At Year | The timestamp of when an ad account was last updated in the database - Universal Time Zone. |
| Ad Name | The name of the ad. |
| Ad Source Ad Id | The unique identifier of the ad from the source dataset. |
| Ad Status | The status of the ad. |
| Ad Updated At Date | The timestamp of when an ad was last updated in the database - Universal Time Zone. |
| Ad Updated At Month | The timestamp of when an ad was last updated in the database - Universal Time Zone. |
| Ad Updated At Quarter | The timestamp of when an ad was last updated in the database - Universal Time Zone. |
| Ad Updated At Time | The timestamp of when an ad was last updated in the database - Universal Time Zone. |
| Ad Updated At Week | The timestamp of when an ad was last updated in the database - Universal Time Zone. |
| Ad Updated At Year | The timestamp of when an ad was last updated in the database - Universal Time Zone. |
| Ad Group Name | The name of the ad group or ad set of the ad. |
| Ad Group Source Ad Group Id | The unique identifier of the ad group or ad set for the ad. |
| Ad Group Status | Status of the ad group or ad set. |
| Ad Group Updated At Date | The timestamp of when an ad group or ad set was last updated in the database - Universal Time Zone. |
| Ad Group Updated At Month | The timestamp of when an ad group or ad set was last updated in the database - Universal Time Zone. |
| Ad Group Updated At Quarter | The timestamp of when an ad group or ad set was last updated in the database - Universal Time Zone. |
| Ad Group Updated At Time | The timestamp of when an ad group or ad set was last updated in the database - Universal Time Zone. |
| Ad Group Updated At Week | The timestamp of when an ad group or ad set was last updated in the database - Universal Time Zone. |
| Ad Group Updated At Year | The timestamp of when an ad group or ad set was last updated in the database - Universal Time Zone. |
| Campaign Advertising Channel Type | The type of advertising channel being used by the campaign. |
| Campaign End Date Date | The date when the ad campaign ends - Universal Time Zone. |
| Campaign End Date Month | The date when the ad campaign ends - Universal Time Zone. |
| Campaign End Date Quarter | The date when the ad campaign ends - Universal Time Zone. |
| Campaign End Date Time | The date when the ad campaign ends - Universal Time Zone. |
| Campaign End Date Week | The date when the ad campaign ends - Universal Time Zone. |
| Campaign End Date Year | The date when the ad campaign ends - Universal Time Zone. |
| Campaign Name | The name of the ad campaign. |
| Campaign Source Campaign Id | The unique identifier of the ad campaign from the source dataset. |
| Campaign Start Date Date | The date when the ad campaign starts - Universal Time Zone. |
| Campaign Start Date Month | The date when the ad campaign starts - Universal Time Zone. |
| Campaign Start Date Quarter | The date when the ad campaign starts - Universal Time Zone. |
| Campaign Start Date Time | The date when the ad campaign starts - Universal Time Zone. |
| Campaign Start Date Week | The date when the ad campaign starts - Universal Time Zone. |
| Campaign Start Date Year | The date when the ad campaign starts - Universal Time Zone. |
| Campaign Status | The status of the ad campaign. |
| Campaign Updated At Date | The timestamp of when an ad campaign was last updated in the database - Universal Time Zone. |
| Campaign Updated At Month | The timestamp of when an ad campaign was last updated in the database - Universal Time Zone. |
| Campaign Updated At Quarter | The timestamp of when an ad campaign was last updated in the database - Universal Time Zone. |
| Campaign Updated At Time | The timestamp of when an ad campaign was last updated in the database - Universal Time Zone. |
| Campaign Updated At Week | The timestamp of when an ad campaign was last updated in the database - Universal Time Zone. |
| Campaign Updated At Year | The timestamp of when an ad campaign was last updated in the database - Universal Time Zone. |
| Insight Ad Network Type | The network type used across the account. This field is native to Google and YouTube and fileld with the ad source for other sources. |
| Insight Date Date | The date of the insight - Universal Time Zone. |
| Insight Date Month | The date of the insight - Universal Time Zone. |
| Insight Date Quarter | The date of the insight - Universal Time Zone. |
| Insight Date Time | The date of the insight - Universal Time Zone. |
| Insight Date Week | The date of the insight - Universal Time Zone. |
| Insight Date Year | The date of the insight - Universal Time Zone. |
| Source | The source of the Ad dataset - Google, Facebook, Tiktok, etc. |
| Average Clicks | The number of paid and earned clicks that occurred on the day of the record. |
| Average Impressions | The number of paid and earned impressions - the number of times an ad appeared on the page - that occurred on the day of the record. |
| Average Link Clicks | The number of link clicks on the ad's text, media or call-to-action that link to destinations or experiences specified by the advertiser. This metric excludes clicks on content or links in the comments section of a post. Currently, only Facebook Ads sourced insights surface this data. |
| Average Spend | The estimated total amount of spend that occurred on the day of the record. |
| Total Clicks | The number of paid and earned clicks that occurred on the day of the record. |
| Total Impressions | The number of paid and earned impressions - the number of times an ad appeared on the page - that occurred on the day of the record. |
| Total Link Clicks | The number of link clicks on the ad's text, media or call-to-action that link to destinations or experiences specified by the advertiser. This metric excludes clicks on content or links in the comments section of a post. Currently, only Facebook Ads sourced insights surface this data. |
| Total Spend | The estimated total amount of spend that occurred on the day of the record. |
[title] Sessions
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Chord OMS/
### x\_fct\_trans\_sessions
| Name | Description |
| -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Anonymous Completed Oms Order Ids | Array of OMS Order IDs associated to the anonymous\_id, as collected by order completed or checkout completed front-end events, over time. |
| Anonymous Completed Order Ids | Array of order IDs associated to the anonymous\_id, as collected by order completed or checkout completed front-end events, over time. |
| Anonymous Completed Order Numbers | Array of order numbers associated to the anonymous\_id, as collected by order completed or checkout completed front-end events, over time. |
| Anonymous Current Blended User Id | Unique id derived from the user\_id and the anonymous\_id. Whenever a customer has a user\_id, the user\_anonymous\_id will be constant for |
| Anonymous Current User Id | The current user\_id associated with the anonymous\_id. This unique user\_id is created by Segment's Identify call. A user\_id can be associated to many anonymous\_ids. |
| Anonymous Id | Unique id created by Chord for each anonymous visitor per store. |
| Anonymous Segment Anonymous Id | Id created by Segment for each anonymous visitor. This id gets created as soon as a customer's browser loads the analytics javascript widget. The anonymous\_id remains unchanged through the entire browsing session from a single device. Depending on configuration, two stores connected stores may have the same anonymous\_id. |
| Anonymous Unique User Ids | Array of user IDs mapped to an anonymous ID. |
| Attribution Point First Touch | The first session associated with the user prior to conversion receives 100% of the attribution, all other sessions recieve 0 points. Reflected with a value of 0 or 1. |
| Attribution Point Forty Twenty Forty | The first and last sessions associated with the user prior to conversion receive 40% of the attribution points each, the remaining middle-touch sessions receive an equal portion of the 20%; 0.4, 0.4, and 0.2/number of remaining sessions. |
| Attribution Point Id | Sessions for a user that occor prior to conversion, or first completed order. |
| Attribution Point Last Touch | The last session associated with the user prior to conversion receives 100% of the attribution, all other sessions recieve 0 points. Reflected with a value of 0 or 1. |
| Attribution Point Linear | All sessions for the user prior to conversion recieve an equal percentage of the attribution points; calculated as 1.0 / number of sessions |
| Customer Type | Classification of the user during the session based on their overall order history (regardless of order filtering criteria): * **Prospective customer**: User with no prior orders and no order in the current session.
* **New customer**: User having their first order in or before the current session.
* **Repeat customer**: User having their 2nd or more orders in or before the current session. |
| End Date Day Num Of Year | The number representing the day of the year. |
| End Date Id | Unique key that uniquify a date. |
| End Date Month Num Of Year | The month number of the year. |
| Landing Page Browser Locale | Locale of browser. |
| Landing Page Device | The device on which the event was sent from. |
| Landing Page Device Category | The device category of the device on which the event was sent from. There are multiple supported values for this column such as 'iPhone', |
| Landing Page Event Table Name | The properly formatted name of the table of the event. |
| Landing Page Event Text | The name of the event. |
| Landing Page Event Text Id | The slug of the event name, mapping to the page or track event table. |
| Landing Page Gclid | The Google Click ID. Google Click ID (GCLID) is a parameter passed in the URL with ad clicks, to identify the campaign and other attributes of the click associated with the ad for ad tracking and campaign attribution. |
| Landing Page Id | Unique key generated by Segment for each tracking or page event. |
| Landing Page Oms Id | Unique key generated by our models that uniquifies an OMS. |
| Landing Page Host | The host of the event's URL. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev`. This facilitates grouping events by host. |
| Landing Page Path | The page path part of the URL. A page path is the part of URL that comes after the hostname (domain) and before the query parameters, URL fragment, or port. (e.g. `/pages/contact-us/` for `https://chord.co/pages/contact-us/?ref=internal-banner` .) |
| Landing Page Query | The query string portion of the URL of the page. |
| Landing Page Referrer | The referrer of the page. The referrer is the webpage that sends visitors to the site using a link. In |
| Landing Page Title | The title/name of the page. |
| Landing Page Url | The URL of the page. |
| Landing Page Referrer Host | The host of the referrer. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev`. This facilitates grouping events by host. |
| Landing Page Segment User Id | The unique ID of the user. |
| Landing Page Store Id | Unique key generated by our models that uniquifies a store. |
| Landing Page Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Landing Page User Agent | The User agent of the device making the request. A User agent request header is a characteristic string that lets servers and |
| Landing Page User Id | Unique key generated by Chord to identify the user. |
| Landing Page Utm Campaign | The campaign name represented by the UTM tags. |
| Landing Page Utm Content | The campaign content represented by the UTM tags. |
| Landing Page Utm Medium | The campaign medium represented by the UTM tags. |
| Landing Page Utm Source | The campaign source represented by the UTM tags. |
| Landing Page Utm Term | The campaign term represented by the UTM tags. |
| Landing Page Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store |
| Last Page Browser Locale | Locale of browser. |
| Last Page Device | The device on which the event was sent from. |
| Last Page Device Category | The device category of the device on which the event was sent from. There are multiple supported values for this column such as 'iPhone', |
| Last Page Event Table Name | The properly formatted name of the table of the event. |
| Last Page Event Text | The name of the event. |
| Last Page Event Text Id | The slug of the event name, mapping to the page or track event table. |
| Last Page Gclid | The Google Click ID. Google Click ID (GCLID) is a parameter passed in the URL with ad clicks, to identify the campaign and other attributes of the click associated with the ad for ad tracking and campaign attribution. |
| Last Page Id | Unique key generated by Segment for each tracking or page event. |
| Last Page Oms Id | Unique key generated by our models that uniquifies an OMS. |
| Last Page Host | The host of the event's URL. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev`. This facilitates grouping events by host. |
| Last Page Path | The page path part of the URL. A page path is the part of URL that comes after the hostname (domain) and before the query parameters, URL fragment, or port. (e.g. `/pages/contact-us/` for `https://chord.co/pages/contact-us/?ref=internal-banner`.) |
| Last Page Query | The query string portion of the URL of the page. |
| Last Page Referrer | The referrer of the page. The referrer is the webpage that sends visitors to the site using a link. In |
| Last Page Title | The title/name of the page. |
| Last Page Url | The URL of the page. |
| Last Page Referrer Host | The host of the referrer. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev`. This facilitates grouping events by host. |
| Last Page Segment User Id | The unique ID of the user. |
| Last Page Store Id | Unique key generated by our models that uniquifies a store. |
| Last Page Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Last Page User Agent | The User agent of the device making the request. A User agent request header is a characteristic string that lets servers and |
| Last Page User Id | Unique key generated by Chord to identify the user. |
| Last Page Utm Campaign | The campaign name represented by the UTM tags. |
| Last Page Utm Content | The campaign content represented by the UTM tags. |
| Last Page Utm Medium | The campaign medium represented by the UTM tags. |
| Last Page Utm Source | The campaign source represented by the UTM tags. |
| Last Page Utm Term | The campaign term represented by the UTM tags. |
| Last Page Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store |
| Session Activity Count | Total count of activities, pave views and tracked events within the session. |
| Session Attribution Channel | The attribution channel for the first page event of the session. Sessions with an attribution of 'Unknown' indicates that there is no attributable data for that session. |
| Session Attribution Channel Paid Or Organic | Indicates if the session's first page attribution is paid or organic. Attribution is considered Organic if the attribution channel is 'Direct', 'Other', 'Organic Search', 'Organic Social', 'Email', or 'SMS'. |
| Session Attribution First Page Url Has Gclid | Indicates if the first page event of the session has a Google Click ID. |
| Session Attribution First Page Url Has Utm | Indicates if the first page event of the session has any utm information. |
| Session Attribution Has Referrer | Indicates if the first page event of the session has a referrer host. |
| Session Attribution Medium | The campaign medium represented by the UTM tags for the first page event of the session. |
| Session Attribution Source | The campaign source represented by the UTM tags for the first page event of the session. |
| Session Attribution Sub Channel | Sub-Channel is a granular level of attribution. |
| Session Completed Oms Order Ids | Array of OMS Order IDs associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Session Completed Order Ids | Array of order IDs associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Session Completed Order Numbers | Array of order numbers associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Session Days Since Last Session End | The days between the last session's end and the start of this session. |
| Session Device | The device on which the event was sent from. |
| Session Device Category | The device category of the device on which the event was sent from. There are multiple supported values for this column such as 'iPhone', |
| Session Duration In Seconds | Total seconds between start and end activities within the session. |
| Session Duration In Seconds Tiers | Total seconds between start and end activities within the session, aggregated into tiers: 0-9s, 10-29s, 30-59s, and 60s or more. |
| Session Has Order Completion | Flag for sessions with an order completed or checkout completed front-end events |
| Session Id | Unique ID for the session. |
| Session Number | Session number per anonymous id. |
| Session Unique Completed Order Count | Count of unique order ids associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Session Unique Completed Order Number Count | Count of unique order numbers associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Start Date Day Num Of Year | The number representing the day of the year. |
| Start Date Id | Unique key that uniquify a date. |
| Start Date Month Num Of Year | The month number of the year. |
| Store Id | Unique key generated by our models that uniquifies a store. |
| Store Name | The name of the store. |
| Store Oms Admin Url | The Admin URL of that OMS. |
| Store Oms Id | Unique key generated by Chord that uniquifies an OMS. |
| Store Oms Store Id | Unique key generated by our models that uniquifies a store. |
| Store Oms Type | The type of the OMS. |
| Store Id | Unique key generated by our models that uniquifies a store. |
| Store Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Store Url | The Storefront URL of of the store. |
| User Address 1 | The first line of the street address. |
| User Address 2 | The optional second line of the address. |
| User Address City | The city of the address. |
| User Address Country | The country of the address. |
| User Address Name | The full name of the customer, based on firstName and lastName. |
| User Address State | The region of the address, such as the province, state, or district. |
| User Address Zip | The postal code of the address. |
| User Completed Oms Order Ids | Array of OMS Order IDs associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| User Completed Order Ids | Array of order IDs associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| User Completed Order Numbers | Array of order numbers associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| User Email | The email associated with the user. |
| User Id | Unique ID per user. It is equal to either 1) a identified\_user\_id as identified by Segment in the Identify call, or 2) an anonynous\_id. |
| User Identified User Id | Unique ID per identified user. (See Segment's documentation on user\_id)\[ `https://segment.com/docs/connections/spec/identify/#user-id` ]. |
| User Ip | IP address associated with the user. |
| User Last Anonymous Id | Last seen anonymous\_id per user. An anonymous\_id is a unique ID per anonymous visitor. (See Segment's documentation on anonymous\_id)\[ `https://segment.com/docs/connections/spec/identify/#anonymous-id` ]. |
| User Last Segment Anonymous Id | This column is not documented. |
| User Segment User Id | The unique ID of the user. |
| User Unique Anonymous Ids | Array of all seen anonymous\_ids per user. An anonymous\_id is a unique ID per anonymous visitor. (See Segment's documentation on anonymous\_id)\[ `https://segment.com/docs/connections/spec/identify/#anonymous-id` ]. |
| User Unique Completed Order Count | Count of unique order ids associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| Visitor Type | Classification of the visitor during the session based on their overall session history: * **New Visitor**: Firt session of an user.
* **Returning Visitor**: Second or more session of an user. |
| End Ts (Universal) | Last activity timestamp for a session - Universal Time Zone. |
| Landing Page Ts (Universal) | The timestamp calculated by Segment correcting clock skew - Universal Time Zone. |
| Last Page Ts (Universal) | The timestamp calculated by Segment correcting clock skew - Universal Time Zone. |
| Session End Ts (Universal) | Last activity timestamp for a session - Universal Time Zone. |
| Session Last Session End Ts (Universal) | The timestamp of the previous session's end per blended user id, if this is not the user's first session - Universal Time Zone. |
| Session Last Session Start Ts (Universal) | The timestamp of the previous session's start per blended user id, if this is not the user's first session - Universal Time Zone. |
| Session Start Ts (Central) | First activity timestamp for a session - Cental Time Zone. |
| Session Start Ts (Eastern) | First activity timestamp for a session - Eastern Time Zone. |
| Session Start Ts (Mountain) | First activity timestamp for a session - Mountain Time Zone. |
| Session Start Ts (Pacific) | First activity timestamp for a session - Pacific Time Zone. |
| Session Start Ts (Universal) | First activity timestamp for a session - Universal Time Zone. |
| Start Ts (Central) | First activity timestamp for a session - Cental Time Zone. |
| Start Ts (Eastern) | First activity timestamp for a session - Eastern Time Zone. |
| Start Ts (Mountain) | First activity timestamp for a session - Mountain Time Zone. |
| Start Ts (Pacific) | First activity timestamp for a session - Pacific Time Zone. |
| Start Ts (Universal) | First activity timestamp for a session - Universal Time Zone. |
| User Created At (Universal) | The timestamp when the user was created - Universal Time Zone. |
| User First Seen At (Universal) | The first time the user was seen on the site, identified as either anonymous ID or user ID - Universal Time Zone. |
[title] Chord Data Platform
[path] /
As a commerce data platform, we empower brands to not only boost revenue and lower customer acquisition cost (CAC), but also deepen their understanding of customers through our infrastructure that exposes predictive insights, revenue forecasting, and customer lifetime value (LTV).
The following documentation provides an in-depth look at some of the data analytics reporting and dashboard capabilities that our platform provides for our brands.
## How-to guides for the Chord Commerce Data Platform
[Overview](docId\:IRMlL09F3QqFfhx5YQBLV)
[Chord Reveal (Private Beta)](docId\:lG4DUiI1rCULMSsFJ3lHK)
[Audiences](docId\:FNUhk7dhtg2ckYZPI89X0)
[Data Activations](docId\:J_Clf0Rgb1RSE684EjJsw)
[Data Sources](docId\:G9t7c0LomYUgBPvloVV5x)
[Data Models](docId:97ZH8HRn9zWfUGvmxF_lT)
[Predictive Models](docId\:dUoNO1y6jn7cdM_dGZ-U6)
[Analytics Features](docId:--5NO0_4Q7n1jp3jT5FY8)
[Model Amplifications](docId\:egHcUaw0cGhSPCIzIYOvu)
[title] Available Destinations
[path] Chord Data Platform/Data Activations/Data Activations/
Chord's Data Activations solution will allow brands to sync Chord-collected data to various marketing and other data activations destinations, including:
Accredible
ActiveCampaign
Adobe Target
Aha
Airship
Airtable
Algolia
Amazon Ads DSP (AMC)
Amazon DynamoDB
Amazon EventBridge
Amazon Pinpoint
Amazon Redshift
Amazon S3
Amplitude
Anaplan
Antavo
Apollo
Appcues
Asana
AskNicely
Attentive
Attio
Autopilot Journeys
Azure Blob Storage
Blackhawk
Bloomreach
Box
Braze
Brevo (formerly Sendinblue)
Campaign Monitor
Canny
Channable
Chargebee
Chargify
ChartMogul
ChatGPT Retrieval Plugin
Chattermill
ChurnZero
CJ Affiliate
CleverTap
ClickUp
Constant Contact
Courier
Criteo
Crowd.dev
Customer.io
Databricks
Delighted
Discord
Drift
Drip
Eagle Eye
Elasticsearch
Emarsys
Enterpret
Facebook Ads
Facebook Product Catalog
Freshdesk
Freshsales
Front
FullStory
Gainsight
GitHub
GitLab
Gladly
Google Ads
Google AlloyDB
Google Analytics 4
Google BigQuery
Google Campaign Manager 360
Google Cloud Storage
Google Datastore
Google Display & Video 360
Google Drive
Google Search Ads 360
Google Sheets
Heap.io
Help Scout
HTTP Request
HubSpot
Impact
Insider
Insightly
Intercom
Iterable
Jira
Kafka
Kevel
Klaviyo
Kustomer
Labelbox
LaunchDarkly
LinkedIn
LiveIntent
Loops
Mailchimp
Mailchimp Transactional (Mandrill)
Mailgun
Marketo
Meilisearch
Microsoft Advertising
Microsoft Dynamics
Microsoft SQL Server
Microsoft Teams
Mixpanel
MoEngage
Mongo DB
mParticle
MySQL
NetSuite
Notion
OneSignal
Optimizely
Oracle Database
Oracle Eloqua
Oracle Fusion
Oracle Responsys
Orbit
Ortto
Outreach
Pardot
Partnerstack
Pendo
Pinterest
Pipedrive
Planhat
PostgreSQL
PostHog
Postscript
Productboard
Qualtrics
Radar
Reddit Ads
Rokt
RollWorks
Sailthru
Salesforce
Salesforce Commerce Cloud
Salesforce Marketing Cloud
Salesloft
Segment
SendGrid
Sense
SFTP
Shopify
Singular
Slack
Snapchat
Snowflake
Split
Sprig
Statsig
Stripe
The Trade Desk
TikTok
Totango
Unify
Userflow
Userpilot
Vero Cloud
Vitally
Webflow
Webhooks
X Ads (formerly Twitter Ads)
Yahoo Ads (DSP)
Zendesk
Zoho CRM
Zuora
If you don't see your destination listed, please reach out to us at [help@chord.co](mailto\:help@chord.co).
[title] Audiences API
[path] Chord Data Platform/Audiences/
# Overview
Chord's Audiences API allows you to access audiences, along with associated audience attributes, directly via API.
:::hint{type="info"}
Looking for information on how to activate an audience to Ninetailed? Check out our documentation [here](https://docs.chord.co/audience-activations-with-ninetailed)!
:::
# Use cases
- Use the audience "Products Abandoned," which has every visitor's top products last viewed but not yet purchased, to customize the experience on your website for repeat visitors by featuring these users' top products for enhanced personalization and conversion opportunity.
- Create an audience with personalized user attributes, such as new vs. returning visitor, last campaign seen, and more, to test different landing page customizations on your website.
# Getting started
## Data destination
Once your account has the Audiences API enabled, the "Dynamic Audiences API" data destination will be available in Data Activations.
## Audiences
You can use a pre-built audience or create a custom audience you want to activate via the Audiences API.
The audience must use the CDP Blended User ID, which is derived from the Chord data models and contains the CDP User ID, if one exists, else the CDP Anonymous ID. This use case is particularly useful when mixing users who may or may not have a known CDP User ID. By using the CDP Blended User ID, audiences can be created for both users and visitors using the same ID, also allowing us to aggregate all audiences at the Blended User ID level in the API.
## Activations sync
### **Select a source and destination**
Once your destination is enabled and you have the audience you'd like to use, you'll create a sync in Activations. Using our Sync UI, we must create a new sync that connects a custom audience as the source, the Dynamic Audiences API as the destination, and the object as `{name}_audiences`, with the object being pre-configured in the provisioning process.
### **Sync behavior**
Sync Behaviors dictate the types of change that should be applied to your data when a sync finds a matching (or not) record in a source and a destination.
We want to use the "Mirror" option, which will perform the following behaviors for records in the destination:
- Create: This will add new users in a given audience.
- Update: This will change values for users in a given audience. For example, if data like top products change for a given user in an audience, this behavior will update that record in the destination.
- Delete: This will delete values for users no longer in a given audience.
### **Sync key**
Sync Keys will dictate how to associate data in the source with the destination. Both the source and destination need to provide a single, unique per record, identifying field. The identifiers will be used to look for matches. When a match is found, or not found, we can use your selected Sync Behavior to decide what to do. Your sync key can be any unique identifier, like a user ID, an email address, etc. However, we recommend using the CDP Blended User ID provided by Chord to provide user consistency across all datasets, allowing for the best matching in the destination.
### **Field mappings**
Once you've defined *how* data is related between your source and destination, the next step is to determine *what* properties should be updated. The field mapping step lets you specify how fields should be mapped from your source model to the destination object's fields.
- We start by assigning our unique user identifier. `anonymous_current_cdp_blended_user_id` will become our `pk` (primary key).
- We can then set up the `sk` (sort key). It is **important** to ensure that this value reflects the name of the Audience being synced. You can easily obtain that value by choosing `Sync Metadata > Source Name`, which will dynamically populate the name applied to your audience.
You should end up with the following:
**Data Field (Optional)**
The destination supports flexible schemas, allowing you to send any data and define custom names for destination fields.
Make sure to send the content to a `data` destination field:
You must use [Liquid templating](https://shopify.github.io/liquid/basics/introduction) to perform last-mile transformations on your source data.
For example, if your audience contains an `anonymous_id`, `user_id`, and a list of `products` and you'd like to append these data components for use via the API, the following mapping will create a `data` attribute in the API response:
```tsx
{
"anonymous_id": {{ record['ANONYMOUS_ID'] }},
"user_id": {{ record['USER_ID'] }},
"products": {{ record['PRODUCTS'] | raw }}
}
```
Any column can be added to this `data` attribute, making these supplemntary values will be available via API.
## Sync Schedule
Like any other sync on our Data Activations page, it can be scheduled to run at regular intervals:
## Sync Results
The Chord platform will display the sync results as usual:
# How to Make Requests to the Audiences API
## Prerequisites
- An API key provided by Chord, to be used as a bearer token. If you have not received your API key, please reach out to help\@chord.co.
- A unique user identifier that is being used as the `pk` in your Sync.
- It should be included in the request headers.
- Depending on your sync field mapping, it could be an email address, an anonymous ID, a user ID, etc. Chord recommends using the CDP Blended User ID as the primary key
## Request Example
### When CDP Blended User ID is being used as the `pk` in your sync
```json
curl -X GET \
-H "Authorization: Bearer YOUR_BEARER_TOKEN" \
-H "chord-user-id: 7496fd47cc30-143c-4279-6e6e8a7a" \
https://analytics.api.chord.co/audiences
```
## Response Example
### When Blended User ID is being used a the `pk` in your sync
```json
{
"user": "7496fd47cc30-143c-4279-6e6e8a7a",
"audiences": [
{
"name": "Audience - Cart Abandoned",
"data": {
"unique_session_count": 2,
"unique_session_with_completed_order_count": 0,
"user_email": "",
"unique_session_added_product_count": 1
}
}
]
}
```
# Request Sample
Below are example requests, but this will depend on your server-side framework. Audiences API should always be called server-side.
**TypeScript**
```typescript
const userId: string | null = null; // assuming that userId is not known
const anonymousId: string = '7496fd47cc30-143c-4279-6e6e8a7a';
// Use the nullish coalescing operator (??) to fall back to anonymousId
// if userId is null or undefined
const blendedUserId: string = userId ?? anonymousId;
const url: string = 'https://analytics.api.chord.co/audiences';
const headers: HeadersInit = {
'Authorization': 'Bearer YOUR_BEARER_TOKEN',
'Chord-User-Id': blendedUserId
};
async function fetchData() {
try {
const response = await fetch(url, {
method: 'GET',
headers: headers
});
if (!response.ok) {
throw new Error(`HTTP error! Status: ${response.status}`);
}
const data = await response.json();
console.log(data); // Handle the response data here
} catch (error) {
console.error('Error:', error); // Handle errors here
}
}
fetchData();
```
# Troubleshooting and FAQs
- **Question: How do I get access to Audiences API?**
- Please reach out to [help@chord.co](mailto\:help@chord.co) or your account executive for more information about or access to this feature.
- **Question: Can I leverage Chord's audiences API to activate audiences on other platforms?**
- Yes! [You can leverage Chord's audiences API to send audiences to Ninetailed](https://docs.chord.co/audience-activations-with-ninetailed). If you need assistance or have questions about other platforms, please reach out to us at [help@chord.co](mailto\:help@chord.co).
[title] Fairing
[path] Chord Data Platform/Data Sources/Connect Data Sources/
Connect your Fairing survey data to Chord. Fairing is the post-purchase survey platform that captures attribution, demographic, and intent signals from customers right after checkout. Chord ingests the full question catalog and every response so you can model attribution channels, NPS, and post-purchase intent alongside the rest of your stack.
## What Chord ingests from Fairing
Chord pulls 2 datasets from your Fairing account. Each dataset becomes its own table in your Chord Snowflake schema.
- **Questions:** every question in your active question stream: id, type, prompt, response options, randomization settings, customer type, frequency, publish timestamps.
- **Responses:** every customer response captured by Fairing: order id, question id, response text, customer id and email, coupon code if applied, UTM source/medium/campaign, and order creation timestamp.
## Generate a Fairing API key
You'll need your Fairing Secret Key from the dashboard. There are no scopes or permissions to configure, it's a single key that grants read access to the Fairing REST API.
:::hint{type="warning"}
**Heads up:** only users with access to the Fairing **Account** page can view or generate API keys. If your role doesn't include it, ask an admin on the account to either retrieve the key for you or grant your user access.
:::
1. Log in to your Fairing dashboard (either directly at app.fairing.co or via your Shopify store's Apps section).
2. Click **Account** in the navigation.
3. Scroll to the **API Keys** section (also labeled "API Credentials" in some accounts).
4. Find the **Secret Key** row and click to unhide / reveal it.
5. Copy the key value.
## Connect the key in Chord
1. Open Chord Hub and go to **Data Sources → Add Source**.
2. Pick **Fairing** from the data source list.
3. Paste the Secret Key you just copied into the **API Key** field.
4. Click **Save.** Chord makes a test call against the Fairing questions endpoint to confirm the key works.
5. The first sync kicks off automatically; subsequent syncs run on your tenant's standard ingestion schedule.
## Troubleshooting
**What does the validate step actually check?**
Chord makes a small read against `https://app.fairing.co/api/questions` and confirms the key returns a 200 response with no authorization error. It does not pull or store any records — that happens on the first scheduled sync after you save the credential.
**The validate step failed. What now?**
Fairing keys don't have scopes, so a 401 means the key value itself is wrong, was rotated, or was copied with extra whitespace (a common issue when copying from a hidden field). Go back to **Account → API Keys** in Fairing, reveal the Secret Key, copy it again carefully, paste it into the same Chord credential entry, and test again.
**Do Fairing API keys expire?**
No. Keys stay valid until someone with Account access manually rotates them in **Account → API Keys**. If a previously working key suddenly fails, check that page first.
**How do I rotate the key?**
Generate a new Secret Key in Fairing's Account page (or ask Fairing support to rotate yours if your dashboard doesn't expose the regenerate option), paste it into the same Chord credential entry, and save. Chord uses the new key on the next scheduled sync.
***
**Need help?** If you hit a credential or connectivity issue you can't resolve, reach out to [help@chord.co](mailto\:help@chord.co) with the exact error message. We'll trace the request and tell you what's failing.
[title] Recommendations Agent
[path] Chord AI/Chord Copilot Chat/
## Introduction
The Recommendations Agent enhances Copilot by offering suggested actions based on the query you submit and the data returned. These recommendations are designed to help you move faster — highlighting next steps you can take without needing to dig deeper on your own.
## How it works
After you ask a question in Copilot, the Recommendation Agent evaluates the result and suggests up to three possible actions. These actions are based on your data and the context of your question.
For example:
- You ask: *“Who are my most loyal customers?”*
- Copilot returns the segment → The Recommendation Agent may suggest: *“Create a segment of these users in Audiences”* or *“Send this group to Meta Ads.”*
## About Confidence Levels
Each recommendation includes a confidence rating — High, Medium, or Low — based on how directly the action connects to your original question and the resulting data.
### Confidence levels are defined as:
- **High**: A clear, logical next step based on the data
*(e.g., Query reveals churning customers → Suggest creating a retention segment)*
- **Medium**: A reasonable action, but with some inference required
*(e.g., Data implies seasonal trends → Suggest campaign timing adjustment)*
- **Low**: Speculative or loosely related
*(e.g., Suggesting product changes based on traffic data alone)*
:::hint{type="info"}
**Note: **Chord displays **all recommendations returned**, regardless of confidence level (up to three per query).
:::
### How Confidence is determined
Confidence levels are determined by the language model (LLM) powering Copilot. We've prompted the model with guidelines like:
- *“Prioritize high-confidence recommendations over speculative ones.”*
- *“Err on the side of fewer, higher-quality recommendations.”*
This means the model self-assesses whether an action is a strong fit for your query. When it's unsure, it’s designed to return fewer or no recommendations, rather than suggest low-confidence actions just to fill space.
### Learning from your actions
Copilot also remembers which recommended actions you take and will use that information to improve future suggestions. Over time, this feedback loop helps the Recommendations Agent prioritize the types of actions you and your team actually finds valuable, making recommendations smarter and more tailored to your workflows.
[title] Chord OMS
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/
### *Table names for customers utilizing the Chord OMS*
- [Activities](https://docs.chord.co/activities)
- [Ads](https://docs.chord.co/c2Te-ads)
- [Conversions](https://docs.chord.co/conversions)
- [Line Items](https://docs.chord.co/line-items)
- [Line Items By Units](https://docs.chord.co/line-items-by-units)
- [Marketing Attribution](https://docs.chord.co/9TGn-marketing-attribution)
- [Orders](https://docs.chord.co/xW-7-orders)
- [Sales](https://docs.chord.co/sales)
- [Sessions](https://docs.chord.co/q_lb-sessions)
- [Stock Requests](https://docs.chord.co/stock-requests)
- [Subscription Events](https://docs.chord.co/subscription-events)
- [Subscriptions](https://docs.chord.co/subscriptions)
- [Transactions](https://docs.chord.co/transactions)
- [Users](https://docs.chord.co/users)
- [Variants](https://docs.chord.co/variants)
### Accessing Chord Data Attribute Definitions:
:::hint{type="success"}
if you have any questions or need help, please reach out to us at [help@chord.co](mailto\:help@chord.co)
:::
[title] Subscriptions Module
[path] Chord Data Platform/Data Sources/
## Introduction
Chord's Subscription Analytics module provides a suite of **7 Explores** designed for self-service subscription analysis.
These Explores:
- Work across Recharge and your OMS
- Provide a unified view of subscription performance
- Support analysis across:
- Customer-level
- Subscription-level
- Product-level
- Lifecycle events
## How to access
1. Log into the Chord Commerce Data Platform
2. Navigate to **Analytics**
3. Click **Explores**
4. Select a **Subscription Explore**
## Quick reference — Which Explore should I use?
Use this as your starting point when you’re not sure where to go.
Each Explore is designed to answer a specific type of business question.
| If your question is about… | What you’re trying to understand | Use this Explore |
| ------------------------------- | --------------------------------------------------- | -------------------------------------- |
| **Overall subscription health** | Are we growing or shrinking? What’s our churn rate? | **Subscription Metrics Daily** |
| **Customer value (LTV)** | Who are our most valuable subscribers? | **Subscriber Journey** |
| **Retention over time** | How long do customers stay? How do cohorts behave? | **Subscriber Journey Monthly** |
| **Behavior leading to churn** | What happens before users cancel? | **Subscription Events Enriched** |
| **Business impact of changes** | How much revenue are we losing from cancellations? | **Subscription Movements Daily** |
| **Product performance** | Which products drive growth or churn? | **Subscription Product Metrics Daily** |
| **Bundle performance** | Which product combinations perform best? | **Subscription Bundle Metrics Daily** |
**You can use this handy guide to start your analysis: **
- Start with **Metrics Daily** → *“What is happening?”*
- Move to **Journey / Monthly** → *“Who is driving this and how does it evolve?”*
- Use **Events** → *“Why is this happening?”*
- Use **Movements / Product / Bundle** → *“Where is the impact coming from?”*
## Key Dimensions & Metrics
[Subscription Metrics Daily Explore](docId\:vrK7FlahNOV_r92ULUJH0)
[Subscriber Journey Explore](docId\:pHLEFk8F-KCnLkaNepm97)
[Subscriber Journey Monthly Explore](docId\:K3t064ARjs6tAEi21ua46)
[Subscription Events Enriched Explore](docId\:PGqIyYRgagkRu-tuwX6jj)
[Subscription Movements Daily Explore](docId\:JjEYNdJwHcf6ua-4ketck)
[Subscription Product Metrics Daily Explore](docId:6lDcTaqrCd0OXvQrVvGOz)
[Subscription Bundle Metrics Daily Explore](docId\:FpvuvhiI9L9Wp4ybhC2Hc)
# Glossary
| Term | What it Means | How to Interpret / Use | Where You’ll See It in Looker |
| ------------------------ | --------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Active Subscription** | A subscription that is currently ongoing. Includes both fully active and paused subscriptions. | Use this to understand the **current size of your subscriber base**. Note that paused users are still counted. | Subscription Metrics Daily (Active Count), Subscriber Journey (Is Active Subscriber), Subscriber Journey Monthly (Is Active Subscriber EOM), Product & Bundle Explores (Active Subscription Count) |
| **Churn / Churned** | A subscription that has been cancelled. Does not include pauses. | Represents **true customer loss**. Track this to understand retention issues. | Subscription Metrics Daily (Churned Count, Churn Rate), Subscriber Journey (Is Churned, Churn Count), Monthly (Is Churned EOM, Cancellations This Month), Events Enriched (Event Type = canceled), Movements (status\_cancelled) |
| **Winback** | A subscriber who cancelled all subscriptions and later returned by subscribing again. | Indicates **successful re-engagement** after churn. | Subscriber Journey (Is Winback), Subscriber Journey Monthly (Has Reactivated By EOM) |
| **Reactivation** | A previously cancelled subscription that becomes active again (subscription-level). | Measures **recovery of churned subscriptions**. | Subscription Metrics Daily (Reactivated Count), Movements (status\_reactivated), Events Enriched (Event Type = reactivated) |
| **Net New** | Net change in subscriptions: New + Reactivated − Cancelled. | Indicates **overall growth vs decline**. | Subscription Metrics Daily (Net New Count) |
| **LTV (Lifetime Value)** | Total revenue generated by a subscriber across all subscription orders. | Use to understand **customer value over time** and compare cohorts or segments. | Subscriber Journey (LTV Gross / Net Revenue), Subscriber Journey Monthly (LTV Gross Revenue EOM) |
| **EOM (End of Month)** | Metrics calculated as of the last day of a month. | Used for **consistent month-over-month comparisons** (retention, LTV growth). | Subscriber Journey Monthly (all EOM fields like Active EOM, LTV EOM) |
| **Solo Subscription** | A subscription that contains only one product. | Helps identify products that perform well **individually**. | Subscription Product Metrics Daily (Solo Subscription Count) |
| **Bundle** | A subscription that contains two or more products. | Useful for analyzing **product combinations and cross-sell behavior**. | Product Metrics (Bundle Subscription Count), Bundle Metrics Daily (all bundle fields) |
| **Movement** | Any change in a subscription’s state (created, cancelled, paused, resumed, reactivated, quantity/price change). | Use to understand **operational changes and trends** in subscriptions. | Subscription Movements Daily (Movement Type, Category), Events Enriched (Event Type) |
| **Provider** | The system managing subscriptions (Recharge, ChordOMS, CustomOMS). | Important context — **data availability and detail vary by provider**, which affects analysis. | All Explores (Provider filter present everywhere) |
[title] Klaviyo Events Data Attribute Definitions
[path] Chord Data Platform/Data Sources/Messaging Module/Untitled/
# Klaviyo Events
### Measures
- **AOV**: Average Order Value
- **Active On Site**: Count of all events of type Active on Site.
- **Bounced Email**: Count of all events of type Bounced Email.
- **Bounced Push**: Count of all events of type Bounced Push.
- **Clicked Email**: Count of all events of type Clicked Email.
- **Clicked SMS**: Count of all events of type Clicked SMS.
- **Email Bounce-to-Send Rate**: Total bounce count / total send count.
- **Email Click Rate**: Total of click email count / total delivery email count.
- **Email Click-to-Open Rate**: Total of all emails clicked / total email open count.
- **Email Conversion-to-Delivery Rate**: Total conversion count / total delivery count.
- **Email Delivery-to-Send Rate**: Total delivery count / total send count.
- **Email Open-to-Delivery Rate**: Total of open email count / total email delivery count.
- **Email Sent**: Sum of Bounced and Received Email
- **Email Unique Click Rate**: Total of all unique emails clicked / total emails sent.
- **Email Unique Click Through Rate**: Total of unique click email count / total delivery email count.
- **Email Unique Click to Open Rate**: Total of unique email clicks / total unique email open count.
- **Email Unique Open Rate**: Total of unique open count / total delivery count.
- **Email Unsubscribe Rate**: Total unsubscribe from email count / total delivery email count.
- **Failed to Delivery SMS**: Count of all events of type Failed to Delivery SMS.
- **Marked Email as Spam**: Count of all events of type Marked Email as Spam.
- **Opened Email**: Count of all events of type Opened Email.
- **Opened Push**: Count of all events of type Opened Push.
- **Ordered Product**: Count of all events of type Ordered Product.
- **Placed Order**: Count of all events of type Placed Order.
- **Push Bounce-to-Send Rate**: Total bounce count / total send count.
- **Push Sent**: Sum of Bounced and Received Mobile Push
- **Push Unique Open Rate**: Total of all unique pushes clicked / total pushes sent.
- **Received Email**: Count of all events of type Received Email.
- **Received Push**: Count of all events of type Received Push.
- **Received SMS**: Count of all events of type Received SMS.
- **Recipients**: Count of all unique events of type Received Email based on person\_id as Last Touch ID.
- **Refunded Order**: Count of all events of type Refunded Order.
- **SMS Failed-to-delivery Rate**: Total of all failed SMS messages / total SMS sent.
- **SMS Unique Click Rate**: Total of all unique SMS clicked / total SMS sent.
- **Sent SMS**: Count of all events of type Relayed SMS.
- **Subscribed To Back In Stock**: Count of all events of type Subscribed to Back In Stock.
- **Subscribed To Email Marketing**: Count of all events of type Subscribed To Email Marketing.
- **Subscribed To List**: Count of all events of type Subscribed to List.
- **Subscribed to SMS Marketing**: Count of all events of type Subscribed to SMS Marketing.
- **Subscribed to SMS Transactional**: Count of all events of type Subscribed to SMS Transactional.
- **Total Cancelled Order**: From numeric\_value field, the sum of all events where the event type is Cancelled Order.
- **Total Checkout Started**: From numeric\_value field, the sum of all events where the event type is Checkout Started.
- **Total Ordered Product**: From numeric\_value field, the sum of all events where the event type is Ordered product.
- **Total Placed Order**: From numeric\_value field, the sum of all events where the event type is Placed Order.
- **Total Refunded Order**: From numeric\_value field, the sum of all events where the event type is Refunded Order.
- **Unique Active On Site**: Count of all unique events of type Active on Site based on person\_id as Last Touch ID.
- **Unique Bounced Push**: Count of all unique events of type Bounced Push based on person\_id as Last Touch ID.
- **Unique Clicked Email**: Count of all unique events of type Clicked Email based on person\_id as Last Touch ID.
- **Unique Clicked SMS**: Count of all unique events of type Clicked SMS based on person\_id as Last Touch ID.
- **Unique Count Bounced Email**: Count of all unique events of type Bounced Email based on person\_id as Last Touch ID.
- **Unique Failed to Delivery SMS**: Count of all unique events of type Failed to Delivery SMS based on person\_id as Last Touch ID.
- **Unique Marked Email as Spam**: Count of all unique events of type Marked Email as Spam based on person\_id as Last Touch ID.
- **Unique Opened Email**: Count of all unique events of type Opened Email based on person\_id as Last Touch ID.
- **Unique Opened Push**: Count of all unique events of type Opened Push based on person\_id as Last Touch ID.
- **Unique Ordered Product**: Count of all unique events of type Ordered Product based on person\_id as Last Touch ID.
- **Unique Placed Order**: Count of all unique events of type Placed Order based on person\_id as Last Touch ID.
- **Unique Received Push**: Count of all unique events of type Received Push based on person\_id as Last Touch ID.
- **Unique Received SMS**: Count of all unique events of type Received SMS based on person\_id as Last Touch ID.
- **Unique Refunded Order**: Count of all unique events of type Refunded Order based on person\_id as Last Touch ID.
- **Unique Relayed SMS**: Count of all unique events of type Relayed SMS based on person\_id as Last Touch ID.
- **Unique Subscribed To Back In Stock**: Count of all unique events of type Subscribed To Back In Stock based on person\_id as Last Touch ID.
- **Unique Subscribed To Email Marketing**: Count of all unique events of type Subscribed To Email Marketing based on person\_id as Last Touch ID.
- **Unique Subscribed To List**: Count of all unique events of type Subscribed to List based on person\_id as Last Touch ID.
- **Unique Subscribed to SMS Marketing**: Count of all unique events of type Subscribed to SMS Marketing based on person\_id as Last Touch ID.
- **Unique Subscribed to SMS Transactional**: Count of all unique events of type Subscribed to SMS Transactional based on person\_id as Last Touch ID.
- **Unique Unsubscribed**: Count of all unique events of type Count Unsubscribed based on person\_id as Last Touch ID.
- **Unique Unsubscribed From Email Marketing**: Count of all unique events of type Unsubscribed From Email Marketing based on person\_id as Last Touch ID.
- **Unique Unsubscribed From List**: Count of all unique events of type Unsubscribed From List based on person\_id as Last Touch ID.
- **Unique Unsubscribed from SMS Marketing**: Count of all unique events of type Unsubscribed to SMS Marketing based on person\_id as Last Touch ID.
- **Unique Unsubscribed from SMS Transactional**: Count of all unique events of type Unsubscribed to SMS Transactional based on person\_id as Last Touch ID.
- **Unique Viewed Product**: Count of all unique events of type Viewed Product based on person\_id as Last Touch ID.
- **Unsubscribed**: Count of all events of type Count Unsubscribed.
- **Unsubscribed From Email Marketing**: Count of all events of type Unsubscribed From Email Marketing.
- **Unsubscribed From List**: Count of all events of type Unsubscribed to List.
- **Unsubscribed from SMS Marketing**: Count of all events of type Unsubscribed to SMS Marketing.
- **Unsubscribed from SMS Transactional**: Count of all events of type Unsubscribed to SMS Transactional.
- **Viewed Product**: Count of all events of type Viewed Product.
### Dimensions
- **Created At**: Timestamp of when the campaign or flow was created.
- **Flow Status**: Current status of the flow. Either 'manual', 'live', or 'draft'. Read more here.
- **Is Archived (Yes / No)**: Boolean of whether the campaign has been archived or not
- **Last Touch Campaign Brand**: The brand of the campaign set in the Hub amplification.
- **Last Touch Campaign Category**: Campaign Category is the highest level of the hierarchy. For example: Fruit > Berries > Strawberries, the Campaign Category is Fruit and covers all Campaigns that are Fruit.
- **Last Touch Campaign Channel**: The Attribution Channel of the campaign set in the Hub amplification. Ex: Email, SMS
- **Last Touch Campaign Class**: Campaign Class is the third level of the hierarchy. For example: Fruit > Berries > Strawberries, the Campaign Class is Strawberries and includes only Berries that are Strawberries. There can be more than one Campaign within the class.
- **Last Touch Campaign Has Tracking Params (Yes / No)**: Indicates if the campaigns is configured to store tracking params in the URL.
- **Last Touch Campaign Name Refined**: A refined, 'friendlier' name of the campaign set in the Hub amplification
- **Last Touch Campaign Objective**: Objective of the campaign set in the Hub amplification. ex: Engagement, Retention, Acquisition
- **Last Touch Campaign Option**: Other attributes of the campaign not captured in the defined attribute fields. These should be comma seperated and set in the Hub amplification.
- **Last Touch Campaign Platform**: The Ad Source of the campaign set in the Hub amplification. Ex: Google Ads, Tiktok Ads
- **Last Touch Campaign Region**: The region of the campaign set in the Hub amplification Ex: US, CA, EU
- **Last Touch Campaign Subcategory**: Campaign Subcategory is the middle level of the hierarchy. For example: Fruit > Berries > Strawberries, the Campaign Subcategory is Berries and includes only Fruits that are Berries.
- **Last Touch Campaign Subchannel**: Subchannel of the campaign set in the Hub amplification
- **Last Touch Campaign Temporality**: The temporality of the campaign set in the Hub amplificationEx: September Sale, October EVG, 20230504, etc
- **Last Touch Campaign Type**: The type of the campaign set in the Hub amplification. ex: Transactional, Batch, Automated
- **Last Touch Flow Brand**: The brand of the campaign set in the Hub amplification.
- **Last Touch Flow Category**: Campaign Category is the highest level of the hierarchy. For example: Fruit > Berries > Strawberries, the Campaign Category is Fruit and covers all Campaigns that are Fruit.
- **Last Touch Flow Channel**: The Attribution Channel of the campaign set in the Hub amplification. Ex: Email, SMS
- **Last Touch Flow Class**: Campaign Class is the third level of the hierarchy. For example: Fruit > Berries > Strawberries, the Campaign Class is Strawberries and includes only Berries that are Strawberries. There can be more than one Campaign within the class.
- **Last Touch Flow Name Refined**: A refined, 'friendlier' name of the campaign set in the Hub amplification
- **Last Touch Flow Objective**: Objective of the campaign set in the Hub amplification. ex: Engagement, Retention, Acquisition
- **Last Touch Flow Option**: Other attributes of the campaign not captured in the defined attribute fields. These should be comma seperated and set in the Hub amplification.
- **Last Touch Flow Platform**: The Ad Source of the campaign set in the Hub amplification. Ex: Google Ads, Tiktok Ads
- **Last Touch Flow Region**: The region of the campaign set in the Hub amplification Ex: US, CA, EU
- **Last Touch Flow Subcategory**: Campaign Subcategory is the middle level of the hierarchy. For example: Fruit > Berries > Strawberries, the Campaign Subcategory is Berries and includes only Fruits that are Berries.
- **Last Touch Flow Subchannel**: Subchannel of the campaign set in the Hub amplification
- **Last Touch Flow Temporality**: The temporality of the campaign set in the Hub amplificationEx: September Sale, October EVG, 20230504, etc
- **Last Touch Flow Type**: The type of the campaign set in the Hub amplification. ex: Transactional, Batch, Automated
- **Name**: A name for this campaign. If not specified, this will default to the subject of the campaign.
- **Occcured At**: Date the event ocurred.
- **Session Date**: The date of the session this event is associated to.
- **Status**: Current status of the campaign. Either 'draft', 'scheduled', 'sent', or 'cancelled'.
- **Touch Type**: What kind of touch the event was attributed to -- 'campaign', 'flow', or null.
- **Trigger Type**: Corresponds to the object which triggered the flow.
- **UTM Campaign**: When the campaign or flow is configured with tracking params, this is the UTM campaign configured.
- **UTM Content**: When the campaign or flow is configured with tracking params, this is the UTM content configured.
- **UTM Medium**: When the campaign or flow is configured with tracking params, this is the UTM medium configured.
- **UTM Source**: When the campaign or flow is configured with tracking params, this is the UTM source configured.
- **UTM Term**: When the campaign or flow is configured with tracking params, this is the UTM term configured.
# Klaviyo Lists
### Measures
- **Average Total Subscribers**: The total number of profiles (subscribers) in the Klaviyo list at the time the data was loaded. This column is used to track the growth or decline of the list over time.
- **Total Subscribers**: Shows the total number of subscribers. For completed periods, this is the value at the end of the period. For the current, in-progress period, this is the value as of the last complete day.
### Dimensions
- **List Created At**: The timestamp indicating when the list was originally created in Klaviyo.
- **List Id**: The unique identifier for a list within Klaviyo. This is the primary key for a list as provided by the Klaviyo API.
- **List Name**: The user-defined name of the Klaviyo list.
- **List Opt In Process**: Specifies the opt-in process for the list, such as single opt-in or double opt-in.
- **Subscribers Date**: The specific date for the list's historical data.
# Klaviyo Segments
### Measures
- **Total Subscribers**: Shows the total number of subscribers. For completed periods, this is the value at the end of the period. For the current, in-progress period, this is the value as of the last complete day.
- **Average Profile Count**: The average number of profiles (subscribers) in the Klaviyo segment at the time the data was loaded. This column is used to track the growth or decline of the segment over time.
- **Profile Count**: The total number of profiles (subscribers) in the Klaviyo segment at the time the data was loaded. This column is used to track the growth or decline of the segment over time.
### Dimensions
- **Segment Id**: The unique identifier for a segment within Klaviyo. This is the primary key for a segment as provided by the Klaviyo API.
- **Segment Name**: The user-defined name of the Klaviyo segment.
- **Segment Created At**: The timestamp indicating when the segment was originally created in Klaviyo.
- **Segment Updated At**: The timestamp indicating when the segment was last updated in Klaviyo.
- **Subscribers Date**: The specific date for the segment's historical data.
- **Subscribers Count**: The number of subscribers in the segment for the given date.
[title] Audience Activations with Sendlane
[path] Chord Data Platform/Data Activations/Data Activations/Destination Set-up Notes/
# Introduction
This document provides an overview of how to use our Sendlane Sync using Chord's Audiences API. Sendlane is a marketing automation platform that unifies email, SMS, forms, and reviews to boost retention, personalization, and revenue.
The primary focus when it comes to audience activations with Sendlane via Chord is to add customer tags defined through Chord’s pre-built and custom audience dashboards. This enables email segmentation and personalization by delivering dynamic audience data as contact tags to Sendlane.
:::hint{type="info"}
If you get stuck or have additional questions as you review this documentation, feel free to reach out to us at [help@chord.co](mailto\:help@chord.co) — our team is also happy to help you activate audiences on other CMS tools or platforms that help you get your job done!
:::
# Chord to Sendlane Activation Flow
- **Chord Platform Application:** Audiences are created via the Chord platform per the existing flow.
- **Integration with DynamoDB:** Chord extracts Audience data from our Snowflake warehouses and stores it in an **AWS DynamoDB table**.
- **AWS Lambda Function:** An **AWS Lambda function** receives the updates and forwards them as contact tags to Sendlane.
- **Sendlane**: The synchronized contact tags can now be utilized in building targeted Segments and Lists using the auidence tag on the contact.
# Integration Details
:::hint{type="info"}
- Chord requires the Sendlane v2 API key to setup the sync.
- It only supports audiences with email as the primary key and audience as the secondary key when syncing audiences from Snowflake to DynamoDB (setup is shown in the sections below).
- Customers emails need to exist in sendlane to have a tag added. This does not add new customers to Sendlane.
:::
# DynamoDB Destination
Chord will handle the connection to the DynamoDB destination for you. You can view it as part of your [Data Activations](https://docs.chord.co/data-activations):
# Creating a Sync
Using our Sync UI, we first need to create a new sync that connects a custom Audience as the **source** and our DynamoDB table as the **destination**.
As a Chord tenant, you will have access to your own dedicated DynamoDB table. The example below is using `chord_audiences` for documentation purposes.
## Select Sync Behavior
Sync Behaviors dictate the types of change that should be applied to your data when a sync finds a matching (or not) record in a source and a destination.
Available sync behaviors are:
- **Update or Create (aka Upsert):** Update existing destination records when IDs match, otherwise, create new records if they're missing.
- **Mirror:** Keep the destination in sync with the source.
- If a row is added or edited in the source, update the destination.
- If a previously synced row no longer is in the source, remove the matching object from the destination.
:::hint{type="info"}
Mirror syncs identify changes by comparing against the data they have already sent -- not the data that might or might not already exist in the destination.
This means that the first sync will be an upsert for all records, and the second and following syncs will account for changes from the source data.
:::
# Sync Key
:::hint{type="danger"}
**Note: **The following steps (Sync Key, Field Mapping) are more advanced and should be handled by Chord employees or individuals with a strong understanding of the feature.
:::
Sync Keys will dictate how to associate data in the source with the destination. Both the source and destination need to provide a single, unique per record, identifying field. The identifiers will be used to look for matches. When a match is found - or not found - we then can use your selected Sync Behavior to decide what to do.
Your sync key can be any kind of unique identifier, like a user ID, an email address, etc. However, we do recommend using a “blended user ID” provided by Chord if possible (see below).
## Mapping with a blended user identifier
Some audiences may contain what we call a “blended user ID,” which is derived from the Chord data models to contain the CDP User ID - if one exists - else the Anonymous ID. This use case is particularly useful when mixing users that may or may not have a known CDP User ID.
This means that you will be able to look up a user via the Audience API using either a CDP anonymous ID or a known User ID (in this case).
:::hint{type="info"}
When using blended ID, it is very important to keep in mind that if you query an Anonymous ID that was identified at any point, our API won't return any result.
:::
# Field Mapping
Once you've defined *how* data is related between your source and destination, the next step is to determine *what* properties should be updated. The field mapping step lets you specify how fields should be mapped from your source model to the destination object's fields.
- We start by assigning our unique user identifier. `anonymous_current_cdp_blended_user_id` will become our `pk` (primary key).
- We can then set up the `sk` (sort key). It is **important** to ensure that this value reflects the name of the Audience being synced. You can easily obtain that value by choosing `Sync Metadata > Source Name`
You should end up with the following:
# Sync Schedule
Like any [Data Activations sync](https://docs.chord.co/gFnF-data-activations) on the Chord data platform, the Sendlane sync can be scheduled to run at regular intervals.
The Chord platform will display the sync results on the** Data Activations** page when you click into the **"Manage Syncs"** button.
[title] Financial Models
[path] Chord Data Platform/Data Models/
Chord gives you three OMS explores for financial, refund, and return analysis. The Transactions explore covers cash movement (sales, captures, and refunds) and books refunds on the date they were issued. The Refund Line Items and Return Line Items explores break refunds and returns down to the order line, so you can read them by product. These explores are available to OMS tenants.
## Quick Reference, Which Explore Should I Use?
| Business question | What you want to understand | Explore |
| --------------------------------------------------------------- | ----------------------------------------------- | ------------------------------- |
| How much revenue moved in this period, including refunds? | Cash-basis revenue and refund dollars by date | Transactions |
| Which products are getting refunded, and for how much? | Refund dollars and refunded units by product | Refund Line Items |
| Which products are getting returned, and why? | Returned units and return reasons by product | Return Line Items |
| Were these refunds tied to a customer return or a cancellation? | Restock type behind each refunded line | Refund Line Items |
| When was the return opened versus when was the refund issued? | The two date axes (return date and refund date) | Transactions, Return Line Items |
## Key Dimensions and Metrics
### Transactions
One row per successful cash-moving transaction (sale, capture, or refund). Refunds book on the date the refund was issued rather than the original order date, which keeps month over month revenue stable.
Common metrics: Gross Sales, Net Sales, # Refunds, # Refunds (distinct), Refunded Amount Sum, # Returns (distinct), Returned Quantity Sum.
Common dimensions: transaction date (cash basis), transaction kind (sale, capture, refund), Refund Created At, Return Created At, Return Status, Return Closed At.
Use this explore for revenue reporting and for refund or return dollars grouped by date.
### Refund Line Items
One row per refunded order line. Join to the order line to group refunds by product (product title, SKU).
Metrics: # Refund Lines, Refunded Quantity, Refunded Subtotal, Refunded Tax, Refunded Amount (incl tax).
Dimensions: Restock Type, Refund Created At, plus product fields from the joined order line.
Use this explore to see refund dollars and refunded units by product.
A note on coverage: the line-item amounts cover merchandise only. They do not include shipping refunds or order adjustments such as restocking fees, because those are not attributed to a product line. The sum of per-line refund amounts will be lower than a refund's full amount by that non-product portion.
### Return Line Items
One row per returned order line. Join to the order line to group returns by product.
Metrics: # Return Lines, Returned Quantity, Refunded Quantity, Refundable Quantity.
Dimensions: Return Reason, Return Reason Note, Return Created At, plus product fields from the joined order line.
Use this explore to see returned units and return reasons by product, and to find returns that are not yet fully refunded (Refundable Quantity greater than zero).
## Glossary
| Term | Definition | How to use it | Where you'll see it |
| -------------------------- | -------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| Return Created At | The date the return was opened | Matches your OMS Total Sales and Net Sales reporting, which book a return when it is opened | Return Line Items, Transactions (Return Created At) |
| Refund Created At | The date the refund was issued | Matches your OMS Finance and Refunds reporting, which book on the refund date | Transactions (Refund Created At and transaction date), Refund Line Items |
| Restock Type | How the refunded items were handled (no restock, cancel, return, legacy restock) | Tells you whether a refunded line was a cancellation before fulfillment (cancel) or a customer return (return) | Refund Line Items |
| Returned Quantity | Units returned on the line | The volume of product coming back | Return Line Items |
| Refunded Quantity | Units that have already been refunded | Compare against Returned Quantity to see how much of a return has been settled | Return Line Items |
| Refundable Quantity | Units on a return still eligible to be refunded | Find returns that are open and not yet fully refunded | Return Line Items |
| Refunded Amount (incl tax) | Refunded subtotal plus refunded tax for a line | Product-level refund value. Does not include shipping or restocking-fee refunds | Refund Line Items |
## Choosing the right date
Returns and refunds sit on two different dates, and they can be weeks apart. A return is opened first (Return Created At), and the refund is issued later (Refund Created At). Group by Return Created At when you want to match your OMS Total Sales view. Group by Refund Created At (or the Transactions explore's transaction date) when you want to match your OMS Finance and Refunds view.
[title] NetSuite
[path] Chord Data Platform/Data Sources/Connect Data Sources/
Connect your NetSuite financial and operational data to Chord. NetSuite is the ERP that powers accounting, inventory, procurement, and order management for many Chord brands. Chord ingests cost, inventory, and revenue attribution data from NetSuite so you can model true per-order COGS, landed costs, and margin alongside the rest of your stack: the costing detail that storefront and subscription platforms don't carry.
Unlike most Chord connectors, which take a single API key, NetSuite uses token-based authentication (TBA), an OAuth 1.0a flow that requires a short setup inside NetSuite to create an integration record, an access token, and a dedicated integration role. This page walks through that setup, the exact role permissions Chord needs, and how to connect the credentials in Chord Hub.
## What Chord ingests from NetSuite
Chord reads NetSuite through SuiteQL and pulls cost and revenue attribution data. Each dataset becomes its own table in your Chord Snowflake schema.
**On the cost side:**
- **Per-transaction COGS:** the realized cost of goods sold posted to the general ledger, sourced from the accounting lines on item fulfillment events (see the note below on when COGS posts).
- **Procurement costs:** purchase costs flowing through purchase orders, vendor bills, and item receipts.
- **Landed costs:** freight, duty, and handling capitalized into inventory cost, where you track them.
- **Inventory cost movements:** cost changes from inventory adjustments and item location cost data.
**On the revenue attribution side,** Chord ingests:
- **Sales orders, invoices, cash sales, and credit memos:** the order and billing documents that tie cost back to revenue.
- **Customer payments:** applied receipts against invoices.
- **Vendor bills, purchase orders, and item receipts:** the procurement documents.
- **Item fulfillments:** shipment events, where per-line COGS posts to the GL.
:::hint{type="info"}
**Heads up:** COGS posts on the item fulfillment event when goods ship, not when the sales order is created. Orders that are entered but not yet fulfilled will show no COGS until the fulfillment posts. This is expected NetSuite behavior, not a gap in the connector.
:::
## Set up token-based authentication in NetSuite
NetSuite authenticates Chord with five values you'll generate during this setup and then paste into Chord Hub:
- Account ID
- Consumer Key
- Consumer Secret
- Token ID
- Token Secret
The setup has three parts: enable the right features, create an integration record, and create an access token tied to a dedicated role. You'll need NetSuite administrator access to complete it.
:::hint{type="warning"}
**Heads up:** the consumer secret and token secret are each shown only once, at the moment you create the integration record and the access token respectively. Copy all five values somewhere safe as you go. If you lose a secret, you can't reveal it later. You'll have to regenerate the integration record or token.
:::
### 1. Enable the required features
In NetSuite, go to **Setup → Company → Enable Features** and open the **SuiteCloud** subtab. All of these settings live on that one subtab:
- In the **SuiteScript** section, confirm **Client SuiteScript** and **Server SuiteScript** are enabled (a prerequisite for token-based authentication).
- In the **Manage Authentication** section, enable **Token-Based Authentication**.
- In the **SuiteTalk (Web Services)** section, enable **REST Web Services**.
- Save the page.
### 2. Create an integration record
Go to **Setup → Integration → Manage Integrations → New**, give the integration a recognizable name (for example, `Chord Data Sync`), and configure it:
- Enable **Token-Based Authentication**.
- Enable **TBA: Issue Token Endpoint**.
- Disable **TBA: Authorization Flow**.
- Disable **Authorization Code Grant**.
- Save the record.
NetSuite displays the consumer key and consumer secret once on the confirmation screen. Copy both now.
### 3. Create an access token
Go to **Setup → Users/Roles → Access Tokens → New** and link three things:
- The integration record you created in step 2.
- A dedicated integration user (an employee record reserved for this connection).
- The integration role carrying the permissions listed below.
Save the token. NetSuite displays the token ID and token secret once. Copy both now.
### 4. Grant the integration role its permissions
The integration role must carry the permissions below, grouped by the NetSuite subtab where you'll find each one. This is the part merchants most often get wrong.
:::hint{type="warning"}
**Important:** Chord reads NetSuite via SuiteQL, which needs three permissions working together: **REST Web Services** and **Log in using Access Tokens** (both under **Setup**), plus **SuiteAnalytics Workbook**, which lives under **Reports** (not Setup) and must be set to access level **Edit**. REST Web Services alone is not enough. SuiteQL also enforces per-table access, so the role needs the **View** permission for every record type Chord reads (the Transactions and Lists grants below). A missing table permission doesn't raise an access error. Instead, the table simply appears not to exist, so that data silently never arrives.
:::
**Setup:**
- Log in using Access Tokens: Full
- REST Web Services: Full
**Reports:**
- SuiteAnalytics Workbook: Edit (this is the permission that authorizes SuiteQL; it lives under Reports, not Setup).
- Financial Statement: View
- Landed Cost Templates: View (optional, only if you track landed costs).
**Transactions (all View):**
- Sales Order
- Invoice
- Cash Sale
- Credit Memo
- Customer Payment
- Item Fulfillment
- Find Transaction
- Vendor Bill
- Purchase Order
- Item Receipt
- Adjust Inventory
- Adjust Inventory Worksheet
**Lists (all View):**
- Customers
- Items
- Vendors
- Subsidiaries
- Accounts
- Departments
- Classes
- Locations
**Custom Records (optional, View, only if you track landed costs):**
- Landed Cost Template
- Landed Cost Template Detail
- Landed Cost Template Mapping
### OneWorld and multiple subsidiaries
On OneWorld accounts, NetSuite's REST API, including SuiteQL, silently filters every response to the integration role's subsidiary scope. There is no error; data outside that scope is simply omitted. A role's **Subsidiary Restrictions** defaults to **User Subsidiary**, which returns only the integration user's own subsidiary. To ingest every subsidiary, set the integration role's **Subsidiary Restrictions** to **All** (or select the specific subsidiaries you want), and make sure the integration employee record has access to them. Otherwise you'll get a clean-looking but incomplete dataset.
## Connect the credentials in Chord
Open Chord Hub and go to **Data Sources → Add Source**.
Pick **NetSuite** from the data source list and enter the five values you generated during setup:
- **Account ID:** your NetSuite account number. Use the plain numeric ID for production. For a sandbox, use the underscore form (for example, `1234567_sb1`), not the hyphenated form shown in the browser URL.
- **Consumer Key**
- **Consumer Secret**
- **Token ID**
- **Token Secret**
Click **Save**. Chord stores the credentials encrypted; it does not make a live call against NetSuite at this step.
When ingestion is enabled for your tenant, the first sync kicks off automatically and validates the credentials end to end. Subsequent syncs run on your tenant's standard ingestion schedule.
:::hint{type="info"}
**Heads up:** because Chord doesn't test the connection when you click Save, a wrong value or a missing role permission won't surface until the first ingestion job runs. If your first sync fails, the troubleshooting items below cover the most common causes.
:::
## Troubleshooting
### Credentials saved but no data is coming through, or I see "role does not have permission"
This almost always means the integration role is missing the **SuiteAnalytics Workbook** permission, or one of the per-record View permissions listed above.
Chord reads NetSuite via SuiteQL, and SuiteQL queries are authorized specifically by **SuiteAnalytics Workbook**. REST Web Services alone is not enough, which is why the credentials save cleanly but the data read fails. A missing table permission makes that table look like it does not exist rather than returning an access error.
1. Add **SuiteAnalytics Workbook (Edit)** under **Reports** on the integration role.
2. Confirm the **Transactions** (including **Find Transaction**) and **Lists** View grants.
3. Save the role.
4. Re-run the sync.
### I'm on OneWorld and some subsidiaries are missing
NetSuite's REST API, including SuiteQL, silently scopes every response to the integration role's subsidiary access. There's no error when data is filtered out.
1. Set the integration role's **Subsidiary Restrictions** to **All** (or select the subsidiaries you want).
2. Make sure the integration employee record has access to those subsidiaries.
3. Re-run the sync.
### Pending orders show no COGS. Is something wrong?
No. NetSuite posts per-line COGS to the GL on the item fulfillment event, when goods ship, not when the sales order is created. Orders that haven't been fulfilled yet will correctly show no COGS until the fulfillment posts.
### Do NetSuite tokens expire?
No. Access tokens stay valid until someone explicitly revokes them in **Setup → Users/Roles → Access Tokens**. If a previously working connection suddenly fails, check that the token is still listed and active, and that the integration role and user are still enabled.
### I lost one of the secrets. How do I recover it?
The consumer secret and token secret are shown only once and can't be revealed later.
- If you lose the consumer secret, regenerate it on the integration record (**Setup → Integration → Manage Integrations**).
- If you lose the token secret, create a new access token (**Setup → Users/Roles → Access Tokens**).
Paste the new values into the same Chord credential entry and save.
### What account ID format should I use for a sandbox?
Use the underscore form, such as `1234567_sb1`. The hyphenated form you see in the NetSuite browser URL (for example, `1234567-sb1`) will not authenticate. Production accounts use the plain numeric ID.
### How do I rotate the credentials?
1. Create a new access token in NetSuite (and a new integration record if you're also rotating the consumer key/secret).
2. Paste the new values into the same Chord credential entry.
3. Save.
Chord uses the new credentials on the next scheduled sync. Once you've confirmed a clean sync, revoke the old token in NetSuite.
### Need help?
If you hit a credential, permission, or connectivity issue you can't resolve, reach out to [help@chord.co](mailto\:help@chord.co) with the exact error message. We'll trace the request and tell you what's failing.
[title] Data Activations
[path] Chord Data Platform/Data Activations/
# Overview
Chord's core differentiator is that it is a comprehensive data platform that not only collects rich transactional and behavioral customer data but also allows modern commerce brands to leverage this data innovatively to unlock competitive marketing campaigns and analytical insights downstream.
With over 160 activation destinations (and counting), Chord provides ample opportunities to engage your data further.
Some popular destinations include:
- Attentive
- Braze
- Customer.io
- Facebook Ads
- Google Ads
- Google Analytics 4
- Hubspot
- Intercom
- Iterable
- Klaviyo
- Marketo
- Reddit Ads
- Salesforce
- Slack
- Zendesk
See our full list of [available destinations](https://docs.chord.co/available-destinations). Chord's Data Activations solution will allow brands to sync Chord-collected data to a vast array of marketing and other data activation tools. This exciting feature suite allows customers to activate their Chord data in smart ways to increase sales and boost store operations.
# Sample Use Cases
Chord Data Activations can empower many different workflows, including but not limited to the following:
- As a **growth marketer**, I want to send automated look-a-like and suppression lists based off advanced analytics to ad platforms to reduce CAC.
- As an **email marketer**, I want to send advanced and predictive analytics to my email platform to personalize campaigns and segment my users to increase customer engagement and reduce CAC.
- As an **accountant**, I want to send analytics to our accounting software to customize our platform, increase efficiencies, and reduce time to close.
- As a **data creator**, I want my various cross-functional teams to self-serve activate advanced and predictive analytics across various platforms.
- As a **developer**, I want my cross-functional teams to send any analytics and predictive analytics to a wide range of destinations without substantial development time (adding to/deleting properties from events, creating and maintaining various integrations).
# Getting Started
You can easily connect and get started with Chord Data Activations. Read on to understand how you can add data destinations and manage your data syncs.
:::hint{type="info"}
If your store does not have full access to Chord Data Activations, you can request access by clicking on the "Request Access" button on the Data Activations page. A Chord team member will reach out to you shortly!
**Note:** Once someone submits a Data Activations access request on behalf of your organization, it will stay in the queue until it is addressed. In other words, there is no need to submit multiple requests for access - we will log one access request per organization.
:::
# Connect a Destination
Before you can send and sync your data, you need to set up a destination for the data.
1. Make sure you are logged into the platform and navigate to **Data Activations **on the left navigation panel.
2. Under **Data Activations**, you'll be able to perform the following actions:
1. **Manage Syncs:** Manage existing data syncs to specific destinations.
2. **Add Destination: **Add a new data destination.
3. Select **Add Destination** to set up a new destination to send your store data.
4. Select the desired destination via the destination catalog. Note that you will need to have API keys ready to make the connection. (Note: Search functionality on this page is coming soon!)
5. Once you select a destination, you will be taken to the destination connection flow.
6. Complete your destination setup to begin managing your data syncs!
## Manage Syncs
Once you have connected a destination, you can begin managing your syncs.
1. Click on the **Manage Syncs** button on the **Data Activations** landing page.
2. On this page (**My Syncs**), you'll see any existing data destination syncs and their status.
3. To create a new sync, click the **Add New Sync** button.
4. When you click **Add New Sync**, you'll be taken to our **Create Sync** flow. You can choose what data source you'd like to pull data from and the destination you want to send that data. Continue to follow along the guided setup to create your sync.
::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/Zy4DO7jgpGCIbIwEB1hSA_screenshot-2024-06-28-at-44116-pm.png" size="100" width="982" height="815" position="center" showCaption="false" indent="2"}
5. To edit an existing sync, click any of the icons under the **Actions** column. Note: You can **Run, Stop, Delete, and Edit **existing syncs.
1. **Run a sync** means you are triggering a data sync ad hoc.
2. **Stop a sync** means you are stopping existing data from syncing for a destination.
3. **Delete a sync** means you are deleting the existing data sync for the chosen destination.
4. **Edit a sync** means you are editing information about the data sync to the chosen destination. **Note: You are not able to update the sync cadence via this Edit functionality. See below for additional information on updating scheduled syncs.**
5. **Update schedule** means you can set and update a data sync schedule for a given destination. See more information on how to do so below.
## Update a Scheduled Sync
You can set specific data syncing schedules for each of your destinations. To edit the sync schedule for a given destination, you can follow the steps outlined below.
::loom[]{url="https://www.loom.com/embed/615fcb52c62b47e7a04c2b0fc6db5af3?sid=3c52230d-9581-42ad-b2c2-91ae597e8103"}
1. Once logged into the Chord platform, navigate to the **Data Activations** page.
2. Click on the **Manage Syncs **button next to **Add Destination**.
3. Click the** clock icon** for the specific destination sync schedule you wish to edit.
4. Select the data sync cadence you wish you apply to the specific desination.
5. Click **Update** to finish updating the sync schedule.
6. Verify that the schedule has been updated for the destination you selected.
# Managing Destinations
Existing destinations may need to be updated from time to time. For example, if you see a broken destination sync, the token used to authorize Chord to connect to your destination may have expired and needs to be reauthorized.
To fix a broken destination sync:
1. Click on the broken service to edit on the **Data Activations** page.
2. Click the **Edit Service** button. You will be redirected to a page where you can reauthorize the service.
3. Follow the steps on-screen, and input the tokens if necesary, to edit or reauthorize the app.
# Troubleshooting and FAQs
- **Question: There's a "Test Sync" feature within the data sync setup flow. What does this entail?**
- The test sync will only send a record for one random user. Once the test is complete, it will populate with the record so you can check the destination that the data sent properly.
- **Question: Are there any limitations when it comes to editing existing syncs?**
- Within the sync, you can rename the fields and configure the sync however you'd like.
- **Question: What happens when a sync fails? **
- If a record is rejected during a sync (e.g., due to invalid data or a temporary issue), we will automatically retry it on the next scheduled sync run and until it succeeds. If a batch of records fails during a sync, our platform will retry that batch using an exponential backoff algorithm, meaning the time between retries increases with each attempt. If records are sent but rejected by the destination, these records will show as rejected and will be retried when the sync is re-executed.
- **Question: I am getting a sync failure because of outdated information (like an outdated API key). How do I reset or update the sync details with new information?**
- You can edit a sync setup by selecting the particular destination you'd like to update and clicking the **Edit Service** button. From there, you can review and edit the sync with new information as needed.
- **Question: I am having trouble syncing custom audiences with Microsoft Ads. **
- To sync custom audiences data with the Microsoft Advertising UI, you need to first accept the terms and conditions in the Microsoft Advertising UI when the customer list is initially created. After these terms and conditions are accepted, you can proceed to create the sync normally.
[title] Ads Module
[path] Chord Data Platform/Data Sources/
# Overview
Chord's Ads Module unlocks connections for various sources of ad spend data and enables a robust Ads explore, which is a wide dataset populated with enriched data fields.
The Ads explore allows for the creation of custom reports and audiences or customer segments with granularity down to the campaign level. Ad spend data is also joined to Chord's rich marketing attribution data, enabling even more detailed performance analysis.
Sample fields available in Ads explore:
- Ad Name
- Ad Status
- Campaign Advertising Channel Type
- Campaign Name
- Source
The module enables direct connections to the following sources:
- Facebook Ads
- Google Ads
- Pinterest Ads
- TikTok Ads
- Youtube Ads
- Bing Ads (Now Available!)
The module unlocks access to the Advertising Spend model amplification (part of [Model Amplifications](https://docs.chord.co/model-amplifications)), which enables brands to add manual or offline ad spend data (e.g. podcasts, newsletters, billboards) for efficient ingestion and transformation alongside their digital ads data for a complete picture of marketing ads spend.
# Use Cases
- Brands create reports to track ad spend over time by channel
- Brands create reports to compare total impressions by campaign and channel
Please reach out to help\@chord.co or your account executive for more information about or access to this feature.
[title] Conversions
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Chord OMS/
### **x\_fct\_trans\_activities**
| Name | Definition |
| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Activity Event Text | The name of the event. |
| Activity Event Text Id | The slug of the event name, mapping to the page or track event table. |
| Activity Id | The unique identifier of an activities (i.e. Track or Page event). |
| Activity Page Path | The page path part of the URL. A page path is the part of URL that comes after the hostname (domain) and before the query parameters, URL fragment, or port. (e.g. \`/pages/contact-us/\` for \`https\://chord.co/pages/contact-us/?ref=internal-banner\`.) |
| Activity Page Query | The query string portion of the URL of the page. |
| Activity Page Title | The title/name of the page. |
| Activity Page Url | The URL of the page. |
| Activity Session Activity Count | Total count of activities, pave views and tracked events within the session. |
| Activity Session Attribution Channel | The attribution channel for the first page event of the session. Sessions with an attribution of 'Unknown' indicates that there is no attributable data for that session. |
| Activity Session Attribution Channel Paid Or Organic | Indicates if the session's first page attribution is paid or organic. Attribution is considered Organic if the attribution channel is 'Direct', 'Other', 'Organic Search', 'Organic Social', 'Email', or 'SMS'. |
| Activity Session Attribution First Page Url Has Gclid | Indicates if the first page event of the session has a Google Click ID. |
| Activity Session Attribution First Page Url Has Utm | Indicates if the first page event of the session has any utm information. |
| Activity Session Attribution Has Referrer | Indicates if the first page event of the session has a referrer host. |
| Activity Session Attribution Medium | The campaign medium represented by the UTM tags for the first page event of the session. |
| Activity Session Attribution Source | The campaign source represented by the UTM tags for the first page event of the session. |
| Activity Session Attribution Sub Channel | Sub-Channel is a granular level of attribution. |
| Activity Session Completed Oms Order Ids | Array of OMS Order IDs associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Activity Session Completed Order Ids | Array of order IDs associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Activity Session Completed Order Numbers | Array of order numbers associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Activity Session Days Since Last Session End | The days between the last session's end and the start of this session. |
| Activity Session Device | The device on which the event was sent from. |
| Activity Session Device Category | The device category of the device on which the event was sent from. There are multiple supported values for this column such as 'iPhone', |
| Activity Session Duration In Seconds | Total seconds between start and end activities within the session. |
| Activity Session Duration In Seconds Tiers | Total seconds between start and end activities within the session, aggregated into tiers: 0-9s, 10-29s, 30-59s, and 60s or more. |
| Activity Session Has Order Completion | Flag for sessions with an order completed or checkout completed front-end events |
| Activity Session Id | Unique ID for the session. |
| Activity Session Number | Session number per anonymous id. |
| Activity Session Unique Completed Order Count | Count of unique order ids associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Activity Session Unique Completed Order Number Count | Count of unique order numbers associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Activity Utm Campaign | The campaign name represented by the UTM tags. |
| Activity Utm Content | The campaign content represented by the UTM tags. |
| Activity Utm Medium | The campaign medium represented by the UTM tags. |
| Activity Utm Source | The campaign source represented by the UTM tags. |
| Activity Utm Term | The campaign term represented by the UTM tags. |
| Activity Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store |
| Anonymous Completed Oms Order Ids | Array of OMS Order IDs associated to the anonymous\_id, as collected by order completed or checkout completed front-end events, over time. |
| Anonymous Completed Order Ids | Array of order IDs associated to the anonymous\_id, as collected by order completed or checkout completed front-end events, over time. |
| Anonymous Completed Order Numbers | Array of order numbers associated to the anonymous\_id, as collected by order completed or checkout completed front-end events, over time. |
| Anonymous Current Blended User Id | Unique id derived from the user\_id and the anonymous\_id. Whenever a customer has a user\_id, the user\_anonymous\_id will be constant for |
| Anonymous Current User Id | The current user\_id associated with the anonymous\_id. This unique user\_id is created by Segment's Identify call. A user\_id can be associated to many anonymous\_ids. |
| Anonymous Id | Unique id created by Chord for each anonymous visitor per store. |
| Anonymous Segment Anonymous Id | Id created by Segment for each anonymous visitor. This id gets created as soon as a customer's browser loads the analytics javascript widget. The anonymous\_id remains unchanged through the entire browsing session from a single device. Depending on configuration, two stores connected stores may have the same anonymous\_id. |
| Anonymous Unique User Ids | Array of user IDs mapped to an anonymous ID. |
| Date Day Num Of Year | The number representing the day of the year. |
| Date Id | Unique key that uniquify a date. |
| Date Month Num Of Year | The month number of the year. |
| Last Seen Page Browser Locale | Locale of browser. |
| Last Seen Page Device | The device on which the event was sent from. |
| Last Seen Page Device Category | The device category of the device on which the event was sent from. There are multiple supported values for this column such as 'iPhone', |
| Last Seen Page Event Table Name | The properly formatted name of the table of the event. |
| Last Seen Page Event Text | The name of the event. |
| Last Seen Page Event Text Id | The slug of the event name, mapping to the page or track event table. |
| Last Seen Page Gclid | The Google Click ID. Google Click ID (GCLID) is a parameter passed in the URL with ad clicks, to identify the campaign and other attributes of the click associated with the ad for ad tracking and campaign attribution. |
| Last Seen Page Id | Unique key generated by Segment for each tracking or page event. |
| Last Seen Page Oms Id | Unique key generated by our models that uniquifies an OMS. |
| Last Seen Page Host | The host of the event's URL. For example \`https\://www\.store-staging.assembly.dev/myPage\` would become \`store-staging.assembly.dev\`. This facilitates grouping events by host. |
| Last Seen Page Path | The page path part of the URL. A page path is the part of URL that comes after the hostname (domain) and before the query parameters, URL fragment, or port. (e.g. \`/pages/contact-us/\` for \`https\://chord.co/pages/contact-us/?ref=internal-banner\`.) |
| Last Seen Page Query | The query string portion of the URL of the page. |
| Last Seen Page Referrer | The referrer of the page. The referrer is the webpage that sends visitors to the site using a link. In |
| Last Seen Page Title | The title/name of the page. |
| Last Seen Page Url | The URL of the page. |
| Last Seen Page Referrer Host | The host of the referrer. For example \`https\://www\.store-staging.assembly.dev/myPage\` would become \`store-staging.assembly.dev\`. This facilitates grouping events by host. |
| Last Seen Page Segment User Id | The unique ID of the user. |
| Last Seen Page Store Id | Unique key generated by our models that uniquifies a store. |
| Last Seen Page Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Last Seen Page User Agent | The User agent of the device making the request. A User agent request header is a characteristic string that lets servers and |
| Last Seen Page User Id | Unique key generated by Chord to identify the user. |
| Last Seen Page Utm Campaign | The campaign name represented by the UTM tags. |
| Last Seen Page Utm Content | The campaign content represented by the UTM tags. |
| Last Seen Page Utm Medium | The campaign medium represented by the UTM tags. |
| Last Seen Page Utm Source | The campaign source represented by the UTM tags. |
| Last Seen Page Utm Term | The campaign term represented by the UTM tags. |
| Last Seen Page Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store |
| Session Landing Page Browser Locale | Locale of browser. |
| Session Landing Page Device | The device on which the event was sent from. |
| Session Landing Page Device Category | The device category of the device on which the event was sent from. There are multiple supported values for this column such as 'iPhone', |
| Session Landing Page Event Table Name | The properly formatted name of the table of the event. |
| Session Landing Page Event Text | The name of the event. |
| Session Landing Page Event Text Id | The slug of the event name, mapping to the page or track event table. |
| Session Landing Page Gclid | The Google Click ID. Google Click ID (GCLID) is a parameter passed in the URL with ad clicks, to identify the campaign and other attributes of the click associated with the ad for ad tracking and campaign attribution. |
| Session Landing Page Id | Unique key generated by Segment for each tracking or page event. |
| Session Landing Page Oms Id | Unique key generated by our models that uniquifies an OMS. |
| Session Landing Page Host | The host of the event's URL. For example \`https\://www\.store-staging.assembly.dev/myPage\` would become \`store-staging.assembly.dev\`. This facilitates grouping events by host. |
| Session Landing Page Path | The page path part of the URL. A page path is the part of URL that comes after the hostname (domain) and before the query parameters, URL fragment, or port. (e.g. \`/pages/contact-us/\` for \`https\://chord.co/pages/contact-us/?ref=internal-banner\`.) |
| Session Landing Page Query | The query string portion of the URL of the page. |
| Session Landing Page Referrer | The referrer of the page. The referrer is the webpage that sends visitors to the site using a link. In |
| Session Landing Page Title | The title/name of the page. |
| Session Landing Page Url | The URL of the page. |
| Session Landing Page Referrer Host | The host of the referrer. For example \`https\://www\.store-staging.assembly.dev/myPage\` would become \`store-staging.assembly.dev\`. This facilitates grouping events by host. |
| Session Landing Page Segment User Id | The unique ID of the user. |
| Session Landing Page Store Id | Unique key generated by our models that uniquifies a store. |
| Session Landing Page Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Session Landing Page User Agent | The User agent of the device making the request. A User agent request header is a characteristic string that lets servers and |
| Session Landing Page User Id | Unique key generated by Chord to identify the user. |
| Session Landing Page Utm Campaign | The campaign name represented by the UTM tags. |
| Session Landing Page Utm Content | The campaign content represented by the UTM tags. |
| Session Landing Page Utm Medium | The campaign medium represented by the UTM tags. |
| Session Landing Page Utm Source | The campaign source represented by the UTM tags. |
| Session Landing Page Utm Term | The campaign term represented by the UTM tags. |
| Session Landing Page Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store |
| Store Id | Unique key generated by our models that uniquifies a store. |
| Store Name | The name of the store. |
| Store Oms Admin Url | The Admin URL of that OMS. |
| Store Oms Id | Unique key generated by Chord that uniquifies an OMS. |
| Store Oms Store Id | Unique key generated by our models that uniquifies a store. |
| Store Oms Type | The type of the OMS. |
| Store Id | Unique key generated by our models that uniquifies a store. |
| Store Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Store Url | The Storefront URL of of the store. |
| User Address 1 | The first line of the street address. |
| User Address 2 | The optional second line of the address. |
| User Address City | The city of the address. |
| User Address Country | The country of the address. |
| User Address Name | The full name of the customer, based on firstName and lastName. |
| User Address State | The region of the address, such as the province, state, or district. |
| User Address Zip | The postal code of the address. |
| User Completed Oms Order Ids | Array of OMS Order IDs associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| User Completed Order Ids | Array of order IDs associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| User Completed Order Numbers | Array of order numbers associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| User Email | The email associated with the user. |
| User Id | Unique ID per user. It is equal to either 1) a identified\_user\_id as identified by Segment in the Identify call, or 2) an anonynous\_id. |
| User Identified User Id | Unique ID per identified user. (See Segment's documentation on user\_id)\[https\://segment.com/docs/connections/spec/identify/#user-id]. |
| User Ip | IP address associated with the user. |
| User Last Anonymous Id | Last seen anonymous\_id per user. An anonymous\_id is a unique ID per anonymous visitor. (See Segment's documentation on anonymous\_id)\[https\://segment.com/docs/connections/spec/identify/#anonymous-id]. |
| User Last Segment Anonymous Id | |
| User Segment User Id | The unique ID of the user. |
| User Unique Anonymous Ids | Array of all seen anonymous\_ids per user. An anonymous\_id is a unique ID per anonymous visitor. (See Segment's documentation on anonymous\_id)\[https\://segment.com/docs/connections/spec/identify/#anonymous-id]. |
| User Unique Completed Order Count | Count of unique order ids associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
### **x\_fct\_trans\_sales**
| Name | Description |
| ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Affiliate Email | Email address of the affiliate. |
| Affiliate Id | Unique key generated by Chord to identify a unique affiliate. |
| Affiliate Name | Full name of the user. |
| Affiliate Seen Emails | List of email addresses seen. |
| Affiliate User Id | Unique key generated by Chord to identify a unique user. |
| Billing Address Address1 | The street address of the customer. |
| Billing Address Address2 | The optional second address of the customer. |
| Billing Address Alternative Phone | The customer's alternative phone number. |
| Billing Address City | The city where the address is. |
| Billing Address Company | A company name. |
| Billing Address Country Abbr | |
| Billing Address Country Name | Full name of the country. |
| Billing Address Firstname | First name of the customer. |
| Billing Address Id | Unique key generated by Chord to identify a unique address. |
| Billing Address Lastname | Last name of the customer. |
| Billing Address Oms Address Id | Unique key generated by Solidus that identifies an address. |
| Billing Address Phone | The customer's phone number. |
| Billing Address State Abbr | |
| Billing Address State Name | Full name of the state. |
| Billing Address Zipcode | The postal code. |
| Order Adjustment Types | List of distinct adjustment reasons for adjustments made to the order. |
| Order Admin Url | The Admin URL of pointing to the order. |
| Order Applied Discount Codes | List of promotion codes applied to the order. |
| Order Applied Discount Codes Count | Count of promotion codes applied to the order. |
| Order Applied Discount Ids | List of promotion ids applied to the order. |
| Order Applied Discount Names | List of promotion names applied to the order. |
| Order Applied Discount Names Count | Count of promotion names applied to the order. |
| Order Cart Url | Url of the cart which contains the order. |
| Order Channel | The channel from which the order is created. |
| Order Completed Order Rank By Subscription | Allows to rank completed orders by completion date for a subscription. |
| Order Completed Order Rank By User | Allows to rank completed orders by completion date for a user. |
| Order Contains Refund | Whether or not the order contains refund adjustments or refunds that are processed outside of the Chord OMS adjustment systems (for example via RMAs or cancellations). |
| Order Contains Replacement | Whether or not the order contains replacement adjustments or shipped replacement items (following an RMA authorization). |
| Order Contains Return | Whether or not the order contains returns (authorized RMAs). |
| Order Contains Rma Refund | Whether or not the order contains RMA refunds (refunds issued after an RMA was requested and authorized). |
| Order Contains Rma Store Credits | This column is not documented. |
| Order Currency | The currency for this order. |
| Order Customer Lifetime Month | Number of months between the current order's completion date and the user's first order completion date. First orders have a value of 1. |
| Order Customer Lifetime Week | Number of weeks between the current order's completion date and the user's first order completion date. First orders always have a value of 1. |
| Order Email | The email address of the customer that made the order. |
| Order Financial State | The current payment state of the order. |
| Order Fulfillment Ids | Array of unique keys generated by Chord to identify the unique shipments for an order. |
| Order Fulfillment Numbers | The unique identifier for this shipment. |
| Order Fulfillment State | The current shipment state of the order. |
| Order Has Discount | Whether or not the order has promotions applied to it. |
| Order Has Order Tags | Whether or not that order has tags. |
| Order Hours From Order To First Fulfillment | Number of hours between order completion and first order shipment; how long it takes a company to get the initial product out to a customer. |
| Order Hours From Order To Last Fulfillment | Number of hours between order completion and last order shipment. |
| Order Id | Unique key generated by Chord to identify a unique order. |
| Order Is Canceled | Whether or not the order is canceled. The order is considered canceled when the canceled\_at date is not null. |
| Order Is Completed | Whether or not that order is completed. The order is considered completed when the completed\_at date is not null. This means that the order does not necessarily have a state = `complete`, since states can change after the order completion (for example in the case of a refund). |
| Order Is First Completed Order | Whether or not that order was the first completed order for a user. |
| Order Is First Order | Whether or not that order was the first order for a user. |
| Order Is First Subscription Completed Order | Whether or not that order was the first completed order for a subscription. |
| Order Is First Subscription Order | Whether or not that order was the first order for a subscription. |
| Order Is Fulfilled | Whether or not that order has shipped. |
| Order Is Part Of Subscription | Whether or not that order is part of a subscription. |
| Order Is Pre Paid Purchase | Whether the order the orderincludes the purchase of a pre-payment; this could be a gift subscription, pre-pay subscription, or gift card. |
| Order Is Pre Paid Redemption | Whether the order included the redemption of a pre-payment; this could be the redemption of a gift subscription, pre-pay subscription, or gift card. |
| Order Is Referred By Affiliate | Whether or not the user is referred by an affiliate. |
| Order Is Referred By Referrer | Whether or not the user is referred by a referrer. |
| Order Is Replacement | True when the order is a replacement order. |
| Order Is Suspicious Referral Conversion | Wether this represents a suspicous referral conversions or not. |
| Order Item Id | Unique key generated by Chord to identify a unique order. |
| Order Item Line Items Quantity | Sum of line items quantities per order. |
| Order Item Product Basket | List of product names per in the order. |
| Order Item Product Basket Count | Number of products in the order. |
| Order Product Basket | The titles of products for a given order array converted to a string. |
| Order Item Total Line Item Unit Quantity | Sum of line item units in the order. |
| Order Item Total Line Items Quantity | Sum of line items quantities per order. |
| Order Item Unique Product Basket | List of unique product names per in the order. |
| Order Item Unique Product Basket Count | Number of unique products in the order. |
| Order Unique Product Basket | The list of unique products for a given order array converted to a string. |
| Order Item Unique Unit Basket | List of unique units in the order. |
| Order Item Unique Unit Basket Count | Count of unique units in the order. |
| Order Unit Basket | The list of units for a given order array converted to a string. |
| Order Item Unique Variant Basket | List of unique variant names per in the order. |
| Order Item Unique Variant Basket Count | Number of unique variants in the order. |
| Order Unique Variant Basket | The list of unique variants for a given order array converted to a string. |
| Order Item Unit Basket | List of all units in the order. |
| Order Item Unit Basket Count | Count of all units in the order. |
| Order Unique Unit Basket | The list of unique units for a given order array converted to a string. |
| Order Item Variant Basket | List of variant names per in the order. |
| Order Item Variant Basket Count | Number of variants in the order. |
| Order Variant Basket | The titles of variants for a given order array converted to a string. |
| Order Number | Human-readable unique key generated by Solidus that identifies an order. It begins with a set of Tenant-Store defined letters and ends in a nine-digit number (for example, CHORD-123456789). This number is shown to the users in various places. These combinations are unique for a given Store. |
| Order Oms Order Id | Unique key generated by Solidus that identifies an order. |
| Order Rank By User | Allows to rank completed orders by completion date for a user. |
| Order Tags | List of tags associated to the order. |
| Order Tags Count | Number of tags associated to the order. |
| Order Referral Conversion Suspicious Reasons | A list of reasons explaining why the referral conversion is suspicious. |
| Order Referrer User Email | The email address of the customer identified with the referral. |
| Order Special Instructions | Any special shipping instructions that have been specified by the customer during checkout. |
| Order State | The current state of the order. |
| Order Store Id | Unique key generated by our models that uniquifies a store. |
| Order Store Name | The name of the store. |
| Order Store Oms Admin Url | The Admin URL of that OMS. |
| Order Store Oms Id | Unique key generated by Chord that uniquifies an OMS. |
| Order Store Oms Store Id | Unique key generated by our models that uniquifies a store. |
| Order Store Oms Type | The type of the OMS. |
| Order Store Id | Unique key generated by our models that uniquifies a store. |
| Order Store Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Order Store Url | The Storefront URL of of the store. |
| Order Subscription Customer Lifetime Month | Number of months between the current order's completion date and the user's first subscription order completion date. First orders have a value of 1. |
| Order Subscription Customer Lifetime Week | Number of weeks between the current order's completion date and the user's first subscription order completion date. First orders always have a value of 1. |
| Order User Referral Code | Unique key generated by Solidus that represents the user's referral code. |
| Order Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store. |
| Referral Conversion Rank By Referrer | Allows to rank a referral conversion by referrer. |
| Referral Id | Unique key generated by Chord to identify a unique referral identifier. |
| Referral Is Converted | Wether this represents a converted referral or not. |
| Referral Is First Conversion | Whether or not the referral was the referrer's first converted referral. |
| Referral Is First Non Suspicious Conversion | Whether or not the referral was the referrer's first non suspicious converted referral. |
| Referral Is Suspicious | Wether this represents a suspicous referral conversions or not. |
| Referral Non Suspicious Conversion Rank By Referrer | Allows ranking of non-suspicious referral conversion by the referrer. |
| Referral Oms Referral Conversion Id | Unique key generated by Solidus that identifies a referral conversion. |
| Referral Suspicious Reasons | A list of reasons explaining why the referral conversion is suspicious. |
| Referrer Currency | The currency for this referral identifier. |
| Referrer Email | The email address of the customer identified with the referral. |
| Referrer Id | Unique key generated by Chord to identify a unique referral identifier. |
| Referrer Oms Referral Identifier Id | Unique key generated by Solidus that identifies a referral identifier. |
| Referrer User Referral Code | Unique key generated by Solidus that represents the user's referral code. |
| Shipping Address Address1 | The street address of the customer. |
| Shipping Address Address2 | The optional second address of the customer. |
| Shipping Address Alternative Phone | The customer's alternative phone number. |
| Shipping Address City | The city where the address is. |
| Shipping Address Company | A company name. |
| Shipping Address Country Abbr | |
| Shipping Address Country Name | Full name of the country. |
| Shipping Address Firstname | First name of the customer. |
| Shipping Address Id | Unique key generated by Chord to identify a unique address. |
| Shipping Address Lastname | Last name of the customer. |
| Shipping Address Oms Address Id | Unique key generated by Solidus that identifies an address. |
| Shipping Address Phone | The customer's phone number. |
| Shipping Address State Abbr | |
| Shipping Address State Name | Full name of the state. |
| Shipping Address Zipcode | The postal code. |
| Subscription Completed Oms Order Ids | List of completed OMS order ids by a subscription. |
| Subscription Completed Order Count | Total amount of orders completed by a subscription. |
| Subscription Completed Order Ids | List of completed order ids by a subscription. |
| Subscription First Order Unique Product Basket | Array of unique product names ordered in the first order per subscription. |
| Subscription First Order Unique Variant Basket | Array of unique SKUs ordered in the first order per subscription. |
| Subscription Has Subscription Tags | Whether or not the subscription has tags. |
| Subscription Id | Unique key generated by Solidus that identifies a subscription. |
| Subscription Interval In Days | The number of days in the subscription interval. |
| Subscription Is Auto Redeemed | Whether the pre-paid subscription will be auto-redeemed or if an action is required by the recepient. |
| Subscription Is Gift | Whether or not the pre-paid subscription is a gift. |
| Subscription Is Recurring | Whether the pre-paid subscription is recurring. |
| Subscription Last Order Unique Product Basket | Array of unique product names ordered in the latest order per subscription. |
| Subscription Last Order Unique Variant Basket | Array of unique SKUs ordered in the latest order per subscription. |
| Subscription Oms Pre Paid Subscription Id | ID generated by ChordOMS to identify a unique pre-paid subscription. |
| Subscription Oms Subscription Id | Unique key generated by Solidus that identifies a subscription. |
| Subscription Pre Paid Subscription Id | Chord generated unique id for the pre-pay subscription. |
| Subscription State | The current state of the subscription, enhanced with values for \`paused\` if the subscription is active and paused. |
| Subscription Tags | The list of tags associated with a subscription. |
| Subscription Tags Count | The number of tags associated with a subscription. |
| Subscription Unique Product Basket | Array of unique product names ever ordered per subscription. |
| Subscription Unique Variant Basket | Array of unique SKUs ever ordered per subscription. |
| User Completed Oms Order Ids | List of completed OMS order ids by a user. |
| User Completed Order Ids | List of completed order ids by a user. |
| User Credit Category Basket | Array of credit categories (Gift Card, Reimbursement, Referral Credits, Prepaid Subscription, GMA) issued per user. |
| User Email | Email address of the user. |
| User First Completed Oms Order Id | OMS order id of the first order completed by a user. |
| User First Completed Order Id | Unique order id of the first order completed by a user. |
| User First Order Unique Ordered Products | Unique products ordered by the user in their first completed order. |
| User First Order Unique Ordered Skus | Unique SKUs ordered by the user in their first completed order. |
| User Has Ordered A La Carte | Whether or not the user has had at least one order that is not part of a subscription. |
| User Has Promo Applied In First Order | Whether or not the user has a promo applied to their first completed order. |
| User Has Subscription In First Order | Whether or not the user's first order is linked to a subscription. |
| User Id | Unique key generated by Chord to identify a unique user. |
| User Is Active Subscriber | Whether or not the user has an active subscription with at least one completed subscription order. An active subscription is one that is not cancelled or paused. |
| User Is Customer | Whether or not the user is a customer. |
| User Is New Customer | Whether or not the user is a new customer. |
| User Is Not Customer | Whether or not the user is not a customer. |
| User Is Returning Customer | Whether or not the user is a returning customer. |
| User Is Subscriber | Whether or not the user has completed at least one subscription order. |
| User Login | The login email address of the user. |
| User Name | Full name of the user. |
| User Number Of Completed A La Carte Orders | Total amount of orders completed by a user that are a la carte. |
| User Number Of Completed Subscription Orders | Total amount of orders completed by a user that was part of a subscription. |
| User Number Of Orders With Promos | The count of completed orders with a promo applied. |
| User Number Of Subscriptions | Total amount of subscriptions linked to a user. |
| User Oms User Id | Unique key generated by Solidus that identifies a user. |
| User Phone | Phone number of the user. |
| User Total Completed Order Count | Total amount of orders completed by a user. |
| User Unique Ordered Products | Unique products ordered by the user across all orders. |
| User Unique Ordered Skus | Unique SKUs ordered by the user across all orders. |
| Billing Address Created At (Universal) | Timestamp at which the address row was created - Universal Time Zone. |
| Billing Address Updated At (Universal) | Timestamp at which the address row was last updated - Universal Time Zone. |
| Order Approved At (Universal) | Reflects when the entity was approved in Solidus - Universal Time Zone. |
| Order Canceled At (Universal) | Reflects when the order was cancelled - Universal Time Zone. |
| Order Completed At (Central) | Reflects when the entity was moved to the `completed` state - Cental Time Zone. |
| Order Completed At (Eastern) | Reflects when the entity was moved to the `completed` state - Eastern Time Zone. |
| Order Completed At (Mountain) | Reflects when the entity was moved to the `completed` state - Mountain Time Zone. |
| Order Completed At (Pacific) | Reflects when the entity was moved to the `completed` state - Pacific Time Zone. |
| Order Completed At (Universal) | Reflects when the entity was moved to the `completed` state - Universal Time Zone. |
| Order Created At (Central) | Reflects when the entity was first created in Solidus - Cental Time Zone. |
| Order Created At (Eastern) | Reflects when the entity was first created in Solidus - Eastern Time Zone. |
| Order Created At (Mountain) | Reflects when the entity was first created in Solidus - Mountain Time Zone. |
| Order Created At (Pacific) | Reflects when the entity was first created in Solidus - Pacific Time Zone. |
| Order Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Order First Fulfillment Fulfilled At (Universal) | Timestamp at which the first shipment for that order was shipped - Universal Time Zone. |
| Order Last Adjustment Refund At (Universal) | Timestamp of the last return adjustment for an order - Universal Time Zone. |
| Order Last Adjustment Replacement At (Universal) | Timestamp of the last replacement adjustment for an order - Universal Time Zone. |
| Order Last Fulfillment Fulfilled At (Universal) | Timestamp at which the last shipment for that order was shipped - Universal Time Zone. |
| Order Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| Referral Converted At (Universal) | Reflects when the referral entity was first converted in Solidus - Universal Time Zone. |
| Referral Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Referral Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| Referrer Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Referrer Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| Shipping Address Created At (Universal) | Timestamp at which the address row was created - Universal Time Zone. |
| Shipping Address Updated At (Universal) | Timestamp at which the address row was last updated - Universal Time Zone. |
| Subscription Actionable Date (Universal) | The date of the next subscription installment. This date is updated after each successful installment. Subscriptions in an inactive state will be null - Universal Time Zone. |
| Subscription Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Subscription First Order Completed At (Universal) | The timestamp of the subscription's first completed order - Universal Time Zone. |
| Subscription Last Order Completed At (Universal) | The timestamp of the subscription's last completed order - Universal Time Zone. |
| Subscription Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| User Created At (Universal) | Timestamp at which the users row was created - Universal Time Zone. |
| User Date Of Birth (Universal) | Date of birth of the user - Universal Time Zone. |
| User Deleted At (Universal) | Timestamp at which the user's account was deleted - Universal Time Zone. |
| User First Order Completed At (Universal) | The timestamp of the user's first completed order - Universal Time Zone. |
| User First Subscription Order Completed At (Universal) | The timestamp of the user's first completed subscription order, regardless of subsequent subscriptions - Universal Time Zone. |
| User Last Order Completed At (Universal) | The timestamp of the user's last completed order - Universal Time Zone. |
| User Last Sign In At (Universal) | The last sign in timestamp for the user - Universal Time Zone. |
| User Updated At (Universal) | Timestamp at which the users row was last updated - Universal Time Zone. |
| Average Additional Tax Total | Total additional taxes for an order. |
| Average Adjustment Fulfillment Tax Total | Total adjustment shipment taxes for an order. |
| Average Adjustment Fulfillment Total | Total shipment adjustments applied to an order. |
| Average Adjustment Other Charges Total | Total of included additional adjustment charges paid for an order. |
| Average Adjustment Other Credits Total | Total of credits issued for an order. |
| Average Adjustment Refund Total | Total of return dollars for an order. |
| Average Adjustment Replacement Total | Total of replacement dollars for an order. |
| Average Adjustment Rma Refund Total | Total of refund dollards associated to an order that was returned via the RMA functionality of the Chord OMS. |
| Average Adjustment Tax Total | Total adjustment taxes an order. |
| Average Adjustment Total | Total of adjustment applied for an order as on the order. |
| Average Applied Gift Card Total | Total of gift card dollars that were used as a payment method in the order |
| Average Commission Total | Commission for an order. |
| Average Fulfillment Total | Total shipment for an order. |
| Average Gross Revenue | Gross amount of revenue generated by the order including items and shipments totals. Gross revenue = total - included\_tax\_total + shipment\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Average Included Tax Total | Total included taxes for an order. |
| Average Item Total | Total price for the order before adjustments. |
| Average Net Revenue | Net revenue generated by the order's items after promotions. Net revenue = total - included\_tax\_total + shipment\_total + adjustment\_total - additional\_tax\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Average Pre Paid Purchase Total | |
| Average Pre Paid Redemption Total | |
| Average Promo Total | Promotions applied to an order. |
| Average Purchased Gift Card Total | Total of gift card dollars that were purchased in the order. |
| Average Reimbursement Credit Total | The amount of store credits owed back in an order |
| Average Tax Total | Total taxes for an order. |
| Average Total Price | Total to be paid by the customer for an order. |
| Average Transaction Total | Total paid by the customer for a completed order. |
| Additional Tax Total | Total additional taxes for an order. |
| Adjustment Fulfillment Tax Total | Total adjustment shipment taxes for an order. |
| Adjustment Fulfillment Total | Total shipment adjustments applied to an order. |
| Adjustment Other Charges Total | Total of included additional adjustment charges paid for an order. |
| Adjustment Other Credits Total | Total of credits issued for an order. |
| Adjustment Refund Total | Total of return dollars for an order. |
| Adjustment Replacement Total | Total of replacement dollars for an order. |
| Adjustment Rma Refund Total | Total of refund dollards associated to an order that was returned via the RMA functionality of the Chord OMS. |
| Adjustment Tax Total | Total adjustment taxes an order. |
| Adjustment Total | Total of adjustment applied for an order as on the order. |
| Applied Gift Card Total | Total of gift card dollars that were used as a payment method in the order |
| Commission Total | Commission for an order. |
| Fulfillment Total | Total shipment for an order. |
| Gross Revenue | Gross amount of revenue generated by the order including items and shipments totals. Gross revenue = total - included\_tax\_total + shipment\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Included Tax Total | Total included taxes for an order. |
| Item Total | Total price for the order before adjustments. |
| Net Revenue | Net revenue generated by the order's items after promotions. Net revenue = total - included\_tax\_total + shipment\_total + adjustment\_total - additional\_tax\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Pre Paid Purchase Total | |
| Pre Paid Redemption Total | |
| Total Price | Total to be paid by the customer for an order. |
| Promo Total | Promotions applied to an order. |
| Purchased Gift Card Total | Total of gift card dollars that were purchased in the order. |
| Reimbursement Credit Total | The amount of store credits owed back in an order |
| Tax Total | Total taxes for an order. |
| Transaction Total | Total paid by the customer for a completed order. |
[title] Dynamic Data Settings
[path] Chord Data Platform/Overview/
# Introduction
With customizable data settings via the **Data Settings** page, you now have the power to tailor key aspects of your Chord Commerce platform to match your unique business needs. With an intuitive interface and flexible options, managing your data reporting preferences is easier than ever—putting you in control of ensuring a seamless experience.
# Features included
:::hint{type="info"}
**Note:** To set your organization’s default time zone, please reach out to [help@chord.co](mailto\:help@chord.co) for assistance.
:::
Admin-level users on the platform are able to set the following for their organization via the Data Setup page:
- **Set Time Zone **
- **By default, the time zone setting for your organization will be set to UTC.** If you would like for the Chord team to preset a different time zone for your organization, an admin-level user must confirm what timezone setting you would like to use for your organization.
- **Set Week Start Day (Week Definition)**
- **Set Fiscal Year Start and Fiscal Periods**
- **Settings Change Log**
- While we do not anticipate these organization-wide settings to change often, we will display a change log to show all users when and which a specific data setting was changed.
:::hint{type="warning"}
Any changes to these data settings will take place at your organization’s next scheduled data refresh and will apply across your entire organization.
:::
If you are a non-admin user, you will not have the ability to change any of the above settings and will see the options grayed-out, like so:
Additionally, data platform users will also be able to use new date fields in Explores that are affiliated with your organization's fiscal calendar. See more details below on how to use these new date fields!
# Get started
## Default time zone setting
- To support a unified time zone reporting structure, we removed all existing time zone field variations in explores.
- If you previously had any existing reports that utilized any of the specific time zone fields in explores, these fields have been automatically converted and mapped to the correct field.
- While all underlying time zone fields were updated, any **filters** on **dashboards only** will require updating the filter **title only**.
- You can update the filter title by following the steps below:
- Click into “Edit dashboard”
- Click the three dots next to the filter and click “Edit”
- Edit the title (ex: remove `(Universal)`)
::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-CAZs6YVRlV61Lwdj3NTgP-20250410-033037.png" size="100" width="1580" height="1454" position="center" darkWidth="1580" darkHeight="1454" showCaption="false" indent="5"}
:::Paragraph{listStyleType="disc" listStart="4" indent="4"}
Click "Update"
:::
:::Paragraph{listStyleType="disc" listStart="5" indent="4"}
Click "Save" to save your dashboard.
:::
- **By default, the time zone setting for your organization will be set to UTC.** If you would like for the Chord team to preset a different time zone for your organization, an admin-level user must confirm what time zone setting you would like to use for your organization.
:::hint{type="info"}
The Chord standard default time zone is UTC. To change your organization’s default time zone, please reach out to [help@chord.co](mailto\:help@chord.co) for assistance.
:::
## Set week start day
This setting will determine when a typical business reporting week begins for your organization.
:::hint{type="info"}
The Chord standard default definition of a week is **Monday through Sunday**.
:::
## Set fiscal year start and fiscal period
This setting will determine when a typical business reporting year begins for your organization and which fiscal calendar period your business reporting should follow.
Note that if you select a fiscal period other than the default calendar (Gregorian), you will be able to choose a starting month via the dropdown field. Note that Chord uses fiscal period calendar logic as governed by the [National Retail Federation](https://nrf.com/resources/4-5-4-calendar).
***The default calendar setting (Gregorian) will always have a starting month of January and will not be able to be changed.***
:::hint{type="info"}
The Chord standard default fiscal calendar start is **January** and uses the **Gregorian** calendar.
:::
## Using fiscal calendar date fields and filters
With dynamic data settings, you will be able to take advantage of both **Standard Dropdown Date Filters **as well as **Relative Date Filters**.
### Standard dropdown date filters
- **Standard Dropdown Date Filters** refer to any and all time fields presented in the existing dropdown fields. These dropdown filters all correspond to the Gregorian Fiscal Calendar and start on Monday.
- Note that the **Standard Dropdown Date Filters cannot be changed**, as these are system defaults.
- With the **Standard Dropdown Date Filters**, you can conduct any analysis related to a specific point in time (day, week, month, year, etc) and filter by standard dimensions.
:::hint{type="warning"}
These filters do not take into account your organization's fiscal calendar settings.
:::
### Relative date filters
- **Relative Date Filters** are used in Chord Quickstarts and takes into account your organization's default fiscal calendar settings.
- **Relative Date Filters** are normally used in reports like the **Business Overview dashboard**, when you want to see your store performance in the last month and need to pull the most recent sales data every time you load the report.
- To set up your reports correctly using **Relative Date Filters**, you need to apply the following filters:
1. Click into the **Explore** you want to use as the base of your report.
2. Select the **Relative Date Filter(s)** you need for your report.
3. Click on number of fiscal periods to filter the report.
4. Set the Last Fiscal Periods filter to **YES** (Note: This is a mandatory filter. If this is not set, your reporting will not be accurate).
# Troubleshooting & FAQs
**Q: I’m not able to edit these settings. What am I doing wrong?**
A: Check to make sure you’re an admin-level user on our platform before attempting to change data settings for your organization. If you are an admin-level user and you are not able to edit these settings, please reach out to [help@chord.co](mailto\:help@chord.co) for help.
**Q: I don't see fiscal calendar options for every date field. Why don't I see fiscal calendars for every date field?**
A: The Chord Commerce team pre-selected the most-used date fields across explores to fiscal calendar options since there are hundreds, if not thousands, of date field options. As such, not all date fields will have fiscal calendars associated to them. If there is a particular date field you need for reporting purposes that doesn't have a fiscal calendar associated but should have one associated, please reach out to [help@chord.co](mailto\:help@chord.co) and we can get you squared away!
[title] Chord AI Modeling
[path] Chord AI/
:::hint{type="info"}
This feature is currently available to **Team Admins** and **Developers** only. If you need assistance, please reach out to help\@chord.co!
:::
# Overview
Data modeling is the foundation for making your business data useful — and trustworthy. It’s the process of defining how your data is structured, connected, and labeled so that everyone in your organization can speak the same data language. It serves as a blueprint for how your store data is stored, used, and connected across all of your systems.
By building in relationships and calculated fields, Chord AI’s models act like a semantic layer, making the data more intelligible both to human users and AI agents. This helps facilitate clearer query writing, more robust automation, and more meaningful insight generation.
# Key Features
:::hint{type="warning"}
Remember to click the **Deploy Changes button **on the **Modeling **page to sync any changes or edits you make within **Chord AI Modeling**!
*This applies to any changes you make to the features below: ****Models, Relationships, and Calculated Fields.***
:::
## **Models**
Models on Chord AI combine schema definitions, metadata, relationships, calculated fields, and semantic logic derived from tables in your data source. Essentially, Models help users and Chord AI understand how your data is interrelated.
::Image[]{src="https://app.archbee.com/api/optimize/TmutqdeXiIw-V3gBZXVjd/tN_Tmb1NgbmBeQAa6scH7-20250930-131148.png" size="58" width="1448" height="656" position="center" darkWidth="1448" darkHeight="656" showCaption="false"}
To create a **Model**, follow the instructions below.
1. Navigate to **Models** on Chord AI.
2. Click “**Add Model**”.
3. Select a table from your connected data source and click “**Next**”.
4. Select the columns you want to add to the model you selected, then click "**>**" to include them. ***Note: Selecting the primary key of your table is available and *******optional*******.***
5. Save your **Model**.
## Relationships
Chord AI **Relationships** define how data tables and data models connect, enabling more efficient querying and analysis of linked data.
::Image[]{src="https://app.archbee.com/api/optimize/TmutqdeXiIw-V3gBZXVjd/xnybaEgNcvB_g9VBjeFM4-20250930-131254.png" size="42" width="780" height="752" position="center" darkWidth="780" darkHeight="752" showCaption="false"}
To add a **Relationship **to a model, follow the instructions below.
1. Navigate to **Models** on Chord AI.
2. Navigate to the specific model you wish to add a **Relationship**.
3. Select the **Actions** menu icon.
4. Click “**Add Relationship**”.
5. Define your **Relationship** properties:
- **From**: Select the left side table and column of this relationship.
- **To**: Select the right side table and column of this relationship.
- **Type**: Select the type of relationship (Many-to-one, One-to-many, One-to-one).
6. Save your **Relationship**.
*Additionally, note the following ****Relationships*** **cannot*** be created on Chord AI:*
**Self-Referential Relationships**
A self-referential relationship is when a column within a model points back to the same model. Chord AI currently does not support creating such self-referential relationships, where a column in a model references the same model. This limitation prevents the direct modeling of hierarchical or recursive data structures within a single model.
:::hint{type="warning"}
Example: In an `Employee` model, the `reportsTo` column may store the `ID` of another `Employee`, indicating the reporting structure within the organization.
:::
**Duplicate Relationships**
Chord AI does not permit the creation of duplicate relationships between the same pair of models using identical columns. This restriction ensures that each relationship remains unique, avoiding redundancy and potential confusion in model associations.
:::hint{type="warning"}
Example: If a relationship already exists between the `Order` and `Customer` models using the `customerID` field, you cannot create another relationship using the same `customerID` field between these models.
:::
## Calculated fields
Chord AI’s **Calculated Fields** lets you create custom columns by applying expressions (similar to formulas in Excel or in Google Sheets). **Calculated Fields** work like spreadsheet formulas for models, with a simple create/edit/delete flow.
::Image[]{src="https://app.archbee.com/api/optimize/TmutqdeXiIw-V3gBZXVjd/rv02BZmQ74aMGuSr3yZVh-20250930-131426.png" size="36" width="520" height="670" position="center" darkWidth="520" darkHeight="670" showCaption="false"}
Follow the steps below to add a **Calculated Field** to a** Model**. You can also view the list of available expressions.
1. Navigate to **Models** on Chord AI.
2. Navigate to the specific model you wish to add a **Calculated Field.**
3. Select the **Actions** menu icon.
4. Click “**Add Calculated Field**”.
5. Name your **Calculated Field**.
6. Select the expression you’d like to apply.
7. Save your **Calculated Field**.
Your **Calculated Field **will appear on the model once saved.
Additionally, if you pick a table that has relationships with other tables, you can "chain" them to drill into the other tables' fields within the **Calculated Field **modal.
To ***delete*** a pre-existing **Calculated Field**, navigate to the relevant **Model** with the **Calculated Field** you wish to delete. Click the ✏️ icon and click “**Delete**”.
::Image[]{src="https://app.archbee.com/api/optimize/TmutqdeXiIw-V3gBZXVjd/2npQNiQum0JC_4aBrqSLf-20250930-131539.png" size="46" width="496" height="238" position="center" darkWidth="496" darkHeight="238" showCaption="false"}
::Image[]{src="https://app.archbee.com/api/optimize/TmutqdeXiIw-V3gBZXVjd/PB4hdfd25p5WkANTlSFWL-20250930-131559.png" size="80" width="2212" height="1044" position="center" darkWidth="2212" darkHeight="1044" showCaption="false"}
# Additional guidelines
Chord AI will now allow users to apply an aggregation (like `MAX`) directly to a **source model field. **This is due to the following:
- **Source models** usually contain “raw” or “dimension” data (like `customer_id`, `created_at`, `product_name`).
- Aggregations (`MAX`, `SUM`, `AVG`, `COUNT_DISTINCT`, etc) are only meaningful when applied to **fact-like numeric measures** or after you’ve joined into the right model/table context.
- If Chord AI allowed aggregation on arbitrary source fields, the results would often be misleading or undefined (e.g. `MAX(customer_id)` isn’t a useful metric).
Chord AI errs on the side of protecting users from invalid queries.
Alternate ways of applying aggregations would be to:
1. Pick a measure field in a model that supports aggregation; or
2. Use relationships (joins) to hop into the next model where that aggregation makes sense.
[title] Chord AI Use Cases
[path] Chord AI/
At Chord, we’re not just giving brand operators a fast way to ask questions like, *“What are our top-selling SKUs by first-time vs. returning customers?”* and get answers in seconds. We’re also equipping technical teams with the framework to make those answers trustworthy, repeatable, and scalable.
With Chord AI, raw data becomes decisions you can act on with confidence. Each use case connects the dots: the business outcome marketers and operators care about, the technical foundations that make it reliable, and real-world examples of how it comes to life.
# At-a-glance: What you can ddo with Chord AI
| Chord AI Can Help You… | Business Value | Audience Fit |
| ------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------- |
| Analyze churn & LTV | Improve retention and growth forecasting | Marketing, Execs |
| Accelerate deployment of commerce data models | Shorten time-to-value, reduce repetitive SQL, scale to more use cases faster | Analytics, BI Teams |
| Build and activate audiences | Enable precise targeting and segmentation | Marketing, Growth |
| Enable flexible data access | Empower advanced users without bottlenecking engineering | Analytics, Technical Ops |
| Monitor data with smart monitoring | Ensure pipelines and metrics stay consistent, reducing troubleshooting time and maintaining trust in insights | Data Engineering, Analytics, Technical Ops |
| Personalize product experiences | Increase conversion & order value | Marketing |
| Standardize metrics with Context Studio | Ensure consistent definitions across teams, reducing confusion and building trust in data | Data Engineering, Analytics, Marketing, Execs |
| Understand customer journeys | Reveal multi-touch paths that drive conversion | Marketing, Product, CX |
| Understand campaigns (email/SMS) | Attribute engagement and ROI more clearly | Marketing, Lifecycle |
| Detect unexpected shifts in key metrics automatically (anomaly detection) | Gives teams peace of mind by continuously monitoring data and flagging anything unusual before it becomes a bigger issue | Operators, Marketing, Analytics |
# Core use cases
## For technical stakeholders
### **Accelerating data model deployment**
**What it is **
Chord AI helps standardize core e-commerce data models (like LTV, CAC, cohort retention) so that your internal teams can build reports and learn more about how your store is performing without requiring custom SQL for every question.
**Why it matters**
Data teams often spend time re-building the same models for every brand or team. Automating repetitive model-building accelerates delivery, reduces errors, and frees engineers to focus on higher-order analytics.
**How it works**
Chord Copilot leverages pre-built, commerce-specific transformations combined with AI assistance for customization. Instead of starting from scratch, technical users can modify and deploy tested models quickly, with confidence in their accuracy.
### Standardizing and scaling events and metrics
**What it is**
Chord AI’s Context Studio lets technical teams embed business rules, definitions, and formatting instructions directly into Copilot, ensuring consistent metric calculations across your organization.
**Why it matters**
Without a shared framework, different teams define key metrics (like “Net Revenue” or “Late Delivery Rate”) in inconsistent ways, leading to confusion and mistrust. Context Studio ensures that operators, marketers, and executives are all working from the same playbook, while technical teams reduce time spent reconciling discrepancies.
**How it works**
Through Context Studio, teams can:
- Define global instructions that apply to all queries (e.g., exclude canceled orders, enforce naming conventions).
- Set question-matching instructions for specific calculations (e.g., how to compute “Net Revenue”).
- Use SQL pairs to map natural language questions to pre-verified SQL queries, ensuring accuracy every time.
This creates a governed, repeatable way to track and activate events and metrics — one that scales as data complexity grows.
### **Smart alerts for data you can trust**
**What it is**
Chord AI actively monitors your data pipelines and metrics, automatically flagging unexpected changes in event delivery, schema consistency, or metric availability — before they turn into business problems.
**Why it matters**
When something breaks in your data, it rarely raises its hand. Broken events and missing metrics can quietly mislead teams, derail reporting, and erode confidence across the business. Chord AI’s smart alerts act like an extra set of eyes on your data — giving both technical and non-technical teams peace of mind that if something’s off, they’ll know.
**How it works**
Through Chord Copilot, brands can configure smart monitors that continuously scan for anomalies in event flow and modeled metrics. When Chord spots a pattern that doesn’t align — like a key metric dropping unexpectedly or a delay in pipeline delivery — Copilot flags it, adds context, and notifies the right people. It’s always running in the background, ensuring your data stays reliable and your team stays ahead of issues.
## For marketers
### **Keeping customers coming back**
**What it is**
Chord Copilot helps brands build stronger customer relationships — by surfacing not only who’s at risk of leaving, but also who’s most worth investing in. Whether it’s a subtle drop in engagement or a loyal customer who just crossed a meaningful milestone, Copilot helps you act on those signals with relevance and care.
**Why it matters**
Retention isn’t just about stopping churn — it’s about recognizing your best customers, keeping them engaged, and making them feel valued. The more you nurture those relationships, the more repeat purchases, referrals, and brand affinity you unlock. Copilot turns customer data into timely opportunities to reward loyalty and re-engage thoughtfully.
**How it works**
Using patterns in purchase history, AOV, engagement, and lifetime behavior, Copilot automatically identifies high-value customers who might be drifting — and loyal customers who deserve recognition. You get ready-to-activate audience segments and the context behind them, so you can run retention plays that are both personal and impactful. It's not about reacting — it's about proactively investing in the customers who drive your business forward.
**Sample prompts**
- *“Find my top 10% of customers by LTV this year — I’d love to offer them early access to our next launch.”*
- *“Who are my loyal customers showing signs of slowing down? I want to see customers with fewer orders in the last 90 days.”*
- *“Build an audience of highly engaged customers who haven’t purchased yet.”*
### **Optimizing ad spend**
**What it is **
Chord Copilot can help brands unify ad spend data across multiple different ad platforms to identify which campaigns and audiences drive true ROI.
**Why it matters**
Ad budgets are shrinking, but performance expectations are growing. Knowing where to double down — and where to cut spend — protects profitability.
**How it works**
Chord ingests ad campaign performance data from Meta, Google, TikTok, and more, which is all normalized into a single, trusted framework to provide instant insights on CAC, ROAS, and other key metrics to drive competitive ad spend analysis.
**Sample prompts**
- *“Show me which ad channels have the highest CAC compared to last month.”*
- *“Which campaign had the biggest drop in ROAS over the last 30 days?”*
- *“Which campaigns had the most clicks but lowest conversions over the last 30 days?”*
### **Surfacing personalized product recommendations**
**What is is **
Surface products each customer is most likely to buy next across different sales channels.
**Why it matters**
Personalized experiences increase conversion rates and average order value (AOV).
**How it works**
Chord Copilot combines smart filtering (such purchase history + similarity to other customers) and store product catalog metadata (such as product attributes) to deliver ranked product recommendations for customers.
**Sample prompts**
- *“Which products should I recommend to first time customers who bought a Product X?”*
- *“Which products should I recommend to customers who only ever buy on discount?”*
- *“Show me what products my highest LTV customers are most likely to purchase next.”*
[title] Chord AI Slack Bot
[path] Chord AI/
:::hint{type="warning"}
**Chord AI for Slack is currently in beta. **Features and behavior may change. For questions or feedback, reach out to your Chord account manager or email us at [help@chord.co](mailto\:help@chord.co)!
:::
**Chord AI** answers data questions about your store directly in Slack — revenue, orders, customers, and more — powered by your Chord data.
## Workspace requirement
Chord AI is only available in the **Chord Slack workspace**. The bot cannot be installed in your own brand or company Slack workspace.
If your brand doesn't already have access to the Chord Slack workspace via a shared external Slack channel, reach out to your account manager to get set up.
## Getting started
The bot can be invited to any shared channel in the Chord Slack workspace. Anyone with permission to invite users — whether a brand team member or a Chord employee — can add it using the /invite command or Slack's standard invite flow.
**Make sure to invite Chord AI** — not Chord AI (Staging) or Chord AI (Dev), which are internal Chord versions. **To avoid any confusion, we recommend letting your Chord team invite the bot to your shared channels first.**
The first time you interact with the bot, mention `@Chord AI` in the shared channel with Chord or send it a direct message. You'll receive a private "Connect Account" message — only visible to you. Click the button to link your Chord account.
Some additional tips:
- If you are signed out of Chord when you try to connect your account via Slack bot, simply log back into the site.
- Once you are back in, you will be presented with a screen to confirm your workspace.
- Once confirmed, you'll get a confirmation message to get back to Slack as soon as they confirm your workspace.
After that, you're ready to go — you won't need to connect again.
:::hint{type="info"}
If you have multiple storefronts or workspaces on Chord, reach out to [help@chord.co](mailto\:help@chord.co) for additional information.
:::
## Asking questions
**In a channel:** Mention the bot with your question, like so:
:::BlockQuote
@Chord AI what was my revenue last month?
:::
The bot replies in a thread under your message.
**Via DM:** Find "Chord AI" in your Slack Apps and send your question directly — no @mention needed.
## Follow-up questions
**In a channel:** Once the bot has answered, reply in the thread — no @mention needed. You can still use `@Chord AI` if you prefer.
**Via DM:** Just reply in the thread.
:::hint{type="info"}
Note: Only the person who started the thread can continue it.
If you reply in someone else's thread, you'll see a private message: "Only the thread owner can continue this conversation. Mention @Chord AI in the channel to start your own."
:::
**Tip:** Any text reply from the thread owner will be treated as a question to the bot — including casual reactions like "interesting!" If you want to react without triggering the bot, use a Slack emoji reaction instead.
## Clarification
Sometimes the bot needs more context before it can answer accurately. When that happens, it will ask a follow-up question in the thread. Reply in the thread with your answer — no @mention needed. The bot picks it up and continues.
Note: Only the person who started the thread can respond to a clarifier.
## Group DMs
Chord AI works in group DMs the same way it does in channels. Add the bot when creating a new group DM. Note that Slack does not allow apps to join an existing 1:1 conversation, so you'll need to start a fresh group DM that includes the Chord AI Slack bot.
Inside a group DM, use `@Chord AI ` to start a new thread. Thread ownership rules apply the same way as in channels.
## Show Reasoning / Show SQL / Open in Hub
Some answers include action buttons:
- **Show Reasoning** — the bot's step-by-step thought process for arriving at the answer
- **Show SQL** — the exact query run against your data
- **Open in Hub** — opens the corresponding conversation in Chord Hub (available in DMs only; replies in Hub will not update the Slack thread)
Anyone in the thread can view Reasoning and SQL. Open in Hub is tied to the thread owner's account.
## Interaction reference
| Scenario | What happens |
| ---------------------------------------------- | ------------------------------------------------------------------- |
| You @Chord AI in a channel | New thread starts under your message |
| You reply in your own thread (no @mention) | Bot treats it as a follow-up and responds |
| Another user replies in your thread | They see a private message directing them to start their own thread |
| Another user @Chord AI in a channel | A new independent thread starts for them |
| Another user clicks Show Reasoning or Show SQL | Works — no ownership restriction |
| You DM the bot | Works normally — no thread ownership concept applies |
| You haven't connected your account yet | You'll be prompted to connect |
[title] Salesforce
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/
### *Table names for customers utilizing Salesforce.*
- [Activities](https://docs.chord.co/BznB-activities)
- [Ads](https://docs.chord.co/ugIc-ads)
- [Braze Campaigns](https://docs.chord.co/braze-campaigns)
- [Conversions](https://docs.chord.co/3Yf6-conversions)
- [Line Items](https://docs.chord.co/T_jI-line-items)
- [Marketing Attribution](https://docs.chord.co/aGFm-marketing-attribution)
- [Orders](https://docs.chord.co/_-4U-orders)
- [Sales](https://docs.chord.co/jWmI-sales)
- [Sessions](https://docs.chord.co/fwj0-sessions)
### Accessing Chord Data Attribute Definitions:
:::hint{type="success"}
if you have any questions or need help, please reach out to us at [help@chord.co](mailto\:help@chord.co)
:::
[title] Users
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Chord OMS/
### **dim\_user\_revenue\_predictions**
| Name | Description |
| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| Frequency | The user's count of completed orders |
| Frequency Bucket | The user's count of completed orders, bucketed into pentile |
| Frequency Bucket Max | The maximum count of completed orders in the pentile bucket |
| Frequency Bucket Min | he minimum count of completed orders in the pentile bucket |
| Frequency Bucket Ranges | The range of completed orders in the pentile bucket |
| Monetary | The user's total net revenue for completed orders |
| Monetary Bucket | The user's total net revenue for completed orders, bucketed into pentiles |
| Monetary Bucket Max | The maximum total net revenue for completed orders in the pentile bucket |
| Monetary Bucket Min | The minimum total net revenue for completed orders in the pentile bucket |
| Monetary Bucket Ranges | The range of total net revenue for completed orders in the pentile bucket |
| User Prediction Lifetime Net Revenue | |
| User Prediction Probability Alive | |
| Recency | The days between user's last completed order and prediction date |
| Recency Bucket | The days between user's last completed order and prediction date, bucketed into pentile |
| Recency Bucket Max | The maximum days between last completed order and prediction date in the pentile bucket |
| Recency Bucket Min | The minimum days between last completed order and prediction date in the pentile bucke |
| Recency Bucket Ranges | The range of days between last completed order and prediction date in the pentile bucket |
| RFM Group | Recency, frequency, and monetary score. Concatenated values of the recency pentile, frequency pentile, and monetary pentile |
| Rfm Score | Recency, frequency, and monetary score. Calculated as (1/R) \* F \* √M |
| Rfm Score Bucket | Recency, frequency, and monetary score. Calculated as (1/R) \* F \* √M, bucketed into deciles |
| User Prediction Completed (Universal) | Date of the most recent prediction batch run - Universal Time Zone. |
| Average Predicted Lifetime Net Revenue | Average of Chord's predicted lifetime net revenue per user |
| Average Predicted Probability Alive | Average of Chord's predicted probability alive per user |
| Average RFM Score | Average of RFM Score |
| Predicted User Lifetime Net Revenue Total | Sum of Chord's predicted lifetime net revenue per user |
### **dim\_user\_product\_recommendations**
| Name | Description |
| ------------------------------------------ | ------------------------------------------------------------------- |
| Product Recommendation 1 | User's first recommended product. |
| Product Recommendation 2 | User's second recommended product. |
| Product Recommendation 3 | User's third recommended product. |
| Product Recommendation 4 | User's fourth recommended product. |
| Product Recommendation 5 | User's fifth recommended product. |
| User Prediction Completed (Universal) Date | Date of the most recent prediction batch run - Universal Time Zone. |
### **x\_fct\_trans\_users**
| Name | Description |
| ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Billing Address Address1 | The street address of the customer. |
| Billing Address Address2 | The optional second address of the customer. |
| Billing Address Alternative Phone | The customer's alternative phone number. |
| Billing Address City | The city where the address is. |
| Billing Address Company | A company name. |
| Billing Address Country Abbr | |
| Billing Address Country Name | Full name of the country. |
| Billing Address Firstname | First name of the customer. |
| Billing Address Id | Unique key generated by Chord to identify a unique address. |
| Billing Address Lastname | Last name of the customer. |
| Billing Address Oms Address Id | Unique key generated by Solidus that identifies an address. |
| Billing Address Phone | The customer's phone number. |
| Billing Address State Abbr | |
| Billing Address State Name | Full name of the state. |
| Billing Address Zipcode | The postal code. |
| Last Subscription Completed Oms Order Ids | List of completed OMS order ids by a subscription. |
| Last Subscription Completed Order Count | Total amount of orders completed by a subscription. |
| Last Subscription Completed Order Ids | List of completed order ids by a subscription. |
| Last Subscription First Order Unique Product Basket | Array of unique product names ordered in the first order per subscription. |
| Last Subscription First Order Unique Variant Basket | Array of unique SKUs ordered in the first order per subscription. |
| Last Subscription Has Subscription Tags | Whether or not the subscription has tags. |
| Last Subscription Id | Unique key generated by Solidus that identifies a subscription. |
| Last Subscription Interval In Days | The number of days in the subscription interval. |
| Last Subscription Is Auto Redeemed | Whether the pre-paid subscription will be auto-redeemed or if an action is required by the recepient. |
| Last Subscription Is Gift | Whether or not the pre-paid subscription is a gift. |
| Last Subscription Is Recurring | Whether the pre-paid subscription is recurring. |
| Last Subscription Last Order Unique Product Basket | Array of unique product names ordered in the latest order per subscription. |
| Last Subscription Last Order Unique Variant Basket | Array of unique SKUs ordered in the latest order per subscription. |
| Last Subscription Oms Pre Paid Subscription Id | ID generated by ChordOMS to identify a unique pre-paid subscription. |
| Last Subscription Oms Subscription Id | Unique key generated by Solidus that identifies a subscription. |
| Last Subscription Pre Paid Subscription Id | Chord generated unique id for the pre-pay subscription. |
| Last Subscription State | The current state of the subscription, enhanced with values for \`paused\` if the subscription is active and paused. |
| Last Subscription Tags | The list of tags associated with a subscription. |
| Last Subscription Tags Count | The number of tags associated with a subscription. |
| Last Subscription Unique Product Basket | Array of unique product names ever ordered per subscription. |
| Last Subscription Unique Variant Basket | Array of unique SKUs ever ordered per subscription. |
| Shipping Address Address1 | The street address of the customer. |
| Shipping Address Address2 | The optional second address of the customer. |
| Shipping Address Alternative Phone | The customer's alternative phone number. |
| Shipping Address City | The city where the address is. |
| Shipping Address Company | A company name. |
| Shipping Address Country Abbr | |
| Shipping Address Country Name | Full name of the country. |
| Shipping Address Firstname | First name of the customer. |
| Shipping Address Id | Unique key generated by Chord to identify a unique address. |
| Shipping Address Lastname | Last name of the customer. |
| Shipping Address Oms Address Id | Unique key generated by Solidus that identifies an address. |
| Shipping Address Phone | The customer's phone number. |
| Shipping Address State Abbr | |
| Shipping Address State Name | Full name of the state. |
| Shipping Address Zipcode | The postal code. |
| User Completed Oms Order Ids | List of completed OMS order ids by a user. |
| User Completed Order Ids | List of completed order ids by a user. |
| User Credit Category Basket | Array of credit categories (Gift Card, Reimbursement, Referral Credits, Prepaid Subscription, GMA) issued per user. |
| User Email | Email address of the user. |
| User First Completed Oms Order Id | OMS order id of the first order completed by a user. |
| User First Completed Order Id | Unique order id of the first order completed by a user. |
| User First Order Unique Ordered Products | Unique products ordered by the user in their first completed order. |
| User First Order Unique Ordered Skus | Unique SKUs ordered by the user in their first completed order. |
| User Has Ordered A La Carte | Whether or not the user has had at least one order that is not part of a subscription. |
| User Has Promo Applied In First Order | Whether or not the user has a promo applied to their first completed order. |
| User Has Subscription In First Order | Whether or not the user's first order is linked to a subscription. |
| User Id | Unique key generated by Chord to identify a unique user. |
| User Is Active Subscriber | Whether or not the user has an active subscription with at least one completed subscription order. An active subscription is one that is not cancelled or paused. |
| User Is Customer | Whether or not the user is a customer. |
| User Is New Customer | Whether or not the user is a new customer. |
| User Is Not Customer | Whether or not the user is not a customer. |
| User Is Returning Customer | Whether or not the user is a returning customer. |
| User Is Subscriber | Whether or not the user has completed at least one subscription order. |
| User Login | The login email address of the user. |
| User Name | Full name of the user. |
| User Number Of Completed A La Carte Orders | Total amount of orders completed by a user that are a la carte. |
| User Number Of Completed Subscription Orders | Total amount of orders completed by a user that was part of a subscription. |
| User Number Of Orders With Promos | The count of completed orders with a promo applied. |
| User Number Of Subscriptions | Total amount of subscriptions linked to a user. |
| User Oms User Id | Unique key generated by Solidus that identifies a user. |
| User Phone | Phone number of the user. |
| User Total Completed Order Count | Total amount of orders completed by a user. |
| User Unique Ordered Products | Unique products ordered by the user across all orders. |
| User Unique Ordered Skus | Unique SKUs ordered by the user across all orders. |
| Billing Address Created At (Universal) | Timestamp at which the address row was created - Universal Time Zone. |
| Billing Address Updated At (Universal) | Timestamp at which the address row was last updated - Universal Time Zone. |
| Last Subscription Actionable Date (Universal) | The date of the next subscription installment. This date is updated after each successful installment. Subscriptions in an inactive state will be null - Universal Time Zone. |
| Last Subscription Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Last Subscription First Order Completed At (Universal) | The timestamp of the subscription's first completed order - Universal Time Zone. |
| Last Subscription Last Order Completed At (Universal) | The timestamp of the subscription's last completed order - Universal Time Zone. |
| Last Subscription Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| Shipping Address Created At (Universal) | Timestamp at which the address row was created - Universal Time Zone. |
| Shipping Address Updated At (Universal) | Timestamp at which the address row was last updated - Universal Time Zone. |
| User Created At (Universal) | Timestamp at which the users row was created - Universal Time Zone. |
| User Date Of Birth (Universal) | Date of birth of the user - Universal Time Zone. |
| User Deleted At (Universal) | Timestamp at which the user's account was deleted - Universal Time Zone. |
| User First Order Completed At (Universal) | The timestamp of the user's first completed order - Universal Time Zone. |
| User First Subscription Order Completed At (Universal) | The timestamp of the user's first completed subscription order, regardless of subsequent subscriptions - Universal Time Zone. |
| User Last Order Completed At (Universal) | The timestamp of the user's last completed order - Universal Time Zone. |
| User Last Sign In At (Universal) | The last sign in timestamp for the user - Universal Time Zone. |
| User Updated At (Universal) | Timestamp at which the users row was last updated - Universal Time Zone. |
| Average Additional Tax Total | Sum of additional taxes paid for all completed orders for a user. |
| Average Adjustment Total | Sum of adjustment applied for all completed orders for a user as on the order. |
| Average Applied Gift Card Total | Sum of gift card amount(s) applied (used as payment method) by a user. |
| Average Commission Total | Sum of commission paid for all completed orders for a user. |
| Average Credit Authorized | Total amount of authorized credit per user. An authorized store credit decrements the amount of credit available. |
| Average Credit Balance | Total amount of credit issued per user. |
| Average Credit Invalidated | Total amount of invalidated credit per user. |
| Average Credit Issued | Total amount of credit issued per user. |
| Average Credit Used | Total amount of credit used per user. |
| Average First Order Gross Revenue | Gross revenue generated by the first completed order for a user. |
| Average First Order Net Revenue | Net revenue generated by the first completed order for a user. |
| Average Fulfillment Total | Sum paid for fulfillment for all completed orders for a user. |
| Average Gross Revenue | Sum of gross revenue generated by all completed orders for a user. |
| Average Included Tax Total | Sum of included taxes paid for all completed orders for a user. |
| Average Item Total | Sum of items price paid for all completed orders for a user. |
| Average Last Order Gross Revenue | Gross revenue generated by the last completed order for a user. |
| Average Last Order Net Revenue | Net revenue generated by the last completed order for a user. |
| Average Net Revenue | Sum of net revenue generated by all completed orders for a user. |
| Average Order Gross Revenue | Average gross revenue generated for a completed orders for a user. |
| Average Order Net Revenue | Average net revenue generated for a completed orders for a user. |
| Average Order Total Price | Average total price for a completed orders for a user. |
| Average Purchased Gift Card Total | Sum of gift card amount(s) purchased by a user. |
| Average Subscription Gross Revenue | Sum of gross revenue generated by all completed subscription orders for a user. |
| Average Subscription Net Revenue | Sum of net revenue generated by all completed subscription orders for a user. |
| Average Tax Total | Sum of total taxes paid for all completed orders for a user. |
| Average Total Price | Sum total paid for all completed orders for a user. |
| Average Transaction Total | Sum paid on all transactions for a user. |
| Additional Tax Total | Sum of additional taxes paid for all completed orders for a user. |
| Adjustment Total | Sum of adjustment applied for all completed orders for a user as on the order. |
| Applied Gift Card Total | Sum of gift card amount(s) applied (used as payment method) by a user. |
| Commission Total | Sum of commission paid for all completed orders for a user. |
| Credit Authorized | Total amount of authorized credit per user. An authorized store credit decrements the amount of credit available. |
| Credit Balance | Total amount of credit issued per user. |
| Credit Invalidated | Total amount of invalidated credit per user. |
| Credit Issued | Total amount of credit issued per user. |
| Credit Used | Total amount of credit used per user. |
| First Order Gross Revenue | Gross revenue generated by the first completed order for a user. |
| First Order Net Revenue | Net revenue generated by the first completed order for a user. |
| Fulfillment Total | Sum paid for fulfillment for all completed orders for a user. |
| Gross Revenue | Sum of gross revenue generated by all completed orders for a user. |
| Included Tax Total | Sum of included taxes paid for all completed orders for a user. |
| Item Total | Sum of items price paid for all completed orders for a user. |
| Last Order Gross Revenue | Gross revenue generated by the last completed order for a user. |
| Last Order Net Revenue | Net revenue generated by the last completed order for a user. |
| Net Revenue | Sum of net revenue generated by all completed orders for a user. |
| Total Price | Sum total paid for all completed orders for a user. |
| Purchased Gift Card Total | Sum of gift card amount(s) purchased by a user. |
| Subscription Gross Revenue | Sum of gross revenue generated by all completed subscription orders for a user. |
| Subscription Net Revenue | Sum of net revenue generated by all completed subscription orders for a user. |
| Tax Total | Sum of total taxes paid for all completed orders for a user. |
| Transaction Total | Sum paid on all transactions for a user. |
[title] Chord AI
[path] /
# **Introduction**
There’s no question that AI is reshaping the e-commerce landscape by giving modern brands the power to understand and serve their customers with more confidence. From surfacing smarter product recommendations to optimizing campaign timing and spend, AI has the potential to turn data into decision-making fuel faster than ever. AI helps brands not only react to customer behavior but anticipate it, offering a level of personalization and efficiency that been out-of-reach for brands geared for growth.
For e-commerce teams under pressure to do more with less, AI becomes a critical force multiplier. It automates repetitive analysis, uncovers trends that would otherwise go unnoticed, and delivers actionable insights in real time. Chord’s data platform is primed to champion modern brands by enabling better customer experiences and smarter growth for cutting-edge brands using data and unlocking smart insights to help hardworking teams reach their full potential.
**Find documentation on Chord AI below:**
::::LinkArray{contentSource="CUSTOM"}
:::LinkArrayItem
[Chord AI Implementation Guide](https://docs.chord.co/chord-ai-implementation-guide)
:::
:::LinkArrayItem
[Chord AI Technical Overview](https://docs.chord.co/chord-ai-technical-overview)
:::
:::LinkArrayItem
[Chord Copilot Chat](https://docs.chord.co/chord-copilot-chat)
:::
:::LinkArrayItem
[Chord AI Charts](https://docs.chord.co/chord-ai-charts)
:::
:::LinkArrayItem
[Chord AI Monitors](https://docs.chord.co/chord-ai-monitors)
:::
:::LinkArrayItem
[Chord AI Context](https://docs.chord.co/chord-ai-context)
:::
:::LinkArrayItem
[Chord AI Modeling](https://docs.chord.co/chord-ai-modeling)
:::
:::LinkArrayItem
[Chord AI Use Cases](https://docs.chord.co/chord-ai-use-cases)
:::
:::LinkArrayItem
[Chord AI FAQ](https://docs.chord.co/chord-ai-faq)
:::
::::
[title] Chord AI Models: Powered by Anthropic
[path] Chord AI/Untitled/
**Last updated: **March 2026
### Overview
Chord AI’s reasoning model has been upgraded to run on Anthropic's models — a leading large language model built for reliability, safety, and consistent performance. This article explains what changed, why we made the switch, and what it means for your day-to-day use of the platform.
### What changed
This upgrade has two parts:
1. **Rebuilt query infrastructure** — We made significant improvements to the underlying query-building layer that powers how Chord AI processes your inputs and generates responses. This is the core of the upgrade.
2. **New AI models** — Chord AI now runs on Anthropic's Claude models, each matched to a specific job:
- **Claude Haiku 4.5** — handles response generation and classifications after data is fetched, optimized for speed and consistency.
- **Claude Opus 4.5** — powers SQL generation, where accuracy and reasoning depth matter most.
Together, these changes represent a foundational upgrade — not just a model swap. Your existing workflows, integrations, and configurations are fully intact.
### Why we upgraded
We evaluated several leading AI models against the needs of Chord's commerce use cases. Anthropic's Claude stood out for three reasons:
- **Output stability** — Anthropic’s models produce consistent, structured responses across repeated and varied inputs, reducing unexpected results.
- **Reasoning quality** — Anthropic’s models handle complex, multi-step logic more reliably — important for tasks like forecasting, segmentation, and data interpretation.
- **Safety by design** — Anthropic builds safety and predictability into the core of their models, which aligns with how we think about trust in our platform.
### How we tested this upgrade
We did not ship this change without validation. Our process included:
1. **Use case coverage testing** — We ran the upgraded model against a broad set of real Chord workflows to confirm output quality and accuracy.
2. **Edge case review** — We stress-tested inputs that historically produced inconsistent or unexpected results.
3. **Output benchmarking** — We compared Anthropic’s responses against our previous model across key quality metrics before making the switch.
The upgrade was rolled out to production only after all tests met our internal quality thresholds.
### What to expect
- **No action required** — There is nothing you need to change or reconfigure.
- **Improved response quality** — You may notice outputs that are more structured and consistent than before.
- **Same interface** — Chord AI looks and works exactly as it did prior to this update.
### FAQs
**Will this affect my existing prompts or workflows?**
No. All existing prompts, automations, and integrations continue to work as before.
**Which Anthropic models are being used?**
Chord AI uses two models: Claude Haiku 4.5 for response generation and classifications, and Claude Opus 4.5 for SQL generation. We will communicate any future model changes in advance.
**Is my data shared with Anthropic?**
No. Your data is processed in accordance with Chord's existing privacy and data handling policies. Please refer to our Privacy Policy for full details.
**Can I recover my previous conversation threads?**
No. Thread history was reset as part of this migration and cannot be recovered. New threads going forward will be retained normally.
**Who do I contact if I notice unexpected behavior?**
Reach out to your Chord account team or submit a ticket through the Help Center.
[title] Subscriber Journey Explore
[path] Chord Data Platform/Data Models/Subscriptions/
## Overview
Customer-level lifetime view.
- Grain: **1 row per subscriber**
- Purpose: analyze **value, behavior, segmentation**
## When to use
- LTV analysis
- Behavioral segmentation
- Cohort analysis (first subscription month)
- Product affinity analysis
- Identify high-value or at-risk users
## Key dimensions & metrics
| Field | Description |
| -------------------------------- | --------------------------------------------------------------------------------------------------- |
| Cohort Month | First subscription month |
| Is Active Subscriber | Currently active |
| Is Churned | No active + has cancelled |
| Is Winback | Churned then reactivated |
| Is Paused Only | Only paused subs remain |
| Behavioral Flags | Ever churned/paused/reactivated |
| Active Subscription Count | Current active count |
| Cancelled Subscription Count | Total cancelled |
| Churn Count | Total cancellations |
| LTV Gross Revenue | Lifetime revenue |
| LTV Net Revenue | (ChordOMS only) |
| LTV Order Count | Total orders |
| Avg Order Value | Average across orders |
| Days Since First Subscription | Tenure |
| Days Since Last Order | Recency |
| Primary Product First Subscribed | First product |
| Distinct Products Ever | Unique products |
| Current Products Subscribed | Active products |
| Is Prepaid Subscriber | Customer has ≥1 prepaid (non-gift) subscription. ChordOMS only. |
| Is Gift Purchaser | Customer has purchased at least one gift subscription. ChordOMS only — resolved via original order. |
| Is Gifted Subscriber | Customer is a recipient of a gift subscription. ChordOMS only. |
## Example business questions
- Average LTV by cohort
- % of winback users
- Highest LTV by first product
- Top active customers
## Notes & caveats
- One row per **customer per provider**
- LTV Net Revenue only available for **ChordOMS**
- Winback = full churn + later reactivation
- **Subscriber Category is a current-state snapshot**, not lifetime behavior
- Gift/prepaid fields are **ChordOMS-only**
- **Gift Purchaser and Gifted Subscriber can both exist** for the same subscription (different users)
- These flags **do NOT override Subscriber Category**
## Glossary
| Term | What it Means | How to Interpret / Use | Where You’ll See It in Looker |
| ------------------------ | --------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Active Subscription** | A subscription that is currently ongoing. Includes both fully active and paused subscriptions. | Use this to understand the **current size of your subscriber base**. Note that paused users are still counted. | Subscription Metrics Daily (Active Count), Subscriber Journey (Is Active Subscriber), Subscriber Journey Monthly (Is Active Subscriber EOM), Product & Bundle Explores (Active Subscription Count) |
| **Churn / Churned** | A subscription that has been cancelled. Does not include pauses. | Represents **true customer loss**. Track this to understand retention issues. | Subscription Metrics Daily (Churned Count, Churn Rate), Subscriber Journey (Is Churned, Churn Count), Monthly (Is Churned EOM, Cancellations This Month), Events Enriched (Event Type = canceled), Movements (status\_cancelled) |
| **Winback** | A subscriber who cancelled all subscriptions and later returned by subscribing again. | Indicates **successful re-engagement** after churn. | Subscriber Journey (Is Winback), Subscriber Journey Monthly (Has Reactivated By EOM) |
| **Reactivation** | A previously cancelled subscription that becomes active again (subscription-level). | Measures **recovery of churned subscriptions**. | Subscription Metrics Daily (Reactivated Count), Movements (status\_reactivated), Events Enriched (Event Type = reactivated) |
| **Net New** | Net change in subscriptions: New + Reactivated − Cancelled. | Indicates **overall growth vs decline**. | Subscription Metrics Daily (Net New Count) |
| **LTV (Lifetime Value)** | Total revenue generated by a subscriber across all subscription orders. | Use to understand **customer value over time** and compare cohorts or segments. | Subscriber Journey (LTV Gross / Net Revenue), Subscriber Journey Monthly (LTV Gross Revenue EOM) |
| **EOM (End of Month)** | Metrics calculated as of the last day of a month. | Used for **consistent month-over-month comparisons** (retention, LTV growth). | Subscriber Journey Monthly (all EOM fields like Active EOM, LTV EOM) |
| **Solo Subscription** | A subscription that contains only one product. | Helps identify products that perform well **individually**. | Subscription Product Metrics Daily (Solo Subscription Count) |
| **Bundle** | A subscription that contains two or more products. | Useful for analyzing **product combinations and cross-sell behavior**. | Product Metrics (Bundle Subscription Count), Bundle Metrics Daily (all bundle fields) |
| **Movement** | Any change in a subscription’s state (created, cancelled, paused, resumed, reactivated, quantity/price change). | Use to understand **operational changes and trends** in subscriptions. | Subscription Movements Daily (Movement Type, Category), Events Enriched (Event Type) |
| **Provider** | The system managing subscriptions (Recharge, ChordOMS, CustomOMS). | Important context — **data availability and detail vary by provider**, which affects analysis. | All Explores (Provider filter present everywhere) |
[title] Browser Compatibility for Accessing the Chord Platform
[path] Chord Data Platform/Overview/
To ensure smooth access to your Chord OMS and data analytics platform, please review the following browser settings. Certain privacy features can interfere with login and session functionality.** As such, Chord recommends that you use the Google Chrome browser to access the platform. **
**Chrome browser users should also ensure that third-party cookies are allowed for optimal experience: **
If you choose to use a different browser, read on for additional guidance on how to update your browser settings to access Chord seamlessly.
### Safari users
Cross-site tracking prevention in Safari may block essential authentication functions.
➡️ **Solution**: For best results, users must **disable cross-site tracking **on Safari to log into the Chord platform.
### Firefox users
Strict or custom cookie settings in Firefox can block the cookies needed to access the Chord platform.
➡️ **Solution**: Use Firefox’s **standard tracking protection** mode when visiting the Chord platform.
If you're still having trouble accessing your dashboard, please reach out to [help@chord.co](mailto\:help@chord.co).
[title] Omni-Channel Sales Data Attributes (Amazon Source)
[path] Chord Data Platform/Data Sources/Untitled/Untitled/
For those clients with the Amazon Selling Partner source, this Explore combines Amazon and Shopify transactional line items into a unified explore.
- **Fulfillment Channel: **Amazon fulfillment channel (null for Shopify)
- **Fulfillment Tax Total**: Fulfillment tax (only for Amazon)
- **Line Item Tax Total**: Tax amount for the line item (only for Amazon)
- **Order Fulfillment State**: Fulfillment state of the order
- **Order Line Fulfillment Total**: Fulfillment cost of the line item
- **Order Line Gross Revenue**: Gross revenue from the line item
- **Order Line Net Revenue**: Net revenue after all deductions
- **Order Line Promo Total**: Total promotional discount applied to the line item
- **Order Line Refund Total**: Total refunded amount for the line item
- **Promo Total**: Total promotions on the order (only for Amazon)
- **Quantity**: Number of items purchased
- **Sales Channel**: Sales channel from which the order originated
- **SKU Price**: Unit price of the SKU
- **Source System**: Source of the data: either amazon or shopify
- **Tax Total**: Total tax on the order (only for Amazon)
- **Total Price**: Total price for the line item
- **Order Created At: **Timestamp when the order was created.
- **Total Fulfillment Tax Total**: Total Fulfillment Tax Total
- **Total Line Item Tax Total**: Total Line Item Tax Total
- **Total Order Line Fulfillment Total**: Total Order Line Fulfillment Total
- **Total Order Line Gross Revenue**: Total Order Line Gross Revenue
- **Total Order Line Net Revenue**: Total Order Line Net Revenue
- **Total Order Line Promo Total**: Total Order Line Promo Total
- **Total Order Line Refund Total**: Total Order Line Refund Total
- **Total Promo Total**: Total Promo Total
- **Total Quantity**: Total Quantity
- **Total SKU Price**: Total SKU Price
- **Total Tax Total**: Total Tax Total
- **Total Total Price**: Total Total Price
[title] Anonymous Audiences
[path] Chord Data Platform/Audiences/
# Overview
As is often the case in audience generation and identification, customer identifying details can be limited. Customer attributes like email address, phone number or User ID are easy to retrieve for customers who have *already* transacted, but not as easy to pull for *anonymous* customers that have yet to be identified. Chord's "blended user ID", along with a few additional configuration steps, helps to solve this and allows for audience building of yet to be identified customers.
## Example audience using Chord Blended ID
## Example audience using user ID & email
As [mentioned here](https://docs.chord.co/audiences-api#Yrz_M), some audiences may contain what Chord calls a “blended user ID,” which is derived from the Chord data models to contain the **CDP User ID** - if one exists - else the **Anonymous ID**. This use case is particularly useful when mixing users that may or may not have a known CDP User ID; by using the CDP Blended User ID, audiences can be created for both users and visitors using the same ID.
:::hint{type="info"}
**Note:** Pre-built audiences like `At-Risk Customers`, `Brand Champions` and `Product Loyalists` are examples of audiences containing user-specific identifiable properties like user name, user ID and user email (which is a property that can be used downstream in most configured data activation destinations to identify and link customer activity).
Should you have any questions, please reach out to [help@chord.co](mailto\:help@chord.co).
:::
# How to pass along blended ID
For anonymous/unidentified audiences to be effectively used, ***Chord's blended user ID ***must be sent downstream to all relevant destinations where the audience is to be activated. This passage requires that the Data Activation destination has a ***corresponding destination configured within Chord CDP.***
In other words, if you are looking to leverage blended IDs in audiences activated to downstream destinations, you **must** configure the corresponding pixel and/or device mode destination in the Chord CDP which is receiving events from a front-end source.
:::hint{type="info"}
**Note:** Pixel and device mode destinations in the Chord CDP typically reflect destinations receiving events from your store *front-end*.
**Examples include:**
- Facebook Pixel
- Google Analytics (Device Mode)
- TikTok Pixel
Should you have any questions, please reach out to [help@chord.co](mailto\:help@chord.co).
:::
# Examples
## Facebook Ads
To help better connect unidentified audiences in your Facebook Ads accounts with their corresponding front-end user events and behavior, it is recommended that the ***Facebook Pixel*** destination be configured in Chord CDP to receive front-end events from your storefront:
Configuring the Facebook Pixel destination in Chord CDP will help facilitate flow of user-specific identifiers downstream into your configured Facebook Ads account (via [Chord Data Activations](https://docs.chord.co/gFnF-data-activations)). [Facebook's customer information parameters](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/customer-information-parameters) define which attributes can be sent and in which format they are required. The more customer information parameters passed along, the higher likelihood of profile match and identification.
## TikTok Ads
To help better connect unidentified audiences in your TikTok Ads accounts with their corresponding front-end user events and behavior, it is recommended that the ***TikTok Pixel ***destination be configured in Chord CDP to receive front-end events from your storefront:
Configuring the TikTok Pixel destination in Chord CDP will facilitate flow of [event-specific attributes ](https://ads.tiktok.com/help/article/how-to-set-up-matching-events-with-events-api?lang=en)like Click ID, Email and Phone, and External ID. This ***External ID*** is mapped to the "blended User ID" captured on the Chord side. Events with an included external ID will increase match rates for improved measurement and audience creation downstream in TikTok Ads.
## Google Ads
To help better connect unidentified audiences in your Google Ads accounts with their corresponding front-end user events and behavior, it is recommended that the ***Google Analytics (Device Mode) ***destination be configured in Chord CDP to receive front-end events from your storefront:
Similar to the destinations above, configuring the Google Analytics (Device Mode) destination in Chord CDP allows for passage of client-side user-specific attributes that can aid in user identification downstream in Google Ads. When the destination is configured, [Google Analytic's user\_id](https://developers.google.com/analytics/devguides/collection/ga4/user-id?client_type=gtag)value will be collected (if available) in the storefront and sent through to Google to be used as another attribute for matching purposes.
:::hint{type="info"}
**Note: **As always, please reach out to [help@chord.co](mailto\:help@chord.co) for assistance.
:::
[title] Chord AI FAQ
[path] Chord AI/
## Data security & privacy
**How does Chord AI protect my data?**
Chord AI adheres to the same high standards of data security and privacy as the rest of the Chord platform. Your data never leaves our secure environment unless explicitly configured by your team.
**Is any of my customer or business data sent to third-party AI providers?**
No. Chord AI processes your data within our platform and does not send any raw business or customer data to external AI providers.
**Does Chord AI use my data to train external LLMs?**
Never. Your data is not used to train, fine-tune, or improve any models outside your organization. Chord AI uses a multi-LLM architecture, handling different data components strategically to ensure your data stays private. Your sensitive data remains protected without risk of being sent or trained to public LLMs.
**Can I control what data Chord AI has access to?**
Yes. Chord AI uses only the data that a given user is permitted to access. If a user can’t view the data on the Chord platform, they can’t query it with AI either.
## Functionality & capabilities
**What can I ask Chord Copilot to do?**
You can ask questions about your customers, orders, products, and performance—Chord Copilot translates these into SQL and returns accurate results from your data.
**What types of questions work best with Chord Copilot?**
Chord Copilot is best with clear, specific questions. Examples:
- “What was our average order value last month?”
- “Which products are most frequently purchased by subscribers?”
**Can I see the SQL behind Chord Copilot’s answers?**
Yes. Chord Copilot is built for transparency. Every response includes the SQL used (easily viewed if you click on the “View SQL” button at the bottom of the answer from Chord Copilot Chat), so you can validate or reuse it as needed.
## Access & use
**Who can use Chord AI in my organization?**
Chord AI access is permission-based. Currently, all users can query data with Chord Copilot Chat during our alpha release. Interacting with Chord AI Context Studio features - creating and adding new Instructions and SQL Pairs - will be available to Team Admins only.
**Does using Chord AI require special training or technical knowledge?**
No training required. Chord AI is designed to work for marketers, operators, and analysts—no SQL background required.
[title] Braze Campaigns
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Salesforce/
### **x\_fct\_campaigns**
| Name | Description |
| ------------------------------- | ------------------------------------------------------------------------------------------------------- |
| Campaign Api Id | Unique key generated by Chord to identify the API ID of the campaign. |
| Campaign App Group Id | Unique key generated by Chord to identify the workspace this event belongs to. |
| Campaign Braze Api Id | API ID of the campaign. |
| Campaign Braze App Group Id | Internal-use Braze ID of the workspace this event belongs to. |
| Campaign Braze Id | Internal-use Braze ID of the campaign. |
| Campaign Id | Unique key generated by Chord to identify the Braze campaign. |
| Campaign Name | Name of the campaign. |
| Campaign Updated At (Universal) | Timestamp of when the campaign was updated - Universal Time Zone. |
| Event Ts (Central) | Timestamp of the event - Cental Time Zone. |
| Event Ts (Eastern) | Timestamp of the event - Eastern Time Zone. |
| Event Ts (Mountain) | Timestamp of the event - Mountain Time Zone. |
| Event Ts (Pacific) | Timestamp of the event - Pacific Time Zone. |
| Event Ts (Universal) | Timestamp of the event - Universal Time Zone. |
| Average Abort Count | Count of abort events. For either SMS or emails. |
| Average Bounce Count | Count of email bounce events. |
| Average Carrier Send Count | Count of messages sent through carriers. |
| Average Channel | Indicates the channel of the event. Accepted values include: Email, SMS, Push Notification, InApp. |
| Average Click Count | Count of click events. Either in Emails or SMS. |
| Average Conversion Count | Count of conversion events. |
| Average Delivery Count | Count of email delivery events. |
| Average Delivery Failure Count | Count of delivery failures in SMS messages. |
| Average Event Id | Unique key generated by Chord for each event. |
| Average Impression Count | Count of impression events. |
| Average Inbound Receive Count | Count of inbound messages received in SMS events. |
| Average Influenced Open Count | Count of influenced open events for push notifications. |
| Average Markasspam Count | Count of emails marked as spam. |
| Average Open Count | Count of email open events. |
| Average Rejection Count | Count of rejection events in SMS messages. |
| Average Revenue | Total revenue generated. |
| Average Send Count | Count of sent messages. Either SMS or Emails. |
| Average Softbounce Count | Count of email soft bounce events. |
| Average Unique Click Count | Count of unique email click events. |
| Average Unique Open Count | Count of unique email open events. |
| Average Unsubscribe Count | Count of email unsubscribe events. |
| Abort Count | Count of abort events. For either SMS or emails. |
| Bounce Count | Count of email bounce events. |
| Carrier Send Count | Count of messages sent through carriers. |
| Channel | Indicates the channel of the event. Accepted values include: Email, SMS, Push Notification, InApp, etc. |
| Click Count | Count of click events. Either in Emails or SMS. |
| Conversion Count | Count of conversion events. |
| Delivery Count | Count of email delivery events. |
| Delivery Failure Count | Count of delivery failures in SMS messages. |
| Event Id | Unique key generated by Chord for each event. |
| Impression Count | Count of impression events. |
| Inbound Receive Count | Count of inbound messages received in SMS events. |
| Influenced Open Count | Count of influenced open events for push notifications. |
| Markasspam Count | Count of emails marked as spam. |
| Open Count | Count of email open events. |
| Rejection Count | Count of rejection events in SMS messages. |
| Revenue | Total revenue generated. |
| Send Count | Count of sent messages. Either SMS or Emails. |
| Softbounce Count | Count of email soft bounce events. |
| Unique Click Count | Count of unique email click events. |
| Unique Open Count | Count of unique email open events. |
| Unsubscribe Count | Count of email unsubscribe events. |
[title] Variants
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Chord OMS/
### **x\_fct\_trans\_variants**
| Name | Description |
| ------------------------------ | ----------------------------------------------------------------------------------- |
| Product Store Id | Unique key generated by our models that uniquifies a store. |
| Product Store Name | The name of the store. |
| Product Store Oms Admin Url | The Admin URL of that OMS. |
| Product Store Oms Id | Unique key generated by Chord that uniquifies an OMS. |
| Product Store Oms Store Id | Unique key generated by our models that uniquifies a store. |
| Product Store Oms Type | The type of the OMS. |
| Product Store Id | Unique key generated by our models that uniquifies a store. |
| Product Store Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Product Store Url | The Storefront URL of of the store. |
| Variant Cost Price | The manufacturing cost of the variant. |
| Variant Depth | The depth of the variant. |
| Variant Height | The height of the variant. |
| Variant Id | Unique key generated by Chord to identify a unique product variant. |
| Variant Is Backorderable | Whether the stock item has at least one location where it is back-orderable or not. |
| Variant Is Inventory Tracked | Whether the inventory should or should not be tracked for this variant. |
| Variant Is Master | Whether this represents the master SKU or not. |
| Variant Is Subscribable | Whether or not a customer can ask to subscribe to this product. |
| Variant Oms Variant Id | Unique key generated by Solidus that identifies a variant. |
| Variant Option Color | Color of the variant. |
| Variant Option Format | Format of the variant. |
| Variant Option Quantity | Quantity of item for the variant. |
| Variant Option Size | Size of the variant. |
| Variant Position | The position of the variant in the list of variants. |
| Variant Sku | The SKU of the variant. |
| Variant Weight | The weight of the variant. |
| Variant Width | The weight of the variant. |
| Variant Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Variant Deleted At (Universal) | Reflects when the entity was deleted - Universal Time Zone. |
| Variant Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| Average Count On Hand | The sum of on-hand stock currently available for the variant. |
| Count On Hand | The sum of on-hand stock currently available for the variant. |
******
[title] E-commerce Data Ingestion
[path] Chord Data Platform/Data Sources/
Chord can ingest data from different e-commerce systems for analysis. Two methods are available:
1. **Chord Ingest **(preferred): a Chord-built system that will pull data from a customer's e-commerce system.
2. **Chord API** (optional): customers can use Chord's REST API to push data from their source system. Reach out to us at [help@chord.co](mailto\:help@chord.co) for more details.
# Chord Ingest
Chord Ingest is Chord's solution for customer not using Shopify (e.g. Magento, BigCommerce, SalesForce Commerce Cloud). To get started, simply input the URL for your system and a valid API key into your Chord instance.
That's it!
## Sample Data Mapping
Since different e-commerce platforms use different names for equivalent records, the table below shows how source records are mapped to Chord's data model.
Below is an example of a data mapping from Magento, a common e-commerce system, and Chord:
### Product
| Chord | Magento |
| ------------ | ----------------------------------- |
| Name | `name` |
| Slug | Combination of the `name` and `id`. |
| SKU | `sku` |
| External ID | `id` |
| Product Type | `type_id` |
### Variant
| Chord | Magento |
| ----------- | ------- |
| SKU | `sku` |
| Price | `price` |
| External ID | `id` |
### Order
| Chord | Magento |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Line items | `order.items[]` |
| Discount | `order.items[].discount_*` |
| Tax | `order.items[].tax_*` |
| Customer | `order.customer_*` |
| Billing address | `order.billing_address` |
| Shipping address | `order.shipping_address` |
| Number | `increment_id` |
| State | Depends on ... |
| Payment state | Depends on `total_due`: * If `total_due` > 0: `balance_due`
* If `total_due` \< 0: `credit_owed`
* If `total_due` == 0: `paid`
* Otherwise: `void` |
| Shipment state | Depends on `status`: * `pending`: `pending`
* `processing`: `ready`
* `complete`: `shipped` |
| Email | `email` |
| Currency | `base_currency_code` |
| Item total | `subtotal` |
| Total | `grand_total` |
| Adjustment total | `grand_total` - `subtotal` |
| Shipment total | `shipping_incl_tax` |
| Promo total | `discount_amount` |
| Payment total | `total_paid` |
| Item count | `total_item_count` |
| Channel | `chord` |
| Included tax total | `base_subtotal_incl_tax` |
| External ID | `id` |
### Line Item
| Chord | Magento |
| -------------------- | -------------------------------------- |
| Quantity | `qty_ordered` |
| Additional tax total | `tax_amount` |
| Price | `price` |
| External ID | `item_id` |
| SKU | `sku` |
| Adjustment total | `additional_tax_total` + `promo_total` |
| Slug | `name` |
| Promo total | `discount_amount` |
### Line Item Discount
| Chord | Magento |
| ------------- | ------------------------- |
| Adjustable ID | `line_item.id` |
| Amount | `discount_amount` |
| Order ID | `line_item.order.id` |
| External ID | "`line_item.id`-discount" |
### Line Item Tax
| Chord | Magento |
| ------------- | -------------------- |
| External ID | "`line_item.id`-tax" |
| Adjustable ID | `line_item.id` |
| Amount | `tax_amount` |
| Order ID | `line_item.order.id` |
### Payment
| Chord | Magento |
| ------ | -------------------------------------------------------------------- |
| Amount | `amount_paid` |
| State | If `amount_paid == amount_ordered`, then `paid`; `pending` otherwise |
| Number | "`entity_id`-`method`" |
### Shipment
| Chord | Magento |
| --------------- | ---------------------- |
| Inventory units | `shipment.items[]` |
| External ID | `entity_id` |
| Number | `entity_id` |
| State | `order.shipment_state` |
| Cost | `order.shipment_total` |
| Shipped At | `created_at` |
### Inventory Unit
| Chord | Magento |
| ----------- | ----------------------------------------------------------------------------------------------------------------- |
| External ID | "`order_item_id`-`index`"; where `index` is a counter of the number of inventory units listed under the shipment. |
| SKU | `sku` |
| Variant ID | Query the Chord database for the variant by `sku` and use the `id` |
### User
| Chord | Magento |
| ----- | ------------------------------------------ |
| Name | "`customer_firstname` `customer_lastname`" |
| Email | `customer_email` |
### Address
| Chord | Magento |
| ----------- | -------------------------------------------------------------------------- |
| City | `city` |
| External ID | `entity_id` |
| Firstname | `firstname` |
| Lastname | `lastname` |
| Address 1 | `street.first` |
| Address 2 | `street.second` |
| Zipcode | `postcode` |
| Phone | `telephone` |
| State | Query the Chord database for the `region_code` and return the state ID |
| Country | Query the Chord database where `iso: country_id` and return the country ID |
## How It Works
When a product is synced, all associated variants are also synced.
When an order is synced, all associated records are also synced:
- Line items
- Discount
- Tax
- Shipments
- Inventory units
- Customer
- Billing address
- Shipping address
- Payments
Chord replicates data 1-1 from the source system, performing the minimum transformations necessary for successful replication.
Chord syncs data daily from a customer's e-commerce system:
1. Product sync: sync all products and variants in the customer's catalogue.
2. Order sync: sync completed orders and associated records updated in the previous 24 hours.
[title] Sales
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Chord OMS/
### **x\_fct\_trans\_sales**
| Name | Description |
| ----------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Affiliate Email | Email address of the affiliate. |
| Affiliate Id | Unique key generated by Chord to identify a unique affiliate. |
| Affiliate Name | Full name of the user. |
| Affiliate Seen Emails | List of email addresses seen. |
| Affiliate User Id | Unique key generated by Chord to identify a unique user. |
| Billing Address Address1 | The street address of the customer. |
| Billing Address Address2 | The optional second address of the customer. |
| Billing Address Alternative Phone | The customer's alternative phone number. |
| Billing Address City | The city where the address is. |
| Billing Address Company | A company name. |
| Billing Address Country Abbr | no description |
| Billing Address Country Name | Full name of the country. |
| Billing Address Firstname | First name of the customer. |
| Billing Address Id | Unique key generated by Chord to identify a unique address. |
| Billing Address Lastname | Last name of the customer. |
| Billing Address Oms Address Id | Unique key generated by ChordOMS that identifies an address. |
| Billing Address Phone | The customer's phone number. |
| Billing Address State Abbr | no description |
| Billing Address State Name | Full name of the state. |
| Billing Address Zipcode | The postal code. |
| Order Adjustment Types | List of distinct adjustment reasons for adjustments made to the order. |
| Order Admin Url | The Admin URL of pointing to the order. |
| Order Applied Discount Codes | List of promotion codes applied to the order. |
| Order Applied Discount Codes Count | Count of promotion codes applied to the order. |
| Order Applied Discount Ids | List of promotion ids applied to the order. |
| Order Applied Discount Names | List of promotion names applied to the order. |
| Order Applied Discount Names Count | Count of promotion names applied to the order. |
| Order Cart Url | Url of the cart which contains the order. |
| Order Channel | The channel from which the order is created. |
| Order Completed Order Rank By Subscription | Allows to rank completed orders by completion date for a subscription. |
| Order Completed Order Rank By User | Allows to rank completed orders by completion date for a user. |
| Order Contains Refund | Whether or not the order contains refund adjustments or refunds that are processed outside of the Chord OMS adjustment systems (for example via RMAs or cancellations). |
| Order Contains Replacement | Whether or not the order contains replacement adjustments or shipped replacement items (following an RMA authorization). |
| Order Contains Return | Whether or not the order contains returns (authorized RMAs). |
| Order Contains Rma Refund | Whether or not the order contains RMA refunds (refunds issued after an RMA was requested and authorized). |
| Order Contains Rma Store Credits | This column is not documented. |
| Order Currency | The currency for this order. |
| Order Customer Lifetime Month | Number of months between the current order's completion date and the user's first order completion date. First orders have a value of 1. |
| Order Customer Lifetime Week | Number of weeks between the current order's completion date and the user's first order completion date. First orders always have a value of 1. |
| Order Email | The email address of the customer that made the order. |
| Order Financial State | The current payment state of the order. |
| Order Fulfillment Ids | Array of unique keys generated by Chord to identify the unique shipments for an order. |
| Order Fulfillment Numbers | The unique identifier for this shipment. |
| Order Fulfillment State | The current shipment state of the order. |
| Order Has Discount | Whether or not the order has promotions applied to it. |
| Order Has Order Tags | Whether or not that order has tags. |
| Order Hours From Order To First Fulfillment | Number of hours between order completion and first order shipment; how long it takes a company to get the initial product out to a customer. |
| Order Hours From Order To Last Fulfillment | Number of hours between order completion and last order shipment. |
| Order Id | Unique key generated by Chord to identify a unique order. |
| Order Is Canceled | Whether or not the order is canceled. The order is considered canceled when the canceled\_at date is not null. |
| Order Is Completed | Whether or not that order is completed. The order is considered completed when the completed\_at date is not null. This means that the order does not necessarily have a state = 'complete', since states can change after the order completion (for example in the case of a refund). |
| Order Is First Completed Order | Whether or not that order was the first completed order for a user. |
| Order Is First Order | Whether or not that order was the first order for a user. |
| Order Is First Subscription Completed Order | Whether or not that order was the first completed order for a subscription. |
| Order Is First Subscription Order | Whether or not that order was the first order for a subscription. |
| Order Is Fulfilled | Whether or not that order has shipped. |
| Order Is Part Of Subscription | Whether or not that order is part of a subscription. |
| Order Is Pre Paid Purchase | Whether the order the orderincludes the purchase of a pre-payment; this could be a gift subscription, pre-pay subscription, or gift card. |
| Order Is Pre Paid Redemption | Whether the order included the redemption of a pre-payment; this could be the redemption of a gift subscription, pre-pay subscription, or gift card. |
| Order Is Referred By Affiliate | Whether or not the user is referred by an affiliate. |
| Order Is Referred By Referrer | Whether or not the user is referred by a referrer. |
| Order Is Replacement | True when the order is a replacement order. |
| Order Is Suspicious Referral Conversion | Wether this represents a suspicous referral conversions or not. |
| Order Item Id | Unique key generated by Chord to identify a unique order. |
| Order Item Line Items Quantity | Sum of line items quantities per order. |
| Order Item Product Basket | List of product names per in the order. |
| Order Item Product Basket Count | Number of products in the order. |
| Order Product Basket | The titles of products for a given order array converted to a string. |
| Order Item Total Line Item Unit Quantity | Sum of line item units in the order. |
| Order Item Total Line Items Quantity | Sum of line items quantities per order. |
| Order Item Unique Product Basket | List of unique product names per in the order. |
| Order Item Unique Product Basket Count | Number of unique products in the order. |
| Order Unique Product Basket | The list of unique products for a given order array converted to a string. |
| Order Item Unique Unit Basket | List of unique units in the order. |
| Order Item Unique Unit Basket Count | Count of unique units in the order. |
| Order Unit Basket | The list of units for a given order array converted to a string. |
| Order Item Unique Variant Basket | List of unique variant names per in the order. |
| Order Item Unique Variant Basket Count | Number of unique variants in the order. |
| Order Unique Variant Basket | The list of unique variants for a given order array converted to a string. |
| Order Item Unit Basket | List of all units in the order. |
| Order Item Unit Basket Count | Count of all units in the order. |
| Order Unique Unit Basket | The list of unique units for a given order array converted to a string. |
| Order Item Variant Basket | List of variant names per in the order. |
| Order Item Variant Basket Count | Number of variants in the order. |
| Order Variant Basket | The titles of variants for a given order array converted to a string. |
| Order Number | Human-readable unique key generated by ChordOMS that identifies an order. It begins with a set of Tenant-Store defined letters and ends in a nine-digit number (for example, CHORD-123456789). This number is shown to the users in various places. These combinations are unique for a given Store. |
| Order Oms Order Id | Unique key generated by ChordOMS that identifies an order. |
| Order Rank By User | Allows to rank completed orders by completion date for a user. |
| Order Tags | List of tags associated to the order. |
| Order Tags Count | Number of tags associated to the order. |
| Order Referral Conversion Suspicious Reasons | A list of reasons explaining why the referral conversion is suspicious. |
| Order Referrer User Email | The email address of the customer identified with the referral. |
| Order Special Instructions | Any special shipping instructions that have been specified by the customer during checkout. |
| Order State | The current state of the order. |
| Order Store Id | Unique key generated by our models that uniquifies a store. |
| Order Store Name | The name of the store. |
| Order Store Oms Admin Url | The Admin URL of that OMS. |
| Order Store Oms Id | Unique key generated by Chord that uniquifies an OMS. |
| Order Store Oms Store Id | Unique key generated by our models that uniquifies a store. |
| Order Store Oms Type | The type of the OMS. |
| Order Store Id | Unique key generated by our models that uniquifies a store. |
| Order Store Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Order Store Url | The Storefront URL of of the store. |
| Order Subscription Customer Lifetime Month | Number of months between the current order's completion date and the user's first subscription order completion date. First orders have a value of 1. |
| Order Subscription Customer Lifetime Week | Number of weeks between the current order's completion date and the user's first subscription order completion date. First orders always have a value of 1. |
| Order User Referral Code | Unique key generated by ChordOMS that represents the user's referral code. |
| Order Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store. |
| Referral Conversion Rank By Referrer | Allows to rank a referral conversion by referrer. |
| Referral Id | Unique key generated by Chord to identify a unique referral identifier. |
| Referral Is Converted | Wether this represents a converted referral or not. |
| Referral Is First Conversion | Whether or not the referral was the referrer's first converted referral. |
| Referral Is First Non Suspicious Conversion | Whether or not the referral was the referrer's first non suspicious converted referral. |
| Referral Is Suspicious | Wether this represents a suspicous referral conversions or not. |
| Referral Non Suspicious Conversion Rank By Referrer | Allows ranking of non-suspicious referral conversion by the referrer. |
| Referral Oms Referral Conversion Id | Unique key generated by ChordOMS that identifies a referral conversion. |
| Referral Suspicious Reasons | A list of reasons explaining why the referral conversion is suspicious. |
| Referrer Currency | The currency for this referral identifier. |
| Referrer Email | The email address of the customer identified with the referral. |
| Referrer Id | Unique key generated by Chord to identify a unique referral identifier. |
| Referrer Oms Referral Identifier Id | Unique key generated by ChordOMS that identifies a referral identifier. |
| Referrer User Referral Code | Unique key generated by ChordOMS that represents the user's referral code. |
| Shipping Address Address1 | The street address of the customer. |
| Shipping Address Address2 | The optional second address of the customer. |
| Shipping Address Alternative Phone | The customer's alternative phone number. |
| Shipping Address City | The city where the address is. |
| Shipping Address Company | A company name. |
| Shipping Address Country Abbr | no description |
| Shipping Address Country Name | Full name of the country. |
| Shipping Address Firstname | First name of the customer. |
| Shipping Address Id | Unique key generated by Chord to identify a unique address. |
| Shipping Address Lastname | Last name of the customer. |
| Shipping Address Oms Address Id | Unique key generated by ChordOMS that identifies an address. |
| Shipping Address Phone | The customer's phone number. |
| Shipping Address State Abbr | no description |
| Shipping Address State Name | Full name of the state. |
| Shipping Address Zipcode | The postal code. |
| Subscription Completed Oms Order Ids | List of completed OMS order ids by a subscription. |
| Subscription Completed Order Count | Total amount of orders completed by a subscription. |
| Subscription Completed Order Ids | List of completed order ids by a subscription. |
| Subscription First Order Unique Product Basket | Array of unique product names ordered in the first order per subscription. |
| Subscription First Order Unique Variant Basket | Array of unique SKUs ordered in the first order per subscription. |
| Subscription Has Subscription Tags | Whether or not the subscription has tags. |
| Subscription Id | Unique key generated by ChordOMS that identifies a subscription. |
| Subscription Interval In Days | The number of days in the subscription interval. |
| Subscription Is Auto Redeemed | Whether the pre-paid subscription will be auto-redeemed or if an action is required by the recepient. |
| Subscription Is Gift | Whether or not the pre-paid subscription is a gift. |
| Subscription Is Recurring | Whether the pre-paid subscription is recurring. |
| Subscription Last Order Unique Product Basket | Array of unique product names ordered in the latest order per subscription. |
| Subscription Last Order Unique Variant Basket | Array of unique SKUs ordered in the latest order per subscription. |
| Subscription Oms Pre Paid Subscription Id | ID generated by ChordOMS to identify a unique pre-paid subscription. |
| Subscription Oms Subscription Id | Unique key generated by ChordOMS that identifies a subscription. |
| Subscription Pre Paid Subscription Id | Chord generated unique id for the pre-pay subscription. |
| Subscription State | The current state of the subscription, enhanced with values for \`paused\` if the subscription is active and paused. |
| Subscription Tags | The list of tags associated with a subscription. |
| Subscription Tags Count | The number of tags associated with a subscription. |
| Subscription Unique Product Basket | Array of unique product names ever ordered per subscription. |
| Subscription Unique Variant Basket | Array of unique SKUs ever ordered per subscription. |
| User Completed Oms Order Ids | List of completed OMS order ids by a user. |
| User Completed Order Ids | List of completed order ids by a user. |
| User Credit Category Basket | Array of credit categories (Gift Card, Reimbursement, Referral Credits, Prepaid Subscription, GMA) issued per user. |
| User Email | Email address of the user. |
| User First Completed Oms Order Id | OMS order id of the first order completed by a user. |
| User First Completed Order Id | Unique order id of the first order completed by a user. |
| User First Order Unique Ordered Products | Unique products ordered by the user in their first completed order. |
| User First Order Unique Ordered Skus | Unique SKUs ordered by the user in their first completed order. |
| User Has Ordered A La Carte | Whether or not the user has had at least one order that is not part of a subscription. |
| User Has Promo Applied In First Order | Whether or not the user has a promo applied to their first completed order. |
| User Has Subscription In First Order | Whether or not the user's first order is linked to a subscription. |
| User Id | Unique key generated by Chord to identify a unique user. |
| User Is Active Subscriber | Whether or not the user has an active subscription with at least one completed subscription order. An active subscription is one that is not cancelled or paused. |
| User Is Customer | Whether or not the user is a customer. |
| User Is New Customer | Whether or not the user is a new customer. |
| User Is Not Customer | Whether or not the user is not a customer. |
| User Is Returning Customer | Whether or not the user is a returning customer. |
| User Is Subscriber | Whether or not the user has completed at least one subscription order. |
| User Login | The login email address of the user. |
| User Name | Full name of the user. |
| User Number Of Completed A La Carte Orders | Total amount of orders completed by a user that are a la carte. |
| User Number Of Completed Subscription Orders | Total amount of orders completed by a user that was part of a subscription. |
| User Number Of Orders With Promos | The count of completed orders with a promo applied. |
| User Number Of Subscriptions | Total amount of subscriptions linked to a user. |
| User Oms User Id | Unique key generated by ChordOMS that identifies a user. |
| User Phone | Phone number of the user. |
| User Total Completed Order Count | Total amount of orders completed by a user. |
| User Unique Ordered Products | Unique products ordered by the user across all orders. |
| User Unique Ordered Skus | Unique SKUs ordered by the user across all orders. |
| Billing Address Created At (Universal) | Timestamp at which the address row was created - Universal Time Zone. |
| Billing Address Updated At (Universal) | Timestamp at which the address row was last updated - Universal Time Zone. |
| Order Approved At (Universal) | Reflects when the entity was approved in ChordOMS - Universal Time Zone. |
| Order Canceled At (Universal) | Reflects when the order was cancelled - Universal Time Zone. |
| Order Completed At (Central) | Reflects when the entity was moved to the 'completed' state - Cental Time Zone. |
| Order Completed At (Eastern) | Reflects when the entity was moved to the 'completed' state - Eastern Time Zone. |
| Order Completed At (Mountain) | Reflects when the entity was moved to the 'completed' state - Mountain Time Zone. |
| Order Completed At (Pacific) | Reflects when the entity was moved to the 'completed' state - Pacific Time Zone. |
| Order Completed At (Universal) | Reflects when the entity was moved to the 'completed' state - Universal Time Zone. |
| Order Created At (Central) | Reflects when the entity was first created in ChordOMS - Cental Time Zone. |
| Order Created At (Eastern) | Reflects when the entity was first created in ChordOMS - Eastern Time Zone. |
| Order Created At (Mountain) | Reflects when the entity was first created in ChordOMS - Mountain Time Zone. |
| Order Created At (Pacific) | Reflects when the entity was first created in ChordOMS - Pacific Time Zone. |
| **Order Created At (Universal)** | Timestamp at which the first shipment for that order was shipped - Universal Time Zone. |
| Order First Fulfillment Fulfilled At (Universal) | Timestamp of the last return adjustment for an order - Universal Time Zone. |
| Order First Fulfillment Fulfilled At (Universal)
Order Last Adjustment Refund At (Universal) | Timestamp of the last replacement adjustment for an order - Universal Time Zone. |
| Order Last Fulfillment Fulfilled At (Universal) | Timestamp at which the last shipment for that order was shipped - Universal Time Zone. |
| Order Updated At (Universal) | Reflects when the entity was last updated in ChordOMS - Universal Time Zone. |
| Referral Converted At (Universal) | Reflects when the referral entity was first converted in ChordOMS - Universal Time Zone. |
| Referral Created At (Universal) | Reflects when the entity was first created in ChordOMS - Universal Time Zone. |
| Referral Updated At (Universal) | Reflects when the entity was last updated in ChordOMS - Universal Time Zone. |
| Referrer Created At (Universal) | Reflects when the entity was first created in ChordOMS - Universal Time Zone. |
| Referrer Updated At (Universal) | Reflects when the entity was last updated in ChordOMS - Universal Time Zone. |
| Shipping Address Created At (Universal) | Timestamp at which the address row was created - Universal Time Zone. |
| Shipping Address Updated At (Universal) | Timestamp at which the address row was last updated - Universal Time Zone. |
| Subscription Actionable Date (Universal) | The date of the next subscription installment. This date is updated after each successful installment. Subscriptions in an inactive state will be null - Universal Time Zone. |
| Subscription Created At (Universal) | Reflects when the entity was first created in ChordOMS - Universal Time Zone. |
| Subscription First Order Completed At (Universal) | The timestamp of the subscription's first completed order - Universal Time Zone. |
| Subscription Last Order Completed At (Universal) | The timestamp of the subscription's last completed order - Universal Time Zone. |
| Subscription Updated At (Universal) | Reflects when the entity was last updated in ChordOMS - Universal Time Zone. |
| User Created At (Universal) | Timestamp at which the users row was created - Universal Time Zone. |
| User Date Of Birth (Universal) | Date of birth of the user - Universal Time Zone.Date of birth of the user - Universal Time Zone. |
| User Deleted At (Universal) | Timestamp at which the user's account was deleted - Universal Time Zone. |
| User First Order Completed At (Universal) | The timestamp of the user's first completed order - Universal Time Zone. |
| User First Subscription Order Completed At (Universal) | The timestamp of the user's first completed subscription order, regardless of subsequent subscriptions - Universal Time Zone. |
| User Last Order Completed At (Universal) | The timestamp of the user's last completed order - Universal Time Zone. |
| User Last Sign In At (Universal) | The last sign in timestamp for the user - Universal Time Zone. |
| User Updated At (Universal) | Timestamp at which the users row was last updated - Universal Time Zone. |
| Average Additional Tax Total | Total additional taxes for an order. |
| Average Adjustment Fulfillment Tax Total | Total adjustment shipment taxes for an order. |
| Average Adjustment Fulfillment Total | Total shipment adjustments applied to an order. |
| Average Adjustment Other Charges Total | Total of included additional adjustment charges paid for an order. |
| Average Adjustment Other Credits Total | Total of credits issued for an order. |
| Average Adjustment Refund Total | Total of return dollars for an order. |
| Average Adjustment Replacement Total | Total of replacement dollars for an order. |
| Average Adjustment Rma Refund Total | Total of refund dollards associated to an order that was returned via the RMA functionality of the Chord OMS. |
| Average Adjustment Tax Total | Total adjustment taxes an order. |
| Average Adjustment Total | Total of adjustment applied for an order as on the order. |
| Average Applied Gift Card Total | Total of gift card dollars that were used as a payment method in the order |
| Average Commission Total | Commission for an order. |
| Average Fulfillment Total | Total shipment for an order. |
| Average Gross Revenue | Gross amount of revenue generated by the order including items and shipments totals. Gross revenue = total - included\_tax\_total + shipment\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Average Included Tax Total | Total included taxes for an order. |
| Average Item Total | Total price for the order before adjustments. |
| Average Net Revenue | Net revenue generated by the order's items after promotions. Net revenue = total - included\_tax\_total + shipment\_total + adjustment\_total - additional\_tax\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Average Pre Paid Purchase Total | |
| Average Pre Paid Redemption Total | |
| Average Promo Total | Promotions applied to an order. |
| Average Purchased Gift Card Total | Total of gift card dollars that were purchased in the order. |
| Average Reimbursement Credit Total | The amount of store credits owed back in an order |
| Average Tax Total | Total taxes for an order. |
| Average Total Price | Total to be paid by the customer for an order. |
| Average Transaction Total | Total paid by the customer for a completed order. |
| Additional Tax Total | Total additional taxes for an order. |
| Adjustment Fulfillment Tax Total | Total adjustment shipment taxes for an order. |
| Adjustment Fulfillment Total | Total shipment adjustments applied to an order. |
| Adjustment Other Charges Total | Total of included additional adjustment charges paid for an order. |
| Adjustment Other Credits Total | Total of credits issued for an order. |
| Adjustment Refund Total | Total of return dollars for an order. |
| Adjustment Replacement Total | Total of replacement dollars for an order. |
| Adjustment Rma Refund Total | Total of refund dollards associated to an order that was returned via the RMA functionality of the Chord OMS. |
| Adjustment Tax Total | Total adjustment taxes an order. |
| Adjustment Total | Total of adjustment applied for an order as on the order. |
| Applied Gift Card Total | Total of gift card dollars that were used as a payment method in the order |
| Commission Total | Commission for an order. |
| Fulfillment Total | Total shipment for an order. |
| Gross Revenue | Gross amount of revenue generated by the order including items and shipments totals. Gross revenue = total - included\_tax\_total + shipment\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Included Tax Total | Total included taxes for an order. |
| Item Total | Total price for the order before adjustments. |
| Net Revenue | Net revenue generated by the order's items after promotions. Net revenue = total - included\_tax\_total + shipment\_total + adjustment\_total - additional\_tax\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Pre Paid Purchase Total | |
| Pre Paid Redemption Total | |
| Total Price | Total to be paid by the customer for an order. |
| Promo Total | Promotions applied to an order. |
| Purchased GiftCard Total | Total of gift card dollars that were purchased in the order. |
| Reimbursement Credit Total | The amount of store credits owed back in an order |
| Tax Total | Total taxes for an order. |
| Transaction Total | Total paid by the customer for a completed order. |
### **order\_discount\_names**
| Name | Description |
| ---------------------------- | -------------------------------------- |
| Order Applied Discount Names | Discount name(s) applied to the order. |
### **order\_tags**
| Name | Description |
| ---------- | ---------------------------------- |
| Order Tags | Order tag(s) applied to the order. |
[title] Messaging Events Data Modeling
[path] Chord Data Platform/Data Sources/Messaging Module/
:::hint{type="info"}
**This feature is currently in Beta. For access to this, please reach out to **[help@chord.co](mailto\:help@chord.co)**! **
:::
# Overview
This guide explains how Chord models messaging engagement data from Klaviyo and Iterable to support campaign analysis, audience segmentation, and activation. We highlight the most important attributes, event types, and how we enhance Klaviyo’s and Iterable’s native data with structure and long-term storage for smarter use across your customer journeys.
Both platforms are unified into a single set of models: the same Explores, the same attribution logic, the same metrics. Differences between platforms are called out where relevant.
:::hint{type="info"}
**Who this is for:** Marketing and CRM teams using Klaviyo to power messaging campaigns and segmentation.
:::
# Core event attributes
Each Klaviyo event modeled in Chord includes the following key attributes:
- **Event Date:** When the action occurred—such as an email being opened, a message clicked, or an order placed.
- **Session:** Sessions help organize activity. A session starts when a user engages with a qualifying event (e.g., opens an email). We use this to model session-based metrics like order attribution or conversion analysis.
- **Touch Type:** Identifies the origin of the message:
| **Touch Type** | **Klaviyo** | **Iterable** |
| --------------- | ------------------------------------ | ------------------------------------- |
| Campaign | One-time sends | One-time sends (blast, triggered) |
| Flow / Workflow | Automated flow messages | Automated workflow messages |
| NULL | External apps or non-Klaviyo sources | Events without a campaign or workflow |
# Measures & metrics
We model multiple types of performance measures to support analysis:
- **Event Counts:** Total number of times an event occurred—e.g., how many emails were opened or links clicked.
- **Unique Events:** First-time actions for a user within a given campaign or flow. For example:
- **Unique Opened Emails** – used to start sessions
- **Unique Click Rate** – calculated as unique clicks divided by unique opens
- This is especially useful for building performance funnels across flows or campaign types.
- **Revenue Attribution:** For events like Placed Order (Klaviyo) or Purchase (Iterable), we capture revenue-related fields and associate them with the triggering session. This allows for clear connection between engagement and revenue outcomes.
- **Supported channels by platform:**
| **Channel** | **Klaviyo** | **Iterable** |
| ----------- | ----------- | ------------ |
| Email | Yes | Yes |
| SMS | Yes | No |
| Push | Yes | Yes |
# Attribution & session modeling
Chord’s **Messaging Explore **supports deeper insights with structured attribution windows and session rules.Both Klaviyo and Iterable use the same session-based last-touch attribution logic:
## **Attribution lookback windows**
| **Channel** | **Lookback Period** | **Platforms** |
| ----------- | ------------------- | ----------------- |
| Email | 120 hours (5 days) | Klaviyo, Iterable |
| Push | 120 hours (5 days) | Klaviyo, Iterable |
| SMS | 24 hours | Klaviyo only |
## **Session-defining events**
A new session begins when a user engages with one of these events:
| **Klaviyo** | **Iterable** |
| ------------- | ------------ |
| Opened Email | Email Open |
| Clicked Email | Email Click |
| Clicked SMS | (no SMS) |
| Opened Push | Push Send |
### Campaign enrichment
| **Field** | **Klaviyo** | **Iterable** |
| ----------------- | --------------------------------------------- | ------------------------- |
| Campaign Name | Yes | Yes |
| Campaign Status | Yes | Yes |
| UTM Parameters | Yes (source, medium, campaign, term, content) | No |
| Message Medium | No | Yes (email, push) |
| Campaign Type | No | Yes (blast, triggered) |
| Template Name | No | Yes |
| Channel Name | No | Yes |
| Message Type | No | Yes |
| Target Lists | No | Yes (list names resolved) |
| Suppression Lists | No | Yes (list names resolved) |
| Workflow ID | No | Yes |
| Send Size | No | Yes |
When the optional Campaign Mapping transform is enabled, both platforms are enriched with standardized campaign classification fields (region, brand, objective, category, etc.).
# Where to find this data on Chord
Once your messaging events are ingested by Chord, you will be able to further analyze your messaging data on Chord. Follow the steps below to dig into your data:
1. Log into the Chord Commerce data platform.
2. Navigate to **Explores** tab on the **Analytics** page.
3. Click on the **Explores** dropdown on the left side of the page.
4. Select one of the following options based on what you’d like to analyze:
1. **Messaging Events**: Use this Explore to create session funnels and analyze campaign or flow performance.
2. **Messaging Lists**: Use this Explore to dive into active subscriber counts.
3. **Messaging Segments:** Use this Explore to analyze behavior-based targeting in campaigns.
# Filtering & interpretation tips
:::hint{type="info"}
**Note:** Klaviyo campaigns don’t include a field that explicitly identifies the channel (e.g., Email vs. SMS). Campaigns rarely mix channels, so we recommend using event types and channel-specific metrics for precision.
:::
- Use `source_platform` to filter for a specific platform or compare across platforms.
- Use **campaign names** to filter for one-time sends. If the campaign name is blank, the event likely came from a **flow (Klaviyo) or workflow (Iterable).**
- You can use **Touch Type** to distinguish flows/workflows from campaigns and external sources.
- Clicks and delivery outcomes are **modeled separately by channel**:
- Email and SMS clicks are tracked independently.
- Rates like **click-through** or **bounce** are also channel-specific.
- Push messaging metrics include bounce, send, and open.
# Active subscriber modeling (***Klaviyo only***)
Chord enhances Klaviyo's list data by adding historical depth:
- **List Membership:** Klaviyo allows you to select lists when building a campaign, but doesn’t retain list membership counts over time.
- **Chord Enhancement:** We snapshot **profile counts** per list at regular intervals so you can:
- Track how many people were eligible for a campaign at send time; and
- Understand historic list size and growth trends.
:::hint{type="info"}
**Analysis not yet available: **Identifying which users were members of specific lists for downstream activation.
:::
[title] Activities
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Chord OMS/
### *x\_fct\_trans\_activities*
| Name | Definition |
| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Activity Event Text | The name of the event. |
| Activity Event Text Id | The slug of the event name, mapping to the page or track event table. |
| Activity Id | The unique identifier of an activities (i.e. Track or Page event). |
| Activity Page Path | The page path part of the URL. A page path is the part of URL that comes after the hostname (domain) and before the query parameters, URL fragment, or port. (e.g. `/pages/contact-us/` for `https://chord.co/pages/contact-us/?ref=internal-banner`.) |
| Activity Page Query | The query string portion of the URL of the page. |
| Activity Page Title | The title/name of the page. |
| Activity Page Url | The URL of the page. |
| Activity Session Activity Count | Total count of activities, pave views and tracked events within the session. |
| Activity Session Attribution Channel | The attribution channel for the first page event of the session. Sessions with an attribution of 'Unknown' indicates that there is no attributable data for that session. |
| Activity Session Attribution Channel Paid Or Organic | Indicates if the session's first page attribution is paid or organic. Attribution is considered Organic if the attribution channel is 'Direct', 'Other', 'Organic Search', 'Organic Social', 'Email', or 'SMS'. |
| Activity Session Attribution First Page Url Has Gclid | Indicates if the first page event of the session has a Google Click ID. |
| Activity Session Attribution First Page Url Has Utm | Indicates if the first page event of the session has any utm information. |
| Activity Session Attribution Has Referrer | Indicates if the first page event of the session has a referrer host. |
| Activity Session Attribution Medium | The campaign medium represented by the UTM tags for the first page event of the session. |
| Activity Session Attribution Source | The campaign source represented by the UTM tags for the first page event of the session. |
| Activity Session Attribution Sub Channel | Sub-Channel is a granular level of attribution. |
| Activity Session Completed Oms Order Ids | Array of OMS Order IDs associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Activity Session Completed Order Ids | Array of order IDs associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Activity Session Completed Order Numbers | Array of order numbers associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Activity Session Days Since Last Session End | The days between the last session's end and the start of this session. |
| Activity Session Device | The device on which the event was sent from. |
| Activity Session Device Category | The device category of the device on which the event was sent from. There are multiple supported values for this column such as iPhone', |
| Activity Session Duration In Seconds | Total seconds between start and end activities within the session. |
| Activity Session Duration In Seconds Tiers | Total seconds between start and end activities within the session, aggregated into tiers: 0-9s, 10-29s, 30-59s, and 60s or more. |
| Activity Session Has Order Completion | Flag for sessions with an order completed or checkout completed front-end events |
| Activity Session Id | Unique ID for the session. |
| Activity Session Number | Session number per anonymous id. |
| Activity Session Unique Completed Order Count | Count of unique order ids associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Activity Session Unique Completed Order Number Count | Count of unique order numbers associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Activity Utm Campaign | The campaign name represented by the UTM tags. |
| Activity Utm Content | The campaign content represented by the UTM tags. |
| Activity Utm Medium | The campaign medium represented by the UTM tags. |
| Activity Utm Source | The campaign source represented by the UTM tags. |
| Activity Utm Term | The campaign term represented by the UTM tags. |
| Activity Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store |
| Anonymous Completed Oms Order Ids | Array of OMS Order IDs associated to the anonymous\_id, as collected by order completed or checkout completed front-end events, over time. |
| Anonymous Completed Order Ids | Array of order IDs associated to the anonymous\_id, as collected by order completed or checkout completed front-end events, over time. |
| Anonymous Completed Order Numbers | Array of order numbers associated to the anonymous\_id, as collected by order completed or checkout completed front-end events, over time. |
| Anonymous Current Blended User Id | Unique id derived from the user\_id and the anonymous\_id. Whenever a customer has a user\_id, the user\_anonymous\_id will be constant for |
| Anonymous Current User Id | The current user\_id associated with the anonymous\_id. This unique user\_id is created by Segment's Identify call. A user\_id can be associated to many anonymous\_ids. |
| Anonymous Id | Unique id created by Chord for each anonymous visitor per store. |
| Anonymous Segment Anonymous Id | Id created by Segment for each anonymous visitor. This id gets created as soon as a customer's browser loads the analytics javascript widget. The anonymous\_id remains unchanged through the entire browsing session from a single device. Depending on configuration, two stores connected stores may have the same anonymous\_id. |
| Anonymous Unique User Ids | Array of user IDs mapped to an anonymous ID. |
| Date Day Num Of Year | The number representing the day of the year. |
| Date Id | Unique key that uniquify a date. |
| Date Month Num Of Year | The month number of the year. |
| Last Seen Page Browser Locale | Locale of browser. |
| Last Seen Page Device | The device on which the event was sent from. |
| Last Seen Page Device Category | The device category of the device on which the event was sent from. There are multiple supported values for this column such as 'iPhone', |
| Last Seen Page Event Table Name | The properly formatted name of the table of the event. |
| Last Seen Page Event Text | The name of the event. |
| Last Seen Page Event Text Id | The slug of the event name, mapping to the page or track event table. |
| Last Seen Page Gclid | The Google Click ID. Google Click ID (GCLID) is a parameter passed in the URL with ad clicks, to identify the campaign and other attributes of the click associated with the ad for ad tracking and campaign attribution. |
| Last Seen Page Id | Unique key generated by Segment for each tracking or page event. |
| Last Seen Page Oms Id | Unique key generated by our models that uniquifies an OMS. |
| Last Seen Page Host | The host of the event's URL. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev`. This facilitates grouping events by host. |
| Last Seen Page Path | The page path part of the URL. A page path is the part of URL that comes after the hostname (domain) and before the query parameters, URL fragment, or port. (e.g. `/pages/contact-us/` for `https://chord.co/pages/contact-us/?ref=internal-banner`.) |
| Last Seen Page Query | The query string portion of the URL of the page. |
| Last Seen Page Referrer | The referrer of the page. The referrer is the webpage that sends visitors to the site using a link. In |
| Last Seen Page Title | The title/name of the page. |
| Last Seen Page Url | The URL of the page. |
| Last Seen Page Referrer Host | The host of the referrer. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev`. This facilitates grouping events by host. |
| Last Seen Page Segment User Id | The unique ID of the user. |
| Last Seen Page Store Id | Unique key generated by our models that uniquifies a store. |
| Last Seen Page Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Last Seen Page User Agent | The User agent of the device making the request. A User agent request header is a characteristic string that lets servers and |
| Last Seen Page User Id | Unique key generated by Chord to identify the user. |
| Last Seen Page Utm Campaign | The campaign name represented by the UTM tags. |
| Last Seen Page Utm Content | The campaign content represented by the UTM tags. |
| Last Seen Page Utm Medium | The campaign medium represented by the UTM tags. |
| Last Seen Page Utm Source | The campaign source represented by the UTM tags. |
| Last Seen Page Utm Term | The campaign term represented by the UTM tags. |
| Last Seen Page Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store |
| Session Landing Page Browser Locale | Locale of browser. |
| Session Landing Page Device | The device on which the event was sent from. |
| Session Landing Page Device Category | The device category of the device on which the event was sent from. There are multiple supported values for this column such as iPhone , |
| Session Landing Page Event Table Name | The properly formatted name of the table of the event. |
| Session Landing Page Event Text | The name of the event. |
| Session Landing Page Event Text Id | The slug of the event name, mapping to the page or track event table. |
| Session Landing Page Gclid | The Google Click ID. Google Click ID (GCLID) is a parameter passed in the URL with ad clicks, to identify the campaign and other attributes of the click associated with the ad for ad tracking and campaign attribution. |
| Session Landing Page Id | Unique key generated by Segment for each tracking or page event. |
| Session Landing Page Oms Id | Unique key generated by our models that uniquifies an OMS. |
| Session Landing Page Host | The host of the event's URL. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev`. This facilitates grouping events by host. |
| Session Landing Page Path | The page path part of the URL. A page path is the part of URL that comes after the hostname (domain) and before the query parameters, URL fragment, or port. (e.g. `/pages/contact-us/` for `https://chord.co/pages/contact-us/?ref=internal-banner`.) |
| Session Landing Page Query | The query string portion of the URL of the page. |
| Session Landing Page Referrer | The referrer of the page. The referrer is the webpage that sends visitors to the site using a link. In |
| Session Landing Page Title | The title/name of the page. |
| Session Landing Page Url | The URL of the page. |
| Session Landing Page Referrer Host | The host of the referrer. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev`. This facilitates grouping events by host. |
| Session Landing Page Segment User Id | The unique ID of the user. |
| Session Landing Page Store Id | Unique key generated by our models that uniquifies a store. |
| Session Landing Page Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Session Landing Page User Agent | The User agent of the device making the request. A User agent request header is a characteristic string that lets servers and |
| Session Landing Page User Id | Unique key generated by Chord to identify the user. |
| Session Landing Page Utm Campaign | The campaign name represented by the UTM tags. |
| Session Landing Page Utm Content | The campaign content represented by the UTM tags. |
| Session Landing Page Utm Medium | The campaign medium represented by the UTM tags. |
| Session Landing Page Utm Source | The campaign source represented by the UTM tags. |
| Session Landing Page Utm Term | The campaign term represented by the UTM tags. |
| Session Landing Page Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store |
| Store Id | Unique key generated by our models that uniquifies a store. |
| Store Name | The name of the store. |
| Store Oms Admin Url | The Admin URL of that OMS. |
| Store Oms Id | Unique key generated by Chord that uniquifies an OMS. |
| Store Oms Store Id | Unique key generated by our models that uniquifies a store. |
| Store Oms Type | The type of the OMS. |
| Store Id | Unique key generated by our models that uniquifies a store. |
| Store Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Store Url | The Storefront URL of of the store. |
| User Address 1 | The first line of the street address. |
| User Address 2 | The optional second line of the address. |
| User Address City | The city of the address. |
| User Address Country | The country of the address. |
| User Address Name | The full name of the customer, based on firstName and lastName. |
| User Address State | The region of the address, such as the province, state, or district. |
| User Address Zip | The postal code of the address. |
| User Completed Oms Order Ids | Array of OMS Order IDs associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| User Completed Order Ids | Array of order IDs associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| User Completed Order Numbers | Array of order numbers associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| User Email | The email associated with the user. |
| User Id | Unique ID per user. It is equal to either 1) a identified\_user\_id as identified by Segment in the Identify call, or 2) an anonynous\_id. |
| User Identified User Id | Unique ID per identified user. (See Segment's documentation on user\_id) `https://segment.com/docs/connections/spec/identify/#user-id` . |
| User Ip | IP address associated with the user. |
| User Last Anonymous Id | Last seen anonymous\_id per user. An anonymous\_id is a unique ID per anonymous visitor. (See Segment's documentation on anonymous\_id) `https://segment.com/docs/connections/spec/identify/#anonymous-id]`. |
| User Last Segment Anonymous Id | This column is not documented. |
| User Segment User Id | The unique ID of the user. |
| User Unique Anonymous Ids | Array of all seen anonymous\_ids per user. An anonymous\_id is a unique ID per anonymous visitor. (See Segment's documentation on anonymous\_id) \` `https://segment.com/docs/connections/spec/identify/#anonymous-id`. |
| User Unique Completed Order Count | Count of unique order ids associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
[title] Chord Reveal (Private Beta)
[path] Chord Data Platform/
## What is Chord Reveal?
**Chord Reveal** helps brands connect the dots between anonymous sessions and real customer identities—unlocking previously hidden insights across acquisition, retention, and conversion. By leveraging persistent, privacy-compliant cookies, we match site visitors to enriched profiles using verified third-party data sources.
The result? Smarter segmentation, better personalization, and stronger ROI across your marketing stack. Unlock new value from anonymous traffic by using our data enricher gives you the context you need.
:::hint{type="info"}
**Chord Reveal is currently available only for users located in the United States.** Visitors accessing your site from outside the U.S. cannot be identified through Chord Reveal.
:::
## Why it matters
Every e-commerce brand sees a large portion of traffic come from anonymous users—people who browse, click, and even add to cart without ever logging in or checking out. Until now, that activity has lived in the dark.
With **Chord Reveal**, you can:
- Identify and connect anonymous sessions to known users.
- Power smarter retargeting and journey orchestration.
- Improve campaign attribution and funnel visibility.
- Enrich your CDP with more complete customer profiles.
## How it works
Chord Reveal uses a blend of behavioral patterning, first-party identifiers (like email captures), and event-level stitching to match sessions across devices and visits—without relying on third-party cookies.
:::hint{type="info"}
Note that de-anonymized user data will not be merged with existing user profiles; this data is merely displaying additional fields based on the same anonymous ID.
:::
When a match is made, Chord automatically updates user records and exposes those enriched identities in existing Explores. If you are a beta user of Chord Reveal, you will be able to leverage a new group label named “Chord Reveal” across the **Activities and Sessions Explores** on the Chord platform.
Additional technical details follow below:
1. **Anonymous User **`Page View`: As with standard user identification, an anonymous user triggers an initial Page View. If this user cannot be mapped to a known `User_ID`, we query our proprietary identity graph built from licensed third party providers to see if this user is identified.
2. **Identity Resolution & Enrichment Match: **If the user is found within the identity graph, we use high-confidence probabilistic scoring and return a structured enrichment object, which includes:
- Email (V1)
- Name (V1)
3. **Data Structure: **Enriched profile data is returned via unique data table separated from first-party customer tables.
4. **Privacy & Compliance: **All data processing adheres to U.S. regulatory frameworks. Consent preferences are honored, and opt-outs are immediately suppressed and removed from data enrichment workflows.
Here is a sample flow of how Chord Reveal works:
1. A visitor anonymously navigates to a page on your website (this individual is Anonymous).
2. If the visitor eventually logs in to their account on your site, they become Self-Identified (no longer Anonymous).
3. If the visitor doesn't log in and Chord identifies them, the visitor becomes Chord Identified (no longer Anonymous).
4. If the visitor logs in after being Chord Identified, then the visitor becomes Self-Identified.
## Getting started with Chord Reveal
### What you’ll need
- Chord CDP access
- Consent collection (via your site or email capture)
- Active web tracking (event capture)
### Setup steps
1. Request access to the private beta
2. Verify event coverage
3. Access and monitor matches via Activities and Sessions Explores
## What to expect
Once Chord Reveal is enabled, you’ll begin to see:
- More users attributed to known IDs
- Enriched session and conversion metrics
- Greater reach in segmentation and re-marketing audiences
## Privacy & consent
Chord Reveal respects privacy by only resolving identity when consented, first-party data is available. All identity resolution is done using hashed identifiers and never relies on third-party cookies or cross-site tracking.
## Questions?
Reach out to [product@chord.co](mailto\:product@chord.co) to request early access to the private beta.
[title] Connect Data Sources
[path] Chord Data Platform/Data Sources/
# What is a data source connector?
Connectors are pre-built interfaces that allow the platform to connect to and retrieve data from various sources such as databases, SaaS applications, and other data repositories. These connectors handle the specific intricacies of interacting with each source system, ensuring a smooth and standardized process for data extraction.
In summary, a connector acts as a bridge between different data systems, ensuring seamless data flow and integration between them.
# List of supported connectors
## Connectors modeled in the data platform:
- **Amazon Selling Partner: **A connection to Amazon that lets sellers and vendors securely pull business data—like orders, inventory, finances, and reports—into their own systems or tools for automation and analytics. ***This data source is currently only available for Shopify OMS brands. ***
- **Chord OMS:** PostgreSQL, a relational database management system for storing and managing structured data.
- **Facebook Ads:** An advertising platform on Facebook for targeted ad campaigns.
- [Fairing](docId\:VfeXgta8VSYPvshybVSzb)**: **A post-purchase survey and customer feedback platform that helps eCommerce brands understand where customers came from and why they converted.
- **Google Ads:** Google's online advertising platform for displaying ads on search results and its advertising network.
- [Iterable](docId\:jLKFa2NEjOCp_t1KecBxI)**:** A cross-channel marketing platform for personalized customer engagement campaigns.
- [Klaviyo](docId:8uDT50KmZR0jRe1kbLfNX)**:** A marketing automation platform specializing in email marketing.
- **Pinterest Ads:** Advertising on Pinterest, a platform for showcasing and promoting products through paid ads.
- **Reddit Ads:** Advertising on Reddit, a platform for reaching specific communities with targeted ads.
- [Recharge](docId\:QgBXiJQDJYVHD9DlXV4F9)**:** An e-commerce platform focused on subscription billing.
- **Shopify:** An e-commerce platform for creating and managing online stores. Chord supports multiple Shopify sources, allowing users to connect more than one Shopify store to the platform.
- [Stay AI](docId\:L9w1Wy-03OyNYHkZJgmep)**: **A Shopify-focused subscription platform that helps eCommerce brands grow recurring revenue through subscriber retention, churn reduction, and customer lifecycle optimization.
- **TikTok Ads:** An advertising platform on TikTok for creating and promoting ads.
- **YouTube Ads:** YouTube's online advertising platform for displaying ads on search results and its advertising network.
## Connectors with data modeling coming soon:
- **Braze:** A customer engagement platform for personalized messaging experiences.
- **Ordergroove: **A subscription commerce platform that helps brands grow recurring revenue through memberships, auto-replenishment, and subscriber retention.
- **Gorgias:** A customer support and helpdesk platform purpose-built for ecommerce brands, unifying email, chat, social, and SMS conversations.
- **Okendo:** A reviews, ratings, and user-generated content platform for ecommerce brands.
- [NetSuite](docId\:uYozU5tQPSa2Tt9aOqnoS)**:** A cloud ERP platform that helps businesses manage finance, inventory, orders, and operations in one unified system.
- **Shopware: **An open commerce platform that helps brands and retailers build flexible B2C and B2B online stores with SaaS, PaaS, or self-hosted deployment options.
- **Zendesk:** A customer service and support platform for managing customer interactions and support tickets.
# Request access to Data Sources
You will see this page if your store does not have full access to Data Sources:
You can easily request access to add your data sources by clicking on the **"Request Access"** button on this page.
Once someone submits an access request on behalf of your organization, it will stay in the access queue until it is completed by Chord’s Support Team. In other words, there is no need to submit multiple requests for access - we will log only one access request per organization.
:::hint{type="info"}
If the Data Sources page is not present or disabled, please reach out to us at [help@chord.co](https://www.notion.so/DRAFT-Data-Source-Ingestor-KB-Doc-1e343ced87a28062baaffef02b83b6be?pvs=21).
:::
# Connector setup
:::hint{type="info"}
Users with the following roles on the Chord platform will have the ability to add and edit data source connectors: **Team Admin, Data Analyst (Chord OMS only), Developer.**
:::
Once your store has access to Data Sources, you’re now ready to add your data source connectors. Follow the instructions below to add your data sources:
1. Log into the Chord Commerce data platform.
2. Navigate to the Data Sources page.
3. Click the **Add Source** button to view our data source connector catalog.
4. From the data source connector catalog, select the data source you want to connect.
5. Follow the instructions on your screen to add your desired connector. ***Note: Chord supports more than one data ingestion method on the platform. Depending on the data source you attempt to connect, you will be guided through different steps to add your connector.***
6. Once you complete the data source connector setup and provide the API key for the specific connector you chose, you will see your data source saved and displayed on the **Data Sources** homepage.
:::hint{type="info"}
Note: Chord supports multiple shopify sources. To add more than one Shopify store, visit the **Data Sources** page and click the **Add Source **button. Repeat this process for each store you want to connect.
:::
## Request a connector
Is your desired data source missing from our catalog? Submit a connector request via the **“Request”** button at the bottom of the **Add Data Sources** page.
Note that the Chord team will review and evaluate all requests, and that not all data sources will be supported.
# Glossary
- **Source:** Our data source connectors, the sources you have either connected or are in the process of, i.e., TikTok Ads, Klaviyo, or Iterable.
- **Setup:** Status of your connection, either **Connected, Incomplete,** or **Broken:**
- **Connected**: Connection was successful and ready to sync (or synced).
- **Incomplete**: Connection has not been finished and needs completion.
- **Broken**: The connector is experiencing issues due to a problem with either the connector itself or its linked destination.
- **Sync Status:** A sync status indicates the current state of data transfer between two systems, offering insights into progress, success, or encountered issues during synchronization.
- **Scheduled**: The synchronization is set to operate at designated intervals. Automated scheduling and execution occur according to the defined frequency.
- **Paused**: Following successful setup tests, the system logs the "Connection Created" user action. During this phase, the connector is halted, refraining from extracting, processing, or loading any data from the source to the destination.
- **Syncing**: The process of harmonizing data between two systems, ensuring that the information in the destination aligns with the source. During a standard sync, new or updated data from the source is transferred to the destination without overwriting existing information.
- **Last Synced:** Timestamp to store the date and time of the most recent sync.
# FAQs and troubleshooting
**Q: I added a Data Source but in the Setup column I see it is Incomplete.**
A: When a data source setup is marked as 'Incomplete' in the Setup column, it indicates that the configuration process hasn't been completed. To proceed, click back on the data source and finish the setup. Additionally, in such scenarios, the Sync Status is typically shown as 'Pause' until the setup is finalized
**Q: Can I pause my connection?**
A: If you temporarily want to halt data synchronization and consider resuming it later, you can choose to pause your connection. While infrequent, this option is especially utilized in combination with Chord. Occasionally, we have seen customers connect a source (enjoying the first two weeks free), pause it, analyze its utility, and then determine whether to continue using and paying for that source
**Q: What happens if we want to disconnect a Data Source?**
A: You can disconnect a Data Source by clicking the selected specific Source and clicking Disconnect Source. You will be prompted to confirm the disconnection. We do recommend reaching out to [help@chord.co](mailto\:help@chord.co) before you do so to ensure proper data disconnection.
**Q: How often does the Sync happen?**
A: Data sync frequency varies and is dependent on your contract. The Chord team will set the schedule according to your general data sync frequency.
**Q: Is it possible to configure the synchronization process?**
A: If you need to make any modification to a configuration, please reach out to [help@chord.co.](mailto\:help@chord.co)
**Q: What credentials would I need to provide to connect data sources?**
A: To connect a data source, you typically need access credentials for the third party source you intend to connect. For Shopify, this includes a `client id `and `client secret`. For other sources, the specific requirements vary — for precise instructions, refer to the setup guide located on the right side panel, as it provides detailed information tailored to each specific integration.
[title] Time
[path] Chord Data Platform/Data Models/
### Timezones
Chord's default timezone is UTC, the originating timezone of the raw data. Chord provides additional timezone options (Pacific, Mountain, Central, and Eastern) for users to customize analyses to their location preferences.
### Time Options
Chord provides additional time options, including:
- **Time: **The timestamp.
- **Date: **The date of the timestamp.
- **Week:** The seven-day period from Monday through Sunday.
- **Month:** The calendar period of the month.
- **Quarter:** `YYYY-QY` defined as the calendar year and calendar three months of the quarter. For example, January 1 through March 31 of 2024 is `2024-Q1`.
- **Year:** The calendar year.
****
:::hint{type="success"}
if you have any questions or need help, please reach out to us at [help@chord.co](mailto\:help@chord.co)
:::
[title] Subscription Movements Daily Explore
[path] Chord Data Platform/Data Models/Subscriptions/
## Overview
Daily summary of subscription changes + estimated revenue impact.
- Grain: **movement type per day**
## When to use
- Quantify revenue impact
- Monitor operational changes
- Investigate anomalies
## Key dimensions & metrics
| Field | Description |
| --------------------------- | ------------------------- |
| Report Date | Date |
| Movement Type | created, cancelled, etc. |
| Movement Category | status / quantity / price |
| Subscription Count | Distinct subs |
| Customer Count | Distinct customers |
| Event Count | Raw events |
| Revenue Impact Estimate | Estimated impact |
| Avg Order Value Affected | AOV |
| Revenue Impact Is Estimated | Always yes |
| Revenue Impact Method | Calculation logic |
## Example business questions
- Revenue lost from cancellations
- Movement comparison (volume + impact)
- Day-of-week trends
- Reactivation recovery
## Notes & caveats
- Revenue is **estimated**, not contractual
- Subscriptions without orders → NULL impact
## Glossary
| Term | What it Means | How to Interpret / Use | Where You’ll See It in Looker |
| ------------------------ | --------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Active Subscription** | A subscription that is currently ongoing. Includes both fully active and paused subscriptions. | Use this to understand the **current size of your subscriber base**. Note that paused users are still counted. | Subscription Metrics Daily (Active Count), Subscriber Journey (Is Active Subscriber), Subscriber Journey Monthly (Is Active Subscriber EOM), Product & Bundle Explores (Active Subscription Count) |
| **Churn / Churned** | A subscription that has been cancelled. Does not include pauses. | Represents **true customer loss**. Track this to understand retention issues. | Subscription Metrics Daily (Churned Count, Churn Rate), Subscriber Journey (Is Churned, Churn Count), Monthly (Is Churned EOM, Cancellations This Month), Events Enriched (Event Type = canceled), Movements (status\_cancelled) |
| **Winback** | A subscriber who cancelled all subscriptions and later returned by subscribing again. | Indicates **successful re-engagement** after churn. | Subscriber Journey (Is Winback), Subscriber Journey Monthly (Has Reactivated By EOM) |
| **Reactivation** | A previously cancelled subscription that becomes active again (subscription-level). | Measures **recovery of churned subscriptions**. | Subscription Metrics Daily (Reactivated Count), Movements (status\_reactivated), Events Enriched (Event Type = reactivated) |
| **Net New** | Net change in subscriptions: New + Reactivated − Cancelled. | Indicates **overall growth vs decline**. | Subscription Metrics Daily (Net New Count) |
| **LTV (Lifetime Value)** | Total revenue generated by a subscriber across all subscription orders. | Use to understand **customer value over time** and compare cohorts or segments. | Subscriber Journey (LTV Gross / Net Revenue), Subscriber Journey Monthly (LTV Gross Revenue EOM) |
| **EOM (End of Month)** | Metrics calculated as of the last day of a month. | Used for **consistent month-over-month comparisons** (retention, LTV growth). | Subscriber Journey Monthly (all EOM fields like Active EOM, LTV EOM) |
| **Solo Subscription** | A subscription that contains only one product. | Helps identify products that perform well **individually**. | Subscription Product Metrics Daily (Solo Subscription Count) |
| **Bundle** | A subscription that contains two or more products. | Useful for analyzing **product combinations and cross-sell behavior**. | Product Metrics (Bundle Subscription Count), Bundle Metrics Daily (all bundle fields) |
| **Movement** | Any change in a subscription’s state (created, cancelled, paused, resumed, reactivated, quantity/price change). | Use to understand **operational changes and trends** in subscriptions. | Subscription Movements Daily (Movement Type, Category), Events Enriched (Event Type) |
| **Provider** | The system managing subscriptions (Recharge, ChordOMS, CustomOMS). | Important context — **data availability and detail vary by provider**, which affects analysis. | All Explores (Provider filter present everywhere) |
[title] Subscription Bundle Metrics Daily Explore
[path] Chord Data Platform/Data Models/Subscriptions/
## Overview
Bundle-level performance (multi-product subscriptions).
- Grain: **bundle combination per day**
## When to use
- Identify top bundle combinations
- Compare bundle churn rates
- Analyze AOV by bundle
## Key dimensions & metrics
| Field | Description |
| --------------------------- | ------------------ |
| Report Date | Date |
| Bundle Key | Unique combo |
| Product Titles | Included products |
| Product Count | Number of products |
| Is Large Bundle | >4 products |
| Active Subscription Count | Active subs |
| New Subscription Count | New subs |
| Churned Subscription Count | Cancelled subs |
| Bundle Churn Rate | Churn rate |
| Avg Order Value | AOV |
| Bundle Rank by Active Count | Popularity |
## Notes & caveats
- Large bundles (5+) grouped into **LARGE\_BUNDLE**
- Single-product subscriptions excluded
## Glossary
| Term | What it Means | How to Interpret / Use | Where You’ll See It in Looker |
| ------------------------ | --------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Active Subscription** | A subscription that is currently ongoing. Includes both fully active and paused subscriptions. | Use this to understand the **current size of your subscriber base**. Note that paused users are still counted. | Subscription Metrics Daily (Active Count), Subscriber Journey (Is Active Subscriber), Subscriber Journey Monthly (Is Active Subscriber EOM), Product & Bundle Explores (Active Subscription Count) |
| **Churn / Churned** | A subscription that has been cancelled. Does not include pauses. | Represents **true customer loss**. Track this to understand retention issues. | Subscription Metrics Daily (Churned Count, Churn Rate), Subscriber Journey (Is Churned, Churn Count), Monthly (Is Churned EOM, Cancellations This Month), Events Enriched (Event Type = canceled), Movements (status\_cancelled) |
| **Winback** | A subscriber who cancelled all subscriptions and later returned by subscribing again. | Indicates **successful re-engagement** after churn. | Subscriber Journey (Is Winback), Subscriber Journey Monthly (Has Reactivated By EOM) |
| **Reactivation** | A previously cancelled subscription that becomes active again (subscription-level). | Measures **recovery of churned subscriptions**. | Subscription Metrics Daily (Reactivated Count), Movements (status\_reactivated), Events Enriched (Event Type = reactivated) |
| **Net New** | Net change in subscriptions: New + Reactivated − Cancelled. | Indicates **overall growth vs decline**. | Subscription Metrics Daily (Net New Count) |
| **LTV (Lifetime Value)** | Total revenue generated by a subscriber across all subscription orders. | Use to understand **customer value over time** and compare cohorts or segments. | Subscriber Journey (LTV Gross / Net Revenue), Subscriber Journey Monthly (LTV Gross Revenue EOM) |
| **EOM (End of Month)** | Metrics calculated as of the last day of a month. | Used for **consistent month-over-month comparisons** (retention, LTV growth). | Subscriber Journey Monthly (all EOM fields like Active EOM, LTV EOM) |
| **Solo Subscription** | A subscription that contains only one product. | Helps identify products that perform well **individually**. | Subscription Product Metrics Daily (Solo Subscription Count) |
| **Bundle** | A subscription that contains two or more products. | Useful for analyzing **product combinations and cross-sell behavior**. | Product Metrics (Bundle Subscription Count), Bundle Metrics Daily (all bundle fields) |
| **Movement** | Any change in a subscription’s state (created, cancelled, paused, resumed, reactivated, quantity/price change). | Use to understand **operational changes and trends** in subscriptions. | Subscription Movements Daily (Movement Type, Category), Events Enriched (Event Type) |
| **Provider** | The system managing subscriptions (Recharge, ChordOMS, CustomOMS). | Important context — **data availability and detail vary by provider**, which affects analysis. | All Explores (Provider filter present everywhere) |
[title] Chord Platform and Okta SSO Integration
[path] Chord Data Platform/Overview/User Management on the Chord Platform/
Welcome to the Chord Platform SSO integration guide.
This will cover the basic understanding of the integration of Okta and the SSO flow and go through the setup process step by step.
## Architecture Diagram
## User flow
1. The user logs into IdP (e.g. Okta) dashboard and selects the Chord application.
2. Okta servers request that the user authenticate the login.
3. On success, the user is redirected to the data platform.
4. The Chord data platform validates the session information from the IdP and logs the user in.
## Sequence Diagram
# Setup Guide
## Receive the two configuration settings from Chord
1. **ACS URL:** XXXXXXXXX
2. **Audience URI:** XXXXXXXXX
## Create and configure a new Okta Application
1. Log into okta.com and click Create App Integration in the Applications tab:
::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/v3C_R0Fsav1vn7UIjtmo3_image.png" size="100" width="2000" height="1130" position="center" alt="Create Applicaiton" darkWidth="2000" darkHeight="1130" showCaption="false" indent="2"}
2. Select **SAML 2.0**.
3. In the **General Settings** form, enter "Chord Hub".
- If integrating on the Chord data platform's staging instance, append" - Staging" to the name.
- The icon below can be downloaded and uploaded for the Chord application:
::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/sFBtbMIqtHK5aYOe13pwf_chord-icon.png" size="12" width="381" height="200" position="flex-start" alt="Chord logo" darkWidth="381" darkHeight="200" showCaption="false" indent="3"}
4. In the **Configure SAML** form, use these steps for the following fields:
- **Single sign-on URL**: Enter the `acs_url` value from the Chord configuration.
- "Use this for Recipient URL and Destination URL**"** should remain checked.
- "Use this for Recipient URL and Destination URL" should remain checked.
- Audience URI (SP Entity ID): Enter the audience\_uri value from the Chord configuration.
- Default RelayState: This value can remain blank.
- " Name ID format: Select ”EmailAddress".
- "Application username: Select “Email"
- Attribute Statements: Create these two:
- Name: firstName;
Name format: Basic;
Value: user.firstName
- Name: lastName;
Name format: Basic;
Value: user.lastName
::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/qQ_55yVDoJnCHMcBRxqdO_image.png" size="100" width="2000" height="2535" position="center" alt="Configure SAML" darkWidth="2000" darkHeight="2535" showCaption="false" indent="3"}
5. There may be a feedback form on the next step, which can be ignored. Then click "Finish. "
## View and send Chord your SAML setup setup instructions
1\. Click the **View SAML setup instructions** button on the **Sign On** tab of your newly created Okta application:
2\. Send Chord the following values from the setup instructions page:
1. **Identity Provider Single Sign-On URL**
2. **Identity Provider Issuer**
3. **X.509 Certificate** (including the BEGIN\_CERTIFICATE and END\_CERTIFICATE lines)
## Provision access to the Chord Application
On the **Assignments** tab under your application in Okta, assign the application to team members who should have access to it by clicking **Assign**:
## Test SSO integration after confirmation from Chord
The Okta user dashboard should show the Chord Application.
Please test the integration by clicking the application to sign in to Chord.
[title] Chord Reveal Data Attribute Definitions
[path] Chord Data Platform/Untitled/
:::hint{type="info"}
Chord Reveal will appear as a “group label” inside the existing Activities, Sessions, and Anonymous explores.
Note: The data inside the Sessions, Activities, and Anonymous explores will only work when they are associated with data from Chord CDP.
:::
### Chord Reveal profile fields
- **First Identifier Attempt At**: Indicates when the first reveal attempt occurred.
- **Last Identifier Attempt At**: Indicates when the last reveal attempt occurred.
- **First Identified At**: Indicates when the anonymous user was first revealed.
- **Personal Email**: The personal email address of the identified user.
- **Business Email**: The professional or work email address of the identified user.
- **Age Range**: The estimated age range of the identified user (e.g., '25-34').
- **Company Address**: The full street address of the user's company.
- **Company City**: The city where the user's company is located.
- **Company Domain**: The website domain of the user's company.
- **Company Employee Count**: The estimated number of employees at the user's company.
- **Company Linkedin URL**: The URL for the user's company LinkedIn page.
- **Company NAICS**: The NAICS (North American Industry Classification System) code for the company's industry.
- **Company Name**: The legal name of the user's company.
- **Company Phone**: The general phone number for the user's company.
- **Company Revenue**: The estimated annual revenue of the user's company.
- **Company SIC**: The SIC (Standard Industrial Classification) code for the company's industry.
- **Company State**: The state or province where the user's company is located.
- **Company Zip**: The postal code for the user's company.
- **Department**: The department the user likely works in at their company (e.g., 'Marketing', 'Engineering').
- **First Name**: The first name of the identified user.
- **Gender**: The gender of the identified user.
- **Homeowner**: Indicates whether the user is a homeowner ('Yes'/'No').
- **Income Range**: The estimated household income range of the identified user.
- **Job Title**: The user's job title at their company (e.g., 'Marketing Manager').
- **Ip**: The IP address of the user from which the enrichment was triggered.
- **Job Title 2**: *No description provided.*
- **Last Name**: The last name of the identified user.
- **Linkedin URL**: The URL for the user's personal LinkedIn profile.
- **Married**: Indicates the marital status of the user ('Yes'/'No').
- **Mobile Phone**: The mobile phone number of the identified user.
- **Net Worth**: The estimated net worth of the identified user.
- **Personal City**: The city where the user resides.
- **Personal State**: The state or province where the user resides.
- **Personal Zip**: The personal postal code of the user.
- **Personal Zip4**: The extended 4-digit postal code (ZIP+4) for the user's personal address.
- **Primary Industry**: The primary industry in which the user works.
- **Professional Address**: The professional or business street address of the user.
- **Professional City**: The city of the user's professional address.
- **Professional State**: The state or province of the user's professional address.
- **Professional Zip**: The postal code of the user's professional address.
- **Professional Zip4**: The extended 4-digit postal code (ZIP+4) for the user's professional address.
- **Referrer URL**: The URL of the page that referred the user to the site, if available.
- **Seniority Level**: The user's seniority level within their company (e.g., 'Entry', 'Senior', 'C-Level').
- **Main Email**: Declares a primary email for the user. It prioritizes the personal email over the business email if both are available.
[title] Understanding Syncs in Chord
[path] Chord Data Platform/Data Activations/Data Activations/
::loom[]{url="https://www.loom.com/embed/b74184812f964a9c9c7285e9d1e64a3f"}
## Introduction
Syncs power Audience activation in Chord. When you send an Audience to a destination, such as an ESP or ad platform, you create a sync.
This page explains how syncs work and how to manage them.
## What is a sync?
A sync connects:
- A Chord Audience
- A destination
- A defined set of mapped fields
It controls how data moves from Chord to your external platform.
A sync does not change your underlying Audience logic. It only controls how that Audience is delivered.
## What you configure in a sync
When setting up a sync, you define:
**1. Destination**
Where the Audience is sent.
**2. Field mappings**
How Chord fields match destination fields.
Clear mapping ensures the destination platform receives data in the correct structure.
**3. Sync behavior**
Depending on the destination, you may configure:
- Full refresh vs. incremental updates
- List additions or removals
- Record update behavior
## Viewing sync history
![]()
![]()
Each sync includes a history of past runs.
You can review:
- Last run details
- Source details
- Destination details
- Full sync history
If a sync fails, start by reviewing the error details in the run history. Most issues relate to:
- Missing required fields
- Invalid mappings
- Destination-side validation rules
## Editing a sync
![]()
To edit a sync:
1. Navigate to **Data Activations**.
2. Click on **Manage Syncs.**
3. Select the specific sync you wish to edit.
4. Click on the three veritcal dots icon in the **Actions **column.
5. Click **Edit sync**.
:::hint{type="info"}
You can also Manage Syncs via the **Audience Destinations** tab on the **Audiences** page.
:::
All settings are available in one structured modal.
Changes apply to future runs. Historical runs remain unchanged.
## Deleting a sync
Deleting a sync:
- Stops future data updates
- Does not delete historical records in the destination platform
- Does not delete the underlying Audience
To delete a sync:
1. Navigate to **Data Activations**.
2. Click on **Manage Syncs.**
3. Select the specific sync you wish to delete.
4. Click on the three veritcal dots icon in the **Actions **column.
5. Click **Delete sync**.
:::hint{type="info"}
You can also Delete Syncs via the **Audience Destinations** tab on the **Audiences** page.
:::
## Best practices
- Confirm required destination fields before mapping.
- Review sync history after your first run.
- Keep field naming consistent across platforms.
- Test new syncs before launching time-sensitive campaigns.
[title] Transactions
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Chord OMS/
### x\_fct\_trans\_transactions
| Name | Description |
| ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Applied Gift Card Amount | Dollar value of the gift card at time of issuance. |
| Applied Gift Card Amount Used | Amount used from the initial gift card amount. |
| Applied Gift Card Currency | Currency of the gift card amount. |
| Applied Gift Card Gift Message | Gift card's custom message from the purchaser to the recipient. |
| Applied Gift Card Id | Unique key generated by Chord that uniquifies a gift card. |
| Applied Gift Card Is Redeemable | Flag that determines whether or not the gift card is redeemable. |
| Applied Gift Card Purchaser Name | Gift card's purchaser name as inputed by the gift card's purchaser. |
| Applied Gift Card Recipient Email | Gift card's recipient email. |
| Applied Gift Card Recipient Name | Gift card's recipient name as inputed by the gift card's purchaser. |
| Applied Gift Card Redemption Code | Gift card's redemption code. |
| Order Adjustment Types | List of distinct adjustment reasons for adjustments made to the order. |
| Order Admin Url | The Admin URL of pointing to the order. |
| Order Applied Discount Codes | List of promotion codes applied to the order. |
| Order Applied Discount Codes Count | Count of promotion codes applied to the order. |
| Order Applied Discount Ids | List of promotion ids applied to the order. |
| Order Applied Discount Names | List of promotion names applied to the order. |
| Order Applied Discount Names Count | Count of promotion names applied to the order. |
| Order Cart Url | Url of the cart which contains the order. |
| Order Channel | The channel from which the order is created. |
| Order Completed Order Rank By Subscription | Allows to rank completed orders by completion date for a subscription. |
| Order Completed Order Rank By User | Allows to rank completed orders by completion date for a user. |
| Order Contains Refund | Whether or not the order contains refund adjustments or refunds that are processed outside of the Chord OMS adjustment systems (for example via RMAs or cancellations). |
| Order Contains Replacement | Whether or not the order contains replacement adjustments or shipped replacement items (following an RMA authorization). |
| Order Contains Return | Whether or not the order contains returns (authorized RMAs). |
| Order Contains Rma Refund | Whether or not the order contains RMA refunds (refunds issued after an RMA was requested and authorized). |
| Order Contains Rma Store Credits | This column is not documented. |
| Order Currency | The currency for this order. |
| Order Customer Lifetime Month | Number of months between the current order's completion date and the user's first order completion date. First orders have a value of 1. |
| Order Customer Lifetime Week | Number of weeks between the current order's completion date and the user's first order completion date. First orders always have a value of 1. |
| Order Email | The email address of the customer that made the order. |
| Order Financial State | The current payment state of the order. |
| Order Fulfillment Ids | Array of unique keys generated by Chord to identify the unique shipments for an order. |
| Order Fulfillment Numbers | The unique identifier for this shipment. |
| Order Fulfillment State | The current shipment state of the order. |
| Order Has Discount | Whether or not the order has promotions applied to it. |
| Order Has Order Tags | Whether or not that order has tags. |
| Order Hours From Order To First Fulfillment | Number of hours between order completion and first order shipment; how long it takes a company to get the initial product out to a customer. |
| Order Hours From Order To Last Fulfillment | Number of hours between order completion and last order shipment. |
| Order Id | Unique key generated by Chord to identify a unique order. |
| Order Is Canceled | Whether or not the order is canceled. The order is considered canceled when the canceled\_at date is not null. |
| Order Is Completed | Whether or not that order is completed. The order is considered completed when the completed\_at date is not null. This means that the order does not necessarily have a state = 'complete', since states can change after the order completion (for example in the case of a refund). |
| Order Is First Completed Order | Whether or not that order was the first completed order for a user. |
| Order Is First Order | Whether or not that order was the first order for a user. |
| Order Is First Subscription Completed Order | Whether or not that order was the first completed order for a subscription. |
| Order Is First Subscription Order | Whether or not that order was the first order for a subscription. |
| Order Is Fulfilled | Whether or not that order has shipped. |
| Order Is Part Of Subscription | Whether or not that order is part of a subscription. |
| Order Is Pre Paid Purchase | Whether the order the orderincludes the purchase of a pre-payment; this could be a gift subscription, pre-pay subscription, or gift card. |
| Order Is Pre Paid Redemption | Whether the order included the redemption of a pre-payment; this could be the redemption of a gift subscription, pre-pay subscription, or gift card. |
| Order Is Referred By Affiliate | Whether or not the user is referred by an affiliate. |
| Order Is Referred By Referrer | Whether or not the user is referred by a referrer. |
| Order Is Replacement | True when the order is a replacement order. |
| Order Is Suspicious Referral Conversion | Wether this represents a suspicous referral conversions or not. |
| Order Number | Human-readable unique key generated by Solidus that identifies an order. It begins with a set of Tenant-Store defined letters and ends in a nine-digit number (for example, CHORD-123456789). This number is shown to the users in various places. These combinations are unique for a given Store. |
| Order Oms Order Id | Unique key generated by Solidus that identifies an order. |
| Order Rank By User | Allows to rank completed orders by completion date for a user. |
| Order Tags | List of tags associated to the order. |
| Order Tags Count | Number of tags associated to the order. |
| Order Referral Conversion Suspicious Reasons | A list of reasons explaining why the referral conversion is suspicious. |
| Order Referrer User Email | The email address of the customer identified with the referral. |
| Order Special Instructions | Any special shipping instructions that have been specified by the customer during checkout. |
| Order State | The current state of the order. |
| Order Subscription Customer Lifetime Month | Number of months between the current order's completion date and the user's first subscription order completion date. First orders have a value of 1. |
| Order Subscription Customer Lifetime Week | Number of weeks between the current order's completion date and the user's first subscription order completion date. First orders always have a value of 1. |
| Order User Referral Code | Unique key generated by Solidus that represents the user's referral code. |
| Order Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store. |
| Purchased Gift Card Amount | Dollar value of the gift card at time of issuance. |
| Purchased Gift Card Amount Used | Amount used from the initial gift card amount. |
| Purchased Gift Card Currency | Currency of the gift card amount. |
| Purchased Gift Card Gift Message | Gift card's custom message from the purchaser to the recipient. |
| Purchased Gift Card Id | Unique key generated by Chord that uniquifies a gift card. |
| Purchased Gift Card Is Redeemable | Flag that determines whether or not the gift card is redeemable. |
| Purchased Gift Card Purchaser Name | Gift card's purchaser name as inputed by the gift card's purchaser. |
| Purchased Gift Card Recipient Email | Gift card's recipient email. |
| Purchased Gift Card Recipient Name | Gift card's recipient name as inputed by the gift card's purchaser. |
| Purchased Gift Card Redemption Code | Gift card's redemption code. |
| Store Id | Unique key generated by our models that uniquifies a store. |
| Store Name | The name of the store. |
| Store Oms Admin Url | The Admin URL of that OMS. |
| Store Oms Id | Unique key generated by Chord that uniquifies an OMS. |
| Store Oms Store Id | Unique key generated by our models that uniquifies a store. |
| Store Oms Type | The type of the OMS. |
| Store Id | Unique key generated by our models that uniquifies a store. |
| Store Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Store Url | The Storefront URL of of the store. |
| Transaction Id | Unique key generated by Chord that uniquifies a transaction. |
| Transaction Payment Method | Represents the transaction's payment method. May include values such as 'Stripe', 'Venmo', etc. |
| Transaction Payment Type | Represents the transaction's payment type. May include values such as 'Money', 'Store Credit', 'Referral credit applied', etc. |
| Transaction Reason | Represents the transaction reason. May include values such as 'Return processing', 'Order canceled', 'Order', 'Order Not Received', etc. |
| Transaction Type | Represents the transaction type. Its value is either 'Payment' or 'Refund'. |
| User Completed Oms Order Ids | List of completed OMS order ids by a user. |
| User Completed Order Ids | List of completed order ids by a user. |
| User Credit Category Basket | Array of credit categories (Gift Card, Reimbursement, Referral Credits, Prepaid Subscription, GMA) issued per user. |
| User Email | Email address of the user. |
| User First Completed Oms Order Id | OMS order id of the first order completed by a user. |
| User First Completed Order Id | Unique order id of the first order completed by a user. |
| User First Order Unique Ordered Products | Unique products ordered by the user in their first completed order. |
| User First Order Unique Ordered Skus | Unique SKUs ordered by the user in their first completed order. |
| User Has Ordered A La Carte | Whether or not the user has had at least one order that is not part of a subscription. |
| User Has Promo Applied In First Order | Whether or not the user has a promo applied to their first completed order. |
| User Has Subscription In First Order | Whether or not the user's first order is linked to a subscription. |
| User Id | Unique key generated by Chord to identify a unique user. |
| User Is Active Subscriber | Whether or not the user has an active subscription with at least one completed subscription order. An active subscription is one that is not cancelled or paused. |
| User Is Customer | Whether or not the user is a customer. |
| User Is New Customer | Whether or not the user is a new customer. |
| User Is Not Customer | Whether or not the user is not a customer. |
| User Is Returning Customer | Whether or not the user is a returning customer. |
| User Is Subscriber | Whether or not the user has completed at least one subscription order. |
| User Login | The login email address of the user. |
| User Name | Full name of the user. |
| User Number Of Completed A La Carte Orders | Total amount of orders completed by a user that are a la carte. |
| User Number Of Completed Subscription Orders | Total amount of orders completed by a user that was part of a subscription. |
| User Number Of Orders With Promos | The count of completed orders with a promo applied. |
| User Number Of Subscriptions | Total amount of subscriptions linked to a user. |
| User Oms User Id | Unique key generated by Solidus that identifies a user. |
| User Phone | Phone number of the user. |
| User Total Completed Order Count | Total amount of orders completed by a user. |
| User Unique Ordered Products | Unique products ordered by the user across all orders. |
| User Unique Ordered Skus | Unique SKUs ordered by the user across all orders. |
| Applied Gift Card Applied At (Universal) | Timestamp that represents the time at which gift card was last applied as a payment method on an order - Universal Time Zone. |
| Applied Gift Card Created At (Universal) | Timestamp that represents the time at which gift card was created - Universal Time Zone. |
| Applied Gift Card Deactivated At (Universal) | Timestamp that represents the time at which gift card was deactivated - Universal Time Zone. |
| Applied Gift Card Sent At (Universal) | Timestamp that represents the time at which gift card was sent to its recipient - Universal Time Zone. |
| Applied Gift Card Updated At (Universal) | Timestamp that represents the time at which gift card was last updated - Universal Time Zone. |
| Order Approved At (Universal) | Reflects when the entity was approved in Solidus - Universal Time Zone. |
| Order Canceled At (Universal) | Reflects when the order was cancelled - Universal Time Zone. |
| Order Completed At (Central) | Reflects when the entity was moved to the 'completed' state - Cental Time Zone. |
| Order Completed At (Eastern) | Reflects when the entity was moved to the 'completed' state - Eastern Time Zone. |
| Order Completed At (Mountain) | Reflects when the entity was moved to the 'completed' state - Mountain Time Zone. |
| Order Completed At (Pacific) | Reflects when the entity was moved to the 'completed' state - Pacific Time Zone. |
| Order Completed At (Universal) | Reflects when the entity was moved to the 'completed' state - Universal Time Zone. |
| Order Created At (Central) | Reflects when the entity was first created in Solidus - Cental Time Zone. |
| Order Created At (Eastern) | Reflects when the entity was first created in Solidus - Eastern Time Zone. |
| Order Created At (Mountain) | Reflects when the entity was first created in Solidus - Mountain Time Zone. |
| Order Created At (Pacific) | Reflects when the entity was first created in Solidus - Pacific Time Zone. |
| Order Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Order First Fulfillment Fulfilled At (Universal) | Timestamp at which the first shipment for that order was shipped - Universal Time Zone. |
| Order Last Adjustment Refund At (Universal) | Timestamp of the last return adjustment for an order - Universal Time Zone. |
| Order Last Adjustment Replacement At (Universal) | Timestamp of the last replacement adjustment for an order - Universal Time Zone. |
| Order Last Fulfillment Fulfilled At (Universal) | Timestamp at which the last shipment for that order was shipped - Universal Time Zone. |
| Order Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| Purchased Gift Card Applied At (Universal) | Timestamp that represents the time at which gift card was last applied as a payment method on an order - Universal Time Zone. |
| Purchased Gift Card Created At (Universal) | Timestamp that represents the time at which gift card was created - Universal Time Zone. |
| Purchased Gift Card Deactivated At (Universal) | Timestamp that represents the time at which gift card was deactivated - Universal Time Zone. |
| Purchased Gift Card Sent At (Universal) | Timestamp that represents the time at which gift card was sent to its recipient - Universal Time Zone. |
| Purchased Gift Card Updated At (Universal) | Timestamp that represents the time at which gift card was last updated - Universal Time Zone. |
| Transaction Ts (Central) | Timestamp that represents the time at which the transaction was last updated - Cental Time Zone. |
| Transaction Ts (Eastern) | Timestamp that represents the time at which the transaction was last updated - Eastern Time Zone. |
| Transaction Ts (Mountain) | Timestamp that represents the time at which the transaction was last updated - Mountain Time Zone. |
| Transaction Ts (Pacific) | Timestamp that represents the time at which the transaction was last updated - Pacific Time Zone. |
| Transaction Ts (Universal) | Timestamp that represents the time at which the transaction was last updated - Universal Time Zone. |
| User Created At (Universal) | Timestamp at which the users row was created - Universal Time Zone. |
| User Date Of Birth (Universal) | Date of birth of the user - Universal Time Zone. |
| User Deleted At (Universal) | Timestamp at which the user's account was deleted - Universal Time Zone. |
| User First Order Completed At (Universal) | The timestamp of the user's first completed order - Universal Time Zone. |
| User First Subscription Order Completed At (Universal) | The timestamp of the user's first completed subscription order, regardless of subsequent subscriptions - Universal Time Zone. |
| User Last Order Completed At (Universal) | The timestamp of the user's last completed order - Universal Time Zone. |
| User Last Sign In At (Universal) | The last sign in timestamp for the user - Universal Time Zone. |
| User Updated At (Universal) | Timestamp at which the users row was last updated - Universal Time Zone. |
| Average Net Revenue | This column is not documented. |
| Average Transaction Amount | Full amount of transaction. The value will be positive if the transaction is a payment, and negative if the transaction is a refund. |
| Net Revenue | This column is not documented. |
| Transaction Amount | Full amount of transaction. The value will be positive if the transaction is a payment, and negative if the transaction is a refund. |
[title] Data Support for Multiple Stores
[path] Chord Data Platform/Overview/
Chord supports a "multi-store" architecture, i.e. sending data from more than one store to the same Chord instance. Chord displays the resulting data in aggregate while also providing the ability to filter by store.
:::hint{type="warning"}
This is an advanced feature. Please speak with someone at Chord before acting on the following.
:::
## Requirements
These must be true:
1. All stores use the same OMS, such as Shopify.
2. It is acceptable that store data will not be isolated.
## Recommendations
When configuring your **Chord CDP**:
- We recommend creating unique Sources per store. The schema name of these Sources must follow a naming convention that we can provide. Use the correct write keys when sending events to each Source.
- All sources should point to the same Chord Data Warehouse Destination.
- We recommend the same approach for other Destinations (e.g. GA4, Klaviyo). It is up to how your business uses those services, but having multiple instances of each may make our data less effective.
## Limitations
The **Integrations > Data Sources **portion of Chord does not currently have multi-store support. Please consult with us with regards to any implications that might have.
Chord does not currently support **multiple currencies**. As a result:
- All currency will be shown as USD, but will not have been converted. For example, sales worth €1,000 will be shown as $1,000. The correct symbol (e.g. "€") will not appear, nor will that $1,000 reflect any conversion rates between EUR and USD.
- Given the above, reports that aggregate data between multiple currencies will not be accurate. For example, sales across three stores worth $100, €50, and £25 would be shown as $175. That total will not reflect any conversation rates between USD and other currencies.
It is worth noting that despite the above, our data does have record of what currency each transaction was made in. That information will be used as we add multi-currency support.
[title] Subscriber Journey Monthly Explore
[path] Chord Data Platform/Data Models/Subscriptions/
## Overview
Monthly snapshots of subscriber state.
- Grain: **1 row per subscriber per month**
- Purpose: **retention + LTV progression analysis**
## When to use
- Cohort retention curves
- LTV growth over time
- Monthly churn/reactivation patterns
- MoM reporting
## Key dimensions & metrics
| Field | Description |
| ------------------------------- | -------------------- |
| Snapshot Month End Date | Month end |
| Cohort Month | First subscription |
| Months Since First Subscription | Cohort age |
| Is Active Subscriber EOM | Active at month end |
| Is Churned EOM | Churned at month end |
| Active Subscription Count EOM | Active count |
| LTV Gross Revenue EOM | Cumulative revenue |
| LTV Order Count EOM | Cumulative orders |
| Orders This Month | Monthly orders |
| Revenue This Month | Monthly revenue |
| New Subscriptions This Month | New subs |
| Cancellations This Month | Cancelled subs |
| Has Churned By EOM | Ever churned |
| Has Reactivated By EOM | Ever reactivated |
| Churn Count By EOM | Total cancellations |
## Example business questions
- Retention curve by cohort
- LTV growth curves
- Monthly subscription revenue
- Churn timing by lifecycle
## Notes & caveats
- EOM = **End of Month**
- Rows only exist **after subscriber creation**
## Glossary
| Term | What it Means | How to Interpret / Use | Where You’ll See It in Looker |
| ------------------------ | --------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Active Subscription** | A subscription that is currently ongoing. Includes both fully active and paused subscriptions. | Use this to understand the **current size of your subscriber base**. Note that paused users are still counted. | Subscription Metrics Daily (Active Count), Subscriber Journey (Is Active Subscriber), Subscriber Journey Monthly (Is Active Subscriber EOM), Product & Bundle Explores (Active Subscription Count) |
| **Churn / Churned** | A subscription that has been cancelled. Does not include pauses. | Represents **true customer loss**. Track this to understand retention issues. | Subscription Metrics Daily (Churned Count, Churn Rate), Subscriber Journey (Is Churned, Churn Count), Monthly (Is Churned EOM, Cancellations This Month), Events Enriched (Event Type = canceled), Movements (status\_cancelled) |
| **Winback** | A subscriber who cancelled all subscriptions and later returned by subscribing again. | Indicates **successful re-engagement** after churn. | Subscriber Journey (Is Winback), Subscriber Journey Monthly (Has Reactivated By EOM) |
| **Reactivation** | A previously cancelled subscription that becomes active again (subscription-level). | Measures **recovery of churned subscriptions**. | Subscription Metrics Daily (Reactivated Count), Movements (status\_reactivated), Events Enriched (Event Type = reactivated) |
| **Net New** | Net change in subscriptions: New + Reactivated − Cancelled. | Indicates **overall growth vs decline**. | Subscription Metrics Daily (Net New Count) |
| **LTV (Lifetime Value)** | Total revenue generated by a subscriber across all subscription orders. | Use to understand **customer value over time** and compare cohorts or segments. | Subscriber Journey (LTV Gross / Net Revenue), Subscriber Journey Monthly (LTV Gross Revenue EOM) |
| **EOM (End of Month)** | Metrics calculated as of the last day of a month. | Used for **consistent month-over-month comparisons** (retention, LTV growth). | Subscriber Journey Monthly (all EOM fields like Active EOM, LTV EOM) |
| **Solo Subscription** | A subscription that contains only one product. | Helps identify products that perform well **individually**. | Subscription Product Metrics Daily (Solo Subscription Count) |
| **Bundle** | A subscription that contains two or more products. | Useful for analyzing **product combinations and cross-sell behavior**. | Product Metrics (Bundle Subscription Count), Bundle Metrics Daily (all bundle fields) |
| **Movement** | Any change in a subscription’s state (created, cancelled, paused, resumed, reactivated, quantity/price change). | Use to understand **operational changes and trends** in subscriptions. | Subscription Movements Daily (Movement Type, Category), Events Enriched (Event Type) |
| **Provider** | The system managing subscriptions (Recharge, ChordOMS, CustomOMS). | Important context — **data availability and detail vary by provider**, which affects analysis. | All Explores (Provider filter present everywhere) |
[title] Activities
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Salesforce/
### x\_fct\_trans\_activities
| Name | Description |
| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Activity Event Text | The name of the event. |
| Activity Event Text Id | The slug of the event name, mapping to the page or track event table. |
| Activity Id | The unique identifier of an activities (i.e. Track or Page event). |
| Activity Page Path | The page path part of the URL. A page path is the part of URL that comes after the hostname (domain) and before the query parameters, URL fragment, or port. (e.g. `/pages/contact-us/` for `https://chord.co/pages/contact-us/?ref=internal-banner` .) |
| Activity Page Query | The query string portion of the URL of the page. |
| Activity Page Title | The title/name of the page. |
| Activity Page Url | The URL of the page. |
| Activity Session Activity Count | Total count of activities, pave views and tracked events within the session. |
| Activity Session Attribution Channel | The attribution channel for the first page event of the session. Sessions with an attribution of 'Unknown' indicates that there is no attributable data for that session. |
| Activity Session Attribution Channel Paid Or Organic | Indicates if the session's first page attribution is paid or organic. Attribution is considered Organic if the attribution channel is 'Direct', 'Other', 'Organic Search', 'Organic Social', 'Email', or 'SMS'. |
| Activity Session Attribution First Page Url Has Gclid | Indicates if the first page event of the session has a Google Click ID. |
| Activity Session Attribution First Page Url Has Utm | Indicates if the first page event of the session has any utm information. |
| Activity Session Attribution Has Referrer | Indicates if the first page event of the session has a referrer host. |
| Activity Session Attribution Medium | The campaign medium represented by the UTM tags for the first page event of the session. |
| Activity Session Attribution Source | The campaign source represented by the UTM tags for the first page event of the session. |
| Activity Session Attribution Sub Channel | Sub-Channel is a granular level of attribution. |
| Activity Session Completed Oms Order Ids | Array of OMS Order IDs associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Activity Session Completed Order Ids | Array of order IDs associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Activity Session Completed Order Numbers | Array of order numbers associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Activity Session Days Since Last Session End | The days between the last session's end and the start of this session. |
| Activity Session Device | The device on which the event was sent from. |
| Activity Session Device Category | The device category of the device on which the event was sent from. There are multiple supported values for this column such as 'iPhone', |
| Activity Session Duration In Seconds | Total seconds between start and end activities within the session. |
| Activity Session Duration In Seconds Tiers | Total seconds between start and end activities within the session, aggregated into tiers: 0-9s, 10-29s, 30-59s, and 60s or more. |
| Activity Session Has Order Completion | Flag for sessions with an order completed or checkout completed front-end events |
| Activity Session Id | Unique ID for the session. |
| Activity Session Number | Session number per anonymous id. |
| Activity Session Unique Completed Order Count | Count of unique order ids associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Activity Session Unique Completed Order Number Count | Count of unique order numbers associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Activity Utm Campaign | The campaign name represented by the UTM tags. |
| Activity Utm Content | The campaign content represented by the UTM tags. |
| Activity Utm Medium | The campaign medium represented by the UTM tags. |
| Activity Utm Source | The campaign source represented by the UTM tags. |
| Activity Utm Term | The campaign term represented by the UTM tags. |
| Activity Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store |
| Anonymous Completed Oms Order Ids | Array of OMS Order IDs associated to the anonymous\_id, as collected by order completed or checkout completed front-end events, over time. |
| Anonymous Completed Order Ids | Array of order IDs associated to the anonymous\_id, as collected by order completed or checkout completed front-end events, over time. |
| Anonymous Completed Order Numbers | Array of order numbers associated to the anonymous\_id, as collected by order completed or checkout completed front-end events, over time. |
| Anonymous Current Blended User Id | Unique id derived from the user\_id and the anonymous\_id. Whenever a customer has a user\_id, the user\_anonymous\_id will be constant for |
| Anonymous Current User Id | The current user\_id associated with the anonymous\_id. This unique user\_id is created by Segment's Identify call. A user\_id can be associated to many anonymous\_ids. |
| Anonymous Id | Unique id created by Chord for each anonymous visitor per store. |
| Anonymous Segment Anonymous Id | Id created by Segment for each anonymous visitor. This id gets created as soon as a customer's browser loads the analytics javascript widget. The anonymous\_id remains unchanged through the entire browsing session from a single device. Depending on configuration, two stores connected stores may have the same anonymous\_id. |
| Anonymous Unique User Ids | Array of user IDs mapped to an anonymous ID. |
| Date Day Num Of Year | The number representing the day of the year. |
| Date Id | Unique key that uniquify a date. |
| Date Month Num Of Year | The month number of the year. |
| Last Seen Page Browser Locale | Locale of browser. |
| Last Seen Page Device | The device on which the event was sent from. |
| Last Seen Page Device Category | The device category of the device on which the event was sent from. There are multiple supported values for this column such as 'iPhone', |
| Last Seen Page Event Table Name | The properly formatted name of the table of the event. |
| Last Seen Page Event Text | The name of the event. |
| Last Seen Page Event Text Id | The slug of the event name, mapping to the page or track event table. |
| Last Seen Page Gclid | The Google Click ID. Google Click ID (GCLID) is a parameter passed in the URL with ad clicks, to identify the campaign and other attributes of the click associated with the ad for ad tracking and campaign attribution. |
| Last Seen Page Id | Unique key generated by Segment for each tracking or page event. |
| Last Seen Page Oms Id | Unique key generated by our models that uniquifies an OMS. |
| Last Seen Page Host | The host of the event's URL. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev`. This facilitates grouping events by host. |
| Last Seen Page Path | The page path part of the URL. A page path is the part of URL that comes after the hostname (domain) and before the query parameters, URL fragment, or port. (e.g. `/pages/contact-us/` for `https://chord.co/pages/contact-us/?ref=internal-banner`) |
| Last Seen Page Query | The query string portion of the URL of the page. |
| Last Seen Page Referrer | The referrer of the page. The referrer is the webpage that sends visitors to the site using a link. In |
| Last Seen Page Title | The title/name of the page. |
| Last Seen Page Url | The URL of the page. |
| Last Seen Page Referrer Host | The host of the referrer. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev`. This facilitates grouping events by host. |
| Last Seen Page Segment User Id | The unique ID of the user. |
| Last Seen Page Store Id | Unique key generated by our models that uniquifies a store. |
| Last Seen Page Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Last Seen Page User Agent | The User agent of the device making the request. A User agent request header is a characteristic string that lets servers and |
| Last Seen Page User Id | Unique key generated by Chord to identify the user. |
| Last Seen Page Utm Campaign | The campaign name represented by the UTM tags. |
| Last Seen Page Utm Content | The campaign content represented by the UTM tags. |
| Last Seen Page Utm Medium | The campaign medium represented by the UTM tags. |
| Last Seen Page Utm Source | The campaign source represented by the UTM tags. |
| Last Seen Page Utm Term | The campaign term represented by the UTM tags. |
| Last Seen Page Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store |
| Session Landing Page Browser Locale | Locale of browser. |
| Session Landing Page Device | The device on which the event was sent from. |
| Session Landing Page Device Category | The device category of the device on which the event was sent from. There are multiple supported values for this column such as 'iPhone', |
| Session Landing Page Event Table Name | The properly formatted name of the table of the event. |
| Session Landing Page Event Text | The name of the event. |
| Session Landing Page Event Text Id | The slug of the event name, mapping to the page or track event table. |
| Session Landing Page Gclid | The Google Click ID. Google Click ID (GCLID) is a parameter passed in the URL with ad clicks, to identify the campaign and other attributes of the click associated with the ad for ad tracking and campaign attribution. |
| Session Landing Page Id | Unique key generated by Segment for each tracking or page event. |
| Session Landing Page Oms Id | Unique key generated by our models that uniquifies an OMS. |
| Session Landing Page Host | The host of the event's URL. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev`. This facilitates grouping events by host. |
| Session Landing Page Path | The page path part of the URL. A page path is the part of URL that comes after the hostname (domain) and before the query parameters, URL fragment, or port. (e.g. `/pages/contact-us/` for `https://chord.co/pages/contact-us/?ref=internal-banner`.) |
| Session Landing Page Query | The query string portion of the URL of the page. |
| Session Landing Page Referrer | The referrer of the page. The referrer is the webpage that sends visitors to the site using a link. In |
| Session Landing Page Title | The title/name of the page. |
| Session Landing Page Url | The URL of the page. |
| Session Landing Page Referrer Host | The host of the referrer. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev`. This facilitates grouping events by host. |
| Session Landing Page Segment User Id | The unique ID of the user. |
| Session Landing Page Store Id | Unique key generated by our models that uniquifies a store. |
| Session Landing Page Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Session Landing Page User Agent | The User agent of the device making the request. A User agent request header is a characteristic string that lets servers and |
| Session Landing Page User Id | Unique key generated by Chord to identify the user. |
| Session Landing Page Utm Campaign | The campaign name represented by the UTM tags. |
| Session Landing Page Utm Content | The campaign content represented by the UTM tags. |
| Session Landing Page Utm Medium | The campaign medium represented by the UTM tags. |
| Session Landing Page Utm Source | The campaign source represented by the UTM tags. |
| Session Landing Page Utm Term | The campaign term represented by the UTM tags. |
| Session Landing Page Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store |
| Store Id | Unique key generated by our models that uniquifies a store. |
| Store Name | The name of the store. |
| Store Oms Admin Url | The Admin URL of that OMS. |
| Store Oms Id | Unique key generated by Chord that uniquifies an OMS. |
| Store Oms Store Id | Unique key generated by our models that uniquifies a store. |
| Store Oms Type | The type of the OMS. |
| Store Id | Unique key generated by our models that uniquifies a store. |
| Store Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Store Url | The Storefront URL of of the store. |
| User Address 1 | The first line of the street address. |
| User Address 2 | The optional second line of the address. |
| User Address City | The city of the address. |
| User Address Country | The country of the address. |
| User Address Name | The full name of the customer, based on firstName and lastName. |
| User Address State | The region of the address, such as the province, state, or district. |
| User Address Zip | The postal code of the address. |
| User Completed Oms Order Ids | Array of OMS Order IDs associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| User Completed Order Ids | Array of order IDs associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| User Completed Order Numbers | Array of order numbers associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| User Email | The email associated with the user. |
| User Id | Unique ID per user. It is equal to either 1) a identified\_user\_id as identified by Segment in the Identify call, or 2) an anonynous\_id. |
| User Identified User Id | Unique ID per identified user. (See Segment's documentation on user\_id)\[ `https://segment.com/docs/connections/spec/identify/#user-id` ]. |
| User Ip | IP address associated with the user. |
| User Last Anonymous Id | Last seen anonymous\_id per user. An anonymous\_id is a unique ID per anonymous visitor. (See Segment's documentation on anonymous\_id)\[ `https://segment.com/docs/connections/spec/identify/#anonymous-id` ]. |
| User Last Segment Anonymous Id | This column is not documented. |
| User Segment User Id | The unique ID of the user. |
| User Unique Anonymous Ids | Array of all seen anonymous\_ids per user. An anonymous\_id is a unique ID per anonymous visitor. (See Segment's documentation on anonymous\_id)\[ `https://segment.com/docs/connections/spec/identify/#anonymous-id` ]. |
| User Unique Completed Order Count | Count of unique order ids associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| Activity Session End Ts (Universal) | Last activity timestamp for a session - Universal Time Zone. |
| Activity Session Last Session End Ts (Universal) | The timestamp of the previous session's end per blended user id, if this is not the user's first session - Universal Time Zone. |
| Activity Session Last Session Start Ts (Universal) | The timestamp of the previous session's start per blended user id, if this is not the user's first session - Universal Time Zone. |
| Activity Session Start Ts (Central) | First activity timestamp for a session - Cental Time Zone. |
| Activity Session Start Ts (Eastern) | First activity timestamp for a session - Eastern Time Zone. |
| Activity Session Start Ts (Mountain) | First activity timestamp for a session - Mountain Time Zone. |
| Activity Session Start Ts (Pacific) | First activity timestamp for a session - Pacific Time Zone. |
| Activity Session Start Ts (Universal) | First activity timestamp for a session - Universal Time Zone. |
| Activity Ts (Central) | The timestamp calculated by Segment correcting clock skew - Cental Time Zone. |
| Activity Ts (Eastern) | The timestamp calculated by Segment correcting clock skew - Eastern Time Zone. |
| Activity Ts (Mountain) | The timestamp calculated by Segment correcting clock skew - Mountain Time Zone. |
| Activity Ts (Pacific) | The timestamp calculated by Segment correcting clock skew - Pacific Time Zone. |
| Activity Ts (Universal) | The timestamp calculated by Segment correcting clock skew - Universal Time Zone. |
| Last Seen Page Ts (Universal) | The timestamp calculated by Segment correcting clock skew - Universal Time Zone. |
| Session Landing Page Ts (Universal) | The timestamp calculated by Segment correcting clock skew - Universal Time Zone. |
| User Created At (Universal) | The timestamp when the user was created - Universal Time Zone. |
| User First Seen At (Universal) | The first time the user was seen on the site, identified as either anonymous ID or user ID - Universal Time Zone. |
### x\_fct\_current\_sales\_\_daily
| Name | Description |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Date Day Num Of Year | The number representing the day of the year. |
| Date Id | Unique key that uniquify a date. |
| Date Month Num Of Year | The month number of the year. |
| Ts (Universal) | The truncated UTC date the order was created - Universal Time Zone. |
| Average Completed Order Count | The total count of orders created on the UTC date that have been completed. An order is considered complete if it has a status of 'Fulfilled' or 'Returned' or it has a status 'Canceled' and has a payment associated with it. |
| Average Created Order Count | The total count of orders created on the UTC date. |
| Average Gross Sales | The gross sales for completed orders. An order is considered complete if it has a status of 'Fulfilled' or 'Returned' or it has a status 'Canceled' and has a payment associated with it. |
| Average Net Revenue | The net sales for completed orders. An order is considered complete if it has a status of 'Fulfilled' or 'Returned' or it has a status 'Canceled' and has a payment associated with it. |
| Average Placed Gross Revenue | Gross Revenue is the pre-tax, pre-adjusted total line item price (unit price \* quantity) + the fulfillment total. |
| Average Placed Net Revenue | Net Revenue is the adjusted line item price (unit price \* quantity - line adjustments) + the adjusted fulfillment (fulfillment total - line adjustments) - order level adjustments - refunds. |
| Completed Order Count | The total count of orders created on the UTC date that have been completed. An order is considered complete if it has a status of 'Fulfilled' or 'Returned' or it has a status 'Canceled' and has a payment associated with it. |
| Created Order Count | The total count of orders created on the UTC date. |
| Gross Sales | The gross sales for completed orders. An order is considered complete if it has a status of 'Fulfilled' or 'Returned' or it has a status 'Canceled' and has a payment associated with it. |
| Net Revenue | The net sales for completed orders. An order is considered complete if it has a status of 'Fulfilled' or 'Returned' or it has a status 'Canceled' and has a payment associated with it. |
| Placed Gross Revenue | Gross Revenue is the pre-tax, pre-adjusted total line item price (unit price \* quantity) + the fulfillment total. |
| Placed Net Revenue | Net Revenue is the adjusted line item price (unit price \* quantity - line adjustments) + the adjusted fulfillment (fulfillment total - line adjustments) - order level adjustments - refunds. |
[title] Audience Activations with Ninetailed
[path] Chord Data Platform/Data Activations/Data Activations/Destination Set-up Notes/
# Introduction
This document provides an overview of how to use our Ninetailed Sync using Chord's Audiences API. Ninetailed is a personalization and experimentation platform built for modern, headless CMS and e-commerce setups. It enables marketers and developers to deliver tailored content and experiences to different user segments.
The primary focus when it comes to audience activations with Ninetailed via Chord is to add profile traits defined through Chord’s pre-built and custom audience dashboards. This enables real-time personalization by delivering dynamic audience data to Ninetailed.
:::hint{type="info"}
If you get stuck or have additional questions as you review this documentation, feel free to reach out to us at [help@chord.co](mailto\:help@chord.co) — our team is also happy to help you activate audiences on other CMS tools or platforms that help you get your job done!
:::
# Chord to Ninetailed Activation Flow
- **Chord Platform Application:** Audiences are created via the Chord platform per the existing flow.
- **Integration with DynamoDB:** Chord extracts Audience data from our Snowflake warehouses and stores it in an **AWS DynamoDB table**.
- **DynamoDB Stream:** A stream of events generated form changes to the table are queued.
- **AWS Lambda Function:** An **AWS Lambda function** receives the events via a connected stream trigger to process and bulk send up to 50 “identify” events per request.
- If emails are used as the primary key for an audience, the emails are hashed before being sent as the id to Ninetailed.
- **Conentful/Ninetailed**: The synchronized traits can now be utilized in building targeted content using the trait attributes on the profile.
# Sample Request to Ninetailed
:::hint{type="info"}
Chord requires the following two items to setup the sync to the [bulk upsert URL](https://www.contentful.com/developers/docs/personalization/experience-api/#batch-upsert-profiles):
- **api\_key**
- **environment**
:::
```javascript
curl --location 'https://experience.ninetailed.co/v2/organizations/{API_KEY}/environments/{ENV}/events' \
--header 'Content-Type: application/json' \
--data '{
"events": [
{
"channel": "server",
"context": {
"library": {
"name": "Chord Audiences",
"version": "1.0.0"
}
},
"messageId": "58f358f2-a858-11ed-afa1-0242ac120002",
"anonymousId": "(userId || anonymousId)",
"userId": "(userId || anonymousId)",
"traits": {"Audience - FirstTimeBuyer": "true" },
"type": "identify"
},
{
"channel": "server",
"context": {
"library": {
"name": "Chord Audiences",
"version": "1.0.0"
}
},
"messageId": "58f358f2-a858-11ed-afa1-0242ac120002",
"anonymousId": "(userId || anonymousId)",
"userId": "(userId || anonymousId)",
"traits": {"Audience - SuperFan": "false" },
"type": "identify"
}
]
}'
```
If emails are used as the primary key for an audience, the emails are hashed before being sent as the ID. If you would like to fetch the profile through Ninetailed using the email, you can obtain the id through this code snippet:
```jsx
async function hashEmail(email) {
const encoder = new TextEncoder();
const data = encoder.encode(email.toLowerCase());
const hashBuffer = await crypto.subtle.digest('SHA-256', data);
const hashArray = Array.from(new Uint8Array(hashBuffer));
const base64Hash = btoa(String.fromCharCode(...hashArray));
return base64Hash.replace(/[^a-zA-Z0-9]/g, '').substring(0, 32);
}
```
# DynamoDB Destination
Chord will handle the connection to the DynamoDB destination for you. You can view it as part of your [Data Activations](https://docs.chord.co/data-activations):
# Creating a Sync
Using our Sync UI, we first need to create a new sync that connects a custom Audience as the **source** and our DynamoDB table as the **destination**.
As a Chord tenant, you will have access to your own dedicated DynamoDB table. The example below is using `chord_audiences` for documentation purposes.
## Select Sync Behavior
Sync Behaviors dictate the types of change that should be applied to your data when a sync finds a matching (or not) record in a source and a destination.
Available sync behaviors are:
- **Update or Create (aka Upsert):** Update existing destination records when IDs match, otherwise, create new records if they're missing.
- **Mirror:** Keep the destination in sync with the source.
- If a row is added or edited in the source, update the destination.
- If a previously synced row no longer is in the source, remove the matching object from the destination.
:::hint{type="info"}
Mirror syncs identify changes by comparing against the data they have already sent -- not the data that might or might not already exist in the destination.
This means that the first sync will be an upsert for all records, and the second and following syncs will account for changes from the source data.
:::
# Sync Key
:::hint{type="danger"}
**Note: **The following steps (Sync Key, Field Mapping) are more advanced and should be handled by Chord employees or individuals with a strong understanding of the feature.
:::
Sync Keys will dictate how to associate data in the source with the destination. Both the source and destination need to provide a single, unique per record, identifying field. The identifiers will be used to look for matches. When a match is found - or not found - we then can use your selected Sync Behavior to decide what to do.
Your sync key can be any kind of unique identifier, like a user ID, an email address, etc. However, we do recommend using a “blended user ID” provided by Chord if possible (see below).
## Mapping with a blended user identifier
Some audiences may contain what we call a “blended user ID,” which is derived from the Chord data models to contain the CDP User ID - if one exists - else the Anonymous ID. This use case is particularly useful when mixing users that may or may not have a known CDP User ID.
This means that you will be able to look up a user via the Audience API using either a CDP anonymous ID or a known User ID (in this case).
:::hint{type="info"}
When using blended ID, it is very important to keep in mind that if you query an Anonymous ID that was identified at any point, our API won't return any result.
:::
# Field Mapping
Once you've defined *how* data is related between your source and destination, the next step is to determine *what* properties should be updated. The field mapping step lets you specify how fields should be mapped from your source model to the destination object's fields.
- We start by assigning our unique user identifier. `anonymous_current_cdp_blended_user_id` will become our `pk` (primary key).
- We can then set up the `sk` (sort key). It is **important** to ensure that this value reflects the name of the Audience being synced. You can easily obtain that value by choosing `Sync Metadata > Source Name`
You should end up with the following:
# Sync Schedule
Like any [Data Activations sync](https://docs.chord.co/gFnF-data-activations) on the Chord data platform, the Ninetailed sync can be scheduled to run at regular intervals.
The Chord platform will display the sync results on the** Data Activations** page when you click into the **"Manage Syncs"** button.
[title] Orders
[path] Chord Data Platform/Data Models/
### Overview
Chord utilizes transactional data from the OMS (Chord OMS, Shopify, etc.) to derive the orders dataset.
### Created vs. Completed Orders
Chord has two different order concepts:
- **Created Order: **When the order was first created in the OMS. This date will be most closely aligned with how OMSes report orders.
- **Completed Order: **When the order is considered complete, either when it's closed or fully fulfilled. This timestamp is useful for financial reporting, such as revenue recognition.
- For Shopify, the `closed_at` timestamp is generated for orders in Shopify that are automatically archived. If this feature is not enabled, the last updated closed fulfillment date is used as the completed at date.
- For Chord OMS, the order is considered completed when the `completed_at` date is not null. This means that the order does not necessarily have a state = 'complete', since states can change after the order completion (for example in the case of a refund).
### Orders vs. Sales Explores
The "Orders" explore contains all orders regardless of status, whereas the "Sales" explore includes only completed orders.
:::hint{type="success"}
if you have any questions or need help, please reach out to us at [help@chord.co](mailto\:help@chord.co)
:::
[title] Marketing Attribution
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Chord OMS/
### extend\_x\_fct\_trans\_orders\_for\_attribution
| Name | Description |
| ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Affiliate Email | Email address of the affiliate. |
| Affiliate Id | Unique key generated by Chord to identify a unique affiliate. |
| Affiliate Name | Full name of the user. |
| Affiliate Seen Emails | List of email addresses seen. |
| Affiliate User Id | Unique key generated by Chord to identify a unique user. |
| Billing Address Address1 | The street address of the customer. |
| Billing Address Address2 | The optional second address of the customer. |
| Billing Address Alternative Phone | The customer's alternative phone number. |
| Billing Address City | The city where the address is. |
| Billing Address Company | A company name. |
| Billing Address Country Abbr | |
| Billing Address Country Name | Full name of the country. |
| Billing Address Firstname | First name of the customer. |
| Billing Address Id | Unique key generated by Chord to identify a unique address. |
| Billing Address Lastname | Last name of the customer. |
| Billing Address Oms Address Id | Unique key generated by Solidus that identifies an address. |
| Billing Address Phone | The customer's phone number. |
| Billing Address State Abbr | |
| Billing Address State Name | Full name of the state. |
| Billing Address Zipcode | The postal code. |
| Order Adjustment Types | List of distinct adjustment reasons for adjustments made to the order. |
| Order Admin Url | The Admin URL of pointing to the order. |
| Order Applied Discount Codes | List of promotion codes applied to the order. |
| Order Applied Discount Codes Count | Count of promotion codes applied to the order. |
| Order Applied Discount Ids | List of promotion ids applied to the order. |
| Order Applied Discount Names | List of promotion names applied to the order. |
| Order Applied Discount Names Count | Count of promotion names applied to the order. |
| Order Cart Url | Url of the cart which contains the order. |
| Order Channel | The channel from which the order is created. |
| Order Completed Order Rank By Subscription | Allows to rank completed orders by completion date for a subscription. |
| Order Completed Order Rank By User | Allows to rank completed orders by completion date for a user. |
| Order Contains Refund | Whether or not the order contains refund adjustments or refunds that are processed outside of the Chord OMS adjustment systems (for example via RMAs or cancellations). |
| Order Contains Replacement | Whether or not the order contains replacement adjustments or shipped replacement items (following an RMA authorization). |
| Order Contains Return | Whether or not the order contains returns (authorized RMAs). |
| Order Contains Rma Refund | Whether or not the order contains RMA refunds (refunds issued after an RMA was requested and authorized). |
| Order Contains Rma Store Credits | This column is not documented. |
| Order Currency | The currency for this order. |
| Order Customer Lifetime Month | Number of months between the current order's completion date and the user's first order completion date. First orders have a value of 1. |
| Order Customer Lifetime Week | Number of weeks between the current order's completion date and the user's first order completion date. First orders always have a value of 1. |
| Order Email | The email address of the customer that made the order. |
| Order Financial State | The current payment state of the order. |
| Order Fulfillment Ids | Array of unique keys generated by Chord to identify the unique shipments for an order. |
| Order Fulfillment Numbers | The unique identifier for this shipment. |
| Order Fulfillment State | The current shipment state of the order. |
| Order Has Discount | Whether or not the order has promotions applied to it. |
| Order Has Order Tags | Whether or not that order has tags. |
| Order Hours From Order To First Fulfillment | Number of hours between order completion and first order shipment; how long it takes a company to get the initial product out to a customer. |
| Order Hours From Order To Last Fulfillment | Number of hours between order completion and last order shipment. |
| Order Id | Unique key generated by Chord to identify a unique order. |
| Order Is Canceled | Whether or not the order is canceled. The order is considered canceled when the canceled\_at date is not null. |
| Order Is Completed | Whether or not that order is completed. The order is considered completed when the completed\_at date is not null. This means that the order does not necessarily have a state = 'complete', since states can change after the order completion (for example in the case of a refund). |
| Order Is First Completed Order | Whether or not that order was the first completed order for a user. |
| Order Is First Order | Whether or not that order was the first order for a user. |
| Order Is First Subscription Completed Order | Whether or not that order was the first completed order for a subscription. |
| Order Is First Subscription Order | Whether or not that order was the first order for a subscription. |
| Order Is Fulfilled | Whether or not that order has shipped. |
| Order Is Part Of Subscription | Whether or not that order is part of a subscription. |
| Order Is Pre Paid Purchase | Whether the order the orderincludes the purchase of a pre-payment; this could be a gift subscription, pre-pay subscription, or gift card. |
| Order Is Pre Paid Redemption | Whether the order included the redemption of a pre-payment; this could be the redemption of a gift subscription, pre-pay subscription, or gift card. |
| Order Is Referred By Affiliate | Whether or not the user is referred by an affiliate. |
| Order Is Referred By Referrer | Whether or not the user is referred by a referrer. |
| Order Is Replacement | True when the order is a replacement order. |
| Order Is Suspicious Referral Conversion | Wether this represents a suspicous referral conversions or not. |
| Order Item Id | Unique key generated by Chord to identify a unique order. |
| Order Item Line Items Quantity | Sum of line items quantities per order. |
| Order Item Product Basket | List of product names per in the order. |
| Order Item Product Basket Count | Number of products in the order. |
| Order Product Basket | The titles of products for a given order array converted to a string. |
| Order Item Total Line Item Unit Quantity | Sum of line item units in the order. |
| Order Item Total Line Items Quantity | Sum of line items quantities per order. |
| Order Item Unique Product Basket | List of unique product names per in the order. |
| Order Item Unique Product Basket Count | Number of unique products in the order. |
| Order Unique Product Basket | The list of unique products for a given order array converted to a string. |
| Order Item Unique Unit Basket | List of unique units in the order. |
| Order Item Unique Unit Basket Count | Count of unique units in the order. |
| Order Unit Basket | The list of units for a given order array converted to a string. |
| Order Item Unique Variant Basket | List of unique variant names per in the order. |
| Order Item Unique Variant Basket Count | Number of unique variants in the order. |
| Order Unique Variant Basket | The list of unique variants for a given order array converted to a string. |
| Order Item Unit Basket | List of all units in the order. |
| Order Item Unit Basket Count | Count of all units in the order. |
| Order Unique Unit Basket | The list of unique units for a given order array converted to a string. |
| Order Item Variant Basket | List of variant names per in the order. |
| Order Item Variant Basket Count | Number of variants in the order. |
| Order Variant Basket | The titles of variants for a given order array converted to a string. |
| Order Number | Human-readable unique key generated by Solidus that identifies an order. It begins with a set of Tenant-Store defined letters and ends in a nine-digit number (for example, CHORD-123456789). This number is shown to the users in various places. These combinations are unique for a given Store. |
| Order Oms Order Id | Unique key generated by Solidus that identifies an order. |
| Order Rank By User | Allows to rank completed orders by completion date for a user. |
| Order Tags | List of tags associated to the order. |
| Order Tags Count | Number of tags associated to the order. |
| Order Referral Conversion Suspicious Reasons | A list of reasons explaining why the referral conversion is suspicious. |
| Order Referrer User Email | The email address of the customer identified with the referral. |
| Order Special Instructions | Any special shipping instructions that have been specified by the customer during checkout. |
| Order State | The current state of the order. |
| Order Store Id | Unique key generated by our models that uniquifies a store. |
| Order Store Name | The name of the store. |
| Order Store Oms Admin Url | The Admin URL of that OMS. |
| Order Store Oms Id | Unique key generated by Chord that uniquifies an OMS. |
| Order Store Oms Store Id | Unique key generated by our models that uniquifies a store. |
| Order Store Oms Type | The type of the OMS. |
| Order Store Id | Unique key generated by our models that uniquifies a store. |
| Order Store Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Order Store Url | The Storefront URL of of the store. |
| Order Subscription Customer Lifetime Month | Number of months between the current order's completion date and the user's first subscription order completion date. First orders have a value of 1. |
| Order Subscription Customer Lifetime Week | Number of weeks between the current order's completion date and the user's first subscription order completion date. First orders always have a value of 1. |
| Order User Referral Code | Unique key generated by Solidus that represents the user's referral code. |
| Order Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store. |
| Referral Conversion Rank By Referrer | Allows to rank a referral conversion by referrer. |
| Referral Id | Unique key generated by Chord to identify a unique referral identifier. |
| Referral Is Converted | Wether this represents a converted referral or not. |
| Referral Is First Conversion | Whether or not the referral was the referrer's first converted referral. |
| Referral Is First Non Suspicious Conversion | Whether or not the referral was the referrer's first non suspicious converted referral. |
| Referral Is Suspicious | Wether this represents a suspicous referral conversions or not. |
| Referral Non Suspicious Conversion Rank By Referrer | Allows ranking of non-suspicious referral conversion by the referrer. |
| Referral Oms Referral Conversion Id | Unique key generated by Solidus that identifies a referral conversion. |
| Referral Suspicious Reasons | A list of reasons explaining why the referral conversion is suspicious. |
| Referrer Currency | The currency for this referral identifier. |
| Referrer Email | The email address of the customer identified with the referral. |
| Referrer Id | Unique key generated by Chord to identify a unique referral identifier. |
| Referrer Oms Referral Identifier Id | Unique key generated by Solidus that identifies a referral identifier. |
| Referrer User Referral Code | Unique key generated by Solidus that represents the user's referral code. |
| Shipping Address Address1 | The street address of the customer. |
| Shipping Address Address2 | The optional second address of the customer. |
| Shipping Address Alternative Phone | The customer's alternative phone number. |
| Shipping Address City | The city where the address is. |
| Shipping Address Company | A company name. |
| Shipping Address Country Abbr | |
| Shipping Address Country Name | Full name of the country. |
| Shipping Address Firstname | First name of the customer. |
| Shipping Address Id | Unique key generated by Chord to identify a unique address. |
| Shipping Address Lastname | Last name of the customer. |
| Shipping Address Oms Address Id | Unique key generated by Solidus that identifies an address. |
| Shipping Address Phone | The customer's phone number. |
| Shipping Address State Abbr | |
| Shipping Address State Name | Full name of the state. |
| Shipping Address Zipcode | The postal code. |
| Subscription Completed Oms Order Ids | List of completed OMS order ids by a subscription. |
| Subscription Completed Order Count | Total amount of orders completed by a subscription. |
| Subscription Completed Order Ids | List of completed order ids by a subscription. |
| Subscription First Order Unique Product Basket | Array of unique product names ordered in the first order per subscription. |
| Subscription First Order Unique Variant Basket | Array of unique SKUs ordered in the first order per subscription. |
| Subscription Has Subscription Tags | Whether or not the subscription has tags. |
| Subscription Id | Unique key generated by Solidus that identifies a subscription. |
| Subscription Interval In Days | The number of days in the subscription interval. |
| Subscription Is Auto Redeemed | Whether the pre-paid subscription will be auto-redeemed or if an action is required by the recepient. |
| Subscription Is Gift | Whether or not the pre-paid subscription is a gift. |
| Subscription Is Recurring | Whether the pre-paid subscription is recurring. |
| Subscription Last Order Unique Product Basket | Array of unique product names ordered in the latest order per subscription. |
| Subscription Last Order Unique Variant Basket | Array of unique SKUs ordered in the latest order per subscription. |
| Subscription Oms Pre Paid Subscription Id | ID generated by ChordOMS to identify a unique pre-paid subscription. |
| Subscription Oms Subscription Id | Unique key generated by Solidus that identifies a subscription. |
| Subscription Pre Paid Subscription Id | Chord generated unique id for the pre-pay subscription. |
| Subscription State | The current state of the subscription, enhanced with values for \`paused\` if the subscription is active and paused. |
| Subscription Tags | The list of tags associated with a subscription. |
| Subscription Tags Count | The number of tags associated with a subscription. |
| Subscription Unique Product Basket | Array of unique product names ever ordered per subscription. |
| Subscription Unique Variant Basket | Array of unique SKUs ever ordered per subscription. |
| User Completed Oms Order Ids | List of completed OMS order ids by a user. |
| User Completed Order Ids | List of completed order ids by a user. |
| User Credit Category Basket | Array of credit categories (Gift Card, Reimbursement, Referral Credits, Prepaid Subscription, GMA) issued per user. |
| User Email | Email address of the user. |
| User First Completed Oms Order Id | OMS order id of the first order completed by a user. |
| User First Completed Order Id | Unique order id of the first order completed by a user. |
| User First Order Unique Ordered Products | Unique products ordered by the user in their first completed order. |
| User First Order Unique Ordered Skus | Unique SKUs ordered by the user in their first completed order. |
| User Has Ordered A La Carte | Whether or not the user has had at least one order that is not part of a subscription. |
| User Has Promo Applied In First Order | Whether or not the user has a promo applied to their first completed order. |
| User Has Subscription In First Order | Whether or not the user's first order is linked to a subscription. |
| User Id | Unique key generated by Chord to identify a unique user. |
| User Is Active Subscriber | Whether or not the user has an active subscription with at least one completed subscription order. An active subscription is one that is not cancelled or paused. |
| User Is Customer | Whether or not the user is a customer. |
| User Is New Customer | Whether or not the user is a new customer. |
| User Is Not Customer | Whether or not the user is not a customer. |
| User Is Returning Customer | Whether or not the user is a returning customer. |
| User Is Subscriber | Whether or not the user has completed at least one subscription order. |
| User Login | The login email address of the user. |
| User Name | Full name of the user. |
| User Number Of Completed A La Carte Orders | Total amount of orders completed by a user that are a la carte. |
| User Number Of Completed Subscription Orders | Total amount of orders completed by a user that was part of a subscription. |
| User Number Of Orders With Promos | The count of completed orders with a promo applied. |
| User Number Of Subscriptions | Total amount of subscriptions linked to a user. |
| User Oms User Id | Unique key generated by Solidus that identifies a user. |
| User Phone | Phone number of the user. |
| User Total Completed Order Count | Total amount of orders completed by a user. |
| User Unique Ordered Products | Unique products ordered by the user across all orders. |
| User Unique Ordered Skus | Unique SKUs ordered by the user across all orders. |
| Billing Address Created At (Universal) | Timestamp at which the address row was created - Universal Time Zone. |
| Billing Address Updated At (Universal) | Timestamp at which the address row was last updated - Universal Time Zone. |
| Order Approved At (Universal) | Reflects when the entity was approved in Solidus - Universal Time Zone. |
| Order Canceled At (Universal) | Reflects when the order was cancelled - Universal Time Zone. |
| Order Completed At (Central) | Reflects when the entity was moved to the 'completed' state - Cental Time Zone. |
| Order Completed At (Eastern) | Reflects when the entity was moved to the 'completed' state - Eastern Time Zone. |
| Order Completed At (Mountain) | Reflects when the entity was moved to the 'completed' state - Mountain Time Zone. |
| Order Completed At (Pacific) | Reflects when the entity was moved to the 'completed' state - Pacific Time Zone. |
| Order Completed At (Universal) | Reflects when the entity was moved to the 'completed' state - Universal Time Zone. |
| Order Created At (Central) | Reflects when the entity was first created in Solidus - Cental Time Zone. |
| Order Created At (Eastern) | Reflects when the entity was first created in Solidus - Eastern Time Zone. |
| Order Created At (Mountain) | Reflects when the entity was first created in Solidus - Mountain Time Zone. |
| Order Created At (Pacific) | Reflects when the entity was first created in Solidus - Pacific Time Zone. |
| Order Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Order First Fulfillment Fulfilled At (Universal) | Timestamp at which the first shipment for that order was shipped - Universal Time Zone. |
| Order Last Adjustment Refund At (Universal) | Timestamp of the last return adjustment for an order - Universal Time Zone. |
| Order Last Adjustment Replacement At (Universal) | Timestamp of the last replacement adjustment for an order - Universal Time Zone. |
| Order Last Fulfillment Fulfilled At (Universal) | Timestamp at which the last shipment for that order was shipped - Universal Time Zone. |
| Order Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| Referral Converted At (Universal) | Reflects when the referral entity was first converted in Solidus - Universal Time Zone. |
| Referral Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Referral Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| Referrer Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Referrer Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| Shipping Address Created At (Universal) | Timestamp at which the address row was created - Universal Time Zone. |
| Shipping Address Updated At (Universal) | Timestamp at which the address row was last updated - Universal Time Zone. |
| Subscription Actionable Date (Universal) | The date of the next subscription installment. This date is updated after each successful installment. Subscriptions in an inactive state will be null - Universal Time Zone. |
| Subscription Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Subscription First Order Completed At (Universal) | The timestamp of the subscription's first completed order - Universal Time Zone. |
| Subscription Last Order Completed At (Universal) | The timestamp of the subscription's last completed order - Universal Time Zone. |
| Subscription Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| User Created At (Universal) | Timestamp at which the users row was created - Universal Time Zone. |
| User Date Of Birth (Universal) | Date of birth of the user - Universal Time Zone. |
| User Deleted At (Universal) | Timestamp at which the user's account was deleted - Universal Time Zone. |
| User First Order Completed At (Universal) | The timestamp of the user's first completed order - Universal Time Zone. |
| User First Subscription Order Completed At (Universal) | The timestamp of the user's first completed subscription order, regardless of subsequent subscriptions - Universal Time Zone. |
| User Last Order Completed At (Universal) | The timestamp of the user's last completed order - Universal Time Zone. |
| User Last Sign In At (Universal) | The last sign in timestamp for the user - Universal Time Zone. |
| User Updated At (Universal) | Timestamp at which the users row was last updated - Universal Time Zone. |
| Average Additional Tax Total | Total additional taxes for an order. |
| Average Adjustment Fulfillment Tax Total | Total adjustment shipment taxes for an order. |
| Average Adjustment Fulfillment Total | Total shipment adjustments applied to an order. |
| Average Adjustment Other Charges Total | Total of included additional adjustment charges paid for an order. |
| Average Adjustment Other Credits Total | Total of credits issued for an order. |
| Average Adjustment Refund Total | Total of return dollars for an order. |
| Average Adjustment Replacement Total | Total of replacement dollars for an order. |
| Average Adjustment Rma Refund Total | Total of refund dollards associated to an order that was returned via the RMA functionality of the Chord OMS. |
| Average Adjustment Tax Total | Total adjustment taxes an order. |
| Average Adjustment Total | Total of adjustment applied for an order as on the order. |
| Average Applied Gift Card Total | Total of gift card dollars that were used as a payment method in the order |
| Average Commission Total | Commission for an order. |
| Average Fulfillment Total | Total shipment for an order. |
| Average Gross Revenue | Gross amount of revenue generated by the order including items and shipments totals. Gross revenue = total - included\_tax\_total + shipment\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Average Included Tax Total | Total included taxes for an order. |
| Average Item Total | Total price for the order before adjustments. |
| Average Net Revenue | Net revenue generated by the order's items after promotions. Net revenue = total - included\_tax\_total + shipment\_total + adjustment\_total - additional\_tax\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Average Pre Paid Purchase Total | The amount of the order that was purchased as a pre-payment; this could be a gift subscription, pre-pay subscription, or gift card. |
| Average Pre Paid Redemption Total | The amount of the order that was the redemption of a pre-payment; this could be the redemption of a gift subscription, pre-pay subscription, or gift card. |
| Average Promo Total | Promotions applied to an order. |
| Average Purchased Gift Card Total | Total of gift card dollars that were purchased in the order. |
| Average Reimbursement Credit Total | The amount of store credits owed back in an order |
| Average Tax Total | Total taxes for an order. |
| Average Total Price | Total to be paid by the customer for an order. |
| Average Transaction Total | Total paid by the customer for a completed order. |
| Additional Tax Total | Total additional taxes for an order. |
| Adjustment Fulfillment Tax Total | Total adjustment shipment taxes for an order. |
| Adjustment Fulfillment Total | Total shipment adjustments applied to an order. |
| Adjustment Other Charges Total | Total of included additional adjustment charges paid for an order. |
| Adjustment Other Credits Total | Total of credits issued for an order. |
| Adjustment Refund Total | Total of return dollars for an order. |
| Adjustment Replacement Total | Total of replacement dollars for an order. |
| Adjustment Rma Refund Total | Total of refund dollards associated to an order that was returned via the RMA functionality of the Chord OMS. |
| Adjustment Tax Total | Total adjustment taxes an order. |
| Adjustment Total | Total of adjustment applied for an order as on the order. |
| Applied Gift Card Total | Total of gift card dollars that were used as a payment method in the order |
| Commission Total | Commission for an order. |
| Fulfillment Total | Total shipment for an order. |
| Gross Revenue | Gross amount of revenue generated by the order including items and shipments totals. Gross revenue = total - included\_tax\_total + shipment\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Included Tax Total | Total included taxes for an order. |
| Item Total | Total price for the order before adjustments. |
| Net Revenue | Net revenue generated by the order's items after promotions. Net revenue = total - included\_tax\_total + shipment\_total + adjustment\_total - additional\_tax\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Pre Paid Purchase Total | The amount of the order that was purchased as a pre-payment; this could be a gift subscription, pre-pay subscription, or gift card. |
| Pre Paid Redemption Total | The amount of the order that was the redemption of a pre-payment; this could be the redemption of a gift subscription, pre-pay subscription, or gift card. |
| Total Price | Total to be paid by the customer for an order. |
| Promo Total | Promotions applied to an order. |
| Purchased Gift Card Total | Total of gift card dollars that were purchased in the order. |
| Reimbursement Credit Total | The amount of store credits owed back in an order |
| Tax Total | Total taxes for an order. |
| Transaction Total | Total paid by the customer for a completed order. |
### x\_fct\_trans\_sessions
| Name | Description |
| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Anonymous Completed Oms Order Ids | Array of OMS Order IDs associated to the anonymous\_id, as collected by order completed or checkout completed front-end events, over time. |
| Anonymous Completed Order Ids | Array of order IDs associated to the anonymous\_id, as collected by order completed or checkout completed front-end events, over time. |
| Anonymous Completed Order Numbers | Array of order numbers associated to the anonymous\_id, as collected by order completed or checkout completed front-end events, over time. |
| Anonymous Current Blended User Id | Unique id derived from the user\_id and the anonymous\_id. Whenever a customer has a user\_id, the user\_anonymous\_id will be constant for |
| Anonymous Current User Id | The current user\_id associated with the anonymous\_id. This unique user\_id is created by Segment's Identify call. A user\_id can be associated to many anonymous\_ids. |
| Anonymous Id | Unique id created by Chord for each anonymous visitor per store. |
| Anonymous Segment Anonymous Id | Id created by Segment for each anonymous visitor. This id gets created as soon as a customer's browser loads the analytics javascript widget. The anonymous\_id remains unchanged through the entire browsing session from a single device. Depending on configuration, two stores connected stores may have the same anonymous\_id. |
| Anonymous Unique User Ids | Array of user IDs mapped to an anonymous ID. |
| Attribution Point First Touch | The first session associated with the user prior to conversion receives 100% of the attribution, all other sessions recieve 0 points. Reflected with a value of 0 or 1. |
| Attribution Point Forty Twenty Forty | The first and last sessions associated with the user prior to conversion receive 40% of the attribution points each, the remaining middle-touch sessions receive an equal portion of the 20%; 0.4, 0.4, and 0.2/number of remaining sessions. |
| Attribution Point Id | Sessions for a user that occor prior to conversion, or first completed order. |
| Attribution Point Last Touch | The last session associated with the user prior to conversion receives 100% of the attribution, all other sessions recieve 0 points. Reflected with a value of 0 or 1. |
| Attribution Point Linear | All sessions for the user prior to conversion recieve an equal percentage of the attribution points; calculated as 1.0 / number of sessions |
| End Date Day Num Of Year | The number representing the day of the year. |
| End Date Id | Unique key that uniquify a date. |
| End Date Month Num Of Year | The month number of the year. |
| Landing Page Browser Locale | Locale of browser. |
| Landing Page Device | The device on which the event was sent from. |
| Landing Page Device Category | The device category of the device on which the event was sent from. There are multiple supported values for this column such as 'iPhone', |
| Landing Page Event Table Name | The properly formatted name of the table of the event. |
| Landing Page Event Text | The name of the event. |
| Landing Page Event Text Id | The slug of the event name, mapping to the page or track event table. |
| Landing Page Gclid | The Google Click ID. Google Click ID (GCLID) is a parameter passed in the URL with ad clicks, to identify the campaign and other attributes of the click associated with the ad for ad tracking and campaign attribution. |
| Landing Page Id | Unique key generated by Segment for each tracking or page event. |
| Landing Page Oms Id | Unique key generated by our models that uniquifies an OMS. |
| Landing Page Host | The host of the event's URL. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev` . This facilitates grouping events by host. |
| Landing Page Path | The page path part of the URL. A page path is the part of URL that comes after the hostname (domain) and before the query parameters, URL fragment, or port. (e.g. `/pages/contact-us/` for `https://chord.co/pages/contact-us/?ref=internal-banner`.) |
| Landing Page Query | The query string portion of the URL of the page. |
| Landing Page Referrer | The referrer of the page. The referrer is the webpage that sends visitors to the site using a link. In |
| Landing Page Title | The title/name of the page. |
| Landing Page Url | The URL of the page. |
| Landing Page Referrer Host | The host of the referrer. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev` . This facilitates grouping events by host. |
| Landing Page Segment User Id | The unique ID of the user. |
| Landing Page Store Id | Unique key generated by our models that uniquifies a store. |
| Landing Page Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Landing Page User Agent | The User agent of the device making the request. A User agent request header is a characteristic string that lets servers and |
| Landing Page User Id | Unique key generated by Chord to identify the user. |
| Landing Page Utm Campaign | The campaign name represented by the UTM tags. |
| Landing Page Utm Content | The campaign content represented by the UTM tags. |
| Landing Page Utm Medium | The campaign medium represented by the UTM tags. |
| Landing Page Utm Source | The campaign source represented by the UTM tags. |
| Landing Page Utm Term | The campaign term represented by the UTM tags. |
| Landing Page Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store |
| Last Page Browser Locale | Locale of browser. |
| Last Page Device | The device on which the event was sent from. |
| Last Page Device Category | The device category of the device on which the event was sent from. There are multiple supported values for this column such as 'iPhone', |
| Last Page Event Table Name | The properly formatted name of the table of the event. |
| Last Page Event Text | The name of the event. |
| Last Page Event Text Id | The slug of the event name, mapping to the page or track event table. |
| Last Page Gclid | The Google Click ID. Google Click ID (GCLID) is a parameter passed in the URL with ad clicks, to identify the campaign and other attributes of the click associated with the ad for ad tracking and campaign attribution. |
| Last Page Id | Unique key generated by Segment for each tracking or page event. |
| Last Page Oms Id | Unique key generated by our models that uniquifies an OMS. |
| Last Page Host | The host of the event's URL. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev`. This facilitates grouping events by host. |
| Last Page Path | The page path part of the URL. A page path is the part of URL that comes after the hostname (domain) and before the query parameters, URL fragment, or port. (e.g. `/pages/contact-us/` for `https://chord.co/pages/contact-us/?ref=internal-banner`.) |
| Last Page Query | The query string portion of the URL of the page. |
| Last Page Referrer | The referrer of the page. The referrer is the webpage that sends visitors to the site using a link. In |
| Last Page Title | The title/name of the page. |
| Last Page Url | The URL of the page. |
| Last Page Referrer Host | The host of the referrer. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev`. This facilitates grouping events by host. |
| Last Page Segment User Id | The unique ID of the user. |
| Last Page Store Id | Unique key generated by our models that uniquifies a store. |
| Last Page Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Last Page User Agent | The User agent of the device making the request. A User agent request header is a characteristic string that lets servers and |
| Last Page User Id | Unique key generated by Chord to identify the user. |
| Last Page Utm Campaign | The campaign name represented by the UTM tags. |
| Last Page Utm Content | The campaign content represented by the UTM tags. |
| Last Page Utm Medium | The campaign medium represented by the UTM tags. |
| Last Page Utm Source | The campaign source represented by the UTM tags. |
| Last Page Utm Term | The campaign term represented by the UTM tags. |
| Last Page Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store |
| Session Activity Count | Total count of activities, pave views and tracked events within the session. |
| Session Attribution Channel | The attribution channel for the first page event of the session. Sessions with an attribution of 'Unknown' indicates that there is no attributable data for that session. |
| Session Attribution Channel Paid Or Organic | Indicates if the session's first page attribution is paid or organic. Attribution is considered Organic if the attribution channel is 'Direct', 'Other', 'Organic Search', 'Organic Social', 'Email', or 'SMS'. |
| Session Attribution First Page Url Has Gclid | Indicates if the first page event of the session has a Google Click ID. |
| Session Attribution First Page Url Has Utm | Indicates if the first page event of the session has any utm information. |
| Session Attribution Has Referrer | Indicates if the first page event of the session has a referrer host. |
| Session Attribution Medium | The campaign medium represented by the UTM tags for the first page event of the session. |
| Session Attribution Source | The campaign source represented by the UTM tags for the first page event of the session. |
| Session Attribution Sub Channel | Sub-Channel is a granular level of attribution. |
| Session Completed Oms Order Ids | Array of OMS Order IDs associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Session Completed Order Ids | Array of order IDs associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Session Completed Order Numbers | Array of order numbers associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Session Days Since Last Session End | The days between the last session's end and the start of this session. |
| Session Device | The device on which the event was sent from. |
| Session Device Category | The device category of the device on which the event was sent from. There are multiple supported values for this column such as 'iPhone', |
| Session Duration In Seconds | Total seconds between start and end activities within the session. |
| Session Duration In Seconds Tiers | Total seconds between start and end activities within the session, aggregated into tiers: 0-9s, 10-29s, 30-59s, and 60s or more. |
| Session Has Order Completion | Flag for sessions with an order completed or checkout completed front-end events |
| Session Id | Unique ID for the session. |
| Session Number | Session number per anonymous id. |
| Session Unique Completed Order Count | Count of unique order ids associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Session Unique Completed Order Number Count | Count of unique order numbers associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Start Date Day Num Of Year | The number representing the day of the year. |
| Start Date Id | Unique key that uniquify a date. |
| Start Date Month Num Of Year | The month number of the year. |
| Store Id | Unique key generated by our models that uniquifies a store. |
| Store Name | The name of the store. |
| Store Oms Admin Url | The Admin URL of that OMS. |
| Store Oms Id | Unique key generated by Chord that uniquifies an OMS. |
| Store Oms Store Id | Unique key generated by our models that uniquifies a store. |
| Store Oms Type | The type of the OMS. |
| Store Id | Unique key generated by our models that uniquifies a store. |
| Store Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Store Url | The Storefront URL of of the store. |
| User Address 1 | The first line of the street address. |
| User Address 2 | The optional second line of the address. |
| User Address City | The city of the address. |
| User Address Country | The country of the address. |
| User Address Name | The full name of the customer, based on firstName and lastName. |
| User Address State | The region of the address, such as the province, state, or district. |
| User Address Zip | The postal code of the address. |
| User Completed Oms Order Ids | Array of OMS Order IDs associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| User Completed Order Ids | Array of order IDs associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| User Completed Order Numbers | Array of order numbers associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| User Email | The email associated with the user. |
| User Id | Unique ID per user. It is equal to either 1) a identified\_user\_id as identified by Segment in the Identify call, or 2) an anonynous\_id. |
| User Identified User Id | Unique ID per identified user. (See Segment's documentation on user\_id)\[ `https://segment.com/docs/connections/spec/identify/#user-id` ]. |
| User Ip | IP address associated with the user. |
| User Last Anonymous Id | Last seen anonymous\_id per user. An `anonymous_id` is a unique ID per anonymous visitor. (See Segment's documentation on anonymous\_id)\[ `https://segment.com/docs/connections/spec/identify/#anonymous-id` ]. |
| User Last Segment Anonymous Id | This column is not documented. |
| User Segment User Id | The unique ID of the user. |
| User Unique Anonymous Ids | Array of all seen anonymous\_ids per user. An `anonymous_id` is a unique ID per anonymous visitor. (See Segment's documentation on anonymous\_id)\[ `https://segment.com/docs/connections/spec/identify/#anonymous-id` ]. |
| User Unique Completed Order Count | Count of unique order ids associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| End Ts (Universal) | Last activity timestamp for a session - Universal Time Zone. |
| Landing Page Ts (Universal) | The timestamp calculated by Segment correcting clock skew - Universal Time Zone. |
| Last Page Ts (Universal) | The timestamp calculated by Segment correcting clock skew - Universal Time Zone. |
| Session End Ts (Universal) | Last activity timestamp for a session - Universal Time Zone. |
| Session Last Session End Ts (Universal) | The timestamp of the previous session's end per blended user id, if this is not the user's first session - Universal Time Zone. |
| Session Last Session Start Ts (Universal) | The timestamp of the previous session's start per blended user id, if this is not the user's first session - Universal Time Zone. |
| Session Start Ts (Central) | First activity timestamp for a session - Cental Time Zone. |
| Session Start Ts (Eastern) | First activity timestamp for a session - Eastern Time Zone. |
| Session Start Ts (Mountain) | First activity timestamp for a session - Mountain Time Zone. |
| Session Start Ts (Pacific) | First activity timestamp for a session - Pacific Time Zone. |
| Session Start Ts (Universal) | First activity timestamp for a session - Universal Time Zone. |
| Start Ts (Central) | First activity timestamp for a session - Cental Time Zone. |
| Start Ts (Eastern) | First activity timestamp for a session - Eastern Time Zone. |
| Start Ts (Mountain) | First activity timestamp for a session - Mountain Time Zone. |
| Start Ts (Pacific) | First activity timestamp for a session - Pacific Time Zone. |
| Start Ts (Universal) | First activity timestamp for a session - Universal Time Zone. |
| User Created At (Universal) | The timestamp when the user was created - Universal Time Zone. |
| User First Seen At (Universal) | The first time the user was seen on the site, identified as either anonymous ID or user ID - Universal Time Zone. |
### user\_completed\_order\_numbers
| Name | Description |
| ---------------------------- | ---------------------------- |
| User Completed Order Numbers | User completed order numbers |
[title] User Attribution on Chord
[path] Chord Data Platform/Data Models/Marketing Attribution/
:::hint{type="info"}
This is our original marketing attribution explore. It was previously called the ***Marketing Attribution Explore***.
:::
## Introduction
On Chord, user attribution is the process of determining which marketing channel, campaign, or touchpoint led to a specific purchase at the user level. **A brand should select this attribution Explore when they want to better analyze when a user became a customer (i.e. when someone made a purchase)**. It helps you understand what drove a customer to *convert*—whether that was an ad, an email, a discount code, or another action right before the sale.
Based on the specific attribution points selected (first-touch, last-touch, linear, or 40-20-40), Chord will attribute revenue metrics based on when the user converts (i.e. makes a purchase).
You can use Chord’s User Attribution Explore when:
- You're tracking customer acquisition or lifecycle journeys.
- You want to understand which sources or campaigns brought in high-value or loyal customers.
- You're segmenting customers by first touch or most recent meaningful engagement.
## Getting Started
1. Log into the Chord Commerce Data Platform.
2. Navigate to your **Analytics** page.
3. Click the **Explores** tab.
4. Select the **Marketing Attribution - User Attribution** item in the dropdown menu (see first image).
5. Navigate to the **User Attribution** Field list on the lefthand side to access the new **attribution point** dimensions (see second image).
6. Select an attribution point dimension applicable to your analysis.
7. Additionally, if you’d like to use different attribution measures, you can select attribution measures under the measures list on the lefthand navigation pane (see third image).
:::hint{type="info"}
For more information on the differences between **Dimensions **and **Measures**, click [here](https://docs.chord.co/glossary#CiE5u).
:::
[title] Receiving Data from Chord via Cloud Storage
[path] Chord Data Platform/Overview/
# Introduction
This guide provides step-by-step instructions for integrating external cloud storage services to Chord's data warehouse (Snowflake). We delegate authentication to Snowflake-managed identities, eliminating the need to manage credentials directly.
We recommend creating a specific bucket specifically to receive data.
Below you'll find instructions for connecting either AWS S3, Google Cloud Storage or Azure Blob Storage services to Chord's data warehouse (Snowflake).
# Configuring an integration for AWS S3
This sections describes how to configure secure access to data files stored in an AWS S3 bucket.
1. Create an IAM Policy that has the permissions required to access the bucket and write objects:
:::Paragraph{indent="3"}
a. Log into the AWS Management Console.
:::
:::Paragraph{indent="3"}
b. From the home dashboard, search for and select **IAM.**
:::
:::Paragraph{indent="3"}
c. From the left-hand navigation pane, select **Account settings.**
:::
:::Paragraph{indent="3"}
d. Under **Security Token Service (STS)** in the Endpoints list, find the **United States (N. Virginia)** (i.e., `us-east-1`) region. If the **STS status** is inactive, move the toggle to **Active**.
:::
:::Paragraph{indent="3"}
e. Select **Create Policy.**
:::
:::Paragraph{indent="3"}
f. For **Policy editor**, select **JSON.**
:::
:::Paragraph{indent="3"}
g. Add a policy document that will allow Chord to access the S3 bucket and folder. The following policy (in JSON format) provides Chord with the required permissions to write data using a single bucket and folder path. Copy and paste the text into the policy editor:
:::
:::CodeblockTabs{indent="3"}
```javascript
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:GetObject",
"s3:GetObjectVersion",
"s3:PutObject",
"s3:DeleteObject"
],
"Resource": "arn:aws:s3::://*"
},
{
"Effect": "Allow",
"Action": [
"s3:ListBucket",
"s3:GetBucketLocation"
],
"Resource": "arn:aws:s3:::",
"Condition": {
"StringLike": {
"s3:prefix": [
"/*"
]
}
}
}
]
}
```
:::
:::Paragraph{indent="3"}
h. Select **Next.**
:::
:::Paragraph{indent="3"}
i. Enter a **Policy name** and an optional Description.
:::
:::Paragraph{indent="3"}
j. Select **Create policy.**
:::
2. Create an IAM Role and attach the custom IAM role:
:::Paragraph{indent="3"}
a. From the left-hand navigation pane in the Identity and Access Management (IAM) Dashboard, select **Roles.**
:::
:::Paragraph{indent="3"}
b. Select **Create role.**
:::
:::Paragraph{indent="3"}
c. Select **AWS account** as the trusted entity type.
:::
:::Paragraph{indent="3"}
d. Select **Another AWS account.**
:::
:::Paragraph{indent="3"}
e. In the **Account ID** field, enter your own AWS account ID temporarily. Later, you will modify the trust relationship and grant access to Snowflake.
:::
:::Paragraph{indent="3"}
f. Select the **Require external ID **option. An external ID is used to grant access to your AWS resources (such as S3 buckets) to a third party like Snowflake. Enter a placeholder ID such as `0000`. In a later step, you will modify the trust relationship for your IAM role and specify the external ID that Chord will provide.
:::
:::Paragraph{indent="3"}
g. Select **Next.**
:::
:::Paragraph{indent="3"}
h. Select the IAM Policy you created in the previous step.
:::
:::Paragraph{indent="3"}
i. Select **Next.**
:::
:::Paragraph{indent="3"}
j. Enter a name and description for the role, then select **Create role**.You have now created an IAM policy, IAM role and attached the policy to the role.
:::
:::Paragraph{indent="3"}
k. On the role summary page, locate and record the **Role ARN** value. You will need to provide Chord this ARN to complete the next steps.
:::
3. Provide Chord the IAM Role ARN and bucket name. The full bucket name is a URL that will look like the following: `s3://my-cool-bucket/`.
4. Once your bucket name and IAM Role ARN is confirmed, Chord will provide an IAM User ARN and an AWS External ID
5. Grant the IAM User permissions to access bucket objects:
:::Paragraph{indent="3"}
a. Sign in to the AWS Management Console
:::
:::Paragraph{indent="3"}
b. Select **IAM**
:::
:::Paragraph{indent="3"}
c. From the left-hand navigation pane, select **Roles**
:::
:::Paragraph{indent="3"}
d. Select the IAM Role you created in the previous step
:::
:::Paragraph{indent="3"}
e. Select the **Trust relationships** tab
:::
:::Paragraph{indent="3"}
f. Select **Edit trust policy**
:::
:::Paragraph{indent="3"}
g. Modify the policy document with the values provided by Chord. This includes IAM User ARN and External ID.
:::
:::CodeblockTabs{indent="3"}
```javascript
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "",
"Effect": "Allow",
"Principal": {
"AWS": ""
},
"Action": "sts:AssumeRole",
"Condition": {
"StringEquals": {
"sts:ExternalId": ""
}
}
}
]
}
```
:::
:::Paragraph{indent="3"}
h. Select **Update policy** to save your changes.
:::
# Configuring an integration for Google Cloud Storage
This sections describes how to configure secure access to data files stored in a Google Cloud Storage bucket.
1. Provide Chord with your GCS `bucket` name. The bucket name is the name of the Cloud Storage bucket that stores your data files. The full bucket name is a URL that will look like the following: `gcs://my-cool-bucket/`.
2. Once your `bucket` name is confirmed, Chord will provide you a Cloud Storage service account name to be used in the following steps.
3. Create a custom role that has the permissions required to access the bucket and write objects:
:::Paragraph{indent="3"}
a. Sign in to the Google Cloud console as a project editor.
:::
:::Paragraph{indent="3"}
b. From the home dashboard, select **IAM & Admin** » **Roles**
:::
:::Paragraph{indent="3"}
c. Select **Create Role.**
:::
:::Paragraph{indent="3"}
d. Enter a **Title** and optional **Description** for the custom role.
:::
:::Paragraph{indent="3"}
e. Select **Add Permissions.**
:::
:::Paragraph{indent="3"}
f. Filter the list of permissions, and add the following from the list: `storage.buckets.get`, `storage.objects.get`, `storage.objects.list`, `storage.objects.create` and `storage.objects.delete`
:::
:::Paragraph{indent="3"}
g. Select **Add.**
:::
:::Paragraph{indent="3"}
h. Select **Create.**
:::
4. Assign the custom role to the Cloud Storage Service Account:
:::Paragraph{indent="3"}
a. Sign in to the Google Cloud console as a project editor.
:::
:::Paragraph{indent="3"}
b. From the home dashboard, select **Cloud Storage** » **Buckets**
:::
:::Paragraph{indent="3"}
c. Filter the list of buckets, and select the in-scope bucket.
:::
:::Paragraph{indent="3"}
d. Select **Permissions** » **View by principals**, then select **Grant access.**
:::
:::Paragraph{indent="3"}
e. Under **Add principals**, paste the name of the service account name provided by Chord.
:::
:::Paragraph{indent="3"}
f. Under **Assign roles**, select the custom IAM role that you created previously, then select **Save.**
:::
5. (Optional) Grant the Cloud Storage service account permissions on the Cloud Key Management Service cryptographic keys:
:::hint{type="info" indent="2"}
This step is required ***only if *** your GCS bucket is encrypted using a key stored in the Google Cloud Key Management Service (Cloud KMS).
:::
:::Paragraph{indent="3"}
a. Sign in to the Google Cloud console as a project editor.
:::
:::Paragraph{indent="3"}
b. From the home dashboard, search for and select **Security** » **Key Management.**
:::
:::Paragraph{indent="3"}
c. Select the key ring that is assigned to your GCS bucket.
:::
:::Paragraph{indent="3"}
d. Click **SHOW INFO PANEL** in the upper-right corner. The information panel for the key ring slides out.
:::
:::Paragraph{indent="3"}
e. Click the **ADD PRINCIPAL** button.
:::
:::Paragraph{indent="3"}
f. In the **New principals** field, search for the service account name provided by Chord.
:::
:::Paragraph{indent="3"}
g. From the **Select a role** dropdown, select the "Cloud KMS CrytoKey Encryptor/Decryptor role".
:::
:::Paragraph{indent="3"}
h. Click the **Save** button. The service account name is added to the **Cloud KMS CrytoKey Encryptor/Decryptor role** dropdown in the information panel.
:::
# Configuring an integration for Microsoft Azure Blob Storage
This sections describes how to configure secure access to data files stored in Microsoft Azure Blob Storage.
1. Provide Chord with your `tenant_id` and `container name`.
2. Once your `tenant_id` and `container name` are confirmed, Chord will provide a consent URL and app name.
3. In a web browser, navigate to the consent URL. The page displays a Microsoft permissions request page.
4. Click the **Accept** button. This action allows the Azure service principal created for Chord’s Snowflake account to be granted an access token on specified resources inside your tenant. Obtaining an access token succeeds only if you grant the service principal the appropriate permissions on the container (see the next step). The Microsoft permissions request page redirects to the Snowflake corporate site (snowflake.com).
5. Sign in to the Microsoft Azure portal.
6. Navigate to **Azure Services** » **Storage Accounts**. Click the name of the storage account you are granting the Snowflake service principal access to.
7. Click **Access Control (IAM)** » **Add role assignment**.
8. Select the desired role to grant to the Snowflake service principal: **Storage Blob Data Contributor grants read and write access**, allowing Snowflake to both load data from and unload data to the storage account.
9. Search for the Snowflake service principal. This is the identity in the app name property that we will provide.
10. Click the **Review + assign** button.
# Troubleshooting
:::hint{type="info"}
This document has been created for customer reference purposes. For the most up-to-date information, you may consult official Snowflake documentation:
- [AWS S3](https://docs.snowflake.com/en/user-guide/data-load-s3-config-storage-integration#configuring-secure-access-to-cloud-storage)
- [Google Cloud Storage](https://docs.snowflake.com/en/user-guide/data-load-gcs-config#step-3-grant-the-service-account-permissions-to-access-bucket-objects)
- [Microsoft Azure Blob Storage](https://docs.snowflake.com/en/user-guide/data-load-azure-config#step-2-grant-snowflake-access-to-the-storage-locations)
:::
# Recommended next steps
If you plan to use cloud storage integration to share data with Chord, we have some helpful recommendations for structuing data to faciliitate seemless data ingestion. See [Chord Data Source Ingestion Guidelines](docId\:XkTAjRAIlw5UnrQRmPAn9).
[title] Ads
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Salesforce/
### **x\_fct\_unions**
| Name | Description |
| --------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Account Name | The name of the ad account. |
| Account Source Account Id | The unique identifier of the ad account from the source dataset. |
| Account Updated At Date | The timestamp of when an ad account was last updated in the database - Universal Time Zone. |
| Account Updated At Month | The timestamp of when an ad account was last updated in the database - Universal Time Zone. |
| Account Updated At Quarter | The timestamp of when an ad account was last updated in the database - Universal Time Zone. |
| Account Updated At Time | The timestamp of when an ad account was last updated in the database - Universal Time Zone. |
| Account Updated At Week | The timestamp of when an ad account was last updated in the database - Universal Time Zone. |
| Account Updated At Year | The timestamp of when an ad account was last updated in the database - Universal Time Zone. |
| Ad Name | The name of the ad. |
| Ad Source Ad Id | The unique identifier of the ad from the source dataset. |
| Ad Status | The status of the ad. |
| Ad Updated At Date | The timestamp of when an ad was last updated in the database - Universal Time Zone. |
| Ad Updated At Month | The timestamp of when an ad was last updated in the database - Universal Time Zone. |
| Ad Updated At Quarter | The timestamp of when an ad was last updated in the database - Universal Time Zone. |
| Ad Updated At Time | The timestamp of when an ad was last updated in the database - Universal Time Zone. |
| Ad Updated At Week | The timestamp of when an ad was last updated in the database - Universal Time Zone. |
| Ad Updated At Year | The timestamp of when an ad was last updated in the database - Universal Time Zone. |
| Ad Group Name | The name of the ad group or ad set of the ad. |
| Ad Group Source Ad Group Id | The unique identifier of the ad group or ad set for the ad. |
| Ad Group Status | Status of the ad group or ad set. |
| Ad Group Updated At Date | The timestamp of when an ad group or ad set was last updated in the database - Universal Time Zone. |
| Ad Group Updated At Month | The timestamp of when an ad group or ad set was last updated in the database - Universal Time Zone. |
| Ad Group Updated At Quarter | The timestamp of when an ad group or ad set was last updated in the database - Universal Time Zone. |
| Ad Group Updated At Time | The timestamp of when an ad group or ad set was last updated in the database - Universal Time Zone. |
| Ad Group Updated At Week | The timestamp of when an ad group or ad set was last updated in the database - Universal Time Zone. |
| Ad Group Updated At Year | The timestamp of when an ad group or ad set was last updated in the database - Universal Time Zone. |
| Campaign Advertising Channel Type | The type of advertising channel being used by the campaign. |
| Campaign End Date Date | The date when the ad campaign ends - Universal Time Zone. |
| Campaign End Date Month | The date when the ad campaign ends - Universal Time Zone. |
| Campaign End Date Quarter | The date when the ad campaign ends - Universal Time Zone. |
| Campaign End Date Time | The date when the ad campaign ends - Universal Time Zone. |
| Campaign End Date Week | The date when the ad campaign ends - Universal Time Zone. |
| Campaign End Date Year | The date when the ad campaign ends - Universal Time Zone. |
| Campaign Name | The name of the ad campaign. |
| Campaign Source Campaign Id | The unique identifier of the ad campaign from the source dataset. |
| Campaign Start Date Date | The date when the ad campaign starts - Universal Time Zone. |
| Campaign Start Date Month | The date when the ad campaign starts - Universal Time Zone. |
| Campaign Start Date Quarter | The date when the ad campaign starts - Universal Time Zone. |
| Campaign Start Date Time | The date when the ad campaign starts - Universal Time Zone. |
| Campaign Start Date Week | The date when the ad campaign starts - Universal Time Zone. |
| Campaign Start Date Year | The date when the ad campaign starts - Universal Time Zone. |
| Campaign Status | The status of the ad campaign. |
| Campaign Updated At Date | The timestamp of when an ad campaign was last updated in the database - Universal Time Zone. |
| Campaign Updated At Month | The timestamp of when an ad campaign was last updated in the database - Universal Time Zone. |
| Campaign Updated At Quarter | The timestamp of when an ad campaign was last updated in the database - Universal Time Zone. |
| Campaign Updated At Time | The timestamp of when an ad campaign was last updated in the database - Universal Time Zone. |
| Campaign Updated At Week | The timestamp of when an ad campaign was last updated in the database - Universal Time Zone. |
| Campaign Updated At Year | The timestamp of when an ad campaign was last updated in the database - Universal Time Zone. |
| Insight Ad Network Type | The network type used across the account. This field is native to Google and YouTube and fileld with the ad source for other sources. |
| Insight Date Date | The date of the insight - Universal Time Zone. |
| Insight Date Month | The date of the insight - Universal Time Zone. |
| Insight Date Quarter | The date of the insight - Universal Time Zone. |
| Insight Date Time | The date of the insight - Universal Time Zone. |
| Insight Date Week | The date of the insight - Universal Time Zone. |
| Insight Date Year | The date of the insight - Universal Time Zone. |
| Source | The source of the Ad dataset - Google, Facebook, Tiktok, etc. |
| Average Clicks | The number of paid and earned clicks that occurred on the day of the record. |
| Average Impressions | The number of paid and earned impressions - the number of times an ad appeared on the page - that occurred on the day of the record. |
| Average Link Clicks | The number of link clicks on the ad's text, media or call-to-action that link to destinations or experiences specified by the advertiser. This metric excludes clicks on content or links in the comments section of a post. Currently, only Facebook Ads sourced insights surface this data. |
| Average Spend | The estimated total amount of spend that occurred on the day of the record. |
| Total Clicks | The number of paid and earned clicks that occurred on the day of the record. |
| Total Impressions | The number of paid and earned impressions - the number of times an ad appeared on the page - that occurred on the day of the record. |
| Total Link Clicks | The number of link clicks on the ad's text, media or call-to-action that link to destinations or experiences specified by the advertiser. This metric excludes clicks on content or links in the comments section of a post. Currently, only Facebook Ads sourced insights surface this data. |
| Total Spend | The estimated total amount of spend that occurred on the day of the record. |
[title] Subscription events
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Chord OMS/
### **x\_fct\_trans\_subscription\_events**
| Name | Description |
| ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Subscription Completed Oms Order Ids | List of completed OMS order ids by a subscription. |
| Subscription Completed Order Count | Total amount of orders completed by a subscription. |
| Subscription Completed Order Ids | List of completed order ids by a subscription. |
| Subscription Event Type | The type of the subscription event. |
| Subscription Event Id | Unique key generated by Chord to identify a unique subscription event. |
| Subscription Event Oms Subscription Event Id | Unique key generated by Solidus that identifies a subscription event. |
| Subscription Event Oms Subscription Id | Unique key generated by Solidus that identifies a subscription. |
| Subscription Event Unique Product Basket | Array of products per subscription when an event is triggered. |
| Subscription Event Unique Variant Basket | Array of SKUs per subscription when an event is triggered. |
| Subscription First Order Unique Product Basket | Array of unique product names ordered in the first order per subscription. |
| Subscription First Order Unique Variant Basket | Array of unique SKUs ordered in the first order per subscription. |
| Subscription Has Subscription Tags | Whether or not the subscription has tags. |
| Subscription Id | Unique key generated by Solidus that identifies a subscription. |
| Subscription Interval In Days | The number of days in the subscription interval. |
| Subscription Is Auto Redeemed | Whether the pre-paid subscription will be auto-redeemed or if an action is required by the recepient. |
| Subscription Is Gift | Whether or not the pre-paid subscription is a gift. |
| Subscription Is Recurring | Whether the pre-paid subscription is recurring. |
| Subscription Last Order Unique Product Basket | Array of unique product names ordered in the latest order per subscription. |
| Subscription Last Order Unique Variant Basket | Array of unique SKUs ordered in the latest order per subscription. |
| Subscription Oms Pre Paid Subscription Id | ID generated by ChordOMS to identify a unique pre-paid subscription. |
| Subscription Oms Subscription Id | Unique key generated by Solidus that identifies a subscription. |
| Subscription Pre Paid Subscription Id | Chord generated unique id for the pre-pay subscription. |
| Subscription State | The current state of the subscription, enhanced with values for \`paused\` if the subscription is active and paused. |
| Subscription Store Id | Unique key generated by our models that uniquifies a store. |
| Subscription Store Name | The name of the store. |
| Subscription Store Oms Admin Url | The Admin URL of that OMS. |
| Subscription Store Oms Id | Unique key generated by Chord that uniquifies an OMS. |
| Subscription Store Oms Store Id | Unique key generated by our models that uniquifies a store. |
| Subscription Store Oms Type | The type of the OMS. |
| Subscription Store Id | Unique key generated by our models that uniquifies a store. |
| Subscription Store Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Subscription Store Url | The Storefront URL of of the store. |
| Subscription Tags | The list of tags associated with a subscription. |
| Subscription Tags Count | The number of tags associated with a subscription. |
| Subscription Unique Product Basket | Array of unique product names ever ordered per subscription. |
| Subscription Unique Variant Basket | Array of unique SKUs ever ordered per subscription. |
| User Completed Oms Order Ids | List of completed OMS order ids by a user. |
| User Completed Order Ids | List of completed order ids by a user. |
| User Credit Category Basket | Array of credit categories (Gift Card, Reimbursement, Referral Credits, Prepaid Subscription, GMA) issued per user. |
| User Email | Email address of the user. |
| User First Completed Oms Order Id | OMS order id of the first order completed by a user. |
| User First Completed Order Id | Unique order id of the first order completed by a user. |
| User First Order Unique Ordered Products | Unique products ordered by the user in their first completed order. |
| User First Order Unique Ordered Skus | Unique SKUs ordered by the user in their first completed order. |
| User Has Ordered A La Carte | Whether or not the user has had at least one order that is not part of a subscription. |
| User Has Promo Applied In First Order | Whether or not the user has a promo applied to their first completed order. |
| User Has Subscription In First Order | Whether or not the user's first order is linked to a subscription. |
| User Id | Unique key generated by Chord to identify a unique user. |
| User Is Active Subscriber | Whether or not the user has an active subscription with at least one completed subscription order. An active subscription is one that is not cancelled or paused. |
| User Is Customer | Whether or not the user is a customer. |
| User Is New Customer | Whether or not the user is a new customer. |
| User Is Not Customer | Whether or not the user is not a customer. |
| User Is Returning Customer | Whether or not the user is a returning customer. |
| User Is Subscriber | Whether or not the user has completed at least one subscription order. |
| User Login | The login email address of the user. |
| User Name | Full name of the user. |
| User Number Of Completed A La Carte Orders | Total amount of orders completed by a user that are a la carte. |
| User Number Of Completed Subscription Orders | Total amount of orders completed by a user that was part of a subscription. |
| User Number Of Orders With Promos | The count of completed orders with a promo applied. |
| User Number Of Subscriptions | Total amount of subscriptions linked to a user. |
| User Oms User Id | Unique key generated by Solidus that identifies a user. |
| User Phone | Phone number of the user. |
| User Total Completed Order Count | Total amount of orders completed by a user. |
| User Unique Ordered Products | Unique products ordered by the user across all orders. |
| User Unique Ordered Skus | Unique SKUs ordered by the user across all orders. |
| Subscription Actionable Date (Universal) | The date of the next subscription installment. This date is updated after each successful installment. Subscriptions in an inactive state will be null - Universal Time Zone. |
| Subscription Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Subscription Event Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Subscription Event Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| Subscription First Order Completed At (Universal) | The timestamp of the subscription's first completed order - Universal Time Zone. |
| Subscription Last Order Completed At (Universal) | The timestamp of the subscription's last completed order - Universal Time Zone. |
| Subscription Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| User Created At (Universal) | Timestamp at which the users row was created - Universal Time Zone. |
| User Date Of Birth (Universal) | Date of birth of the user - Universal Time Zone. |
| User Deleted At (Universal) | Timestamp at which the user's account was deleted - Universal Time Zone. |
| User First Order Completed At (Universal) | The timestamp of the user's first completed order - Universal Time Zone. |
| User First Subscription Order Completed At (Universal) | The timestamp of the user's first completed subscription order, regardless of subsequent subscriptions - Universal Time Zone. |
| User Last Order Completed At (Universal) | The timestamp of the user's last completed order - Universal Time Zone. |
| User Last Sign In At (Universal) | The last sign in timestamp for the user - Universal Time Zone. |
| User Updated At (Universal) | Timestamp at which the users row was last updated - Universal Time Zone. |
### **subscription\_event\_unique\_product\_basket**
| Name | Description |
| --------------------- | -------------------------------------------------------- |
| Unique Product Basket | Unique product basket at the time of subscription event. |
[title] Salesforce Marketing Cloud (SFMC)
[path] Chord Data Platform/Data Activations/Data Activations/Destination Set-up Notes/
*This page describes how to connect Salesforce Marketing Cloud (SFMC) as a Data Activation*
## Getting Started
In this guide, we will show you how to connect Salesforce Marketing Cloud to Chord Data Activations and create your first sync.
:::hint{type="warning"}
This process involves several steps - please set aside 15-30 minutes to complete it. Note that you may be on an older or newer version of Marketing Cloud which has slightly different screens than the ones pictured below. Marketing Cloud configuration can be complex, so if you have any questions please contact us via ***help\@chord.co ***and we'll help you tailor these instructions to your needs.
:::
### 1. Create and Configure a Server-to-Server Installed Package
Sign in to Salesforce Marketing Cloud and enter "Setup"
Navigate to "Apps > Installed Packages". Click "New" to create a new package. Create an app called "Chord" and provide an optional description, then click "Save"
Click "Add Component" and choose "API Integration"
Choose "Server-to-Server" as the OAuth Integration Type
In "Set Server-to-Server Properties", given the new component the following permissions by checking the appropriate boxes:
- Automation > **Automations: Read, Write, Execute**
- Contacts > **Audiences: Read, Write**
- Contacts > **List and Subscribers: Read, Write**
- Data > **Data Extensions: Read, Write**
- Data > **File Locations: Read, Write**
- Journeys > **Journeys: Read, Write**
Click "Save" to continue. You should see a new Component in your package - verify that it has the correct permissions (in the Scope section) by comparing to the image below.
Copy the **Client Id**, **Client Secret**, and **Authentication Base URI** from this page - you will need to provide these values to Chord Data Activations in Step 3.
### 2. Create an SFTP Account in Salesforce Marketing Cloud
Chord Data Activations uses the ExactTarget Enhanced FTP server to upload large data files to your Salesforce Marketing Cloud instance and prepare them for import. In this step, you'll ensure there is a File Location for Chord to upload the data, and create a new user account on your FTP server that Chord can use to sign in.
**File Location**
In Salesforce Marketing Cloud Setup, navigate to "Data Management > File Locations". If you have an Enhanced FTP location with an external key of "ExactTarget Enhanced FTP", then no action is required. If you do not see this File Location, click "Create" to generate a new location with the following configurations:
- An "External Key" value of **ExactTarget Enhanced FTP**
- A "Location Type" of **Enhanced FTP Site Import Directory**
**FTP User**
Still in Salesforce Marketing Cloud Setup, navigate to "Data Management > FTP Accounts" and click "Add FTP User".
For the email address, type in **help\@chord.co** and give the user a strong, random password. You do not need to write down or memorize this password - Chord does not require it, and in step 4 we will replace it with an SSH key. Make sure to give the Chord user "Full" access, and do not specify any IPs in the "Allowlist IPs" list. Click Next.
There's nothing to do yet on the next screen - we'll set up SSH Keys later.
Select the Root folder as the Home Folder for your user. Click "Save" to create the user.
Select the Root folder as the Home Folder
Salesforce Marketing Cloud will create the user, which may take a few seconds. Copy the **FTP Username** that was assigned to the user, which you'll need in Step 3.
### 3. Configure Chord with Your Connection Information
Go to Chord Data Activation Destinations, click **New Destination** and choose **Salesforce Marketing Cloud**.
In the dialog, fill out the data you gathered in steps 2 and 3:
- Name: A descriptive name of your choosing. If you have more than one Salesforce Marketing Cloud connection, you can use this field to help you keep track them
- Endpoint URL: Fill in the **Authentication Base URI** from Step 1
- Client ID and Client Secret: Fill in the **Client ID** and **Client Secret** from Step 1
- SFTP User: Fill in the **FTP Username** from Step 2(Optional) **Business Unit MID**: If you would like to create a connection for a business unit other than your primary SFMC account, you can provide a Business Unit MID. This can be found in the SFMC top navigation menu:
- Include Shared Data Extensions?: If you would like Chord to access shared data extensions, check this box. This has performance implications (see below for more details).
- In order to enable Chord support for business units, you will also need to turn on business unit app integration in your SFMC instance under `Setup` > `Apps` > `Installed Packages` > `Chord` > `Access` > `Enable Integration` :
Click **Save Connection**.
Chord will show your new Salesforce Marketing Cloud connection in its connections list
### 4. Upload Chord's SSH Public Key to Marketing Cloud
The final step is to configure Marketing Cloud to accept Chord's SSH public key for FTP access, instead of using a password. Still in Chord, click the button labeled "Click to Download" next to the "SFTP Public Key". This will download a file called "census.pub" to your computer - make a note of where it was saved.
Return to Salesforce Marketing Cloud Setup and navigate to "Data Management" > "Key Management". Click "Create".
- For "Key Type", choose "SSH"
- For "Name", type "Chord Public Key"
- For "External Key", type "chord-public-key"
- Check the "Public Key" checkbox
- Click "Browse" next to the "Key (required)" field and find the "census.pub" file you previously downloaded.
- Click "Save"
Now we'll associate the key with the Chord user. Navigate to "Data Management" > "FTP Accounts". Choose the "help\@chord.co" user and click the small arrow next to their name (you may need to scroll to the right. Choose "SSH Keys" from the drop-down menu.
Click in the "Search SSH Keys" box and find "Chord Public Key" and select it. Change the "Authentication Options" to "SSH Key" and click "Save". In a few seconds, Salesforce Marketing Cloud will finish configuring the SSH key (you can click the refresh icon at the top right to see the activity log go from "Pending" to "Success".
You're ready to start using Chord Data Activations to load data from your warehouse to Salesforce Marketing Cloud!
## Supported Objects and Behaviors
| **Object Name** | **Supported?** | **Sync Keys** | **Behaviors** |
| --------------------- | -------------- | ----------------- | -------------------------------------- |
| Data Extension | ✅ | Unique Identifier | Update or Create, Update Only, Replace |
| Contact | ✅ | Contact Key | Update or Create |
| API-Triggered Journey | ✅ | Contact Key | Update or Create, Mirror |
## 🏗️ Working With Data Extensions
Data Extensions are a fundamental component of Salesforce Marketing Cloud and are used in various capacities, including email personalization, segmentation, and reporting. They're unique in that they combine the common marketing automation concepts of segmentation and custom/relational data together into a single mechanism.
Chord allows you to sync data to existing data extensions, create new ones, and add fields to existing ones as well.
### Creating a data extension
You can select any existing data extension as a destination for a sync. You can also create a new data extension when setting up a Chord sync.
1. Click New Object
2. Provide a name for your data extension
3. Optionally, you can provide a different name for the identifier. By default, we'll use **ID**.
:::hint{type="info"}
You can also have Chord create the data extension within a subfolder by providing it in the data extension name. The subfolder must already exist, Chord won't automatically create it. The subfolder will be relative to any configured root folder (see below).
:::
### Adding new properties
Whether you're working with a brand new data extension or an existing one, you can always add more properties to a data extension. Within the Mappings section, either the **Add Mapping** or **Generate Mappings** allow you to add new properties to the data extension that will be created next time the sync is run.
### Setting a root folder
Some Salesforce Marketing Cloud installations have a very large number of data extensions. Chord allows specify a specific folder to use as the root or base folder. Only data extensions within this folder or its subfolders will be shown in Chord and new data extensions will be created in this folder.
- Visit the Destinations page and find your Salesforce Marketing Cloud connection.
- Click **Edit**.
- Set the Folder Path value to match your desired folder.
- Click **Save Connection**.
### Shared Data Extensions
In addition to Data Extentions in your specified root folder, you can also have Chord look for shared data extensions. For organizations with thousands of data extensions (regardless of whether they're shared or not), this can make the process of scanning for all existing extensions very slow. This slowness will show up when setting up new Chord connections or creating a new data extension. If you're experiencing slow performance, you can disable this feature by unchecking the "Include Shared Data Extensions?" checkbox in the Salesforce Marketing Cloud connection settings.
## Advanced Configuration
By default, Chord uses Salesforce Marketing Cloud's bulk upload mechanism which is powered by SFTP. This is the recommended mechanism for most syncs. However, for small data volumes, it may be preferred to send updates individually via Salesforce Marketing Cloud's SOAP API for faster processing. If your syncs must be processed with as low latency as possible and you have a relatively small number of changes, you can disable the standard SFTP method of syncing.
[title] Marketing Attribution
[path] Chord Data Platform/Data Models/
# Introduction
Marketing attribution is the process of figuring out which marketing touchpoints—like ads, email campaigns, or social media posts —contributed to a customer taking a specific action, such as making a purchase. Essentially, marketing attribution is a critical piece of the toolkit for connecting customer actions (like ad clicks and email opens) to customer outcomes (like revenue and retention).
Think of it as giving credit where credit is due: if a customer sees a Facebook ad, then opens an email, and finally clicks a Google search ad before buying, attribution helps determine how much each of those steps mattered in the path to the customer’s purchase. It’s foundational for making smarter, data-backed decisions that move the needle for your business.
# Chord’s Methodology
While understanding marketing attribution helps you spend smarter and grow faster, it can also be tough to analyze because people are unpredictable, their purchase journeys are messy, and your tools don’t always talk to each other cleanly.
Chord makes attribution not only possible, but practical—giving you the tools to go from reactive reporting to proactive growth strategy. It's built to make analysts like you more confident, efficient, and impactful.
Below you will find additional information on Chord’s methodology behind marketing attribution.
## User Stitching
User stitching is the identity resolution process of assigning an anonymous ID, or many anonymous IDs, to a user ID for all events recorded for a given user. This is becoming increasingly challenging in a world where users navigate websites from various devices and across multiple sessions, both before and after each purchase.
Once user information, such as user ID or email, is known for a given touchpoint, the user can be assigned to the anonymous ID throughout time to understand all of the events and sessions before and after purchase(s). This process will be repeated for all known anonymous IDs and then aggregated to have one or many anonymous IDs to one user ID combination for a user's history.
Partitioning by user\_id provides a more accurate attribution and allows a better view of users across various devices and sessions.
## Attribution Points
There are many different types of attribution methodologies that marketers can leverage. Chord supports four different attribution points that you can use as part of your analysis.
Note: Which attribution point system you use will depend on which touchpoint your business considers to be the most important.
The attribution point systems are:
- **First-Touch:** The first session gets 100% of the attribution points.
- Tip: If you’re focused on reporting on first-touch attribution, you will want to leverage this attribution point system.
- **Last-Touch:** The last session gets 100% of the attribution points.
- **Linear:** All sessions get assigned an equal portion of the attribution points.
- Tip: If you’re focused on multi-touch attribution and each touchpoint is valuable to your analysis, leverage this point system to assign equal weight to all of your touchpoints.
- **40-20-40 (Forty-Twenty-Forty):** The first and last sessions each get assigned 40% of the attribution points, and the sessions in-between get an equal portion of the remaining 20%.
- Note: For users with only one session, that session gets all the points. If a user has two sessions, there’s a 50/50 split between the sessions.
Here’s an example of how these attribution points can be used in your analysis for a single customer:
### Further examples
Brands will be interested in first-touch and multi-touch attribution. Here are some examples that may help illustrate the differences:
**First-Touch Attribution**
- **What it does**: Gives 100% of the credit to the *first* marketing interaction that brought a user to your brand.
- **Focus**: *Customer acquisition.*
- **Example**: If someone saw a TikTok ad, then later clicked an email and made a purchase, first-touch attribution credits the TikTok ad.
**Multi-Touch Attribution**
- **What it does**: Distributes credit across *multiple touchpoints* a customer interacts with before converting.
- **Focus**: *The entire journey.*
- **Example**: That same customer’s TikTok ad, email click, and final purchase via a paid search ad might each get a portion of the credit (based on the attribution point you choose).
## Channel Mapping
Chord assigns a referring channel category to each session.
:::hint{type="info"}
Note that we extract sources and mediums from Chord's eventing, specifically the landing page UTM parameters. For sessions with no UTMs, we infer the source and medium from the referring URL whenever possible.
:::
We are able to assign all sessions to one of the following categories when mapping source-medium pairs with channels:
- **Paid search:** Traffic driven by paid ads on search engines (like Google Ads or Bing Ads). This includes search results labeled as “sponsored” or “ad.”
- **Organic search:** Traffic that comes from unpaid search engine results. These are links users click after typing a query, without seeing or clicking an ad.
- **Paid social:** Traffic from paid ads on social platforms like Facebook, Instagram, TikTok, Pinterest, or Snapchat.
- **Organic social:** Traffic from unpaid posts, shares, or profile links on social media platforms.
- **Email:** Traffic from marketing emails sent to your list—newsletters, promotions, post-purchase messages, etc.
- **SMS:** Traffic from text message marketing—includes promotions, order updates with links, or personalized offers sent via SMS.
- **Direct:** Traffic from users who type your URL directly into their browser or access your site via a bookmark.
- **Affiliate:** Traffic from third-party websites promoting your products in exchange for a commission on referred sales.
- **Other:** A mapping for which the combinations of variables (source, medium, GCLID, referrer) have at least one value but is unknown as to which channel this combination should be mapped.
Here’s an example of an aggregated channel-level view of multi-touch attribution:
While Chord assigns a default channel mapping, customers can choose to create their own channel mappings through Chord's Amplifications feature to override Chord's default logic.
# User Attribution vs. Order Attribution on Chord
Chord provides two different models for you to start digging into your rich attribution data. One focuses on analysis at the User (customer) level and the other centers around Order-level data. Read on for additional information about each of these models.
## User Attribution
:::hint{type="info"}
**Note:** The **Marketing Attribution - User Attribution Explore** was previously called **Marketing Attribution Explore**.
:::
- **What it does**: We attribute the revenue metrics based on when a user converts (i.e. makes a purchase).
- For more information, view our [User Attribution documentation](https://docs.chord.co/user-attribution-on-chord).
## Order Attribution
:::hint{type="info"}
**Note: **The **Marketing Attribution - Order Attribution Explore** is a NEW attribution Explore.
:::
- **What it does**: We assign an attribution value based on every session before a purchase. The key difference here us that we identify the session when the user makes their first purchase and then we repeat the attribution exercise with every session thereafter.
- For more information, view our [Order Attribution documentation](https://docs.chord.co/order-attribution-on-chord).
## User vs. Order Attribution Comparison
Here’s an example highlighting the differences in methodology for the two Explores:
[title] Subscriptions
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Chord OMS/
### x\_fct\_trans\_subscriptions
| Name | Description |
| ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Billing Address Address1 | The street address of the customer. |
| Billing Address Address2 | The optional second address of the customer. |
| Billing Address Alternative Phone | The customer's alternative phone number. |
| Billing Address City | The city where the address is. |
| Billing Address Company | |
| Billing Address Country Abbr | A company name. |
| Billing Address Country Name | Full name of the country. |
| Billing Address Firstname | First name of the customer. |
| Billing Address Id | Unique key generated by Chord to identify a unique address. |
| Billing Address Lastname | Last name of the customer. |
| Billing Address Oms Address Id | Unique key generated by Solidus that identifies an address. |
| Billing Address Phone | The customer's phone number. |
| Billing Address State Abbr | |
| Billing Address State Name | Full name of the state. |
| Billing Address Zipcode | The postal code. |
| Shipping Address Address1 | The street address of the customer. |
| Shipping Address Address2 | The optional second address of the customer. |
| Shipping Address Alternative Phone | The customer's alternative phone number. |
| Shipping Address City | The city where the address is. |
| Shipping Address Company | A company name. |
| Shipping Address Country Abbr | |
| Shipping Address Country Name | Full name of the country. |
| Shipping Address Firstname | First name of the customer. |
| Shipping Address Id | Unique key generated by Chord to identify a unique address. |
| Shipping Address Lastname | Last name of the customer. |
| Shipping Address Oms Address Id | Unique key generated by Solidus that identifies an address. |
| Shipping Address Phone | The customer's phone number. |
| Shipping Address State Abbr | |
| Shipping Address State Name | Full name of the state. |
| Shipping Address Zipcode | The postal code. |
| Subscription Completed Oms Order Ids | List of completed OMS order ids by a subscription. |
| Subscription Completed Order Count | Total amount of orders completed by a subscription. |
| Subscription Completed Order Ids | List of completed order ids by a subscription. |
| Subscription First Order Unique Product Basket | Array of unique product names ordered in the first order per subscription. |
| Subscription First Order Unique Variant Basket | Array of unique SKUs ordered in the first order per subscription. |
| Subscription Has Subscription Tags | Whether or not the subscription has tags. |
| Subscription Id | Unique key generated by Solidus that identifies a subscription. |
| Subscription Interval In Days | The number of days in the subscription interval. |
| Subscription Is Auto Redeemed | Whether the pre-paid subscription will be auto-redeemed or if an action is required by the recepient. |
| Subscription Is Gift | Whether or not the pre-paid subscription is a gift. |
| Subscription Is Recurring | Whether the pre-paid subscription is recurring. |
| Subscription Last Order Unique Product Basket | Array of unique product names ordered in the latest order per subscription. |
| Subscription Last Order Unique Variant Basket | Array of unique SKUs ordered in the latest order per subscription. |
| Subscription Oms Pre Paid Subscription Id | ID generated by ChordOMS to identify a unique pre-paid subscription. |
| Subscription Oms Subscription Id | Unique key generated by Solidus that identifies a subscription. |
| Subscription Pre Paid Subscription Id | Chord generated unique id for the pre-pay subscription. |
| Subscription State | The current state of the subscription, enhanced with values for \`paused\` if the subscription is active and paused. |
| Subscription Store Id | Unique key generated by our models that uniquifies a store. |
| Subscription Store Name | The name of the store. |
| Subscription Store Oms Admin Url | The Admin URL of that OMS. |
| Subscription Store Oms Id | Unique key generated by Chord that uniquifies an OMS. |
| Subscription Store Oms Store Id | Unique key generated by our models that uniquifies a store. |
| Subscription Store Oms Type | The type of the OMS. |
| Subscription Store Id | Unique key generated by our models that uniquifies a store. |
| Subscription Store Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Subscription Store Url | The Storefront URL of of the store. |
| Subscription Tags | The list of tags associated with a subscription. |
| Subscription Tags Count | The number of tags associated with a subscription. |
| Subscription Unique Product Basket | Array of unique product names ever ordered per subscription. |
| Subscription Unique Variant Basket | Array of unique SKUs ever ordered per subscription. |
| User Completed Oms Order Ids | List of completed OMS order ids by a user. |
| User Completed Order Ids | List of completed order ids by a user. |
| User Credit Category Basket | Array of credit categories (Gift Card, Reimbursement, Referral Credits, Prepaid Subscription, GMA) issued per user. |
| User Email | Email address of the user. |
| User First Completed Oms Order Id | OMS order id of the first order completed by a user. |
| User First Completed Order Id | Unique order id of the first order completed by a user. |
| User First Order Unique Ordered Products | Unique products ordered by the user in their first completed order. |
| User First Order Unique Ordered Skus | Unique SKUs ordered by the user in their first completed order. |
| User Has Ordered A La Carte | Whether or not the user has had at least one order that is not part of a subscription. |
| User Has Promo Applied In First Order | Whether or not the user has a promo applied to their first completed order. |
| User Has Subscription In First Order | Whether or not the user's first order is linked to a subscription. |
| User Id | Unique key generated by Chord to identify a unique user. |
| User Is Active Subscriber | Whether or not the user has an active subscription with at least one completed subscription order. An active subscription is one that is not cancelled or paused. |
| User Is Customer | Whether or not the user is a customer. |
| User Is New Customer | Whether or not the user is a new customer. |
| User Is Not Customer | Whether or not the user is not a customer. |
| User Is Returning Customer | Whether or not the user is a returning customer. |
| User Is Subscriber | Whether or not the user has completed at least one subscription order. |
| User Login | The login email address of the user. |
| User Name | Full name of the user. |
| User Number Of Completed A La Carte Orders | Total amount of orders completed by a user that are a la carte. |
| User Number Of Completed Subscription Orders | Total amount of orders completed by a user that was part of a subscription. |
| User Number Of Orders With Promos | The count of completed orders with a promo applied. |
| User Number Of Subscriptions | Total amount of subscriptions linked to a user. |
| User Oms User Id | Unique key generated by Solidus that identifies a user. |
| User Phone | Phone number of the user. |
| User Total Completed Order Count | Total amount of orders completed by a user. |
| User Unique Ordered Products | Unique products ordered by the user across all orders. |
| User Unique Ordered Skus | Unique SKUs ordered by the user across all orders. |
| Billing Address Created At (Universal) | Timestamp at which the address row was created - Universal Time Zone. |
| Billing Address Updated At (Universal) | Timestamp at which the address row was last updated - Universal Time Zone. |
| Shipping Address Created At (Universal) | Timestamp at which the address row was created - Universal Time Zone. |
| Shipping Address Updated At (Universal) | Timestamp at which the address row was last updated - Universal Time Zone. |
| Subscription Actionable Date (Universal) | The date of the next subscription installment. This date is updated after each successful installment. Subscriptions in an inactive state will be null - Universal Time Zone. |
| Subscription Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Subscription First Order Completed At (Universal) | The timestamp of the subscription's first completed order - Universal Time Zone. |
| Subscription Last Order Completed At (Universal) | The timestamp of the subscription's last completed order - Universal Time Zone. |
| Subscription Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| User Created At (Universal) | Timestamp at which the users row was created - Universal Time Zone. |
| User Date Of Birth (Universal) | Date of birth of the user - Universal Time Zone. |
| User Deleted At (Universal) | Timestamp at which the user's account was deleted - Universal Time Zone. |
| User First Order Completed At (Universal) | The timestamp of the user's first completed order - Universal Time Zone. |
| User First Subscription Order Completed At (Universal) | The timestamp of the user's first completed subscription order, regardless of subsequent subscriptions - Universal Time Zone. |
| User Last Order Completed At (Universal) | The timestamp of the user's last completed order - Universal Time Zone. |
| User Last Sign In At (Universal) | The last sign in timestamp for the user - Universal Time Zone. |
| User Updated At (Universal) | Timestamp at which the users row was last updated - Universal Time Zone. |
| Average Additional Tax Total | Sum of additional taxes paid for all completed orders for a subscription. |
| Average Adjustment Total | Sum of adjustment applied for all completed orders for a subscription as on the order. |
| Average Commission Total | Sum of commission paid for all completed orders for a subscription. |
| Average Fulfillment Total | Sum paid for fulfillment for all completed orders for a subscription. |
| Average Included Tax Total | Sum of included taxes paid for all completed orders for a subscription. |
| Average Item Total | Sum of items price paid for all completed orders for a subscription. |
| Average Promo Total | Sum of promotions applied for all completed orders for a subscription. |
| Average Tax Total | Sum of total taxes paid for all completed orders for a subscription. |
| Average Total Completed Order Count | Total amount of orders completed by a subscription. |
| Average Transaction Total | Sum paid on all transactions for a subscription. |
| Additional Tax Total | Sum of additional taxes paid for all completed orders for a subscription. |
| Adjustment Total | Sum of adjustment applied for all completed orders for a subscription as on the order. |
| Commission Total | Sum of commission paid for all completed orders for a subscription. |
| Total Completed Order Count | Total amount of orders completed by a subscription. |
| Fulfillment Total | Sum paid for fulfillment for all completed orders for a subscription. |
| Included Tax Total | Sum of included taxes paid for all completed orders for a subscription. |
| Item Total | Sum of items price paid for all completed orders for a subscription. |
| Promo Total | Sum of promotions applied for all completed orders for a subscription. |
| Tax Total | Sum of total taxes paid for all completed orders for a subscription. |
| Transaction Total | Sum paid on all transactions for a subscription. |
### subscription\_unique\_product\_basket
| Name | Description |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| Unique Product Basket | Unique product basket for the subscription. Includes all products associated with the subscription, historical and current. |
[title] Data Sources
[path] Chord Data Platform/
Data sources are the origins from which Chord collects and processes your business data. By connecting your data sources to the Chord data platform, you can centralize information from across your tech stack and make it available for analytics, modeling, and activation.
Chord supports a growing list of connectors for SaaS applications, e-commerce platforms, advertising networks, and databases. Once connected, data from these sources is extracted, transformed, and loaded into the platform on a scheduled basis.
# **What's in this section**
Got it! Here's the updated **What's in this section** block based on the actual content of each page:
**What's in this section**
- **Connect data sources** — Learn how to add and manage data source connectors in the Chord platform, including setup steps, supported connectors, and troubleshooting guidance.
- **Ads module** — Overview of the ads explore for building custom reports and analyzing ad spend alongside Chord's marketing attribution data.
- **Messaging module** — Overview of the messaging explore for tracking campaign sends, opens, clicks, and subscription rates.
- **Sales channel module** — Organize and analyze revenue data across all your sales channels, including DTC storefronts, third-party marketplaces, and retail partnerships via Amazon Selling Partner. (Note: This module is only available for Shopify OMS brands.)
- **Subscriptions module** — Analyze subscription performance using Chord's suite of subscription explores. Covers metrics like churn, retention, LTV, and subscriber growth.
- **E-commerce data ingestion** — Learn how Chord ingests data from non-Shopify e-commerce platforms like Magento, BigCommerce, and Salesforce Commerce Cloud, including data mapping and sync details.
[title] Subscriptions
[path] Chord Data Platform/Data Models/
## Introduction
Chord's Subscription Analytics module provides a suite of **7 Explores** designed for self-service subscription analysis.
These Explores:
- Work across Recharge and your OMS
- Provide a unified view of subscription performance
- Support analysis across:
- Customer-level
- Subscription-level
- Product-level
- Lifecycle events
## How to access
1. Log into the Chord Commerce Data Platform
2. Navigate to **Analytics**
3. Click **Explores**
4. Select a **Subscription Explore**
## Quick reference — Which Explore should I use?
Use this as your starting point when you’re not sure where to go.
Each Explore is designed to answer a specific type of business question.
| If your question is about… | What you’re trying to understand | Use this Explore |
| ------------------------------- | --------------------------------------------------- | -------------------------------------- |
| **Overall subscription health** | Are we growing or shrinking? What’s our churn rate? | **Subscription Metrics Daily** |
| **Customer value (LTV)** | Who are our most valuable subscribers? | **Subscriber Journey** |
| **Retention over time** | How long do customers stay? How do cohorts behave? | **Subscriber Journey Monthly** |
| **Behavior leading to churn** | What happens before users cancel? | **Subscription Events Enriched** |
| **Business impact of changes** | How much revenue are we losing from cancellations? | **Subscription Movements Daily** |
| **Product performance** | Which products drive growth or churn? | **Subscription Product Metrics Daily** |
| **Bundle performance** | Which product combinations perform best? | **Subscription Bundle Metrics Daily** |
**You can use this handy guide to start your analysis: **
- Start with **Metrics Daily** → *“What is happening?”*
- Move to **Journey / Monthly** → *“Who is driving this and how does it evolve?”*
- Use **Events** → *“Why is this happening?”*
- Use **Movements / Product / Bundle** → *“Where is the impact coming from?”*
## Key Dimensions & Metrics
[Subscription Metrics Daily Explore](docId\:vrK7FlahNOV_r92ULUJH0)
[Subscriber Journey Explore](docId\:pHLEFk8F-KCnLkaNepm97)
[Subscriber Journey Monthly Explore](docId\:K3t064ARjs6tAEi21ua46)
[Subscription Events Enriched Explore](docId\:PGqIyYRgagkRu-tuwX6jj)
[Subscription Movements Daily Explore](docId\:JjEYNdJwHcf6ua-4ketck)
[Subscription Product Metrics Daily Explore](docId:6lDcTaqrCd0OXvQrVvGOz)
[Subscription Bundle Metrics Daily Explore](docId\:FpvuvhiI9L9Wp4ybhC2Hc)
# Glossary
| Term | What it Means | How to Interpret / Use | Where You’ll See It in Looker |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Active Subscription** | A subscription that is currently ongoing. Includes both fully active and paused subscriptions. | Use this to understand the **current size of your subscriber base**. Note that paused users are still counted. | Subscription Metrics Daily (Active Count), Subscriber Journey (Is Active Subscriber), Subscriber Journey Monthly (Is Active Subscriber EOM), Product & Bundle Explores (Active Subscription Count) |
| **Churn / Churned** | A subscription that has been cancelled. Does not include pauses. | Represents **true customer loss**. Track this to understand retention issues. | Subscription Metrics Daily (Churned Count, Churn Rate), Subscriber Journey (Is Churned, Churn Count), Monthly (Is Churned EOM, Cancellations This Month), Events Enriched (Event Type = canceled), Movements (status\_cancelled) |
| **Winback** | A subscriber who cancelled all subscriptions and later returned by subscribing again. | Indicates **successful re-engagement** after churn. | Subscriber Journey (Is Winback), Subscriber Journey Monthly (Has Reactivated By EOM) |
| **Reactivation** | A previously cancelled subscription that becomes active again (subscription-level). | Measures **recovery of churned subscriptions**. | Subscription Metrics Daily (Reactivated Count), Movements (status\_reactivated), Events Enriched (Event Type = reactivated) |
| **Net New** | Net change in subscriptions: New + Reactivated − Cancelled. | Indicates **overall growth vs decline**. | Subscription Metrics Daily (Net New Count) |
| **LTV (Lifetime Value)** | Total revenue generated by a subscriber across all subscription orders. | Use to understand **customer value over time** and compare cohorts or segments. | Subscriber Journey (LTV Gross / Net Revenue), Subscriber Journey Monthly (LTV Gross Revenue EOM) |
| **EOM (End of Month)** | Metrics calculated as of the last day of a month. | Used for **consistent month-over-month comparisons** (retention, LTV growth). | Subscriber Journey Monthly (all EOM fields) |
| **Subscriber Category** | Mutually-exclusive current-state classification of a customer: active / partially\_paused / fully\_paused / canceled / never\_subscribed. | Use to segment customers by **current lifecycle state**. A reactivated customer returns to *active*. | Subscriber Journey, Subscriber Journey Monthly (current value) |
| **Partially Paused** | Customer has at least one active AND at least one paused subscription simultaneously. | Identifies **at-risk users** scaling down but not fully churned. | Subscription Metrics Daily (Partially Paused Subscribers Count), Subscriber Journey (Subscriber Category) |
| **Fully Paused** | Customer's only non-canceled subscriptions are paused. | A **softer churn signal** — these users may still reactivate. | Subscription Metrics Daily (Fully Paused Subscribers Count), Subscriber Journey (Subscriber Category) |
| **Never Subscribed** | Customer exists in the system but has never had a subscription. | Useful for sizing **first-subscription / cross-sell opportunity**. | Subscriber Journey only |
| **Prepaid Subscriber** | Customer has at least one prepaid (non-gift) subscription. | Identifies **upfront billing behavior**. ChordOMS only. | Subscription Metrics Daily (Prepaid Subscribers Count), Subscriber Journey (Is Prepaid Subscriber) |
| **Gift Purchaser** | Customer has purchased one or more gift subscriptions for someone else. | Useful for **marketing segmentation and gifting behavior**. ChordOMS only. | Subscription Metrics Daily (Gift Purchasers Count — cumulative), Subscriber Journey (Is Gift Purchaser) |
| **Gifted Subscriber** | Customer is receiving a gift subscription (someone else purchased it). | Useful for **conversion strategies** (turning recipients into paying users). ChordOMS only. | Subscription Metrics Daily (Gifted Subscribers Count), Subscriber Journey (Is Gifted Subscriber) |
| **Solo Subscription** | A subscription that contains only one product. | Helps identify products that perform well **individually**. | Subscription Product Metrics Daily (Solo Subscription Count) |
| **Bundle** | A subscription that contains two or more products. | Useful for analyzing **cross-sell and product combinations**. | Product Metrics (Bundle Subscription Count), Bundle Metrics Daily |
| **Movement** | Any change in a subscription’s state (created, cancelled, paused, resumed, reactivated, quantity/price change). | Use to understand **operational changes and trends** in subscriptions. | Subscription Movements Daily (Movement Type), Events Enriched (Event Type) |
| **Provider** | The system managing subscriptions (Recharge, ChordOMS, CustomOMS). | Important context — **data availability varies by provider**, impacting analysis. | All Explores |
[title] Subscription Metrics Daily Explore
[path] Chord Data Platform/Data Models/Subscriptions/
## Overview
Daily summary of subscription counts and flows.
- Grain: **1 row per day**
- Purpose: monitor **growth, churn, and overall health**
## When to use
- Track subscription health on dashboards
- Monitor churn trends over time
- Evaluate net growth vs decline
- Support executive-level reporting
## Key dimensions & metrics
| Field | Description |
| ---------------------------------- | ------------------------------------------------------------------------------- |
| Report Date | Date of snapshot |
| Active Count | Total active subscriptions |
| New Count | Subscriptions created that day |
| Churned Count | Subscriptions cancelled that day |
| Reactivated Count | Previously cancelled → active |
| Paused Count | Subscriptions paused that day |
| Resumed Count | Subscriptions resumed that day |
| Net New Count | New + Reactivated − Churned |
| Churn Rate | Churned / previous day active |
| Cancelled Cumulative Count | Running total cancellations |
| Active Subscribers Count | Point-in-time count of customers with ≥1 active sub and no paused subs |
| Partially Paused Subscribers Count | Point-in-time count of customers with both active AND paused subs |
| Fully Paused Subscribers Count | Point-in-time count of customers with only paused subs |
| Canceled Subscribers Count | Point-in-time count of customers whose only remaining subs are canceled |
| Prepaid Subscribers Count | Point-in-time count of customers with ≥1 prepaid (non-gift) sub (ChordOMS only) |
| Gifted Subscribers Count | Point-in-time count of customers currently receiving a gift sub (ChordOMS only) |
| Gift Purchasers Count | Cumulative count of customers who have purchased a gift sub (ChordOMS only) |
## Example business questions
- Daily churn trend (last 90 days)
- Net growth trend over time
- Monthly adds vs losses
## Notes & caveats
- **Churn = cancellation only** (pauses excluded)
- Paused/Resumed counts are **distinct subscription counts**, not event counts
- Churn rate returns **NULL** if no previous-day active subscriptions
- The subscriber counts above are **point-in-time (recalculated per report\_date)**
- **Gift Purchasers Count is cumulative** — once a customer has bought a gift, they remain counted
- **Prepaid, Gifted, and Gift Purchasers are ChordOMS-only** — Recharge and CustomOMS tenants will always show 0
## Glossary
| Term | What it Means | How to Interpret / Use | Where You’ll See It in Looker |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Active Subscription** | A subscription that is currently ongoing. Includes both fully active and paused subscriptions. | Use this to understand the **current size of your subscriber base**. Note that paused users are still counted. | Subscription Metrics Daily (Active Count), Subscriber Journey (Is Active Subscriber), Subscriber Journey Monthly (Is Active Subscriber EOM), Product & Bundle Explores (Active Subscription Count) |
| **Churn / Churned** | A subscription that has been cancelled. Does not include pauses. | Represents **true customer loss**. Track this to understand retention issues. | Subscription Metrics Daily (Churned Count, Churn Rate), Subscriber Journey (Is Churned, Churn Count), Monthly (Is Churned EOM, Cancellations This Month), Events Enriched (Event Type = canceled), Movements (status\_cancelled) |
| **Winback** | A subscriber who cancelled all subscriptions and later returned by subscribing again. | Indicates **successful re-engagement** after churn. | Subscriber Journey (Is Winback), Subscriber Journey Monthly (Has Reactivated By EOM) |
| **Reactivation** | A previously cancelled subscription that becomes active again (subscription-level). | Measures **recovery of churned subscriptions**. | Subscription Metrics Daily (Reactivated Count), Movements (status\_reactivated), Events Enriched (Event Type = reactivated) |
| **Net New** | Net change in subscriptions: New + Reactivated − Cancelled. | Indicates **overall growth vs decline**. | Subscription Metrics Daily (Net New Count) |
| **LTV (Lifetime Value)** | Total revenue generated by a subscriber across all subscription orders. | Use to understand **customer value over time** and compare cohorts or segments. | Subscriber Journey (LTV Gross / Net Revenue), Subscriber Journey Monthly (LTV Gross Revenue EOM) |
| **EOM (End of Month)** | Metrics calculated as of the last day of a month. | Used for **consistent month-over-month comparisons** (retention, LTV growth). | Subscriber Journey Monthly (all EOM fields) |
| **Subscriber Category** | Mutually-exclusive current-state classification of a customer: active / partially\_paused / fully\_paused / canceled / never\_subscribed. | Use to segment customers by **current lifecycle state**. A reactivated customer returns to *active*. | Subscriber Journey, Subscriber Journey Monthly (current value) |
| **Partially Paused** | Customer has at least one active AND at least one paused subscription simultaneously. | Identifies **at-risk users** scaling down but not fully churned. | Subscription Metrics Daily (Partially Paused Subscribers Count), Subscriber Journey (Subscriber Category) |
| **Fully Paused** | Customer's only non-canceled subscriptions are paused. | A **softer churn signal** — these users may still reactivate. | Subscription Metrics Daily (Fully Paused Subscribers Count), Subscriber Journey (Subscriber Category) |
| **Never Subscribed** | Customer exists in the system but has never had a subscription. | Useful for sizing **first-subscription / cross-sell opportunity**. | Subscriber Journey only |
| **Prepaid Subscriber** | Customer has at least one prepaid (non-gift) subscription. | Identifies **upfront billing behavior**. ChordOMS only. | Subscription Metrics Daily (Prepaid Subscribers Count), Subscriber Journey (Is Prepaid Subscriber) |
| **Gift Purchaser** | Customer has purchased one or more gift subscriptions for someone else. | Useful for **marketing segmentation and gifting behavior**. ChordOMS only. | Subscription Metrics Daily (Gift Purchasers Count — cumulative), Subscriber Journey (Is Gift Purchaser) |
| **Gifted Subscriber** | Customer is receiving a gift subscription (someone else purchased it). | Useful for **conversion strategies** (turning recipients into paying users). ChordOMS only. | Subscription Metrics Daily (Gifted Subscribers Count), Subscriber Journey (Is Gifted Subscriber) |
| **Solo Subscription** | A subscription that contains only one product. | Helps identify products that perform well **individually**. | Subscription Product Metrics Daily (Solo Subscription Count) |
| **Bundle** | A subscription that contains two or more products. | Useful for analyzing **cross-sell and product combinations**. | Product Metrics (Bundle Subscription Count), Bundle Metrics Daily |
| **Movement** | Any change in a subscription’s state (created, cancelled, paused, resumed, reactivated, quantity/price change). | Use to understand **operational changes and trends** in subscriptions. | Subscription Movements Daily (Movement Type), Events Enriched (Event Type) |
| **Provider** | The system managing subscriptions (Recharge, ChordOMS, CustomOMS). | Important context — **data availability varies by provider**, impacting analysis. | All Explores |
[title] Chord AI Context
[path] Chord AI/
# Introduction
Chord AI’s Context helps you capture and manage verified insights in the form of **Instructions **and **SQL Pairs**.
**Instructions** offer two levels of guidance:
- **Global Instructions**, which apply to all queries (e.g., applying business rules like filtering out canceled orders, enforcing rounding conventions or naming standards across the board), and
- **Question‑Matching Instructions**, which apply only when a question matches a defined pattern (e.g., how to calculate “late delivery rate” based on specific date logic).
Together, these ensure more precise, standardized SQL generation aligned with your organization’s metrics and logic.
Additionally, **SQL Pairs** allow you to map natural language questions—like “What is our average customer lifetime value?”—to pre‑verified SQL queries, so that when similar questions are asked in the future, Chord AI can generate accurate and consistent results using those saved queries.
Question types that are best served by **SQL Pairs** include:
- Complex business or computation logic that requires precise SQL formulation.
- Frequently asked business questions with established calculation methods.
- Custom KPIs and metrics specific to your brand.
Combined, **Instructions** and **SQL Pairs** give Chord AI the ability to answer domain-specific questions with high consistency and accuracy—capturing organizational knowledge, reducing SQL errors, and improving trust in AI-generated outputs.
Read on for additional information about these features within Chord Context.
## Instructions
The **Instructions** feature in Chord Context lets your team embed business logic and formatting rules directly into how the system generates SQL queries and answers. By using Instructions, organizations can standardize how metrics are calculated, ensure consistent SQL structure, and provide data context in a way that aligns closely with internal definitions. It helps Chord Copilot produce accurate, reliable, and predictable answers by capturing domain-specific business rules and metrics logic in advance.
There are two types of **Instructions** that organizations can customize: **Global Instructions** and **Question-Matching Instructions**.
### Global instructions
You can set **Global Instructions** that apply to all questions—perfect for enforcing naming conventions, consistent rounding, data filters (e.g. excluding canceled orders), and join behaviors.
To add a **Global Instruction**:
1. Navigate to the **Context** navigation link.
2. Click the **"Add Instruction"** button.
3. Select **"Global"** under **"Apply instruction to"**.
4. Enter your instruction details in the text field.
5. Click** "Submit"** to save and apply the instruction.
### Question-matching instructions
You can also define **Question-Matching Instructions**, which only apply when user queries match specific patterns or topics—such as calculating “late delivery rate” using your exact definition.
To add a** Question-Matching Instruction**:
1. Navigate to the **Context** navigation link.
2. Click on the **Instructions** tab.
3. Click the** "Add Instruction"** button.
4. Select **"Matched to specific questions"** under **"Apply instruction to".**
5. Enter your instruction details in the text field.
6. Add questions that should trigger the instruction.
7. Click **"Submit"** to save and apply the instruction.
## SQL pairs
Chord AI's **SQL Pairs** capability allows you to capture and map natural‑language questions to their exact SQL queries, building a trusted knowledge base of verified answers. Whenever a team member asks a similar question—such as "What is our average order value?"—Chord AI can pull the saved SQL and respond with the exact computation each time, ensuring consistency across the organization.
To set up a **SQL Pair**, you can manually add a SQL pair to Chord Context if you know certain questions that your team will ask in advance.
To manually add a **SQL Pair**:
1. Navigate to the **Context** navigation link.
2. Click on the **Question-SQL Pairs** tab.
3. Click the** "Add Question-SQL Pair"** button.
4. Add a question and the corresponding SQL statement that answers the quesiton.
5. Click **"Create"** to create and save the SQL Pair.
Once a SQL Pair is created, you can view, edit, or delete a specific SQL Pair at any time.
[title] Stock Requests
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Chord OMS/
### **x\_fct\_trans\_stock\_requests**
| Name | Description |
| ------------------------------------ | ----------------------------------------------------------------------------------- |
| Product Description | The description of the product. |
| Product Id | Unique key generated by Chord to identify a unique product. |
| Product Is Adult Signature Required | If an adult's signature is required. |
| Product Is Promotionable | Whether promotions can apply to the product. |
| Product Name | The name of the product. |
| Product Oms Product Id | Unique key generated by Solidus that identifies a product. |
| Product Property Gender | Product property gender. |
| Product Slug | The slug of the product. |
| Stock Request Id | Unique key generated by Chord to identify a unique stock request. |
| Stock Request Oms Stock Request Id | Unique key generated by Solidus that identifies a stock request. |
| Stock Request Requester Email | Email address of the user requesting stock. |
| Stock Request Status | Status of the stock request. |
| Store Id | Unique key generated by our models that uniquifies a store. |
| Store Name | The name of the store. |
| Store Oms Admin Url | The Admin URL of that OMS. |
| Store Oms Id | Unique key generated by Chord that uniquifies an OMS. |
| Store Oms Store Id | Unique key generated by our models that uniquifies a store. |
| Store Oms Type | The type of the OMS. |
| Store Id | Unique key generated by our models that uniquifies a store. |
| Store Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Store Url | The Storefront URL of of the store. |
| Variant Cost Price | The manufacturing cost of the variant. |
| Variant Depth | The depth of the variant. |
| Variant Height | The height of the variant. |
| Variant Id | Unique key generated by Chord to identify a unique product variant. |
| Variant Is Backorderable | Whether the stock item has at least one location where it is back-orderable or not. |
| Variant Is Inventory Tracked | Whether the inventory should or should not be tracked for this variant. |
| Variant Is Master | Whether this represents the master SKU or not. |
| Variant Is Subscribable | Whether or not a customer can ask to subscribe to this product. |
| Variant Oms Variant Id | Unique key generated by Solidus that identifies a variant. |
| Variant Option Color | Color of the variant. |
| Variant Option Format | Format of the variant. |
| Variant Option Quantity | Quantity of item for the variant. |
| Variant Option Size | Size of the variant. |
| Variant Position | The position of the variant in the list of variants. |
| Variant Sku | The SKU of the variant. |
| Variant Weight | The weight of the variant. |
| Variant Width | The weight of the variant. |
| Product Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Product Deleted At (Universal) | Reflects when the entity was deleted - Universal Time Zone. |
| Product Discontinued At (Universal) | Reflects when the entity was discontinued - Universal Time Zone. |
| Product Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| Stock Request Created At (Universal) | Timestamp at which the stock request was created - Universal Time Zone. |
| Stock Request Updated At (Universal) | Timestamp at which the stock request was last updated - Universal Time Zone. |
| Variant Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Variant Deleted At (Universal) | Reflects when the entity was deleted - Universal Time Zone. |
| Variant Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
[title] Data Models
[path] Chord Data Platform/
## Introduction
Data models, or transformations, are tables created by our analytics engineering team to present data in a shape that is easy to consume for analytics purposes. Orders facts, product dimensions, and user dimensions are all examples of potential entities (or tables) in a data model.
Creating data models is essential for transforming raw data into structured, meaningful, and usable formats that drive analytics, reporting, and decision-making. Well-designed data models also serve as the foundation for powering more robust and useful AI systems by providing clean, consistent inputs that improve model accuracy, reduce noise, and support richer feature engineering. In short, data models not only enable better business intelligence but also unlock the full potential of AI by ensuring data is trustworthy, well-organized, and aligned with real-world context.
## Why Data Models Matter
🔧 **Structure and Organization**
- Data models define **how data is organized**, related, and stored.
- They bring **consistency and clarity** to how teams understand and query data.
:::BlockQuote
Example: Instead of dealing with hundreds or even thousands of unconnected tables, a well-designed model organizes them into clean dimensions (like Customers, Products) and facts (like Revenue).
:::
**🤖 Unlock Full Potential of AI with Organized, Accurate, and Business-Ready Context**
- Models provide the structured, high-quality data that machine learning systems rely on for accuracy and relevance.
- They enable richer feature engineering, reduce noise, and ensure AI outputs are grounded in business-ready context.
**📊 Enable Reliable Analytics**
- Models establish **clean relationships** between metrics and dimensions, reducing errors and ambiguity.
- They ensure that calculations like revenue, retention, or conversion rate are **accurate and consistent** across tools and users, creating a **single source of truth**.
**🚀 Power Self-Service & Scale**
- With intuitive, documented models (e.g., via dbt or semantic layers), non-technical users can explore data confidently.
- Teams avoid reinventing logic and reduce dependency on data engineers or analysts for every question.
🔒 **Governance and Control**
- Data models provide **defined logic, lineage, and ownership**, supporting governance, auditing, and compliance.
- They help enforce **data quality checks, contracts, and access controls**.
📐 **Improve Performance and Efficiency**
- Well-modeled data reduces duplication and streamlines queries.
- Optimized joins, indexing, and aggregations improve performance in warehouses and BI tools.
🧠 **Support Business Understanding**
- Models reflect the **business logic**—how the company defines a customer, transaction, or lifecycle stage.
- They bridge the gap between technical schemas and business needs.
## How it Works
Chord utilizes the **Kimball approach** to data modeling. This is a widely used method in analytics and data warehousing that enables teams to build models that are easy to understand and utilize.
It breaks data into two core types of tables:
🧾 **Fact Tables (fct\_)** – The “What Happened”
Fact tables track **events or transactions**, such as purchases, logins, or ad clicks.
They include **measurable data** such as revenue, quantities, time of action, and user IDs.
:::BlockQuote
Example: A table of all orders placed on your website, including order amount, date, and customer ID.
:::
��** Dimension Tables (dim\_) – The “Who” and “What”**
Dimension tables provide **context** for facts. They describe things like customers, products, or regions.
:::BlockQuote
Example: A table of customer information with name, email, signup date, and status (active/inactive).
:::
These two types of tables are designed to **join together** easily, allowing users to answer questions like:
- *“How much revenue did we make from active customers last month?”*
- *“Which products are most popular among new users?”*
### 🛠️ How Chord Builds Data Models
**Step 1: Ingest Raw Data**
Data often starts messy—coming from tools like:
- Shopify (orders, line items, products, etc.)
- Chord CDP (website client-side events and server-side events)
- Klaviyo (messaging)
- Facebook Ads (ad spend and metrics)
This data is loaded into a cloud data warehouse. However, at this point, it remains messy, inconsistent, and contains duplicates, inconsistent naming, or missing values. Additionally, each source typically contains tens or hundreds of separate tables that must be combined to make sense of the data.
**Step 2: Clean and Normalize the Data**
Chord utilizes **dbt** (short for *data build tool*), a transformation tool that helps data teams clean, organize, and document data as it flows from raw sources to clean, usable models. Chord's analytics engineers build these data models in layers in dbt using programming languages like SQL, python, jinja and YAML. The various data modelling layers allow us to:
- **Clean** the raw data (e.g., standardize names, remove junk values, Handle nulls, trims, formatting, or simple derived fields
- **Deduplicate** records
- **Convert **data types (e.g., string to timestamp)
- **Filte**r out irrelevant rows (e.g., deleted or test records)
- **Add flags** like is\_active
- **Convert or standardize** (e.g., currency conversion, unit standardization)
- **Join related tables** from different systems (e.g., linking a CDP session to a Shopify order)
- **Enrich** records with helpful metadata or flags
- **Define **metrics
**Step 3: Organize into Facts and Dimensions**
Once cleaned, the data is structured into:
- **Dimension models** like dim\_customers, dim\_products, dim\_dates
- **Fact models** like fct\_orders, fct\_pageviews, fct\_subscriptions
**Step 4: Explode!**
Chord utilizes an explosion technique to join every applicable dimension and fact table into a single, consolidated table, such as Orders, so that every field applicable to orders is now available in a single, unified table. We call these x\_fct tables. Now, there's no need for one-to-many joins between dimension and fact tables, and instead, data is readily joined to immediately start analysis!
These data models models are **versioned, documented, and tested** in dbt to ensure reliability. They run daily (or even hourly), so dashboards and AI models always use fresh, trustworthy data.
## **Getting Started**
Chord's data models power your AI, Analytics, and Activations in the Chord platform. You'll see data models such as Orders, Sessions, and more in your Explores section of Analytics. For the full list of models, along with each field therein, see the documentation in [Chord Data Attribute Definitions](docId\:EehJlvlJqMT3Q98V-e87N).
:::hint{type="success"}
if you have any questions or need help, please reach out to us at [help@chord.co](mailto\:help@chord.co)
:::
[title] Custom Audiences
[path] Chord Data Platform/Audiences/
# Overview
Chord's pre-built audiences give brands a quick and easy way to view (and activate) specific customer segments for marketing and beyond. In addition to modifying pre-built templates, brands can now also **create custom audiences directly from Explores** — capturing the exact filters and conditions used in an analysis with just one click. These custom audiences, like all others in Chord, can then be sent to third-party tools via the data activation suite to drive deeper e-commerce insights and customer engagement.
# How to create an activate audiences from Explores
::loom[]{url="https://www.loom.com/embed/f67b3e580ea44c76941004e2b677c7e9"}
You can now build and save custom audiences faster with the new **Create Audience **button — available directly in Explores.
When you've defined your filters and segments in an Explore, the **Create Audience** button allows you to:
- **Capture your current Explore state: **Everything you've filtered, defined, and scoped is preserved as the foundation of your new audience.
- **Name your audience: **Give it a clear, meaningful name to reflect its purpose or intended use.
- **Save it to your Shared Audiences folder: **No need to export or switch views — your audience is instantly saved and available for reuse.
:::hint{type="info"}
**Bonus: Auto-Select on Save**
Once your audience is saved, it will be automatically pre-selected when you navigate to the **Shared Audiences **view. That means you can immediately take action, explore further, or use it in downstream workflows — no extra clicks required.
:::
# How to create and activate audiences from Prebuilt Audiences
1. Once logged into the Chord data platform, navigate to the **Prebuilt Audiences **page.
2. Select a prebuilt audience that you'd like to customize. Click on the **Use As Template **button.
3. Give your new audience a new title and/or a description in the modal and click **Create Audience**.
4. After you have made the desired changes to your custom audience segment, click **Sync Audience **to send your custom audience to Chord Activations.
5. From here, you can send your customized audience segment to an existing sync OR create a new sync for your audience.
:::hint{type="info"}
**Note: **If you do not see your custom audience synced to data activations, please reach out to [help@chord.co](mailto\:help@chord.co) for assistance.
:::
# Troubleshooting and FAQs
- **Question: I clicked "Activate Audience" after creating a customized pre-built audience, and nothing happened. What did I do wrong?**
- ***Does your organization have access to Chord's Data Activations suite?*** If not, your team manager can request access to the Data Activations features and a Chord representative will be in touch shortly!
- If you organization ***does*** have access to the Data Activations features, you will see the below Audience Activations page:
::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-e9rTSZxiy5TQusRKHwyIM-20250403-143535.png" size="100" width="2694" height="1196" position="center" darkWidth="2694" darkHeight="1196" showCaption="false" indent="3"}
:::Paragraph{listStyleType="disc" listStart="3" indent="2"}
From here, you can follow the existing steps to create a data activations destination and will see your customized prebuilt audience list in the data sources dropdown menu.
:::
- **Question: I just created a custom segment and sent it to activations following the instructions above but don't see the audience segment I need in the activations suite. What did I do wrong?**
- The sync should occur immediately. However, if you do not see your custom audience listed under the activations modal, it may be due to issues with the setup of the audience in which the underlying SQL is not compiling. You''ll want to check that:
- Your dimension does not show "Remove filled in dates" like below. If your dimension does show "Remove filled in dates," select "Remove filled in dates" and then re-save your audience.
::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/iCsIrWE2VP6jmzs1DjUUy-71trnVimpGL2TkOVcmWS8-20250714-181904.png" size="100" width="1014" height="544" position="center" darkWidth="1014" darkHeight="544" showCaption="false" indent="4"}
:::Paragraph{listStyleType="disc" listStart="2" indent="2"}
If you do not see your custom audience listed under the activations modal, please reach out to [help@chord.co ](mailto\:help@chord.co) for assistance.
:::
- **Question: Can I edit and activate a custom audience segment that has been previously activated? **
- No, you will not be able to edit a custom audience segment that has been previously activated. You will need to create new audience segments each time in order to send the customer list to the Chord data activations suite.
- **Question:** **What if I am not creating an audience through the Chord data platform and want to send information to a third-party app like Klaviyo or Google Sheets? **
- This is something the Chord team is working on supporting through a separate custom data activations feature. This workflow is not supported by **Custom Audiences.**
[title] Omni-Channel Sales Data Modeling
[path] Chord Data Platform/Data Sources/Untitled/
:::hint{type="info"}
**This Explore is only available to Shopify OMS customers at this time.**
:::
# Overview
E-commerce brands don’t sell in just one place—and your data shouldn’t treat each sales channel as a silo. Chord’s new omni-channel sales data modeling brings together sales data from all your key commerce channels—including Shopify, Chord OMS, Salesforce, and third-party marketplaces like Amazon—into a unified, comprehensive dataset.
For Chord brands with the Amazon Selling Partner source, this Explore combines Amazon and Shopify transactional line items into a unified Explore.
This omni-channel approach allows you to:
- Analyze total sales across all channels in one place.
- Compare performance across categories or by individual channel.
- Break down revenue by channel to support reporting and strategy.
- Track trends and customer behavior regardless of point of sale.
# Core Event Attributes
- Line Items
- Source System: Can be Amazon or Shopify
- Order
- Order Created Date
# Where to Find This Data in Chord
Once your Amazon Selling Partner source events are ingested by Chord, you will be able to further analyze this data on Chord.
:::hint{type="info"}
For assistance with getting Amazon Selling Partner data ingested on Chord, please contact help\@chord.co.
:::
Once your Amazon Selling Partner data has been ingested and synced, follow the steps below to dig into your data:
1. Log into the Chord Commerce data platform.
2. Navigate to **Explores** tab on the **Analytics** page.
3. Click on the **Explores** dropdown on the left side of the page.
4. Select the** Omni-Channel Sales** Explore.
[title] Orders
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Chord OMS/
### x\_fct\_trans\_orders
| Name | Description |
| ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Affiliate Email | Email address of the affiliate. |
| Affiliate Id | Unique key generated by Chord to identify a unique affiliate. |
| Affiliate Name | Full name of the user. |
| Affiliate Seen Emails | List of email addresses seen. |
| Affiliate User Id | Unique key generated by Chord to identify a unique user. |
| Billing Address Address1 | The street address of the customer. |
| Billing Address Address2 | The optional second address of the customer. |
| Billing Address Alternative Phone | The customer's alternative phone number. |
| Billing Address City | The city where the address is. |
| Billing Address Company | A company name. |
| Billing Address Country Abbr | |
| Billing Address Country Name | Full name of the country. |
| Billing Address Firstname | First name of the customer. |
| Billing Address Id | Unique key generated by Chord to identify a unique address. |
| Billing Address Lastname | Last name of the customer. |
| Billing Address Oms Address Id | Unique key generated by Solidus that identifies an address. |
| Billing Address Phone | The customer's phone number. |
| Billing Address State Abbr | |
| Billing Address State Name | Full name of the state. |
| Billing Address Zipcode | The postal code. |
| Order Adjustment Types | List of distinct adjustment reasons for adjustments made to the order. |
| Order Admin Url | The Admin URL of pointing to the order. |
| Order Applied Discount Codes | List of promotion codes applied to the order. |
| Order Applied Discount Codes Count | Count of promotion codes applied to the order. |
| Order Applied Discount Ids | List of promotion ids applied to the order. |
| Order Applied Discount Names | List of promotion names applied to the order. |
| Order Applied Discount Names Count | Count of promotion names applied to the order. |
| Order Cart Url | Url of the cart which contains the order. |
| Order Channel | The channel from which the order is created. |
| Order Completed Order Rank By Subscription | Allows to rank completed orders by completion date for a subscription. |
| Order Completed Order Rank By User | Allows to rank completed orders by completion date for a user. |
| Order Contains Refund | Whether or not the order contains refund adjustments or refunds that are processed outside of the Chord OMS adjustment systems (for example via RMAs or cancellations). |
| Order Contains Replacement | Whether or not the order contains replacement adjustments or shipped replacement items (following an RMA authorization). |
| Order Contains Return | Whether or not the order contains returns (authorized RMAs). |
| Order Contains Rma Refund | Whether or not the order contains RMA refunds (refunds issued after an RMA was requested and authorized). |
| Order Contains Rma Store Credits | This column is not documented. |
| Order Currency | The currency for this order. |
| Order Customer Lifetime Month | Number of months between the current order's completion date and the user's first order completion date. First orders have a value of 1. |
| Order Customer Lifetime Week | Number of weeks between the current order's completion date and the user's first order completion date. First orders always have a value of 1. |
| Order Days Since Last Order Completed | The days between the last order's completed date and this order's. Only for completed orders. |
| Order Days Since Last Order Completed | The days between the last order's created date and this order's. |
| Order Email | The email address of the customer that made the order. |
| Order Financial State | The current payment state of the order. |
| Order Fulfillment Ids | Array of unique keys generated by Chord to identify the unique shipments for an order. |
| Order Fulfillment Numbers | The unique identifier for this shipment. |
| Order Fulfillment State | The current shipment state of the order. |
| Order Has Discount | Whether or not the order has promotions applied to it. |
| Order Has Order Tags | Whether or not that order has tags. |
| Order Hours From Order To First Fulfillment | Number of hours between order completion and first order shipment; how long it takes a company to get the initial product out to a customer. |
| Order Hours From Order To Last Fulfillment | Number of hours between order completion and last order shipment. |
| Order Id | Unique key generated by Chord to identify a unique order. |
| Order Is Canceled | Whether or not the order is canceled. The order is considered canceled when the canceled\_at date is not null. |
| Order Is Completed | Whether or not that order is completed. The order is considered completed when the completed\_at date is not null. This means that the order does not necessarily have a state = 'complete', since states can change after the order completion (for example in the case of a refund). |
| Order Is First Completed Order | Whether or not that order was the first completed order for a user. |
| Order Is First Order | Whether or not that order was the first order for a user. |
| Order Is First Subscription Completed Order | Whether or not that order was the first completed order for a subscription. |
| Order Is First Subscription Order | Whether or not that order was the first order for a subscription. |
| Order Is Fulfilled | Whether or not that order has shipped. |
| Order Is Part Of Subscription | Whether or not that order is part of a subscription. |
| Order Is Pre Paid Purchase | Whether the order the orderincludes the purchase of a pre-payment; this could be a gift subscription, pre-pay subscription, or gift card. |
| Order Is Pre Paid Redemption | Whether the order included the redemption of a pre-payment; this could be the redemption of a gift subscription, pre-pay subscription, or gift card. |
| Order Is Referred By Affiliate | Whether or not the user is referred by an affiliate. |
| Order Is Referred By Referrer | Whether or not the user is referred by a referrer. |
| Order Is Replacement | True when the order is a replacement order. |
| Order Is Suspicious Referral Conversion | Wether this represents a suspicous referral conversions or not. |
| Order Item Id | Unique key generated by Chord to identify a unique order. |
| Order Item Line Items Quantity | Sum of line items quantities per order. |
| Order Item Product Basket | List of product names per in the order. |
| Order Item Product Basket Count | Number of products in the order. |
| Order Product Basket | The titles of products for a given order array converted to a string. |
| Order Item Total Line Item Unit Quantity | Sum of line item units in the order. |
| Order Item Total Line Items Quantity | Sum of line items quantities per order. |
| Order Item Unique Product Basket | List of unique product names per in the order. |
| Order Item Unique Product Basket Count | Number of unique products in the order. |
| Order Unique Product Basket | The list of unique products for a given order array converted to a string. |
| Order Item Unique Unit Basket | List of unique units in the order. |
| Order Item Unique Unit Basket Count | Count of unique units in the order. |
| Order Unit Basket | The list of units for a given order array converted to a string. |
| Order Item Unique Variant Basket | List of unique variant names per in the order. |
| Order Item Unique Variant Basket Count | Number of unique variants in the order. |
| Order Unique Variant Basket | The list of unique variants for a given order array converted to a string. |
| Order Item Unit Basket | List of all units in the order. |
| Order Item Unit Basket Count | Count of all units in the order. |
| Order Unique Unit Basket | The list of unique units for a given order array converted to a string. |
| Order Item Variant Basket | List of variant names per in the order. |
| Order Item Variant Basket Count | Number of variants in the order. |
| Order Variant Basket | The titles of variants for a given order array converted to a string. |
| Order Number | Human-readable unique key generated by Solidus that identifies an order. It begins with a set of Tenant-Store defined letters and ends in a nine-digit number (for example, CHORD-123456789). This number is shown to the users in various places. These combinations are unique for a given Store. |
| Order Oms Order Id | Unique key generated by Solidus that identifies an order. |
| Order Rank By User | Allows to rank completed orders by completion date for a user. |
| Order Tags | List of tags associated to the order. |
| Order Tags Count | Number of tags associated to the order. |
| Order Referral Conversion Suspicious Reasons | A list of reasons explaining why the referral conversion is suspicious. |
| Order Referrer User Email | The email address of the customer identified with the referral. |
| Order Special Instructions | Any special shipping instructions that have been specified by the customer during checkout. |
| Order State | The current state of the order. |
| Order Store Id | Unique key generated by our models that uniquifies a store. |
| Order Store Name | The name of the store. |
| Order Store Oms Admin Url | The Admin URL of that OMS. |
| Order Store Oms Id | Unique key generated by Chord that uniquifies an OMS. |
| Order Store Oms Store Id | Unique key generated by our models that uniquifies a store. |
| Order Store Oms Type | The type of the OMS. |
| Order Store Id | Unique key generated by our models that uniquifies a store. |
| Order Store Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Order Store Url | The Storefront URL of of the store. |
| Order Subscription Customer Lifetime Month | Number of months between the current order's completion date and the user's first subscription order completion date. First orders have a value of 1. |
| Order Subscription Customer Lifetime Week | Number of weeks between the current order's completion date and the user's first subscription order completion date. First orders always have a value of 1. |
| Order User Referral Code | Unique key generated by Solidus that represents the user's referral code. |
| Order Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store. |
| Referral Conversion Rank By Referrer | Allows to rank a referral conversion by referrer. |
| Referral Id | Unique key generated by Chord to identify a unique referral identifier. |
| Referral Is Converted | Wether this represents a converted referral or not. |
| Referral Is First Conversion | Whether or not the referral was the referrer's first converted referral. |
| Referral Is First Non Suspicious Conversion | Whether or not the referral was the referrer's first non suspicious converted referral. |
| Referral Is Suspicious | Wether this represents a suspicous referral conversions or not. |
| Referral Non Suspicious Conversion Rank By Referrer | Allows ranking of non-suspicious referral conversion by the referrer. |
| Referral Oms Referral Conversion Id | Unique key generated by Solidus that identifies a referral conversion. |
| Referral Suspicious Reasons | A list of reasons explaining why the referral conversion is suspicious. |
| Referrer Currency | The currency for this referral identifier. |
| Referrer Email | The email address of the customer identified with the referral. |
| Referrer Id | Unique key generated by Chord to identify a unique referral identifier. |
| Referrer Oms Referral Identifier Id | Unique key generated by Solidus that identifies a referral identifier. |
| Referrer User Referral Code | Unique key generated by Solidus that represents the user's referral code. |
| Shipping Address Address1 | The street address of the customer. |
| Shipping Address Address2 | The optional second address of the customer. |
| Shipping Address Alternative Phone | The customer's alternative phone number. |
| Shipping Address City | The city where the address is. |
| Shipping Address Company | A company name. |
| Shipping Address Country Abbr | |
| Shipping Address Country Name | Full name of the country. |
| Shipping Address Firstname | First name of the customer. |
| Shipping Address Id | Unique key generated by Chord to identify a unique address. |
| Shipping Address Lastname | Last name of the customer. |
| Shipping Address Oms Address Id | Unique key generated by Solidus that identifies an address. |
| Shipping Address Phone | The customer's phone number. |
| Shipping Address State Abbr | |
| Shipping Address State Name | Full name of the state. |
| Shipping Address Zipcode | The postal code. |
| Subscription Completed Oms Order Ids | List of completed OMS order ids by a subscription. |
| Subscription Completed Order Count | Total amount of orders completed by a subscription. |
| Subscription Completed Order Ids | List of completed order ids by a subscription. |
| Subscription First Order Unique Product Basket | Array of unique product names ordered in the first order per subscription. |
| Subscription First Order Unique Variant Basket | Array of unique SKUs ordered in the first order per subscription. |
| Subscription Has Subscription Tags | Whether or not the subscription has tags. |
| Subscription Id | Unique key generated by Solidus that identifies a subscription. |
| Subscription Interval In Days | The number of days in the subscription interval. |
| Subscription Is Auto Redeemed | Whether the pre-paid subscription will be auto-redeemed or if an action is required by the recepient. |
| Subscription Is Gift | Whether or not the pre-paid subscription is a gift. |
| Subscription Is Recurring | Whether the pre-paid subscription is recurring. |
| Subscription Last Order Unique Product Basket | Array of unique product names ordered in the latest order per subscription. |
| Subscription Last Order Unique Variant Basket | Array of unique SKUs ordered in the latest order per subscription. |
| Subscription Oms Pre Paid Subscription Id | ID generated by ChordOMS to identify a unique pre-paid subscription. |
| Subscription Oms Subscription Id | Unique key generated by Solidus that identifies a subscription. |
| Subscription Pre Paid Subscription Id | Chord generated unique id for the pre-pay subscription. |
| Subscription State | The current state of the subscription, enhanced with values for \`paused\` if the subscription is active and paused. |
| Subscription Tags | The list of tags associated with a subscription. |
| Subscription Tags Count | The number of tags associated with a subscription. |
| Subscription Unique Product Basket | Array of unique product names ever ordered per subscription. |
| Subscription Unique Variant Basket | Array of unique SKUs ever ordered per subscription. |
| User Completed Oms Order Ids | List of completed OMS order ids by a user. |
| User Completed Order Ids | List of completed order ids by a user. |
| User Credit Category Basket | Array of credit categories (Gift Card, Reimbursement, Referral Credits, Prepaid Subscription, GMA) issued per user. |
| User Email | Email address of the user. |
| User First Completed Oms Order Id | OMS order id of the first order completed by a user. |
| User First Completed Order Id | Unique order id of the first order completed by a user. |
| User First Order Unique Ordered Products | Unique products ordered by the user in their first completed order. |
| User First Order Unique Ordered Skus | Unique SKUs ordered by the user in their first completed order. |
| User Has Ordered A La Carte | Whether or not the user has had at least one order that is not part of a subscription. |
| User Has Promo Applied In First Order | Whether or not the user has a promo applied to their first completed order. |
| User Has Subscription In First Order | Whether or not the user's first order is linked to a subscription. |
| User Id | Unique key generated by Chord to identify a unique user. |
| User Is Active Subscriber | Whether or not the user has an active subscription with at least one completed subscription order. An active subscription is one that is not cancelled or paused. |
| User Is Customer | Whether or not the user is a customer. |
| User Is New Customer | Whether or not the user is a new customer. |
| User Is Not Customer | Whether or not the user is not a customer. |
| User Is Returning Customer | Whether or not the user is a returning customer. |
| User Is Subscriber | Whether or not the user has completed at least one subscription order. |
| User Login | The login email address of the user. |
| User Name | Full name of the user. |
| User Number Of Completed A La Carte Orders | Total amount of orders completed by a user that are a la carte. |
| User Number Of Completed Subscription Orders | Total amount of orders completed by a user that was part of a subscription. |
| User Number Of Orders With Promos | The count of completed orders with a promo applied. |
| User Number Of Subscriptions | Total amount of subscriptions linked to a user. |
| User Oms User Id | Unique key generated by Solidus that identifies a user. |
| User Phone | Phone number of the user. |
| User Total Completed Order Count | Total amount of orders completed by a user. |
| User Unique Ordered Products | Unique products ordered by the user across all orders. |
| User Unique Ordered Skus | Unique SKUs ordered by the user across all orders. |
| Billing Address Created At (Universal) | Timestamp at which the address row was created - Universal Time Zone. |
| Billing Address Updated At (Universal) | Timestamp at which the address row was last updated - Universal Time Zone. |
| Order Approved At (Universal) | Reflects when the entity was approved in Solidus - Universal Time Zone. |
| Order Canceled At (Universal) | Reflects when the order was cancelled - Universal Time Zone. |
| Order Completed At (Central) | Reflects when the entity was moved to the 'completed' state - Cental Time Zone. |
| Order Completed At (Eastern) | Reflects when the entity was moved to the 'completed' state - Eastern Time Zone. |
| Order Completed At (Mountain) | Reflects when the entity was moved to the 'completed' state - Mountain Time Zone. |
| Order Completed At (Pacific) | Reflects when the entity was moved to the 'completed' state - Pacific Time Zone. |
| Order Completed At (Universal) | Reflects when the entity was moved to the 'completed' state - Universal Time Zone. |
| Order Created At (Central) | Reflects when the entity was first created in Solidus - Cental Time Zone. |
| Order Created At (Eastern) | Reflects when the entity was first created in Solidus - Eastern Time Zone. |
| Order Created At (Mountain) | Reflects when the entity was first created in Solidus - Mountain Time Zone. |
| Order Created At (Pacific) | Reflects when the entity was first created in Solidus - Pacific Time Zone. |
| Order Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Order First Fulfillment Fulfilled At (Universal) | Timestamp at which the first shipment for that order was shipped - Universal Time Zone. |
| Order Last Adjustment Refund At (Universal) | Timestamp of the last return adjustment for an order - Universal Time Zone. |
| Order Last Adjustment Replacement At (Universal) | Timestamp of the last replacement adjustment for an order - Universal Time Zone. |
| Order Last Fulfillment Fulfilled At (Universal) | Timestamp at which the last shipment for that order was shipped - Universal Time Zone. |
| Order Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| Referral Converted At (Universal) | Reflects when the referral entity was first converted in Solidus - Universal Time Zone. |
| Referral Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Referral Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| Referrer Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Referrer Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| Shipping Address Created At (Universal) | Timestamp at which the address row was created - Universal Time Zone. |
| Shipping Address Updated At (Universal) | Timestamp at which the address row was last updated - Universal Time Zone. |
| Subscription Actionable Date (Universal) | The date of the next subscription installment. This date is updated after each successful installment. Subscriptions in an inactive state will be null - Universal Time Zone. |
| Subscription Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Subscription First Order Completed At (Universal) | The timestamp of the subscription's first completed order - Universal Time Zone. |
| Subscription Last Order Completed At (Universal) | The timestamp of the subscription's last completed order - Universal Time Zone. |
| Subscription Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| User Created At (Universal) | Timestamp at which the users row was created - Universal Time Zone. |
| User Date Of Birth (Universal) | Date of birth of the user - Universal Time Zone. |
| User Deleted At (Universal) | Timestamp at which the user's account was deleted - Universal Time Zone. |
| User First Order Completed At (Universal) | The timestamp of the user's first completed order - Universal Time Zone. |
| User First Subscription Order Completed At (Universal) | The timestamp of the user's first completed subscription order, regardless of subsequent subscriptions - Universal Time Zone. |
| User Last Order Completed At (Universal) | The timestamp of the user's last completed order - Universal Time Zone. |
| User Last Sign In At (Universal) | The last sign in timestamp for the user - Universal Time Zone. |
| User Updated At (Universal) | Timestamp at which the users row was last updated - Universal Time Zone. |
| Average Additional Tax Total | Total additional taxes for an order. |
| Average Adjustment Fulfillment Tax Total | Total adjustment shipment taxes for an order. |
| Average Adjustment Fulfillment Total | Total shipment adjustments applied to an order. |
| Average Adjustment Other Charges Total | Total of included additional adjustment charges paid for an order. |
| Average Adjustment Other Credits Total | Total of credits issued for an order. |
| Average Adjustment Refund Total | Total of return dollars for an order. |
| Average Adjustment Replacement Total | Total of replacement dollars for an order. |
| Average Adjustment Rma Refund Total | Total of refund dollards associated to an order that was returned via the RMA functionality of the Chord OMS. |
| Average Adjustment Tax Total | Total adjustment taxes an order. |
| Average Adjustment Total | Total of adjustment applied for an order as on the order. |
| Average Applied Gift Card Total | Total of gift card dollars that were used as a payment method in the order |
| Average Commission Total | Commission for an order. |
| Average Fulfillment Total | Total shipment for an order. |
| Average Gross Revenue | Gross amount of revenue generated by the order including items and shipments totals. Gross revenue = total - included\_tax\_total + shipment\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Average Included Tax Total | Total included taxes for an order. |
| Average Item Total | Total price for the order before adjustments. |
| Average Net Revenue | Net revenue generated by the order's items after promotions. Net revenue = total - included\_tax\_total + shipment\_total + adjustment\_total - additional\_tax\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Average Pre Paid Purchase Total | The amount of the order that was purchased as a pre-payment; this could be a gift subscription, pre-pay subscription, or gift card. |
| Average Pre Paid Redemption Total | The amount of the order that was the redemption of a pre-payment; this could be the redemption of a gift subscription, pre-pay subscription, or gift card. |
| Average Promo Total | Promotions applied to an order. |
| Average Purchased Gift Card Total | Total of gift card dollars that were purchased in the order. |
| Average Reimbursement Credit Total | The amount of store credits owed back in an order |
| Average Tax Total | Total taxes for an order. |
| Average Total Price | Total to be paid by the customer for an order. |
| Average Transaction Total | Total paid by the customer for a completed order. |
| Additional Tax Total | Total additional taxes for an order. |
| Adjustment Fulfillment Tax Total | Total adjustment shipment taxes for an order. |
| Adjustment Fulfillment Total | Total shipment adjustments applied to an order. |
| Adjustment Other Charges Total | Total of included additional adjustment charges paid for an order. |
| Adjustment Other Credits Total | Total of credits issued for an order. |
| Adjustment Refund Total | Total of return dollars for an order. |
| Adjustment Replacement Total | Total of replacement dollars for an order. |
| Adjustment Rma Refund Total | Total of refund dollards associated to an order that was returned via the RMA functionality of the Chord OMS. |
| Adjustment Tax Total | Total adjustment taxes an order. |
| Adjustment Total | Total of adjustment applied for an order as on the order. |
| Applied Gift Card Total | Total of gift card dollars that were used as a payment method in the order |
| Commission Total | Commission for an order. |
| Fulfillment Total | Total shipment for an order. |
| Gross Revenue | Gross amount of revenue generated by the order including items and shipments totals. Gross revenue = total - included\_tax\_total + shipment\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Included Tax Total | Total included taxes for an order. |
| Item Total | Total price for the order before adjustments. |
| Net Revenue | Net revenue generated by the order's items after promotions. Net revenue = total - included\_tax\_total + shipment\_total + adjustment\_total - additional\_tax\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Pre Paid Purchase Total | The amount of the order that was purchased as a pre-payment; this could be a gift subscription, pre-pay subscription, or gift card. |
| Pre Paid Redemption Total | The amount of the order that was the redemption of a pre-payment; this could be the redemption of a gift subscription, pre-pay subscription, or gift card. |
| Total Price | Total to be paid by the customer for an order. |
| Promo Total | Promotions applied to an order. |
| Purchased Gift Card Total | Total of gift card dollars that were purchased in the order. |
| Reimbursement Credit Total | The amount of store credits owed back in an order |
| Tax Total | Total taxes for an order. |
| Transaction Total | Total paid by the customer for a completed order. |
### order\_discount\_codes
| Name | Description |
| ---------------------------- | -------------------------------------- |
| Order Applied Discount Codes | Discount code(s) applied to the order. |
### order\_discount\_names
| Name | Description |
| ---------------------------- | -------------------------------------- |
| Order Applied Discount Names | Discount name(s) applied to the order. |
### order\_tags
| Name | Description |
| ---------- | ---------------------------------- |
| Order Tags | Order tag(s) applied to the order. |
### subscription\_tags
| Name | Description |
| ----------------- | ----------------------------------------- |
| Subscription Tags | Subscription tag(s) applied to the order. |
[title] Line Items By Units
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Chord OMS/
### **x\_fct\_trans\_line\_items**
| Name | Description |
| ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Affiliate Email | Email address of the affiliate. |
| Affiliate Id | Unique key generated by Chord to identify a unique affiliate. |
| Affiliate Name | Full name of the user. |
| Affiliate Seen Emails | List of email addresses seen. |
| Affiliate User Id | Unique key generated by Chord to identify a unique user. |
| Billing Address Address1 | The street address of the customer. |
| Billing Address Address2 | The optional second address of the customer. |
| Billing Address Alternative Phone | The customer's alternative phone number. |
| Billing Address City | The city where the address is. |
| Billing Address Company | A company name. |
| Billing Address Country Abbr | |
| Billing Address Country Name | Full name of the country. |
| Billing Address Firstname | First name of the customer. |
| Billing Address Id | Unique key generated by Chord to identify a unique address. |
| Billing Address Lastname | Last name of the customer. |
| Billing Address Oms Address Id | Unique key generated by Solidus that identifies an address. |
| Billing Address Phone | The customer's phone number. |
| Billing Address State Abbr | |
| Billing Address State Name | Full name of the state. |
| Billing Address Zipcode | The postal code. |
| Bundle All Parts | List that contains all of the parts skus for a specific bundle. |
| Bundle Id | Unique key of line item variant if it is a bundle or kit, coalesce of bundles from line\_item\_part\_bundles and parts\_and\_bundles. |
| Bundle Is Bundle | Whether or not the bundle is an actual bundle. |
| Bundle Is Oms Bundle | Whether or not the bundle is an actual Chord OMS bundle. |
| Bundle Name | The name of the bundle. |
| Bundle Variant Sku | Variant sku associated with the bundle variant id. |
| Line Item Adjustment Types | List of distinct adjustment reasons for adjustments made to the order line item. |
| Line Item Contains Refund | Whether or not the line item contains a partial or full refund. Refunds can be done via adjustments, RMAs or order cancellations. |
| Line Item Contains Replacement | Whether or not the line item contains a replacement adjustment or has been partially or fully replaced via the Chord OMS RMA functionality. |
| Line Item Contains Return | Whether or not the line item has been partially or fully returned via the Chord OMS RMA functionality. |
| Line Item Fulfillment State | Status of the shipment. |
| Line Item Id | Unique key generated by Chord to identify a unique line item. |
| Line Item Is Subscription Item | Whether or not the line item is part of a subscription. |
| Line Item Oms Line Item Id | Unique key generated by Solidus that identifies a line item. |
| Line Item Price | The price of the variant. |
| Line Item Quantity | The quantity of how many of said variant was purchased. |
| Line Item Unique Line Item Count Per Order | Count of unique line items per order. |
| Order Adjustment Types | List of distinct adjustment reasons for adjustments made to the order. |
| Order Admin Url | The Admin URL of pointing to the order. |
| Order Applied Discount Codes | List of promotion codes applied to the order. |
| Order Applied Discount Codes Count | Count of promotion codes applied to the order. |
| Order Applied Discount Ids | List of promotion ids applied to the order. |
| Order Applied Discount Names | List of promotion names applied to the order. |
| Order Applied Discount Names Count | Count of promotion names applied to the order. |
| Order Cart Url | Url of the cart which contains the order. |
| Order Channel | The channel from which the order is created. |
| Order Completed Order Rank By Subscription | Allows to rank completed orders by completion date for a subscription. |
| Order Completed Order Rank By User | Allows to rank completed orders by completion date for a user. |
| Order Contains Refund | Whether or not the order contains refund adjustments or refunds that are processed outside of the Chord OMS adjustment systems (for example via RMAs or cancellations). |
| Order Contains Replacement | Whether or not the order contains replacement adjustments or shipped replacement items (following an RMA authorization). |
| Order Contains Return | Whether or not the order contains returns (authorized RMAs). |
| Order Contains Rma Refund | Whether or not the order contains RMA refunds (refunds issued after an RMA was requested and authorized). |
| Order Contains Rma Store Credits | This column is not documented. |
| Order Currency | The currency for this order. |
| Order Customer Lifetime Month | Number of months between the current order's completion date and the user's first order completion date. First orders have a value of 1. |
| Order Customer Lifetime Week | Number of weeks between the current order's completion date and the user's first order completion date. First orders always have a value of 1. |
| Order Email | The email address of the customer that made the order. |
| Order Financial State | The current payment state of the order. |
| Order Fulfillment Ids | Array of unique keys generated by Chord to identify the unique shipments for an order. |
| Order Fulfillment Numbers | The unique identifier for this shipment. |
| Order Fulfillment State | The current shipment state of the order. |
| Order Has Discount | Whether or not the order has promotions applied to it. |
| Order Has Order Tags | Whether or not that order has tags. |
| Order Hours From Order To First Fulfillment | Number of hours between order completion and first order shipment; how long it takes a company to get the initial product out to a customer. |
| Order Hours From Order To Last Fulfillment | Number of hours between order completion and last order shipment. |
| Order Id | Unique key generated by Chord to identify a unique order. |
| Order Is Canceled | Whether or not the order is canceled. The order is considered canceled when the canceled\_at date is not null. |
| Order Is Completed | Whether or not that order is completed. The order is considered completed when the completed\_at date is not null. This means that the order does not necessarily have a state = 'complete', since states can change after the order completion (for example in the case of a refund). |
| Order Is First Completed Order | Whether or not that order was the first completed order for a user. |
| Order Is First Order | Whether or not that order was the first order for a user. |
| Order Is First Subscription Completed Order | Whether or not that order was the first completed order for a subscription. |
| Order Is First Subscription Order | Whether or not that order was the first order for a subscription. |
| Order Is Fulfilled | Whether or not that order has shipped. |
| Order Is Part Of Subscription | Whether or not that order is part of a subscription. |
| Order Is Pre Paid Purchase | Whether the order the orderincludes the purchase of a pre-payment; this could be a gift subscription, pre-pay subscription, or gift card. |
| Order Is Pre Paid Redemption | Whether the order included the redemption of a pre-payment; this could be the redemption of a gift subscription, pre-pay subscription, or gift card. |
| Order Is Referred By Affiliate | Whether or not the user is referred by an affiliate. |
| Order Is Referred By Referrer | Whether or not the user is referred by a referrer. |
| Order Is Replacement | True when the order is a replacement order. |
| Order Is Suspicious Referral Conversion | Wether this represents a suspicous referral conversions or not. |
| Order Item Id | Unique key generated by Chord to identify a unique order. |
| Order Item Line Items Quantity | Sum of line items quantities per order. |
| Order Item Product Basket | List of product names per in the order. |
| Order Item Product Basket Count | Number of products in the order. |
| Order Product Basket | The titles of products for a given order array converted to a string. |
| Order Item Total Line Item Unit Quantity | Sum of line item units in the order. |
| Order Item Total Line Items Quantity | Sum of line items quantities per order. |
| Order Item Unique Product Basket | List of unique product names per in the order. |
| Order Item Unique Product Basket Count | Number of unique products in the order. |
| Order Unique Product Basket | The list of unique products for a given order array converted to a string. |
| Order Item Unique Unit Basket | List of unique units in the order. |
| Order Item Unique Unit Basket Count | Count of unique units in the order. |
| Order Unit Basket | The list of units for a given order array converted to a string. |
| Order Item Unique Variant Basket | List of unique variant names per in the order. |
| Order Item Unique Variant Basket Count | Number of unique variants in the order. |
| Order Unique Variant Basket | The list of unique variants for a given order array converted to a string. |
| Order Item Unit Basket | List of all units in the order. |
| Order Item Unit Basket Count | Count of all units in the order. |
| Order Unique Unit Basket | The list of unique units for a given order array converted to a string. |
| Order Item Variant Basket | List of variant names per in the order. |
| Order Item Variant Basket Count | Number of variants in the order. |
| Order Variant Basket | The titles of variants for a given order array converted to a string. |
| Order Number | Human-readable unique key generated by Solidus that identifies an order. It begins with a set of Tenant-Store defined letters and ends in a nine-digit number (for example, CHORD-123456789). This number is shown to the users in various places. These combinations are unique for a given Store. |
| Order Oms Order Id | Unique key generated by Solidus that identifies an order. |
| Order Rank By User | Allows to rank completed orders by completion date for a user. |
| Order Tags | List of tags associated to the order. |
| Order Tags Count | Number of tags associated to the order. |
| Order Referral Conversion Suspicious Reasons | A list of reasons explaining why the referral conversion is suspicious. |
| Order Referrer User Email | The email address of the customer identified with the referral. |
| Order Special Instructions | Any special shipping instructions that have been specified by the customer during checkout. |
| Order State | The current state of the order. |
| Order Store Id | Unique key generated by our models that uniquifies a store. |
| Order Store Name | The name of the store. |
| Order Store Oms Admin Url | The Admin URL of that OMS. |
| Order Store Oms Id | Unique key generated by Chord that uniquifies an OMS. |
| Order Store Oms Store Id | Unique key generated by our models that uniquifies a store. |
| Order Store Oms Type | The type of the OMS. |
| Order Store Id | Unique key generated by our models that uniquifies a store. |
| Order Store Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Order Store Url | The Storefront URL of of the store. |
| Order Subscription Customer Lifetime Month | Number of months between the current order's completion date and the user's first subscription order completion date. First orders have a value of 1. |
| Order Subscription Customer Lifetime Week | Number of weeks between the current order's completion date and the user's first subscription order completion date. First orders always have a value of 1. |
| Order User Referral Code | Unique key generated by Solidus that represents the user's referral code. |
| Order Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store. |
| Product Description | The description of the product. |
| Product Id | Unique key generated by Chord to identify a unique product. |
| Product Is Adult Signature Required | If an adult's signature is required. |
| Product Is Promotionable | Whether promotions can apply to the product. |
| Product Name | The name of the product. |
| Product Oms Product Id | Unique key generated by Solidus that identifies a product. |
| Product Property Gender | Product property gender. |
| Product Slug | The slug of the product. |
| Product Store Id | Unique key generated by our models that uniquifies a store. |
| Product Store Name | The name of the store. |
| Product Store Oms Admin Url | The Admin URL of that OMS. |
| Product Store Oms Id | Unique key generated by Chord that uniquifies an OMS. |
| Product Store Oms Store Id | Unique key generated by our models that uniquifies a store. |
| Product Store Oms Type | The type of the OMS. |
| Product Store Id | Unique key generated by our models that uniquifies a store. |
| Product Store Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Product Store Url | The Storefront URL of of the store. |
| Shipping Address Address1 | The street address of the customer. |
| Shipping Address Address2 | The optional second address of the customer. |
| Shipping Address Alternative Phone | The customer's alternative phone number. |
| Shipping Address City | The city where the address is. |
| Shipping Address Company | A company name. |
| Shipping Address Country Abbr | |
| Shipping Address Country Name | Full name of the country. |
| Shipping Address Firstname | First name of the customer. |
| Shipping Address Id | Unique key generated by Chord to identify a unique address. |
| Shipping Address Lastname | Last name of the customer. |
| Shipping Address Oms Address Id | Unique key generated by Solidus that identifies an address. |
| Shipping Address Phone | The customer's phone number. |
| Shipping Address State Abbr | |
| Shipping Address State Name | Full name of the state. |
| Shipping Address Zipcode | The postal code. |
| Subscription Completed Oms Order Ids | List of completed OMS order ids by a subscription. |
| Subscription Completed Order Count | Total amount of orders completed by a subscription. |
| Subscription Completed Order Ids | List of completed order ids by a subscription. |
| Subscription First Order Unique Product Basket | Array of unique product names ordered in the first order per subscription. |
| Subscription First Order Unique Variant Basket | Array of unique SKUs ordered in the first order per subscription. |
| Subscription Has Subscription Tags | Whether or not the subscription has tags. |
| Subscription Id | Unique key generated by Solidus that identifies a subscription. |
| Subscription Interval In Days | The number of days in the subscription interval. |
| Subscription Is Auto Redeemed | Whether the pre-paid subscription will be auto-redeemed or if an action is required by the recepient. |
| Subscription Is Gift | Whether or not the pre-paid subscription is a gift. |
| Subscription Is Recurring | Whether the pre-paid subscription is recurring. |
| Subscription Last Order Unique Product Basket | Array of unique product names ordered in the latest order per subscription. |
| Subscription Last Order Unique Variant Basket | Array of unique SKUs ordered in the latest order per subscription. |
| Subscription Oms Pre Paid Subscription Id | ID generated by ChordOMS to identify a unique pre-paid subscription. |
| Subscription Oms Subscription Id | Unique key generated by Solidus that identifies a subscription. |
| Subscription Pre Paid Subscription Id | Chord generated unique id for the pre-pay subscription. |
| Subscription State | The current state of the subscription, enhanced with values for \`paused\` if the subscription is active and paused. |
| Subscription Tags | The list of tags associated with a subscription. |
| Subscription Tags Count | The number of tags associated with a subscription. |
| Subscription Unique Product Basket | Array of unique product names ever ordered per subscription. |
| Subscription Unique Variant Basket | Array of unique SKUs ever ordered per subscription. |
| User Completed Oms Order Ids | List of completed OMS order ids by a user. |
| User Completed Order Ids | List of completed order ids by a user. |
| User Credit Category Basket | Array of credit categories (Gift Card, Reimbursement, Referral Credits, Prepaid Subscription, GMA) issued per user. |
| User Email | Email address of the user. |
| User First Completed Oms Order Id | OMS order id of the first order completed by a user. |
| User First Completed Order Id | Unique order id of the first order completed by a user. |
| User First Order Unique Ordered Products | Unique products ordered by the user in their first completed order. |
| User First Order Unique Ordered Skus | Unique SKUs ordered by the user in their first completed order. |
| User Has Ordered A La Carte | Whether or not the user has had at least one order that is not part of a subscription. |
| User Has Promo Applied In First Order | Whether or not the user has a promo applied to their first completed order. |
| User Has Subscription In First Order | Whether or not the user's first order is linked to a subscription. |
| User Id | Unique key generated by Chord to identify a unique user. |
| User Is Active Subscriber | Whether or not the user has an active subscription with at least one completed subscription order. An active subscription is one that is not cancelled or paused. |
| User Is Customer | Whether or not the user is a customer. |
| User Is New Customer | Whether or not the user is a new customer. |
| User Is Not Customer | Whether or not the user is not a customer. |
| User Is Returning Customer | Whether or not the user is a returning customer. |
| User Is Subscriber | Whether or not the user has completed at least one subscription order. |
| User Login | The login email address of the user. |
| User Name | Full name of the user. |
| User Number Of Completed A La Carte Orders | Total amount of orders completed by a user that are a la carte. |
| User Number Of Completed Subscription Orders | Total amount of orders completed by a user that was part of a subscription. |
| User Number Of Orders With Promos | The count of completed orders with a promo applied. |
| User Number Of Subscriptions | Total amount of subscriptions linked to a user. |
| User Oms User Id | Unique key generated by Solidus that identifies a user. |
| User Phone | Phone number of the user. |
| User Total Completed Order Count | Total amount of orders completed by a user. |
| User Unique Ordered Products | Unique products ordered by the user across all orders. |
| User Unique Ordered Skus | Unique SKUs ordered by the user across all orders. |
| Variant Cost Price | The manufacturing cost of the variant. |
| Variant Depth | The depth of the variant. |
| Variant Height | The height of the variant. |
| Variant Id | Unique key generated by Chord to identify a unique product variant. |
| Variant Is Backorderable | Whether the stock item has at least one location where it is back-orderable or not. |
| Variant Is Inventory Tracked | Whether the inventory should or should not be tracked for this variant. |
| Variant Is Master | Whether this represents the master SKU or not. |
| Variant Is Subscribable | Whether or not a customer can ask to subscribe to this product. |
| Variant Oms Variant Id | Unique key generated by Solidus that identifies a variant. |
| Variant Option Color | Color of the variant. |
| Variant Option Format | Format of the variant. |
| Variant Option Quantity | Quantity of item for the variant. |
| Variant Option Size | Size of the variant. |
| Variant Position | The position of the variant in the list of variants. |
| Variant Sku | The SKU of the variant. |
| Variant Weight | The weight of the variant. |
| Variant Width | The weight of the variant. |
| Billing Address Created At (Universal) | Timestamp at which the address row was created - Universal Time Zone. |
| Billing Address Updated At (Universal) | Timestamp at which the address row was last updated - Universal Time Zone. |
| Line Item Last Adjustment Refund At (Universal) | Timestamp of the last return adjustment for an order line item - Universal Time Zone. |
| Line Item Last Adjustment Replacement At (Universal) | Timestamp of the last replacement adjustment for an order line item - Universal Time Zone. |
| Order Approved At (Universal) | Reflects when the entity was approved in Solidus - Universal Time Zone. |
| Order Canceled At (Universal) | Reflects when the order was cancelled - Universal Time Zone. |
| Order Completed At (Central) | Reflects when the entity was moved to the 'completed' state - Cental Time Zone. |
| Order Completed At (Eastern) | Reflects when the entity was moved to the 'completed' state - Eastern Time Zone. |
| Order Completed At (Mountain) | Reflects when the entity was moved to the 'completed' state - Mountain Time Zone. |
| Order Completed At (Pacific) | Reflects when the entity was moved to the 'completed' state - Pacific Time Zone. |
| Order Completed At (Universal) | Reflects when the entity was moved to the 'completed' state - Universal Time Zone. |
| Order Created At (Central) | Reflects when the entity was first created in Solidus - Cental Time Zone. |
| Order Created At (Eastern) | Reflects when the entity was first created in Solidus - Eastern Time Zone. |
| Order Created At (Mountain) | Reflects when the entity was first created in Solidus - Mountain Time Zone. |
| Order Created At (Pacific) | Reflects when the entity was first created in Solidus - Pacific Time Zone. |
| Order Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Order First Fulfillment Fulfilled At (Universal) | Timestamp at which the first shipment for that order was shipped - Universal Time Zone. |
| Order Last Adjustment Refund At (Universal) | Timestamp of the last return adjustment for an order - Universal Time Zone. |
| Order Last Adjustment Replacement At (Universal) | Timestamp of the last replacement adjustment for an order - Universal Time Zone. |
| Order Last Fulfillment Fulfilled At (Universal) | Timestamp at which the last shipment for that order was shipped - Universal Time Zone. |
| Order Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| Product Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Product Deleted At (Universal) | Reflects when the entity was deleted - Universal Time Zone. |
| Product Discontinued At (Universal) | Reflects when the entity was discontinued - Universal Time Zone. |
| Product Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| Shipping Address Created At (Universal) | Timestamp at which the address row was created - Universal Time Zone. |
| Shipping Address Updated At (Universal) | Timestamp at which the address row was last updated - Universal Time Zone. |
| Subscription Actionable Date (Universal) | The date of the next subscription installment. This date is updated after each successful installment. Subscriptions in an inactive state will be null - Universal Time Zone. |
| Subscription Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Subscription First Order Completed At (Universal) | The timestamp of the subscription's first completed order - Universal Time Zone. |
| Subscription Last Order Completed At (Universal) | The timestamp of the subscription's last completed order - Universal Time Zone. |
| Subscription Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| User Created At (Universal) | Timestamp at which the users row was created - Universal Time Zone. |
| User Date Of Birth (Universal) | Date of birth of the user - Universal Time Zone. |
| User Deleted At (Universal) | Timestamp at which the user's account was deleted - Universal Time Zone. |
| User First Order Completed At (Universal) | The timestamp of the user's first completed order - Universal Time Zone. |
| User First Subscription Order Completed At (Universal) | The timestamp of the user's first completed subscription order, regardless of subsequent subscriptions - Universal Time Zone. |
| User Last Order Completed At (Universal) | The timestamp of the user's last completed order - Universal Time Zone. |
| User Last Sign In At (Universal) | The last sign in timestamp for the user - Universal Time Zone. |
| User Updated At (Universal) | Timestamp at which the users row was last updated - Universal Time Zone. |
| Variant Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Variant Deleted At (Universal) | Reflects when the entity was deleted - Universal Time Zone. |
| Variant Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| Average Adjusted Total Price | Total price for the line item after adjustments. |
| Average Adjustment Fulfillment Tax Total | Total of adjustment shipment taxes paid for the line item. |
| Average Adjustment Tax Total | Total of included adjustment taxes paid for the line item. |
| Average Adjustment Total | The sum of all adjustment for this line item. |
| Average Order Additional Tax Total | Total additional taxes for an order. |
| Average Order Adjustment Fulfillment Tax Total | Total adjustment shipment taxes for an order. |
| Average Order Adjustment Fulfillment Total | Total shipment adjustments applied to an order. |
| Average Order Adjustment Other Charges Total | Total of included additional adjustment charges paid for an order. |
| Average Order Adjustment Other Credits Total | Total of credits issued for an order. |
| Average Order Adjustment Refund Total | Total of return dollars for an order. |
| Average Order Adjustment Replacement Total | Total of replacement dollars for an order. |
| Average Order Adjustment Rma Refund Total | Total of refund dollards associated to an order that was returned via the RMA functionality of the Chord OMS. |
| Average Order Adjustment Tax Total | Total adjustment taxes an order. |
| Average Order Adjustment Total | Total of adjustment applied for an order as on the order. |
| Average Order Applied Gift Card Total | Total of gift card dollars that were used as a payment method in the order |
| Average Order Commission Total | Commission for an order. |
| Average Order Fulfillment Total | Total shipment for an order. |
| Average Order Gross Revenue | Gross amount of revenue generated by the order including items and shipments totals. Gross revenue = total - included\_tax\_total + shipment\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Average Order Included Tax Total | Total included taxes for an order. |
| Average Order Item Total | Total price for the order before adjustments. |
| Average Order Net Revenue | Net revenue generated by the order's items after promotions. Net revenue = total - included\_tax\_total + shipment\_total + adjustment\_total - additional\_tax\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Average Order Pre Paid Purchase Total | |
| Average Order Pre Paid Redemption Total | |
| Average Order Promo Total | Promotions applied to an order. |
| Average Order Purchased Gift Card Total | Total of gift card dollars that were purchased in the order. |
| Average Order Reimbursement Credit Total | |
| Average Order Tax Total | Total taxes for an order. |
| Average Order Total Price | Total to be paid by the customer for an order. |
| Average Order Transaction Total | Total paid by the customer for a completed order. |
| Average Promo Total | The sum of all of the promo totals from this line items and promotions. |
| Average Quantity | The quantity of how many of said variant was purchased. |
| Average Tax Total | Total of total taxes paid for the line item. |
| Average Total Price | Total price for the line item before adjustments. |
| Adjusted Total Price | Total price for the line item after adjustments. |
| Adjustment Fulfillment Tax Total | Total of adjustment shipment taxes paid for the line item. |
| Adjustment Tax Total | Total of included adjustment taxes paid for the line item. |
| Adjustment Total | The sum of all adjustment for this line item. |
| Order Additional Tax Total | Total additional taxes for an order. |
| Order Adjustment Fulfillment Tax Total | Total adjustment shipment taxes for an order. |
| Order Adjustment Fulfillment Total | Total shipment adjustments applied to an order. |
| Order Adjustment Other Charges Total | Total of included additional adjustment charges paid for an order. |
| Order Adjustment Other Credits Total | Total of credits issued for an order. |
| Order Adjustment Refund Total | Total of return dollars for an order. |
| Order Adjustment Replacement Total | Total of replacement dollars for an order. |
| Order Adjustment Rma Refund Total | Total of refund dollards associated to an order that was returned via the RMA functionality of the Chord OMS. |
| Order Adjustment Tax Total | Total adjustment taxes an order. |
| Order Adjustment Total | Total of adjustment applied for an order as on the order. |
| Order Applied Gift Card Total | Total of gift card dollars that were used as a payment method in the order |
| Order Commission Total | Commission for an order. |
| Order Fulfillment Total | Total shipment for an order. |
| Order Gross Revenue | Gross amount of revenue generated by the order including items and shipments totals. Gross revenue = total - included\_tax\_total + shipment\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Order Included Tax Total | Total included taxes for an order. |
| Order Item Total | Total price for the order before adjustments. |
| Order Net Revenue | Net revenue generated by the order's items after promotions. Net revenue = total - included\_tax\_total + shipment\_total + adjustment\_total - additional\_tax\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Order Pre Paid Purchase Total | |
| Order Pre Paid Redemption Total | |
| Order Promo Total | Promotions applied to an order. |
| Order Purchased Gift Card Total | Total of gift card dollars that were purchased in the order. |
| Order Reimbursement Credit Total | |
| Order Tax Total | Total taxes for an order. |
| Order Total Price | Total to be paid by the customer for an order. |
| Order Transaction Total | Total paid by the customer for a completed order. |
| Total Price | Total price for the line item before adjustments. |
| Promo Total | The sum of all of the promo totals from this line items and promotions. |
| Quantity | The quantity of how many of said variant was purchased. |
| Tax Total | Total of total taxes paid for the line item. |
### **order\_discount\_codes**
| Name | Description |
| ---------------------------- | -------------------------------------- |
| Order Applied Discount Codes | Discount code(s) applied to the order. |
### **order\_discount\_names**
| Name | Description |
| ---------------------------- | -------------------------------------- |
| Order Applied Discount Names | Discount name(s) applied to the order. |
### **order\_tags**
| Name | Description |
| ---------- | ---------------------------------- |
| Order Tags | Order tag(s) applied to the order. |
### **subscription\_tags**
| Name | Description |
| ----------------- | ----------------------------------------- |
| Subscription Tags | Subscription tag(s) applied to the order. |
[title] Users
[path] Chord Data Platform/Data Models/
### New vs. Repeat Users
In purchasing, we have the concept of new vs. returning users or customers:
**New Users: **Whether or not the user is a new user, as defined by if the user has completed a first order.
**Repeat Users: **Whether or not the user is a returning user, as defined by the user has purchased again following a first order.
If analyzing new unique users and repeat unique users in a given period, they can be counted more than once since a user can be both new and repeat in the period when there's more than one purchase. As a result, the count of new users plus the count of repeat users may be greater than the count of total unique users. For example, this user is shown as a new and repeat user in this period and only counted once as a unique customer:
| User OMS User ID | Unique New Customer Count | Unique Repeat Customer Count | Unique Customer Count |
| ---------------- | ------------------------- | ---------------------------- | --------------------- |
| 12345678 | 1 | 1 | 1 |
If we add the purchase dates, we'll see that this user purchased twice over the period analyzed, which is why this user shows as both new and repeat in this period:
| User OMS User ID | Order Completed Date | Unique New Customer Count | Unique Repeat Customer Count | Unique Customer Count |
| ---------------- | -------------------- | ------------------------- | ---------------------------- | --------------------- |
| 12345678 | 1/1/2024 | 1 | 0 | 1 |
| 12345678 | 2/5/2024 | 0 | 1 | 1 |
:::hint{type="success"}
if you have any questions or need help, please reach out to us at [help@chord.co](mailto\:help@chord.co)
:::
[title] Google Ads
[path] Chord Data Platform/Data Activations/Data Activations/Destination Set-up Notes/
*This page describes how to connect Google Ads as a Data Activation*
## Getting Started
Connecting to your Google Ads account is straightforward.
- From the Destinations page, click **New Destination** and select Google Ads from the menu.
- Complete the OAuth flow. Make sure your are signed into a user account that has permissions to both view all of your accounts, as well as submit data to them (readonly accounts will not work).
- Select the Ads account you wish to use with Chord Data Activations. If you'd like to sync to multiple accounts, you will need to add each as its own destination.
| **Object Name** | **Supported?** | **Sync Keys** | **Behaviors** |
| -------------------------------- | -------------- | ------------------------------------------------------------- | ---------------- |
| Call Conversion | ✅ | Caller ID | Update or Create |
| Click Conversion | ✅ | Google Click ID, Google wBraid, Google gBraid, | Update or Create |
| Conversion Adjustment | ✅ | Any unique identifier | Send |
| Customer Match Lists (Audiences) | ✅ | External ID, MAID, Email, First Name, Last Name, Phone Number | Upsert |
| Enhanced Conversion | ✅ | N/A | Update or Create |
# Contact Support
Need help? Contact Chord support at [help@chord.co](mailto\:help@chord.co)!
[title] Line Items
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Chord OMS/
### **x\_fct\_trans\_line\_items**
| Name | Description |
| ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Affiliate Email | Email address of the affiliate. |
| Affiliate Id | Unique key generated by Chord to identify a unique affiliate. |
| Affiliate Name | Full name of the user. |
| Affiliate Seen Emails | List of email addresses seen. |
| Affiliate User Id | Unique key generated by Chord to identify a unique user. |
| Billing Address Address1 | The street address of the customer. |
| Billing Address Address2 | The optional second address of the customer. |
| Billing Address Alternative Phone | The customer's alternative phone number. |
| Billing Address City | The city where the address is. |
| Billing Address Company | A company name. |
| Billing Address Country Abbr | |
| Billing Address Country Name | Full name of the country. |
| Billing Address Firstname | First name of the customer. |
| Billing Address Id | Unique key generated by Chord to identify a unique address. |
| Billing Address Lastname | Last name of the customer. |
| Billing Address Oms Address Id | Unique key generated by Solidus that identifies an address. |
| Billing Address Phone | The customer's phone number. |
| Billing Address State Abbr | |
| Billing Address State Name | Full name of the state. |
| Billing Address Zipcode | The postal code. |
| Bundle All Parts | List that contains all of the parts skus for a specific bundle. |
| Bundle Id | Unique key of line item variant if it is a bundle or kit, coalesce of bundles from line\_item\_part\_bundles and parts\_and\_bundles. |
| Bundle Is Bundle | Whether or not the bundle is an actual bundle. |
| Bundle Is Oms Bundle | Whether or not the bundle is an actual Chord OMS bundle. |
| Bundle Name | The name of the bundle. |
| Bundle Variant Sku | Variant sku associated with the bundle variant id. |
| Line Item Adjustment Types | List of distinct adjustment reasons for adjustments made to the order line item. |
| Line Item Contains Refund | Whether or not the line item contains a partial or full refund. Refunds can be done via adjustments, RMAs or order cancellations. |
| Line Item Contains Replacement | Whether or not the line item contains a replacement adjustment or has been partially or fully replaced via the Chord OMS RMA functionality. |
| Line Item Contains Return | Whether or not the line item has been partially or fully returned via the Chord OMS RMA functionality. |
| Line Item Fulfillment State | Status of the shipment. |
| Line Item Id | Unique key generated by Chord to identify a unique line item. |
| Line Item Is Subscription Item | Whether or not the line item is part of a subscription. |
| Line Item Oms Line Item Id | Unique key generated by Solidus that identifies a line item. |
| Line Item Price | The price of the variant. |
| Line Item Quantity | The quantity of how many of said variant was purchased. |
| Line Item Unique Line Item Count Per Order | Count of unique line items per order. |
| Order Adjustment Types | List of distinct adjustment reasons for adjustments made to the order. |
| Order Admin Url | The Admin URL of pointing to the order. |
| Order Applied Discount Codes | List of promotion codes applied to the order. |
| Order Applied Discount Codes Count | Count of promotion codes applied to the order. |
| Order Applied Discount Ids | List of promotion ids applied to the order. |
| Order Applied Discount Names | List of promotion names applied to the order. |
| Order Applied Discount Names Count | Count of promotion names applied to the order. |
| Order Cart Url | Url of the cart which contains the order. |
| Order Channel | The channel from which the order is created. |
| Order Completed Order Rank By Subscription | Allows to rank completed orders by completion date for a subscription. |
| Order Completed Order Rank By User | Allows to rank completed orders by completion date for a user. |
| Order Contains Refund | Whether or not the order contains refund adjustments or refunds that are processed outside of the Chord OMS adjustment systems (for example via RMAs or cancellations). |
| Order Contains Replacement | Whether or not the order contains replacement adjustments or shipped replacement items (following an RMA authorization). |
| Order Contains Return | Whether or not the order contains returns (authorized RMAs). |
| Order Contains Rma Refund | Whether or not the order contains RMA refunds (refunds issued after an RMA was requested and authorized). |
| Order Contains Rma Store Credits | This column is not documented. |
| Order Currency | The currency for this order. |
| Order Customer Lifetime Month | Number of months between the current order's completion date and the user's first order completion date. First orders have a value of 1. |
| Order Customer Lifetime Week | Number of weeks between the current order's completion date and the user's first order completion date. First orders always have a value of 1. |
| Order Email | The email address of the customer that made the order. |
| Order Financial State | The current payment state of the order. |
| Order Fulfillment Ids | Array of unique keys generated by Chord to identify the unique shipments for an order. |
| Order Fulfillment Numbers | The unique identifier for this shipment. |
| Order Fulfillment State | The current shipment state of the order. |
| Order Has Discount | Whether or not the order has promotions applied to it. |
| Order Has Order Tags | Whether or not that order has tags. |
| Order Hours From Order To First Fulfillment | Number of hours between order completion and first order shipment; how long it takes a company to get the initial product out to a customer. |
| Order Hours From Order To Last Fulfillment | Number of hours between order completion and last order shipment. |
| Order Id | Unique key generated by Chord to identify a unique order. |
| Order Is Canceled | Whether or not the order is canceled. The order is considered canceled when the canceled\_at date is not null. |
| Order Is Completed | Whether or not that order is completed. The order is considered completed when the completed\_at date is not null. This means that the order does not necessarily have a state = 'complete', since states can change after the order completion (for example in the case of a refund). |
| Order Is First Completed Order | Whether or not that order was the first completed order for a user. |
| Order Is First Order | Whether or not that order was the first order for a user. |
| Order Is First Subscription Completed Order | Whether or not that order was the first completed order for a subscription. |
| Order Is First Subscription Order | Whether or not that order was the first order for a subscription. |
| Order Is Fulfilled | Whether or not that order has shipped. |
| Order Is Part Of Subscription | Whether or not that order is part of a subscription. |
| Order Is Pre Paid Purchase | Whether the order the orderincludes the purchase of a pre-payment; this could be a gift subscription, pre-pay subscription, or gift card. |
| Order Is Pre Paid Redemption | Whether the order included the redemption of a pre-payment; this could be the redemption of a gift subscription, pre-pay subscription, or gift card. |
| Order Is Referred By Affiliate | Whether or not the user is referred by an affiliate. |
| Order Is Referred By Referrer | Whether or not the user is referred by a referrer. |
| Order Is Replacement | True when the order is a replacement order. |
| Order Is Suspicious Referral Conversion | Wether this represents a suspicous referral conversions or not. |
| Order Item Id | Unique key generated by Chord to identify a unique order. |
| Order Item Line Items Quantity | Sum of line items quantities per order. |
| Order Item Product Basket | List of product names per in the order. |
| Order Item Product Basket Count | Number of products in the order. |
| Order Product Basket | The titles of products for a given order array converted to a string. |
| Order Item Total Line Item Unit Quantity | Sum of line item units in the order. |
| Order Item Total Line Items Quantity | Sum of line items quantities per order. |
| Order Item Unique Product Basket | List of unique product names per in the order. |
| Order Item Unique Product Basket Count | Number of unique products in the order. |
| Order Unique Product Basket | The list of unique products for a given order array converted to a string. |
| Order Item Unique Unit Basket | List of unique units in the order. |
| Order Item Unique Unit Basket Count | Count of unique units in the order. |
| Order Unit Basket | The list of units for a given order array converted to a string. |
| Order Item Unique Variant Basket | List of unique variant names per in the order. |
| Order Item Unique Variant Basket Count | Number of unique variants in the order. |
| Order Unique Variant Basket | The list of unique variants for a given order array converted to a string. |
| Order Item Unit Basket | List of all units in the order. |
| Order Item Unit Basket Count | Count of all units in the order. |
| Order Unique Unit Basket | The list of unique units for a given order array converted to a string. |
| Order Item Variant Basket | List of variant names per in the order. |
| Order Item Variant Basket Count | Number of variants in the order. |
| Order Variant Basket | The titles of variants for a given order array converted to a string. |
| Order Number | Human-readable unique key generated by Solidus that identifies an order. It begins with a set of Tenant-Store defined letters and ends in a nine-digit number (for example, CHORD-123456789). This number is shown to the users in various places. These combinations are unique for a given Store. |
| Order Oms Order Id | Unique key generated by Solidus that identifies an order. |
| Order Rank By User | Allows to rank completed orders by completion date for a user. |
| Order Tags | List of tags associated to the order. |
| Order Tags Count | Number of tags associated to the order. |
| Order Referral Conversion Suspicious Reasons | A list of reasons explaining why the referral conversion is suspicious. |
| Order Referrer User Email | The email address of the customer identified with the referral. |
| Order Special Instructions | Any special shipping instructions that have been specified by the customer during checkout. |
| Order State | The current state of the order. |
| Order Store Id | Unique key generated by our models that uniquifies a store. |
| Order Store Name | The name of the store. |
| Order Store Oms Admin Url | The Admin URL of that OMS. |
| Order Store Oms Id | Unique key generated by Chord that uniquifies an OMS. |
| Order Store Oms Store Id | Unique key generated by our models that uniquifies a store. |
| Order Store Oms Type | The type of the OMS. |
| Order Store Id | Unique key generated by our models that uniquifies a store. |
| Order Store Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Order Store Url | The Storefront URL of of the store. |
| Order Subscription Customer Lifetime Month | Number of months between the current order's completion date and the user's first subscription order completion date. First orders have a value of 1. |
| Order Subscription Customer Lifetime Week | Number of weeks between the current order's completion date and the user's first subscription order completion date. First orders always have a value of 1. |
| Order User Referral Code | Unique key generated by Solidus that represents the user's referral code. |
| Order Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store. |
| Product Description | The description of the product. |
| Product Id | Unique key generated by Chord to identify a unique product. |
| Product Is Adult Signature Required | If an adult's signature is required. |
| Product Is Promotionable | Whether promotions can apply to the product. |
| Product Name | The name of the product. |
| Product Oms Product Id | Unique key generated by Solidus that identifies a product. |
| Product Property Gender | Product property gender. |
| Product Slug | The slug of the product. |
| Product Store Id | Unique key generated by our models that uniquifies a store. |
| Product Store Name | The name of the store. |
| Product Store Oms Admin Url | The Admin URL of that OMS. |
| Product Store Oms Id | Unique key generated by Chord that uniquifies an OMS. |
| Product Store Oms Store Id | Unique key generated by our models that uniquifies a store. |
| Product Store Oms Type | The type of the OMS. |
| Product Store Id | Unique key generated by our models that uniquifies a store. |
| Product Store Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Product Store Url | The Storefront URL of of the store. |
| Shipping Address Address1 | The street address of the customer. |
| Shipping Address Address2 | The optional second address of the customer. |
| Shipping Address Alternative Phone | The customer's alternative phone number. |
| Shipping Address City | The city where the address is. |
| Shipping Address Company | A company name. |
| Shipping Address Country Abbr | |
| Shipping Address Country Name | Full name of the country. |
| Shipping Address Firstname | First name of the customer. |
| Shipping Address Id | Unique key generated by Chord to identify a unique address. |
| Shipping Address Lastname | Last name of the customer. |
| Shipping Address Oms Address Id | Unique key generated by Solidus that identifies an address. |
| Shipping Address Phone | The customer's phone number. |
| Shipping Address State Abbr | |
| Shipping Address State Name | Full name of the state. |
| Shipping Address Zipcode | The postal code. |
| Subscription Completed Oms Order Ids | List of completed OMS order ids by a subscription. |
| Subscription Completed Order Count | Total amount of orders completed by a subscription. |
| Subscription Completed Order Ids | List of completed order ids by a subscription. |
| Subscription First Order Unique Product Basket | Array of unique product names ordered in the first order per subscription. |
| Subscription First Order Unique Variant Basket | Array of unique SKUs ordered in the first order per subscription. |
| Subscription Has Subscription Tags | Whether or not the subscription has tags. |
| Subscription Id | Unique key generated by Solidus that identifies a subscription. |
| Subscription Interval In Days | The number of days in the subscription interval. |
| Subscription Is Auto Redeemed | Whether the pre-paid subscription will be auto-redeemed or if an action is required by the recepient. |
| Subscription Is Gift | Whether or not the pre-paid subscription is a gift. |
| Subscription Is Recurring | Whether the pre-paid subscription is recurring. |
| Subscription Last Order Unique Product Basket | Array of unique product names ordered in the latest order per subscription. |
| Subscription Last Order Unique Variant Basket | Array of unique SKUs ordered in the latest order per subscription. |
| Subscription Oms Pre Paid Subscription Id | ID generated by ChordOMS to identify a unique pre-paid subscription. |
| Subscription Oms Subscription Id | Unique key generated by Solidus that identifies a subscription. |
| Subscription Pre Paid Subscription Id | Chord generated unique id for the pre-pay subscription. |
| Subscription State | The current state of the subscription, enhanced with values for \`paused\` if the subscription is active and paused. |
| Subscription Tags | The list of tags associated with a subscription. |
| Subscription Tags Count | The number of tags associated with a subscription. |
| Subscription Unique Product Basket | Array of unique product names ever ordered per subscription. |
| Subscription Unique Variant Basket | Array of unique SKUs ever ordered per subscription. |
| User Completed Oms Order Ids | List of completed OMS order ids by a user. |
| User Completed Order Ids | List of completed order ids by a user. |
| User Credit Category Basket | Array of credit categories (Gift Card, Reimbursement, Referral Credits, Prepaid Subscription, GMA) issued per user. |
| User Email | Email address of the user. |
| User First Completed Oms Order Id | OMS order id of the first order completed by a user. |
| User First Completed Order Id | Unique order id of the first order completed by a user. |
| User First Order Unique Ordered Products | Unique products ordered by the user in their first completed order. |
| User First Order Unique Ordered Skus | Unique SKUs ordered by the user in their first completed order. |
| User Has Ordered A La Carte | Whether or not the user has had at least one order that is not part of a subscription. |
| User Has Promo Applied In First Order | Whether or not the user has a promo applied to their first completed order. |
| User Has Subscription In First Order | Whether or not the user's first order is linked to a subscription. |
| User Id | Unique key generated by Chord to identify a unique user. |
| User Is Active Subscriber | Whether or not the user has an active subscription with at least one completed subscription order. An active subscription is one that is not cancelled or paused. |
| User Is Customer | Whether or not the user is a customer. |
| User Is New Customer | Whether or not the user is a new customer. |
| User Is Not Customer | Whether or not the user is not a customer. |
| User Is Returning Customer | Whether or not the user is a returning customer. |
| User Is Subscriber | Whether or not the user has completed at least one subscription order. |
| User Login | The login email address of the user. |
| User Name | Full name of the user. |
| User Number Of Completed A La Carte Orders | Total amount of orders completed by a user that are a la carte. |
| User Number Of Completed Subscription Orders | Total amount of orders completed by a user that was part of a subscription. |
| User Number Of Orders With Promos | The count of completed orders with a promo applied. |
| User Number Of Subscriptions | Total amount of subscriptions linked to a user. |
| User Oms User Id | Unique key generated by Solidus that identifies a user. |
| User Phone | Phone number of the user. |
| User Total Completed Order Count | Total amount of orders completed by a user. |
| User Unique Ordered Products | Unique products ordered by the user across all orders. |
| User Unique Ordered Skus | Unique SKUs ordered by the user across all orders. |
| Variant Cost Price | The manufacturing cost of the variant. |
| Variant Depth | The depth of the variant. |
| Variant Height | The height of the variant. |
| Variant Id | Unique key generated by Chord to identify a unique product variant. |
| Variant Is Backorderable | Whether the stock item has at least one location where it is back-orderable or not. |
| Variant Is Inventory Tracked | Whether the inventory should or should not be tracked for this variant. |
| Variant Is Master | Whether this represents the master SKU or not. |
| Variant Is Subscribable | Whether or not a customer can ask to subscribe to this product. |
| Variant Oms Variant Id | Unique key generated by Solidus that identifies a variant. |
| Variant Option Color | Color of the variant. |
| Variant Option Format | Format of the variant. |
| Variant Option Quantity | Quantity of item for the variant. |
| Variant Option Size | Size of the variant. |
| Variant Position | The position of the variant in the list of variants. |
| Variant Sku | The SKU of the variant. |
| Variant Weight | The weight of the variant. |
| Variant Width | The weight of the variant. |
| Billing Address Created At (Universal) | Timestamp at which the address row was created - Universal Time Zone. |
| Billing Address Updated At (Universal) | Timestamp at which the address row was last updated - Universal Time Zone. |
| Line Item Last Adjustment Refund At (Universal) | Timestamp of the last return adjustment for an order line item - Universal Time Zone. |
| Line Item Last Adjustment Replacement At (Universal) | Timestamp of the last replacement adjustment for an order line item - Universal Time Zone. |
| Order Approved At (Universal) | Reflects when the entity was approved in Solidus - Universal Time Zone. |
| Order Canceled At (Universal) | Reflects when the order was cancelled - Universal Time Zone. |
| Order Completed At (Central) | Reflects when the entity was moved to the 'completed' state - Cental Time Zone. |
| Order Completed At (Eastern) | Reflects when the entity was moved to the 'completed' state - Eastern Time Zone. |
| Order Completed At (Mountain) | Reflects when the entity was moved to the 'completed' state - Mountain Time Zone. |
| Order Completed At (Pacific) | Reflects when the entity was moved to the 'completed' state - Pacific Time Zone. |
| Order Completed At (Universal) | Reflects when the entity was moved to the 'completed' state - Universal Time Zone. |
| Order Created At (Central) | Reflects when the entity was first created in Solidus - Cental Time Zone. |
| Order Created At (Eastern) | Reflects when the entity was first created in Solidus - Eastern Time Zone. |
| Order Created At (Mountain) | Reflects when the entity was first created in Solidus - Mountain Time Zone. |
| Order Created At (Pacific) | Reflects when the entity was first created in Solidus - Pacific Time Zone. |
| Order Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Order First Fulfillment Fulfilled At (Universal) | Timestamp at which the first shipment for that order was shipped - Universal Time Zone. |
| Order Last Adjustment Refund At (Universal) | Timestamp of the last return adjustment for an order - Universal Time Zone. |
| Order Last Adjustment Replacement At (Universal) | Timestamp of the last replacement adjustment for an order - Universal Time Zone. |
| Order Last Fulfillment Fulfilled At (Universal) | Timestamp at which the last shipment for that order was shipped - Universal Time Zone. |
| Order Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| Product Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Product Deleted At (Universal) | Reflects when the entity was deleted - Universal Time Zone. |
| Product Discontinued At (Universal) | Reflects when the entity was discontinued - Universal Time Zone. |
| Product Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| Shipping Address Created At (Universal) | Timestamp at which the address row was created - Universal Time Zone. |
| Shipping Address Updated At (Universal) | Timestamp at which the address row was last updated - Universal Time Zone. |
| Subscription Actionable Date (Universal) | The date of the next subscription installment. This date is updated after each successful installment. Subscriptions in an inactive state will be null - Universal Time Zone. |
| Subscription Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Subscription First Order Completed At (Universal) | The timestamp of the subscription's first completed order - Universal Time Zone. |
| Subscription Last Order Completed At (Universal) | The timestamp of the subscription's last completed order - Universal Time Zone. |
| Subscription Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| User Created At (Universal) | Timestamp at which the users row was created - Universal Time Zone. |
| User Date Of Birth (Universal) | Date of birth of the user - Universal Time Zone. |
| User Deleted At (Universal) | Timestamp at which the user's account was deleted - Universal Time Zone. |
| User First Order Completed At (Universal) | The timestamp of the user's first completed order - Universal Time Zone. |
| User First Subscription Order Completed At (Universal) | The timestamp of the user's first completed subscription order, regardless of subsequent subscriptions - Universal Time Zone. |
| User Last Order Completed At (Universal) | The timestamp of the user's last completed order - Universal Time Zone. |
| User Last Sign In At (Universal) | The last sign in timestamp for the user - Universal Time Zone. |
| User Updated At (Universal) | Timestamp at which the users row was last updated - Universal Time Zone. |
| Variant Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. |
| Variant Deleted At (Universal) | Reflects when the entity was deleted - Universal Time Zone. |
| Variant Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. |
| Average Adjusted Total Price | Total price for the line item after adjustments. |
| Average Adjustment Fulfillment Tax Total | Total of adjustment shipment taxes paid for the line item. |
| Average Adjustment Tax Total | Total of included adjustment taxes paid for the line item. |
| Average Adjustment Total | The sum of all adjustment for this line item. |
| Average Order Additional Tax Total | Total additional taxes for an order. |
| Average Order Adjustment Fulfillment Tax Total | Total adjustment shipment taxes for an order. |
| Average Order Adjustment Fulfillment Total | Total shipment adjustments applied to an order. |
| Average Order Adjustment Other Charges Total | Total of included additional adjustment charges paid for an order. |
| Average Order Adjustment Other Credits Total | Total of credits issued for an order. |
| Average Order Adjustment Refund Total | Total of return dollars for an order. |
| Average Order Adjustment Replacement Total | Total of replacement dollars for an order. |
| Average Order Adjustment Rma Refund Total | Total of refund dollards associated to an order that was returned via the RMA functionality of the Chord OMS. |
| Average Order Adjustment Tax Total | Total adjustment taxes an order. |
| Average Order Adjustment Total | Total of adjustment applied for an order as on the order. |
| Average Order Applied Gift Card Total | Total of gift card dollars that were used as a payment method in the order |
| Average Order Commission Total | Commission for an order. |
| Average Order Fulfillment Total | Total shipment for an order. |
| Average Order Gross Revenue | Gross amount of revenue generated by the order including items and shipments totals. Gross revenue = total - included\_tax\_total + shipment\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Average Order Included Tax Total | Total included taxes for an order. |
| Average Order Item Total | Total price for the order before adjustments. |
| Average Order Net Revenue | Net revenue generated by the order's items after promotions. Net revenue = total - included\_tax\_total + shipment\_total + adjustment\_total - additional\_tax\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Average Order Pre Paid Purchase Total | |
| Average Order Pre Paid Redemption Total | |
| Average Order Promo Total | Promotions applied to an order. |
| Average Order Purchased Gift Card Total | Total of gift card dollars that were purchased in the order. |
| Average Order Reimbursement Credit Total | |
| Average Order Tax Total | Total taxes for an order. |
| Average Order Total Price | Total to be paid by the customer for an order. |
| Average Order Transaction Total | Total paid by the customer for a completed order. |
| Average Promo Total | The sum of all of the promo totals from this line items and promotions. |
| Average Quantity | The quantity of how many of said variant was purchased. |
| Average Tax Total | Total of total taxes paid for the line item. |
| Average Total Price | Total price for the line item before adjustments. |
| Adjusted Total Price | Total price for the line item after adjustments. |
| Adjustment Fulfillment Tax Total | Total of adjustment shipment taxes paid for the line item. |
| Adjustment Tax Total | Total of included adjustment taxes paid for the line item. |
| Adjustment Total | The sum of all adjustment for this line item. |
| Order Additional Tax Total | Total additional taxes for an order. |
| Order Adjustment Fulfillment Tax Total | Total adjustment shipment taxes for an order. |
| Order Adjustment Fulfillment Total | Total shipment adjustments applied to an order. |
| Order Adjustment Other Charges Total | Total of included additional adjustment charges paid for an order. |
| Order Adjustment Other Credits Total | Total of credits issued for an order. |
| Order Adjustment Refund Total | Total of return dollars for an order. |
| Order Adjustment Replacement Total | Total of replacement dollars for an order. |
| Order Adjustment Rma Refund Total | Total of refund dollards associated to an order that was returned via the RMA functionality of the Chord OMS. |
| Order Adjustment Tax Total | Total adjustment taxes an order. |
| Order Adjustment Total | Total of adjustment applied for an order as on the order. |
| Order Applied Gift Card Total | Total of gift card dollars that were used as a payment method in the order |
| Order Commission Total | Commission for an order. |
| Order Fulfillment Total | Total shipment for an order. |
| Order Gross Revenue | Gross amount of revenue generated by the order including items and shipments totals. Gross revenue = total - included\_tax\_total + shipment\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Order Included Tax Total | Total included taxes for an order. |
| Order Item Total | Total price for the order before adjustments. |
| Order Net Revenue | Net revenue generated by the order's items after promotions. Net revenue = total - included\_tax\_total + shipment\_total + adjustment\_total - additional\_tax\_total - purchased\_gift\_card\_total - pre-payment subscription purchase amount |
| Order Pre Paid Purchase Total | |
| Order Pre Paid Redemption Total | |
| Order Promo Total | Promotions applied to an order. |
| Order Purchased Gift Card Total | Total of gift card dollars that were purchased in the order. |
| Order Reimbursement Credit Total | |
| Order Tax Total | Total taxes for an order. |
| Order Total Price | Total to be paid by the customer for an order. |
| Order Transaction Total | Total paid by the customer for a completed order. |
| Total Price | Total price for the line item before adjustments. |
| Promo Total | The sum of all of the promo totals from this line items and promotions. |
| Quantity | The quantity of how many of said variant was purchased. |
| Tax Total | Total of total taxes paid for the line item. |
### **order\_discount\_codes**
| Name | Description |
| ---------------------------- | -------------------------------------- |
| Order Applied Discount Codes | Discount code(s) applied to the order. |
### **order\_discount\_names**
| Name | Description |
| ---------------------------- | -------------------------------------- |
| Order Applied Discount Names | Discount name(s) applied to the order. |
### **order\_tags**
| Name | Description |
| ---------- | ---------------------------------- |
| Order Tags | Order tag(s) applied to the order. |
### **subscription\_tags**
| Name | Description |
| ----------------- | ----------------------------------------- |
| Subscription Tags | Subscription tag(s) applied to the order. |
[title] Available Expressions
[path] Chord AI/Chord AI Modeling/
### Aggregations
- **Average**
Returns the average of the values in the column.
Syntax: `avg(column)` -> double
- **Count**
Returns the count of non-null rows (also known as records) in the selected data.
Syntax: `count(column)` -> bigint
- **Max**
Returns the largest value found in the column.
Syntax: `max(column)`-> \[same as input]
- **Min**
Returns the smallest value found in the column.
Syntax: `min(column)` -> \[same as input]
- **Sum** Adds up all the values of the column.
Syntax: `sum(column)` -> \[same as input]
### Math functions
- **Absolute**
Returns the absolute (positive) value of the specified column.
Syntax: `abs(column)` -> \[same as input]
- **Cube root**
Returns the cube root ofthe number.
Syntax: `cbrt(column)` -> double
- **Ceil**
Rounds a decimal up (ceil as in ceiling).
Syntax: `ceil(column)` -> \[same as input]
- **Exponential**
Returns Euler's number, e, raised to the power of the supplied number.
Syntax: `exp(column)`-> double
- **Floor**
Rounds a decimal number down.
Syntax:`floor(column)` -> \[same as input]
- **Ln**
Returns the natural logarithm of?the number.
Syntax: `ln(column)` -> double
- **Log10**
Returns the base 10 log of the number.
Syntax: `log10(column)` -> double
- **Round**
Rounds a decimal number either up or down to the nearest integer value.
Syntax: `round(column)` -> \[same as input]
- **Signum**
Returns the signum function of the number.
Syntax: `sign(column)` -> \[same as input]
### String functions
- **Length**
Returns the number of characters in string.
Syntax: `length(column)` -> bigint
- **Reverse**
Returns string with the characters in reverse order.
Syntax: `reverse(column)` -> varbinary
[title] Analytics Homepage Overview
[path] Chord Data Platform/Overview/
# Introduction
Chord's analytics platform is a powerful tool that helps businesses collect, organize, and interpret data, transforming raw information into actionable insights. With customizable dashboards and reports, brand operators, analysts, and marketers can visualize trends, measure key metrics, and optimize strategies across various channels, empowering teams to drive growth and efficiency with confidence.
Below is a tour of the **Analytics Homepage** and its key features.
# Page overview
The **Analytics Homepage** consists of the following features:
- **Pinned Reports**
- **My Reports**
- **Shared Reports**
- **Explores**
- **Quickstarts**
More information on each of the above features is provided below.
:::hint{type="info"}
**A note on terminology:**
A** report **on the Chord platform can refer to either a **dashboard** or a **Look** (which also known as an **explore**). A **dashboard** is made up of a collection of **Looks** (**explores**).
:::
## Pinned Reports
This is the first page you will land on under the **Analytics Homepage**. The **Pinned Reports **tab will display pinned dashboards and Looks. **Pinned Reports **allows users to view key reports as designated by admin users, making it easy for all stakeholders to access vital company reports in one central location.
## My Reports
You'll be able to see all of the dashboards and Looks in your personal folder via the dropdown menu on the top left of the **My Reports **page.
You will also be able to create new dashboards and Looks from this page, as well as share and import dashboard links with your team. You can also share a report to your organization's shared reports folder from your personal reports folder as well.
## Shared Reports
By default, the **Shared Reports** page will display all of the shared reports in your organization. Use the dropdown menu on the left to view the list of all shared dashboards and Looks.
Additionally, any custom, personal reports that are created ***and shared*** to your organization via the **My Reports **page will also appear here.
## Explores
The **Explores** page is where you can dive into your data a bit deeper and use different data dimensions to create individual measures to build visualizations and reports. You can use the dropdown menu on the top left to explore different categories of data that Chord collects on behalf of your store.
## **Quickstarts**
Chord Commerce's **Quickstarts** is where you will find a collection of Looks and dashboards created by the Chord team that you can use to build reports that suit your business needs. You can search and filter different quickstart templates in our library to find what you are looking for in no time.
For additional information about quickstarts, visit our guide [here](https://docs.chord.co/using-quickstarts).
[title] Chord Copilot Chat
[path] Chord AI/
Chord Copilot is your on-demand data teammate. Ask questions about your store in plain language — revenue, customers, orders, products — and get accurate answers instantly, no SQL knowledge required. You can also export results directly to CSV, Excel, or Google Sheets.
## Getting started
1. Log into Chord.
2. Navigate to **Chord Copilot** from the left navigation menu.
3. Ask a question about your store's data, or browse suggested questions using the **Suggested Questions** dropdown below the chat box.
4. Wait momentarily for Copilot to respond.
Once Copilot answers, you can ask follow-up questions, export results, or take additional actions from the answer window.
## Answer actions
After Copilot responds, the following actions are available:
**Preview results** — view the answer in a table format. From here you can:
- Show/hide the search bar
- Show/hide column filters
- Show/hide specific columns
- Toggle row density
- Toggle full screen
**Export data** — download results as a CSV, Excel file, or export directly to Google Sheets.
**View chart** — view the answer as a visualization. Chord Copilot automatically selects the chart type (line, bar, etc.). You can pin any visualization to your Charts dashboard.
**View SQL** — see the exact query Copilot ran against your data.
**See reasoning** — view the step-by-step thought process and data tables Copilot used to arrive at your answer. This reflects Copilot's intent interpretation and routing — how it understood your question and which data it pulled before generating a response.
**Monitor** — set up an ongoing monitor for the metric in your question using the monitoring AI agent.
## Conversation history
Chord Copilot retains your conversation history across sessions. You can return to any previous thread and pick up where you left off — no need to re-ask or re-establish context.
To access past conversations, click **View History** in the top right corner of the Copilot page. History is scoped to your account — you'll only see threads you've started.
To start fresh, click **New Conversation** in the top right corner.
## Enriched context
Copilot uses enriched context to deliver more accurate, relevant answers. Three capabilities work together behind the scenes:
**Persistent conversation history** — Copilot remembers what you've discussed across sessions. When you return to a thread, it understands prior context without you having to repeat yourself.
**Intent interpretation and routing** — before generating a response, Copilot interprets the intent behind your question and routes it to the right data and logic. You can see this in action via **See reasoning** in the answer window.
**Real-time data warehouse enrichment** — Copilot pulls live data from your warehouse at query time, ensuring answers reflect your most current data rather than a cached snapshot.
These improvements are on by default. No configuration is required.
## Clarifier
Copilot includes a built-in clarifier that asks smart follow-up questions when your query is complex or ambiguous — gathering enough context before it responds.
The clarifier is **enabled by default**. You can turn it off using the **Use Clarifier** toggle in the chat input at any time.
*Questions or feedback? Reach out to help\@chord.co.*
[title] Sharing Data with Chord via Snowflake
[path] Chord Data Platform/Overview/
# Introduction
This guide provides step-by-step instructions for sharing data with Chord via Snowflake.
Snowflake's secure data sharing capabilities lets you share specific database objects in your Snowflake account with other Snowflake accounts. There are two primary mechanisms by which Snowflake enables sharing data across accounts.
1. ***A direct share***. Use a direct share to share data with one or more accounts in the same Snowflake region. You do not need to copy or move data shared with a direct share.
2. ***A private listing***. Use a private listing to share data directly with other Snowflake accounts in any Snowflake region. A private listing is a managed service that will automatically handle cross-region and cross-cloud replication. See [auto-fulfillment costs](https://docs.snowflake.com/en/collaboration/provider-understand-cost-auto-fulfillment) for pricing details.
# Creating a direct share
A **direct share** is appropriate when your Snowflake account resides in the same cloud / region as Chord's Snowflake account (AWS - US East Ohio). If your Snowflake account resides in a different cloud / region, please refer to "Creating a private listing" below.
:::hint{type="info"}
You must use the `ACCOUNTADMIN` role or a role that has been granted the `CREATE SHARE` global privilege to create shares.
:::
To create a direct share in the Snowflake UI:
1. Sign in to Snowsight.
2. In the navigation menu, select **Data sharing** » **External sharing**.
3. Select the **Shared by your account** tab.
4. Select **Share** » **Create a Direct Share**.
5. In the Share Data dialog, select **+ Select Data** and then:
- Select a source database.
- Select a target object or objects from the source database.
- Optionally, update the **Secure Share Identifier** created for your share.
- Optionally, enter a **Description**.
- In the remaining text box, enter an account locator. Chord's account locator is: `CZA77372.RK46674`. Entering a partial account locator lists all accounts that match the entered text. Repeat as required to add additional accounts. You can only add accounts within the same region to the share.
- Select **Create Share**.
# Creating a private listing
A **private listing** is used to share data directly with other Snowflake accounts in any Snowflake region. A private listing is a managed service that will automatically handle cross-region and cross-cloud replication. See [auto-fulfillment costs](https://docs.snowflake.com/en/collaboration/provider-understand-cost-auto-fulfillment) for pricing details.
## Accept the terms and conditions
In order to create a listing, you first need to accept the terms and conditions via [Snowflake Provider and Consumer Terms](https://docs.snowflake.com/collaboration/provider-becoming#review-and-accept-the-snowflake-provider-and-consumer-terms). We also recommend that you review the [Provider Policies](https://www.snowflake.com/provider-policies/).
:::hint{type="info"}
In order to provide a free private listing, you do not need to set up a Provider Profile.
:::
## Enable auto-fulfillment
When you share a private listing with Snowflake accounts in another region, you must enable auto-fulfillment. Auto-fulfillment is a Snowflake-managed service that handles the automatic replication of data across clouds / regions.
:::hint{type="warning"}
In order to enable auto-fulfillment, you need to assume the `ORGADMIN` and `ACCOUNTADMIN` roles.
:::
To enable auto-fulfillment open a Snowflake worksheet and run the following:
```pgsql
USE ROLE ORGADMIN;
SELECT SYSTEM$ENABLE_GLOBAL_DATA_SHARING_FOR_ACCOUNT('');
USE ROLE ACCOUNTADMIN;
GRANT MANAGE LISTING AUTO FULFILLMENT ON ACCOUNT TO ROLE ACCOUNTADMIN;
SELECT SYSTEM$IS_GLOBAL_DATA_SHARING_ENABLED_FOR_ACCOUNT('');
```
If you do not know your account name, you can use the following SQL:
`SELECT CURRENT_ACCOUNT_NAME();`
## Create a private listing
1. Sign in to Snowsight.
2. In the navigation menu, select **Marketplace** » **Provider Studio**.
3. Select **Create Listing** » **Specified Consumers**.
4. In the **Edit listing title** dialog, enter a name for your listing.
5. Select the **Add data product** button, then click **+ Select** to select the objects to attach to the listing.
- If you select one or more database objects, Snowflake creates a secure share with those objects. You can change the name of the secure share.
- If you select an existing secure share, the name of that share appears.
6. In the **Access type** dropdown, select **Free**.
7. In the **Who can access** section, add the organization and account names for the consumers that you want to share the listing with. Chord's account locator is: `CZA77372.RK46674`
- If you add a consumer account in a region that isn’t your local region, Snowflake enables auto-fulfillment to replicate data to the remote region after a consumer gets your listing. Complete the following additional steps:
- In the **Auto-fulfillment** section, enter a value and select an interval to specify how often to replicate your data product from your region to the remote region.
- If you don’t have a default warehouse set, select a warehouse to use for auto-fulfillment.
8. Enter a description for your listing.
9. In the **Legal Terms** section, select "Terms of service will be provided offline". If you don’t see any legal terms, you must first accept the Snowflake Provider and Consumer Terms.
10. (Optional) In the **Attributes** section, add custom attributes to your listing.
11. (Optional) Click in the **Data dictionary** section to add featured objects from the listing’s data dictionary.
12. (Optional) Click in the **Business needs** section to add tags that describe the business needs that your data product addresses.
13. (Optional) Click in the **Quick Start Examples** section to add sample SQL queries or a notebook that demonstrate how to use the data product.
14. Select **Publish** to publish the listing to the selected consumers. Snowflake saves your listing if you don’t publish it immediately.
[title] Receiving data from Chord via Snowflake
[path] Chord Data Platform/Overview/
# Overview
If you use Snowflake, receiving data from Chord via a Snowflake listing is an easy and secure way to access your raw and transformed data. Chord will own all the costs of replication and transformation, and customers will be responsible for one yearly maintenance fee to Chord.
# Provide your Snowflake account identifier
To utilize the Snowflake share, you'll need to provide Chord your *data sharing account identifier. *To generate your data sharing account identifier run the following in Snowflake:
```pgsql
SELECT CURRENT_ORGANIZATION_NAME() || '.' || CURRENT_ACCOUNT_NAME();
```
Please alert your account manager if this is of interest to you or email [help@chord.co](mailto\:help@chord.co) to get started!
# Accepting a Snowflake listing
Once Chord has established a listing with your Snowflake account, you will need to accept the listing in the Snowflake UI. To access a private listing that was shared with you, do the following:
1. Sign in to Snowsight.
2. In the navigation menu, select **Data sharing** » **External sharing**.
3. On the **Shared with you** page under **Privately shared listings**, select the listing you want to access.
4. Select **Get**.
Note: You must use the `ACCOUNTADMIN` role or another role with the `CREATE DATABASE` and `IMPORT SHARE` privileges to access a listing.
[title] Pre-Built Audiences
[path] Chord Data Platform/Audiences/
# Overview
Want to learn more about the different pre-built audience segments Chord has to offer? Check out the information below!
# Pre-built audience segments
The following audience segments are ready for activation:
| **Audience Segment** | **Description** | **Audience Category** |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------ | --------------------- |
| Brand Champions | Customers who purchase frequently, have purchased recently, and have purchases with average or better order value. | Repeat Customers |
| Product Loyalists | Customers loyal to a single product. | Repeat Customers |
| New Customers (90 days) | Customers who completed their first purchase in the last 90 days. | First Time Customers |
| New Customers (30 days) | Customers who completed their first purchase in the last 30 days. | First Time Customers |
| Customers-to-Be | Customers who have added an item to cart at least once but not checked out. | Prospective Buyers |
| Coupon Entrants | Customers who applied a promo to their first order and have used a promo in at least one additional order. | Customers |
## Predictive audiences
The following predictive audiences are also available:
| **Predictive Audience Segment** | **Description** | **Audience Category** |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- |
| At-Risk Customers | Customers who are at the highest risk of not purchasing again. | Repeat Customers |
| Almost-Purchasers | Shoppers with browsing behaviors indicating they are likely to complete a purchase soon and might purchase sooner with some incentive or confidence-building. | Prospective Buyers |
| Motivated Customers | Customers who don’t need a promotion, discount, or additional incentive to make another purchase. | Motivated Customers |
[title] Sessions
[path] Chord Data Platform/Data Models/
# Sessions
A **session** at Chord is a continuous window of activity by a single visitor on your storefront. Sessions are the atomic unit we use for analytics like traffic, attribution, conversion rate, and bounce rate. One row per session is exposed through the analytics layer, ready to be joined to orders, users, landing pages, and marketing channels.
This page describes how Chord defines, builds, and enriches sessions.
## What a session represents
A session captures **everything one visitor did in one sitting** on a single storefront. It begins with their first event, continues as long as they stay active, and closes after they go quiet. Every page view, product view, add-to-cart, checkout step, and order placed during that window is rolled up under a single **Session ID**.
A session is always scoped to a single **OMS** and **store,** a visitor browsing two of your storefronts at the same time produces two distinct sessions, one per store.
## How a session begins and ends
Chord uses a **30-minute inactivity timeout**.
- A new session starts on a visitor's very first event.
- The session continues as long as the gap between two consecutive events is **30 minutes or less**.
- A new session begins the moment a gap **exceeds 30 minutes**.
There is no fixed maximum session length. A visitor who keeps interacting can stay in the same session for hours. **There is also no calendar-day cutoff: a session that begins at 11:50 PM and continues at 12:05 AM is one session, not two.**
:::BlockQuote
**Example:** A visitor lands on your homepage at 10:00, views a product at 10:08, adds to cart at 10:15, walks away, and returns to view another product at 10:40. The 10:40 view is **25 minutes** after the previous event, so it stays in the same session. If they had instead returned at 10:46 (**31 minutes later)** that view would start a brand-new session.
:::
The session's **Start Time** is the timestamp of its first event; the **End Time** is the timestamp of its last event; the **Duration** is the difference. A session with only one event has a duration of zero.
## How visitors are stitched across sessions
Every event arriving from your storefront carries an **anonymous ID** (a browser/device cookie) and, once the visitor logs in or places an order, a **user ID** from your OMS.
Chord builds a single, stable identity per visitor (internally called the **blended user ID)** using the following rule:
- If we have **ever** seen a user ID associated with this anonymous ID, that user ID becomes the visitor's identity for **every session**, including sessions that happened before they logged in.
- If we have never seen a user ID, the anonymous ID itself is the identity.
The practical effect: when someone browses anonymously for a week, then signs up, all of their earlier sessions are **retroactively re-attributed** to the same person. They show up as a single user in the user dimension, with their full session history attached.
**Cross-subdomain stitching is automatic.** The Chord CDP SDK persists the anonymous ID across subdomains, so a visitor who browses on shop.example.com and checks out on checkout.example.com is treated as a single visitor across both. No special reconciliation is required.
## What is attached at the session level
Every session row carries:
**Identity & scope**
- **Session ID**: a unique identifier for this session
- **Blended User ID**: the stitched visitor identity (see *How visitors are stitched* above)
- **Anonymous ID**: the visitor's browser/device cookie
- **OMS**, **Store**: the storefront the session belongs to
- **Session Number**: the visitor's 1st, 2nd, 3rd… session
- **Visitor Type:** New Visitor if it is the visitor's first session, otherwise Returning Visitor
**Timing**
- **Start Time**, **End Time**, **Duration in Seconds**
- **Duration Tier:** a bucketed view of the session length: 0–9s, 10–29s, 30–59s, or 60s+
- **Activity Count:** the number of page views plus tracked events in the session
- **Days Since Last Session**: how long it has been since this visitor's previous session ended
**Landing & device**
- **Landing Page:** the **first page view** of the session (or, if the session has only non-page events, the first event)
- **Last Seen Page**: the **most recent page view** in the session
- **Device** and **Device Category** (desktop / mobile / tablet), inferred from the user agent
**Marketing attribution**: derived from the **landing page** of the session
- UTM source, medium, campaign, term, content
- Google / Meta / Microsoft click IDs
- Page referrer
- Channel and sub-channel mapped from the UTM/referrer combination through Chord's marketing channel mapping (e.g., Paid Search, Paid Social, Email, SMS, Affiliate, Direct, Other). [See more on channel definition.](https://docs.chord.co/attribution-channel-mapping)
- A paid-vs-organic flag derived from the channel
- *(Optional)* a Post-purchase survey override: when the UTM-derived channel is Direct or Unknown and the visitor answered a post-purchase survey on the resulting order, Chord uses the survey answer as the channel.
**Conversion milestones**
For each session, Chord exposes a flag for whether the visitor reached each step of the funnel:
- **Has Product Viewed**: the visitor opened at least one product detail page
- **Has Product Added:** at least one product was added to the cart
- **Has Cart Viewed**: the visitor opened the cart
- **Has Checkout Started**: the visitor entered the checkout flow
- **Has Checkout Completed**: the visitor finished the checkout flow
- **Has Order Completion:** at least one order was placed during the session
Alongside these flags, the session also carries:
- **Completed Order IDs / Numbers**: the orders that were placed during the session
- **Order Revenue Totals**: gross, net, tax, fulfillment, and refunds, summed across all orders completed in the session
**Customer state at the time of the session**
- **Customer Type**: Prospective customer (no prior orders), New customer (first order is in or before this session), or Repeat customer (had a prior order before this session)
- **Is Bounced Session**: see *Bounce definition* below
## How orders attach to sessions
An order is attached to a session when a corresponding Order Completed or Checkout Completed event lands inside that session's window. The order then contributes its revenue, basket, discount codes, and tags to the session's totals.
A session can contain more than one order; revenue fields are summed across them. Conversely, an order can only attach to one session (the one in which the completion event fired).
For [multi-touch attribution](https://docs.chord.co/rxEl-marketing-attribution), Chord computes four standard models per session toward the visitor's next conversion:
- **First touch:** full credit to the visitor's first session
- **Last touch:** full credit to the converting session
- **Linear:** equal credit across all sessions up to and including the conversion
- **40 / 20 / 40**: 40% first session, 40% converting session, the remaining 20% spread evenly across the middle
These points are exposed at the session grain and are also rolled up to orders.
## What is **excluded** from sessions
**Bot and synthetic traffic.** Sessions are built only from real visitor activity. Before any session is constructed, Chord filters out events that look automated — that is, events whose browser user agent matches a known bot or automation tool. The filter is grouped into four categories:
- **Search-engine and social crawlers:** e.g. Googlebot variants, Baidu, ByteDance, Yahoo Slurp, Facebook's link-preview crawler, Meta's external agent.
- **SEO and analytics crawlers**: e.g. Screaming Frog, HubSpot Crawler, SEOMonitor.
- **Uptime and synthetic-monitoring tools**: e.g. Datadog Synthetics, Shopify's checkout-observation probes.
- **Generic automation patterns and headless browsers**: any user agent containing bot, crawler, or spider, plus headless tools like Headless Chrome, PhantomJS, Selenium, Puppeteer, and Playwright.
In addition, one known synthetic ad-feed combination of UTM parameters (utm\_campaign=sag\_organic + utm\_source=google + utm\_medium=product\_sync) is stripped, since it is generated by automated product syncing rather than by a real shopper.
Filtered events never produce sessions and never inflate visit, conversion, or attribution counts.
:::BlockQuote
This filter relies on the browser's self-reported user agent. Sophisticated automation that deliberately impersonates a real browser will not be caught at this layer.
:::
**Server-side events.** Sessionization runs on **client-side** events only, events that actually represent something a real visitor did in a browser. Server-side events are kept elsewhere in the warehouse but are not eligible to start, extend, or end a session.
### Bounce definition
A session is marked **bounced** when **all** of the following hold:
- The session has only one page view
- Only one distinct page (URL + query) was visited
- The visitor did not start checkout and did not place an order
- The duration was under 2 seconds
If any one of those conditions fails, the session is non-bounced.
## Edge cases and caveats
- **Late-arriving events.** When a delayed event lands for a visitor, Chord re-evaluates that visitor's full activity history so the session boundaries remain correct. This means historical session counts can shift slightly between runs as late events arrive.
- **Identity discovered later.** As described above, a visitor's earlier anonymous sessions are retroactively re-attributed to their user ID once they identify. Counts of "anonymous sessions" can therefore decrease over time as visitors sign in or check out.
- **Multi-storefront visitors.** A visitor browsing two of your stores simultaneously produces two distinct sessions — one per store — even if they share an anonymous ID.
- **Cross-device.** Not modeled. Sessions on different devices are independent unless the same identifier is asserted on both.
- **Bot filtering is user-agent based.** Sophisticated automation that spoofs a real user agent will not be caught by these filters.
- **Empty sessions.** A session must have at least one client-side event by construction. There is no concept of a "page view that didn't fire."
:::hint{type="success"}
if you have any questions or need help, please reach out to us at [help@chord.co](mailto\:help@chord.co)
:::
[title] Chord AI Charts
[path] Chord AI/
Skip the digging and go straight to saved insights. Our AI Charts surface the most relevant metrics that have been saved by your teammates so you can quickly understand what metrics have been searched and saved by your team.
- **Pin a Chart: **To pin a chart, ask a question to our AI chat feature. If your answer can be visualized, you can pin the visualization to your charts via the **Pin **button as shown above.
- **Remove a Pinned Chart:** To remove a pinned chart from a dashboard, go to a pinned chart and click the trash icon.
- **Refresh a Pinned Chart:** To refresh a pinned chart, click the refresh icon on a pinned chart.
- **Download a Pinned Chart: **To download and save a pinned chart as an SVG or PNG, click on the download icon.
- **Reorder a Pinned Chart:** To change the position of a given chart and reorder them on the page, simply drag and drop them to your desired location.
:::hint{type="info"}
Note: At this time, the AI dashboards displays ALL pinned charts in your organization.
:::
[title] Chord AI Monitors
[path] Chord AI/
Confidence starts with consistency. Chord’s AI Monitors continuously check the health and accuracy of your data queries, alerting you when something’s off—before it impacts decisions.
# Getting started
To set up a monitor, follow the instructions below:
1. Log into Chord.
2. Navigate to **Copilot** from the left navigation menu.
3. Ask a question about your store’s data, or choose a question from our most-asked questions list from the question tiles below the conversation box.
4. Once you receive an answer, click on the **Monitor **button to generate an AI monitor for your question.
5. After your monitor is generated, you'll be able to review the SQL created to build the monitor as well as refine the monitor as-needed. See below video for a quick look at what this looks like.
# Managing monitors
Once you create a monitor, it will appear on the **Monitors** page.
This page has the following features:
- **Create a new monitor:** Create a new monitor by clicking on the “Create New Monitor” button on the top right corner of the Monitors page and following the instructions in the modal to ask a question in the Chat.
- **Alert summary tiles:** Click on any of these tiles to filter out the monitors in the table below to quickly see active or paused alerts and alerts with errors. Clicking on **Total Alerts** will display all available alerts
- **Monitors filters:** You can search for a specific monitor and also use the status filter to find alerts that are active, inactive, paused, or erroring.
- **Monitors list and actions:** The table lists each of the available monitors for your organization. You will see the alert name, who created the alert, monitoring frequency, whether the monitor is active or inactive, when the monitor was last run, and additional actions. The available actions are:
- Run Test Now
- Pause
- View History
- Edit
[title] Chord AI Implementation Guide
[path] Chord AI/
Getting started with Chord AI is designed to be effortless. You don’t need a team of engineers or weeks of setup — simply connect your data source and Chord takes care of the rest.
From standardizing your data to powering retrieval and generating safe, AI-driven queries, everything is built to work seamlessly out of the box.
The result: You can start asking questions and uncover insights with confidence — right from day one.
## **Set-up requirements**
- [ ] Define and familiarize yourself with your store’s data warehouse models.
- [ ] Prepare a shortlist of key custom metrics, definitions, and specific questions and SQL queries important to your organization.
- [ ] Connect your store’s data source to the Chord AI platform.
- [ ] Configure and set your store’s data warehouse models on Chord AI to help Chord AI understand your store’s data structure.
- [ ] Configure and set key Instructions and SQL Pairs (custom metrics, definitions, and specific questions and SQL queries) through the Context Studio.
:::hint{type="info"}
Contact [help@chord.co](mailto\:help@chord.co) for additional guidance and troubleshooting!
:::
[title] Chord AI Technical Overview
[path] Chord AI/
This guide explains how Chord AI works under the hood — from data connection through to generating answers. It's designed for both brand users and technical teams who want to understand what's happening at each step.
# How Chord AI works
Chord AI processes every question through five stages. Here's what happens at each one.
## 1. Connect data source
**What happens:** Chord securely connects to your commerce data warehouse.
**Why it matters:** Chord AI works directly with your data — not a copy of it. This ensures answers are always based on your actual store data.
**Behind the scenes:** The connection uses warehouse share with validation checks for schema, freshness, and permissions. Note that connecting multiple data sources is not supported at this time.
## 2. Data source modeling
**What happens:** Your data schema is indexed and transformed into structured, analytics-ready models. You can enrich this layer with business-specific logic via Chord AI Context — adding instructions and SQL pairs to define how key metrics are calculated.
**Why it matters:** This is the abstraction layer between your warehouse and Chord's AI models. It ensures terms like "revenue" or "customer" mean the same thing every time, across every query.
**Behind the scenes:** Chord AI indexes your schema and stores it in a vector database. We only work with the schema — not the underlying data itself — keeping your models decoupled from the warehouse.
## 3. Intent interpretation and routing
**What happens:** When a question is submitted via Copilot Chat, Chord AI interprets the intent behind it before retrieving any data. It determines what the question is really asking, identifies any ambiguity, and routes the request to the appropriate data and logic.
**Why it matters:** This step is what allows Copilot to handle complex or loosely worded questions accurately. Rather than treating every input as a literal string, Chord AI reasons about what you're trying to understand before it acts.
**Behind the scenes:** The clarifier agent may activate at this stage to ask follow-up questions if the query needs more context. Once intent is confirmed, the request is passed to the retrieval layer.
## 4. Data retrieval
**What happens:** Chord AI retrieves the relevant data tables from the modeling layer and pulls live data from your warehouse at query time.
**Why it matters:** Real-time retrieval means answers reflect your most current data — not a cached snapshot from a prior sync.
**Behind the scenes:** Chord AI queries the vector database to identify which schema elements are relevant, pulls the top results, then enriches the query with live warehouse data before passing it to the LLM.
## 5. Generating outputs via LLM
**What happens:** Chord AI builds an optimized SQL query, validates it, runs it against your data source, and returns the result through Copilot.
**Why it matters:** This step automates complex analysis — giving you accurate answers without writing SQL manually.
**Behind the scenes:** Chord AI uses two Anthropic Claude models for this stage — Claude Opus for SQL generation, where reasoning depth matters most, and Claude Haiku for response generation and classification, optimized for speed and consistency. For more detail, see Chord AI Models: Powered by Anthropic.
## Data privacy
Chord AI does not store your data. We work with your schema only — the structure and definitions of your data, not the records themselves. Your data never leaves your warehouse without your explicit configuration.
For more detail on data security, see the [Chord AI FAQ](docId\:ZPWngfj3CK6UWAM29TiO9).
*Questions or feedback? Reach out to help\@chord.co.*
[title] Chord Data Attribute Definitions
[path] Chord Data Platform/Data Models/
As a commerce data platform, we empower brands to not only boost revenue and lower customer acquisition cost (CAC), but also deepen their understanding of customers through our infrastructure that exposes predictive insights, revenue forecasting, and customer lifetime value (LTV).
With the always-expanding size of the ***Chord Data Attribute*** catalog, it is vital that users understand the fields getting used in your Chord reporting and the nuances that come with that.
The following documentation provides the definition(s) and methodology for all ***available Chord Data attributes***.
These attributes and their definitions can be accessed via the *Explore* view of any report, by clicking on the "i" icon for any field.
:::hint{type="info"}
💡 If you or your team have additional questions please reach out to **help\@chord.co.**
:::
[title] Predictive Marketing Attribution
[path] Chord Data Platform/Data Models/Marketing Attribution/
Chord now offers predictive attribution! Read more about it in [Predictive Marketing Attribution](docId\:Ks2RX6EIsS95edjK5G84i) .
[title] Destination Set-up Notes
[path] Chord Data Platform/Data Activations/Data Activations/
Listed ahead are detailed set-up steps for some of the most commonly used Chord Data Activation Destinations.
##
[title] Messaging Module
[path] Chord Data Platform/Data Sources/
# Overview
Chord's Messaging Module unlocks connections for various sources of messaging data, including sources like email and SMS platforms, and enables a robust Messaging Explore, a wide dataset populated with enriched data fields.
The Messaging Explore allows the creation of custom reports and audiences or customer segments with granularity down to the campaign level.
Sample fields available in the Messaging explore:
- Number of sends
- Number of opens
- Number of clicks
The module enables direct connections to the following sources:
- Klaviyo
- Iterable
- Attentive (Coming Soon)
# Use Cases
- Brands create reports to track sends, opens, and clicks for various campaigns
- Brands create reports to analyze subscribe and unsubscribe rates
Please reach out to help\@chord.co or your account executive for more information about or access to this feature.
[title] User Management on the Chord Platform
[path] Chord Data Platform/Overview/
# User roles and permissions
Collaborating with your colleagues is essential when it comes to store operations and analyzing your store performance metrics. The Chord Commerce Data Platform has four core permission levels that enable collaboration. These roles and permissions are outlined below.
| **Activity** | **Member (Regular User)** | **Developer** | **Order Manager\*** | **Data Analyst\* ** | **Team Admin ** |
| -------------------------------------------------------------------------------- | ------------------------- | ------------- | ------------------- | ------------------------ | -------------------- |
| Can view data & analytics dashboards | ✅ | ✅ | - | ✅ | ✅ |
| Can use Quickstarts | ✅ | ✅ | - | ✅ | ✅ |
| Can create new custom reports using Explores functionality | ✅ | ✅ | - | ✅ | ✅ |
| Can pin custom analytics reports | - | - | - | ✅ | ✅ |
| Can view and manage Chord OMS orders
(Applies to Chord Autonomy customers) | ✅ | - | ✅ | - | ✅ |
| Can manage data activations and activation syncs | - | ✅ | - | ✅ | ✅ |
| Can manage audiences | - | - | - | ✅ | ✅ |
| Can manage data sources | - | ✅ | - | ✅ | ✅ |
| Can manage model amplifications | - | - | - | ✅ | ✅ |
| Can manage CDP destinations | - | ✅ | - | ✅ | ✅ |
| Can add CDP connectors, sources, destinations | - | ✅ | - | ✅ | ✅ |
| Can update or edit model amplifications | - | - | - | ✅ | ✅ |
| Can add activations destinations | - | - | - | ✅ | ✅ |
| Can create consent categories | - | ✅ | - | - | ✅ |
| Can manage (set, edit, delete) consent category mappings | - | ✅ | - | - | ✅ |
| Can manage dynamic data settings | - | ✅ | - | ✅ | ✅ |
| Can add data sources | - | ✅ | - | ✅ | ✅ |
| Can view team members | ✅ | ✅ | ✅ | ✅ | ✅ |
| Can invite new users | - | - | - | - | ✅ |
| Can upgrade or downgrade user permissions | - | - | - | - | ✅ |
| Can remove users | - | - | - | - | ✅ |
:::hint{type="info"}
**\*Note:** **The Order Manager and Data Analyst roles are only applicable for Chord Autonomy customers that use Chord OMS to manage orders. **
Additionally, Chord Commerce team members are **Super Admins **on the platform and won't be visible on your team page or count toward your total platform user count.
:::
# Inviting a user
You need to have **Team Admin** level permissions to invite a user on the Chord platform.
A **Team Admin** level user should follow the steps below to invite a new user:
1. Log in to Chord and click **Team** on the left navigation panel.
2. Click **Invite User.**
3. Select the appropriate role and related permissions for the user: **Member**,** Order Manager**, **Data Analyst**, or **Team Admin.**
4. Provide the user’s email address and click **Invite to join.**
5. Once the newly invited user receives the invitation email, they will be prompted to provide their full name before their first sign-on.
6. You can check whether or not the newly invited user established their account by viewing the status of their invitation on the **Team** page.
## Inviting a user via SSO
:::hint{type="info"}
💡 Developer documentation on SSO via Okta can be found here: [Chord Platform and Okta SSO Integration](docId\:aILd8lOFx9eCbBSKjCsgX).
:::
1. The user logs into the IdP dashboard (e.g. Okta) and selects the Chord Hub application.
2. Okta servers request that the user authenticate the login.
3. On success, the user is redirected to the Chord platform.
4. The user will automatically be granted **Member (Regular User)** level access to the Chord platform.
5. The Chord platform validates the session information from the IdP and logs the user in.
# Upgrading user permissions
:::hint{type="info"}
**Note:** **The Order Manager and Data Analyst roles are only applicable for Chord Autonomy customers that use Chord OMS to manage orders. **
:::
You need to have **Team Admin** level permissions to upgrade roles and permissions on the Chord platform. On Chord, the **Team Admin** role is the role with the most permissions on the platform.
A **Team Admin** should follow the steps below to upgrade a team member’s permission level:
1. Log in to Chord and click **Team** on the left navigation panel.
2. Click on an existing team member that is currently a **Member, Order Admin, **or** Data Analyst**.
3. Select whether or not the existing team member should have **Admin** level privileges by selecting **Team Admin** in the dropdown selector.
4. Click **Save Changes**.
# Downgrading user permissions
:::hint{type="info"}
**Note:** **The Order Manager and Data Analyst roles are only applicable for Chord Autonomy customers that use Chord OMS to manage orders. **
:::
You need to have **Team Admin** level permissions to downgrade another user’s permissions on the Chord platform.
A **Team Admin **user should follow the steps below to downgrade a team member’s permission level:
1. Log in to Chord and click **Team** on the left navigation panel.
2. Click on an existing team member with** Team Admin** level permissions.
3. Select either the** Member, Order Admin, **or** Data Analyst **role option, as applicable to the individual's role, via the dropdown selector.
4. Click **Save Changes**.
# Removing a user
To remove an existing user on the Chord platform, you need to have **Team Admin** level permissions.
A **Team Admin** user should follow the steps below to remove a collaborator:
1. Log in to Chord and click **Team** on the left navigation panel.
2. Click on the user you wish to remove from the platform.
3. Click the **Delete** button.
4. You can verify that the user has been removed by clicking back into the **Team** link.
## Removing a user via SSO
:::hint{type="info"}
Note that if a user’s SSO access is revoked, there is no way for that same user to log into Chord. Chord does not currently support automatic user removal in the platform if a user has been revoked access via SSO.
:::
To remove an SSO user from the Chord platform, an existing **Admin** level user should log into Chord and delete the user following the steps outlined above in the “**Removing a User**” section. ***Note that this step should be completed *******after******* the user’s access to the Chord platform via SSO has been removed.***
Please contact [help@chord.co](mailto\:help@chord.co) if you need help removing a user or have any questions about this process.
[title] Overview
[path] Chord Data Platform/
## Data on Chord
### Actionable data
Get a 360˚ view of your customer with powerfully rich data housed in a single source of truth. Easily manage cross-channel data with curated dashboards and customizable explores, and gain deeper insight into customer interactions with rich behavioral event data to complement complete transactional data.
### Data integrations
Chord's integration platform provides you the capability to get your OMS and customer data to the third party vendors you need to get them to, when you need to, while providing you vibrant and thorough events data for Chord's analytics engine.
[title] Sales Channel Module
[path] Chord Data Platform/Data Sources/
# Overview
The Sales Channel Module helps you understand where your revenue is coming from—across every channel that contributes to your business. Whether your brand sells through DTC storefronts, third-party marketplaces, or retail partnerships, this module organizes and exposes the data you need to attribute orders, optimize performance, and evaluate new growth opportunities.
With sales channel data modeled consistently and made accessible in Chord’s platform, you can track, analyze, and activate on channel-specific insights with confidence.
[title] Order Attribution on Chord
[path] Chord Data Platform/Data Models/Marketing Attribution/
:::hint{type="info"}
This is a **NEW** Explore introduced in May 2025.
:::
# Introduction
Since a customer can purchase from a brand more than once, it follows that brands will want to analyze different purchase paths than rolling them all up to the first order’s attribution. Instead of centering analysis at the user-level, this new Explore is centered around orders, or when a customer makes a purchase.
On Chord, we identify the session when a customer makes their first purchase and then we repeat the attribution exercise with every following session as part of Order Attribution. Thus, we apply a brand’s chosen specific attribution methodology based on orders. **Essentially, order attribution allows brands to analyze sessions and revenue for all purchase data.** It’s useful for understanding both marketing attribution and connecting sessions to specific orders.
You can use Chord’s Order Attribution Explore when:
- You want to measure the performance of marketing efforts tied to multiple purchases.
- You're evaluating campaign ROI, revenue by channel, or purchase funnel effectiveness.
- You're reporting on conversion events, like how many orders were driven by a campaign.
# Getting Started
1. Log into the Chord Commerce Data Platform.
2. Navigate to your **Analytics** page.
3. Click the **Explores** tab.
4. Select the **Marketing Attribution - Order Attribution** item in the dropdown menu (see first image).
5. Navigate to the **Order Attribution** Field list on the lefthand side to access the new **attribution point** dimensions (see second image).
6. Select an attribution point dimension applicable to your analysis.
7. Additionally, if you’d like to use different attribution measures, you can select attribution measures under the measures list on the lefthand navigation pane (see third image).
:::hint{type="info"}
For more information on the differences between **Dimensions** and **Measures**, click [here](https://docs.chord.co/glossary#CiE5u).
:::
[title] Recharge
[path] Chord Data Platform/Data Sources/Connect Data Sources/
Connect your Recharge subscription data to Chord
Recharge is the subscription management platform that powers recurring billing, customer portals, and lifecycle events for many subscription brands on Shopify. Chord ingests subscription, order, charge, customer, and product data from Recharge so you can model retention, churn, and lifetime value alongside the rest of your stack.
## What Chord ingests from Recharge
Chord pulls 12 datasets from your Recharge account. Each dataset becomes its own table in your Chord Snowflake schema:
:::Paragraph{indent="1"}
**Subscriptions: **Active and historical subscription records: frequency, status, line items, next billing date
:::
:::Paragraph{indent="1"}
**Orders**: Subscription-driven orders, including cart and shipping details
:::
:::Paragraph{indent="1"}
**Charges**:Individual charge attempts and outcomes: successes, failures, retries
:::
:::Paragraph{indent="1"}
**Customers: **Customer profiles linked to subscriptions
:::
:::Paragraph{indent="1"}
**Addresses**: Shipping and billing addresses on customer accounts
:::
:::Paragraph{indent="1"}
**Discounts**: Discount codes and their usage on subscriptions
:::
:::Paragraph{indent="1"}
**Events**: Subscription lifecycle events: cancellations, pauses, reactivations, swaps, skipped charges
:::
:::Paragraph{indent="1"}
**Collections**: Product collections and their merchandising structure
:::
:::Paragraph{indent="1"}
**Plans**: Selling plans (frequency × price tiers) attached to products
:::
:::Paragraph{indent="1"}
**One-time products**: One-time products purchased alongside subscriptions
:::
:::Paragraph{indent="1"}
**Bundle** selections: Choices made within bundle subscriptions
:::
## Generate a Recharge API token
You'll need a Recharge API token with the seven read scopes listed below. The token is created in the Recharge merchant admin and pasted into Chord Hub.
***Heads up:**** Only store owners can access the API tokens page by default. If you're a staff user, ask your store owner to either generate the token for you or grant your account API token permissions first.*
1. Log in to the **Recharge merchant portal**.
2. In the left sidebar, click **Tools & apps**, then click **API tokens**.
3. Click **Create an API Token**, then choose **Admin API token**.
4. Fill in the **Details** section:
- **Token name** — something recognizable, e.g. Chord data sync.
- **Contact email** — an inbox at your company that Recharge can reach about this token.
5. Under **Permissions**, set the following required scopes below as **Read access** (leave everything else as **No access**):
## Required scopes
Chord needs all seven of these read scopes for the connector to pull every dataset cleanly. Make sure each one is enabled before saving the token.
:::Paragraph{indent="1"}
**Read subscriptions:** Subscriptions, One-time products, Bundle selections
**Read orders: **Orders, Charges
**Read customers:** Customers, Addresses
**Read discounts: **Discounts
**Read events:** Events
**Read plans: **Plans
:::
:::Paragraph{indent="1"}
**Read products: **Products
:::
# Connect the token in Chord
1. Open **Chord Hub** and go to **Data Sources → Add Source.**
2. Pick **Recharge** from the data source list.
3. Paste the token you just copied into the **API token** field.
4. Click **Save** — Chord makes a test call against your Recharge account to confirm the token works and has all seven read scopes.
5. The first sync kicks off automatically; subsequent syncs run on your tenant's standard ingestion schedule.
## Troubleshooting****
**What does the validate step actually check?**
Chord makes a small read against scoped endpoints and confirms the token returns data without a permission error. It does not pull or store any records, that happens on the first scheduled sync after you save the credential.
**The validate step failed with a scope error. What now?**
Recharge tokens are editable after created, you can add scopes to an existing token. Go back to **Tools & apps → API tokens** in Recharge, edit the existing token with all seven read scopes enabled, and then, go back to Chord and test the connection once again.
**Do Recharge API tokens expire?**
No. Tokens stay valid until a store owner manually revokes them in **Tools & apps → API tokens**. If a previously working token suddenly fails, check that page first to confirm it's still listed and active.
**How do I rotate the token?**
Generate a new token in Recharge with the same seven read scopes, paste it into the same Chord credential entry, and save. Chord uses the new token on the next scheduled sync. Once you've confirmed the new token validates and the next sync runs cleanly, delete the old token from Recharge.
**Who can see the token after it's saved in Chord?**
The token value is encrypted at rest in Chord Hub and is never displayed back in the UI. You can rotate or delete it any time, but you can't view the original value once it's saved.
## Need help?
If you hit a scope or permission issue you can't resolve, reach out to [help@chord.co](mailto\:help@chord.co) with the exact error message. We'll trace the request and tell you which scope is missing.
[title] Audiences
[path] Chord Data Platform/
# Introduction
::loom[]{url="https://www.loom.com/embed/7fd9b8d5498347b9be830611ada97195?sid=459330a8-4e97-4ff9-b759-d7f13eea1dd0"}
Chord Audiences is a comprehensive home base that enables brands to better connect with and retain customers using the data gathered and enriched by the Chord Commerce platform.
**Using Audiences, Chord brands will be able to:**
- Personalize content and marketing campaigns for specific sets of customers to increase brand awareness and engagement.
- Leverage customer data to help with product planning and sales optimization.
- Unlock the potential of customer data by utilizing the data activation suite - and more!
# Features
- Ability to access and sync audiences across your organization
- [Nine (9) pre-built audience segments](https://docs.chord.co/pre-built-audiences), including predictive audiences.
- Simple data activation capability via [Chord Data Activations](https://docs.chord.co/pre-built-audiences) (if enabled on your account)
# Getting started
## Request early access to audiences
If your organization does not yet have access to Audiences, you can easily request this feature following the steps below.
1. Log into the Chord Commerce data platform.
2. Click on Audiences in the side navigation pane.
3. Click the "Request Early Access" button.
4. Once submitted, you will see that the request was received by our team. A Chord team member will review your request and enable Audiences for you and your organization.
Once access is granted, you are now one step closer to activating key customer segments!
:::hint{type="info"}
Once Audiences is activated for your organization, you will receive an e-mail from [help@chord.co ](mailto\:help@chord.co)or another team member.
:::
# Using Shared Audiences
The Shared Audiences tab displays all custom audience segments that exist for your organization. These audiences can be synced and activated downstream via audience destinations.
Simply search for your desired audience segment in the dropdown and then click **Sync Audience** to be taken to audience destinations to set up your sync.
:::hint{type="info"}
We are working on the ability to create a custom audience segment from scratch. In the meantime, you can browse existing audience templates ([prebuilt audiences](https://docs.chord.co/pre-built-audiences)) and build your custom audience from these templates. You can also check our documentation on how to [create custom audiences via LookML](https://docs.chord.co/custom-audiences).
If you need assistance, please reach out to [help@chord.co](mailto\:help@chord.co).
:::
# Using Chord Prebuilt Audiences
Chord has created a number of audiences for you to be able to use and activate instantly. You can activate these audience segments immediately, or use them as templates to build custom audiences. To use prebuilt audiences, follow the instructions below.
1. Log into the Chord Commerce data platform.
2. Click on the Audiences link in the lefthand navigation page.
3. Select “**Prebuilt Audiences**”.
4. View and use a pre-built audience of your choice.
5. Once you select a prebuilt audience, you will have a couple of different options for your chosen audience segment:
1. **If you would like to use the prebuilt audience segment as-is**, you can easily send your prebuilt audience of choice to a third-party destination of your choice by clicking "**Sync Audience**" (Requires access to Chord's Data Activation suite).
2. **If you would like to add further customizations or dimensions to a prebuilt audience**, click “**Use as Template**” to use the prebuilt audience as a starter template.
:::hint{type="info"}
Read more about Chord’s pre-built audiences [here](https://docs.chord.co/pre-built-audiences)!
:::
# Using audience destinations
:::hint{type="warning"}
This section is gated on the Chord platform since it requires access to Chord’s Data Activations feature. Please reach out to your account manager for additional information and to request access if you do not see our audience destinations.
Alternatively, you can also request access through the platform directly on this tab.
:::
With the Chord Activations Suite, you can use your audience data in useful ways to drive marketing campaigns and analytical insights downstream.
1. If you want to activate a custom audience segment in a pre-existing destination that has already been set up, click on **Manage Syncs**.
1. Note: If you have not yet set up destinations or your desired destination has not been created yet, follow the destination creation instructions [here](https://docs.chord.co/data-activations#xcfzl).
2. From here, click **Add New Sync** to add a new sync to an existing destination.
3. Using the Sync UI, select the following options to locate the custom audience you’d like to use:
Follow the rest of the Sync UI flow as normal. For more information, check out our activations documentation [here](https://docs.chord.co/data-activations).
# Troubleshooting and FAQs
- **Issue: I don't see the pre-built audiences segments. What am I doing wrong?**
- Solution: Your organization may not have Audiences enabled. Check to see if you need to request access. If an access request has already been submitted, we're already working on your request and will grant you access shortly!
- **Issue: How do I get Chord's Data Activations feature?**
- Solution: Requesting access to Chord's Data Activations for your organization can be done instantly and within the product. Follow the steps below:
- After you've logged into Chord, click on "**Data Activations**" in the sidebar menu pane.
- On the **Data Activations** page, click the pink "**Request Access**" button.
- Your request will be reviewed by our Accounts team. We will be reaching out shortly. In the meantime, feel free to familiarize yourself with Activations with our [feature documentation](https://app.archbee.com/docs/8bOVl7vg1M-0GKcUIBnmZ/gFnFGu_57zya0cO8Wc0tK)!
- **Question: Can I edit or customize these pre-built audiences?**
- Yes, you can edit or customize these pre-built audiences. You can do so by following the steps below:
- Click on a pre-built audience you'd like to edit.
- On the audience list page, find and click the gear icon near the top right corner of the page.
- Click "Save As..."
- Edit the audience list to your preferences.
- **Note:** The audience that you edit or otherwise customize on top of the existing pre-built audience template will not appear in Data Activations quite yet. We are working on supporting this flow - coming soon!
# Contact Support
Need help? Contact Chord support at [help@chord.co](mailto\:help@chord.co)!
[title] Facebook Ads (Meta)
[path] Chord Data Platform/Data Activations/Data Activations/Destination Set-up Notes/
*This page describes how to connect Facebook Ads (Meta) as a Data Activation*
## Getting Started
Facebook Ads support two separate authentication mechanisms: OAuth and System User. Chord recommends using `System User` for the most reliable connection long term as it does not require re-authentication every 60 days.
### Using a System User (Recommended)
The steps to create a [Facebook System User](https://www.facebook.com/business/help/327596604689624?id=2190812977867143) are more complex than using OAuth, but it's the most reliable way to connect to Facebook Ads, especially if you intend to use the connection long term.
A regular system user is recommended over an admin system user. You can use an existing system user or create a new one with the following steps:
- To generate a system user token, you'll first need an application. If you don't have one already, you can create one with the following steps:
- Open your Business Manager
- Navigate to **Business Settings > Accounts > Apps**
- Click **Add** and then **Create New App ID**
- For use case select **Other**
- Then for Type select **Business**
- Then fill out the relevant details and press **Create App**
- Now you can generate a system user for the app. Go to your Business Manager and navigate to **Business Settings > Users > System Users**
Above your list of system users click **Add **to create a new System User
1. Provide a name and role. Chord does **not** need an Admin role, Employee is sufficient.
2. Once the system user is created click on **Add Assets** and add the Application you created in step one. Make sure to assign *full control* of the app to the system user.
- You'll also need to assign your System User *full control *over any Ad Accounts that own any Custom Audiences you'd like to sync data to.
- Now generate a token for the System User by pressing **Generate New Token.**
- You will need to provide the following scope for Chord to sync to your Facebook Conversions and Custom Audiences: *ads\_management*
- Make sure to select `Never` for token expiration so you do not need to manually reauthorize your Chord connection every 60 days.
- Once your token is generated be sure to save it in a safe place. This is the token you must provide to Chord Data Activations as a credential for your connection.
:::hint{type="info"}
To validate that your System User Token is set up correctly and has the necessary scopes you can input your access token in the link below.
[https://developers.facebook.com/tools/debug/accesstoken](https://developers.facebook.com/tools/debug/accesstoken)
:::
### Using an Existing System User
If you already have a system user you can use it by simply generating a new token with the correct permissions. Be sure to assign the asset for your Application to your System User with full control. Chord Data Activations needs the *ads\_management* scope.
### Using OAuth
If you'd like to use OAuth, connecting to Facebook Ads is as simple as clicking the "Connect" button and following the prompts. Chord will guide you through the process of authenticating with Facebook and selecting the ad accounts you'd like to sync data from.
The downside of this method is that authentication will expire every 60 days and require re-authentication. We recommend using a System User for the most reliable connection long term.
[title] Sharing Data with Chord from Cloud Storage (cloned)
[path] Chord Data Platform/Overview/
# Introduction
This guide provides step-by-step instructions for integrating external cloud storage services to Chord's data warehouse (Snowflake). We delegate authentication to Snowflake-managed identities, eliminating the need to manage credentials directly.
Below you'll find instructions for connecting either AWS S3, Google Cloud Storage or Azure Blob Storage services to Chord's data warehouse (Snowflake).
# Configuring an integration for AWS S3
This sections describes how to configure secure access to data files stored in an AWS S3 bucket.
1. Create an IAM Policy that has the permissions required to access the bucket and get objects:
:::Paragraph{indent="3"}
a. Log into the AWS Management Console.
:::
:::Paragraph{indent="3"}
b. From the home dashboard, search for and select **IAM.**
:::
:::Paragraph{indent="3"}
c. From the left-hand navigation pane, select **Account settings.**
:::
:::Paragraph{indent="3"}
d. Under **Security Token Service (STS)** in the Endpoints list, find the **United States (N. Virginia)** (i.e., `us-east-1`) region. If the **STS status** is inactive, move the toggle to **Active**.
:::
:::Paragraph{indent="3"}
e. Select **Create Policy.**
:::
:::Paragraph{indent="3"}
f. For **Policy editor**, select **JSON.**
:::
:::Paragraph{indent="3"}
g. Add a policy document that will allow Chord to access the S3 bucket and folder. The following policy (in JSON format) provides Chord with the required permissions to read data using a single bucket and folder path. Copy and paste the text into the policy editor:
:::
:::CodeblockTabs{indent="3"}
```javascript
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:GetObject",
"s3:GetObjectVersion"
],
"Resource": "arn:aws:s3::://*"
},
{
"Effect": "Allow",
"Action": [
"s3:ListBucket",
"s3:GetBucketLocation"
],
"Resource": "arn:aws:s3:::",
"Condition": {
"StringLike": {
"s3:prefix": [
"/*"
]
}
}
}
]
}
```
:::
:::Paragraph{indent="3"}
h. Select **Next.**
:::
:::Paragraph{indent="3"}
i. Enter a **Policy name** and an optional Description.
:::
:::Paragraph{indent="3"}
j. Select **Create policy.**
:::
2. Create an IAM Role and attach the custom IAM role:
:::Paragraph{indent="3"}
a. From the left-hand navigation pane in the Identity and Access Management (IAM) Dashboard, select **Roles.**
:::
:::Paragraph{indent="3"}
b. Select **Create role.**
:::
:::Paragraph{indent="3"}
c. Select **AWS account** as the trusted entity type.
:::
:::Paragraph{indent="3"}
d. Select **Another AWS account.**
:::
:::Paragraph{indent="3"}
e. In the **Account ID** field, enter your own AWS account ID temporarily. Later, you will modify the trust relationship and grant access to Snowflake.
:::
:::Paragraph{indent="3"}
f. Select the **Require external ID **option. An external ID is used to grant access to your AWS resources (such as S3 buckets) to a third party like Snowflake. Enter a placeholder ID such as `0000`. In a later step, you will modify the trust relationship for your IAM role and specify the external ID that Chord will provide.
:::
:::Paragraph{indent="3"}
g. Select **Next.**
:::
:::Paragraph{indent="3"}
h. Select the IAM Policy you created in the previous step.
:::
:::Paragraph{indent="3"}
i. Select **Next.**
:::
:::Paragraph{indent="3"}
j. Enter a name and description for the role, then select **Create role**.You have now created an IAM policy, IAM role and attached the policy to the role.
:::
:::Paragraph{indent="3"}
k. On the role summary page, locate and record the **Role ARN** value. You will need to provide Chord this ARN to complete the next steps.
:::
3. Provide Chord the IAM Role ARN and bucket name. The full bucket name is a URL that will look like the following: `s3://my-cool-bucket/`.
4. Once your bucket name and IAM Role ARN is confirmed, Chord will provide an IAM User ARN and an AWS External ID
5. Grant the IAM User permissions to access bucket objects:
:::Paragraph{indent="3"}
a. Sign in to the AWS Management Console
:::
:::Paragraph{indent="3"}
b. Select **IAM**
:::
:::Paragraph{indent="3"}
c. From the left-hand navigation pane, select **Roles**
:::
:::Paragraph{indent="3"}
d. Select the IAM Role you created in the previous step
:::
:::Paragraph{indent="3"}
e. Select the **Trust relationships** tab
:::
:::Paragraph{indent="3"}
f. Select **Edit trust policy**
:::
:::Paragraph{indent="3"}
g. Modify the policy document with the values provided by Chord. This includes IAM User ARN and External ID.
:::
:::CodeblockTabs{indent="3"}
```javascript
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "",
"Effect": "Allow",
"Principal": {
"AWS": ""
},
"Action": "sts:AssumeRole",
"Condition": {
"StringEquals": {
"sts:ExternalId": ""
}
}
}
]
}
```
:::
:::Paragraph{indent="3"}
h. Select **Update policy** to save your changes.
:::
# Configuring an integration for Google Cloud Storage
This sections describes how to configure secure access to data files stored in a Google Cloud Storage bucket.
1. Provide Chord with your GCS `bucket` name. The bucket name is the name of the Cloud Storage bucket that stores your data files. The full bucket name is a URL that will look like the following: `gcs://my-cool-bucket/`.
2. Once your `bucket` name is confirmed, Chord will provide you a Cloud Storage service account name to be used in the following steps.
3. Create a custom role that has the permissions required to access the bucket and get objects:
:::Paragraph{indent="3"}
a. Sign in to the Google Cloud console as a project editor.
:::
:::Paragraph{indent="3"}
b. From the home dashboard, select **IAM & Admin** » **Roles**
:::
:::Paragraph{indent="3"}
c. Select **Create Role.**
:::
:::Paragraph{indent="3"}
d. Enter a **Title** and optional **Description** for the custom role.
:::
:::Paragraph{indent="3"}
e. Select **Add Permissions.**
:::
:::Paragraph{indent="3"}
f. Filter the list of permissions, and add the following from the list: `storage.buckets.get`, `storage.objects.get` and `storage.objects.list`
:::
:::Paragraph{indent="3"}
g. Select **Add.**
:::
:::Paragraph{indent="3"}
h. Select **Create.**
:::
4. Assign the custom role to the Cloud Storage Service Account:
:::Paragraph{indent="3"}
a. Sign in to the Google Cloud console as a project editor.
:::
:::Paragraph{indent="3"}
b. From the home dashboard, select **Cloud Storage** » **Buckets**
:::
:::Paragraph{indent="3"}
c. Filter the list of buckets, and select the in-scope bucket.
:::
:::Paragraph{indent="3"}
d. Select **Permissions** » **View by principals**, then select **Grant access.**
:::
:::Paragraph{indent="3"}
e. Under **Add principals**, paste the name of the service account name provided by Chord.
:::
:::Paragraph{indent="3"}
f. Under **Assign roles**, select the custom IAM role that you created previously, then select **Save.**
:::
5. (Optional) Grant the Cloud Storage service account permissions on the Cloud Key Management Service cryptographic keys:
:::hint{type="info" indent="2"}
This step is required ***only if *** your GCS bucket is encrypted using a key stored in the Google Cloud Key Management Service (Cloud KMS).
:::
:::Paragraph{indent="3"}
a. Sign in to the Google Cloud console as a project editor.
:::
:::Paragraph{indent="3"}
b. From the home dashboard, search for and select **Security** » **Key Management.**
:::
:::Paragraph{indent="3"}
c. Select the key ring that is assigned to your GCS bucket.
:::
:::Paragraph{indent="3"}
d. Click **SHOW INFO PANEL** in the upper-right corner. The information panel for the key ring slides out.
:::
:::Paragraph{indent="3"}
e. Click the **ADD PRINCIPAL** button.
:::
:::Paragraph{indent="3"}
f. In the **New principals** field, search for the service account name provided by Chord.
:::
:::Paragraph{indent="3"}
g. From the **Select a role** dropdown, select the "Cloud KMS CrytoKey Encryptor/Decryptor role".
:::
:::Paragraph{indent="3"}
h. Click the **Save** button. The service account name is added to the **Cloud KMS CrytoKey Encryptor/Decryptor role** dropdown in the information panel.
:::
# Configuring an integration for Microsoft Azure Blob Storage
This sections describes how to configure secure access to data files stored in Microsoft Azure Blob Storage.
1. Provide Chord with your `tenant_id` and `container name`.
2. Once your `tenant_id` and `container name` are confirmed, Chord will provide a consent URL and app name.
3. In a web browser, navigate to the consent URL. The page displays a Microsoft permissions request page.
4. Click the **Accept** button. This action allows the Azure service principal created for Chord’s Snowflake account to be granted an access token on specified resources inside your tenant. Obtaining an access token succeeds only if you grant the service principal the appropriate permissions on the container (see the next step). The Microsoft permissions request page redirects to the Snowflake corporate site (snowflake.com).
5. Sign in to the Microsoft Azure portal.
6. Navigate to **Azure Services** » **Storage Accounts**. Click the name of the storage account you are granting the Snowflake service principal access to.
7. Click **Access Control (IAM)** » **Add role assignment**.
8. Select the desired role to grant to the Snowflake service principal: **Storage Blob Data Reader grants read access only.** This allows loading data from files staged in the storage account.
9. Search for the Snowflake service principal. This is the identity in the app name property that we will provide.
10. Click the **Review + assign** button.
# Troubleshooting
:::hint{type="info"}
This document has been created for customer reference purposes. For the most up-to-date information, you may consult official Snowflake documentation:
- [AWS S3](https://docs.snowflake.com/en/user-guide/data-load-s3-config-storage-integration#configuring-secure-access-to-cloud-storage)
- [Google Cloud Storage](https://docs.snowflake.com/en/user-guide/data-load-gcs-config#step-3-grant-the-service-account-permissions-to-access-bucket-objects)
- [Microsoft Azure Blob Storage](https://docs.snowflake.com/en/user-guide/data-load-azure-config#step-2-grant-snowflake-access-to-the-storage-locations)
:::
# Recommended next steps
If you plan to use cloud storage integration to share data with Chord, we have some helpful recommendations for structuing data to faciliitate seemless data ingestion. See [Chord Data Source Ingestion Guidelines](docId\:XkTAjRAIlw5UnrQRmPAn9).
[title] Subscription Events Enriched Explore
[path] Chord Data Platform/Data Models/Subscriptions/
## Overview
Event-level lifecycle analysis.
- Grain: **1 row per event**
- Purpose: analyze **event sequences and churn drivers**
## When to use
- Identify events leading to churn
- Analyze time between events
- Study lifecycle journeys
- Understand post-event outcomes
## Key dimensions & metrics
| Field | Description |
| ------------------------------------ | ------------------------------- |
| Event Type | created, paused, canceled, etc. |
| Event Date | Timestamp |
| Event Sequence Number | Order in lifecycle |
| Previous Event Type | Prior event |
| Days Since Previous Event | Time gap |
| Status Before | Status before event |
| Next Event Type | Next event |
| Days Until Next Event | Time gap |
| Is Terminal Event | Last event |
| Will Churn 30d / 90d | Forward-looking flags |
| Days Until Churn | Time to cancellation |
| Subscription Status Final | Final state |
| Customer Event Sequence | Across all subs |
| Is First Subscription Event | First-ever event |
| Customer Subscription Count At Event | Active subs count |
## Example business questions
- Events preceding cancellation
- Time from creation → churn
- Pause → resume vs cancel
- Churn probability after creation
- Event journey depth before churn
## Notes & caveats
- Churn flags look **forward from event**
- Churn = **cancellation only**
- Event richness varies by provider
## Glossary
| Term | What it Means | How to Interpret / Use | Where You’ll See It in Looker |
| ------------------------ | --------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Active Subscription** | A subscription that is currently ongoing. Includes both fully active and paused subscriptions. | Use this to understand the **current size of your subscriber base**. Note that paused users are still counted. | Subscription Metrics Daily (Active Count), Subscriber Journey (Is Active Subscriber), Subscriber Journey Monthly (Is Active Subscriber EOM), Product & Bundle Explores (Active Subscription Count) |
| **Churn / Churned** | A subscription that has been cancelled. Does not include pauses. | Represents **true customer loss**. Track this to understand retention issues. | Subscription Metrics Daily (Churned Count, Churn Rate), Subscriber Journey (Is Churned, Churn Count), Monthly (Is Churned EOM, Cancellations This Month), Events Enriched (Event Type = canceled), Movements (status\_cancelled) |
| **Winback** | A subscriber who cancelled all subscriptions and later returned by subscribing again. | Indicates **successful re-engagement** after churn. | Subscriber Journey (Is Winback), Subscriber Journey Monthly (Has Reactivated By EOM) |
| **Reactivation** | A previously cancelled subscription that becomes active again (subscription-level). | Measures **recovery of churned subscriptions**. | Subscription Metrics Daily (Reactivated Count), Movements (status\_reactivated), Events Enriched (Event Type = reactivated) |
| **Net New** | Net change in subscriptions: New + Reactivated − Cancelled. | Indicates **overall growth vs decline**. | Subscription Metrics Daily (Net New Count) |
| **LTV (Lifetime Value)** | Total revenue generated by a subscriber across all subscription orders. | Use to understand **customer value over time** and compare cohorts or segments. | Subscriber Journey (LTV Gross / Net Revenue), Subscriber Journey Monthly (LTV Gross Revenue EOM) |
| **EOM (End of Month)** | Metrics calculated as of the last day of a month. | Used for **consistent month-over-month comparisons** (retention, LTV growth). | Subscriber Journey Monthly (all EOM fields like Active EOM, LTV EOM) |
| **Solo Subscription** | A subscription that contains only one product. | Helps identify products that perform well **individually**. | Subscription Product Metrics Daily (Solo Subscription Count) |
| **Bundle** | A subscription that contains two or more products. | Useful for analyzing **product combinations and cross-sell behavior**. | Product Metrics (Bundle Subscription Count), Bundle Metrics Daily (all bundle fields) |
| **Movement** | Any change in a subscription’s state (created, cancelled, paused, resumed, reactivated, quantity/price change). | Use to understand **operational changes and trends** in subscriptions. | Subscription Movements Daily (Movement Type, Category), Events Enriched (Event Type) |
| **Provider** | The system managing subscriptions (Recharge, ChordOMS, CustomOMS). | Important context — **data availability and detail vary by provider**, which affects analysis. | All Explores (Provider filter present everywhere) |
[title] Chord Data Source Ingestion Guidelines
[path] Chord Data Platform/Overview/
**Your Data Warehouse → Chord**
Getting started with Chord is designed to be frictionless. We meet your data where it is, allowing you to unlock AI-driven insights, leverage the Chord Copilot, and activate your data downstream, all while leveraging your existing infrastructure investments. All we need is for your data to land in cloud storage as files. We take it from there.
For Snowflake users, please refer to [Sharing Data with Chord via Snowflake](docId\:o_LFN3Hs3wslRifj_ykKi). If you are not using Snowflake, we can still ingest data from your warehouse (Athena, BigQuery, Redshift, Postgres, Databricks, and others) using Parquet with Cloud Storage (S3, etc.). For step-by-step instructions for integrating external cloud storage services to Chord's data warehouse (Snowflake), see [Receiving Data from Chord via Cloud Storage](docId\:bL5Mzd2XGYPARsF-6_YnG).
*Note that Chord's schema expectations and IAM configurations can vary by cloud provider. *
## **The approach**
Chord provides two options for sharing data with us.
### **Option 1: Bring your own models**
Send us your data as is. Chord will simply handle the rest. Export your current tables (Orders, Customers, Products, etc.) exactly as they exist in your warehouse today. You do not need to rename columns, change data types, or map relationships.
- **Your effort:** Low. Simple export.
- **How it works:** Chord ingests your raw data and will adapt to your schema to generate insights. Chord AI and Copilot understand your schema by reading table and column names, and you can query, analyze, segment, and activate immediately.
- **Best for:** Teams who want to test the platform quickly without engineering overhead and already have clean, modelled data in a data warehouse.
:::hint{type="warning"}
**Note: **Some of Chord's data models will not be available if your brand chooses this option.
:::
### **Option 2: Bring your data and leverage Chord’s models**
Map your data to [Chord’s Unified Schema](https://docs.chord.co/oms-schema), and unlock access to Chord’s full Analytics suite. This option is for teams that want standardized reporting, attribution, and activation across tools.
- **Your effort:** Moderate. Requires writing SQL transformations.
- **How it works:** You ensure your data matches our specifications before it leaves your environment. Chord builds the unified tables. You still own the raw data. Chord owns the modelling layer.
- **Best for:** Teams that want standardized metrics across teams, plug-and-play attribution and lifecycle reporting, and activation-ready datasets.
## Required Entities
At a minimum, Chord recommends providing:
- Orders
- Customers
- Line Items
- Products
- Variants
- Payments
- Returns
- Refunds
- Shipments
- Orders
- Order Line Items
- Subscriptions
## **Setup and automation**
When processing a high volume of files from object storage, it’s helpful to name files according to a hierarchy that can be easily queried. Using the following key format is advised:
`//////_.parquet`
Here’s a specific example of what this might look like:
`example-oms/orders/2025/08/11/20:29:25/2025-08-10-14:00_e791c45e.parquet`
This means the file is the orders collection from your custom OMS platform. It was uploaded on `2025-08-11 at 20:29:25 UTC` and the data is for the hour of 2025-08-10 14:00. It’s also helpful to include a unique identifier for the file (in this case, shortened GUID `e791c45e`) corresponding to the compute process that produced this file.
[title] Klaviyo
[path] Chord Data Platform/Data Sources/Connect Data Sources/
Connect your Klaviyo marketing data to Chord. Klaviyo is the email, SMS, and push platform that powers segmentation, lifecycle flows, and campaign sends. Chord ingests campaign, flow, event, list, segment, and profile data from Klaviyo so you can model engagement, deliverability, and attribution alongside the rest of your stack.
## What Chord ingests from Klaviyo
Chord pulls 11 datasets from your Klaviyo account. Each dataset becomes its own table in your Chord Snowflake schema.
- **Flows**: email and SMS automation flows: name, status, trigger type, creation date.
- **Metrics:** every metric tracked in Klaviyo (native and integration-sourced): name, integration source, creation date.
- **Email campaigns**: one-off email sends: send options, tracking config, schedule, audience.
- **SMS campaigns:** one-off SMS sends: send options, tracking config, schedule, audience.
- **Mobile push campaigns**: push notification sends: send options, tracking config, schedule.
- **Lists**: static contact lists: name, opt-in process, profile count, creation date.
- **Segments**: dynamic audience segments: name, profile count, creation and update timestamps.
- **Events**: every customer event landed in Klaviyo (native and integration-sourced): event properties, metric, profile, timestamp.
- **Profiles**: customer profile records: email, phone, identifiers, properties, timestamps.
- **List profiles:**bridge table mapping profiles to lists with joined-at timestamps.
- **Segment profiles**: bridge table mapping profiles to segments.
:::hint{type="info"}
**Heads up:** the three profile datasets (profiles, list profiles, segment profiles) are off by default. On accounts with millions of profiles they fan out heavily and can slow your tenant's overall ingestion. If you need any of them, ask your Chord contact to enable them per resource.
:::
## Generate a Klaviyo private API key
You'll need a Klaviyo private API key with the seven read scopes listed below. The key is created in Klaviyo account settings and pasted into Chord Hub.
:::hint{type="warning"}
**Heads up:** only Klaviyo account owners and users with the "manage API keys" permission can create private API keys. If your role doesn't include it, ask an admin on the account to either generate the key for you or grant your user the permission first.
:::
1. Log in to your Klaviyo account.
2. Click your account name in the **bottom-left** corner of the navigation, then click **Settings**.
3. Click **API Keys**.
4. Click **Create Private API Key**. Name the key something recognizable, e.g. `chord data sync`.
5. Choose **Custom **for the scopes panel and set each of the seven required scopes below to **Read** (leave everything else as **No Access**).
6. Click **Create**. Copy the key value, Klaviyo only shows it once and there is no way to reveal it later.
**Required scopes:** Chord needs all seven of these read scopes for the connector to pull every dataset cleanly. Make sure each one is set to **Read** in the Custom scopes panel before saving the key.
- Flows (read-only)
- Metrics (read-only)
- Campaigns (read-only)
- Lists (read-only)
- Segments (read-only)
- Profiles (read-only)
- Events (read-only)
## Connect the key in Chord
1. Open Chord Hub and go to **Data Sources → Add Source**.
2. Pick **Klaviyo** from the data source list.
3. Paste the private API key you just copied into the **API Key** field.
4. Click **Save** — Chord makes a test call against the Klaviyo profiles endpoint to confirm the key works.
5. The first sync kicks off automatically; subsequent syncs run on your tenant's standard ingestion schedule.
## Troubleshooting
**What does the validate step actually check?**
Chord makes a small read against `https://a.klaviyo.com/api/profiles/` and confirms the key returns a 200 response with no permission error. It does not pull or store any records — that happens on the first scheduled sync after you save the credential.
**The validate step failed with a scope error. What now?**
Klaviyo private keys are not editable after creation — to change scopes you have to make a new one. Go back to **Account → Settings → API Keys** in Klaviyo, click **Create Private API Key** with all seven read scopes enabled, paste the new key into the same Chord credential entry, and test the connection once again. Then delete the old key in Klaviyo.
**Do Klaviyo private API keys expire?**
No. Keys stay valid until someone with manage-API-keys permission manually revokes them in **Account → Settings → API Keys**. If a previously working key suddenly fails, check that page first to confirm it's still listed and active.
**How do I rotate the key?**
Generate a new private API key in Klaviyo with the same seven read scopes, paste it into the same Chord credential entry, and save. Chord uses the new key on the next scheduled sync. Once you've confirmed the new key validates and the next sync runs cleanly, delete the old key from Klaviyo.
**Why don't I see profiles or membership data in Copilot?**
The profiles, list profiles, and segment profiles datasets are disabled by default on Chord-managed Klaviyo connectors. If your use case needs any of them (cohort modeling, list-level reporting, segment membership joins), ask your Chord contact to enable them and the next sync will start populating those tables.
***
**Need help?** If you hit a scope or permission issue you can't resolve, reach out to [help@chord.co](mailto\:help@chord.co) with the exact error message. We'll trace the request and tell you which scope is missing.
[title] Stay AI
[path] Chord Data Platform/Data Sources/Connect Data Sources/
Connect your Stay AI subscription data to Chord. Stay AI (formerly Retextion) is the subscription management platform powering recurring billing, customer portals, and lifecycle automations for Shopify subscription brands. Chord ingests subscription, order, and selling plan data from Stay AI so you can model retention, churn, and lifetime value alongside the rest of your stack.
## What Chord ingests from Stay AI
Chord pulls 3 datasets from your Stay AI account.
- **Subscriptions:** active and historical subscription records: status, line items, cadence, next billing date, customer link.
- **Orders:** subscription-driven orders linked back to the originating subscription contract.
- **Selling plan groups:** selling plan group definitions: cadences, bundle configuration, product mappings.
## Generate a Stay AI API key
You'll need a Stay AI API key from the merchant portal. There are no scopes or permissions to configure, it's a single token that grants read access to the Stay AI REST API.
:::hint{type="warning"}
**Heads up:** only users with admin access to the Stay AI merchant portal can generate API keys. If your role doesn't include it, ask an admin on the account to either generate the key for you or grant your user the permission first.
:::
1. Log in to the Stay AI merchant portal.
2. In the left sidebar, go to **Settings → API Keys**.
3. Click **New API Key**. Name the key something recognizable, e.g. `chord data sync`.
4. In the API Keys table, find the new row and click **Show** in the Private Key column to reveal the key.
5. Copy the key value.
:::hint{type="info"}
**Heads up:** unlike most platforms, Stay AI keeps the private key viewable after creation, you can return to **Settings → API Keys** and click **Show** any time to see it again. There's no "you only get one chance to copy it" moment.
:::
## Connect the key in Chord
1. Open Chord Hub and go to **Data Sources → Add Source**.
2. Pick **Stay AI** from the data source list.
3. Paste the API key you just copied into the **API Key** field.
4. Click **Save.** Chord makes a test call against the Stay AI subscriptions endpoint to confirm the key works.
5. The first sync kicks off automatically; subsequent syncs run on your tenant's standard ingestion schedule.
## Troubleshooting
**What does the validate step actually check?**
Chord makes a small read against `https://api.retextion.com/api/v2/subscriptions` and confirms the key returns a 200 response with no authorization error. It does not pull or store any records, that happens on the first scheduled sync after you save the credential.
**The validate step failed. What now?**
Stay AI API keys don't have scopes, so a 401 means the key value itself is wrong, was revoked, or was copied with extra whitespace. Go back to **Settings → API Keys** in the Stay AI portal, confirm the key is still listed and active, and either copy it again carefully or generate a new one. Paste the value into the same Chord credential entry and test again.
**Do Stay AI API keys expire?**
No. Keys stay valid until someone with portal admin access manually revokes them in **Settings → API Keys**. If a previously working key suddenly fails, check that page first to confirm it's still listed and active.
**How do I rotate the key?**
Generate a new API key in Stay AI, paste it into the same Chord credential entry, and save. Chord uses the new key on the next scheduled sync. Once you've confirmed the new key validates and the next sync runs cleanly, delete the old key from Stay AI.
**Who can see the key after it's saved in Chord?**
The key value is encrypted at rest in Chord Hub and is never displayed back in the UI. You can rotate or delete it any time, but you can't view the original value once it's saved.
**Why does the API host say **`retextion.com`**?**
Stay AI was previously called Retextion. The product was rebranded but the underlying API host and authentication header (`X-RETEXTION-ACCESS-TOKEN`) still use the legacy name. This is expected. Chord's connector handles the naming difference internally; you only ever interact with "Stay AI" in the Chord Hub UI.
***
**Need help?** If you hit a credential or connectivity issue you can't resolve, reach out to [help@chord.co](mailto\:help@chord.co) with the exact error message. We'll trace the request and tell you what's failing.
[title] Iterable
[path] Chord Data Platform/Data Sources/Connect Data Sources/
Connect your Iterable marketing data to Chord. Iterable is the cross-channel marketing platform that powers email, SMS, push, web push, and in-app messaging for many Chord brands. Chord ingests campaigns, templates, message metadata, user history, and full event streams from Iterable so you can model engagement, deliverability, and channel attribution alongside the rest of your stack.
## What Chord ingests from Iterable
Chord pulls 10 dataset groups from your Iterable account.
- **Campaign history:** every campaign sent: name, type, status, schedule, audience, channel.
- **Templates**: base, blast, triggered, and workflow templates referenced by campaigns.
- **Channels, lists, message types**: channel definitions (email, SMS, push, etc.), all lists, and message type configurations.
- **User history**: user profile snapshots and attribute changes over time.
- **Email events**: sends, opens, clicks, bounces, complaints, subscribes, unsubscribes.
- **SMS events**: sends, clicks, bounces.
- **Push events**: sends, opens, bounces.
- **Web push events**: sends, clicks.
- **In-app message events**: sends, opens, clicks.
- **Purchase events**: commerce events sent to Iterable from your store.
- **Custom events:** any custom event types you've defined in Iterable.
## Generate an Iterable API key
You'll need a **Server-side** Iterable API key. The Chord connector reads from Iterable's REST and export APIs from a backend service, so client-side, mobile, or JWT-enabled key types are not the right fit.
:::hint{type="warning"}
**Heads up:** only Iterable users with the **Project Admin** permission can create API keys. If your role doesn't include it, ask an admin on the project to either generate the key for you or grant your user the permission first.
:::
1. Log in to your Iterable account.
2. In the top navigation, click your account name, then click **Settings** (some accounts go directly to **Integrations**).
3. Click **Integrations → API Keys**.
4. Click **New API Key**. Name the key something recognizable, e.g. `chord data sync`.
5. Select **Server-side** as the key type.
6. Leave **JWT Authentication** off (it's only required for client-side key types).
7. Click **Create**. Copy the key value immediately. Iterable shows the key only once and there is no way to reveal it later.
## Connect the key in Chord
1. Open Chord Hub and go to **Data Sources → Add Source**.
2. Pick **Iterable** from the data source list.
3. Paste the API key you just copied into the **API Key** field.
4. Click **Save,** Chord makes a test call against the Iterable channels endpoint to confirm the key works.
5. The first sync kicks off automatically; subsequent syncs run on your tenant's standard ingestion schedule. The first run can take significantly longer than steady-state syncs because Iterable's export API has to materialize historical events.
## Troubleshooting
**What does the validate step actually check?**
Chord makes a small read against `https://api.iterable.com/api/channels` with the `Api-Key` header set to your key, and confirms a 200 response. It does not pull or store any records — that happens on the first scheduled sync after you save the credential.
**The validate step failed. What now?**
A 401 means the key value is wrong, was rotated, or was copied with extra whitespace. A 200 from a different endpoint but a failure here usually means the key type isn't Server-side. Go back to **Integrations → API Keys** in Iterable, confirm the key is listed as a Server-side key and is still active, then regenerate it if needed and paste the new value into the same Chord credential entry.
**Do Iterable API keys expire?**
No. Keys stay valid until a Project Admin manually revokes them in **Integrations → API Keys**. If a previously working key suddenly fails, check that page first to confirm it's still listed and active.
**How do I rotate the key?**
Generate a new Server-side API key in Iterable, paste it into the same Chord credential entry, and save. Chord uses the new key on the next scheduled sync. Once you've confirmed the new key validates and the next sync runs cleanly, delete the old key from Iterable.
**Why are my recent events not showing up yet?**
Iterable's bulk export API materializes events on a daily partition. A purchase that happened five minutes ago will not appear in Chord until the next scheduled sync (and its export job for today's partition) completes.
**Why don't I see in-app or web push event tables?**
Those channels only generate events if they're enabled and configured in your Iterable project. If your team doesn't run in-app or web push campaigns, those tables will be empty or missing, this is expected, not a connector bug.
***
**Need help?** If you hit a credential or connectivity issue you can't resolve, reach out to [help@chord.co](mailto\:help@chord.co) with the exact error message. We'll trace the request and tell you what's failing.
[title] Data Activations
[path] Chord Data Platform/
Chord unlocks a rich landscape of unified commerce data on behalf of modern brands. This data empowers brands to drive radical decisions and maximize growth.
Our platform empowers brands to not only boost revenue and lower customer acqusition cost (CAC), but also deepens their understanding of customers through our infrastructure that exposes predictive insights, revenue forecasting, and customer lifetime value (LTV).
Read on for more information about the data insights that power the brands using Chord.
[title] Subscription Product Metrics Daily Explore
[path] Chord Data Platform/Data Models/Subscriptions/
## Overview
Product-level subscription performance.
- Grain: **product per day**
## When to use
- Identify high-churn products
- Track product growth/decline
- Analyze bundle vs solo usage
## Key dimensions & metrics
| Field | Description |
| ----------------------------- | ------------------- |
| Report Date | Date |
| Product Title | Name |
| SKU | Identifier |
| Active Subscription Count | Active subs |
| New Subscription Count | New subs |
| Churned Subscription Count | Cancelled subs |
| Product Churn Rate | Product-level churn |
| Solo Subscription Count | Single-product subs |
| Bundle Subscription Count | Multi-product subs |
| Total Quantity | Total units |
| Active Count Change 7d / 30d | Trend |
| Avg Products Per Subscription | Avg bundle size |
## Notes & caveats
- Bundle = **multi-product subscription**
- Solo vs bundle = **consumption behavior insight**
## Glossary
| Term | What it Means | How to Interpret / Use | Where You’ll See It in Looker |
| ------------------------ | --------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Active Subscription** | A subscription that is currently ongoing. Includes both fully active and paused subscriptions. | Use this to understand the **current size of your subscriber base**. Note that paused users are still counted. | Subscription Metrics Daily (Active Count), Subscriber Journey (Is Active Subscriber), Subscriber Journey Monthly (Is Active Subscriber EOM), Product & Bundle Explores (Active Subscription Count) |
| **Churn / Churned** | A subscription that has been cancelled. Does not include pauses. | Represents **true customer loss**. Track this to understand retention issues. | Subscription Metrics Daily (Churned Count, Churn Rate), Subscriber Journey (Is Churned, Churn Count), Monthly (Is Churned EOM, Cancellations This Month), Events Enriched (Event Type = canceled), Movements (status\_cancelled) |
| **Winback** | A subscriber who cancelled all subscriptions and later returned by subscribing again. | Indicates **successful re-engagement** after churn. | Subscriber Journey (Is Winback), Subscriber Journey Monthly (Has Reactivated By EOM) |
| **Reactivation** | A previously cancelled subscription that becomes active again (subscription-level). | Measures **recovery of churned subscriptions**. | Subscription Metrics Daily (Reactivated Count), Movements (status\_reactivated), Events Enriched (Event Type = reactivated) |
| **Net New** | Net change in subscriptions: New + Reactivated − Cancelled. | Indicates **overall growth vs decline**. | Subscription Metrics Daily (Net New Count) |
| **LTV (Lifetime Value)** | Total revenue generated by a subscriber across all subscription orders. | Use to understand **customer value over time** and compare cohorts or segments. | Subscriber Journey (LTV Gross / Net Revenue), Subscriber Journey Monthly (LTV Gross Revenue EOM) |
| **EOM (End of Month)** | Metrics calculated as of the last day of a month. | Used for **consistent month-over-month comparisons** (retention, LTV growth). | Subscriber Journey Monthly (all EOM fields like Active EOM, LTV EOM) |
| **Solo Subscription** | A subscription that contains only one product. | Helps identify products that perform well **individually**. | Subscription Product Metrics Daily (Solo Subscription Count) |
| **Bundle** | A subscription that contains two or more products. | Useful for analyzing **product combinations and cross-sell behavior**. | Product Metrics (Bundle Subscription Count), Bundle Metrics Daily (all bundle fields) |
| **Movement** | Any change in a subscription’s state (created, cancelled, paused, resumed, reactivated, quantity/price change). | Use to understand **operational changes and trends** in subscriptions. | Subscription Movements Daily (Movement Type, Category), Events Enriched (Event Type) |
| **Provider** | The system managing subscriptions (Recharge, ChordOMS, CustomOMS). | Important context — **data availability and detail vary by provider**, which affects analysis. | All Explores (Provider filter present everywhere) |
[title] Sessions
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Salesforce/
### x\_fct\_trans\_sessions
| Name | Description |
| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Anonymous Completed Oms Order Ids | Array of OMS Order IDs associated to the anonymous\_id, as collected by order completed or checkout completed front-end events, over time. |
| Anonymous Completed Order Ids | Array of order IDs associated to the anonymous\_id, as collected by order completed or checkout completed front-end events, over time. |
| Anonymous Completed Order Numbers | Array of order numbers associated to the anonymous\_id, as collected by order completed or checkout completed front-end events, over time. |
| Anonymous Current Blended User Id | Unique id derived from the user\_id and the anonymous\_id. Whenever a customer has a user\_id, the user\_anonymous\_id will be constant for |
| Anonymous Current User Id | The current user\_id associated with the anonymous\_id. This unique user\_id is created by Segment's Identify call. A user\_id can be associated to many anonymous\_ids. |
| Anonymous Id | Unique id created by Chord for each anonymous visitor per store. |
| Anonymous Segment Anonymous Id | Id created by Segment for each anonymous visitor. This id gets created as soon as a customer's browser loads the analytics javascript widget. The anonymous\_id remains unchanged through the entire browsing session from a single device. Depending on configuration, two stores connected stores may have the same anonymous\_id. |
| Anonymous Unique User Ids | Array of user IDs mapped to an anonymous ID. |
| Attribution Point First Touch | The first session associated with the user prior to conversion receives 100% of the attribution, all other sessions recieve 0 points. Reflected with a value of 0 or 1. |
| Attribution Point Forty Twenty Forty | The first and last sessions associated with the user prior to conversion receive 40% of the attribution points each, the remaining middle-touch sessions receive an equal portion of the 20%; 0.4, 0.4, and 0.2/number of remaining sessions. |
| Attribution Point Id | Sessions for a user that occor prior to conversion, or first completed order. |
| Attribution Point Last Touch | The last session associated with the user prior to conversion receives 100% of the attribution, all other sessions recieve 0 points. Reflected with a value of 0 or 1. |
| Attribution Point Linear | All sessions for the user prior to conversion recieve an equal percentage of the attribution points; calculated as 1.0 / number of sessions |
| End Date Day Num Of Year | The number representing the day of the year. |
| End Date Id | Unique key that uniquify a date. |
| End Date Month Num Of Year | The month number of the year. |
| Landing Page Browser Locale | Locale of browser. |
| Landing Page Device | The device on which the event was sent from. |
| Landing Page Device Category | The device category of the device on which the event was sent from. There are multiple supported values for this column such as 'iPhone', |
| Landing Page Event Table Name | The properly formatted name of the table of the event. |
| Landing Page Event Text | The name of the event. |
| Landing Page Event Text Id | The slug of the event name, mapping to the page or track event table. |
| Landing Page Gclid | The Google Click ID. Google Click ID (GCLID) is a parameter passed in the URL with ad clicks, to identify the campaign and other attributes of the click associated with the ad for ad tracking and campaign attribution. |
| Landing Page Id | Unique key generated by Segment for each tracking or page event. |
| Landing Page Oms Id | Unique key generated by our models that uniquifies an OMS. |
| Landing Page Host | The host of the event's URL. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev`. This facilitates grouping events by host. |
| Landing Page Path | The page path part of the URL. A page path is the part of URL that comes after the hostname (domain) and before the query parameters, URL fragment, or port. (e.g. `/pages/contact-us/` for `https://chord.co/pages/contact-us/?ref=internal-banner`.) |
| Landing Page Query | The query string portion of the URL of the page. |
| Landing Page Referrer | The referrer of the page. The referrer is the webpage that sends visitors to the site using a link. In |
| Landing Page Title | The title/name of the page. |
| Landing Page Url | The URL of the page. |
| Landing Page Referrer Host | The host of the referrer. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev`. This facilitates grouping events by host. |
| Landing Page Segment User Id | The unique ID of the user. |
| Landing Page Store Id | Unique key generated by our models that uniquifies a store. |
| Landing Page Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Landing Page User Agent | The User agent of the device making the request. A User agent request header is a characteristic string that lets servers and |
| Landing Page User Id | Unique key generated by Chord to identify the user. |
| Landing Page Utm Campaign | The campaign name represented by the UTM tags. |
| Landing Page Utm Content | The campaign content represented by the UTM tags. |
| Landing Page Utm Medium | The campaign medium represented by the UTM tags. |
| Landing Page Utm Source | The campaign source represented by the UTM tags. |
| Landing Page Utm Term | The campaign term represented by the UTM tags. |
| Landing Page Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store |
| Last Page Browser Locale | Locale of browser. |
| Last Page Device | The device on which the event was sent from. |
| Last Page Device Category | The device category of the device on which the event was sent from. There are multiple supported values for this column such as 'iPhone', |
| Last Page Event Table Name | The properly formatted name of the table of the event. |
| Last Page Event Text | The name of the event. |
| Last Page Event Text Id | The slug of the event name, mapping to the page or track event table. |
| Last Page Gclid | The Google Click ID. Google Click ID (GCLID) is a parameter passed in the URL with ad clicks, to identify the campaign and other attributes of the click associated with the ad for ad tracking and campaign attribution. |
| Last Page Id | Unique key generated by Segment for each tracking or page event. |
| Last Page Oms Id | Unique key generated by our models that uniquifies an OMS. |
| Last Page Host | The host of the event's URL. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev`. This facilitates grouping events by host. |
| Last Page Path | The page path part of the URL. A page path is the part of URL that comes after the hostname (domain) and before the query parameters, URL fragment, or port. (e.g. `/pages/contact-us/` for `https://chord.co/pages/contact-us/?ref=internal-banner`.) |
| Last Page Query | The query string portion of the URL of the page. |
| Last Page Referrer | The referrer of the page. The referrer is the webpage that sends visitors to the site using a link. In |
| Last Page Title | The title/name of the page. |
| Last Page Url | The URL of the page. |
| Last Page Referrer Host | The host of the referrer. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev` . This facilitates grouping events by host. |
| Last Page Segment User Id | The unique ID of the user. |
| Last Page Store Id | Unique key generated by our models that uniquifies a store. |
| Last Page Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Last Page User Agent | The User agent of the device making the request. A User agent request header is a characteristic string that lets servers and |
| Last Page User Id | Unique key generated by Chord to identify the user. |
| Last Page Utm Campaign | The campaign name represented by the UTM tags. |
| Last Page Utm Content | The campaign content represented by the UTM tags. |
| Last Page Utm Medium | The campaign medium represented by the UTM tags. |
| Last Page Utm Source | The campaign source represented by the UTM tags. |
| Last Page Utm Term | The campaign term represented by the UTM tags. |
| Last Page Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store |
| Session Activity Count | Total count of activities, pave views and tracked events within the session. |
| Session Attribution Channel | The attribution channel for the first page event of the session. Sessions with an attribution of 'Unknown' indicates that there is no attributable data for that session. |
| Session Attribution Channel Paid Or Organic | Indicates if the session's first page attribution is paid or organic. Attribution is considered Organic if the attribution channel is 'Direct', 'Other', 'Organic Search', 'Organic Social', 'Email', or 'SMS'. |
| Session Attribution First Page Url Has Gclid | Indicates if the first page event of the session has a Google Click ID. |
| Session Attribution First Page Url Has Utm | Indicates if the first page event of the session has any utm information. |
| Session Attribution Has Referrer | Indicates if the first page event of the session has a referrer host. |
| Session Attribution Medium | The campaign medium represented by the UTM tags for the first page event of the session. |
| Session Attribution Source | The campaign source represented by the UTM tags for the first page event of the session. |
| Session Attribution Sub Channel | Sub-Channel is a granular level of attribution. |
| Session Completed Oms Order Ids | Array of OMS Order IDs associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Session Completed Order Ids | Array of order IDs associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Session Completed Order Numbers | Array of order numbers associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Session Days Since Last Session End | The days between the last session's end and the start of this session. |
| Session Device | The device on which the event was sent from. |
| Session Device Category | The device category of the device on which the event was sent from. There are multiple supported values for this column such as 'iPhone', |
| Session Duration In Seconds | Total seconds between start and end activities within the session. |
| Session Duration In Seconds Tiers | Total seconds between start and end activities within the session, aggregated into tiers: 0-9s, 10-29s, 30-59s, and 60s or more. |
| Session Has Order Completion | Flag for sessions with an order completed or checkout completed front-end events |
| Session Id | Unique ID for the session. |
| Session Number | Session number per anonymous id. |
| Session Unique Completed Order Count | Count of unique order ids associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Session Unique Completed Order Number Count | Count of unique order numbers associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Start Date Day Num Of Year | The number representing the day of the year. |
| Start Date Id | Unique key that uniquify a date. |
| Start Date Month Num Of Year | The month number of the year. |
| Store Id | Unique key generated by our models that uniquifies a store. |
| Store Name | The name of the store. |
| Store Oms Admin Url | The Admin URL of that OMS. |
| Store Oms Id | Unique key generated by Chord that uniquifies an OMS. |
| Store Oms Store Id | Unique key generated by our models that uniquifies a store. |
| Store Oms Type | The type of the OMS. |
| Store Id | Unique key generated by our models that uniquifies a store. |
| Store Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Store Url | The Storefront URL of of the store. |
| User Address 1 | The first line of the street address. |
| User Address 2 | The optional second line of the address. |
| User Address City | The city of the address. |
| User Address Country | The country of the address. |
| User Address Name | The full name of the customer, based on firstName and lastName. |
| User Address State | The region of the address, such as the province, state, or district. |
| User Address Zip | The postal code of the address. |
| User Completed Oms Order Ids | Array of OMS Order IDs associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| User Completed Order Ids | Array of order IDs associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| User Completed Order Numbers | Array of order numbers associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| User Email | The email associated with the user. |
| User Id | Unique ID per user. It is equal to either 1) a identified\_user\_id as identified by Segment in the Identify call, or 2) an anonynous\_id. |
| User Identified User Id | Unique ID per identified user. (See Segment's documentation on user\_id)\[ `https://segment.com/docs/connections/spec/identify/#user-id` ]. |
| User Ip | IP address associated with the user. |
| User Last Anonymous Id | Last seen anonymous\_id per user. An anonymous\_id is a unique ID per anonymous visitor. (See Segment's documentation on anonymous\_id)\[ `https://segment.com/docs/connections/spec/identify/#anonymous-id` ]. |
| User Last Segment Anonymous Id | This column is not documented. |
| User Segment User Id | The unique ID of the user. |
| User Unique Anonymous Ids | Array of all seen anonymous\_ids per user. An anonymous\_id is a unique ID per anonymous visitor. (See Segment's documentation on anonymous\_id)\[ `https://segment.com/docs/connections/spec/identify/#anonymous-id` ]. |
| User Unique Completed Order Count | Count of unique order ids associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| End Ts (Universal) | Last activity timestamp for a session - Universal Time Zone. |
| Landing Page Ts (Universal) | The timestamp calculated by Segment correcting clock skew - Universal Time Zone. |
| Last Page Ts (Universal) | The timestamp calculated by Segment correcting clock skew - Universal Time Zone. |
| Session End Ts (Universal) | Last activity timestamp for a session - Universal Time Zone. |
| Session Last Session End Ts (Universal) | The timestamp of the previous session's end per blended user id, if this is not the user's first session - Universal Time Zone. |
| Session Last Session Start Ts (Universal) | The timestamp of the previous session's start per blended user id, if this is not the user's first session - Universal Time Zone. |
| Session Start Ts (Central) | First activity timestamp for a session - Cental Time Zone. |
| Session Start Ts (Eastern) | First activity timestamp for a session - Eastern Time Zone. |
| Session Start Ts (Mountain) | First activity timestamp for a session - Mountain Time Zone. |
| Session Start Ts (Pacific) | First activity timestamp for a session - Pacific Time Zone. |
| Session Start Ts (Universal) | First activity timestamp for a session - Universal Time Zone. |
| Start Ts (Central) | First activity timestamp for a session - Cental Time Zone. |
| Start Ts (Eastern) | First activity timestamp for a session - Eastern Time Zone. |
| Start Ts (Mountain) | First activity timestamp for a session - Mountain Time Zone. |
| Start Ts (Pacific) | First activity timestamp for a session - Pacific Time Zone. |
| Start Ts (Universal) | First activity timestamp for a session - Universal Time Zone. |
| User Created At (Universal) | The timestamp when the user was created - Universal Time Zone. |
| User First Seen At (Universal) | The first time the user was seen on the site, identified as either anonymous ID or user ID - Universal Time Zone. |
[title] Shopify
[path] Chord Data Platform/Data Models/Chord's Methodology as Compared to Other Platforms/
### Overview
Chord ingests raw data directly from Shopify and then transforms this data through a data modeling layer to clean and enrich for more efficient, enriched, and meaningful analyses. Chord's data models can differ from what users see directly in the Shopify platform.
### Variations Between Chord's Data Models and the Shopify Platform
**Order State**
Chord provides two views of orders:
- Orders placed regardless of fulfillment status or cancellation.
- Completed orders, a subset of all orders defined as an order that has a `closed_at` timestamp and has been fully fulfilled. The `closed_at` timestamp is generated for orders in Shopify that are automatically archived. If this feature is not enabled, the last updated closed fulfillment date is used as the completed date.
Shopify includes any orders placed regardless of fulfillment status or cancellation.
The "Orders" dataset displays all orders, whereas the "Sales" dataset includes completed orders only. To get to a view closer to Shopify, use the “Orders” Explore to view all orders and use the "Order Created At" date field instead of "Order Completed At."
**Timestamps**
Chord's models provides options for both `Order Created At` and `Order Completed At`, or `Closed At`, timestamps.
Shopify uses the last `Edited At` timestamp in reporting if the order was edited, and if not edited, the `Order Created At` timestamp. For example, if an order were placed in January and edited in Shopify in February, it would show in February orders. Yet, unedited orders placed in January would show in January orders. Within Chord, these orders would show either when placed in January or when closed.
**Timezones**
Chord provides various timezones for both the "Order Created At" and "Order Completed At" fields so you can customize them to your timezone. Chord's default timezone is UTC and provides the following additional timezone options: Pacific, Mountain, Central, and Eastern.
In Shopify, the timezone can be configured in settings, so you can check the timezone of your account to then use the same timezone within Chord.
:::hint{type="success"}
if you have any questions or need help, please reach out to us at [help@chord.co](mailto\:help@chord.co)
:::
[title] Pinterest Tag
[path] Chord CDP/CDP Destinations/CDP Destination Catalog/
# **Pinterest Tag** is Pinterest's conversion tracking pixel. It loads the Pinterest Tag JavaScript SDK in the browser and forwards ecommerce events to Pinterest for campaign measurement, audience building, and automated bidding optimization. There is no server-side component.
# Getting Started
This is a device-mode destination. The Pinterest Tag SDK is loaded automatically — no manual script installation is required. You will need:
- **Tag ID** — your Pinterest Tag ID, found in your Pinterest Ads account under **Ads > Conversions**.
Optionally:
- **Use Enhanced Match Loading** — when enabled, passes the user's email to Pinterest during initialization for enhanced matching. Defaults to `false`.
# Connecting to the Pinterest Tag CDP Destination
:::BlockQuote
**Warning:** Before connecting destinations in the Chord CDP, please verify with all Destination owners that all **non-Chord CDP** configured destinations are **disabled**. Running external destinations alongside configured Chord CDP destinations **can result in duplicate events downstream.**
:::
1. Log into the Chord data platform.
2. Navigate to the CDP.
3. Click the **"Add"** button next to Destinations.
4. Select **Pinterest Tag** from the destination catalog.
5. Enter the destination name and your **Tag ID**.
6. Optionally enable **Use Enhanced Match Loading**.
7. Click **"Create"** to connect.
# Events
All Pinterest Tag events include an `event_id` parameter set to the Chord `messageId` for deduplication.
# Event Mapping
# Page Events
**Pinterest SDK call:** `pintrk("track", "PageVisit", pageProps)`
# Identify Events
Sets user identity for Pinterest enhanced matching.
**Pinterest SDK call:** `pintrk("set", { np, em })`
# Product List Viewed
**Pinterest SDK call:** `pintrk("track", "ViewCategory", categoryData)`
# Products Searched / Products List Filtered
Both map to the `Search` event.
**Pinterest SDK call:** `pintrk("track", "Search", searchData)`
# Product Added
**Pinterest SDK call:** `pintrk("track", "AddToCart", cartData)`
# Order Completed
Same attributes as **Product Added** above.
**Pinterest SDK call:** `pintrk("track", "Checkout", checkoutData)`
# Other Track Events
Any unrecognized track event is forwarded using the raw Chord event name.
**Pinterest SDK call:** `pintrk("track", eventName, properties)`
# Line Items
When products are present, each product is mapped to a Pinterest line item:
# Custom Property Forwarding
Configure destination mappings in Hub with `properties.*` destination paths to forward additional event properties into `pintrk("track", ...)` payloads. Only explicitly-configured non-schema fields are forwarded — nothing flows through automatically.
**How to configure:**
1. Open the destination's **Mappings** tab in Hub.
2. Add a mapping with source path `properties.loyalty_tier` and destination path `properties.loyalty_tier`.
3. On the next event, `loyalty_tier` will appear in the event properties payload sent to Pinterest.
**What is excluded:**
- Schema fields already handled by the destination transform (e.g. `currency`, `value`, `order_id`, `line_items`) — these flow through the structured transform
- PII fields (`email`) — handled separately during initialization via enhanced match loading
When a custom mapping targets a schema field (e.g. `properties.value → properties.value`), the customer-configured value overrides the destination's computed default. This allows schema fields to be sourced from a different event property — for example, mapping `properties.total → properties.value` to use your order total as the conversion value.
# Initialization
The plugin loads `https://s.pinimg.com/ct/core.js`, then calls `pintrk("load", tagId)` (optionally with `{ em: email }` if **Use Enhanced Match Loading** is enabled and an email is available on the triggering event), followed by `pintrk("page")` to fire the initial page view.
The plugin manages SDK loading state (`fresh` → `loading` → `loaded`/`failed`) to prevent duplicate script loads. If the script fails to load, subsequent events are silently dropped.
# CSP Requirements
If your site uses a Content Security Policy, allow the following domains:
***
**Updated 27 May 2026**
[title] Messaging Events
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Shopify/
| **Name ** | **Description ** |
| ----------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| AOV | Average Order Value |
| Active On Site | Count of all events of type Active on Site. |
| Bounced Email | Count of all events of type Bounced Email. |
| Bounced Push | Count of all events of type Bounced Push. |
| Clicked Email | Count of all events of type Clicked Email. |
| Clicked SMS | Count of all events of type Clicked SMS. |
| Email Bounce‑to‑Send Rate | Total bounce count / total send count. |
| Email Click Rate | Total of click email count / total delivery email count. |
| Email Click‑to‑Open Rate | Total of all emails clicked / total email open count. |
| Email Conversion‑to‑Delivery Rate | Total conversion count / total delivery count. |
| Email Delivery‑to‑Send Rate | Total delivery count / total send count. |
| Email Open‑to‑Delivery Rate | Total of open email count / total email delivery count. |
| Email Sent | Sum of Bounced and Received Email. |
| Email Unique Click Rate | Total of all unique emails clicked / total emails sent. |
| Email Unique Click Through Rate | Total of unique click email count / total delivery email count. |
| Email Unique Click to Open Rate | Total of unique email clicks / total unique email open count. |
| Email Unique Open Rate | Total of unique open count / total delivery count. |
| Email Unsubscribe Rate | Total unsubscribe from email count / total delivery email count. |
| Failed to Delivery SMS | Count of all events of type Failed to Delivery SMS. |
| Marked Email as Spam | Count of all events of type Marked Email as Spam. |
| Opened Email | Count of all events of type Opened Email. |
| Opened Push | Count of all events of type Opened Push. |
| Ordered Product | Count of all events of type Ordered Product. |
| Placed Order | Count of all events of type Placed Order. |
| Push Bounce‑to‑Send Rate | Total bounce count / total send count. |
| Push Sent | Sum of Bounced and Received Mobile Push. |
| Push Unique Open Rate | Total of all unique pushes clicked / total pushes sent. |
| Received Email | Count of all events of type Received Email. |
| Received Push | Count of all events of type Received Push. |
| Received SMS | Count of all events of type Received SMS. |
| Recipients | Count of all unique events of type Received Email based on person\_id as Last Touch ID. |
| Refunded Order | Count of all events of type Refunded Order. |
| SMS Failed‑to‑delivery Rate | Total of all failed SMS messages / total SMS sent. |
| SMS Unique Click Rate | Total of all unique SMS clicked / total SMS sent. |
| Sent SMS | Count of all events of type Relayed SMS. |
| Subscribed To Back In Stock | Count of all events of type Subscribed to Back In Stock. |
| Subscribed To Email Marketing | Count of all events of type Subscribed to Email Marketing. |
| Subscribed To List | Count of all events of type Subscribed to List. |
| Subscribed to SMS Marketing | Count of all events of type Subscribed to SMS Marketing. |
| Subscribed to SMS Transactional | Count of all events of type Subscribed to SMS Transactional. |
| Total Cancelled Order | From numeric\_value field, the sum of all events where the event type is Cancelled Order. |
| Total Checkout Started | From numeric\_value field, the sum of all events where the event type is Checkout Started. |
| Total Ordered Product | From numeric\_value field, the sum of all events where the event type is Ordered product. |
| Total Placed Order | From numeric\_value field, the sum of all events where the event type is Placed Order. |
| Total Refunded Order | From numeric\_value field, the sum of all events where the event type is Refunded Order. |
| Unique Active On Site | Count of all unique events of type Active on Site based on person\_id as Last Touch ID. |
| Unique Bounced Push | Count of all unique events of type Bounced Push based on person\_id as Last Touch ID. |
| Unique Clicked Email | Count of all unique events of type Clicked Email based on person\_id as Last Touch ID. |
| Unique Clicked SMS | Count of all unique events of type Clicked SMS based on person\_id as Last Touch ID. |
| Unique Count Bounced Email | Count of all unique events of type Bounced Email based on person\_id as Last Touch ID. |
| Unique Failed to Delivery SMS | Count of all unique events of type Failed to Delivery SMS based on person\_id as Last Touch ID. |
| Unique Marked Email as Spam | Count of all unique events of type Marked Email as Spam based on person\_id as Last Touch ID. |
| Unique Opened Email | Count of all unique events of type Opened Email based on person\_id as Last Touch ID. |
| Unique Opened Push | Count of all unique events of type Opened Push based on person\_id as Last Touch ID. |
| Unique Ordered Product | Count of all unique events of type Ordered Product based on person\_id as Last Touch ID. |
| Unique Placed Order | Count of all unique events of type Placed Order based on person\_id as Last Touch ID. |
| Unique Received Push | Count of all unique events of type Received Push based on person\_id as Last Touch ID. |
| Unique Received SMS | Count of all unique events of type Received SMS based on person\_id as Last Touch ID. |
| Unique Refunded Order | Count of all unique events of type Refunded Order based on person\_id as Last Touch ID. |
| Unique Relayed SMS | Count of all unique events of type Relayed SMS based on person\_id as Last Touch ID. |
| Unique Subscribed To Back In Stock | Count of all unique events of type Subscribed to Back In Stock based on person\_id as Last Touch ID. |
| Unique Subscribed To Email Marketing | Count of all unique events of type Subscribed to Email Marketing based on person\_id as Last Touch ID. |
| Unique Subscribed To List | Count of all unique events of type Subscribed to List based on person\_id as Last Touch ID. |
| Unique Subscribed to SMS Marketing | Count of all unique events of type Subscribed to SMS Marketing based on person\_id as Last Touch ID. |
| Unique Subscribed to SMS Transactional | Count of all unique events of type Subscribed to SMS Transactional based on person\_id as Last Touch ID. |
| Unique Unsubscribed | Count of all unique events of type Count Unsubscribed based on person\_id as Last Touch ID. |
| Unique Unsubscribed From Email Marketing | Count of all unique events of type Unsubscribed From Email Marketing based on person\_id as Last Touch ID. |
| Unique Unsubscribed From List | Count of all unique events of type Unsubscribed From List based on person\_id as Last Touch ID. |
| Unique Unsubscribed from SMS Marketing | Count of all unique events of type Unsubscribed to SMS Marketing based on person\_id as Last Touch ID. |
| Unique Unsubscribed from SMS Transactional | Count of all unique events of type Unsubscribed to SMS Transactional based on person\_id as Last Touch ID. |
| Unique Viewed Product | Count of all unique events of type Viewed Product based on person\_id as Last Touch ID. |
| Unsubscribed | Count of all events of type Count Unsubscribed. |
| Unsubscribed From Email Marketing | Count of all events of type Unsubscribed From Email Marketing. |
| Unsubscribed From List | Count of all events of type Unsubscribed to List. |
| Unsubscribed from SMS Marketing | Count of all events of type Unsubscribed to SMS Marketing. |
| Unsubscribed from SMS Transactional | Count of all events of type Unsubscribed to SMS Transactional. |
| Viewed Product | Count of all events of type Viewed Product. |
| Created At | Timestamp of when the campaign or flow was created. |
| Flow Status | Current status of the flow. Either 'manual', 'live', or 'draft'. |
| Is Archived (Yes / No) | Boolean of whether the campaign has been archived or not. |
| Last Touch Campaign Brand | The brand of the campaign set in the Hub amplification. |
| Last Touch Campaign Category | Campaign Category is the highest level of the hierarchy. Ex: Fruit > Berries > Strawberries the Campaign Category is Fruit and covers all Campaigns that are Fruit. |
| Last Touch Campaign Channel | The Attribution Channel of the campaign set in the Hub amplification. Ex: Email, SMS |
| Last Touch Campaign Class | Campaign Class is the third level of the hierarchy. Ex: Fruit > Berries > Strawberries the Campaign Class is Strawberries and includes only Berries that are Strawberries. There can be more than one Campaign within the class. |
| Last Touch Campaign Has Tracking Params (Yes / No) | Indicates if the campaign is configured to store tracking params in the URL. |
| Last Touch Campaign Name Refined | A refined, 'friendlier' name of the campaign set in the Hub amplification. |
| Last Touch Campaign Objective | Objective of the campaign set in the Hub amplification. Ex: Engagement, Retention, Acquisition |
| Last Touch Campaign Option | Other attributes of the campaign not captured in the defined attribute fields. These should be comma separated and set in the Hub amplification. |
| Last Touch Campaign Platform | The Ad Source of the campaign set in the Hub amplification. Ex: Google Ads, TikTok Ads |
| Last Touch Campaign Region | The region of the campaign set in the Hub amplification Ex: US, CA, EU |
| Last Touch Campaign Subcategory | Campaign Subcategory is the middle level of the hierarchy. Ex: Fruit > Berries > Strawberries the Campaign Subcategory is Berries and includes only Fruits that are Berries. |
| Last Touch Campaign Subchannel | Subchannel of the campaign set in the Hub amplification. |
| Last Touch Campaign Temporality | The temporality of the campaign set in the Hub amplification Ex: September Sale, October EVG, 20230504, etc. |
| Last Touch Campaign Type | The type of the campaign set in the Hub amplification. Ex: Transactional, Batch, Automated. |
| Last Touch Flow Brand | The brand of the flow set in the Hub amplification. |
| Last Touch Flow Category | Category for the flow set in the Hub amplification. |
| Last Touch Flow Channel | The Attribution Channel of the flow set in the Hub amplification. Ex: Email, SMS. |
| Last Touch Flow Class | Class for the flow set in the Hub amplification. |
| Last Touch Flow Name Refined | A refined, 'friendlier' name of the flow set in the Hub amplification. |
| Last Touch Flow Objective | Objective of the flow set in the Hub amplification. |
| Last Touch Flow Option | Other attributes of the flow not captured in the defined attribute fields. |
| Last Touch Flow Platform | The Ad Source of the flow set in the Hub amplification. |
| Last Touch Flow Region | The region of the flow set in the Hub amplification. Ex: US, CA, EU. |
| Last Touch Flow Subcategory | Subcategory of the flow set in the Hub amplification. |
| Last Touch Flow Subchannel | Subchannel of the flow set in the Hub amplification. |
| Last Touch Flow Temporality | The temporality of the flow set in the Hub amplification. Ex: September Sale, etc. |
| Last Touch Flow Type | The type of the flow set in the Hub amplification. Ex: Transactional, Batch, Automated. |
| Name (Campaign) | A name for this campaign. If not specified, this will default to the subject of the campaign. |
| Occurred At | Date the event occurred. |
| Session Date | The date of the session this event is associated to. |
| Status | Current status of the campaign. Either 'draft', 'scheduled', 'sent', or 'cancelled'. |
| Touch Type | What kind of touch the event was attributed to -- 'campaign', 'flow', or null. |
| Trigger Type | Corresponds to the object which triggered the flow. |
| UTM Campaign | When the campaign or flow is configured with tracking params, this is the UTM campaign configured. |
| UTM Content | When the campaign or flow is configured with tracking params, this is the UTM content configured. |
| UTM Medium | When the campaign or flow is configured with tracking params, this is the UTM medium configured. |
| UTM Source | When the campaign or flow is configured with tracking params, this is the UTM source configured. |
| UTM Term | When the campaign or flow is configured with tracking params, this is the UTM term configured. |
[title] Omni-Channel Sales
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Shopify/
| **Name** | **Description** |
| ------------------------------------ | ------------------------------------------------------ |
| Fulfillment Channel | Amazon fulfillment channel (null for Shopify). |
| Fulfillment Tax Total | Fulfillment tax (only for Amazon). |
| Line Item Tax Total | Tax amount for the line item (only for Amazon). |
| Order Fulfillment State | Fulfillment state of the order. |
| Order Line Fulfillment Total | Fulfillment cost of the line item. |
| Order Line Gross Revenue | Gross revenue from the line item. |
| Order Line Net Revenue | Net revenue after all deductions. |
| Order Line Promo Total | Total promotional discount applied to the line item. |
| Order Line Refund Total | Total refunded amount for the line item. |
| Promo Total | Total promotions on the order (only for Amazon). |
| Quantity | Number of items purchased. |
| Sales Channel | Sales channel from which the order originated. |
| SKU Price | Unit price of the SKU. |
| Source System | Source of the data: either Amazon or Shopify. |
| Tax Total | Total tax on the order (only for Amazon). |
| Total Price | Total price for the line item. |
| Order Created At | Timestamp when the order was created. |
| Total Fulfillment Tax Total | Total Fulfillment Tax Total. |
| Total Line Item Tax Total | Total Line Item Tax Total. |
| Total Order Line Fulfillment Total | Total Order Line Fulfillment Total. |
| Total Order Line Gross Revenue | Total Order Line Gross Revenue. |
| Total Order Line Net Revenue | Total Order Line Net Revenue. |
| Total Order Line Promo Total | Total Order Line Promo Total. |
| Total Order Line Refund Total | Total Order Line Refund Total. |
| Total Promo Total | Total Promo Total. |
| Total Quantity | Total Quantity. |
| Total SKU Price | Total SKU Price. |
| Total Tax Total | Total Tax Total. |
| Total Total Price | Total Total Price. |
[title] Users
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Shopify/
### **x\_fct\_trans\_users**
| Name | Description |
| ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Billing Address 1 | The street address of the billing address. |
| Billing Address 2 | An additional field for the street address of the billing address. |
| Billing Address City | The city, town, or village of the billing address. |
| Billing Address Company | The company associated to this billing address. |
| Billing Address Country | The name of the country of the billing address. |
| Billing Address Country Code | The two-letter code (ISO 3166-1 format) for the country of the billing address. |
| Billing Address First Name | The first name of the person associated to this billing address. |
| Billing Address Id | Unique identifier generated by Chord for a Billing Address. |
| Billing Address Last Name | The last name of the person associated to this billing address. |
| Billing Address Latitude | The latitude of the billing address. |
| Billing Address Longitude | The longitude of the billing address. |
| Billing Address Name | The full name of the person associated to this billing address. |
| Billing Address Oms Billing Address Id | Unique key generated by Shopify that identifies a billing address. |
| Billing Address Phone | The phone number associated to this billing address. |
| Billing Address Province | The name of the region (province, state, prefecture, …) of the billing address. |
| Billing Address Province Code | The two-letter abbreviation of the region of the billing address. |
| Billing Address Zip | The postal code of the billing address. |
| Shipping Address 1 | The street address of the shipping address. |
| Shipping Address 2 | An additional field for the street address of the shipping address. |
| Shipping Address City | The city, town, or village of the shipping address. |
| Shipping Address Company | The company associated to this shipping address. |
| Shipping Address Country | The name of the country of the shipping address. |
| Shipping Address Country Code | The two-letter code (ISO 3166-1 format) for the country of the shipping address. |
| Shipping Address First Name | The first name of the person associated to this shipping address. |
| Shipping Address Id | Unique identifier generated by Chord for a Shipping Address. |
| Shipping Address Last Name | The last name of the person associated to this shipping address. |
| Shipping Address Latitude | The latitude of the shipping address. |
| Shipping Address Longitude | The longitude of the shipping address. |
| Shipping Address Name | The full name of the person associated to this shipping address. |
| Shipping Address Oms Shipping Address Id | Unique key generated by Shopify that identifies a shipping address. |
| Shipping Address Phone | The phone number associated to this shipping address. |
| Shipping Address Province | The name of the region (province, state, prefecture, ...) of the shipping address. |
| Shipping Address Province Code | The two-letter abbreviation of the region of the shipping address. |
| Shipping Address Zip | The postal code of the shipping address. |
| User Completed Oms Order Ids | List of all completed OMS order ids for a user. |
| User Completed Order Names | List of all completed order names for a user. |
| User Email | The email of the customer. |
| User First Completed Oms Order Id | Order id from the OMS for the first completed order. |
| User First Completed Order Name | Order name for the first completed order. |
| User First Name | The first name of the customer. |
| User First Name Last Initial | The first name and last name initials of the customer. This appends the value of \`first\_name\` and the first character of \`last\_name\` together. |
| User First Order Unique Ordered Products | List of unique products purchased by the user in their first completed order. |
| User First Order Unique Ordered Skus | List of unique variant SKUs purchased by the user in their first completed order. |
| User First Subscription Ids | Array of first subscription ids purchased by the user. The user may have more than one subscription created at the same time, resulting in more than one subscription counted as first. |
| User Full Name | The full name of the customer. This appends the value of \`first\_name\` and \`last\_name\` together. |
| User Has Ordered A La Carte | Whether or not the user has had at least one order that is not a part of a subscription. |
| User Has Promo Applied In First Order | Whether the first completed order has a promo applied or not. |
| User Has Reactivation Subscription | Whether or not the user has at least one subscription created after the first subscription is cancelled. |
| User Has Subscription In First Order | Whether or not the user's first order is linked to a subscription. |
| User Has Verified Email | Whether the customer has verified their email address. |
| User Id | Unique identifier generated by Chord to identify the user. |
| User Is Active Subscriber | Whether or not the user has an active subscription with at least one completed subscription order. An active subscription is one that is not cancelled or paused. Subscribers may have completed subscription orders on inactive subscriptions, but will not be considered active if their current subscription has no completed orders. |
| User Is Customer | Whether the user has completed at least one order or not. |
| User Is New Customer | Whether the user has completed one order or not. |
| User Is Not Customer | Whether the user has no completed orders or not. |
| User Is Returning Customer | Whether the user has completed more than one order or not. |
| User Is Subscriber | Whether or not the user has completed at least one subscription order. |
| User Last Name | The last name of the customer. |
| User Last Subscription Ids | Array of last subscription ids purchased by a user. The user may have more than one subscription created at the same time, resulting in more than one subscription counted as last. |
| User Number Of Cancelled Subscriptions | Total number of subscriptions the user has cancelled. |
| User Number Of Completed A La Carte Orders | Total number of orders completed by a user that are a la carte. |
| User Number Of Completed Orders | Total count of completed orders by the user. |
| User Number Of Completed Subscription Orders | Total number of orders completed by a user that are part of a subscription. |
| User Number Of Created Subscription Orders | Total number of orders created by a user that are part of a subscription. |
| User Number Of Orders With Promos | Count of completed orders with a promo applied. |
| User Number Of Reactivated Subscriptions | Total number of subscriptions for a user that are reactivations. These subscriptions may be active, inactive, or concurrent. |
| User Number Of Subscriptions | Total number of subscriptions linked to a user. These subscriptions may be active, inactive, or concurrent. |
| User Oms User Id | Unique identifier generated by the OMS to identify the user. |
| User Phone | The phone number of the customer. |
| User Unique Ordered Product Type | List of unique product types purchased by the user across all completed orders. |
| User Unique Ordered Products | List of unique products purchased by the user across all completed orders. |
| User Unique Ordered Skus | List of unique variant SKUs purchased by the user across all completed orders. |
| User First Completed Order Completed At (Universal) | Timestamp for the first order completed - Universal Time Zone. |
| User First Completed Order Created At (Universal) | Timestamp for the first completed order created - Universal Time Zone. |
| User First Order Created At (Universal) | Timestamp of the first created order for the user - Universal Time Zone. |
| User First Subscription Created At (Universal) | Timestamp of when the first subscription was created per user - Universal Time Zone. |
| User First Subscription Order Completed At (Universal) | The timestamp of the user's first completed subscription order, regardless of subsequent subscriptions - Universal Time Zone. |
| User First Subscription Order Created At (Universal) | The timestamp of the user's first completed subscription order, regardless of subsequent subscriptions - Universal Time Zone. |
| User Last Completed Order Completed At (Universal) | Timestamp for the most recent order completed - Universal Time Zone. |
| User Last Completed Order Created At (Universal) | Timestamp for the most recent completed order created - Universal Time Zone. |
| Average A La Carte Gross Revenue | Sum of gross revenue generated by all completed a la carte orders for a user. |
| Average A La Carte Net Revenue | Sum of net revenue generated by all completed a la carte orders for a user. |
| Average Additional Tax Total | When taxes are not included in the subtotal, this is total tax added to the order. |
| Average First Order Gross Revenue | Gross revenue of the first completed order. |
| Average First Order Net Revenue | Net revenue of the first completed order. |
| Average Fulfillment Total | The sum of all shipping prices in the location's currency. |
| Average Gross Revenue | Gross revenue of the order calculated as \`item\_total\` + \`fulfillment\_total\` |
| Average Included Tax Total | When taxes are included in the subtotal, this is the total tax included in the order. |
| Average Item Total | The sum of all line item prices in the location's currency. |
| Average Last Order Gross Revenue | Gross revenue of the most recent completed order. |
| Average Last Order Net Revenue | Net revenue of the most recent completed order. |
| Average Manual Transaction Total | Sum of all sales transaction with gateway of type 'manual'. |
| Average Net Revenue | Net revenue of the order calculated as \`item\_total\` + \`fulfillment\_total\` - \`promo\_total\` - \`refund\_total\` |
| Average Order Gross Revenue | The average order gross revenue of completed orders per user. |
| Average Order Net Revenue | The average order net revenue of completed orders per user. |
| Average Order Transaction Total | The average transaction total of completed orders per user. |
| Average Payment Total | Sum of all sales transaction with gateway of type 'shopify\_payments'. |
| Average Promo Total | The total discounts applied to the price of the order in the location's currency. |
| Average Refund Total | Sum of all the transactions that are of kind 'refund' applied to the order. |
| Average Subscription Gross Revenue | Sum of gross revenue generated by all completed subscription orders for a user. |
| Average Subscription Net Revenue | Sum of net revenue generated by all completed subscription orders for a user. |
| Average Tax Total | The sum of all the taxes applied to the order in the location's currency. |
| Average Total Ordered Quantity | The total quantity of variant SKUs purchased the user. |
| Average Total Price | The sum of all line item prices, discounts, shipping, taxes, and tips in the |
| Average Total Unique Ordered Products | The count of unique products purchased the user. |
| Average Transaction Total | Sum of all sale transactions for the order. |
| A La Carte Gross Revenue | Sum of gross revenue generated by all completed a la carte orders for a user. |
| A La Carte Net Revenue | Sum of net revenue generated by all completed a la carte orders for a user. |
| Additional Tax Total | When taxes are not included in the subtotal, this is total tax added to the order. |
| First Order Gross Revenue | Gross revenue of the first completed order. |
| First Order Net Revenue | Net revenue of the first completed order. |
| Fulfillment Total | The sum of all shipping prices in the location's currency. |
| Gross Revenue | Gross revenue of the order calculated as \`item\_total\` + \`fulfillment\_total\` |
| Included Tax Total | When taxes are included in the subtotal, this is the total tax included in the order. |
| Item Total | The sum of all line item prices in the location's currency. |
| Last Order Gross Revenue | Gross revenue of the most recent completed order. |
| Last Order Net Revenue | Net revenue of the most recent completed order. |
| Manual Transaction Total | Sum of all sales transaction with gateway of type 'manual'. |
| Net Revenue | Net revenue of the order calculated as \`item\_total\` + \`fulfillment\_total\` - \`promo\_total\` - \`refund\_total\` |
| Total Ordered Quantity | The total quantity of variant SKUs purchased the user. |
| Payment Total | Sum of all sales transaction with gateway of type 'shopify\_payments'. |
| Total Price | The sum of all line item prices, discounts, shipping, taxes, and tips in the |
| Promo Total | The total discounts applied to the price of the order in the location's currency. |
| Refund Total | Sum of all the transactions that are of kind 'refund' applied to the order. |
| Subscription Gross Revenue | Sum of gross revenue generated by all completed subscription orders for a user. |
| Subscription Net Revenue | Sum of net revenue generated by all completed subscription orders for a user. |
| Tax Total | The sum of all the taxes applied to the order in the location's currency. |
| Transaction Total | Sum of all sale transactions for the order. |
| Total Unique Ordered Products | The count of unique products purchased the user. |
[title] Google Analytics 4
[path] Chord Data Platform/Data Models/Chord's Methodology as Compared to Other Platforms/
# **Overview**
Google Analytics offers an excellent version of attribution, but it doesn’t let you combine attribution with other insights that non-tracked data can deliver. For example, e-commerce merchants might want to compare attribution channels for specific products or for certain user segments.
# Variations Between Chord Data Models and the Google Analytics 4 Platform
## **Timezones**
Chord provides various timezones for timestamp fields so you can customize them to your timezone. Chord's default timezone is UTC and provides the following additional timezone options: Pacific, Mountain, Central, and Eastern.
In Google Analytics 4 (GA4), the timezone can be configured in settings, so you can check the timezone of your account to then use the same timezone within Chord.
## Bounce Rate Calculations
Chord's definition of a bounce is **any single-page session**. On the GA4 platform, a bounce is defined as **any session that was not engaged***,* which means that the bounce rate is now also susceptible to what is also configured as a [key event](https://support.google.com/analytics/answer/9355848?sjid=11469173535203784940-NA) in GA4.
**For example:** If there are single-page sessions with a particular event (such as `order_completed`) and if the same event was also configured as a "key event" via GA4, it will not be counted as a bounce in GA4.
[title] Variant Attributes
[path] Chord Data Platform/Model Amplifications/
:::hint{type="info"}
Note: Our Model Amplifications feature **only accepts files in CSV format at this time. **Please make sure the files you upload are CSV files.
:::
# **Overview**
The Variant Attribute configuration maps additional attributes per variant that may not be available in the OMS. While the OMS may have fields for capturing some attributes within variants, Brand operators often want more flexibility and control over their products.
This configuration provides the ability to add a three-tiered hierarchy per variant including Category, Sub Category, and Class. Utilizing all three layers is not required.
Additional attributes per variant can also be added and updated here including:
- **Color **
- **Function**
- **Material**
- **Shape**
- **Size**
- **Style**
- **Other **- this can include multiple fields not represented by the above attributes, separated by a comma.
All of these attributes flow through the model and are surfaced in the Line Items Explore.
:::hint{type="info"}
**Note: **The configuration allows for only one row per variant.
:::
## Sample Use Cases
While surfacing additional information is useful, these fields can be used to answer more nuanced questions:
- A brand has recently released a new item and want to see performance by size - not just net revenue, but returns over time. Color can be added to pivot and see the performance over time.
- A brand wants to segment their customers based on the purchase of a certain product and the function.
- A brand has different teams working on specific product lines. The hierarchy can be used to quicky filter a dashboard for the individual teams needs without having to build a custom dimension.
Surfacing these fields opens up the ability to slice the data in more dimensions and manage reports in new way.
[title] Delighted
[path] Chord CDP/CDP Destinations/CDP Destination Catalog/
# Introduction
Delighted is a customer experience platform that helps businesses collect, analyze, and act on customer feedback using tools like Net Promoter Score (NPS), CSAT, CES, and more. It enables companies to send surveys via email, web, SMS, and other channels, and provides real-time insights to improve customer satisfaction and loyalty.
# Getting started
To properly use Chord's Delighted destination, your account-specific Delighted API key must be provided.
### **API key**
To find this key, follow the guidelines here:
1. Log into your brand's Delighted account and click on ***Integrations ***in the top ribbon
2. On the Integrations page, select ***API***
3. Copy the key titled ***Your API Key***
#
# Connecting to the Delighted CDP destination
1. Log into the Chord data platform.
2. Navigate to the CDP.
3. Click the **"Add"** button next to Destinations.
4. Select **Delighted **from the destination catalog.
5. Enter in the destination name, the **API Key** and the **Delay** amount (if applicable)
6. Click **"Create" **to connect.
# Chord events relevant for destination
Not all Chord Tracking events are used downstream in your configured destinations. The most relevant and important events in the Chord tracking plan are mapped within the CDP destination, relayed and then ingested in the destination. The Chord tracking plan events used by the [Delighted API](https://app.delighted.com/docs/api/sending-to-people) are:
| **Chord Tracking Event** | *Destination Event* |
| ------------------------ | ------------------------------------------- |
| **All track events** | *person.create (survey is sent by default)* |
| **Identify** | *person.create (no survey sent)* |
**Note: There is no specific event filtering within the Chord Delighted destination**. All Chord `track` and `identify` events are processed regardless of the event name. Chord `track` events create a ***person ***in Delighted and triggers a survey to be sent. Chord `identify` events, by default, create a ***person ***in Delighted but does *not* send a survey.
:::hint{type="danger"}
Before connecting destinations in the Chord CDP, please verify with all Destination owners that all **non-Chord CDP** configured destinations are *disabled.*
**
Running external destinations alongside configured Chord CDP destinations ***can result in duplicate events downstream. ***
:::
[title] Conversions
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Salesforce/
### x\_fct\_trans\_activities
| Name | Description |
| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Activity Event Text | The name of the event. |
| Activity Event Text Id | The slug of the event name, mapping to the page or track event table. |
| Activity Id | The unique identifier of an activities (i.e. Track or Page event). |
| Activity Page Path | The page path part of the URL. A page path is the part of URL that comes after the hostname (domain) and before the query parameters, URL fragment, or port. (e.g. `/pages/contact-us/` for `https://chord.co/pages/contact-us/?ref=internal-banner` .) |
| Activity Page Query | The query string portion of the URL of the page. |
| Activity Page Title | The title/name of the page. |
| Activity Page Url | The URL of the page. |
| Activity Session Activity Count | Total count of activities, pave views and tracked events within the session. |
| Activity Session Attribution Channel | The attribution channel for the first page event of the session. Sessions with an attribution of 'Unknown' indicates that there is no attributable data for that session. |
| Activity Session Attribution Channel Paid Or Organic | Indicates if the session's first page attribution is paid or organic. Attribution is considered Organic if the attribution channel is 'Direct', 'Other', 'Organic Search', 'Organic Social', 'Email', or 'SMS'. |
| Activity Session Attribution First Page Url Has Gclid | Indicates if the first page event of the session has a Google Click ID. |
| Activity Session Attribution First Page Url Has Utm | Indicates if the first page event of the session has any utm information. |
| Activity Session Attribution Has Referrer | Indicates if the first page event of the session has a referrer host. |
| Activity Session Attribution Medium | The campaign medium represented by the UTM tags for the first page event of the session. |
| Activity Session Attribution Source | The campaign source represented by the UTM tags for the first page event of the session. |
| Activity Session Attribution Sub Channel | Sub-Channel is a granular level of attribution. |
| Activity Session Completed Oms Order Ids | Array of OMS Order IDs associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Activity Session Completed Order Ids | Array of order IDs associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Activity Session Completed Order Numbers | Array of order numbers associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Activity Session Days Since Last Session End | The days between the last session's end and the start of this session. |
| Activity Session Device | The device on which the event was sent from. |
| Activity Session Device Category | The device category of the device on which the event was sent from. There are multiple supported values for this column such as 'iPhone', |
| Activity Session Duration In Seconds | Total seconds between start and end activities within the session. |
| Activity Session Duration In Seconds Tiers | Total seconds between start and end activities within the session, aggregated into tiers: 0-9s, 10-29s, 30-59s, and 60s or more. |
| Activity Session Has Order Completion | Flag for sessions with an order completed or checkout completed front-end events |
| Activity Session Id | Unique ID for the session. |
| Activity Session Number | Session number per anonymous id. |
| Activity Session Unique Completed Order Count | Count of unique order ids associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Activity Session Unique Completed Order Number Count | Count of unique order numbers associated to the session\_id, as collected by order completed or checkout completed front-end events. |
| Activity Utm Campaign | The campaign name represented by the UTM tags. |
| Activity Utm Content | The campaign content represented by the UTM tags. |
| Activity Utm Medium | The campaign medium represented by the UTM tags. |
| Activity Utm Source | The campaign source represented by the UTM tags. |
| Activity Utm Term | The campaign term represented by the UTM tags. |
| Activity Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store |
| Anonymous Completed Oms Order Ids | Array of OMS Order IDs associated to the anonymous\_id, as collected by order completed or checkout completed front-end events, over time. |
| Anonymous Completed Order Ids | Array of order IDs associated to the anonymous\_id, as collected by order completed or checkout completed front-end events, over time. |
| Anonymous Completed Order Numbers | Array of order numbers associated to the anonymous\_id, as collected by order completed or checkout completed front-end events, over time. |
| Anonymous Current Blended User Id | Unique id derived from the user\_id and the anonymous\_id. Whenever a customer has a user\_id, the user\_anonymous\_id will be constant for |
| Anonymous Current User Id | The current user\_id associated with the anonymous\_id. This unique user\_id is created by Segment's Identify call. A user\_id can be associated to many anonymous\_ids. |
| Anonymous Id | Unique id created by Chord for each anonymous visitor per store. |
| Anonymous Segment Anonymous Id | Id created by Segment for each anonymous visitor. This id gets created as soon as a customer's browser loads the analytics javascript widget. The anonymous\_id remains unchanged through the entire browsing session from a single device. Depending on configuration, two stores connected stores may have the same anonymous\_id. |
| Anonymous Unique User Ids | Array of user IDs mapped to an anonymous ID. |
| Date Day Num Of Year | The number representing the day of the year. |
| Date Id | Unique key that uniquify a date. |
| Date Month Num Of Year | The month number of the year. |
| Last Seen Page Browser Locale | Locale of browser. |
| Last Seen Page Device | The device on which the event was sent from. |
| Last Seen Page Device Category | The device category of the device on which the event was sent from. There are multiple supported values for this column such as 'iPhone', |
| Last Seen Page Event Table Name | The properly formatted name of the table of the event. |
| Last Seen Page Event Text | The name of the event. |
| Last Seen Page Event Text Id | The slug of the event name, mapping to the page or track event table. |
| Last Seen Page Gclid | The Google Click ID. Google Click ID (GCLID) is a parameter passed in the URL with ad clicks, to identify the campaign and other attributes of the click associated with the ad for ad tracking and campaign attribution. |
| Last Seen Page Id | Unique key generated by Segment for each tracking or page event. |
| Last Seen Page Oms Id | Unique key generated by our models that uniquifies an OMS. |
| Last Seen Page Host | The host of the event's URL. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev`. This facilitates grouping events by host. |
| Last Seen Page Path | The page path part of the URL. A page path is the part of URL that comes after the hostname (domain) and before the query parameters, URL fragment, or port. (e.g. `/pages/contact-us/` for `https://chord.co/pages/contact-us/?ref=internal-banner` .) |
| Last Seen Page Query | The query string portion of the URL of the page. |
| Last Seen Page Referrer | The referrer of the page. The referrer is the webpage that sends visitors to the site using a link. In |
| Last Seen Page Title | The title/name of the page. |
| Last Seen Page Url | The URL of the page. |
| Last Seen Page Referrer Host | The host of the referrer. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev`. This facilitates grouping events by host. |
| Last Seen Page Segment User Id | The unique ID of the user. |
| Last Seen Page Store Id | Unique key generated by our models that uniquifies a store. |
| Last Seen Page Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Last Seen Page User Agent | The User agent of the device making the request. A User agent request header is a characteristic string that lets servers and |
| Last Seen Page User Id | Unique key generated by Chord to identify the user. |
| Last Seen Page Utm Campaign | The campaign name represented by the UTM tags. |
| Last Seen Page Utm Content | The campaign content represented by the UTM tags. |
| Last Seen Page Utm Medium | The campaign medium represented by the UTM tags. |
| Last Seen Page Utm Source | The campaign source represented by the UTM tags. |
| Last Seen Page Utm Term | The campaign term represented by the UTM tags. |
| Last Seen Page Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store |
| Session Landing Page Browser Locale | Locale of browser. |
| Session Landing Page Device | The device on which the event was sent from. |
| Session Landing Page Device Category | The device category of the device on which the event was sent from. There are multiple supported values for this column such as 'iPhone', |
| Session Landing Page Event Table Name | The properly formatted name of the table of the event. |
| Session Landing Page Event Text | The name of the event. |
| Session Landing Page Event Text Id | The slug of the event name, mapping to the page or track event table. |
| Session Landing Page Gclid | The Google Click ID. Google Click ID (GCLID) is a parameter passed in the URL with ad clicks, to identify the campaign and other attributes of the click associated with the ad for ad tracking and campaign attribution. |
| Session Landing Page Id | Unique key generated by Segment for each tracking or page event. |
| Session Landing Page Oms Id | Unique key generated by our models that uniquifies an OMS. |
| Session Landing Page Host | The host of the event's URL. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev`. This facilitates grouping events by host. |
| Session Landing Page Path | The page path part of the URL. A page path is the part of URL that comes after the hostname (domain) and before the query parameters, URL fragment, or port. (e.g. `/pages/contact-us/` for `https://chord.co/pages/contact-us/?ref=internal-banner`.) |
| Session Landing Page Query | The query string portion of the URL of the page. |
| Session Landing Page Referrer | The referrer of the page. The referrer is the webpage that sends visitors to the site using a link. In |
| Session Landing Page Title | The title/name of the page. |
| Session Landing Page Url | The URL of the page. |
| Session Landing Page Referrer Host | The host of the referrer. For example `https://www.store-staging.assembly.dev/myPage` would become `store-staging.assembly.dev`. This facilitates grouping events by host. |
| Session Landing Page Segment User Id | The unique ID of the user. |
| Session Landing Page Store Id | Unique key generated by our models that uniquifies a store. |
| Session Landing Page Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Session Landing Page User Agent | The User agent of the device making the request. A User agent request header is a characteristic string that lets servers and |
| Session Landing Page User Id | Unique key generated by Chord to identify the user. |
| Session Landing Page Utm Campaign | The campaign name represented by the UTM tags. |
| Session Landing Page Utm Content | The campaign content represented by the UTM tags. |
| Session Landing Page Utm Medium | The campaign medium represented by the UTM tags. |
| Session Landing Page Utm Source | The campaign source represented by the UTM tags. |
| Session Landing Page Utm Term | The campaign term represented by the UTM tags. |
| Session Landing Page Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store |
| Store Id | Unique key generated by our models that uniquifies a store. |
| Store Name | The name of the store. |
| Store Oms Admin Url | The Admin URL of that OMS. |
| Store Oms Id | Unique key generated by Chord that uniquifies an OMS. |
| Store Oms Store Id | Unique key generated by our models that uniquifies a store. |
| Store Oms Type | The type of the OMS. |
| Store Id | Unique key generated by our models that uniquifies a store. |
| Store Tenant Id | Unique key generated by Chord that uniquifies a tenant. |
| Store Url | The Storefront URL of of the store. |
| User Address 1 | The first line of the street address. |
| User Address 2 | The optional second line of the address. |
| User Address City | The city of the address. |
| User Address Country | The country of the address. |
| User Address Name | The full name of the customer, based on firstName and lastName. |
| User Address State | The region of the address, such as the province, state, or district. |
| User Address Zip | The postal code of the address. |
| User Completed Oms Order Ids | Array of OMS Order IDs associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| User Completed Order Ids | Array of order IDs associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| User Completed Order Numbers | Array of order numbers associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| User Email | The email associated with the user. |
| User Id | Unique ID per user. It is equal to either 1) a identified\_user\_id as identified by Segment in the Identify call, or 2) an anonynous\_id. |
| User Identified User Id | Unique ID per identified user. (See Segment's documentation on user\_id)\[ `https://segment.com/docs/connections/spec/identify/#user-id` ]. |
| User Ip | IP address associated with the user. |
| User Last Anonymous Id | Last seen anonymous\_id per user. An anonymous\_id is a unique ID per anonymous visitor. (See Segment's documentation on anonymous\_id)\[ `https://segment.com/docs/connections/spec/identify/#anonymous-id` ]. |
| User Last Segment Anonymous Id | This column is not documented. |
| User Segment User Id | The unique ID of the user. |
| User Unique Anonymous Ids | Array of all seen anonymous\_ids per user. An anonymous\_id is a unique ID per anonymous visitor. (See Segment's documentation on anonymous\_id)\[ `https://segment.com/docs/connections/spec/identify/#anonymous-id` ]. |
| User Unique Completed Order Count | Count of unique order ids associated to the user\_id, as collected by order completed or checkout completed front-end events, over time. |
| Activity Session End Ts (Universal) | Last activity timestamp for a session - Universal Time Zone. |
| Activity Session Last Session End Ts (Universal) | The timestamp of the previous session's end per blended user id, if this is not the user's first session - Universal Time Zone. |
| Activity Session Last Session Start Ts (Universal) | The timestamp of the previous session's start per blended user id, if this is not the user's first session - Universal Time Zone. |
| Activity Session Start Ts (Central) | First activity timestamp for a session - Cental Time Zone. |
| Activity Session Start Ts (Eastern) | First activity timestamp for a session - Eastern Time Zone. |
| Activity Session Start Ts (Mountain) | First activity timestamp for a session - Mountain Time Zone. |
| Activity Session Start Ts (Pacific) | First activity timestamp for a session - Pacific Time Zone. |
| Activity Session Start Ts (Universal) | First activity timestamp for a session - Universal Time Zone. |
| Activity Ts (Central) | The timestamp calculated by Segment correcting clock skew - Cental Time Zone. |
| Activity Ts (Eastern) | The timestamp calculated by Segment correcting clock skew - Eastern Time Zone. |
| Activity Ts (Mountain) | The timestamp calculated by Segment correcting clock skew - Mountain Time Zone. |
| Activity Ts (Pacific) | The timestamp calculated by Segment correcting clock skew - Pacific Time Zone. |
| Activity Ts (Universal) | The timestamp calculated by Segment correcting clock skew - Universal Time Zone. |
| Last Seen Page Ts (Universal) | The timestamp calculated by Segment correcting clock skew - Universal Time Zone. |
| Session Landing Page Ts (Universal) | The timestamp calculated by Segment correcting clock skew - Universal Time Zone. |
| User Created At (Universal) | The timestamp when the user was created - Universal Time Zone. |
| User First Seen At (Universal) | The first time the user was seen on the site, identified as either anonymous ID or user ID - Universal Time Zone. |
### x\_fct\_current\_sales\_\_daily
| Name | Description |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Date Day Num Of Year | The number representing the day of the year. |
| Date Id | Unique key that uniquify a date. |
| Date Month Num Of Year | The month number of the year. |
| Ts (Universal) | The truncated UTC date the order was created - Universal Time Zone. |
| Average Completed Order Count | The total count of orders created on the UTC date that have been completed. An order is considered complete if it has a status of 'Fulfilled' or 'Returned' or it has a status 'Canceled' and has a payment associated with it. |
| Average Created Order Count | The total count of orders created on the UTC date. |
| Average Gross Sales | The gross sales for completed orders. An order is considered complete if it has a status of 'Fulfilled' or 'Returned' or it has a status 'Canceled' and has a payment associated with it. |
| Average Net Revenue | The net sales for completed orders. An order is considered complete if it has a status of 'Fulfilled' or 'Returned' or it has a status 'Canceled' and has a payment associated with it. |
| Average Placed Gross Revenue | Gross Revenue is the pre-tax, pre-adjusted total line item price (unit price \* quantity) + the fulfillment total. |
| Average Placed Net Revenue | Net Revenue is the adjusted line item price (unit price \* quantity - line adjustments) + the adjusted fulfillment (fulfillment total - line adjustments) - order level adjustments - refunds. |
| Completed Order Count | The total count of orders created on the UTC date that have been completed. An order is considered complete if it has a status of 'Fulfilled' or 'Returned' or it has a status 'Canceled' and has a payment associated with it. |
| Created Order Count | The total count of orders created on the UTC date. |
| Gross Sales | The gross sales for completed orders. An order is considered complete if it has a status of 'Fulfilled' or 'Returned' or it has a status 'Canceled' and has a payment associated with it. |
| Net Revenue | The net sales for completed orders. An order is considered complete if it has a status of 'Fulfilled' or 'Returned' or it has a status 'Canceled' and has a payment associated with it. |
| Placed Gross Revenue | Gross Revenue is the pre-tax, pre-adjusted total line item price (unit price \* quantity) + the fulfillment total. |
| Placed Net Revenue | Net Revenue is the adjusted line item price (unit price \* quantity - line adjustments) + the adjusted fulfillment (fulfillment total - line adjustments) - order level adjustments - refunds. |
[title] Pinning and Unpinning Reports
[path] Chord Data Platform/Analytics Features/
# Introduction
:::hint{type="info"}
**A note on terminology:**
A **report** on the Chord platform can refer to either a **dashboard** or a **Look** (which also known as an **explore**). A **dashboard** is made up of a collection of **Looks** (**explores**).
:::
Shared folders and report pinning enables streamlined access to reports and efficient collaboration, especially when managing complex data needs across teams. The **Pinned Reports** page allows users to store and view key reports, making it easy for all stakeholders to access vital company reports in one central location. With report pinning, users can easily denote high-priority reports so that the most mission-critical reports.
Together, these features support Chord’s mission of empowering e-commerce brands to make informed, data-driven decisions faster and with greater confidence.
# Getting started
You can pin personal reports that have been added to your company’s shared folder or any of the quickstarts offered on our data platform.
To create a new report, follow these instructions: [Creating Custom Reports](https://docs.chord.co/creating-custom-reports).
## Pin a report
To pin a report, you can find the relevant report you’d like to use under **Shared Reports** or **Quickstarts**.
Click the **Pin **button to place the desired dashboard or Look to your organization’s **Pinned Reports** page. The reports will be organized and displayed alphabetically on the **Pinned Reports **tab.
***Note that you cannot pin reports directly from your personal folder*** (**My Reports**). To pin a report that is currently in your personal folder, you must first promote and share that report to your organization’s **Shared Reports**.
## Unpin a report
To unpin a report, find the relevant report you’d like to remove on the **Pinned Reports** page. Click on the **Unpin **icon to remove the report from the **Pinned Reports** page.
You can also choose to unpin a pinned report via **Shared Reports** and **Quickstarts** as well.
# FAQs and troubleshooting
- **Question: Am I still able to publish reports in My Reports?**
- No. With the introduction of pinning and unpinning reports, we are no longer supporting the publishing (and unpublishing flow). You can now share any dashboard or Look you want from your personal reports folder into your organization’s shared reports folder.
[title] Analytics Features
[path] Chord Data Platform/
Chord provides our customers with many ways to explore, drill into, visualize, and interact with dashboards and datasets. These introductory articles will help you learn various ways to analyze the data within Chord's platform.
::::LinkArray{contentSource="CUSTOM"}
:::LinkArrayItem{headerType="COLOR" headerColor="#e70ecb"}
[Modifying a Report](docId\:o0DcETIai7zJpE0KA_k_Z)
:::
:::LinkArrayItem{headerType="COLOR" headerColor="#08eb0d"}
[Creating Custom Calculations](docId\:UYDUa-D3xb1HYqEji71AZ)
:::
:::LinkArrayItem{headerType="COLOR" headerColor="#e70ecb"}
[Analytics Glossary](docId\:Fpt4aisPEKBSwvU0y6b6V)
:::
:::LinkArrayItem{headerType="COLOR" headerColor="#112df0"}
[Login Looker FAQ](docId\:B9llaL1wZkZW0cNhOy0Bi)
:::
:::LinkArrayItem
[Looks vs Dashboards](docId\:fA4DAozF7HCePGaTo545d)
:::
:::LinkArrayItem{headerType="COLOR" headerColor="#e70ecb"}
[Chord Data Models](docId\:WrZedQ3_AsfqtB3yj4owA)
:::
:::LinkArrayItem{headerType="COLOR" headerColor="#280df1"}
[Creating Custom Fields](docId:-SPL6T9NwSJsMGiNFZRf3)
:::
:::LinkArrayItem{headerType="COLOR" headerColor="#06f14d"}
[Scheduling Reports](docId\:E_uN9QRhGPB0HfNm4-LTy)
:::
:::LinkArrayItem{headerType="COLOR" headerColor="#e70ecb"}
[Creating Custom Reports](docId\:tHtxyLZcR7OwMGHP3U8JS)
:::
::::
[title] Shopify
[path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/
### *Table names for customers utilizing Shopify*
- [Activities](https://docs.chord.co/rMpK-activities)
- [Ads](https://docs.chord.co/ads)
- [Conversions](https://docs.chord.co/X04m-conversions)
- [Line Items](https://docs.chord.co/V4Ck-line-items)
- [Marketing Attribution](https://docs.chord.co/marketing-attribution)
- [Messaging Events](docId\:AGakAnptsXULVe8pAi7Ch)
- [Messaging Lists](docId\:bD2STULWbtS8nLveVnzWp)
- [Messaging Segments](docId\:FifHtmo5bsN8OvFouip3R)
- [Omni-Channel Sales](docId\:vlB_A079thuNHLkvkXoYe)
- [Orders](https://docs.chord.co/orders)
- [Sales](https://docs.chord.co/VaMi-sales)
- [Sessions](https://docs.chord.co/sessions)
- [Users](https://docs.chord.co/PLPk-users)
### Accessing Chord Data Attribute Definitions:
:::hint{type="success"}
if you have any questions or need help, please reach out to us at [help@chord.co](mailto\:help@chord.co)
:::
[title] Braze (Device Mode)
[path] Chord CDP/CDP Destinations/CDP Destination Catalog/Untitled/
# Introduction
Braze is a customer engagement platform that helps brands deliver personalized, real-time messaging across channels like email, push notifications, SMS, and in-app messages. It connects user behavior data with messaging tools, enabling marketers to create targeted, automated campaigns that drive retention, conversion, and loyalty—all from a single platform.
# Getting started
This is a device mode destination. You will need the Braze API key to connect this destination. **Note that this key is distinct from your Braze 'Classic' API key. **
You can find the correct API key under **Settings > App Settings > Web > API key**.
# Connecting to the Braze (Device Mode) CDP destination
1. Log into the Chord data platform.
2. Navigate to the CDP.
3. Click the **"Add"** button next to Destinations.
4. Select **Braze (Device Mode) **from the destination catalog.
5. Enter in the destination name and the **Braze API key**.
6. Click **"Create" **to connect.
# Chord events relevant for destination
Not all Chord Tracking events are used downstream in your configured destinations. The most relevant and important events in the Chord tracking plan are mapped within the CDP destination, relayed and then ingested in the destination. The Chord tracking plan events used by the [Braze (Device Mode)](https://docs.customer.io/integrations/data-out/connections/braze/#track-event) destiantion are:
| **Chord Tracking Event** | *Destination Event* |
| -------------------------- | ---------------------------------------- |
| **Order Completed** | *logPurchase* |
| **All Other Track Events** | *logCustomEvent* |
| **Identify** | *getUser *(updates user attributes) |
:::hint{type="danger"}
Before connecting destinations in the Chord CDP, please verify with all Destination owners that all **non-Chord CDP** configured destinations are *disabled.*
**
Running external destinations alongside configured Chord CDP destinations ***can result in duplicate events downstream. ***
:::
[title] MNTN Conversions Pixel (Server-Side)
[path] Chord CDP/CDP Destinations/CDP Destination Catalog/
**MNTN Conversion Pixel** is MNTN's conversion tracking pixel for Connected TV (CTV) attribution and ROAS reporting. This destination fires a JavaScript pixel on conversion events (purchases, sign-ups, leads), enabling MNTN to attribute conversions to CTV ad exposure and optimize campaigns. There is no server-side component.
For site-wide audience building and page-level attribution, use this destination alongside the [MNTN Tracking Pixel]().
# Getting Started
This is a device-mode destination. The pixel fires by dynamically inserting a `
```
If you'd like to implement this yourself instead, you need to add two attributes:
| Attribute name | Description | Example value |
| ----------------- | ------------------------------------------------------------------------ | -------------------------------------- |
| `_cdpAnonymousId` | CDP session identifier. Read this from the `ajs_anonymous_id` cookie. | `32e5434e-ed1a-42bf-acd9-64de286879fa` |
| `_googleClientId` | Google client ID. Read this from the `_ga` cookie, with `.substring(6)`. | `961446296.1716300180` |
In a Shopify theme, you can add cart attributes using the [Cart API](https://shopify.dev/docs/api/ajax/reference/cart#update-cart-attributes). We recommend adding these attributes at a time that doesn’t block user interaction with your site, like when the cart page loads or after a product is added to the cart.
See [Unifying Data Across Sources](docId\:FYmI5G8eWB-YYpyh-GU4o) for more details.
[title] TikTok Conversions API
[path] Chord CDP/CDP Destinations/CDP Destination Catalog/
The **TikTok Conversions API** destination sends event data directly from Chord CDP to TikTok's servers, bypassing the browser entirely. Unlike the [TikTok Pixel (device mode)](), server-side events are immune to ad blockers and browser tracking restrictions, providing more reliable signal for attribution and optimization.
Use this destination alongside the [TikTok Pixel destination]() for maximum data coverage. TikTok deduplicates events using the `event_id` field.
# Getting Started
This is a cloud-mode destination. You will need:
- **Access Token** — generated via TikTok Ads Manager or the TikTok API. Found in **Assets > Events > Web Events > Settings**.
- **Pixel Code** — your TikTok Pixel ID, found in your TikTok Ads Manager under **Assets > Events > Web Events**.
Optionally:
- **Test Event Code** — a test event code from the TikTok Ads events manager. When set, events are tagged for test mode and will appear in the TikTok test events dashboard.
# Connecting to the TikTok Conversions API CDP Destination
:::BlockQuote
**Warning:** Before connecting destinations in the Chord CDP, please verify with all Destination owners that all **non-Chord CDP** configured destinations are **disabled**. Running external destinations alongside configured Chord CDP destinations **can result in duplicate events downstream.**
:::
1. Log into the Chord data platform.
2. Navigate to the CDP.
3. Click the **"Add"** button next to Destinations.
4. Select **TikTok Conversions API** from the destination catalog.
5. Enter the destination name, **Access Token**, and **Pixel Code**.
6. Optionally enter a **Test Event Code** during initial setup.
7. Click **"Create"** to connect.
# Events
# Event Mapping
| Chord Event | TikTok Event |
| --------------------------- | -------------------------------------------------------- |
| `page` | `PageView` |
| `Order Completed` | `CompletePayment` |
| `Checkout Started` | `InitiateCheckout` |
| `Product Added` | `AddToCart` |
| `Product Viewed` | `ViewContent` |
| `Products Searched` | `Search` |
| `Payment Info Entered` | `AddPaymentInfo` |
| `Product Added to Wishlist` | `AddToWishlist` |
| `Product Clicked` | `ClickButton` |
| `Signed Up` | `CompleteRegistration` |
| `Subscription Created` | `Subscribe` |
| *(any other track event)* | Chord event name passed as-is See [Custom Events]() |
# User Data (All Events)
All user data fields are SHA-256 hashed before sending, except where noted.
| TikTok Attribute | Chord Source (Priority Order) | Notes |
| ---------------- | --------------------------------------------------------------------------------------------------- | ------------------------------------------------------- |
| `external_id` | `userId` > `anonymousId` | SHA-256 hashed |
| `email` | `properties.email` > `context.traits.email` | SHA-256 hashed, lowercased |
| `phone` | `properties.phone` > `context.traits.phone` | SHA-256 hashed, E.164 format |
| `first_name` | `properties.first_name` > `context.traits.first_name` | SHA-256 hashed |
| `last_name` | `properties.last_name` > `context.traits.last_name` | SHA-256 hashed |
| `city` | `properties.address.city` > `context.traits.address.city` | Lowercased, non-alphanumeric chars removed (not hashed) |
| `state` | `properties.address.state` > `context.traits.address.state` | Lowercased, non-alphanumeric chars removed (not hashed) |
| `country` | `properties.address.country` > `context.traits.address.country` | Lowercased, non-alphanumeric chars removed (not hashed) |
| `zip_code` | `properties.address.postal_code` / `properties.address.zip_code` > `context.traits.address.zipcode` | SHA-256 hashed |
| `ip` | `context.ip` | Not hashed |
| `user_agent` | `context.userAgent` | Not hashed |
| `locale` | `context.locale` | Not hashed |
| `ttclid` | `properties.ttclid` > URL query param `ttclid` | TikTok click ID |
| `ttp` | `properties.ttp` | TikTok cookie |
# Page Data (All Events)
| TikTok Attribute | Chord Source (Priority Order) |
| ---------------- | ----------------------------------------------- |
| `url` | `properties.url` > `context.page.url` |
| `referrer` | `properties.referrer` > `context.page.referrer` |
# Event Data (All Events)
| TikTok Attribute | Chord Source | Notes |
| ------------------ | ------------------------------------------------ | --------------------------------------------- |
| `event` | Mapped event name | See event mapping above |
| `event_time` | `timestamp` | Unix seconds; falls back to current time |
| `event_id` | `messageId` | Used for deduplication with device-mode pixel |
| `limited_data_use` | `event.limited_data_use` (top-level event field) | Defaults to `false` |
# Order Properties (All Track Events)
| TikTok Attribute | Chord Source (Priority Order) | Notes |
| ---------------- | ------------------------------------------------------------------------------------------- | -------------------------------- |
| `currency` | `properties.currency` | |
| `value` | `properties.value` > `properties.revenue` > calculated from `contents` (`price × quantity`) | |
| `order_id` | `properties.order_id` | |
| `shop_id` | `properties.shop_id` | |
| `content_type` | `properties.content_type` | `"product"` or `"product_group"` |
| `description` | `properties.description` | |
| `query` | `properties.query` > `properties.search_term` | Relevant for Products Searched |
# Multi-Product Events
For **Order Completed**, **Checkout Started**, and **Payment Info Entered**, products are read from `properties.products[]`:
| TikTok Attribute | Chord Source |
| ------------------ | ---------------------------------- |
| `content_id` | `properties.products[].product_id` |
| `content_name` | `properties.products[].name` |
| `content_category` | `properties.products[].category` |
| `price` | `properties.products[].price` |
| `quantity` | `properties.products[].quantity` |
| `brand` | `properties.products[].brand` |
# Single-Product Events
For **Product Added**, **Product Viewed**, **Product Clicked**, **Products Searched**, and **Product Added to Wishlist**, product data is read from top-level `properties`:
| TikTok Attribute | Chord Source |
| ------------------ | ----------------------- |
| `content_id` | `properties.product_id` |
| `content_name` | `properties.name` |
| `content_category` | `properties.category` |
| `price` | `properties.price` |
| `quantity` | `properties.quantity` |
| `brand` | `properties.brand` |
# Custom Events
Any `track` event that does not match a Chord tracking plan event name is forwarded to TikTok using the Chord event name as-is. TikTok accepts arbitrary event names for reporting and audience segmentation, though only TikTok standard event names support campaign bid optimization.
The following non-tracking-plan events have explicit TikTok standard event name mappings and will be translated automatically if your storefront fires them:
| Chord Event | TikTok Event | Notes |
| ----------------------- | ------------ | ----------------------------------------------------------------- |
| `Form Submitted` | `SubmitForm` | Sends `form_name` from `properties.form_name` > `properties.name` |
| `Callback Started` | `Contact` | |
| `Download Link Clicked` | `Download` | |
If the TikTok event name you want to fire does not match your Chord event name, use a property mapping in the Hub to rename the event before it reaches this destination.
# Testing and Validation
After connecting the destination:
1. Set a **Test Event Code** in the destination configuration.
2. Trigger events from your storefront or use the **Live Events** tab in the Chord CDP.
3. In TikTok Ads Manager, navigate to **Assets > Events > Web Events** and open the **Test Events** tab to verify events are received.
4. Remove the **Test Event Code** before going live to avoid events being excluded from campaigns.
# Custom Property Forwarding
Configure destination mappings in Hub with `properties.*` destination paths to forward additional event properties into the TikTok event's `properties` object (the same object that holds `currency`, `value`, `contents`, etc.). Only explicitly-configured non-schema fields are forwarded — nothing flows through automatically.
**How to configure:**
1. Open the destination's **Mappings** tab in Hub.
2. Add a mapping with source path `properties.loyalty_tier` and destination path `properties.loyalty_tier`.
3. On the next event, `loyalty_tier` will appear in the properties payload sent to TikTok.
**What is excluded:**
- Schema fields already handled by the destination transform (e.g. `currency`, `value`, `order_id`, `contents`) — these flow through the structured transform
- PII fields (`email`, `phone`, `first_name`, `last_name`) — these are handled via `user_data` with SHA-256 hashing
When a custom mapping targets a schema field (e.g. `properties.value → properties.value`), the customer-configured value overrides the destination's computed default. This allows schema fields to be sourced from a different event property — for example, mapping `properties.total → properties.value` to use your order total as the conversion value.
***
**Updated 27 May 2026**
[title] StackAdapt Pixel
[path] Chord CDP/CDP Destinations/CDP Destination Catalog/
**StackAdapt** is a programmatic advertising platform for native, display, video, and connected TV campaigns. This destination loads the StackAdapt Universal Pixel in the browser and forwards identify and track events for conversion measurement and audience targeting. There is no server-side component.
# Getting Started
This is a device-mode destination. The StackAdapt Universal Pixel is loaded automatically — no manual script installation is required. You will need:
- **Pixel ID** — your Universal Pixel ID, found in the **Pixels** page in your StackAdapt account.
# Connecting to the StackAdapt CDP Destination
:::BlockQuote
**Warning:** Before connecting destinations in the Chord CDP, please verify with all Destination owners that all **non-Chord CDP** configured destinations are **disabled**. Running external destinations alongside configured Chord CDP destinations **can result in duplicate events downstream.**
:::
1. Log into the Chord data platform.
2. Navigate to the CDP.
3. Click the **"Add"** button next to Destinations.
4. Select **StackAdapt** from the destination catalog.
5. Enter the destination name and your **Pixel ID**.
6. Click **"Create"** to connect.
# Events
# Event Mapping
| Chord Event Type | StackAdapt SDK Call | Notes |
| ---------------- | -------------------------------------- | ---------------------------------------------------------------- |
| `page` | `saq("ts", pixelId)` | Page view tracking call |
| `identify` | *(stores user traits in memory)* | Traits attached to subsequent track events; not sent immediately |
| `track` | `saq("conv", pixelId, conversionData)` | All track events forwarded as conversions |
# Page Events
Fires a StackAdapt page view tracking call.
**StackAdapt SDK call:** `saq("ts", pixelId)`
No additional attributes are sent with page events.
# Identify Events
Identify events store user traits in browser memory. These traits are **not** sent to StackAdapt immediately — they are attached to all subsequent track conversion events for the duration of the browser session.
| StackAdapt Trait | Chord Source (Priority Order) |
| ---------------- | --------------------------------------------------------------------------- |
| `email` | `properties.email` > `context.traits.email` > `traits.email` |
| `first_name` | `properties.first_name` > `context.traits.first_name` > `traits.first_name` |
| `last_name` | `properties.last_name` > `context.traits.last_name` > `traits.last_name` |
| `phone` | `properties.phone` > `context.traits.phone` > `traits.phone` |
# Track Events
Sends a conversion event to StackAdapt with ecommerce data and any previously stored user traits from `identify` calls.
**StackAdapt SDK call:** `saq("conv", pixelId, conversionData)`
## Always Included
| StackAdapt Attribute | Chord Source | Notes |
| -------------------- | ------------------------------ | --------------------------------------- |
| `action` | `event` (the track event name) | |
| `email` | Stored from `identify` | Included if an `identify` call was made |
| `first_name` | Stored from `identify` | Included if an `identify` call was made |
| `last_name` | Stored from `identify` | Included if an `identify` call was made |
| `phone` | Stored from `identify` | Included if an `identify` call was made |
## Order-Level Attributes
| StackAdapt Attribute | Chord Source (Priority Order) | Notes |
| -------------------- | ----------------------------------------------------------------------------------------- | ----------------------------------------- |
| `order_id` | `properties.cart_id` / `properties.order_id` | Included if present |
| `revenue` | `properties.revenue` > `properties.total` > `properties.value` > calculated from products | Prefers subtotal (excluding tax/shipping) |
| `currency` | `properties.currency` | Defaults to `"USD"` |
## Product Attributes (Single Product)
When `properties.products[]` contains exactly one product, product fields are sent as flat attributes:
| StackAdapt Attribute | Chord Source (Priority Order) |
| -------------------- | ------------------------------------------------------------------------------------------------ |
| `product_id` | `properties.products[0].product_id` > `properties.products[0].id` > `properties.products[0].sku` |
| `product_category` | `properties.products[0].category` |
| `product_name` | `properties.products[0].name` |
| `product_price` | `properties.products[0].price` |
| `product_quantity` | `properties.products[0].quantity` — defaults to `1` |
## Product Attributes (Multiple Products)
When `properties.products[]` contains two or more products, they are sent as a `products` array. Each element uses the same field mapping as the single product above. Empty product objects are filtered out.
# Initialization
The plugin loads the StackAdapt Universal Pixel script. The plugin manages SDK loading state (`fresh` → `loading` → `loaded`/`failed`) to prevent duplicate script loads. If the script fails to load, subsequent events are silently dropped.
# CSP Requirements
If your site uses a Content Security Policy, allow the following domains:
| Directive | Domain |
| ------------- | --------------------------------------------------------- |
| `script-src` | `https://tags.srv.stackadapt.com` |
| `connect-src` | `https://tags.srv.stackadapt.com`, `https://qvdt3feo.com` |
| `style-src` | `https://tags.srv.stackadapt.com` |
***
**Updated 6 Apr 2026**
[title] Integrations
[path] Chord Event Tracking/Guides/
## *What are integrations?*
Integrations connect your software to third-party applications so they can share information with each other. They share data from one system to the next which provides you with more features and options while using your software.
[title] Shopify consent management
[path] Chord Event Tracking/Getting started/Shopify/
Chord integrates with Shopify's Customer Privacy API to manage user consent preferences. This ensures events are only sent to destinations that the customer has consented to, helping you comply with privacy regulations like GDPR and CCPA.
## How It Works
Before sending any events, Chord checks the customer's consent status using Shopify's Customer Privacy API:
1. The custom web pixel checks if tracking is allowed by verifying that both `analyticsProcessingAllowed()` and `marketingAllowed()` return `true`.
2. If tracking is not allowed, no events are sent to the Chord CDP.
3. If tracking is allowed, a consent object is attached to every event describing the customer's preferences for each consent category.
4. The Chord CDP uses the consent category mappings you configure to determine which destinations receive each event.
## Step 1: Confirm Pixel Settings
In your Shopify Admin, go to **Customer Events > Custom Pixels > Your Chord CDP Pixel **and confirm the options in the `Customer privacy` configuration above the pixel code
**Note: **These settings are ***recommended*** by the Chord team as the CDP pixel is deployed with these permissions in mind. If these need to be set to a different configuration, please reach out to ***help\@chord.co ***
### Permission
- `Required` - **selected**
- `Marketing` - **enabled**
- `Analytics` - **enabled**
**Why "Required" with Marketing + Analytics:**
When set to "Required", Shopify populates the `customerPrivacyStatus` object that the pixel reads. The Marketing and Analytics checkboxes tell Shopify that these are the consent categories relevant to this pixel. Without them, the consent fields may not reflect the visitor's actual choices.
### Data Sale
- `Data collected qualifies as data sale` - **selected**
**Why "Data collected qualifies as data sale":**
This ensures the `saleOfDataAllowed` flag is populated when a visitor opts out of data sale (e.g., under CCPA). If set to "does not qualify", this flag would always return as allowed, even if the visitor opted out.
## Step 2: Configure Customer Privacy in Shopify
In your Shopify Admin, go to **Settings > Customer privacy**.
### Cookie Banner (Required)
The cookie banner **must** be enabled for Chord's consent management to work. Without it, the Customer Privacy API is unavailable and Chord will not send any events.
To enable:
1. Select **Cookie banner** > **Activate cookie banner**.
2. Choose the regions where the banner should appear.
3. Click **Activate**.
Alternatively, to use a custom banner from the Shopify App Store:
1. Select **Cookie banner** > **More actions** > **Use custom cookie banner**.
2. Choose regions and click **Activate**.
### Data Sales Opt-Out Page (Recommended)
Allows visitors to control how their data is shared with third parties.
1. Select **Data-sales opt-out page**.
2. Choose regions and click **Activate**.
## Step 3: Configure Consent Categories in Chord CDP
Shopify's Customer Privacy API provides four consent categories. You need to map these in the Chord CDP so events are routed to the correct destinations based on customer preferences.
In the Chord CDP, navigate to **CDP > Consent Categories > Create Your First Consent Category** and add these four categories:
| Category Name (customizable) | Category ID (must be exact) |
| ---------------------------- | --------------------------- |
| Performance cookies | `analytics` |
| Marketing cookies | `marketing` |
| Preference cookies | `preferences` |
| Sale of data | `sale_of_data` |
For each category, choose which destinations should be mapped. Mapping a destination to a category means that destination will only receive events if the customer has consented to that category.
### Consent Category Definitions
- **analytics** — Customer analytics about storefront usage and interactions. Collected by Shopify's cookie banner as "performance cookies."
- **marketing** — Marketing, attribution, and targeted advertising. Collected as "marketing cookies."
- **preferences** — Customer preferences such as language, currency, and size. Collected as "preference cookies."
- **sale\_of\_data** — Sharing data with third parties for behavioral advertising. Collected by Shopify's data sales opt-out page.
## How Consent Is Transmitted
The custom web pixel reads the customer's consent preferences from the Customer Privacy API and constructs a consent object on every event:
```json
{
"analytics": true,
"marketing": true,
"preferences": true,
"sale_of_data": false
}
```
The values are determined by Shopify's Customer Privacy API methods:
| Category | Shopify API Method |
| -------------- | ------------------------------------------------ |
| `analytics` | `customerPrivacy.analyticsProcessingAllowed()` |
| `marketing` | `customerPrivacy.marketingAllowed()` |
| `preferences` | `customerPrivacy.preferencesProcessingAllowed()` |
| `sale_of_data` | `customerPrivacy.saleOfDataAllowed()` |
## Global Privacy Control (GPC)
Chord CDP recognizes the Global Privacy Control signal as an opt-out of data sales. If a customer has GPC activated in their browser and is browsing from a region where opting out is supported, the `sale_of_data` category will be set to `false`.
## No Additional Code Required
Consent management is handled automatically by the custom web pixel and the Chord CDP. You do not need to add any consent-related code to your storefront — the web pixel reads consent status from Shopify's Customer Privacy API and includes it with every event.
[title] Configuration
[path] Chord Event Tracking/Getting started/
This page documents all configuration options for the `@chordcommerce/analytics` library.
## Initialization Options
| Property | Required | Default | Description |
| ------------------------ | -------- | --------- | ---------------------------------------------------------------------------------------------- |
| `cdpDomain` | Yes\* | — | Your Chord domain (provided by the Chord team) |
| `cdpWriteKey` | Yes\* | — | Your Chord write key (provided by the Chord team) |
| `cdp` | No\* | — | Reference to an external analytics library. If provided, events are also sent to that library. |
| `formatters` | Yes | — | Functions for transforming your platform's data into the Chord tracking plan format |
| `metadata` | Yes | — | Event metadata identifying your store and platform |
| `consent` | No | — | Consent adapter: `"onetrust"`, `"ketch"`, or `"shopify"` |
| `awaitConsent` | No | `false` | If `true`, delays sending events until consent is given (timeout: 1 minute) |
| `debug` | No | `false` | Validates events against the tracking plan and logs warnings. Recommended during development. |
| `enableLogging` | No | `true` | Logs errors via `console.log` |
| `namespace` | No | `"chord"` | The global namespace where the Chord instance is available (e.g., `window.chord`) |
| `stripNull` | No | `true` | Removes properties with null values from events before sending |
| `enableWebPixelListener` | No | `true` | Receives events from Chord's Shopify custom web pixel. Disable if not using the web pixel. |
:::BlockQuote
\*At least one of `cdpDomain`/`cdpWriteKey` or `cdp` must be provided. If all three are omitted, no events are sent.
:::
## Metadata
Metadata is included with every event and identifies your store to Chord.
```typescript
metadata: {
i18n: {
currency: 'USD', // ISO 4217 currency code (uppercase)
locale: 'en-US', // Locale string
},
ownership: {
omsId: '...', // UUID assigned by Chord
storeId: '...', // UUID assigned by Chord
tenantId: '...', // UUID assigned by Chord
},
platform: {
name: 'Shopify', // Your commerce platform name
type: 'web', // 'web' or 'pos'
},
store: {
domain: 'my-store', // Store slug (for Shopify: the part before .myshopify.com)
},
}
```
### Metadata Fields
| Property | Required | Description |
| ----------------------------- | -------- | ------------------------------------------------------------- |
| `metadata.i18n.currency` | Yes | ISO 4217 currency code, uppercase (e.g., `USD`, `GBP`, `EUR`) |
| `metadata.i18n.locale` | Yes | Locale string (e.g., `en-US`, `fr-FR`) |
| `metadata.ownership.omsId` | Yes | UUID assigned by Chord (unique per store) |
| `metadata.ownership.storeId` | Yes | UUID assigned by Chord (unique per store) |
| `metadata.ownership.tenantId` | Yes | UUID assigned by Chord (unique per organization) |
| `metadata.platform.name` | Yes | Commerce platform name (e.g., `Shopify`, `Custom`) |
| `metadata.platform.type` | Yes | Platform type: `web` or `pos` |
| `metadata.store.domain` | Yes | Store domain or slug |
## Formatters
Formatters are functions that transform your platform's data structures into the format expected by the Chord tracking plan. There are two types: **object formatters** (required) and **event formatters** (optional).
### Object Formatters (Required)
You must provide formatters for four core data types. Each formatter receives a props object and returns a plain object matching the Chord tracking plan schema.
| Formatter | Input | Description |
| ----------------------------- | -------------- | ----------------------------------------------------- |
| `formatters.objects.cart` | `{ cart }` | Transforms your cart object into tracking plan format |
| `formatters.objects.checkout` | `{ checkout }` | Transforms your checkout object |
| `formatters.objects.lineItem` | `{ lineItem }` | Transforms a single line item |
| `formatters.objects.product` | `{ product }` | Transforms a single product |
Example:
```typescript
formatters: {
objects: {
cart: ({ cart }) => ({
cart_id: cart.id,
products: cart.lines.map(line => ({
product_id: line.merchandise.product.id,
sku: line.merchandise.sku,
name: line.merchandise.product.title,
price: parseFloat(line.merchandise.price.amount),
quantity: line.quantity,
category: line.merchandise.product.productType,
})),
}),
checkout: ({ checkout }) => ({
order_id: checkout.id,
revenue: parseFloat(checkout.subtotalPrice.amount),
total: parseFloat(checkout.totalPrice.amount),
tax: parseFloat(checkout.totalTax.amount),
shipping: parseFloat(checkout.shippingLine?.price.amount || '0'),
currency: checkout.currencyCode,
products: checkout.lineItems.map(item => ({
product_id: item.variant.product.id,
sku: item.variant.sku,
name: item.title,
price: parseFloat(item.variant.price.amount),
quantity: item.quantity,
})),
}),
lineItem: ({ lineItem }) => ({
product_id: lineItem.merchandise.product.id,
sku: lineItem.merchandise.sku,
name: lineItem.merchandise.product.title,
price: parseFloat(lineItem.merchandise.price.amount),
quantity: lineItem.quantity,
}),
product: ({ product }) => ({
product_id: product.id,
sku: product.variants?.[0]?.sku,
name: product.title,
price: parseFloat(product.priceRange.minVariantPrice.amount),
category: product.productType,
brand: product.vendor,
url: `/products/${product.handle}`,
image_url: product.featuredImage?.url,
}),
},
}
```
### Event Formatters (Optional)
Event formatters run after Chord constructs the event from object formatters, allowing you to transform or enrich specific events before they are sent to Chord. This is useful when you need to add custom properties or override default behavior for specific events.
## TypeScript Support
The library accepts a generic type parameter for type-safe formatter inputs:
```typescript
interface ObjectTypes {
Cart: ShopifyCart
Checkout: ShopifyCheckout
LineItem: ShopifyLineItem
Product: ShopifyProduct
}
const chord = new ChordAnalytics(options)
```
Individual formatter types are also available:
```typescript
import type { CartFormatter, ProductFormatter } from '@chordcommerce/analytics'
const cartFormatter: CartFormatter = ({ cart }) => {
// `cart` is typed as ShopifyCart
return { /* ... */ }
}
```
[title] Custom storefront installation
[path] Chord Event Tracking/Getting started/Custom storefront/
# Custom Storefront Installation
This guide covers adding Chord event tracking to custom-built storefronts, standalone websites, or commerce platforms other than Shopify.
## Prerequisites
Before starting, ensure you have the values listed in [Getting Started]().
## Step 1: Install the Package
```shell
npm install @chordcommerce/analytics@1.21.3
# or
yarn add @chordcommerce/analytics@1.21.3
```
## Step 2: Initialize the Library
`@chordcommerce/analytics` is a browser-side library. It requires access to `window` and the DOM to load destination scripts, listen for events, and send tracking data. **It must not be initialized during server-side rendering (SSR).**
If your framework renders pages on the server (Next.js, Remix, Nuxt, Hydrogen, etc.), you must ensure Chord only initializes in the browser. Here are several approaches:
### Option A: React `useEffect` (Recommended for React frameworks)
`useEffect` only runs in the browser, never during SSR. This is the simplest and most idiomatic approach for React-based frameworks like Next.js and Hydrogen.
```tsx
'use client'
import { ChordAnalytics } from '@chordcommerce/analytics'
import { createContext, useContext, useEffect, useRef } from 'react'
const ChordContext = createContext(null)
export function ChordProvider({ children }: { children: React.ReactNode }) {
const chordRef = useRef(null)
useEffect(() => {
if (!chordRef.current) {
chordRef.current = new ChordAnalytics({
cdpDomain: process.env.NEXT_PUBLIC_CHORD_DOMAIN,
cdpWriteKey: process.env.NEXT_PUBLIC_CHORD_WRITE_KEY,
formatters: {
objects: {
cart: (props) => { /* transform cart data */ },
checkout: (props) => { /* transform checkout data */ },
lineItem: (props) => { /* transform line item data */ },
product: (props) => { /* transform product data */ },
},
},
metadata: {
i18n: { currency: 'USD', locale: 'en-US' },
ownership: {
omsId: process.env.NEXT_PUBLIC_CHORD_OMS_ID!,
storeId: process.env.NEXT_PUBLIC_CHORD_STORE_ID!,
tenantId: process.env.NEXT_PUBLIC_CHORD_TENANT_ID!,
},
platform: { name: 'Custom', type: 'web' },
store: { domain: 'your-store-domain' },
},
})
}
}, [])
return (
{children}
)
}
export function useChord() {
return useContext(ChordContext)
}
```
Then wrap your app in `` and use the `useChord()` hook in any component that needs to send tracking events.
### Option B: Next.js Dynamic Import with `ssr: false`
This prevents the Chord module from being imported on the server entirely. Useful when you want to isolate all Chord logic in a single component.
```tsx
import dynamic from 'next/dynamic'
const ChordProvider = dynamic(() => import('./ChordProvider'), { ssr: false })
export default function Layout({ children }) {
return (
{children}
)
}
```
### Option C: `typeof window` Guard
The simplest approach for non-React frameworks or plain JavaScript. Check for the browser environment before initializing.
```typescript
import { ChordAnalytics } from '@chordcommerce/analytics'
if (typeof window !== 'undefined') {
window.chord = new ChordAnalytics({
cdpDomain: 'your-chord-domain',
cdpWriteKey: 'your-chord-write-key',
// ... rest of config
})
}
```
:::hint{type="info"}
**Important: **The formatter examples above are illustrative. You must map your platform's specific data structures to the fields expected by the Chord tracking plan. See Configuration for detailed formatter documentation.
:::
## Step 3: Add Tracking Calls
Once initialized, use the SDK methods to track commerce events:
```typescript
// Page views
chord.page()
// Product interactions
chord.trackProductViewed({ cart, product: { product, quantity: 1 } })
chord.trackProductAdded({ cart, product: { product, quantity: 1 } })
chord.trackProductRemoved({ cart, lineitem })
// Cart
chord.trackCartViewed({ cart })
// Checkout
chord.trackCheckoutStarted({ checkout })
chord.trackPaymentInfoEntered({ checkoutId, step: 1, paymentMethod: 'credit_card' })
// Orders
chord.trackOrderCompleted({
orderId: 'ORD-123',
orderDate: '2026-03-09',
currency: 'USD',
revenue: 89.99,
total: 99.99,
products: [{ /* ... */ }],
})
// User identity
chord.identify(userId, { email: 'user@example.com' })
```
See [SDK API Reference]() for the complete list of tracking methods and their parameters.
## Step 4: Add Environment Variables
```javascript
CHORD_DOMAIN=https://your-chord-domain
CHORD_WRITE_KEY=your-write-key
CHORD_OMS_ID=your-oms-id
CHORD_STORE_ID=your-store-id
CHORD_TENANT_ID=your-tenant-id
```
## TypeScript Support
The library supports generic type parameters for improved type safety:
```typescript
interface MyObjectTypes {
Cart: MyCartType
Checkout: MyCheckoutType
LineItem: MyLineItemType
Product: MyProductType
}
const chord = new ChordAnalytics(options)
// Now chord.trackProductViewed expects { product: MyProductType }
```
## Verifying the Installation
1. Set `debug: true` in your configuration options during development. This validates events against the tracking plan and logs warnings for missing or incorrect properties.
2. Check the browser console for Chord event logging.
3. Verify events appear in the Chord Live Events view.
[title] SDK API reference
[path] Chord Event Tracking/Getting started/
Complete reference for all tracking methods available in the `@chordcommerce/analytics` library.
## Page Views
### `chord.page()`
Sends a page view event to Chord.
```typescript
chord.page()
```
***
## User Identity
### `chord.identify(userId, traits)`
Sends an identify event to associate a user with their traits. Call this after account creation, login, or when a user submits identifying information.
```typescript
chord.identify(userId, { email, phone, firstName, lastName })
// or without userId:
chord.identify({ email, phone })
```
| Property | Type | Required | Description |
| -------- | -------- | -------- | -------------------------------------- |
| `userId` | `string` | No | The user's unique identifier |
| `traits` | `object` | No | User traits (email, phone, name, etc.) |
:::BlockQuote
**Best practice:** Send `identify` before `track` events when both occur at the same time. Some downstream integrations require identity to be established before processing track events.
:::
### `chord.reset()`
Resets the user session. The user receives a new anonymous identifier and previous user data is cleared. Call this after logout.
```typescript
chord.reset()
```
***
## Product Events
### `chord.trackProductViewed({ cart, product })`
Sends a "Product Viewed" event. Call this whenever a product page is viewed.
| Property | Type | Required | Description |
| ------------------- | -------- | -------- | --------------------------- |
| `cart` | `any` | Yes | The current cart |
| `product.product` | `any` | Yes | Product and variant details |
| `product.position` | `number` | No | Position in a list |
| `product.quantity` | `number` | No | Quantity |
| `product.variantId` | `any` | No | Product variant identifier |
### `chord.trackProductAdded({ cart, product })`
Sends a "Product Added" event when a product is first added to cart (not for quantity changes).
Same parameters as `trackProductViewed`.
### `chord.trackProductRemoved({ cart, lineitem })`
Sends a "Product Removed" event when a product is removed from cart.
| Property | Type | Required | Description |
| ---------- | ----- | -------- | ---------------------- |
| `cart` | `any` | Yes | The cart after removal |
| `lineitem` | `any` | Yes | The removed line item |
### `chord.trackProductClicked({ cart, product, listId, listName })`
Sends a "Product Clicked" event when a product link is clicked.
| Property | Type | Required | Description |
| ------------------ | -------- | -------- | -------------------- |
| `cart` | `any` | Yes | The current cart |
| `product.product` | `any` | Yes | Product details |
| `product.position` | `number` | No | Position in the list |
| `listId` | `any` | No | List identifier |
| `listName` | `string` | No | List name |
### `chord.trackProductListViewed({ category, listId, listName, products })`
Sends a "Product List Viewed" event.
| Property | Type | Required | Description |
| ---------- | -------- | -------- | -------------------- |
| `category` | `string` | No | Product category |
| `listId` | `string` | No | List identifier |
| `listName` | `string` | No | List name |
| `products` | `array` | Yes | Products in the list |
### `chord.trackProductListFiltered({ category, listId, listName, filters, sorts })`
Sends a "Product List Filtered" event when filters are applied.
| Property | Type | Required | Description |
| ---------- | -------- | -------- | ------------------------------------- |
| `category` | `string` | No | Product category |
| `listId` | `string` | No | List identifier |
| `listName` | `string` | No | List name |
| `filters` | `array` | No | Applied filters (`[{ type, value }]`) |
| `sorts` | `array` | No | Applied sorts (`[{ type, value }]`) |
### `chord.trackProductsSearched({ query })`
Sends a "Products Searched" event.
| Property | Type | Required | Description |
| ----------- | -------- | -------- | ----------------------- |
| `query` | `string` | No | Search query |
| `productId` | `any` | No | Product ID searched for |
| `currency` | `string` | No | ISO 4217 currency code |
| `price` | `number` | No | Product price |
| `quantity` | `number` | No | Quantity |
***
## Cart Events
### `chord.trackCartViewed({ cart })`
Sends a "Cart Viewed" event.
| Property | Type | Required | Description |
| -------- | ----- | -------- | ---------------- |
| `cart` | `any` | Yes | The current cart |
***
## Checkout Events
### `chord.trackCheckoutStarted({ checkout })`
Sends a "Checkout Started" event.
| Property | Type | Required | Description |
| ---------- | ----- | -------- | -------------------- |
| `checkout` | `any` | Yes | The current checkout |
### `chord.trackCheckoutStepViewed({ checkoutId, step })`
Sends a "Checkout Step Viewed" event.
| Property | Type | Required | Description |
| ---------------- | -------- | -------- | ------------------- |
| `checkoutId` | `string` | Yes | Checkout identifier |
| `step` | `number` | Yes | Step number |
| `paymentMethod` | `string` | No | Payment method |
| `shippingMethod` | `string` | No | Shipping method |
### `chord.trackCheckoutStepCompleted({ checkoutId, step })`
Sends a "Checkout Step Completed" event.
Same parameters as `trackCheckoutStepViewed`.
### `chord.trackPaymentInfoEntered({ checkoutId, step })`
Sends a "Payment Info Entered" event.
| Property | Type | Required | Description |
| ---------------- | -------- | -------- | -------------------- |
| `checkoutId` | `string` | No | Checkout identifier |
| `step` | `number` | Yes | Step number |
| `paymentMethod` | `string` | No | Payment method used |
| `shippingMethod` | `string` | No | Shipping method |
| `coupon` | `string` | No | Coupon code |
| `currency` | `string` | No | Currency code |
| `orderId` | `string` | No | Order identifier |
| `value` | `number` | No | Total value |
| `products` | `array` | No | Products in checkout |
***
## Order Events
### `chord.trackOrderCompleted({ orderId, orderDate, currency, revenue, total, products })`
Sends an "Order Completed" event.
| Property | Type | Required | Description |
| ----------- | -------- | -------- | ---------------------------- |
| `orderId` | `string` | Yes | Order identifier |
| `orderDate` | `string` | Yes | Date of completion |
| `currency` | `string` | Yes | Currency code |
| `revenue` | `number` | Yes | Revenue (subtotal) |
| `total` | `number` | Yes | Total with discounts/coupons |
| `products` | `array` | Yes | Products in the order |
***
## Coupon Events
### `chord.trackCouponApplied({ cartId, couponId, couponName, discount, orderId })`
Sends a "Coupon Applied" event after successful application.
| Property | Type | Required | Description |
| ------------ | -------- | -------- | ------------------------ |
| `cartId` | `string` | No | Cart identifier |
| `couponId` | `string` | No | Coupon identifier |
| `couponName` | `string` | No | Coupon name |
| `discount` | `number` | No | Monetary discount amount |
| `orderId` | `string` | No | Order identifier |
### `chord.trackCouponDenied({ cartId, couponId, couponName, orderId, reason })`
Sends a "Coupon Denied" event.
Same parameters as `trackCouponApplied`, plus `reason` (`string`, optional).
### `chord.trackCouponEntered({ cartId, couponId, couponName, discount, orderId })`
Sends a "Coupon Entered" event immediately after entry, before approval/denial.
Same parameters as `trackCouponApplied`.
### `chord.trackCouponRemoved({ cartId, couponId, couponName, discount, orderId })`
Sends a "Coupon Removed" event.
Same parameters as `trackCouponApplied`.
***
## Email & Login Events
### `chord.trackEmailCaptured({ email, placementComponent, placementPage })`
Sends an "Email Captured" event when a customer enters an email address.
| Property | Type | Required | Description |
| -------------------- | -------- | -------- | --------------------------------------------------- |
| `email` | `string` | No | Email address captured |
| `placementComponent` | `string` | No | UI component identifier (e.g., `footer-newsletter`) |
| `placementPage` | `string` | No | Page identifier (e.g., `homepage`) |
### `chord.trackLoginStarted({ email })`
Sends a "Login Started" event.
| Property | Type | Required | Description |
| -------- | -------- | -------- | -------------------- |
| `email` | `string` | No | Email used for login |
***
## Authentication Events
### `chord.trackSignedIn({ email, method })`
Sends a "Signed In" event after successful login.
| Property | Type | Required | Description |
| -------- | -------- | -------- | ------------ |
| `email` | `string` | No | User's email |
| `method` | `string` | No | Login method |
### `chord.trackSignedUp({ email, method })`
Sends a "Signed Up" event after successful signup.
Same parameters as `trackSignedIn`.
### `chord.trackSignedOut({ email })`
Sends a "Signed Out" event after successful logout.
| Property | Type | Required | Description |
| -------- | -------- | -------- | ------------ |
| `email` | `string` | No | User's email |
***
## Navigation Events
### `chord.trackNavigationClicked({ category, label, navigationPlacement, navigationTitle, navigationUrl })`
Sends a "Navigation Clicked" event.
| Property | Type | Required | Description |
| --------------------- | -------- | -------- | ------------------------------------ |
| `category` | `string` | No | Navigation category |
| `label` | `string` | No | Navigation label |
| `navigationPlacement` | `string` | No | Placement (e.g., `header`, `footer`) |
| `navigationTitle` | `string` | No | Navigation title |
| `navigationUrl` | `string` | No | Target URL |
***
## Variant Events
### `chord.trackVariantClicked({ product, cart, lineItemId, coupon })`
Sends a "Variant Clicked" event.
| Property | Type | Required | Description |
| ------------ | -------- | -------- | -------------------- |
| `product` | `any` | Yes | The variant clicked |
| `cart` | `any` | Yes | The current cart |
| `lineItemId` | `string` | No | Line item identifier |
| `coupon` | `string` | No | Coupon code |
***
## Subscription Events
### `chord.trackSubscriptionCancelled({ subscriptionId, ... })`
Sends a "Subscription Cancelled" event.
| Property | Type | Required | Description |
| ---------------- | -------- | -------- | ------------------------------ |
| `subscriptionId` | `string` | No | Subscription identifier |
| `email` | `string` | No | Associated email |
| `brand` | `string` | No | Associated brand |
| `currency` | `string` | No | Currency code |
| `intervalLength` | `number` | No | Subscription interval length |
| `intervalUnits` | `string` | No | Interval units (e.g., `month`) |
| `state` | `string` | No | Subscription state |
| `products` | `array` | No | Products in subscription |
| `actionableDate` | `string` | No | Actionable date |
| `endDate` | `string` | No | End date |
| `address` | `object` | No | Associated address |
***
## Generic Track Method
### `chord.track(eventName, properties)`
Sends a custom event directly to Chord. This bypasses formatters and sends properties as-is.
```typescript
chord.track('Custom Event Name', {
custom_property: 'value',
another_property: 123,
})
```
:::hint{type="info"}
**Important: **This method does not use formatters or transform property names. Use snake\_case for all property names. Prefer event-specific methods when available.
:::
[title] Subscription Resumed
[path] Chord Event Tracking/Server Events/Track/
This event is triggered when a paused subscription was resumed.
# Properties
| **Name** | **Type** | **Description** | **Required** |
| --------------------- | ---------- | -------------------------------------------------------------------------------------------------------------------------------------- | ------------ |
| `subscription_id` | `string` | Unique ID of the subscription | Yes |
| `interval_length` | `number` | Combined with `interval_units`, specifies the cadence of the subscription. E.g. for a **3 week** cadence, this value will be `3`. | No |
| `interval_units` | `string` | Combined with `interval_length`, specifies the cadence of the subscription. E.g. for a **3 week** cadence, this value will be `weeks`. | No |
| `actionable_date` | `string` | ISO date when the next installment order will be generated. | No |
| `state` | `string` | State of the subscription (e.g. `active`, `paused`, `canceled`). | No |
| `payment_method_name` | `string` | Name of the payment method for installment orders. | No |
| `email` | `string` | Email address associated with the subscription | No |
| `canceled_at` | `string` | ISO date when the subscription was canceled, if applicable | No |
| `canceled_by` | `string` | Email address of the user who canceled the subscription, if applicable | No |
| `activated_at` | `string` | ISO date when the subscription was activated | Yes |
| `address` | `object` | Shipping address of the subscription. | Yes |
| `products` | `object[]` | Products in the subscription | Yes |
## Address
| **Name** | **Type** | **Description** | **Required** |
| ------------------- | -------- | -------------------------------------------------------- | ------------ |
| `address1` | `string` | The street address of the customer | No |
| `address2` | `string` | Additional street address of the customer (if necessary) | No |
| `alternative_phone` | `string` | Customer's alternative phone number | No |
| `phone` | `string` | Customer's phone number | No |
| `city` | `string` | City of the shipping address | No |
| `company` | `string` | Name of the company, if applicable | No |
| `country` | `string` | ISO country code for the shipping address | No |
| `name` | | Customer name | No |
| `state` | `string` | ISO state code for the shipping address | No |
| `zipcode` | `string` | Zip or postal code for the shipping address | No |
## Products array
| **Name** | **Type** | **Description** | **Required** |
| -------------- | -------- | ---------------------------------------------------------------------------------------- | ------------ |
| `affiliation` | `string` | Store or affiliation from which this transaction occurred (for example, "Google Store"). | No |
| `brand` | `string` | Brand associated with the product | No |
| `line_item_id` | `string` | ID of the line item in the database | No |
| `name` | `string` | Name of the product | Yes |
| `position` | `number` | Position in the product list | No |
| `price` | `number` | Price of the product | Yes |
| `product_id` | `string` | ID of the product in the database | Yes |
| `quantity` | `number` | The quantity of products purchased in this line item | Yes |
| `revenue` | `number` | Revenue ($) associated with this line item (excluding shipping and tax) | Yes |
| `sku` | `string` | SKU of the variant | Yes |
| `variant_name` | `string` | Name of the variant | No |
| `variant_id` | `string` | ID of the variant in the database | No |
# Sample Payload
```json
{
"type": "track",
"event": "Subscription Resumed",
"properties": {
"subscription_id": "1",
"interval_length": 3,
"interval_units": "weeks",
"actionable_date": "2026-01-01T00:00:00.000Z",
"state": "active",
"payment_method_name": "Stripe",
"email": "user@example.com",
"canceled_at": null,
"canceled_by": null,
"activated_at": "2026-01-01T00:00:00.000Z",
"address": {
"address1": "123 Fake St",
"address2": null,
"alternative_phone": null,
"phone": "123456789",
"city": "Oak Lawn",
"state": "IL",
"country": "US",
"name": "John Doe",
"zipcode": "60532"
},
"products": [
{
"affiliation": "Affiliation",
"brand": "Brand",
"line_item_id": "16207084552295",
"name": "Product Name",
"position": 1,
"price": 219,
"product_id": "7036464939671",
"quantity": 1,
"revenue": 219,
"sku": "SKU123",
"variant": "Variant Name",
"variant_id": "40952658057847"
}
]
}
}
```
# Example
```bash
curl https://production.cdp.ingest.chord.co/api/track \
--header "Content-Type: application/json" \
--header "X-Write-Key: $CDP_WRITE_KEY" \
--data-raw '
{
"type": "track",
"event": "Subscription Resumed",
"properties": {
"subscription_id": "1",
"interval_length": 3,
"interval_units": "weeks",
"actionable_date": "2026-01-01T00:00:00.000Z",
"state": "active",
"payment_method_name": "Stripe",
"email": "user@example.com",
"canceled_at": null,
"canceled_by": null,
"activated_at": "2026-01-01T00:00:00.000Z",
"address": {
"address1": "123 Fake St",
"address2": null,
"alternative_phone": null,
"phone": "123456789",
"city": "Oak Lawn",
"state": "IL",
"country": "US",
"name": "John Doe",
"zipcode": "60532"
},
"products": [
{
"affiliation": "Affiliation",
"brand": "Brand",
"line_item_id": "16207084552295",
"name": "Product Name",
"position": 1,
"price": 219,
"product_id": "7036464939671",
"quantity": 1,
"revenue": 219,
"sku": "SKU123",
"variant": "Variant Name",
"variant_id": "40952658057847"
}
]
}
}
'
```
[title] Verifying Your Chord Implementation
[path] Chord Event Tracking/Getting started/
## **Front End/Client Side Events**
Follow these steps to verify the installation and implementation of the Chord client on your website:
1. Inspect the markup of any page on your site, you should see a script tag similar to the following inside the `` tags:
```javascript
```
2. Open your browser’s dev tools and select the Network tab. Search “ingest”. You should see your CDP domain loading with a 200 status code.
3. Take actions on your site to trigger events. Viewing products, Adding to cart, etc. You should see these events post to the CDP domain with your write key and formatted properties:
4. In the Chord platform, navigate to CDP —> Live Events —> Incoming Events. Filter the list by your website source. You will see a live stream of events with search and filter capabilities.
## **Back End/Server Events**
Follow these steps to verify the implementation of the Chord client with your back end systems:
1. Trigger a notification from the system that sends data to Chord i.e a webhook notification for Order Completed, Checkout Started, etc.
2. In the Chord platform, navigate to CDP —> Live Events —> Incoming Events. Filter the list by your back end source. You will see a live stream of events with search and filter capabilities.
[title] Guides
[path] Chord Event Tracking/
[title] The Context Object
[path] Chord Event Tracking/
Every analytics event in the Chord CDP carries a `context` object alongside its `properties`. While `properties` describe what happened in the event, `context` describes the environment in which it happened — the page, the user's device, their location, and any identity traits that have been associated with them.
Destination plugins use `context` fields as fallback sources when event properties are not present. For example, a user's email set via an `identify` call will be available on all subsequent track events as `context.traits.email`.
# How Context Is Populated
How `context` gets populated depends on whether the event originates from a browser (via the Chord SDK) or is sent server-to-server (S2S).
## Browser Events
Browser events are those sent by the `@chordcommerce/analytics` SDK running in the user's browser. The SDK and Chord's ingest layer together populate `context` automatically — no extra configuration required:
**Automatically by the Chord SDK**
- `context.page` — current URL, path, referrer, title
- `context.userAgent` — browser user agent string
- `context.locale` — browser locale (e.g. `en-US`)
- `context.library` — SDK name and version
- `context.screen` — screen dimensions and density
- `context.campaign` — UTM parameters parsed from the URL
- `context.clientIds` — third-party client IDs (GA4, Facebook, Amplitude) read from cookies
**From **`identify`** calls**
When your code calls `identify(userId, traits)`, the traits are stored and attached to all subsequent events as `context.traits`. This is the mechanism that makes user attributes like email, name, and address available on track events without repeating them in every event's `properties`.
**Enriched at ingest (browser events only)**
Chord's ingest layer adds the following from the HTTP request headers for browser-originated events:
- `context.ip` — originating IP address
- `context.userAgent` — extracted from the `User-Agent` header if not already set by the SDK
- `context.locale` — extracted from the `Accept-Language` header if not already set by the SDK
- `context.page.url/path/search/host` — populated from the HTTP `Referer` header if not already set
## Server-to-Server (S2S) Events
S2S events are sent directly from your backend using a server-side write key. Because there is no browser involved, **no context fields are added automatically** — the ingest layer does not extract user agent, locale, or page data from S2S requests.
For S2S events, `context` contains only what you explicitly include in the event payload. If your server-side event should carry page, trait, or campaign context, you must attach it yourself before sending.
**Recommended practice:** When sending S2S events that correspond to a browser action (e.g. an order confirmation triggered server-side), forward the user agent and any UTM parameters your frontend captured, and include them in the event's `context` object.
## Geolocation Enrichment
`context.geo` is resolved from `context.ip` and is only meaningful for browser events. For browser events, `context.ip` is captured automatically from the HTTP request, so geo fields are always populated.
For S2S events, the originating IP belongs to your server, not the end user, so geolocation derived from it has no value. `context.geo` will not be present on S2S events.
# Schema Reference
## context.page
URL and navigation context for the current page. Populated automatically by the browser SDK for browser events. For S2S events, populate these fields manually if the event relates to a specific page.
| Field | Type | Description |
| ------------------ | ------ | ------------------ |
| `url` | string | Full page URL |
| `path` | string | URL path component |
| `host` | string | Hostname |
| `referrer` | string | Referrer URL |
| `referring_domain` | string | Referrer hostname |
| `search` | string | Query string |
| `title` | string | Page title |
## context.traits
User traits from the most recent `identify` call. These persist across events for the browser session. Destination plugins use these as fallbacks when event `properties` do not carry the same information.
### Standard Traits
| Field | Type | Description |
| ------------ | ------ | ------------------------ |
| `email` | string | User email address |
| `phone` | string | Phone number |
| `first_name` | string | First name |
| `last_name` | string | Last name |
| `name` | string | Full name |
| `address` | object | See address schema below |
### context.traits.address
The standard address schema for `context.traits.address` aligns with the Chord tracking plan address conventions:
| Field | Type | Description |
| ---------- | ------ | ----------------------------- |
| `address1` | string | Street address line 1 |
| `address2` | string | Street address line 2 |
| `city` | string | City |
| `state` | string | State or province |
| `country` | string | Country |
| `zipcode` | string | Postal / ZIP code |
| `name` | string | Recipient name |
| `company` | string | Company name |
| `phone` | string | Address-specific phone number |
:::BlockQuote
**Note:** The event extractor also recognises legacy field names as fallbacks — `street` for `address1`, `street2` for `address2`, and `zip` / `postalCode` for `zipcode`. These are supported for backwards compatibility but `address1`, `address2`, and `zipcode` are the canonical names.
:::
## context.clientIds
Third-party tracking IDs read from browser cookies.
| Field | Type | Description |
| -------------------- | ------ | ---------------------------------------- |
| `ga4.clientId` | string | Google Analytics 4 client ID |
| `ga4.sessionIds` | any | GA4 session IDs |
| `fbc` | string | Facebook click ID (from `_fbc` cookie) |
| `fbp` | string | Facebook browser ID (from `_fbp` cookie) |
| `amplitudeSessionId` | number | Amplitude session ID (Unix ms) |
| `amplitudeDeviceId` | string | Amplitude device ID |
## context.campaign
UTM parameters parsed from the page URL.
| Field | Type | Description |
| --------- | ------ | -------------- |
| `name` | string | `utm_campaign` |
| `source` | string | `utm_source` |
| `medium` | string | `utm_medium` |
| `content` | string | `utm_content` |
| `term` | string | `utm_term` |
## context.geo
Geolocation data resolved from `context.ip`. Only present on browser events — for S2S events the originating IP is the server's IP, which has no meaningful geo value.
| Field | Type | Description |
| -------------------- | ------ | ------------------------------- |
| `country.code` | string | ISO 3166-1 alpha-2 country code |
| `country.name` | string | Country name |
| `region.code` | string | Region / state code |
| `region.name` | string | Region / state name |
| `city.name` | string | City name |
| `location.latitude` | number | Latitude |
| `location.longitude` | number | Longitude |
## context.device
Mobile device information. Populated by mobile SDKs; typically absent for browser events.
| Field | Type | Description |
| ------------------- | ------- | ----------------------------------- |
| `id` | string | Device ID |
| `type` | string | Device type (e.g. `ios`, `android`) |
| `manufacturer` | string | Device manufacturer |
| `model` | string | Device model |
| `name` | string | Device name |
| `advertisingId` | string | Advertising ID (IDFA / GAID) |
| `adTrackingEnabled` | boolean | Whether ad tracking is enabled |
| `token` | string | Push notification token |
## context.os
Operating system information. Populated by mobile SDKs.
| Field | Type | Description |
| --------- | ------ | ------------------------------- |
| `name` | string | OS name (e.g. `iOS`, `Android`) |
| `version` | string | OS version string |
## context.network
Network information. Populated by mobile SDKs.
| Field | Type | Description |
| ----------- | ------- | ------------------------------ |
| `carrier` | string | Mobile carrier name |
| `wifi` | boolean | Whether connected via WiFi |
| `cellular` | boolean | Whether connected via cellular |
| `bluetooth` | boolean | Whether Bluetooth is on |
## context.screen
Screen dimensions. Populated by the browser SDK and mobile SDKs.
| Field | Type | Description |
| --------- | ------ | ---------------------------------- |
| `width` | number | Screen width in pixels |
| `height` | number | Screen height in pixels |
| `density` | number | Pixel density (device pixel ratio) |
## context.app
Application metadata. Populated by mobile SDKs.
| Field | Type | Description |
| ----------- | ------ | ------------------------- |
| `name` | string | App name |
| `version` | string | App version |
| `build` | string | Build number |
| `namespace` | string | App namespace / bundle ID |
## Other Fields
| Field | Type | Description |
| ----------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `ip` | string | Originating IP address. Set automatically for browser events and used to populate `context.geo`. Not meaningful for S2S events (server IP, not user IP). |
| `userAgent` | string | Browser user agent string. Browser events only — not set on S2S events unless provided explicitly. |
| `locale` | string | Browser locale (e.g. `en-US`). Browser events only — not set on S2S events unless provided explicitly. |
| `library.name` | string | Chord SDK name |
| `library.version` | string | Chord SDK version |
***
**Updated 22 Apr 2026**
[title] Order Canceled
[path] Chord Event Tracking/Server Events/Track/
This event is triggered when a customer cancels an order.
# Properties
| **Name** | **Type** | **Description** | **Required** |
| ------------------ | ---------- | ---------------------------------------------------------------------------------------- | ------------ |
| `affiliation` | `string` | Store or affiliation from which this transaction occurred (for example, "Google Store"). | No |
| `channel` | `string` | The sales channel | No |
| `checkout_id` | `string` | ID of the checkout session for the purchase | No |
| `checkout_type` | `string` | Checkout provider (e.g. `Stripe`) | No |
| `currency` | `string` | ISO currency code of the transaction (e.g. `USD`) | Yes |
| `discount` | `number` | The total discount applied to the order | No |
| `email` | `string` | Email address associated with the order | No |
| `first_name` | `string` | Customer's first name | No |
| `last_name` | `string` | Customer's last name | No |
| `order_date` | `date` | Date and time the order was placed | Yes |
| `order_id` | `string` | Order/transaction ID | Yes |
| `phone` | `string` | Customer's phone number | No |
| `products` | `object[]` | Products in the order | Yes |
| `revenue` | `number` | Revenue ($) associated with the transaction (excluding shipping and tax) | Yes |
| `shipping` | `number` | The total amount for shipping | No |
| `shipping_city` | `string` | City of the shipping address | No |
| `shipping_country` | `string` | ISO country code for the shipping address | No |
| `shipping_state` | `string` | ISO state code for the shipping address | No |
| `shipping_zipcode` | `string` | Zip or postal code for the shipping address | No |
| `subscription_id` | `string` | ID of the subscription created from this purchase, if applicable | No |
| `subtotal` | `number` | Order total including discounts but excluding shipping and tax | No |
| `tax` | `number` | The total tax captured on the order | No |
| `total` | `number` | The order grand total, summing the subtotal, discount, shipping, and tax | Yes |
## Products array
| **Name** | **Type** | **Description** | **Required** |
| -------------- | -------- | ---------------------------------------------------------------------------------------- | ------------ |
| `affiliation` | `string` | Store or affiliation from which this transaction occurred (for example, "Google Store"). | No |
| `brand` | `string` | Brand associated with the product | No |
| `line_item_id` | `string` | ID of the line item in the database | No |
| `name` | `string` | Name of the product | Yes |
| `position` | `number` | Position in the product list | No |
| `price` | `number` | Price of the product | Yes |
| `product_id` | `string` | ID of the product in the database | Yes |
| `quantity` | `number` | The quantity of products purchased in this line item | Yes |
| `revenue` | `number` | Revenue ($) associated with this line item (excluding shipping and tax) | Yes |
| `sku` | `string` | SKU of the variant | Yes |
| `variant_name` | `string` | Name of the variant | No |
| `variant_id` | `string` | ID of the variant in the database | No |
# Sample Payload
```json
{
"type": "track",
"event": "Order Canceled",
"properties": {
"affiliation": "Afilliation",
"checkout_id": "40854979018855",
"checkout_type": "Shopify | OMS | Other",
"currency": "USD",
"discount": 5,
"email": "user@example.com",
"first_name": "John",
"last_name": "Doe",
"order_date": "2025-09-12T11:45:45-07:00",
"order_id": "6736819880039",
"order_number": "1895671",
"phone": "+15555555555",
"revenue": 219,
"shipping": 9.9,
"shipping_city": "Fall River",
"shipping_country": "US",
"shipping_state": "MA",
"shipping_zipcode": "02720",
"subtotal": 219,
"tax": 13.69,
"total": 237.59,
"products": [
{
"affiliation": "Affiliation",
"brand": "Brand",
"line_item_id": "16207084552295",
"name": "Product Name",
"position": 1,
"price": 219,
"product_id": "7036464939671",
"quantity": 1,
"revenue": 219,
"sku": "SKU123",
"variant": "Variant Name",
"variant_id": "40952658057847"
}
],
"meta": {
"i18n": {
"currency": "USD",
"locale": "en-US"
},
"platform": {
"name": "Shopify | OMS | Other",
"type": "web"
},
"store": {
"domain": "domain"
},
"version": {
"major": 3,
"minor": 0,
"patch": 0
}
}
},
"userId": "8046328840295",
"anonymousId": "7a76b270-c318-4477-b1e1-33eac94dbd1e"
}
```
# Example
```bash
curl https://production.cdp.ingest.chord.co/api/track \
--header "Content-Type: application/json" \
--header "X-Write-Key: $CDP_WRITE_KEY" \
--data-raw '{
{
"type": "track",
"event": "Order Canceled",
"properties": {}
"meta": {},
"userId": "123456",
"anonymousId": "7a76b270-c318-4477-b1e1-33eac94dbd1e"
}
```
[title] Untitled
[path] Chord Event Tracking/Getting started/
[title] Untitled
[path] Chord Event Tracking/Getting started/
[title] Shopify subscription event tracking
[path] Chord Event Tracking/Getting started/Shopify/
## Overview
If your Shopify store sells subscriptions, Chord can track subscription lifecycle events such as creation, cancellation, and payment failures. These events are delivered to Chord via Shopify webhooks, similar to [Shopify server event tracking](docId\:xbL7zBqE14BT7gbTMl0un).
However, Shopify restricts subscription contract webhook events to the app that originally created the contract (such as Shopify Subscriptions or Recharge). Because of this limitation, the Chord webhook source cannot listen to subscription-specific webhook events directly. Instead, **Shopify Flow** is used as a workaround to forward these events to Chord.
## Prerequisites
Before configuring subscription event tracking, confirm the following:
- Chord has access to your Shopify store
- You have access to your Chord workspace
- [Shopify server event tracking](docId\:xbL7zBqE14BT7gbTMl0un) is already configured (Admin API key and webhook source are in place)
- [Shopify Flow](https://apps.shopify.com/flow) is installed on your Shopify store
If you have questions about any of these prerequisites, contact [help@chord.co](mailto\:help@chord.co).
## Supported Subscription Events
| Shopify Webhook Topic | Chord Event |
| --------------------------------------- | --------------------------- |
| `subscription_contracts/create` | Subscription Created |
| `subscription_contracts/cancel` | Subscription Canceled |
| `subscription_contracts/pause` | Subscription Paused |
| `subscription_contracts/expire` | Subscription Expired |
| `subscription_billing_attempts/failure` | Subscription Payment Failed |
## Installation
### Step 1: Install Shopify Flow
[Shopify Flow](https://apps.shopify.com/flow) is a free automation app from Shopify. It may already be installed on your store — your Chord implementation team may have set it up during provisioning. If you are unsure, contact [help@chord.co](mailto\:help@chord.co).
### Step 2: Import Flows
Your Chord implementation team will provide three Flow files:
- `[CHORD] - Subscription Contract Created.flow`
- `[CHORD] - Subscription Updated (Cancelled / Expired / Paused).flow`
- `[CHORD] - Subscription Payment Failed.flow`
To import each flow:
1. In your Shopify Admin, go to **Apps > Shopify Flow**.
2. Click **Import Flow**.
3. Upload the `.flow` file and confirm the import.
4. Repeat for each of the three flow files.
### Step 3: Verify the Flows
1. In Shopify Flow, review each imported workflow to confirm it is active.
2. Trigger a test subscription event in your store (e.g., create a test subscription).
3. In your Chord workspace, navigate to the Shopify webhook source and open the **Debugger** tab.
4. Confirm that the expected subscription events appear.
## Support
If you encounter issues configuring subscription flows or do not see subscription events in your Chord workspace, contact [help@chord.co](mailto\:help@chord.co) with details about the problem.
[title] Shopify server event tracking
[path] Chord Event Tracking/Getting started/Shopify/
## Overview
When installed on your Shopify store, Chord sends tracking events from two sources:
1. **Your storefront**, using either the Chord Shopify web pixel or `@chordcommerce/analytics` (see [Shopify installation](docId:7gGdgpVq4j3qwBPrHY1Fr))
2. **Chord's server events service**, which sends tracking events from a Shopify webhook source in your Chord workspace in response to webhook triggers from Shopify
When Chord provisions your workspace, it includes a Shopify webhook source. This source listens for webhook events from Shopify and transforms them into Chord events.
## Requirements
Locate the webhook source in your Chord workspace, named **"Shopify Webhooks."** Chord typically creates this source as part of your workspace provisioning. You will need:
- The **settings page** of this source during the "Create an Admin API Key" step
- The **webhook URL** of this source during the "Create Webhook Subscriptions" step
If you cannot find the source or are unsure which one it is, contact [help@chord.co](mailto\:help@chord.co).
## Step 1: Create an Admin API Key
Chord's webhook source requires an Admin API key with the `read_orders` scope to retrieve order details from Shopify. We recommend creating a dedicated custom app in your Shopify account for Chord, which makes it easy to manage access.
### Create the API key in Shopify
1. In your Shopify Admin, go to **Settings > Apps and sales channels > Develop apps > Create an app**.
2. Name the app (e.g., "Chord Webhooks").
3. Click **Configure Admin API Scopes**.
4. Select `read_orders` only and click **Save**.
5. On the **Overview** tab, click **Install app**.
6. Copy the **Admin API access token**.
### Add the token to your Chord workspace
1. In your Chord workspace, navigate to your Shopify webhook source.
2. Open **Settings > Connection**.
3. Enter the Admin API access token in the **Access Token** field.
4. Click **Save Changes**.
## Step 2: Create Webhook Subscriptions
1. In your Chord workspace, navigate to your Shopify webhook source.
2. Find the webhook URL under the **Configure your webhook** heading. Copy this URL.
3. In your Shopify Admin, go to **Settings > Notifications > Webhooks** (or use the Shopify Admin API to create subscriptions programmatically — you can use the same Admin API access token you created in Step 1).
4. Create a webhook subscription for each of the supported topics listed below. Each subscription should use the same webhook URL you copied from your Chord workspace.
### Supported Webhook Topics
| Webhook Topic | Chord Event |
| ------------------ | ---------------- |
| `checkouts/create` | Checkout Created |
| `orders/create` | Order Completed |
| `refunds/create` | Order Refunded |
| `customers/delete` | Customer Deleted |
| `customers/merge` | Customer Merged |
| `locations/delete` | Location Deleted |
| `orders/delete` | Order Deleted |
| `products/delete` | Product Deleted |
## Verifying the Installation
Shopify's built-in webhook testing does not send payloads that match real webhook payloads. To verify that server events are flowing correctly:
1. Complete a test transaction in your Shopify store.
2. In your Chord workspace, navigate to the Shopify webhook source and open the **Debugger** tab.
3. Confirm that the expected events (Checkout Created, Order Completed, etc.) appear.
## Subscription Events
If your store sells subscriptions, Chord can also track subscription lifecycle events (creation, cancellation, payment failures, etc.). Due to Shopify platform restrictions, subscription events require a different setup using Shopify Flow.
See [Shopify subscription event tracking](docId:3IRbD314fqAJoOWdjV6Ax) for details.
## Associating Server Events with Storefront Sessions
To link server events with front-end storefront events from the same customer session, the storefront must save certain browser identifiers as attributes on the cart or order. These identifiers are then retrieved by the webhook source and included in Chord events.
For details, see [Unifying Data Across Sources]().
[title] Subscription Expired
[path] Chord Event Tracking/Server Events/Track/
This event is triggered when a prepaid subscription has expired.
# Properties
| **Name** | **Type** | **Description** | **Required** |
| --------------------- | ---------- | -------------------------------------------------------------------------------------------------------------------------------------- | ------------ |
| `subscription_id` | `string` | Unique ID of the subscription | Yes |
| `interval_length` | `number` | Combined with `interval_units`, specifies the cadence of the subscription. E.g. for a **3 week** cadence, this value will be `3`. | No |
| `interval_units` | `string` | Combined with `interval_length`, specifies the cadence of the subscription. E.g. for a **3 week** cadence, this value will be `weeks`. | No |
| `actionable_date` | `string` | ISO date when the next installment order will be generated. | No |
| `state` | `string` | State of the subscription (e.g. `active`, `paused`, `canceled`). | No |
| `payment_method_name` | `string` | Name of the payment method for installment orders. | No |
| `email` | `string` | Email address associated with the subscription | No |
| `canceled_at` | `string` | ISO date when the subscription was canceled, if applicable | No |
| `canceled_by` | `string` | Email address of the user who canceled the subscription, if applicable | No |
| `activated_at` | `string` | ISO date when the subscription was activated | Yes |
| `address` | `object` | Shipping address of the subscription. | Yes |
| `products` | `object[]` | Products in the subscription | Yes |
## Address
| **Name** | **Type** | **Description** | **Required** |
| ------------------- | -------- | -------------------------------------------------------- | ------------ |
| `address1` | `string` | The street address of the customer | No |
| `address2` | `string` | Additional street address of the customer (if necessary) | No |
| `alternative_phone` | `string` | Customer's alternative phone number | No |
| `phone` | `string` | Customer's phone number | No |
| `city` | `string` | City of the shipping address | No |
| `company` | `string` | Name of the company, if applicable | No |
| `country` | `string` | ISO country code for the shipping address | No |
| `name` | | Customer name | No |
| `state` | `string` | ISO state code for the shipping address | No |
| `zipcode` | `string` | Zip or postal code for the shipping address | No |
## Products array
| **Name** | **Type** | **Description** | **Required** |
| -------------- | -------- | ---------------------------------------------------------------------------------------- | ------------ |
| `affiliation` | `string` | Store or affiliation from which this transaction occurred (for example, "Google Store"). | No |
| `brand` | `string` | Brand associated with the product | No |
| `line_item_id` | `string` | ID of the line item in the database | No |
| `name` | `string` | Name of the product | Yes |
| `position` | `number` | Position in the product list | No |
| `price` | `number` | Price of the product | Yes |
| `product_id` | `string` | ID of the product in the database | Yes |
| `quantity` | `number` | The quantity of products purchased in this line item | Yes |
| `revenue` | `number` | Revenue ($) associated with this line item (excluding shipping and tax) | Yes |
| `sku` | `string` | SKU of the variant | Yes |
| `variant_name` | `string` | Name of the variant | No |
| `variant_id` | `string` | ID of the variant in the database | No |
# Sample Payload
```json
{
"type": "track",
"event": "Subscription Expired",
"properties": {
"subscription_id": "1",
"interval_length": 3,
"interval_units": "weeks",
"actionable_date": "2026-01-01T00:00:00.000Z",
"state": "active",
"payment_method_name": "Stripe",
"email": "user@example.com",
"canceled_at": null,
"canceled_by": null,
"activated_at": "2026-01-01T00:00:00.000Z",
"address": {
"address1": "123 Fake St",
"address2": null,
"alternative_phone": null,
"phone": "123456789",
"city": "Oak Lawn",
"state": "IL",
"country": "US",
"name": "John Doe",
"zipcode": "60532"
},
"products": [
{
"affiliation": "Affiliation",
"brand": "Brand",
"line_item_id": "16207084552295",
"name": "Product Name",
"position": 1,
"price": 219,
"product_id": "7036464939671",
"quantity": 1,
"revenue": 219,
"sku": "SKU123",
"variant": "Variant Name",
"variant_id": "40952658057847"
}
]
}
}
```
# Example
```bash
curl https://production.cdp.ingest.chord.co/api/track \
--header "Content-Type: application/json" \
--header "X-Write-Key: $CDP_WRITE_KEY" \
--data-raw '
{
"type": "track",
"event": "Subscription Expired",
"properties": {
"subscription_id": "1",
"interval_length": 3,
"interval_units": "weeks",
"actionable_date": "2026-01-01T00:00:00.000Z",
"state": "active",
"payment_method_name": "Stripe",
"email": "user@example.com",
"canceled_at": null,
"canceled_by": null,
"activated_at": "2026-01-01T00:00:00.000Z",
"address": {
"address1": "123 Fake St",
"address2": null,
"alternative_phone": null,
"phone": "123456789",
"city": "Oak Lawn",
"state": "IL",
"country": "US",
"name": "John Doe",
"zipcode": "60532"
},
"products": [
{
"affiliation": "Affiliation",
"brand": "Brand",
"line_item_id": "16207084552295",
"name": "Product Name",
"position": 1,
"price": 219,
"product_id": "7036464939671",
"quantity": 1,
"revenue": 219,
"sku": "SKU123",
"variant": "Variant Name",
"variant_id": "40952658057847"
}
]
}
}
'
```
[title] Snap Pixel
[path] Chord CDP/CDP Destinations/CDP Destination Catalog/
**Snap Pixel** is Snapchat's conversion tracking pixel for measuring ad performance and building retargeting audiences. This destination loads the Snapchat Pixel JavaScript SDK in the browser and forwards ecommerce and engagement events to Snapchat Ads. There is no server-side component.
# Getting Started
This is a device-mode destination. The Snapchat Pixel SDK is loaded automatically — no manual script installation is required. You will need:
- **Pixel ID** — your Snapchat Pixel ID, found in your Snapchat Ads Manager under **Assets > Pixels**.
Optionally:
- **Product Content ID Field** — which product field to use as the content ID: `sku`, `product_id`, or `variant_id`. Defaults to `sku`. If the configured field is absent on a product, it falls back through `sku → variant_id → product_id → id`. **If you are also using the Snapchat Conversions API destination, this must be set to the same value in both destinations** so that item IDs match between client-side and server-side events.
# Connecting to the Snap Pixel CDP Destination
:::BlockQuote
**Warning:** Before connecting destinations in the Chord CDP, please verify with all Destination owners that all **non-Chord CDP** configured destinations are **disabled**. Running external destinations alongside configured Chord CDP destinations **can result in duplicate events downstream.**
:::
1. Log into the Chord data platform.
2. Navigate to the CDP.
3. Click the **"Add"** button next to Destinations.
4. Select **Snap Pixel** from the destination catalog.
5. Enter the destination name and your **Pixel ID**.
6. Optionally configure the **Product Content ID Field**.
7. Click **"Create"** to connect.
# Events
All Snap Pixel events include a `client_dedup_id` parameter set to the Chord `messageId` for deduplication.
# Event Mapping
| Chord Event | Snap Event |
| --------------------------- | ----------------- |
| `page` | `PAGE_VIEW` |
| `Order Completed` | `PURCHASE` |
| `Product Added` | `ADD_CART` |
| `Product Viewed` | `VIEW_CONTENT` |
| `Checkout Started` | `START_CHECKOUT` |
| `Subscription Created` | `SUBSCRIBE` |
| `Products Searched` | `SEARCH` |
| `Payment Info Entered` | `ADD_BILLING` |
| `Product Added to Wishlist` | `ADD_TO_WISHLIST` |
| `Signed Up` | `SIGN_UP` |
# Page Events
**Snap SDK call:** `snaptr("track", "PAGE_VIEW", { client_dedup_id })`
No additional attributes are sent with page events.
# Identify Events
Re-initializes the Snap Pixel with user data for enhanced matching. The event is skipped if neither email nor phone is available.
**Snap SDK call:** `snaptr("init", pixelId, userData)`
| Snap Attribute | Chord Source (Priority Order) | Notes |
| ------------------- | ----------------------------- | ---------------------- |
| `user_email` | `context.traits.email` | Omitted if not present |
| `user_phone_number` | `context.traits.phone` | Omitted if not present |
# Order Completed
Fires a purchase conversion event with order and product data.
**Snap SDK call:** `snaptr("track", "PURCHASE", orderData)`
| Snap Attribute | Chord Source (Priority Order) | Notes |
| ---------------- | ---------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| `item_ids` | Each product's configured field → `sku` → `variant_id` → `product_id` → `id` | Array of products with a resolvable ID; omitted if empty |
| `item_category` | `properties.products[0].category` | First product's category |
| `currency` | `properties.currency` | Defaults to `"USD"` |
| `price` | `properties.value` | Total value after quantity (`price × qty`); formatted to 2 decimal places |
| `transaction_id` | `properties.order_id` | Used by Snapchat to deduplicate against CAPI Purchase events |
| `number_items` | Count of products with a resolvable ID | |
# Product Added
Fires an add-to-cart event using the first product from `properties.products[]`.
**Snap SDK call:** `snaptr("track", "ADD_CART", productData)`
| Snap Attribute | Chord Source (Priority Order) | Notes |
| --------------- | ----------------------------------------------------------------------------- | --------------------------------------------------------- |
| `item_ids` | First product's configured field → `sku` → `variant_id` → `product_id` → `id` | Single-element array; event skipped if no ID resolves |
| `item_category` | `properties.products[0].category` | |
| `currency` | `properties.currency` | Defaults to `"USD"` |
| `price` | `properties.value` | Total value after quantity; formatted to 2 decimal places |
# Product Viewed
Same attributes as **Product Added** above.
**Snap SDK call:** `snaptr("track", "VIEW_CONTENT", productData)`
# Checkout Started
Same attributes as **Order Completed** above.
**Snap SDK call:** `snaptr("track", "START_CHECKOUT", orderData)`
# Subscription Created
Same attributes as **Order Completed** above.
**Snap SDK call:** `snaptr("track", "SUBSCRIBE", orderData)`
# Products Searched
**Snap SDK call:** `snaptr("track", "SEARCH", searchData)`
| Snap Attribute | Chord Source (Priority Order) | Notes |
| --------------- | ----------------------------------------------- | ----- |
| `search_string` | `properties.query` > `properties.search_string` | |
# Payment Info Entered
No additional attributes beyond the dedup ID.
**Snap SDK call:** `snaptr("track", "ADD_BILLING", { client_dedup_id })`
# Product Added to Wishlist
Same attributes as **Product Added** above.
**Snap SDK call:** `snaptr("track", "ADD_TO_WISHLIST", productData)`
# Signed Up
No additional attributes beyond the dedup ID.
**Snap SDK call:** `snaptr("track", "SIGN_UP", { client_dedup_id })`
# Initialization
The plugin loads `https://sc-static.net/scevent.min.js` and calls `snaptr("init", pixelId)`, optionally with `user_email` and `user_phone_number` if available on the triggering event. Before the script loads, a queue buffers any calls to `snaptr`.
The plugin manages SDK loading state (`fresh` → `loading` → `loaded`/`failed`) to prevent duplicate script loads. If the script fails to load, subsequent events are silently dropped.
# CSP Requirements
If your site uses a Content Security Policy, allow the following domains:
| Directive | Domain |
| ------------- | ----------------------- |
| `script-src` | `https://sc-static.net` |
| `connect-src` | `https://sc-static.net` |
***
**Updated 23 Apr 2026**
[title] Subscription Payment Failed
[path] Chord Event Tracking/Server Events/Track/
This event is triggered when the payment for a subscription installment order fails for any reason (e.g. insufficient funds, declined card).
# Properties
| **Name** | **Type** | **Description** | **Required** |
| --------------------- | ---------- | -------------------------------------------------------------------------------------------------------------------------------------- | ------------ |
| `subscription_id` | `string` | Unique ID of the subscription | Yes |
| `interval_length` | `number` | Combined with `interval_units`, specifies the cadence of the subscription. E.g. for a **3 week** cadence, this value will be `3`. | No |
| `interval_units` | `string` | Combined with `interval_length`, specifies the cadence of the subscription. E.g. for a **3 week** cadence, this value will be `weeks`. | No |
| `actionable_date` | `string` | ISO date when the next installment order will be generated. | No |
| `state` | `string` | State of the subscription (e.g. `active`, `paused`, `canceled`). | No |
| `payment_method_name` | `string` | Name of the payment method for installment orders. | No |
| `email` | `string` | Email address associated with the subscription | No |
| `canceled_at` | `string` | ISO date when the subscription was canceled, if applicable | No |
| `canceled_by` | `string` | Email address of the user who canceled the subscription, if applicable | No |
| `activated_at` | `string` | ISO date when the subscription was activated | Yes |
| `address` | `object` | Shipping address of the subscription. | Yes |
| `products` | `object[]` | Products in the subscription | Yes |
## Address
| **Name** | **Type** | **Description** | **Required** |
| ------------------- | -------- | -------------------------------------------------------- | ------------ |
| `address1` | `string` | The street address of the customer | No |
| `address2` | `string` | Additional street address of the customer (if necessary) | No |
| `alternative_phone` | `string` | Customer's alternative phone number | No |
| `phone` | `string` | Customer's phone number | No |
| `city` | `string` | City of the shipping address | No |
| `company` | `string` | Name of the company, if applicable | No |
| `country` | `string` | ISO country code for the shipping address | No |
| `name` | | Customer name | No |
| `state` | `string` | ISO state code for the shipping address | No |
| `zipcode` | `string` | Zip or postal code for the shipping address | No |
## Products array
| **Name** | **Type** | **Description** | **Required** |
| -------------- | -------- | ---------------------------------------------------------------------------------------- | ------------ |
| `affiliation` | `string` | Store or affiliation from which this transaction occurred (for example, "Google Store"). | No |
| `brand` | `string` | Brand associated with the product | No |
| `line_item_id` | `string` | ID of the line item in the database | No |
| `name` | `string` | Name of the product | Yes |
| `position` | `number` | Position in the product list | No |
| `price` | `number` | Price of the product | Yes |
| `product_id` | `string` | ID of the product in the database | Yes |
| `quantity` | `number` | The quantity of products purchased in this line item | Yes |
| `revenue` | `number` | Revenue ($) associated with this line item (excluding shipping and tax) | Yes |
| `sku` | `string` | SKU of the variant | Yes |
| `variant_name` | `string` | Name of the variant | No |
| `variant_id` | `string` | ID of the variant in the database | No |
# Sample Payload
```json
{
"type": "track",
"event": "Subscription Payment Failed",
"properties": {
"subscription_id": "1",
"interval_length": 3,
"interval_units": "weeks",
"actionable_date": "2026-01-01T00:00:00.000Z",
"state": "active",
"payment_method_name": "Stripe",
"email": "user@example.com",
"canceled_at": null,
"canceled_by": null,
"activated_at": "2026-01-01T00:00:00.000Z",
"address": {
"address1": "123 Fake St",
"address2": null,
"alternative_phone": null,
"phone": "123456789",
"city": "Oak Lawn",
"state": "IL",
"country": "US",
"name": "John Doe",
"zipcode": "60532"
},
"products": [
{
"affiliation": "Affiliation",
"brand": "Brand",
"line_item_id": "16207084552295",
"name": "Product Name",
"position": 1,
"price": 219,
"product_id": "7036464939671",
"quantity": 1,
"revenue": 219,
"sku": "SKU123",
"variant": "Variant Name",
"variant_id": "40952658057847"
}
]
}
}
```
# Example
```bash
curl https://production.cdp.ingest.chord.co/api/track \
--header "Content-Type: application/json" \
--header "X-Write-Key: $CDP_WRITE_KEY" \
--data-raw '
{
"type": "track",
"event": "Subscription Payment Failed",
"properties": {
"subscription_id": "1",
"interval_length": 3,
"interval_units": "weeks",
"actionable_date": "2026-01-01T00:00:00.000Z",
"state": "active",
"payment_method_name": "Stripe",
"email": "user@example.com",
"canceled_at": null,
"canceled_by": null,
"activated_at": "2026-01-01T00:00:00.000Z",
"address": {
"address1": "123 Fake St",
"address2": null,
"alternative_phone": null,
"phone": "123456789",
"city": "Oak Lawn",
"state": "IL",
"country": "US",
"name": "John Doe",
"zipcode": "60532"
},
"products": [
{
"affiliation": "Affiliation",
"brand": "Brand",
"line_item_id": "16207084552295",
"name": "Product Name",
"position": 1,
"price": 219,
"product_id": "7036464939671",
"quantity": 1,
"revenue": 219,
"sku": "SKU123",
"variant": "Variant Name",
"variant_id": "40952658057847"
}
]
}
}
'
```
[title] CDP Consent Categories (Consent Management Category Mapping)
[path] Chord CDP/
:::hint{type="info"}
Note: This feature is available to Chord users who are assigned a **Team Admin** or **Developer **role.
****
**Member and Data Analyst **roles can view existing consent categories and mappings but cannot edit or delete consent categories. **Order Admins** will **not** have access to this feature.
For additional support, please reach out to [help@chord.co](mailto\:help@chord.co).
:::
# Introduction
Consent management category mapping is the process of aligning the types of customer data you collect—like behavioral, transactional, or marketing preferences—with specific consent categories. This ensures that your brand honors user privacy choices across every touchpoint, making it easier to stay compliant with data privacy guidelines while still managing customer data responsibly.
Chord CDP makes it super easy to create, enable, and manage consent management categories with just a few clicks. Follow the steps below to set up your consent management categories and assign category mappings.
# Create a Consent Category
To create a consent category, follow the steps below:
1. Log into the Chord data platform.
2. Click into the **Chord CDP**.
3. Navigate to the **Consent Categories** tab.
4. Click the **"+ New Category"** button.
5. Update the **Name** of the consent category.
6. Click the ✔️ icon to save the consent category name.
7. Provide the **External ID** of the consent category. **Note: **This field will be matched against the browser consent managment category id. This is usually defined in the browser's consent management platform.
8. Click the **"Save"** button to save your new consent category.
# Map a Consent Category
Once you have created consent categories, you can now map them to the relevant destinations.
1. Make sure you are in the** Chord CDP**. Click the **"Overview"** tab.
2. Make sure you have destinations connected.
3. Choose a destination that you'd like to map an existing consent category and click **"Edit"**.
4. Within the destination, scroll down to the Consent Requirements section. Toggle your desired **consent categories** on and off.
5. Click **"Save Changes"** to save your updates.
# Edit Consent Categories
1. Make sure you are in the** Chord CDP**. Click the **"Consent Categories"** tab.
2. For the consent category you'd like to update, click the ✏️ icon.
3. Make the necessary updates to the consent category and click the **"Save"** button.
# Remove Consent Categories
1. Make sure you are in the** Chord CDP**. Click the **"Consent Categories"** tab.
2. For the consent category you'd like to update, click the 🗑️ icon.
3. You'll see a pop up confirming the deletion. Click **"Delete"**.
4. The consent category you chose has been deleted!
[title] Event deduplication
[path] Chord CDP/
## Delivery Guarantee
The Chord CDP provides **at-least-once delivery** for every event. This means the CDP attempts to deliver each event at least once and may retry when failures occur, so in rare cases the same event may be delivered more than once.
Duplicates are typically caused by transient events in the underlying message pipeline:
- A processing instance restarting (deployment, autoscaling, crash) before its progress is acknowledged
- A network blip or pause that causes an in-flight message to be redelivered
- An upstream producer retry after an unconfirmed delivery
- Temporary failures in downstream services that trigger replays
This is the same delivery model used by the major customer data platforms (Segment, Rudderstack, mParticle), and is the standard guarantee for streaming event pipelines.
## Current Deduplication Policy
The Chord CDP **does not perform message-level deduplication within the pipeline itself**. Instead, deduplication is the responsibility of the downstream destination.
For every event the CDP processes, the source-provided `messageId` is preserved end-to-end and made available to every destination. Destinations should use the `messageId` (or a deterministic value derived from it — some destinations require a transformed identifier, e.g., a `messageId` with a suffix) to detect and reject duplicates on their side.
### How destinations should handle duplicates
| Destination Type | Recommended Approach |
| ------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Data warehouses** (Snowflake, BigQuery, Postgres, Redshift, ClickHouse, etc.) | Configure deduplication at the destination using `messageId` as the primary key. The Chord CDP supports per-connection deduplication options (`deduplicate` + `primaryKey`) that perform `MERGE`/`UPSERT` on each load. ClickHouse destinations collapse duplicates on background merges via the `ReplacingMergeTree` table engine. |
| **HTTP APIs** (Braze, Klaviyo, Insider, Stripe, etc.) | Pass `event.messageId` (or a destination-specific derivation of it) as an idempotency key in the API request — typically via the `Idempotency-Key` HTTP header. Most modern APIs will reject or ignore requests with a previously-seen idempotency key. |
| **Reverse ETL / loopback destinations** | Filter by `messageId` in the destination system, or rely on the destination's natural primary-key constraints. |
## Why Deduplicate at the Destination?
Destination-side deduplication is the conventional pattern for streaming data systems, for several reasons:
1. **Destinations have authoritative state.** A warehouse already knows whether a row with a given primary key exists. An HTTP API already knows whether it has processed a given idempotency key. Asking these systems to detect duplicates is more reliable than maintaining a parallel record elsewhere.
2. **Destinations are diverse.** Different destinations have different definitions of "duplicate" — some merge by primary key, some upsert by composite key, some collapse on background processes. A pipeline-level dedup can't capture this nuance.
3. **It avoids a single point of failure.** A pipeline-level dedup store would be a critical-path dependency; if it became slow or unavailable, the entire pipeline would degrade. Pushing dedup to destinations keeps the pipeline fast and stateless.
4. **It aligns with how streaming pipelines work.** At-least-once is the default delivery semantic of the underlying streaming infrastructure. Building exactly-once on top requires complex coordination that introduces its own failure modes.
## Implications for Custom Functions (UDFs)
UDFs run inside the CDP pipeline before events are dispatched to destinations. Because the CDP is at-least-once, **a UDF may execute more than once for the same source event** in rare redelivery scenarios.
For UDFs that are pure transformations (enrichment, filtering, splitting), this is harmless — the destination will still deduplicate the result by `messageId`.
However, UDFs that perform **external write operations** (calling a third-party API that modifies state, incrementing a remote counter, sending an email, writing to a database) should be designed to be idempotent. The standard approach is to pass `event.messageId` as an idempotency key to the external system:
```javascript
export default async function (event, { fetch }) {
await fetch("https://api.example.com/orders", {
method: "POST",
headers: {
"Content-Type": "application/json",
"Idempotency-Key": event.messageId, // ← prevents duplicate writes on redelivery
},
body: JSON.stringify({ /* ... */ }),
});
return event;
}
```
Without an idempotency key, a redelivered event could cause the UDF's external write to occur twice.
## Working with `messageId`
Every event flowing through the CDP carries a `messageId` field. If the source provides one, it is preserved end-to-end. If not, the CDP generates a unique identifier at ingest time. The `messageId` is:
- **Stable** — the same value is forwarded to every destination
- **Unique** — within a reasonable window (system-generated unique identifiers, or source-provided identifiers that the source guarantees unique)
- **Available everywhere** — exposed on the `event` object inside UDFs as `event.messageId`, included in the payloads sent to destinations, and visible in Live Events
Use it as the canonical key for any deduplication, tracing, or correlation downstream.
## Related Topics
- For details on configuring per-connection deduplication options for a warehouse destination, see your destination configuration page in the Chord Console.
- For guidance on writing idempotent UDFs, see the CDP Functions documentation.
## Support
For questions about deduplication, delivery guarantees, or how to configure your destination, please contact [help@chord.co](mailto\:help@chord.co).
[title] Unifying Data Across Sources
[path] Chord Event Tracking/Guides/
Chord’s standard data implementation includes events being sent to the CDP from, at minimum, a website front-end and a server source. To ensure these events are associated to the same user record in the CDP, the website front-end needs to save a few browser identifiers as attributes on the cart or order, so they can be retrieved later by the server source and included in CDP events.
## Shopify
For Shopify sites, these identifiers should be added as cart attributes.
If using the Shopify Storefront API in a headless architecture, this can be done using the [`cartAttributesUpdate`](https://shopify.dev/docs/api/storefront/2023-10/mutations/cartAttributesUpdate) mutation.
If you are using the Shopify web pixel in a store that uses a Liquid theme, you'll want to add the following script to your Liquid theme:
```html
```
## Others
At minimum, a cart attribute named `_cdpAnonymousId` must be added with the value being the anonymous ID assigned to the user in the browser. When using Segment, this ID can be found by calling `window.analytics.user().anonymousId()` on any page where Segment’s Javascript is present. It won't be available until after Segment has been initialized, so you may want to wait for the `analytics.ready` [callback](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/#ready).
If using Google destinations, add an attribute named `_googleClientId` with the value `getCookie('_ga').substring(6)`. *Note: *`getCookie`* is not a native Javascript function and needs to be implemented. See *[an example implementation](https://developer.mozilla.org/en-US/docs/Web/API/Document/cookie)*.*
Add these attributes to the cart before the customer navigates to checkout. Ideally, if adding these attributes requires an API request, add these attributes at a time that doesn’t block user interaction with your site, like when the cart page loads or after a product is added to the cart.
[title] Migrating from Segment to Chord CDP
[path] Chord Event Tracking/Guides/
:::hint{type="info"}
The only difference between using Chord's SDKs to send events to Chord CDP vs Segment is *where the events are sent*. **The events will remain exactly the same.** As a result, only small configuration changes are needed. Easy!
:::
## Client-side / front-end events
### Chord Analytics library
If you're using the `@chordcommerce/analytics` library on a headless site, your current implementation might look something like this:
```javascript
import { ChordAnalytics } from '@chordcommerce/analytics'
import { AnalyticsBrowser } from '@segment/analytics-next'
const cdp = AnalyticsBrowser.load({
writeKey: process.env.SEGMENT_WRITE_KEY,
})
const chord = new ChordAnalytics({
cdp,
formatters: { ... },
metadata: { ... },
})
// Example events
chord.page()
chord.trackProductAdded({ ... })
```
In that case, migrating to Chord CDP will involve:
1. updating `@chordcommerce/analytics` to version `1.9.1` or greater
2. removing the `@segment/analytics-next` dependency
3. removing initialization of the `cdp` variable and configuration option
4. using `cdpDomain` and `cdpWriteKey` configuration options - both to be provided by Chord - instead
5. using the `consent` configuration option for built-in consent management support (optional)
The resulting code will look something like this:
```javascript
import { ChordAnalytics } from '@chordcommerce/analytics'
const chord = new ChordAnalytics({
cdpDomain: process.env.CHORD_CDP_DOMAIN,
cdpWriteKey: process.env.CHORD_CDP_WRITE_KEY,
consent: 'shopify', // optional
formatters: { ... },
metadata: { ... },
})
// Example events (unchanged)
chord.page()
chord.trackProductAdded({ ... })
```
**Running both in parallel**
It is possible to send every event to both Chord CDP *and* Segment at the same time. This is useful for running a side-by-side comparison of event data during migration. It also buys more time when migrating destinations.
The resulting code would be a combination of the two examples above; for example:
```javascript
import { ChordAnalytics } from '@chordcommerce/analytics'
import { AnalyticsBrowser } from '@segment/analytics-next'
const cdp = AnalyticsBrowser.load({
writeKey: process.env.SEGMENT_WRITE_KEY,
})
const chord = new ChordAnalytics({
cdp,
cdpDomain: process.env.CHORD_CDP_DOMAIN,
cdpWriteKey: process.env.CHORD_CDP_WRITE_KEY,
formatters: { ... },
metadata: { ... },
})
// Example events (unchanged)
chord.page()
chord.trackProductAdded({ ... })
```
Once the validation and migration are complete, the Segment code can be safely removed to match the second example.
### Shopify web pixel
If you're using Chord's Shopify web pixel - either for a fully Liquid site or just for Checkout Extensibility - we will provide an updated web pixel that supports Chord CDP.
### Chord OMS SDKs
If your storefront is built on Chord OMS using the Gatsby or Next.js starterkits, the Chord team will help you swap the Segment snippet for the Chord CDP snippet.
## Server-side / back-end events
Regardless of OMS, Chord will assist in the migration of server-side/back-end events. It will be an equally simple process, but the actual implementation will vary based on the current architecture.
[title] Track
[path] Chord Event Tracking/Server Events/
Track events correspond to actions your user or system complete during the purchase journey. For example `Order Completed`or `Shipment Shipped`.
All track events must include the following properties in the payload:
| **Property** | **Type** | **Required?** | **Description** |
| ------------- | -------- | ------------- | ---------------------------------------------- |
| `type` | string | Required | `track` |
| `event` | string | Required | The name of the event, e.g. \`Order Completed |
| `userId` | string | Optional | ID # of the identified user (or email address) |
| `anonymousId` | string | Optional | ID # of the unidentified user, if available. |
# Events
## Order
- [Order Canceled](docId\:jT_YWRciuuG2WPM9XDkLw)
- [Order Completed](docId\:IaFTvqdHTQ3FxnLE5PQSw)
- [Order Refunded](docId\:YaUKCcBlzZrvKh3K_CI59)
## Shipment
- [Shipment Delivered](docId\:elrpV-N5cDhSuN1gV2hYZ)
- [Shipment Shipped](docId\:wBwx9EJNDlM5p23UUBZ3i)
## Subscription
- [Subscription Auto-Renewed](docId\:gpYpS0JPX88Y7YnRvKhL4)
- [Subscription Created](docId\:ynO6odyqwmXB4sjuTVFAk)
- [Subscription Expired](docId\:WJypi_5RbWTho_PcvZqhG)
- [Subscription Order Skipped](docId\:waZijYIJRELHrGO33lzBz)
- [Subscription Paused](docId\:kJd6LrttTCi-WTi3o-pmg)
- [Subscription Payment Failed](docId\:Nui186-7ahi2Pi-AmBvSp)
- [Subscription Reminder Sent](docId\:IZnizDZpz3BfO1UJXFTsb)
- [Subscription Resumed](docId:2iM6eWnIHdl1k_o_DlyCy)
## User
- [User Created](docId\:YjBnI8mWgI6aBGtpqvLGO)
[title] Tag
[path] Chord CDP/CDP Destinations/CDP Destination Catalog/
The **Tag** destination lets you run custom JavaScript or HTML snippets in the browser whenever a Chord CDP event fires. Use it to send events to third-party tools that don't have a built-in Chord destination, fire custom pixels, or trigger any browser-side logic tied to your event stream. There is no server-side component.
# Getting Started
This is a device-mode destination. No external credentials are required — you provide the code to execute directly in the destination configuration.
# Connecting to the Tag CDP Destination
1. Log into the Chord data platform.
2. Navigate to the CDP.
3. Click the **"Add"** button next to Destinations.
4. Select **Tag** from the destination catalog.
5. Enter a destination name.
6. Paste your JavaScript or HTML snippet into the **Code** field.
7. Click **"Create"** to connect.
# How It Works
Every time a Chord event fires (e.g. `window.chord.track("Order Completed", {...})`), the Tag destination executes your code once with the full event object available. Your snippet runs synchronously in the browser — no polling, no persistent listeners required.
Two code modes are supported:
## JavaScript Mode
Write plain JavaScript. The event is available as a local `const event` variable — no imports or setup needed.
**Source track call:**
```js
window.chord.track("Order Completed", {
order_id: "R-10042",
revenue: 89.95,
total: 96.94,
currency: "USD",
order_date: "2026-05-11T14:23:00Z",
email: "jane@example.com",
shipping: 4.99,
tax: 2.0,
subtotal: 79.97,
products: [
{ product_id: "prod_1", sku: "SHIRT-BLU-M", name: "Blue T-Shirt", price: 29.99, quantity: 2, revenue: 59.98 },
{ product_id: "prod_2", sku: "HAT-BLK-OS", name: "Black Cap", price: 19.99, quantity: 1, revenue: 19.99 }
]
});
```
**Tag destination code:**
```js
console.log(event.event, event.properties);
```
**Console output:**
```javascript
Order Completed {order_id: 'R-10042', revenue: 89.95, total: 96.94, currency: 'USD', order_date: '2026-05-11T14:23:00Z', products: Array(2), …}
```
## HTML Mode
Embed `
```
**After macro substitution**, the injected script looks like:
```html
```
# The Event Object
| Field | Type | Present on | Description |
| ------------- | ------ | --------------- | --------------------------------------------------------- |
| `type` | string | All events | Event type: `"track"`, `"identify"`, or `"page"` |
| `event` | string | `track` only | Event name, e.g. `"Order Completed"` |
| `userId` | string | All events | Identified user ID (if available) |
| `anonymousId` | string | All events | Anonymous browser ID |
| `timestamp` | string | All events | ISO 8601 timestamp |
| `messageId` | string | All events | Unique ID for this event |
| `properties` | object | `track`, `page` | Event-specific or page properties |
| `traits` | object | `identify` | User traits passed to `identify()` |
| `context` | object | All events | Contextual info: IP, user agent, page URL, campaign, etc. |
Use `event.type` to distinguish between call types; use `event.event` to match specific track event names.
# Filtering by Event Name
Your code receives **every** event. Use a conditional to scope your logic to specific events:
```js
if (event.event === "Order Completed") {
// runs only on Order Completed
}
```
# Example: Hello World — Order Completed
This snippet logs order details to the browser console and sends a beacon to a custom endpoint whenever an `Order Completed` event fires.
**Source track call:**
```js
window.chord.track("Order Completed", {
order_id: "R-10042",
revenue: 89.95,
total: 96.94,
currency: "USD",
order_date: "2026-05-11T14:23:00Z",
email: "jane@example.com",
shipping: 4.99,
tax: 2.0,
subtotal: 79.97,
products: [
{ product_id: "prod_1", sku: "SHIRT-BLU-M", name: "Blue T-Shirt", price: 29.99, quantity: 2, revenue: 59.98 },
{ product_id: "prod_2", sku: "HAT-BLK-OS", name: "Black Cap", price: 19.99, quantity: 1, revenue: 19.99 }
]
});
```
**Tag destination code:**
```js
if (event.event === "Order Completed") {
var props = event.properties;
console.log(
"[My Tag] Order Completed — order_id:", props.order_id,
"revenue:", props.revenue,
"currency:", props.currency
);
navigator.sendBeacon(
"https://my-analytics.example.com/collect",
JSON.stringify({
event: event.event,
order_id: props.order_id,
revenue: props.revenue,
currency: props.currency,
products: props.products
})
);
}
```
**Console output:**
```javascript
[My Tag] Order Completed — order_id: R-10042 revenue: 89.95 currency: USD
```
**Beacon payload** (JSON body sent to your endpoint):
```json
{
"event": "Order Completed",
"order_id": "R-10042",
"revenue": 89.95,
"currency": "USD",
"products": [
{
"product_id": "prod_1",
"sku": "SHIRT-BLU-M",
"name": "Blue T-Shirt",
"price": 29.99,
"quantity": 2,
"revenue": 59.98
},
{
"product_id": "prod_2",
"sku": "HAT-BLK-OS",
"name": "Black Cap",
"price": 19.99,
"quantity": 1,
"revenue": 19.99
}
]
}
```
## Order Completed Properties Reference
| Property | Type | Required | Description |
| ------------ | ------ | -------- | ------------------------------------------------- |
| `order_id` | string | Yes | Order identifier |
| `revenue` | number | Yes | Revenue from the order |
| `total` | number | Yes | Total order value |
| `currency` | string | Yes | ISO 4217 currency code (e.g. `"USD"`) |
| `order_date` | string | Yes | Order date (ISO 8601) |
| `products` | array | Yes | Line items — see tracking plan for product schema |
| `email` | string | No | Customer email |
| `first_name` | string | No | Customer first name |
| `last_name` | string | No | Customer last name |
| `coupon` | string | No | Coupon code applied |
| `discount` | number | No | Discount amount |
| `shipping` | number | No | Shipping cost |
| `tax` | number | No | Tax amount |
| `subtotal` | number | No | Pre-tax, pre-shipping subtotal |
For the full tracking plan including all events and property schemas, refer to the Chord Tracking Plan documentation.
# Limitations
- **Device-mode only** — Tag destination code runs in the browser. It has no access to server-side context and cannot be used for server-to-server integrations.
- **No persistent state** — Your snippet is executed fresh on each event. Use `window` to share state across calls if needed.
- **Event filtering** — The destination connection supports `events` and `hosts` filters in the connection settings to restrict which events or domains trigger your code. You can also filter inside your snippet with `event.type` or `event.event` for finer-grained control.
***
**Updated 11 May 2026**
[title] Order Refunded
[path] Chord Event Tracking/Server Events/Track/
This event is triggered when an order is refunded.
# Properties
| **Name** | **Type** | **Description** | **Required** |
| ------------------ | ---------- | ---------------------------------------------------------------------------------------- | ------------ |
| `affiliation` | `string` | Store or affiliation from which this transaction occurred (for example, "Google Store"). | No |
| `channel` | `string` | The sales channel | No |
| `checkout_id` | `string` | ID of the checkout session for the purchase | No |
| `checkout_type` | `string` | Checkout provider (e.g. `Stripe`) | No |
| `currency` | `string` | ISO currency code of the transaction (e.g. `USD`) | Yes |
| `discount` | `number` | The total discount applied to the order | No |
| `email` | `string` | Email address associated with the order | No |
| `first_name` | `string` | Customer's first name | No |
| `last_name` | `string` | Customer's last name | No |
| `order_date` | `date` | Date and time the order was placed | Yes |
| `order_id` | `string` | Order/transaction ID | Yes |
| `phone` | `string` | Customer's phone number | No |
| `products` | `object[]` | Products in the order | Yes |
| `revenue` | `number` | Revenue ($) associated with the transaction (excluding shipping and tax) | Yes |
| `shipping` | `number` | The total amount for shipping | No |
| `shipping_city` | `string` | City of the shipping address | No |
| `shipping_country` | `string` | ISO country code for the shipping address | No |
| `shipping_state` | `string` | ISO state code for the shipping address | No |
| `shipping_zipcode` | `string` | Zip or postal code for the shipping address | No |
| `subscription_id` | `string` | ID of the subscription created from this purchase, if applicable | No |
| `subtotal` | `number` | Order total including discounts but excluding shipping and tax | No |
| `tax` | `number` | The total tax captured on the order | No |
| `total` | `number` | The order grand total, summing the subtotal, discount, shipping, and tax | Yes |
## Products array
| **Name** | **Type** | **Description** | **Required** |
| -------------- | -------- | ---------------------------------------------------------------------------------------- | ------------ |
| `affiliation` | `string` | Store or affiliation from which this transaction occurred (for example, "Google Store"). | No |
| `brand` | `string` | Brand associated with the product | No |
| `line_item_id` | `string` | ID of the line item in the database | No |
| `name` | `string` | Name of the product | Yes |
| `position` | `number` | Position in the product list | No |
| `price` | `number` | Price of the product | Yes |
| `product_id` | `string` | ID of the product in the database | Yes |
| `quantity` | `number` | The quantity of products purchased in this line item | Yes |
| `revenue` | `number` | Revenue ($) associated with this line item (excluding shipping and tax) | Yes |
| `sku` | `string` | SKU of the variant | Yes |
| `variant_name` | `string` | Name of the variant | No |
| `variant_id` | `string` | ID of the variant in the database | No |
# Sample Payload
```json
{
"type": "track",
"event": "Order Refunded",
"properties": {
"affiliation": "Afilliation",
"checkout_id": "40854979018855",
"checkout_type": "Shopify | OMS | Other",
"currency": "USD",
"discount": 5,
"email": "user@example.com",
"first_name": "John",
"last_name": "Doe",
"order_date": "2025-09-12T11:45:45-07:00",
"order_id": "6736819880039",
"order_number": "1895671",
"phone": "+15555555555",
"revenue": 219,
"shipping": 9.9,
"shipping_city": "Fall River",
"shipping_country": "US",
"shipping_state": "MA",
"shipping_zipcode": "02720",
"subtotal": 219,
"tax": 13.69,
"total": 237.59,
"products": [
{
"affiliation": "Affiliation",
"brand": "Brand",
"line_item_id": "16207084552295",
"name": "Product Name",
"position": 1,
"price": 219,
"product_id": "7036464939671",
"quantity": 1,
"revenue": 219,
"sku": "SKU123",
"variant": "Variant Name",
"variant_id": "40952658057847"
}
],
"meta": {
"i18n": {
"currency": "USD",
"locale": "en-US"
},
"platform": {
"name": "Shopify | OMS | Other",
"type": "web"
},
"store": {
"domain": "domain"
},
"version": {
"major": 3,
"minor": 0,
"patch": 0
}
}
},
"userId": "8046328840295",
"anonymousId": "7a76b270-c318-4477-b1e1-33eac94dbd1e"
}
```
# Example
```bash
curl https://production.cdp.ingest.chord.co/api/track \
--header "Content-Type: application/json" \
--header "X-Write-Key: $CDP_WRITE_KEY" \
--data-raw '{
{
"type": "track",
"event": "Order Refunded",
"properties": {}
"meta": {},
"userId": "123456",
"anonymousId": "7a76b270-c318-4477-b1e1-33eac94dbd1e"
}
```
[title] Getting started
[path] Chord Event Tracking/
## Overview
Chord Commerce is a commerce data platform for modern brands that streamlines the unification and activation of data across various business teams. The platform provides recommended tracking events for commerce sites to gather transactional and behavioral data, enabling comprehensive analytics and insights.
To get started, choose the guide that matches your commerce platform below.
## Installation Guides
### Shopify
For all Shopify stores — whether using a Liquid theme, Hydrogen, or a custom headless storefront.
- [Shopify installation](docId:7gGdgpVq4j3qwBPrHY1Fr) — Add Chord event tracking to your Shopify store
- [Shopify consent management](docId:8VjVftGhqN3w2fXaLQ43Z) — Configure privacy consent with Shopify's Customer Privacy API
### Non-Shopify Platforms
For custom storefronts, standalone websites, or platforms other than Shopify.
- [Custom storefront installation](docId\:UVSfzl1AlI_pMXp3KVO-B) — Add Chord event tracking using the Analytics SDK
- [Custom storefront consent management](docId\:NnS7HQreREyTGuQiQ7FoW) — Configure privacy consent with OneTrust or other providers
## Reference
- [Configuration](docId\:TEmFRwmdsClHrFfFNW_Zr) — Configuration options, metadata, and formatters
- [SDK API reference](docId\:iRcChoqam1zT_0UQZeLPp) — Complete list of tracking methods and their parameters
## Prerequisites
The Chord team will provide the following values needed for setup:
| Value | Description |
| ------------- | --------------------------------------------- |
| CDP Domain | Your Chord endpoint |
| CDP Write Key | Authentication key for sending events |
| OMS ID | UUID identifying your order management system |
| Store ID | UUID identifying your store |
| Tenant ID | UUID identifying your organization |
Contact [help@chord.co](mailto\:help@chord.co) if you haven't received these values.
[title] Shopify installation
[path] Chord Event Tracking/Getting started/Shopify/
This guide covers adding Chord event tracking to any Shopify store — Liquid themes, Hydrogen, or custom headless storefronts. The setup has three parts:
1. **Add **`@chordcommerce/analytics`** to your storefront** — loads the tracking library on your site
2. **Add the custom web pixel in Shopify Admin** — tracks checkout events and, for Liquid themes, storefront events
3. **Enable server event tracking via webhooks** — tracks server-side events such as order creations and order refunds
Adding all three elements ensures that all events, from browsing through checkout — including on Shopify's hosted checkout pages, are tracked in Chord.
:::hint{type="warning"}
Due to technical limitations within Shopify, the Chord analytics package does not load on Shop Pay pages.
:::
## Prerequisites
Before starting, ensure you have the values listed in [Getting Started]().
## How it works
Chord tracking on Shopify uses two components that work together:
1. `@chordcommerce/analytics` runs on your storefront pages and sends tracking events to Chord. It also loads any device-mode destination scripts (such as Google Analytics or Meta Pixel) directly in the browser. Additionally, it listens for events forwarded from the custom web pixel.
2. **The custom web pixel** runs within Shopify's event system, where it subscribes to all customer events (page views, add-to-cart, checkout steps, order completion). For storefront events, the web pixel forwards them to a listener on the top window within `@chordcommerce/analytics`, which processes the event and delivers it to Chord and any configured destinations (device-mode and cloud-mode). For checkout events that occur on Shopify-hosted pages, the web pixel sends them directly to Chord via cloud mode.
This architecture ensures complete event coverage — storefront interactions, Shopify-hosted checkout pages, and post-purchase events are all captured through a single, unified pipeline.
:::hint{type="info"}
**Note:** Due to technical limitations in Shopify, device-mode destinations (scripts that run in the browser) cannot be loaded or executed on Shopify-hosted pages. These pages include:
- Checkout
- Order status
- Thank you page
Events on these pages are delivered exclusively via cloud mode. Storefront pages are not affected — device-mode destinations load and execute normally there.
:::
## Step 1: Add `@chordcommerce/analytics` to Your Storefront
### Option A: Liquid Theme
For stores using a standard Shopify Liquid theme, add the Chord analytics snippet to your theme.
1. In your Shopify Admin, go to **Online Store > Themes > Edit code**.
2. Create a new snippet called `chord.liquid` and paste the following:
:::CodeblockTabs{indent="1"}
```javascript
{% comment %} //Instantiates analytics-liquid-identifiers, which handles reading/pasing of Cookies to Shopify cart attributes {% endcomment %}
{% comment %} //Instantiates Chord Analytics {% endcomment %}
```
:::
3. In `layout/theme.liquid`, add the following before the closing `` tag:
:::CodeblockTabs{indent="1"}
```javascript
{% render 'chord' %}
```
:::
### Option B: Hydrogen / Headless Storefront
For Hydrogen or other JavaScript-based storefronts, install the npm package.
1. Install the package:
2. Initialize the library in your root layout or app entry point:
3. Add your environment variables:
See [Configuration]() for the full list of options, and [SDK API Reference]() for tracking methods you can call from your storefront code.
## Step 2: Add the Custom Web Pixel
The custom web pixel subscribes to all Shopify customer events and tracks events on Shopify-hosted pages, such as checkout. Specifically for each platform:
- **Liquid themes**: All storefront and checkout tracking
- **Headless storefronts**: Checkout tracking only (storefront events are handled by your SDK integration in Step 1)
### Installation
1. In your Shopify Admin, go to **Settings > Customer events**.
2. Click **Add custom pixel**.
3. Name the pixel (e.g., "Chord").
4. Paste the web pixel code provided by the Chord team. The code includes configuration constants at the top that must be filled in:
5. Under **Customer privacy**, select **Does not require consent** (consent is managed by `@chordcommerce/analytics` — see [Consent Management]()).
6. Click **Save**, then click **Connect** to activate the pixel.
### Verifying the Installation
After installing both components, open your browser's developer console and verify:
1. **On a storefront page** (e.g., a product page): You should see Chord network requests when browsing products, adding to cart, etc.
2. **On the checkout page**: Checkout events (Checkout Started, Payment Info Entered, Order Completed) should appear in your Chord Live Events view.
:::hint{type="info"}
**Tip:** Set debug: true in your @chordcommerce/analytics configuration during development. This validates events against the tracking plan and logs warnings for missing or incorrect properties
:::
## Step 3: Enable Server Event Tracking
In addition to front-end tracking, Chord can receive server-side events from Shopify via webhooks. This enables tracking for events that occur outside the browser, such as order refunds.
See [Shopify server event tracking](docId\:xbL7zBqE14BT7gbTMl0un) for setup instructions.
## Troubleshooting
### Events not appearing in Chord
- Verify the Domain and Write Key are correct in both the analytics library and the web pixel.
- Check the browser console for error messages from Chord.
- Ensure the web pixel status is "Connected" in Shopify Admin > Customer events.
### Storefront events missing (Liquid themes)
- Confirm `{% render 'chord' %}` is in your `theme.liquid` layout.
- Check the browser console for script loading errors from jsdelivr.
### Checkout events missing
- Verify the web pixel is connected (not just saved) in Shopify Admin.
- Check that the credentials in the web pixel match your analytics library configuration.