[space] Chord Commerce [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] Okendo [path] Chord Data Platform/Data Sources/Connect Data Sources/ Connect your Okendo reviews and survey data to Chord. Okendo is the reviews, ratings, and customer-survey platform that powers social proof and post-purchase feedback for many Chord brands. Chord ingests your product reviews and your survey responses, including NPS, so you can analyze review sentiment, ratings, and customer feedback next to your orders, subscriptions, and the rest of your commerce data. ## What Chord ingests from Okendo Chord brings in two categories of Okendo data. Each becomes its own table (or set of tables) in your Chord Snowflake schema, and both link back to your orders and customers. - **Product reviews.** Every review left on your products: star rating, review title and body, sentiment, the reviewer, the product and variant reviewed, verified and incentivized flags, helpful-vote counts, any merchant reply, and any reward attached to the review. Chord pulls these from the Okendo Merchant REST API on your tenant's standard sync schedule. - **Survey responses.** Your post-purchase and NPS survey submissions: the survey and channel, each answered question (question text, question type, the answer, and any custom "Other" answer), and the NPS score and category where applicable. Every response links back to the originating order and customer. These arrive continuously through Okendo's webhook events, and historical responses are backfilled once (see below). :::hint{type="info"} **Heads up:** reviews and survey responses reach Chord through different mechanisms. Okendo's API can list your reviews, but it has no endpoint to list your surveys. The next section explains how each one flows in and what that means for the data you'll see. ::: ## How Chord ingests Okendo data Three workflows sit behind your Okendo data. You don't operate any of them yourself. This is here so you understand what data shows up, when, and why. **1. Reviews, pulled from the API.** Once you connect your Okendo credentials in Chord, Chord calls the Okendo Merchant REST API on your regular ingestion schedule and pulls your reviews into the warehouse. This is a normal scheduled sync, like your other connectors. **2. Survey responses, captured through webhooks.** Okendo's API can return reviews, but it has no way to list your surveys, so Chord can't pull survey responses the way it pulls reviews. Instead, Chord captures them through Okendo's webhook events. As customers submit responses, Okendo sends an event that Chord receives into its CDP ingestion and lands in your warehouse. This is a going-forward feed. Every new response flows in from the moment the webhook is live. :::hint{type="warning"} **Heads up:** the Okendo survey webhook is configured as part of Chord onboarding, not something you set up yourself. If you're onboarding Okendo surveys and you're unsure whether the webhook is already live for your account, confirm with your Chord contact so you know when the going-forward feed starts. ::: **3. Survey backfill for historical responses.** The webhook feed only covers responses submitted after it goes live. To fill in everything before that, Chord backfills your historical survey responses: it requests the responses for each of your known surveys directly from Okendo, then reconciles them against the live webhook feed so nothing is double-counted. The result is a single, deduplicated view of your survey responses that spans both history and everything arriving in real time. :::hint{type="info"} **Heads up:** reviews and survey responses are modeled in Chord and available for analysis next to your OMS and commerce data. NPS is derived from the survey answers themselves, so it lives with your survey-response data rather than in a separate feed. ::: ## Generate your Okendo API credentials You'll need two values from Okendo: your **User ID** and a **Merchant REST API Key**. Okendo generates them together in the integration settings of the app, and Chord uses them as a pair. The User ID acts as the username and the API key as the password for authenticating to the Okendo Merchant REST API. There are no scopes or permission toggles to configure. :::hint{type="warning"} **Heads up:** generating API credentials is an account-level action in Okendo, so you'll typically need admin access to the app. If you don't see the integration settings, ask an admin on your Okendo account to generate the credentials for you. ::: 1. Log in to the Okendo app. 2. Go to **Settings → Integrations**. 3. Under the API credentials section, click **Generate** (or **Show**, if credentials already exist) to reveal your **User ID** and **Merchant REST API Key**. 4. Copy both values. The User ID is a UUID that looks like `00000000-0000-0000-0000-000000000000`. The Merchant REST API Key is a 32-character string. ## Connect the credentials in Chord 1. Open Chord Hub and go to **Data Sources → Add Source**. 2. Pick **Okendo** from the data source list. 3. Paste your Okendo User ID into the **User ID** field. 4. Paste your Merchant REST API Key into the **API Key** field. 5. Click **Save**. Chord makes a test call against the Okendo reviews endpoint to confirm the credentials work. 6. The first reviews sync kicks off automatically, and later syncs run on your tenant's standard ingestion schedule. Survey responses flow in through the webhook feed and the one-time backfill described above. ## Troubleshooting **What does the validate step actually check?** Chord makes a small read against `https://api.okendo.io/enterprise/reviews?limit=1` using your User ID and API key, and confirms it returns a 200 response. It does not pull or store any records. That happens on the first scheduled sync after you save the credentials. **The validate step failed. What now?** Okendo credentials are a User ID and key pair with no scopes, so a failure almost always means one of the two values is wrong, was regenerated in Okendo, or was copied with extra whitespace. Go back to **Settings → Integrations** in the Okendo app, reveal both values again, and re-copy them carefully. It's easy to grab the User ID and the API key from the wrong rows. Paste both into the same Chord credential entry and test again. **Why do I only see reviews so far, and not survey responses?** Reviews are pulled from the API as soon as you connect your credentials, so they appear on the first sync. Survey responses depend on Okendo's webhook feed plus the historical backfill, which are set up during onboarding rather than by connecting the API key. If your reviews are landing but survey responses aren't, confirm with your Chord contact that the survey webhook is live for your account. **Where does NPS come from?** NPS score and category come from the answers inside your survey responses. Okendo carries them on the survey submission itself. Once your survey-response data is flowing, NPS is available alongside it, with no separate NPS feed to connect. **Do Okendo API credentials expire?** Okendo's public documentation doesn't state an expiration policy for Merchant REST API credentials. If a credential that worked before suddenly fails, check **Settings → Integrations** in the Okendo app first to confirm the values are still present and haven't been regenerated, then re-copy them into Chord. **How do I rotate the credentials?** Regenerate the credentials in the Okendo app, paste the new User ID and API key into the same Chord credential entry, and save. Chord uses the new values on the next scheduled sync. Confirm the new credentials validate and the next sync runs cleanly before you rely on them. *** **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] 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] 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. ![](https://archbee-image-uploads.s3.amazonaws.com/iCsIrWE2VP6jmzs1DjUUy-wfWNIv0GtdtOW8Y4-YyTy-20250305-025408.png) ## 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. ![](https://archbee-image-uploads.s3.amazonaws.com/iCsIrWE2VP6jmzs1DjUUy-NnJdqggEjwn4KdrLEshvL-20250305-174003.png) ### 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. ![](https://archbee-image-uploads.s3.amazonaws.com/iCsIrWE2VP6jmzs1DjUUy-m5jXtE4ouBcs4ZfHVXpEU-20250305-174305.png) 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. ![](https://archbee-image-uploads.s3.amazonaws.com/iCsIrWE2VP6jmzs1DjUUy-CEOGJeBHGoVIJhiWKkoFV-20250305-174944.png) You should end up with the following: ![](https://archbee-image-uploads.s3.amazonaws.com/iCsIrWE2VP6jmzs1DjUUy-t4Lf9B4QaT9DUYKSHImma-20250305-174955.png) **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: ![](https://archbee-image-uploads.s3.amazonaws.com/iCsIrWE2VP6jmzs1DjUUy-_6pU13DoZFz3PxzalPVVx-20250305-175229.png) 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: ![](https://archbee-image-uploads.s3.amazonaws.com/iCsIrWE2VP6jmzs1DjUUy-thJl0oUwqJEG5b0Pkump--20250305-180439.png) ## Sync Results The Chord platform will display the sync results as usual: ![](https://archbee-image-uploads.s3.amazonaws.com/iCsIrWE2VP6jmzs1DjUUy-X8TfnjmOZSJ_Y6Zt4mjEV-20250305-180533.png) # 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] 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] 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] 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] 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] 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: ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-t4udfCSVJNaR8PFAKe6k5-20250826-215007.png) 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] 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] 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] 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] Ask Chord: Powered by Anthropic [path] AI features/Ask Chord/ Ask Chord runs on Anthropic's Claude, a large language model built for reliability, safety, and consistent performance. This page explains which models Ask Chord uses, how they're matched to specific tasks, and why we chose Anthropic. ### Models in use Ask Chord uses three Claude models, each matched to a specific job, with a fallback model if Claude is unavailable. | **Task** | **Primary model** | **Fallback** | | --------------------- | ----------------- | ------------ | | Copilot chat | Claude Opus 4.8 | GPT-5.5 | | Insights agent | Claude Sonnet 4.6 | GPT-5.5 | | Audience smart naming | Claude Haiku 4.5 | — | **Copilot chat** handles conversational Q\&A, where reasoning depth and context-handling matter most. **Insights agent** handles analysis and synthesis tasks that run after data is fetched, balancing quality with speed. **Audience smart naming** generates concise names for saved audiences, a lightweight task suited to a fast, smaller model. Why Anthropic We evaluated several leading AI models against Chord's commerce use cases. Anthropic's Claude stood out for three reasons: - **Output stability. **Claude produces consistent, structured responses across repeated and varied inputs, reducing unexpected results. - **Reasoning quality.** Claude handles complex, multi-step logic reliably, which matters 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. ### FAQs **Will model updates affect my existing prompts or workflows?** No. All existing prompts, automations, and integrations continue to work as before. 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. See our privacy policy for full details. **Who do I contact if I notice unexpected behavior?** Reach out to [help@chord.co](mailto\:help@chord.co) or contact your Chord account team. [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] 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: ** ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-FfgexO5vj2sBwL0Gj0hWK-20250812-213654.png) 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] 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] 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: ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/BJD3bwQX1CdwlRvNAA_-v_image.png) :::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] 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] 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] 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] 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] 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): ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-GSUPCD0jzNGoCxiv5gAFW-20250604-160005.png) # 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. ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-IIBTNPUc8q9wVFWASXs9f-20250604-160053.png) ## 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. ::: ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-HWRhV1evYyi9ZT8Iia6mH-20250604-160243.png) # 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` ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-l-DPlQsNVCkMdTHP09kVw-20250604-184828.png) You should end up with the following: ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-k8QyJ3A0yWvduWyPeXSWC-20250604-184854.png) # 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. ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-fuAQWG0ucAxMkBZweRVhS-20250604-184943.png "Sync Schedule Dropdown") ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-E3YejzY7wz1A8fcHZAkri-20250604-185856.png) ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-QZ2bv9iaWkdE7_QQEwX_6-20250604-190014.png "My Syncs sidesheet ") [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] 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. ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/BJD3bwQX1CdwlRvNAA_-v_image.png) :::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] 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: ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-vmg8V81u8d5Ex6hfDlKy7-20250625-194138.png) ### 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: ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-OacLGp66sV3Nq3aR19AAk-20250625-194300.png) 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: ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-jc79KdX-SQmE6zLJwewrq-20250625-194419.png) [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] 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 ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-_ctAlSnwxZL8JlFmcDPm4-20250625-194943.png) ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-q_mNgK75709uYYBRLSmrW-20250625-195051.png) ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-yb7hcdwK9G3InrRr4dVmr-20250625-195110.png) 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] 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 ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-iwnqujpfI5syVKKaR2GyZ-20250625-194714.png) ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-NHEWAfN4o-SAGsUs6D2W3-20250625-194737.png) ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-1S_KoGbM_QnFhoDDBEw46-20250625-194747.png) 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] 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): ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-GSUPCD0jzNGoCxiv5gAFW-20250604-160005.png) # 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. ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-IIBTNPUc8q9wVFWASXs9f-20250604-160053.png) ## 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. ::: ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-HWRhV1evYyi9ZT8Iia6mH-20250604-160243.png) # 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` ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-l-DPlQsNVCkMdTHP09kVw-20250604-184828.png) You should end up with the following: ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-k8QyJ3A0yWvduWyPeXSWC-20250604-184854.png) # 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. ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-fuAQWG0ucAxMkBZweRVhS-20250604-184943.png "Sync Schedule Dropdown") ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-E3YejzY7wz1A8fcHZAkri-20250604-185856.png) ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-QZ2bv9iaWkdE7_QQEwX_6-20250604-190014.png "My Syncs sidesheet ") [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. ![](https://docs.getcensus.com/~gitbook/image?url=https%3A%2F%2F217220813-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MV3poo0VqVau1o8I79_%252Fuploads%252Fh9zq593WC6OFOBLkL0JU%252FGoogle%2520Ads.png%3Falt%3Dmedia%26token%3Ddcc96d7c-45bd-4eb8-8aef-72aa0a461148\&width=768\&dpr=4\&quality=100\&sign=f2b6417e\&sv=2) | **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] 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] 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] 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] 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] 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] 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] 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] 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" ![](https://docs.getcensus.com/~gitbook/image?url=https%3A%2F%2F217220813-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MV3poo0VqVau1o8I79_%252Fuploads%252Fgit-blob-fecefa194ecc308306afc53e9cd87a7c4798eda2%252Fsfmc_step1.png%3Falt%3Dmedia\&width=768\&dpr=4\&quality=100\&sign=32f2601e\&sv=2) ![](https://docs.getcensus.com/~gitbook/image?url=https%3A%2F%2F217220813-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MV3poo0VqVau1o8I79_%252Fuploads%252Fgit-blob-457512f75353bb417ad78e477db7af8516034cd4%252Fsfmc_step2.png%3Falt%3Dmedia\&width=768\&dpr=4\&quality=100\&sign=2930b5fb\&sv=2) Click "Add Component" and choose "API Integration" ![](https://docs.getcensus.com/~gitbook/image?url=https%3A%2F%2F217220813-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MV3poo0VqVau1o8I79_%252Fuploads%252Fgit-blob-0a537972b9f9d52f0049877113c4b828bcaf584a%252Fsfmc_step3.png%3Falt%3Dmedia\&width=768\&dpr=4\&quality=100\&sign=9d91c69e\&sv=2) Choose "Server-to-Server" as the OAuth Integration Type ![](https://docs.getcensus.com/~gitbook/image?url=https%3A%2F%2F217220813-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MV3poo0VqVau1o8I79_%252Fuploads%252Fgit-blob-25da65adfd719a965c6bd2b8ca6ae7f10eba93b6%252Fsfmc_step4.png%3Falt%3Dmedia\&width=768\&dpr=4\&quality=100\&sign=43451a34\&sv=2) 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. ![](https://docs.getcensus.com/~gitbook/image?url=https%3A%2F%2F217220813-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MV3poo0VqVau1o8I79_%252Fuploads%252Fgit-blob-aac65832b016af844c687a0a6e6d33a5ea0ef95f%252Fsfmc_step5.png%3Falt%3Dmedia\&width=768\&dpr=4\&quality=100\&sign=491c27f1\&sv=2) 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** ![](https://docs.getcensus.com/~gitbook/image?url=https%3A%2F%2F217220813-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MV3poo0VqVau1o8I79_%252Fuploads%252Fgit-blob-3f6c70fb187151a03427a18cd3cfb0916a47e66c%252Fscreely-1653426548785.png%3Falt%3Dmedia\&width=768\&dpr=4\&quality=100\&sign=2dbd9373\&sv=2) **FTP User** Still in Salesforce Marketing Cloud Setup, navigate to "Data Management > FTP Accounts" and click "Add FTP User". ![](https://docs.getcensus.com/~gitbook/image?url=https%3A%2F%2F217220813-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MV3poo0VqVau1o8I79_%252Fuploads%252Fgit-blob-94892a29ccacd2471ec8c9a0e133952445f4eeef%252Fsfmc_step6.png%3Falt%3Dmedia\&width=768\&dpr=4\&quality=100\&sign=10cbb0a\&sv=2) 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. ![](https://docs.getcensus.com/~gitbook/image?url=https%3A%2F%2F217220813-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MV3poo0VqVau1o8I79_%252Fuploads%252Fgit-blob-e14ed2e30bf540d7faa95c5c78d55243f016a56e%252Fsfmc_step7.png%3Falt%3Dmedia\&width=768\&dpr=4\&quality=100\&sign=327efbf6\&sv=2) There's nothing to do yet on the next screen - we'll set up SSH Keys later. ![](https://docs.getcensus.com/~gitbook/image?url=https%3A%2F%2F217220813-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MV3poo0VqVau1o8I79_%252Fuploads%252Fgit-blob-1937d6a4500043942f851e9fb1f75c3bef9e7068%252Fsfmc_step8.png%3Falt%3Dmedia\&width=768\&dpr=4\&quality=100\&sign=cbd1864c\&sv=2) Select the Root folder as the Home Folder for your user. Click "Save" to create the user. ![](https://docs.getcensus.com/~gitbook/image?url=https%3A%2F%2F217220813-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MV3poo0VqVau1o8I79_%252Fuploads%252FGjZZVE7O8pBeCVWQONTX%252FScreenshot%25202024-06-25%2520at%25205.31.39%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D3b6adca0-6729-480e-a3b7-862aec5ff593\&width=768\&dpr=4\&quality=100\&sign=f0636bc0\&sv=2) 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**. ![](https://docs.getcensus.com/~gitbook/image?url=https%3A%2F%2F217220813-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MV3poo0VqVau1o8I79_%252Fuploads%252FT1vbrCUX8HPrMr9amP9r%252FSFMC%2520-%2520Card.png%3Falt%3Dmedia%26token%3D9dfc20af-c67a-4271-a025-f895486357b8\&width=768\&dpr=4\&quality=100\&sign=1249e05\&sv=2) 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). ![](https://docs.getcensus.com/~gitbook/image?url=https%3A%2F%2F217220813-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MV3poo0VqVau1o8I79_%252Fuploads%252FmkM68LXtFbHQMUGVu4is%252FCleanShot%25202023-02-02%2520at%252010.01.34%25402x.png%3Falt%3Dmedia%26token%3Df45369bd-5872-4e7a-9b7e-514d9def00f8\&width=768\&dpr=4\&quality=100\&sign=9d5c1ce9\&sv=2) - 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` : ![](https://docs.getcensus.com/~gitbook/image?url=https%3A%2F%2F217220813-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MV3poo0VqVau1o8I79_%252Fuploads%252Fgit-blob-bacd9f6d9c09e664ae85e509882982977fedceab%252FCleanShot%25202023-01-03%2520at%252011.12.41%25402x.png%3Falt%3Dmedia\&width=768\&dpr=4\&quality=100\&sign=9d3a4965\&sv=2) 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". ![](https://docs.getcensus.com/~gitbook/image?url=https%3A%2F%2F217220813-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MV3poo0VqVau1o8I79_%252Fuploads%252F6Doshr25YpCK6KJNXLxL%252FSFMC%2520-%2520Config.png%3Falt%3Dmedia%26token%3D04012a15-a217-4e3f-9293-1b0f4345dbfe\&width=768\&dpr=4\&quality=100\&sign=5a0f0d11\&sv=2) - 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. ![](https://docs.getcensus.com/~gitbook/image?url=https%3A%2F%2F217220813-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MV3poo0VqVau1o8I79_%252Fuploads%252Fgit-blob-94b903da3f6a1633516d92c909c5e057f2c99ca1%252Fsfmc_step12.png%3Falt%3Dmedia\&width=768\&dpr=4\&quality=100\&sign=a560b5e6\&sv=2) ![](https://docs.getcensus.com/~gitbook/image?url=https%3A%2F%2F217220813-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MV3poo0VqVau1o8I79_%252Fuploads%252Fgit-blob-72ea0eb357cf75395da2f04b809654edf550e747%252Fsfmc_step13.png%3Falt%3Dmedia\&width=768\&dpr=4\&quality=100\&sign=e034ef7f\&sv=2) 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". ![](https://docs.getcensus.com/~gitbook/image?url=https%3A%2F%2F217220813-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MV3poo0VqVau1o8I79_%252Fuploads%252Fgit-blob-d158ecccb3153bd01b90bf817da942c815299fff%252Fsfmc_step14.png%3Falt%3Dmedia\&width=768\&dpr=4\&quality=100\&sign=c62ac329\&sv=2) 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. ![](https://docs.getcensus.com/~gitbook/image?url=https%3A%2F%2F217220813-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MV3poo0VqVau1o8I79_%252Fuploads%252FSOFwu2fLPn5oTuKvuLBg%252FSFMC%2520-%2520New%2520DE.png%3Falt%3Dmedia%26token%3D244f136a-81f1-47f4-b894-16f2df299a86\&width=768\&dpr=4\&quality=100\&sign=388cf783\&sv=2) 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. ![](https://docs.getcensus.com/~gitbook/image?url=https%3A%2F%2F217220813-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MV3poo0VqVau1o8I79_%252Fuploads%252FmjDPTw8mIF1CuCj2yWmN%252FSFMC%2520-%2520Folder%2520Path.png%3Falt%3Dmedia%26token%3D36d74652-48a3-45b4-ba5e-295f6c4c494c\&width=768\&dpr=4\&quality=100\&sign=eb8c834a\&sv=2) - 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] 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] Home [path] / **Chord** Chord is a commerce data and AI platform for modern brands. It unifies your commerce data, models it into a trusted foundation, and lets your team get answers and take action without waiting on SQL or analysts. **AI features** Ask questions, get alerts, connect external AI tools, and configure your business logic. **Chord Data Platform** Your data foundation: sources, modeling, audiences, activations, and analytics. **Chord CDP** Collect, unify, and activate customer data, including sources, destinations, and identity. **Chord Event Tracking** Your tracking plan and pixel setup. **Chord OMS** Order management. **New here? **Start with **Ask Chord **to see what Chord can do with your data. Questions or feedback? Reach out to [help@chord.co](mailto\:help@chord.co). [title] Chord FAQ [path] AI features/ ## Data security and privacy **How does Ask Chord protect my data?** Ask Chord 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. Ask Chord processes your data within our platform and does not send any raw business or customer data to external AI providers. **Does Ask Chord use my data to train external LLMs?** Never. Your data is not used to train, fine-tune, or improve any models outside your organization. Ask Chord uses a multi-LLM architecture that handles different data components strategically to ensure your data stays private. Your sensitive data remains protected without risk of being sent to or trained on public LLMs. **Can I control what data Ask Chord has access to?** Yes. Ask Chord uses only the data that a given user is permitted to access. If a user can't view data on the Chord platform, they can't query it with AI either. ## Functionality and capabilities **What can I use Ask Chord for?** You can ask questions about your customers, orders, products, and performance. Ask Chord translates these into SQL and returns accurate results from your data. **What types of questions work best with Ask Chord?** Ask Chord works best with clear, specific questions. For example: - "What was our average order value last month?" - "Which products are most frequently purchased by subscribers?" **Can I see the SQL behind Chord's answers?** Yes. Every response includes the SQL used. Click **View SQL** at the bottom of any Copilot answer to view or reuse it. **What's the difference between Classic Copilot and Ask Chord?** Classic Copilot follows a structured pipeline to answer questions. Copilot Next is a ground-up rebuild that uses an agentic model, allowing it to reason through complex, multi-part questions more flexibly. Ask Chord is currently in early access. See the Ask Chord Technical Overview for more detail. ### Access and use **Who can use Ask Chord in my organization?** Ask Chord access is permission-based. Reach out to your Chord account team for details on access controls for your organization. **Does using Ask Chord require special training or technical knowledge?** No training required. Ask Chord is designed to work for marketers, operators, and analysts, no SQL background needed. **Who do I contact if something isn't working as expected?** Reach out to help\@chord.co or contact your Chord account team. [title] Ask Chord [path] AI features/ Ask Chord gives your team instant answers from your commerce data. No SQL, no analysts, no waiting. Ask questions in plain language and get accurate, warehouse-backed results in seconds. It's built directly on your data and configured around your business logic, so answers reflect how your store actually works without generic benchmarks or approximations. ![]() ### What you can do with Ask Chord **Ask questions in plain language.** Query revenue, customers, orders, products, and more through Ask Chord. Ask Chord retains conversation history, interprets intent, and enriches answers with real-time warehouse data. **Monitor key metrics automatically.** Set threshold-based alerts on any metric with Monitors. Get notified when something changes without having to check manually. **Configure Ask Chord for your business. **Use Context to add business-specific instructions. ### Documentation | Page | What it covers | | -------------------------------------------------- | --------------------------------------------------------------------- | | [Chord MCP](docId\:xDXIDcjizy5jo0os6459T) | Connecting your Chord data to Claude for plain-language data queries. | | [Ask Chord](docId\:uDKKrg_now046q4AHxW_1) | Asking questions and working with answers. | | [Chord Monitors](docId\:V-tvyXQ6DT1vta_rU6ww6) | Setting up automated metric alerts. | | [Chord Context](docId\:mfhdXenmV-zhZshr_0Bpa) | Adding instructions and SQL pairs. | | [Ask Chord Use Cases](docId:6NaZo1PB2NL3m-VRxTPyR) | Example questions and workflows. | | [Chord FAQ](docId\:ZPWngfj3CK6UWAM29TiO9) | Common questions and answers. | *Questions or feedback? Reach out to *[help@chord.co](mailto\:help@chord.co)*.* [title] MCP Server Usage Guidelines [path] AI features/Chord MCP/ # Using the Chord MCP Server The Chord MCP server lets AI clients query your Chord data conversationally. This page covers what it is built for, what it is not, and the limits that apply so you can use it well. ## What the MCP server is for The MCP server is for interactive, agentic querying from AI clients like Ask Chord, Claude Desktop, and other MCP-compatible tools. You ask a question in natural language, your client uses the Chord tools to answer it, and you get an answer back. It is designed for exploration and analysis in the moment. A person or an agent asks a question, gets a result, and acts on it. The tools it exposes (`search_schema`, `search_sql_pairs`, `search_instructions`, and `execute_sql`) are there to help a client reason its way to a good answer, not to serve as a raw data feed. ## What it is not for The MCP server is not a data API and not a warehouse connection. Please avoid using it to: - **Power live or production dashboards.** Do not wire `execute_sql` to dashboard tiles that refresh on a timer. A single dashboard refresh can fan out into hundreds or thousands of tool calls. - **Continuously poll for data.** Firing repeated queries on a short loop to keep an external app in sync is not a supported pattern. - **Bulk-replicate the warehouse. **The MCP server is not a mechanism for copying your Chord data out at scale. These patterns generate very high call volume, run into the rate limits below, and drive up compute cost with no benefit over the supported patterns further down this page. # Rate limits MCP tool calls are rate limited per account. The current limit is 60 tool calls per minute. Calls above the limit are rejected until the next window. Chord may apply additional limits over longer windows and may adjust these limits over time. Design your usage to stay well under the ceiling. If your client is regularly hitting the limit, that is usually a sign it is being used as a polling API rather than as an interactive assistant, and the patterns below will serve you better. # Cost awareness MCP queries run against Snowflake and consume compute. Occasional interactive querying is inexpensive. Sustained, high-frequency querying, like the dashboard and polling patterns above, can get expensive quickly, because every call is real warehouse compute. A few efficient, scheduled queries cost a fraction of continuous per-tile polling. # Patterns that work If you have a recurring data need, you can still use MCP well. The goal is fewer, well-formed queries instead of many small live ones. - **Pull on a schedule, not on every view.** Run one efficient query on a cadence that fits your needs, for example daily or hourly, and cache the result in your app. Do not query live on every tile or page load. - **Batch related questions**. Ask for what you need in as few calls as possible rather than many small ones. - **Cache and reuse.** Store results your app reads repeatedly instead of re-querying for the same data. Clients that stay comfortably within the limits tend to follow exactly this shape: a small number of efficient queries on a schedule, with results cached on their side. ## Need data in your own systems? If you need Chord data delivered into your own warehouse or application beyond what interactive MCP querying supports, reach out to your Chord contact so we can point you to the right path for your setup. [title] Ask Chord Technical Overview [path] AI features/Ask Chord/ This guide explains how Ask Chord 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 Ask Chord works Ask Chord is a ground-up rebuild of the Classic Chord AI experience. Rather than following a fixed pipeline, Ask Chord uses an LLM agent that reasons through your question and decides which tools to call, making it better suited for complex, multi-part questions. **How it works** 1. You ask a question in Ask Chord. 2. An LLM agent receives your question along with access to a set of Ask Chord tools via Chord MCP, a Model Context Protocol server that exposes your schema, saved views, SQL pairs, instructions, and SQL execution as individual callable tools. 3. The agent chains these tools as needed: searching your schema, retrieving relevant context, and executing SQL against your warehouse. 4. Results stream back in real time as the agent composes its answer. ## Ask Chord at-a-glance | | **Ask Chord** | | ----------------- | --------------------------------------------- | | **Orchestration** | LLM agent that chains tools dynamically | | **Data access** | Individual MCP tools via Chord MCP | | **Best for** | Complex, multi-step, or exploratory questions | | **Status** | Generally available | ## Data privacy Ask Chord does not store your data. We work with your schema only, meaning 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 FAQ](docId\:ZPWngfj3CK6UWAM29TiO9). [title] AI features [path] / **AI features** Chord's AI features let your team work with your commerce data directly, no SQL or analysts required. - **Ask Chord:** ask questions about your data in plain language and get answers in seconds. - **Chord Monitors: **get alerted when a metric crosses a threshold you set. - **Chord MCP:** connect your Chord data to external AI tools like Claude. - **Chord Context:** teach Chord your business logic so answers reflect how your store works. New to Chord's AI? Start with **Ask Chord**. For worked examples, see [Ask Chord Use Cases](docId:6NaZo1PB2NL3m-VRxTPyR). [title] Creating Audiences from Custom Explores [path] AI features/Ask Chord/ Ask Chord can turn any answer with a list of records into a saved audience and an explore in **Custom Explores.** **How it works:** 1. Ask a question that returns a list of records (e.g. "customers whose first order was in Q1 2025"). 2. Click **Explore in Analytics** on the answer. 3. Name the audience and click **Create Audience**. 4. Open **View in Custom Explores** or **View in Shared Audiences** once it finishes. **Good to know:** - Names must be unique. Reusing an existing audience name is blocked, since that audience may already feed a live data sync. - Answers without a list of records (e.g. definition questions) can't be turned into an audience. - To activate an audience, check out our instructions on [audience activations](docId\:FNUhk7dhtg2ckYZPI89X0). [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] 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: ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/BJD3bwQX1CdwlRvNAA_-v_image.png) :::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] 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] 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] 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] 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. ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/9pzOJrQB09tfcwHXcfrhe_screenshot-2024-07-15-at-54638-pm.png) 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. ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/7U5zexVtadX1gaCG_on_4_screenshot-2024-07-15-at-54509-pm.png) 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: ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-1gt1bN7KxE0ad7VppnJvq-20250228-191524.png) 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] 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] 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] 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] 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] Sharing Data with Chord from 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. 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] 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 ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-UPMPV-mOwhMwKKz5YkYJX-20240828-222450.png "Audiences - Request Access screen") ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-Ud88_XLUzAXv9OYh63_BQ-20240828-222526.png "Audiences - Request Received screen") 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). ::: ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-2qq8arKpgcM3xATvwenje-20250305-165002.png) # 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. ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-lYmzow7K6PUjGCupwlJIr-20250305-165109.png) 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: ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-MNaB013a-k40xzTy0BR0m-20250305-165159.png) 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. ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-gr_HryWrsD_M9ii8q7P9S-20250305-165353.png) 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: ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-xnkPXESY1UUplI2n4I2m9-20250305-165431.png) 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! ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-2UR4gILD2aRiANDbYZwj8-20240829-144310.png "Gear button location") ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-qSUCsUSCDpyLFRcJD3_CQ-20240829-144336.png "Save As location") # Contact Support Need help? Contact Chord support at [help@chord.co](mailto\:help@chord.co)! [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 ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/-70bD-vNrMr_JnXpcMYtP_image.png) ## Example audience using user ID & email ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/yjK1Lb7cR4QTppEpSqOA6_image.png) 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: ![](https://archbee-image-uploads.s3.amazonaws.com/U9fkmkKcgT5gcNLmEiMMt-7Yv6hfmVbRz1jGwsF7GnR-20250630-171346.gif) 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: ![](https://archbee-image-uploads.s3.amazonaws.com/U9fkmkKcgT5gcNLmEiMMt-r_dStZkaBj-iV4KYuwmWc-20250630-172226.gif) 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: ![](https://archbee-image-uploads.s3.amazonaws.com/U9fkmkKcgT5gcNLmEiMMt-kbxleogXQtVafRvT6kE9K-20250630-172929.gif) 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 Retargeting [path] Chord Data Platform/ Chord can identify anonymous website visitors and bring them into your retargeting campaigns, so you reach more shoppers without changing how your campaigns already work. Today, your retargeting campaigns (Cart Abandonment, Product Abandonment, and Price Drop) only reach shoppers who logged in or gave you their email. Everyone else, even shoppers who browsed products and left, was invisible to those campaigns. Chord Reveal can match many of those anonymous visitors to a real email address using trusted third-party data. Once matched, those shoppers are automatically added to the same retargeting campaigns you already run. More of your website visitors become instantly reachable. Your existing campaign rules, timing, and suppression logic do not change. # How it works Reveal adds one new step before your campaigns run. Here is the flow: 1. A shopper browses your site anonymously and doesn't log in or submit an email. 2. Reveal attempts to match that visitor to a real email address using third-party identity data. 3. If a match is found, Chord checks whether that email already exists in your CRM. 4. If the email is new to your CRM, the shopper is labeled reveal. 1. If it already exists, they're treated the same as any other known shopper. 5. The shopper (with their new label) flows into your existing Cart Abandonment, Product Abandonment, or Price Drop campaign, exactly like any other eligible shopper. Nothing about your campaign rules, send timing, or suppression lists changes. Reveal only adds new shoppers to the pool who were previously excluded. # The new "source" label Every shopper entering these campaigns now carries a label showing how they were identified: - **Existing:** A shopper you already knew, through login or a submitted email. - **Reveal:** A shopper newly identified through Reveal, who wasn't in your CRM before. This label is available in your CRM, so you can see it, filter by it, and act on it. It doesn't change who receives a campaign; **it just tells you where each contact came from.** You can also ask Ask Chord for these counts directly, broken out by abandonment stage: how many people in a cart or checkout abandonment audience are reachable only because Reveal supplied their email. See [Building abandonment audiences with Ask Chord](docId\:RTCgtU26XJTiT9_fOZdeM). # What you can do with this Using the new source label is **optional**. If you do nothing, Reveal-identified shoppers simply flow into your existing campaigns like anyone else. If you want more control, you can: - Build separate segments for Reveal shoppers vs. everyone else, to compare how each group responds. - Customize messaging, for example a softer, more introductory tone for Reveal shoppers who haven't heard from your brand before. - Adjust send frequency for Reveal shoppers if you want a lighter touch while you build trust with them. - Measure incremental impact, since the label makes it possible to isolate revenue and engagement that Reveal alone made possible. # What we need from you Before Reveal-identified shoppers can receive messages, your team should: 1. Confirm your CRM is set up to create a contact profile from an email address alone (Reveal-matched shoppers won't always have a full customer ID). 2. Confirm there are no filters in place that would block new profiles that lack that customer ID. 3. Make sure Chord Reveal is enabled on your account. Retargeting can only reach these newly identified shoppers if Reveal is turned on. Everything else is optional. Segmenting, custom messaging, and frequency changes can be added later, whenever it's useful to you. # What to expect Reveal is designed to unlock reach and revenue you were previously missing, without adding risk to what's already working: - Previously invisible, high-intent shoppers become reachable. - Your retargeting audience grows. - You gain a way to measure the incremental lift Reveal drives. # Good to know - Reveal currently matches U.S. visitors only. Shoppers outside the U.S. aren't affected and continue to be handled exactly as they are today. - This is an additive change. No existing campaign logic, audience, or suppression rule is being modified or replaced. - To see current abandonment audience sizes, and how many are reachable because of Reveal, ask Ask Chord or see [Building abandonment audiences with Ask Chord](docId\:RTCgtU26XJTiT9_fOZdeM). :::hint{type="info"} Questions about how this applies to your account? Reach out to your Chord team and we'll walk through the details together. ::: [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] 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] 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] 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] Overview [path] Chord Data Platform/ ## Data on Chord ![A diagram of Chord's data infrastructure](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/ZIveIJqNfTYaB6D7yEWKK_data-infrastructure-2.png "Chord's Data Infrastructure") ### 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] Building abandonment audiences with Ask Chord [path] Chord Data Platform/Chord Retargeting/ You can ask Ask Chord for a browse, cart, or checkout abandonment audience in plain language, and get sessions, people, and reachability back without building a Looker explore by hand. It works from Chord's purpose-built abandonment data, which covers closed browsing sessions from the trailing 72 hours, so the numbers reflect a rolling window rather than a fixed report. Ask again a few hours later and expect the counts to move. ## What you can ask Ask in whatever words come naturally. A few examples: - "Who abandoned their cart in the last 72 hours?" - "Build me a checkout abandonment audience." - "What do we have on abandonment audiences right now?" - "What's the Chord Reveal uplift on our cart abandoners?" ## What Ask Chord returns Ask Chord reports three stages side by side, and a session lands in exactly one of them: - **Product abandonment.** Someone browsed and left without adding anything to their cart. - **Cart abandonment.** Someone added an item to their cart but never started checkout. - **Checkout abandonment.** Someone started checkout but never completed it. For each stage, it reports: - Sessions and distinct people. - How many of those people are identified versus anonymous. - How many are reachable by email, counting an email on the customer record even when the session itself carried none. - How many identified people have no email on file at all. - The Chord Reveal uplift: of the people reachable by email, how many are reachable only because Reveal supplied the address, versus how many were reachable without it. This is broken out per stage, not just as one account-wide number. On an account without Reveal, Ask Chord says so and reports the uplift as zero. - How many people bought after abandoning. Ask Chord leaves them out of the audience by default and tells you how many it left out, so a win-back never reaches someone who has already converted. :::hint{type="info"} Example, not a benchmark: one account's 72-hour window turned up 1,430 cart and checkout abandoners, 253 reachable by email, Reveal supplied the address for 82 of those, and 38 people who bought after abandoning were left out. Your numbers will look different. ::: ## Narrowing and saving the audience Ask Chord can narrow the list on request. You can ask for: - A cart value floor. - A specific product sitting in the cart. - Only people with no purchase at all in the last 90 days. - The people who bought after abandoning added back in, if you want them. - One row per person instead of one row per session. - The list ranked by another customer attribute. Ask Chord returns the member list either way. Where the Audiences feature is turned on for your account, tell it to save the list and give it a name. From there it is a custom audience like any other, and syncing it to your marketing tools works the same way. See [Custom Audiences](docId\:XkYKcgelkloN7k--QeSyK). ## Limits to know - The 72-hour window is fixed and can't be widened. Ask about a longer stretch and Ask Chord answers from your event history instead, where identity only exists for shoppers who were logged in at the time. - Email reachability is usually a small slice of any abandonment audience. Most abandoners are anonymous, so plan for channels beyond email if you want to reach the rest. - Ask Chord reports the numbers and the definitions behind them. It doesn't recommend a campaign, a discount, or a send cadence, that part is still up to you. :::hint{type="info"} Questions about how this applies to your account? Reach out to your Chord team and we'll walk through the details together. ::: [title] Custom Audiences [path] Chord Data Platform/Audiences/ # Overview Custom Audiences give brands a quick and easy way to view (and activate) specific customer segments for marketing and beyond. The quickest way to build one is to describe it to **Ask Chord** in plain language. You can also capture one from an explore, or start from a prebuilt template. # How to Create and Activate Audiences from Ask Chord Describe the audience you want in plain language, for example "everyone who abandoned their cart in the last 72 hours with a cart over $50" or "one-time buyers from the last 90 days who used a discount". Ask Chord builds it, tells you how many people are in it and how many are reachable, and you can narrow it in the same conversation. When the list looks right, tell Ask Chord to save it and give it a name. The audience lands in your shared audiences folder alongside the ones built from explores or templates. From there, click "Sync Audience" to send it to Chord Activations exactly as you would for any other custom audience. For what Ask Chord reports on abandonment audiences and how to narrow them, see [Building abandonment audiences with Ask Chord](docId\:RTCgtU26XJTiT9_fOZdeM). # 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 ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-o6TOHc82hlvbTHknmYLEe-20250403-142749.png) ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-B5tsXZ-cCymeEOrvlIC-0-20250403-143047.png) ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-BrwPprBVzAZFWTdE_fJf_-20250403-143729.png) 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" 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" 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] NetSuite [path] Chord Data Platform/Data Sources/Connect Data Sources/ NetSuite is a cloud ERP that manages finance, inventory, and orders for most enterprise brands. Chord ingests NetSuite's general ledger, transaction, and item master data so you can model per-order COGS, landed costs, inventory movements, and revenue attribution alongside the rest of your stack. Chord reads exclusively via SuiteQL, an SQL interface to NetSuite's data, using Token-Based Authentication (OAuth 1.0a). ## What Chord ingests from NetSuite Chord pulls 21 datasets from your NetSuite account. Each dataset becomes its own table in your Chord Snowflake schema. - **Account.** Chart of accounts: account number, name, type, balance, and hierarchy. - **Account type.** Account classification lookup (e.g. Income, Expense, Bank, Fixed Asset). - **Accounting period.** Fiscal calendar: period name, start/end date, closed flag per accounting book. - **Classification.** Classification segment lookup (aka segments or classes in older NetSuite configs). - **Customer.** Customer records: name, identifier, email, billing/shipping address, tax ID, stage. - **Department.** Department segment lookup. - **Employee.** Employee records (full sync per run, useful for payroll joins). - **Entity.** Unified bridge spanning customer, vendor, and employee records: name, type, primary address. - **Item.** Item catalog: SKU, description, item type, cost, pricing, costing method, custom fields. - **Subsidiary.** Legal entity / subsidiary lookup (critical for OneWorld accounts). - **Transaction status.** Transaction-status lookup, scoped per transaction type (e.g. Pending, Billed, Closed). - **Vendor.** Vendor records: name, identifier, email, address, tax ID, payment terms. - **Aggregate item location.** On-hand and available quantity per item and location. Aggregates multiple quantity types (committed, on order, backordered). Use this for inventory snapshot reporting. - **Inventory item locations.** Per-location quantity detail: on hand, committed, backordered, on order. Use this for supply-chain planning. - **Assembly item locations.** Per-location quantity detail for assembly (parent) items. - **Item location availability.** Available quantity per item and location. - **Transaction.** Transaction header spanning all types: sales orders, invoices, cash sales, credit memos, vendor bills, purchase orders, item fulfillments, payment applications, and inventory adjustments. Merged incrementally on last modified date. Includes custom fields. - **Transaction line.** Transaction line detail: quantity, rate, amount, GL account mappings, custom fields. One row per line per transaction. Merged incrementally (cursor is the parent transaction's last modified date). - **Transaction accounting line.** General ledger posting detail per transaction line and accounting book: account, debit/credit amounts, posting date. This is the source for realized COGS and revenue attribution. Merged incrementally. - **Transaction shipping address.** Shipping address snapshot per transaction. Merged incrementally. - **Transaction billing address.** Billing address snapshot per transaction. Merged incrementally. ## Generate a NetSuite API credential set You'll need five values from your NetSuite account: Account ID, Consumer Key, Consumer Secret, Token ID, and Token Secret. All five must be copied from NetSuite together at the time of creation or rotation. Chord uses them to sign OAuth 1.0a requests to the SuiteQL endpoint. Token-Based Authentication (TBA) is the only supported flow. OAuth 2.0 is not available. :::hint{type="warning"} **Heads up:** only NetSuite account administrators or users with the "Setup" permission for Integration and Access Tokens can create these credentials. If your role doesn't include it, ask a NetSuite admin to either generate the credential set for you or grant your user the required permissions first. ::: **1. Enable required features in NetSuite.** Log in to NetSuite as an administrator. 1. Go to **Setup → Company → Enable Features**. 2. Click the **SuiteCloud** tab. 3. In the **SuiteScript** section, check **Client and Server** (if not already enabled). 4. In the **Manage Authentication** section, check **Token-Based Authentication** (if not already enabled). 5. In the **SuiteTalk (Web Services)** section, check **REST Web Services** (if not already enabled). 6. Click **Save**. **2. Create an integration record to get Consumer Key and Consumer Secret.** 1. Go to **Setup → Integration → Manage Integrations → New**. 2. Fill in Name: something like `Chord data sync`. 3. Check **Token-Based Authentication** (if not already checked). 4. Uncheck **Authorization Code Grant Credential Flow** (Chord signs requests directly and does not use callbacks). 5. Click **Save**. 6. On the confirmation page, you'll see **Consumer Key** and **Consumer Secret**. Copy both values immediately. They are shown only once. **3. Create an access token to get Token ID and Token Secret.** 1. Go to **Setup → Users/Roles → Access Tokens → New**. 2. Select the Integration: pick the integration record you just created (e.g. `Chord data sync`). 3. Select the User: the integration user who will own this token (e.g. a dedicated service account). 4. Select the Role: the integration role you'll grant with the permissions below. 5. Click **Save**. 6. On the confirmation page, you'll see **Token ID** and **Token Secret**. Copy both values immediately. They are shown only once and cannot be revealed later. **4. Grant required permissions to the integration role.** 1. Go to **Setup → Users/Roles → Manage Roles** and click the integration role you selected above. 2. Click the **Permissions** subtab. Grant the following Setup permissions: - **Log in using Access Tokens** → Full - **REST Web Services** → Full Grant the following Reports permission: - **SuiteAnalytics Workbook** → Edit. This permission is critical for SuiteQL queries. REST Web Services alone is not sufficient. Grant the following Lists permissions (View level): - **Customers** → View - **Items** → View - **Vendors** → View - **Subsidiaries** → View - **Accounts** → View - **Departments** → View - **Classes** → View - **Locations** → View - **Accounting Periods** → View - **Inventory** → View Grant the following Transactions permissions (View level): - **Sales Orders** → View - **Invoices** → View - **Cash Sales** → View - **Credit Memos** → View - **Customer Payments** → View - **Item Fulfillments** → View - **Vendor Bills** → View - **Purchase Orders** → View - **Item Receipts** → View - **Adjust Inventory** → View 3. Click **Save**. **5. For OneWorld accounts, ensure all-subsidiary access.** If your NetSuite account uses multiple subsidiaries (OneWorld): 1. Go to **Setup → Users/Roles → Manage Roles** and click the integration role. 2. Under the **Subsidiary Restrictions** setting, choose **All** (or **Selected** with all target subsidiaries checked). If left at the default **User Subsidiary**, Chord will silently ingest only the integration user's assigned subsidiary and miss all others. 3. Go to **Setup → Users/Roles → Manage Users**, click the integration user, and confirm under **Subsidiary Restrictions** that they also have access to **All** target subsidiaries. 4. Click **Save**. ## Connect the credential set in Chord 1. Open Chord Hub and go to **Data Sources → Add Source**. 2. Pick **NetSuite** from the data source list. 3. Enter your Account ID in the **Account ID** field. Format: production = `1234567`, sandbox = `1234567_SB1` (underscore before the SB suffix, not hyphen). 4. Paste the Consumer Key you copied into the **Consumer Key** field. 5. Paste the Consumer Secret you copied into the **Consumer Secret** field. 6. Paste the Token ID you copied into the **Token ID** field. 7. Paste the Token Secret you copied into the **Token Secret** field. 8. Click **Save**. Chord will make a test SuiteQL query against your NetSuite account to confirm all five values are correct and the integration role has the required permissions. This validation happens immediately on save. 9. If validation passes, the first sync kicks off automatically. Subsequent syncs run on your tenant's standard ingestion schedule. If validation fails, you'll see an error message with details on what's missing or misconfigured (see troubleshooting below). ## Troubleshooting **The credential validation failed with a 400 error. What does the error detail text say?** NetSuite returns HTTP 400 with status `INVALID_PARAMETER` for both authentication failures and permission problems. The error message body contains a detail field that tells you which one. Look for one of these two messages: - **"SuiteAnalytics Workbook feature has been disabled"** → The feature is turned off account-wide. Fix: Go to **Setup → Company → Enable Features**, click the **SuiteCloud** tab, and check **Analytics** in the SuiteAnalytics section. Save and retry the Chord validation. - **"Your current role does not have permission to perform this action"** → The feature is on, but the integration role is missing the SuiteAnalytics Workbook permission. Fix: Go to **Setup → Users/Roles → Manage Roles**, click the integration role, click **Permissions**, find **Reports**, and grant **SuiteAnalytics Workbook → Edit**. Save and retry the Chord validation. These two failures look identical from the HTTP status code alone, but the detail text tells you which one you're facing and where to fix it. **The validation failed with **`INVALID_LOGIN`**, but my credentials look right to me. What's the most likely cause?** The most common cause (especially if this credential was working before) is that you rotated your access token or consumer credentials but didn't update all five fields in Chord at the same time. NetSuite returns `INVALID_LOGIN` whenever the signature doesn't match, whether the cause is a typo, a revoked token, or (most commonly) a partial update. The error text itself won't tell you which, so check for a partial update first. When you regenerate a token in NetSuite, you get new Token ID and Token Secret values. When you regenerate consumer credentials, you get new Consumer Key and Consumer Secret values. If you paste only some of the new values into Chord while others remain stale, the OAuth signature will fail. The signature requires all five pieces to match exactly as they stand together in NetSuite at that moment. Updating four fields and leaving one stale breaks the connection. Always copy all five values fresh from NetSuite (Account ID, Consumer Key, Consumer Secret, Token ID, Token Secret) and paste them all into Chord at once, then save. Chord validates all five together immediately on save. **I copied the values but validation still fails. Should I check for hidden whitespace?** Yes. Consumer Key, Consumer Secret, Token ID, and Token Secret are long strings that are easy to copy with leading or trailing whitespace, which breaks the signature. Paste each field into Chord, then manually check that there are no spaces at the very start or end of the value. NetSuite's credential display pages sometimes add whitespace when you select the text. Clear it before pasting. If you're still stuck, generate fresh credentials in NetSuite and retry. You may have copied partially or with an invisible character. **Do NetSuite TBA tokens expire?** No. Access tokens remain valid indefinitely unless you explicitly revoke or regenerate them in NetSuite. If a working credential suddenly fails, check that the token has not been revoked under **Setup → Users/Roles → Access Tokens**. Also check that the integration user and role have not been disabled. TBA tokens do not time out, but they break if the user account or the role is deactivated. **How do I rotate the credential set?** 1. In NetSuite, regenerate the access token: go to **Setup → Users/Roles → Access Tokens**, click the token, and click **Regenerate Token**. This produces a new Token ID and Token Secret. 2. At the same time, go to **Setup → Integration → Manage Integrations**, click your integration record, and regenerate the Consumer Key and Consumer Secret: click **Regenerate Credentials**. 3. Copy all five values: Account ID (unchanged), plus the new Consumer Key, Consumer Secret, Token ID, and Token Secret. 4. In Chord, open the same NetSuite credential entry, paste all five values (replacing what's there), and click **Save**. Chord validates the new set immediately on save. 5. Once validation passes and the next sync runs cleanly, you can delete the old token and integration record in NetSuite. **I'm only seeing data from one subsidiary but we have multiple. What's happening?** This is a OneWorld scope issue. By default, the integration role's **Subsidiary Restrictions** are set to **User Subsidiary**, which silently filters all SuiteQL responses to only that subsidiary. NetSuite returns no error for out-of-scope rows. It just excludes them. Check the role and integration user's **Subsidiary Restrictions** (as described in step 5 of the credential setup above) and set them to **All** to access every subsidiary. Then kick off a new Chord sync. *** **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 (or screenshot). We'll trace the request against your NetSuite account and tell you what's missing or misconfigured. [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] 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] 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] 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] 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. ![](https://archbee-image-uploads.s3.amazonaws.com/lGdX_fn_gYcg4afmFCucz-Q4KMOUDhq4ha8YJo6UCC2-20250417-215456.png) 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] 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] 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] 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] Attentive [path] Chord Data Platform/Data Sources/Connect Data Sources/ Attentive is a mobile messaging platform for SMS and email campaigns. Connecting it to Chord brings your subscribers, message sends, and engagement events into your warehouse, so SMS and email performance sits next to your orders, sessions, and other paid channels. To connect, you create an app in Attentive, generate an API key, and share the key with Chord. The steps below cover all three. ## Attentive is webhook-only Attentive does not offer an API to read your message history. It only pushes events out as they happen, through webhooks. That has one consequence worth planning around: Chord can only capture Attentive events from the day your webhook is registered forward. Sends, clicks, and opt-ins from before that date are not retrievable through the API and will not appear in your warehouse. If you need historical subscriber data, Attentive can export subscriber details for a segment from its own UI as a one-time file. Ask your Chord contact if you want that loaded alongside the live event feed. ## Generate an Attentive API key You need an Attentive user with access to the integrations page. If you cannot see it, ask your Attentive account admin. 1. Log in to Attentive. 2. Go to **Integrations**. 3. Click **+ Create App** in the top right. 4. Set **App name** to `Chord`. 5. Set **Contact email** to your own email address. 6. Under **Permissions**, every API starts at **No Access**. Set **Webhooks** to **Write** and leave the rest at **No Access**. 7. Click **Create**. The **Copy API key** modal appears. 8. Click **Copy**, then paste the key somewhere safe before you close the modal. Attentive shows the API key **only once**. Attentive's own wording: "This is the only time you will be able to copy this API key." If you close the modal without copying it, regenerate the key from the app on the integrations page and copy the new one. Attentive offers only **No Access** or **Write** for each API. There is no read-only level, so **Write** on Webhooks is the minimum that works. ## Turn on event webhooks The key alone is not enough. The app also has to be allowed to send events. 1. On the integrations page, select the app you just created. 2. Open the **Settings** tab, then the **Webhooks** tab. 3. Set **Event Webhook Status** to **ON**. 4. Under **Subscribe to event notifications**, select **Subscription webhook**. Chord registers the specific events it needs once it has your key. You do not pick events yourself. ## Share the key with Chord Send the key to your Chord contact or to [help@chord.co](mailto\:help@chord.co) over your agreed secure channel. Do not put it in a plain email or a public Slack channel. Treat it like a password. Anyone holding it can send messages from your Attentive account. Chord verifies the key with a single authenticated call to Attentive, registers the webhook, and confirms back to you. Events start arriving from that point. The key is encrypted at rest and is never shown again in the Chord UI. ## What Chord receives Once the webhook is live, Chord captures these events as they happen: - **Subscriptions.** SMS and email opt-ins and opt-outs. - **Sends.** SMS and email messages sent, with message and campaign identifiers. - **Engagement.** Email opens, and link clicks on both SMS and email. - **Inbound.** Replies your subscribers send back over SMS. - **Attributes.** Custom subscriber attributes as they are set. ## Troubleshooting **Chord says the key is invalid.** Confirm you copied the full value from the modal with no missing characters and no trailing space. If you regenerated the key in Attentive after sending it, send the new one. **The key works but no events arrive.** Check the app on Attentive's integrations page. **Webhooks** must be **Write**, and **Event Webhook Status** must be **ON** under Settings then Webhooks. Changing either takes effect without a new key. **I connected today. Where is last quarter's data?** It does not exist to fetch. See the webhook-only section above. Nothing before your webhook registration date is available through the Attentive API. **Do Attentive API keys expire?** No. A key stays valid until you regenerate it or delete the app. **How do I rotate the key?** Regenerate it on the app on Attentive's integrations page, copy the new value, and send it to Chord. The old key stops working the moment you regenerate, so events pause until Chord has the new one. Tell your Chord contact before you rotate so the gap stays short. **My Attentive plan has no integrations page.** API access is not enabled on every Attentive plan. Contact Attentive support to turn it on, then start at step 1. *** Stuck on a step? Email [help@chord.co](mailto\:help@chord.co) with the exact error text and we will trace it. [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] 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 ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/fohRkFTuxg-_LMR9yaZy6_sso-hub-diagram-2.jpg) ## 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 ![Sequence Diagram](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/s7J_FQCyUWvkI4ehlQHMl_sso-hub-diagram-5.jpg) # 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: ![View SAML setup instructions](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/1Au_R3GeO-Xf_LxJsGzsH_image.png) 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**: ![Assignment button](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/Hvt5cW-5eyAsG7pajO2Fb_image.png) ## 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 Context [path] AI features/ # Introduction ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-zPTxv9KUQixj52c3V58cI-20250910-152227.png) 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, Ask Chord 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 Ask Chord 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 ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/LBWVPPXwlhq3dTTpiqWBP-20250919-173838.png) The **Instructions** feature 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 Ask Chord 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 ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/R91aHF4uETf2aTa0gnD6B-20250919-173806.png) **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?", Ask Chord 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] 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] 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] Ask Chord Use Cases [path] AI features/Ask Chord/ 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 Ask Chord, 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 do with Ask Chord | Ask Chord 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 | | 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 | # Core use cases ## For technical stakeholders ### Accelerating data model deployment **What it is ** Ask Chord 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 Ask Chord 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** Ask Chord’s Context Studio lets technical teams embed business rules, definitions, and formatting instructions directly into Ask Chord, 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. ## For marketers ### Keeping customers coming back **What it is** Chord 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, Ask Chord 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. Ask Chord 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, Ask Chord 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 ** Ask Chord 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** Ask Chord 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 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] 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] 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** ![Create a new app ID or connect an existing app](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/0Pj9TAN_EVWEsCCflhAty_image.png) ![Select the "Other" Use Case](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/lOMFs4mNpwJzF1c8KDThp_image.png) - Then fill out the relevant details and press **Create App** ![Add app details](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/97f2EyNgOgrMTec2imc5O_image.png) - 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. ![Generating a system user](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/eIkIE1bUcEHojUtGQ44S0_image.png) - 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. ![Granting full access to relevant ad accounts](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/sT-AyUbs64NfQyMcHnNxS_image.png) ![Granting ad account access](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/1-o--EA60TV9KOdsFdPGy_image.png) - 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. ![Generating a token](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/em80DRYYfM0_zy_jFGx3Z_image.png) ![Set the app for token generation](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/PH1qEKvX_5HrfxrjFeOvW_image.png) ![Set the expiration for token generation](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/RknfY7qUWbaet9IunfFrX_image.png) ![Set the permissions for token generation](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/j4w5hsGxWBixyWLblLtWQ_image.png) ![Collect & save your token](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/en1I5bop5KBvWo4LdfBxH_image.png) - 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] 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] 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] 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] 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. - [Okendo](docId\:DK3s74A3djXbiGYwktaHA)**:** A reviews, ratings, and user-generated content platform for ecommerce brands. - **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. - [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: ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-LZQfvH1jdHOBmK7x-r3LG-20250725-214022.png) 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.** ::: ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-GVLRPpu1qIluWW7rp_7UP-20250725-213921.png "Data Sources Homepage") ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV--c_tIPXiT9qdG8zC3IdFv-20250725-213939.png "Data Sources Connector Catalog") 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 ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-xM6NRhqrn_Zqw19eVTHYE-20250725-213901.png) 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] 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] 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] 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] 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] Chord MCP [path] AI features/ # Try Chord MCP in Claude Desktop Chord MCP turns Claude into a data analyst for your store. Once it's connected, you can ask questions like *"how many returning customers viewed a cart before purchasing?"* in plain English, and Claude pulls the answer straight from your Chord warehouse, writing and running the SQL for you behind the scenes. This guide walks you through connecting Chord MCP to **Claude Desktop** in about five minutes. No coding required for the recommended path; a more technical setup is covered at the end for engineers who want it. **What you'll need** - A Claude account (Free, Pro, Max, Team, or Enterprise) with **Claude Desktop** installed - A Chord account with access to your organization's data - About 5 minutes :::hint{type="info"} **For best results, use Claude Opus (or the most capable model available on your plan).** Answering a data question involves multiple steps behind the scenes: searching your schema, checking saved queries and org conventions, drafting SQL, and validating it before running. More capable models complete these steps faster and more reliably, especially for complex questions like cohort analysis, churn breakdowns, or year-over-year comparisons. Smaller models handle simple lookups well but may time out on multi-step queries. To change your model, use the model picker near the message box and select Opus before starting your conversation. ::: ## What is Chord MCP? MCP (Model Context Protocol) is an open standard that lets AI assistants like Claude connect securely to outside tools and data. Chord MCP is our hosted MCP server: it gives Claude a safe, read-only window into your Chord data warehouse. When you ask a data question, Claude uses Chord MCP to: - Look up the right tables and saved queries in your warehouse - Apply your organization's conventions (how you define revenue, which test orders to exclude, and so on) - Write the SQL, run it, and explain the answer back to you You stay in control the whole time. The connection is **read-only.** Claude can look at your data and answer questions, but it can't change or delete anything. ## Set up Chord MCP (recommended path) The easiest way to connect is through Claude's built-in **Custom Connectors**. This works entirely in the Claude interface — no terminal, no config files. :::BlockQuote **A note for Team and Enterprise plans:** Only an organization **Owner** can add a custom connector for the whole org. If you're on a Team or Enterprise plan and don't see the option to add one, ask your Claude workspace Owner to add Chord MCP first (using the steps below), then skip to step 3. ::: ### 1. Open your Connectors settings In Claude, go to **Settings → Connectors**. - On **Pro or Max** plans, this is under **Customize → Connectors**. Click the **"+"** button, then **"Add custom connector."** - On **Team or Enterprise** plans, an Owner adds it under **Organization settings → Connectors** → **"Add"** → hover **"Custom"** → select **"Web."** ### 2. Add the Chord MCP server URL When prompted for the remote MCP server URL, enter: :::BlockQuote \ ::: Leave the optional Advanced settings (OAuth Client ID / Secret) blank - you don't need them. Click **"Add."** ### 3. Connect and sign in Find **Chord** in your list of connectors and click **"Connect."** A browser window opens for you to sign in to Chord and approve access. This is a standard OAuth sign-in; Claude never sees your password, and you can revoke access anytime from your connector settings. Once you've approved, you're connected. ✅ ### 4. Turn it on in a conversation Start a new chat. Click the **"+"** (or **"Search and tools"**) button near the message box, choose **Connectors**, and make sure **Chord** is toggled on for the conversation. ## Ask your first question Type a question in plain English. Claude will recognize it as a data question and use Chord MCP automatically. Try one of these: - *"How many orders did we have last month?"* - *"What was our gross revenue in Q1, broken down by month?"* - *"Show me our top 10 products by revenue this year."* - *"How many new customers did we acquire last quarter versus the quarter before?"* - *"What's our average order value over the last 90 days?"* Behind the scenes, Claude finds the right tables, applies your warehouse conventions, writes the SQL, runs it, and explains the result, usually citing which tables and definitions it used so you can trust the number. :::BlockQuote **Tip:** The more specific you are, the better. "Gross revenue" and "net revenue" can mean different things — say which one you want, and Claude will use the matching definition. ::: ## What Claude can do with Chord MCP Once connected, Claude has a toolkit for working with your warehouse. You don't need to call these directly since Claude picks the right ones but here's what's happening under the hood: | **Capability** | **What it does** | | ----------------- | --------------------------------------------------------------------------------------------------- | | **Run query** | Executes the read-only SQL and returns the rows. | | **Search schema** | Discovers which tables exist in your warehouse and what they contain. | | **Saved views** | Checks whether a trusted, pre-built query already answers your question. | | **Past queries** | Finds similar questions you've asked before as examples. | | **Instructions** | Applies your org's standing rules (revenue definitions, test-order exclusions, segmentation logic). | | **Documentation** | Answers "how do I…" questions about Chord itself. | | **Preview table** | Peeks at a few rows of a table for a quick sanity check. | | **Tenants** | Lets you see and switch between Chord organizations you belong to. | :::BlockQuote **Working across multiple organizations?** If you have access to more than one Chord org, just ask Claude something like *"switch to the \[org name] organization"* and it will route your questions to that warehouse for the rest of the conversation. ::: ## Troubleshooting **Which Claude model should I use?** For the best experience, we strongly recommend Claude Opus (or the most capable model available on your plan) when working with Chord MCP. Answering a data question isn't a single step. Behind the scenes, Claude searches your schema, checks saved queries and your org's conventions, drafts the SQL, validates it, and sometimes revises it before running. Complex questions like cohort analysis, churn breakdowns, and year-over-year comparisons can take many of these steps, and more capable models complete them in fewer, faster passes. Smaller models like Sonnet handle simple lookups well ("how many orders did we have last month?"), but on multi-step analytical questions they may take longer or time out before reaching an answer. To change your model in Claude, use the model picker near the message box and select Opus before starting your conversation. **My question times out or never finishes** Complex analytical questions involve several rounds of schema lookup, SQL drafting, and validation. If you're seeing timeouts, switch to Claude Opus using the model picker near the message box. It resolves ambiguous questions in fewer steps. Breaking a big question into smaller ones ("first show me cancellations by week, then break down the top week by reason") also helps on any model. **Claude isn't using Chord / says it can't reach the data.** Make sure the Chord connector is toggled **on** for your current conversation (the "+" or "Search and tools" menu). Connectors are enabled per chat. **The connector won't connect.** Chord MCP connects from Claude's cloud, not from your laptop, so `https://mcp.chord.co/mcp` needs to be reachable over the public internet. This works out of the box for the hosted Chord endpoint. If your team runs Chord behind a corporate firewall or VPN, your network admin may need to allowlist Anthropic's IP ranges. **I signed in but still get permission errors.** Your Chord account needs access to the organization's data. Confirm with your Chord admin that your account has the right permissions, then disconnect and reconnect the connector. **I need to change the connection.** To edit a custom connector, remove it (Connectors settings → the three-dot menu → **Remove**) and add it again with the updated details. ## Advanced: connect via config file (for engineers) If you'd rather wire Chord MCP up through Claude Desktop's local configuration instead of the Custom Connectors UI, you can. This uses the mcp-remote shim to bridge Claude Desktop to the hosted server. :::BlockQuote **Requirements:** Node.js (for npx) and, for the script below, jq. macOS and Linux only. ::: **Option A — one-line installer.** Run: :::BlockQuote curl -fsSL \ | bash -s -- --client claude-desktop ::: This merges a Chord MCP entry into your claude\_desktop\_config.json. Then fully quit Claude Desktop (**Cmd+Q** on macOS) and reopen it. The first connection opens a browser for OAuth sign-in. **Option B — edit the config by hand.** Open your Claude Desktop config file: - **macOS:** \~/Library/Application Support/Claude/claude\_desktop\_config.json - **Linux:** \~/.config/Claude/claude\_desktop\_config.json Add Chord under mcpServers: :::BlockQuote \{ "mcpServers": \{ "ask-chord": \{ "command": "npx", "args": \["-y", "mcp-remote", "\"] } } } ::: Save the file, fully quit and reopen Claude Desktop, and complete the browser sign-in on first connect. :::BlockQuote **Heads up:** The local config-file method (claude\_desktop\_config.json) is a separate mechanism from Custom Connectors and is specific to Claude Desktop. For most people, the recommended Custom Connector path is simpler and also works in Claude on the web and Cowork. ::: ## Questions? Reach out to your Chord contact or email [help@chord.co](mailto\:help@chord.co) and we'll help you get connected. [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] 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] Gorgias [path] Chord Data Platform/Data Sources/Connect Data Sources/ Gorgias is a customer support and helpdesk platform built for ecommerce brands, unifying email, chat, social, and SMS conversations into one inbox. Connecting Gorgias to Chord brings your support history into the same warehouse as your orders, customers, and marketing data, so ticket volume, response times, and CSAT can be analyzed alongside everything else your brand tracks. ## What Chord ingests from Gorgias Chord pulls 12 datasets from your Gorgias account. Each dataset becomes its own table in your Chord Snowflake schema. - **Tickets.** Every support ticket, including channel, subject, status, assignment, and tags. - **Messages.** Every message tied to a ticket, with sender and timestamp. - **Customers.** Contact records from Gorgias, including name and email. - **Satisfaction surveys.** CSAT ratings and comments left on resolved tickets. - **Tags.** The tag library used to label and filter tickets. - **Users.** Agent accounts in your Gorgias workspace. - **Teams.** The team groupings tickets can be assigned to. - **Integrations.** The third-party apps and channels connected to your Gorgias account. - **Macros.** Saved canned responses. - **Rules.** Automation rules configured in Gorgias. - **Views.** Saved ticket views and filters. - **Events.** Account activity events, pulled with a 30-day lookback on the first sync. Once your connector is live, ask your Chord contact to enable the Gorgias Tickets explore and the prebuilt Gorgias Support Showcase dashboard in Analytics. :::hint{type="info"} **Heads up:** Tickets, messages, customers, and events sync incrementally, picking up only what changed since the last run. Satisfaction surveys, tags, users, teams, integrations, macros, rules, and views resync in full every run. ::: ## Generate a Gorgias API key You'll need three things from Gorgias: your account subdomain, the email address of the Gorgias user the key belongs to, and a REST API key generated from that user's account. There's no scope picker. One key grants access under that user's own permissions. :::hint{type="warning"} **Heads up:** Only account owners and admins can generate a REST API key in Gorgias. If you're on another role, ask an admin on your team to create the key or grant you access first. ::: 1. Log in to your Gorgias helpdesk. 2. Click the **Settings** icon in the bottom-left corner, then go to **Account → REST API**. 3. Under **Password (API Key)**, click **Create API Key**. The key is generated immediately and shown alongside your base API URL and username. 4. Copy the key. It stays visible on the REST API page, so you can come back for it later. The **Reset** button next to it generates a new key and invalidates the old one immediately, so only use it when you mean to rotate. 5. Note the subdomain from your Gorgias URL (the part before `.gorgias.com`) and the email address of the account you generated the key under. You'll need both to connect in Chord. ## Connect the key in Chord 1. Open Chord Hub and go to **Data Sources → Add Source**. 2. Pick **Gorgias** from the data source list. 3. Enter your Gorgias account subdomain in the **Account Subdomain** field. Use just the prefix, for example `yourbrand` for `yourbrand.gorgias.com`, not the full URL. 4. Enter the email address of the Gorgias user who owns the key in the **User Email** field. 5. Paste the key into the **API Key** field. 6. Click **Save**. Chord makes a test call against `https://.gorgias.com/api/account` to confirm the credentials work. 7. The first sync kicks off automatically and backfills your ticket, message, and customer history. From there, Gorgias syncs on your tenant's standard ingestion schedule. ## Troubleshooting **What does the validate step actually check?** Chord sends a `GET` request to `https://.gorgias.com/api/account` using HTTP Basic auth with the email and API key you entered. A `200` response means the credentials are valid and the connection saves. No ticket or customer data is pulled or stored at this stage. It's a connectivity check only. **The validate step failed. What now?** Check that the subdomain field holds just the prefix, `yourbrand`, not the full URL and not a trailing slash. Confirm the email matches the Gorgias user the key was generated under, not a different teammate's account. If both look right, someone may have clicked **Reset** in Gorgias since you copied the key. Open **Settings → Account → REST API**, copy the current value, and paste it into Chord. **Do Gorgias API keys expire?** No. A key stays valid until someone clicks **Reset** next to it in Gorgias. That invalidates the old key at once, and syncing stops until the new one is saved in Chord. **How do I rotate the key?** In Gorgias, go to **Settings → Account → REST API** and click **Reset** next to **Password (API Key)**. The old key stops working the moment the new one appears, so paste the new value into the same Gorgias credential entry in Chord Hub and click **Save** right away to keep the gap short. **How does Gorgias data connect to my order and customer data?** Chord matches Gorgias contacts to your store's customer records by email, lowercased and trimmed on both sides, inside the Gorgias Tickets explore. A contact with no email on file, or one who's never placed an order, won't have a match. Gorgias doesn't carry an order reference, so there's no direct ticket-to-order join, only the email-based customer match. The explore includes a **Has Matching OMS Customer** field under the Customer group, so you can filter to matched contacts or see unmatched tickets as a known gap instead of blank customer attributes. "No" covers both contacts who never ordered and contacts whose Gorgias record has no email to match on. **Why does my raw ticket count look higher than the support volume I'd expect?** Not every row in the tickets table is a genuine support request. Review-platform notifications, social mentions, and other automated messages can land in Gorgias as tickets alongside real customer conversations, depending on how your team has Gorgias configured. If you're using ticket counts as a proxy for support volume, check the `channel` and `via` fields on each ticket to see how it actually arrived, rather than relying on total row count alone. :::hint{type="info"} **Need help?** If you hit a credential or connectivity issue you can't resolve on the platform, 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] 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] Analytics Glossary [path] Chord Data Platform/Analytics Features/ This page lists terms used on our Analytics platform. ## A - **Admins** have a variety of options for limiting what users can view and interact with in Looker. - A **data** **action** lets users perform tasks in other tools, directly from Looker. For example, the action can cause an email to be sent or can set values in other applications — or it can do anything else that you can configure a receiving server to do. The receiving server must be able to accept a JSON POST. - An **advanced filter **lets users create a dashboard filter with a field from an Explore that is not represented on the dashboard itself. - **Alerts** enable users to specify conditions in the data of a dashboard tile that, when met or exceeded, trigger a notification to be sent at the desired frequency to specific recipients. Alerts are set on query-based or Look-linked tiles on user-defined dashboards, LookML dashboards, and legacy dashboards; and they can be sent through email or with Looker's Slack or Slack Attachment (API Token) integrations. - **Application Time Zone** is an admin setting for the default time zone in which scheduled Looks and queries run, where supported. When User Specific Time Zones are enabled, the Application Time Zone becomes the default time zone for users who do not have a time zone value set for their accounts. - An **asynchronous** (or async) query is a data request that makes one call to start the request, one or more calls to check the completion status of the query, and one call to fetch the results of the completed query. Async queries can help avoid freezing apps, connection timeouts and long dashboard load times. ## B - A **base view **is the view used as the starting point for building an Explore. From there, you can join other views into the base view to be used in the Explore. Typically, Explores are named after the base view, but you can also use the `from` parameter to name the Explore's base view if you don't want to name the Explore after its base view. - Looker **Blocks** are pre-built pieces of LookML that you can use and customize to your exact specification. From optimized SQL patterns to fully built-out data models, blocks can be used as a starting point for quick and flexible data modeling in Looker. - A **board** holds a collection of manually curated dashboards, Looks, and links. Dashboards and Looks, which are stored in folders, can be pinned to multiple boards. Boards may include links and descriptions to provide context and can make it easier for users to find the information that is most relevant to them. - **Browsing** involves viewing, sharing, sending, and downloading data from dashboards, Looks, and Explores. ## C - Formerly known as Discourse, the **Looker Community** is a user forum featuring posts, discussions, questions, and ideas shared among Looker users and experts. - Looker **components** are the technical implementation of the Looker Design System, built with React, TypeScript, and Styled Components. They consist of UI components, filter components, and visualization components. - In the Admin section of Looker, you establish the database **connection** from which a model will retrieve data. - **Constants**, which are defined with the LookML `constant` parameter in a project manifest file, let you specify a value that can be reused throughout a project. You can reference constants anywhere in your model where strings are accepted. - In Looker's documentation, the term **content** typically refers to Looks and dashboards. - **Content** access controls whether a user or group can view or make changes to a board, or to a folder (called a Space prior to Looker 6.20) and its contents. The two content access levels are **View** and **Manage Access, Edit**. - **Cross-filtering** lets users apply ad hoc filters to dashboards that use the new dashboard experience. With cross-filtering, users can click a data point in one dashboard tile to have all dashboard tiles automatically filter on that value. Specific cross-filters cannot be saved to a dashboard, but they can be shared by sharing a cross-filtered dashboard's URL. ## D - A **dashboard** is essentially a collection of one or more saved queries, displayed as visualization or text tiles together on one page. Looker offers two types of dashboard experience: new dashboards and legacy dashboards. - **Data access **controls which data a user or group is allowed to view. This type of access can be restricted or granted either at the user level or at the data level. - A **dimension** is a field that represents an attribute, fact, or value, which can be selected from the field picker within an Explore and can be used to filter a query. Common dimensions include such attributes as dates, names, and IDs, and often correspond to columns in your underlying data table. A dimension can also be created within a view file. - Dimension fill is a feature that lets you instruct Looker to fill in missing dates or values for a given dimension, such as a **date dimension** with some years missing. You can avoid misleading graphs by preventing Looker from connecting the values in an incomplete set. The dimension fill option can be turned on or off with the `allow_fill` parameter. - Using a [dimension group](https://cloud.google.com/looker/docs/reference/param-field-dimension-group), you can create multiple dimensions for a single underlying date or time column in the database. For example, you could split a `duration`-type dimension group into intervals of days, weeks, months, and so on. - Looker makes it possible to **drill** into the data on a visualization or an Explore to get more specific information about a specific data point. To drill into data on a visualization, select the part of the visualization about which you'd like more information. For the **Data** section of an Explore, select the value of a measure, or select the value of a dimension that can be drilled into. ## E - An **element** is a tile or visualization on a LookML dashboard, created using the `element` parameter - Explore (*n.*) - An **Explore** is the starting point for queries. An Explore shows a specified set of fields from its associated view file, and these fields can be selected from the field picker to construct a query, which can be saved as a Look or dashboard tile. Explore URLs can also be shared. - explore, exploring (*v.*) - **Exploring** involves using data to answer questions in Looker. - An **Explore file **is a LookML project file with the extension `.explore.lkml`. Can be used for extending Explores across models and for defining native derived tables. - The `explore`** **parameter adds a view to Looker's menu of Explores. As a best practice, an Explore should be defined inside of a model file. Explores reference views and each Explore can contain joins to other views. An Explore can also be defined in an Explore file that is then included in a model file. - **Extensions** are web applications built with Looker components that are developed through the **Looker extension framework**. ## F - A **fanout** occurs when one row of a primary data table can correspond to more than one row of a joined table, resulting in duplicated records and incorrectly calculated aggregations. In Looker, the fanout problem is avoided through the use of symmetric aggregates and by correctly defining the dataset's primary key. - **Feature acces**s controls the types of actions a user is allowed to take in Looker. This type of access is managed by permission sets. - Explores and views contain **fields**, mostly dimensions and measures, which are the fundamental building blocks for Looker queries. - **Filter** **expressions** are an advanced way to filter Looker queries. You can use them in the Explore section of Looker by adding a filter and choosing the **matches (advanced)** option. They are also used in LookML for elements that take a `filter` parameter. You can write filter expressions to filter on a string or to partially match strings, date and time, Boolean values, numbers, and location fields. - In the Looker UI, a **folder** is a place where dashboards, Looks, and other folders (subfolders) are stored. Each user has a personal folder, and a Looker instance can also have various kinds of shared folders. Access to content in Looker is allocated at the folder level. **Folders** were called "Spaces" prior to Looker 6.20. - In the Looker IDE, a **folder** is an organizational structure for your LookML files. - **Looker functions** let you transform your data or reference data in complex ways. They are similar in nature to Excel functions. ## G - Users can be added to one or more **groups**. **Groups** are useful for managing users' access to particular data, features, and content within Looker, as well as for assigning roles to users in bulk. ## J - **(*****n.*****)** The `join` parameter lets you define the **join** relationship between an Explore and a view, so that you can combine data from multiple views. You can join in as many views as you like for any given Explore. - **(*****v.*****)** Combine data from multiple views by defining the relationship between an Explore and a view through a `join` parameter. ## L - **Look** is a single table or visualization saved as its own individual report. Looks can be added to dashboards, scheduled, shared, and made public. Any changes made to a Look will be reflected in any dashboards that contain it. - Table calculations, custom fields, and custom filters rely on Lo**oker expressions** (Lexp) to perform calculations. A Looker expression is built from a combination of functions, operators, and fields, and possibly constants or variables - **LookML **is a language for describing dimensions, aggregates, calculations and data relationships in a SQL database. The Looker app uses a model written in LookML to construct SQL queries against a particular database - A LookML dashboard is [written entirely using LookML](https://cloud.google.com/looker/docs/reference/lookml-dashboard-overview) (as opposed to a user-defined dashboard, which is created by using the visualization editor). ## M - A measure is a field in an Explore that represents measurable information about your data, such as sums, counts, and so forth. A measure is declared in a view file and can be of an aggregate or non-aggregate type - The **Merged Results **feature lets you combine data from different Explores (even from different models, projects, or connections). Using the Merged Results feature, you can create a query from an Explore, then add queries from other Explores to display the merged results in a single table. The Merged Results feature performs similarly to a left join in SQL: it's as if the added query is being left-joined into the primary query - The **metadata** panel in the Looker IDE shows contextually relevant information for a LookML object. For example, if your cursor is on a `view` parameter in the IDE, the metadata panel will show you which Explores have that view joined in and other views that are extensions of that view. ## P - Admins can manage **permissions** to determine which users and groups can access content, data, and features. Permissions can be model-specific or instance-wide. Permission sets must be used as part of a role to have any effect - The **primary key **is the dimension that has exactly one unique value for each row of data. When data tables are joined together in a one-to-many relationship, the primary key must be defined correctly in order to avoid a fanout - A **primary quer**y is a single query created from a single Explore. When working with merged results, the primary query is a similar concept to the primary ID when joining multiple tables in SQL - In Looker, a **project** is a set of related models and other files (like Explores, views, and LookML dashboards) that you will use to define your data model. In general, a project corresponds to a single Git repository. ## R - A **role** defines the privileges that a user or group will have for a specific set of models in Looker. Create a role by combining one model set with one permission set. ## S - A Space is a folder where dashboards, Looks, and other Spaces (subspaces) are stored. Each user has a personal Space, and a Looker instance can also have a variety of shared Spaces. Access to content in Looker is allocated at the Space level. Spaces are also known as **folders** - A **SQL-based** derived table is a derived table that has a query defined with a SQL query, referring to columns in your database. SQL-based derived tables can be temporary or persistent. ## T - **Table calculations** are similar to spreadsheet formulas and are performed on the results of a query, after the query has executed - **Themes** are a way to customize the appearance of your embedded Looker dashboards and Explores. You can use themes to customize font family, text color, background color, tile color, and other visual elements - **Tiles** are visualizations that are added to a dashboard from an Explore or a Look. **Tiles** can be query-based or Look-linked. Query tiles differ from Look-linked tiles because they are stored only on dashboards. ## U - By **unsubscribing**, users can choose to stop receiving scheduled content deliveries and alert notifications. The consequences for unsubscribing differ depending on how the delivery is set up - **User Specific Time Zones **is an admin option that, when enabled, lets users choose their own time zones. Queries will be created with the time zones of the users who created them - **User-defined dashboards** are created by adding content through Looker's user interface, rather than using LookML. This is the most common type of dashboard. ## V - In Looker, a** view **can represent an underlying database table or a derived table. Views are the building blocks for Explores, which make the information in a view available for querying with the field picker in the Explore UI. By convention, a view is defined in a view file. - **A view file** is where you define the dimensions, measures, and other fields that are used in your LookML model. - **Visual drilling** is supported by dashboards using the new dashboard experience. To enable visual drilling, LookML developers customize a drill visualization using the `link` parameter. Dashboard viewers can select whether to view the custom visualization or a data table by clicking buttons at the top of the drill window. [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] Line Items [path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Shopify/ ### x\_fct\_trans\_line\_items | 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. | | First Fulfillment Id | Unique identifier for a Shopify Fulfillment at a specific point in time | | First Fulfillment Oms Fulfillment Id | Unique key generated by Shopify that identifies a fulfillment. | | First Fulfillment Shipment Status | Represent the status of the shipment. | | First Fulfillment Status | The status of the fulfillment. | | First Fulfillment Tracking Company | The name of the tracking company. | | First Fulfillment Tracking Numbers | A list of tracking numbers provided by the tracking company. | | First Fulfillment Tracking Urls | The URLs of tracking pages for the fulfillment. | | Line Item Id | Unique identifier for a Shopify Line Item at a specific point in time. | | Is First Product Type Order | Whether this order contains the first product type for the user. | | Is Last Product Type Order | Whether this order contains the last, most recent, product type for the user. | | Is Repeat Product Type Order | Whether this order contains a repeat product type for the user. | | Line Item Oms Order Line Id | Unique key generated by Shopify that identifies a line item. | | Line Item Quantity | The number of said product that was purchased through this order. | | Rank of Product Type Order | Rank orders with the same product type per user. | | Location Id | Unique identifier for a Shopify Location at a specific point in time | | Location Is Active | Whether the location is active or not. | | Location Is Online | Whether or not this location represents an online location. | | Location Is Physical | Whether or not this location represents a physical location. | | Location Name | The name of a location. | | Location Oms Location Id | Unique key generated by Shopify that identifies a location. | | Order Admin Url | Contains the full URL directing to the admin dashboard of Shopify for that given order. | | Order App Id | The ID of the app from Shopify that created the order. | | Order App Name | App name associated with the app id. This field will be generated if the Hub Configuration is enabled and the value has been set. | | Order Applied Discount Codes | The discount 'codes' applied or a given order. | | Order Applied Discount Codes Count | The total number of applied discount code for a given order. | | Order Cancel Reason | The reason as to why the order was cancelled. | | Order Cart Website Locale | When available, this is the shopify international site activated prior to cart creation. | | Order Completed Order Rank By User | Allows to rank customer carts by completion date. In other words, this will rank the customer's completed order from 1 to X (X being the most recent order that was completed). | | Order Completed Subscription Order Rank By User | Allows to rank customer subscription orders by completion date. | | Order Contains First Subscription Order | A boolean value to indicate whether an order contains the first subscription order or not. An order may contain a mix of first and recurring subscriptions. | | Order Created Order Rank By User | Allows to rank customer carts by creation date. In other words, this will rank the customer's creation order from 1 to X (X being the last order that was created). An order can be created but never completed. | | Order Created Subscription Order Rank By User | Allows to rank customer subscription orders by creation date. | | Order Customer Lifetime Month | Number of months between the current order's creation date and the user's first order creation date. First orders have a value of 1. | | Order Customer Lifetime Week | Number of weeks between the current order's creation date and the user's first order creation date. First orders always have a value of 1. | | Order Filtered Order | Whether or not this order will be flagged by custom filter. | | Order Financial State | The status of transaction associated with the order. | | Order Fulfillment State | The summarized status of the 'shipment/fulfillment' associated with the order. | | Order Has Discount | Whether or not the order has had a discount applied to it. | | Order Has Order Tag | Whether or not the order has an order tag applied to it. | | Order Id | Unique identifier generated by Chord for an order. | | Order Included Fulfillment Codes | Aggregated array of fulfillment codes, represented as a string. | | Order Included Fulfillment Methods | Aggregated array of fulfillment methods, represented as a string. | | Order Included Payment Gateways | This is the rolled up successful payment gateway for an order. Successful payments are included if they are sale or capture transactions. | | Order Included Source Subscription Ids | String list of included source subscription ids per order. Subscription information received from tenant-enabled platforms including Recharge and Shopify Plus. | | Order Included Subscription Ids | String list of included subscription ids per order. Subscription information received from tenant-enabled platforms including Recharge and Shopify Plus. | | Order Is Admin | Whether or not the order was created by an admin. | | Order Is Cancelled | Whether or not the order was cancelled. If \`cancelled\_at\` is non-null then we consider the order has being cancelled. | | Order Is Completed | Whether or not the order was completed. An order is considered completed if it has a closed\_at timestamp and has been fully fulfilled. Closed\_at 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. | | Order Is First Completed Order | Whether the order was the customer's first completed order or not. | | Order Is First Order | Whether the order was the customer's first order or not. | | Order Is First Subscription Completed Order | Whether the order was the customer's first completed subscription order or not. | | Order Is First Subscription Order | Whether the order was the customer's first subscription order or not. | | Order Is Part Of Subscription | Boolean flag to indicate whether the order was a part of a subscription plan or not. | | Order Is Test | Whether this is a test order or not. | | Order Item Id | Unique identifier generated by Chord for an order. | | Order Item Is First Product Type Order | Whether this order contains the first product type basket for the user. | | Order Item Is Last Product Type Order | Whether this order contains the last, most recent, product type basket for the user. | | Order Item Is Repeat Product Type Order | Whether this order contains a repeat product type basket for the user. | | Order Item Product Basket Count | The count of products for a given order. | | Product Basket | The titles of products for a given orderarray converted to a string. | | Order Item Product Purchased Quantity | The total number of product purchased for a given order. | | Order Item Rank Product Type Order | Rank orders with the same product type basket per user. | | Order Item Unique Product Basket Count | The count of unique products for a given order. | | Unique Product Basket | The unique titles of products for a given order array converted to a string. | | Order Item Unique Product Type | The unique line item product types for a given order. | | Order Item Unique Variant Basket Count | The count of unique SKUs for a given order. | | Unique Variant Basket | The unique SKUs of variants for a given order array converted to a string. | | Order Item Variant Basket Count | The count of variants for a given order. | | Variant Basket | The SKUs of variants for a given order array converted to a string. | | Order Item Variant Purchased Quantity | The total number of variants purchased for a given order. | | Order Name | Unique name generated by Shopify that is displayed to the customer (e.g. | | Order Number Of Non Reactivated Subscriptions | Number of non reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Order Number Of Reactivated Subscriptions | Number of reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Order Oms Order Id | Unique key generated by Shopify that identifies an order. | | Order Tags | The order tags applied to a given order, in alphabetical order. | | Order Tags Count | The total number of order tags for a given order. | | Order Processing Method | How the payment was processed. | | Order Segment Anonymous Id | When available, this is where we store Segment's anonymous\_id at the time of checkout. | | Order Source Name | Where did the order get created from. | | Product Handle | A unique human-friendly string for the product (i.e. slug). | | Product Id | Unique identifier for a Shopify Product at a specific point in time | | Product Is Active | Whether or not the product is active. | | Product Is Custom Item | Whether or not the product is a custom one. | | Product Oms Product Id | Unique key generated by Shopify that identifies a product. | | Product Type | A string that defines the type of the product. | | Product Title | The name of the product. | | Product Vendor | The name of item's supplier. | | Product Was Previously Deleted | Whether or not the product was previously deleted. | | 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. | | 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 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. | | Variant Barcode | The barcode, UPC, or ISBN number for the product. | | Variant Color | The color of the variant set in the Hub configuration. This field will be generated if the Hub Configuration is enabled and the value has been set. | | Variant Function | The function of the variant set in the Hub configuration. This field will be generated if the Hub Configuration is enabled and the value has been set. | | Variant Grams | The weight of the variant in grams. | | Variant Id | Unique identifier for a Shopify Variant at a specific point in time. | | Variant Is Taxable | Whether a tax is charged when the product variant is sold. | | Variant Material | The material of the variant set in the Hub configuration. This field will be generated if the Hub Configuration is enabled and the value has been set. | | Variant Oms Variant Id | Unique key generated by Shopify that identifies a variant. | | Variant Option 1 | The first custom property that is attached to the variant. | | Variant Option 2 | The second custom property that is attached to the variant. | | Variant Option 3 | The third custom property that is attached to the variant. | | Variant Other Attributes | Other attributes of the variant not captured in the defined attribute fields. These should be comma seperated and set in the Hub configuration. This field will be generated if the Hub Configuration is enabled and the value has been set. | | Variant Price | The price of the variant. | | Variant Product Category | Product Category is the highest level of the variant hierarchy. For example: Fruit > Berries > Strawberries, the Product Category is Fruit and covers all variants that are Fruit. This field will be generated if the Hub Configuration is enabled and the value has been set. | | Variant Product Class | Product Class is the third level of the variant hierarchy. For example: Fruit > Berries > Strawberries, the Product Class is Strawberries and includes only Berries that are Strawberries. There can be more than one variant within the class. This field will be generated if the Hub Configuration is enabled and the value has been set. | | Variant Product Subcategory | Product Subcategory is the middle level of the variant hierarchy. For example: Fruit > Berries > Strawberries, the Product Subcategory is Berries and includes only Fruits that are Berries. This field will be generated if the Hub Configuration is enabled and the value has been set. | | Variant Shape | The shape of the variant set in the Hub configuration. This field will be generated if the Hub Configuration is enabled and the value has been set. | | Variant Size | The size of the variant set in the Hub configuration. This field will be generated if the Hub Configuration is enabled and the value has been set. | | Variant Sku | A unique identifier for the product variant in the shop. | | Variant Style | The style of the variant set in the Hub configuration. This field will be generated if the Hub Configuration is enabled and the value has been set. | | Variant Title | The title of the variant. | | Order Cancelled At (Universal) | Reflects when the order was cancelled in Shopify - Universal Time Zone. | | Order Completed At (Central) | The timestamp when this order became completed - Cental Time Zone. | | Order Completed At (Eastern) | The timestamp when this order became completed - Eastern Time Zone. | | Order Completed At (Mountain) | The timestamp when this order became completed - Mountain Time Zone. | | Order Completed At (Pacific) | The timestamp when this order became completed - Pacific Time Zone. | | Order Completed At (Universal) | The timestamp when this order became completed - Universal Time Zone. | | Order Created At (Central) | Reflects when the entity was first created in Shopify - Cental Time Zone. | | Order Created At (Eastern) | Reflects when the entity was first created in Shopify - Eastern Time Zone. | | Order Created At (Mountain) | Reflects when the entity was first created in Shopify - Mountain Time Zone. | | Order Created At (Pacific) | Reflects when the entity was first created in Shopify - Pacific Time Zone. | | Order Created At (Universal) | Reflects when the entity was first created in Shopify - Universal Time Zone. | | Order Last Fulfillment At (Universal) | The maximum timestamp for the last update order fulfillment - Universal Time Zone. | | Order Updated At (Universal) | Reflects when the entity was last updated in Shopify - Universal Time Zone. | | 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 Quantity | The quantity of variants sold. | | Average Sku Price | The price of the product that was purchased through this order. | | Average Total Price | The total price of the line item, not including any discounts. The total price is calculated using the original unit price multiplied by the quantity. | | Total Price | The total price of the line item, not including any discounts. The total price is calculated using the original unit price multiplied by the quantity. | | Quantity | The quantity of variants sold. | | Sku Price | The price of the product that was purchased through this order. | ### extend\_x\_fct\_trans\_orders\_multipay | Name | Description | | ------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Order Contains Fulfillment Order | Whether the order contains a fulfillment order. | | Order Contains Multipay Subscription Installment | Whether the order contains a multipay order. | | Order Contains Payment Order | Whether the order contains a payment order. | | Order Installment Charge Ids | Array of Recharge charge ids for the installments in the order, if there is more than one multipay subscription represented, there will be a unique array per installment. | | Order Installment Recharge Order Ids | Array of Recharge order ids for the installments in the order, if there is more than one multipay subscription represented, there will be a unique array per installment. | | Order Installment Shopify Order Ids | Array of the Shopify order ids for the installments in the order, if there is more than one multipay subscription represented, there will be a unique array per installment. | | Order Included Installment Count | Count of total installments in the order. | | Order Included Payment Plans | Array of payment plans included in the order. If an order contains multiple subscriptions, each subscription will be represented. | | Average Total Child Refunds | The total adjusted dollars that were refunded to a child installment order for paid orders. | | Average Total Child Shipping Received | Total shipping paid for child orders within an installment. Shipping is included for the first installment order of a child-only order if the order is mixed. If the order contains a fulfillment order, the shipping will remain attached to the fulfillment order. | | Average Total Child Unit Price Received | The total unit price received for child order payments for the installment. Payments are included if the payment status is recorded as 'success', 'refunded', or 'partially\_refunded'. | | Average Total Fulfillment Unit Price Received | The total unit price received for fulfillment order payments for the installment. Payments are included if the payment status is recorded as 'success', 'refunded', or 'partially\_refunded'. | | Average Total Subscription Installment Value | The total unit price of the installment, calculated as fulfillment order (unit price \* quantity) \* total expected payments. | | Average Total Unit Price Remaining | The total installment value minus the total fulfillment and child payments received. | | Average Total Estimated Shipping Price | The total estimated shipping across all installments in the order. | | Average Total Estimated Item Tax | The total estimated item tax across all installments in the order. | | Average Total Estimated Shipping Tax | The total estimated shipping tax across all installments in the order. | | Total Child Refunds | The total adjusted dollars that were refunded to a child installment order for paid orders. | | Total Child Shipping Received | Total shipping paid for child orders within an installment. Shipping is included for the first installment order of a child-only order if the order is mixed. If the order contains a fulfillment order, the shipping will remain attached to the fulfillment order. | | Total Child Unit Price Received | The total unit price received for child order payments for the installment. Payments are included if the payment status is recorded as 'success', 'refunded', or 'partially\_refunded'. | | Total Fulfillment Unit Price Received | The total unit price received for fulfillment order payments for the installment. Payments are included if the payment status is recorded as 'success', 'refunded', or 'partially\_refunded'. | | Total Subscription Installment Value | The total unit price of the installment, calculated as fulfillment order (unit price \* quantity) \* total expected payments. | | Total Unit Price Remaining | The total installment value minus the total fulfillment and child payments received. | | Total Estimated Shipping Price | The total estimated shipping across all installments in the order. | | Total Estimated Item Tax | The total estimated item tax across all installments in the order. | | Total Estimated Shipping Tax | The total estimated shipping tax across all installments in the order. | ### order\_applied\_discount\_codes | Name | Description | | ---------------------------- | ----------------------------------- | | Order Applied Discount Codes | Discount code applied to the order. | ### order\_tags | Name | Description | | ---------- | ---------------------------------- | | Order Tags | Order tag(s) applied to the order. | [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] Line Items [path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Salesforce/ ### x\_fct\_order\_lines | Name | Description | | --------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Order Account Id | ID generated by chord to identify the account. | | Order Bill To Contact Id | ID of the Contact associated with the Order Summary. It represents the shopper in the storefront when not using person accounts. | | Order Billing City | Billing address city. | | Order Billing Country | Billing address country. | | Order Billing Email Address | Email address on the billing address. | | Order Billing State | Billing address state. | | Order Billing State Country | The billing state or country of the order. Default to billing country if state is unavailable. | | Order Currency Iso Code | Available only for stores with the multicurrency feature enabled. Contains the ISO code for the currency of the original Order associated with the Order Summary. The default value is USD. Possible values are: DKK—Danish Krone, EUR—Euro, GBP—British Pound, USD—U.S. Dollar. | | Order Fulfillment Ids | IDs generated by Chord to identify the fulfillments associated with the order. | | Order Fulfillment Numbers | The fulfillment numbers associated with the order. | | Order Fulfillment Statuses | The fulfillment statuses associated with the order. | | Order Has A Shipped Fulfillment | A flag marking if an order has a shipped fulfillment. | | Order Hours To First Delivery | The number of hours between when the order was created and the first fulfillment was created. | | Order Hours To Last Delivery | The number of hours between when the order was created and the last, most recent, fulfillment was created. | | Order Id | ID generated by Chord to identify the order. | | Order Is Canceled | Whether an order is canceled. | | Order Is Completed | Whether an order is 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. | | Order Line Description | Description of the Order Item Summary. This field can be edited in the OMS. | | Order Line Fulfillment Ids | ID generated by Chord to identify the fulfillment ids associated with the order item. | | Order Line Fulfillment Item Ids | IDs generated by Chord to identify the fulfillment items associated with the order item. | | Order Line Gross Unit Price | Unit price, including tax, of the Order Item Summary. This value is equal to the single Unit Price + the amount of tax on the single Unit Price. Note that this field is rounded. | | Order Line Id | ID generated by Chord to identify the order line. | | Order Line Is Completed | Whether an order is 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. | | Order Line Number | The order line number assigned to this Order Item Summary. For example, if this object is the third in the displayed list of Order Item Summaries belonging to the Order Summary, this value is 3. | | Order Line List Price | List price of the product represented by this Order Item Summary. | | Order Line Name | Name of the Order Item Summary. | | Order Line Number Of Fulfillments | The number of fulfillments associated with the order item. | | Order Line Oms Fulfillment Ids | ID generated by the OMS to identify the fulfillment ids associated with the order item. | | Order Line Oms Fulfillment Item Ids | ID generated by the OMS to identify the fulfillment items associated with the order item. | | Order Line Oms Order Item Id | The ID generated by the oms for the order item summary. | | Order Line Oms Return Order Ids | IDs generated by the OMS to identify the return order.
| | Order Line Oms Return Order Item Ids | IDs generated by the OMS to identify the return items associated with the order item. | | Order Line Product Code | Product code of the product represented by this Order Item Summary. | | Order Line Product Id | ID generated by chord to identify the product associated with the order line. | | Order Line Promotion Details Collection | Promotion details to of the Order Item Summary. | | Order Line Return Order Ids | IDs generated by Chord to identify the return order. | | Order Line Return Order Item Ids | IDs generated by Chord to identify the return items associated with the order item. | | Order Line Sku | The stock keeping unit (SKU) of the Product2 associated with the Order Item Summary. | | Order Line Status | Status of the Order Item Summary. The default value is ORDERED. Possible values are: ALLOCATED—Allocated, CANCELED—Canceled, FULFILLED—Fulfilled, ORDERED—Ordered, PAID—Paid, PARTIALLYALLOCATED—Partially Allocated, PARTIALLYFULFILLED—Partially Fulfilled, RESHIPPED—Reshipped, RETURNED—Returned. | | Order Line Total Fulfillment Quantity | The quantity of item in the fulfillments. | | Order Line Type | Type of the Order Item Summary. Delivery Charge indicates that the Order Item Summary represents a delivery charge. Order Product indicates that it represents any other type of product, service, or charge. Each type corresponds to one type code, shown here in parentheses. Possible values are: Delivery Charge (Charge), Order Product (Product). | | Order Line Type Code | Type code of the Order Item Summary. Charge indicates that the Order Item Summary represents a delivery charge. Product indicates that it represents any other type of product, service, or charge. Possible values are: Charge, Product. | | Order Line Unit Price | Unit price of the product represented by the Order Item Summary. | | Order Number Of Fulfillments | The total number of fulfillments associated with the order. | | Order Number Of Reimbursements | The number of reimbursements associated with an order. | | Order Oms Account Id | ID of the account or person account associated with the Order Summary. It represents the shopper in the storefront. | | Order Oms Fulfillment Ids | ID generated by the OMS to identify the order. | | Order Oms Order Id | The id generated by the OMS for the Order Summary. | | Order Oms Order Payment Summary Ids | IDs generated by the OMS to identify the payment summaries associated with the order. | | Order Oms Return Order Ids | IDs generated by the OMS to identify the returns associated with the order. | | Order Is First Order | Whether the order is first order associated with the account. | | Order Number | Name of the Order Summary. | | Order Payment Summary Ids | IDs generated by Chord to identify the payment summaries associated with the order. | | Order Original Order Id | ID of the original order associated with this Order Summary. | | Order Payment Methods | The payment methods associated with the order.
| | Order Payment Types | The payment types associated with the order. | | Order Po Number | Purchase order number associated with this Order Summary. | | Order Promotion Details Collection | The promotion details associated with the Order Summary. | | Order Return Order Ids | IDs generated by Chord to identify the returns associated with the order. | | Order Return Order Numbers | The return order numbers associated with the order. | | Order Sales Channel Id | ID of the Sales Channel associated with this Order Summary. | | Order Status | Status of the order summary. Unlike the Status and Status Category fields on the order and Fulfillment Order objects, this field is optional. | | Order Tax Locale Type | The system used to handle tax on the original Order associated with the Order Summary. Gross usually applies to taxes like value-added tax (VAT), and Net usually applies to taxes like sales tax. Possible values are: Gross (displays most prices and taxes as combined values), Net (displays most prices and taxes as separate values). | | Order Utm Campaign | The UTM Campaign associated with the Order Summary. | | Order Utm Medium | The UTM Medium associated with the Order Summary. | | Product Color | Color of the product. | | Product Id | | | Product Oms Product Id | ID generated by the OMS to identify the product.
| | Product Sku | SKU for the product. | | Product Sku Description | Description of the product. | | Order Created At (Central) | The date the Order Summary was created - Cental Time Zone. | | Order Created At (Eastern) | The date the Order Summary was created - Eastern Time Zone. | | Order Created At (Mountain) | The date the Order Summary was created - Mountain Time Zone. | | Order Created At (Pacific) | The date the Order Summary was created - Pacific Time Zone. | | Order Created At (Universal) | The date the Order Summary was created - Universal Time Zone. | | Order First Fulfillment Created At (Universal) | Timestamp when the first fulfillment for the order was created - Universal Time Zone. | | Order First Order Created At (Universal) | Timestamp when the first order was created at - Universal Time Zone. | | Order Last Fulfillment Created At (Universal) | Timestamp when the most recent, or last, fulfillment for the order was created - Universal Time Zone. | | Order Last Modified Date (Universal) | The date the Order Summary was last modified - Universal Time Zone. | | Order Line Created At (Universal) | Date the Order Item Summary was created - Universal Time Zone. | | Order Line First Fulfillment Created At (Universal) | The first created at timestamp of a fulfillment item - Universal Time Zone.
| | Order Line First Fulfillment Expected Delivery Date (Universal) | The first expected delivery date of a fulfillment item - Universal Time Zone. | | Order Line Last Fulfillment Created At (Universal) | The most recent created at timestamp of a fulfillment item - Universal Time Zone. | | Order Line Last Fulfillment Expected Delivery Date (Universal) | The most recent expected delivery date of a fulfillment item - Universal Time Zone. | | Order Line Requested Delivery Date (Universal) | Requested delivery date for the item - Universal Time Zone. | | Order Ordered Date (Universal) | Date of the original order associated with this Order Summary - Universal Time Zone. | | Average Adjusted Total Price | Line Item total, including adjustments but not tax, of the Order Item Summary. | | Average Adjustment Total | Total of all non-order-level price adjustments applied to this Order Item Summary. This value includes Order Item Adjustment Line Summaries that don’t belong to an Order Adjustment Group Summary, or that belong to an Order Adjustment Group Summary of type Split Line. | | Average Quantity | Current total quantity of products represented by this order item summary. Equal to Quantity Ordered minus (Quantity Canceled and Quantit Returned). | | Average Quantity Allocated | Allocated quantity on this order item summary. This quantity is associated with one or more Fulfillment Order Line Items. | | Average Quantity Canceled | Canceled quantity on this Order Item Summary. | | Average Quantity Fulfilled | Fulfilled quantity on this Order Item Summary. This quantity can no longer be canceled. | | Average Quantity Ordered | Ordered quantity on this Order Item Summary. It includes the originally ordered quantity plus any quantity added to the order later. | | Average Quantity Return Initiated | Quantity returned or pending return on this Order Item Summary. | | Average Quantity Returned | Returned quantity on this Order Item Summary. | | Average Quantity Shipped | The quantity of items shipped. | | Average Total Price | Total, not including adjustments or tax, of the Order Item Summary. | | Average Total Tax Amount | Tax on the Total Price. | | Adjusted Total Price | Line Item total, including adjustments but not tax, of the Order Item Summary. | | Adjustment Total | Total of all non-order-level price adjustments applied to this Order Item Summary. This value includes Order Item Adjustment Line Summaries that don’t belong to an Order Adjustment Group Summary, or that belong to an Order Adjustment Group Summary of type Split Line. | | Total Price | Total, not including adjustments or tax, of the Order Item Summary. | | Quantity | Current total quantity of products represented by this order item summary. Equal to Quantity Ordered minus (Quantity Canceled and Quantit Returned). | | Quantity Allocated | Allocated quantity on this order item summary. This quantity is associated with one or more Fulfillment Order Line Items. | | Quantity Canceled | Canceled quantity on this Order Item Summary. | | Quantity Fulfilled | Fulfilled quantity on this Order Item Summary. This quantity can no longer be canceled. | | Quantity Ordered | Ordered quantity on this Order Item Summary. It includes the originally ordered quantity plus any quantity added to the order later. | | Quantity Return Initiated | Quantity returned or pending return on this Order Item Summary. | | Quantity Returned | Returned quantity on this Order Item Summary. | | Quantity Shipped | The quantity of items shipped. | | Total Tax Amount | Tax on the Total Price. | [title] Campaign Mapping [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 Oftentimes, brands need to map campaign names to different attributes. Chord's Campaign Mapping amplifcation allows brands to identify and log campaigns based on a number of different attributes. ## How It Works The configuration allows the brand to identify and define campaigns based on a combination of the following options: - **Campaign Name: **This is a unique field. - **Campaign Name Refined:** Optional, simplified campaign name. - **Campaign Region** (ex: US, CA, EU) - **Campaign Brand** - **Campaign Type** (ex: Transactional, Batch, Automated) - **Campaign Objective **(ex: Engagement, Retention, Acquisition) - **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. - **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. - **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. - **Campaign Platform: **The Ad Source of the campaign. (Ex: Google Ads, Tiktok Ads) - **Campaign Channel:** The attribution channel of the campaign. (Ex: Email, SMS) - **Campaign Sub-Channel: **Sub-Channel is a granular level of attribution. - **Campaign Temporality **(Ex: September Sale, October EVG, 20230504, etc) - **Campaign Option: **Include any additional attributes not captured by existing fields. You may add more than one attribute with a comma separating. Periodically, Chord will assess adding additional attribute columns. ## Sample Use Case Brands can easily extend their enriched Chord data set to include campaign mapping data and answer more robust business questions tied to different marketing and business campaigns throughout different regions, channels, etc. [title] Northbeam Pixel [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ **Northbeam Pixel** is Northbeam's JavaScript tag for client-side attribution tracking. This destination loads the Northbeam pixel in the browser and forwards page view, identity, and ecommerce events to Northbeam. For server-side order reporting, see the [Northbeam](#) destination. # Getting Started This is a device-mode destination. The Northbeam pixel is loaded automatically — no manual script installation is required. You will need: - **Data Client ID** — the UUID that identifies your Northbeam account. Found in the Northbeam dashboard under **Settings > API Keys**. Optionally, configure custom goal IDs for ecommerce funnel events (see [Custom Goals](#) below). # Connecting to the Northbeam 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 **Northbeam Pixel** from the destination catalog. 5. Enter the destination name and your **Data Client ID**. 6. Optionally configure custom goal IDs for Product Viewed, Add to Cart, and Checkout Started events. 7. Click **"Create"** to connect. # Using Alongside the Northbeam (Cloud-Mode) Destination The Northbeam Pixel and the [Northbeam](#) server-side destination can be used together. Both send purchase data to Northbeam — the pixel via `firePurchaseEvent` and the cloud-mode destination via the Orders API. Northbeam deduplicates purchases by order ID, so running both should not result in double-counted orders. If you are using only the pixel destination (no cloud-mode), note that **Order Refunded** events are not reported — refunds require the server-side Orders API. # Event Mapping | Chord Event | Northbeam Call | | ------------------ | ---------------------------------------------------------- | | `page` | `trackPageView()` | | `identify` | `identify(email)` + `identifyCustomerId("custom", userId)` | | `Order Completed` | `firePurchaseEvent(orderData)` | | `Product Viewed` | `fireCustomGoal(productViewedGoalId, {})` | | `Product Added` | `fireCustomGoal(addToCartGoalId, {})` | | `Checkout Started` | `fireCustomGoal(checkoutStartedGoalId, {})` | | `Email Captured` | `fireEmailCaptureEvent(email, {})` | # Page Events **Northbeam call:** `window.Northbeam.trackPageView()` Called on every `page` event after the initial page load. The Northbeam pixel fires `trackPageViewInitial` automatically during initialization to capture the first page view — subsequent SPA navigations fire `trackPageView()`. No additional attributes are sent with page events. # Identify Events Updates the Northbeam identity graph for the current visitor. **Northbeam calls:** - `window.Northbeam.identify(email)` — fires when `context.traits.email` is present - `window.Northbeam.identifyCustomerId("custom", userId)` — fires when `userId` is present Both calls are made independently if their respective fields are available. | Northbeam Parameter | Chord Source | | ------------------- | ---------------------- | | `email` | `context.traits.email` | | `customerId` | `userId` | # Order Completed Fires a purchase conversion event with full order and line item data. **Northbeam call:** `window.Northbeam.firePurchaseEvent(orderData)` | Northbeam Field | Chord Source | Notes | | ------------------------- | -------------------------------------------------------------- | --------------------------------------- | | `id` | `properties.order_id` | Required by Northbeam for deduplication | | `totalPrice` | `properties.total` → `properties.revenue` → `properties.value` | Defaults to `0` | | `shippingPrice` | `properties.shipping` | Defaults to `0` | | `taxPrice` | `properties.tax` | Defaults to `0` | | `coupons` | `properties.coupon` | Empty string if absent | | `currency` | `properties.currency` | Defaults to `"USD"` | | `lineItems[].productId` | `product.product_id` → `product.sku` → `product.id` | | | `lineItems[].variantId` | `product.variant_id` → `product.sku` → `product.product_id` | | | `lineItems[].productName` | `product.name` | | | `lineItems[].variantName` | `product.variant` → `product.name` | | | `lineItems[].price` | `product.price` | Defaults to `0` | | `lineItems[].quantity` | `product.quantity` | Defaults to `1` | # Custom Goals Northbeam tracks **Product Viewed**, **Product Added**, and **Checkout Started** events as custom goals. Custom goals count event occurrences only — they do not carry revenue or product data. Goal names must be registered with the Northbeam team before they appear in your Northbeam dashboard. Configure goal IDs in the destination settings to match what you have registered with Northbeam: | Setting | Default Value | Chord Event | | ------------------------ | -------------------- | ------------------ | | Product Viewed Goal ID | `product_viewed` | `Product Viewed` | | Add to Cart Goal ID | `add_to_cart` | `Product Added` | | Checkout Started Goal ID | `checkout_initiated` | `Checkout Started` | **Northbeam call:** `window.Northbeam.fireCustomGoal(goalId, {})` # Email Captured Fires when an `Email Captured` track event includes a user email address. This both records the email capture goal and links the email to the current visitor in Northbeam. **Northbeam call:** `window.Northbeam.fireEmailCaptureEvent(email, {})` The event is skipped if no email is present on the event. # Initialization The plugin loads `//j.northbeam.io/ota-sp/{dataClientId}.js` and sets up a command queue to buffer calls before the script loads. `trackPageViewInitial` fires automatically during initialization to capture the first 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: | Directive | Domain | | ------------- | ------------------------ | | `script-src` | `https://j.northbeam.io` | | `connect-src` | `https://j.northbeam.io` | *** **Updated 11 May 2026** [title] Downloading Reports [path] Chord Data Platform/Analytics Features/ ### Introduction Dashboards and reports across the platform can be downloaded so that you can share or send your visualization or data. ### Downloading reports In every dashboard and analysis, you'll notice in the top right corner there are three vertical dots or a gear icon, depending on the type of visualization, that provide various options for your reports, including downloading the data. Navigating to "Download" will open a pop-up with various options to customize your download. **Formats** Within the Download pop-up, you'll first see a drop-down for various format options, including: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/Mc1IuiiEpECFdjbKtWt7S_screenshot-2024-06-27-at-63843-pm.png" size="62" width="858" height="422" position="center" darkWidth="858" darkHeight="422" showCaption="false"} **Data Over 5,000 Rows** While exploring datasets, the data results limit will default to 500 results, but it can be increased to 5,000 results. However, you can still download all the results. In the Download pop-up, there is a section for "Number of rows and columns to include," which displays an option for "All results" to download the full dataset. ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/SLMaGORQnq7AOAg2xPo1g_screenshot-2024-06-27-at-65444-pm.png) **If All Results is disabled** The **All results** option is typically disabled for queries that do any of the following: - Involve row totals or table calculations - Use percent of total, percent of previous, or running totals types of measures If you remove the above, such as table calculations, then you'll be able to download all results. [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*** # ![](https://app.archbee.com/api/optimize/TmutqdeXiIw-V3gBZXVjd/_hF7LMMwoyJxk_o7nGrvJ_image.png "Navigate to Integrations Page") ![](https://app.archbee.com/api/optimize/TmutqdeXiIw-V3gBZXVjd/r0m6wAB8129Sq3BFebx6z_image.png "Select the API option") ![](https://app.archbee.com/api/optimize/TmutqdeXiIw-V3gBZXVjd/Xr4k1JVovtIwxAvnM8Flm_image.png "Copy 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] Accessing Data Science Features [path] Chord Data Platform/Predictive Models/ There are minimum data thresholds required to ensure our data science model outputs are accurate. Customer lifetime revenue, purchase likelihood, revenue forecasts, product recommendations, and probability alive are available to Chord customers who have at least: - 2000 completed transactions and nine months of transaction history - 90 cumulative days containing transactions - 500 completed transactions from the last 90 days and - transactions completed in the past 30 days [title] Chord's Methodology as Compared to Other Platforms [path] Chord Data Platform/Data Models/ ### Overview Chord ingests raw data from various data sources and then transforms it through a data modeling layer to clean and enrich it for more efficient, meaningful analyses. As a result, Chord's data models can differ from what users see directly in other platforms. :::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] Customer Lifetime Revenue (CLR) [path] Chord Data Platform/Predictive Models/ ### What is Customer Lifetime Revenue? Customer lifetime revenue and purchase likelihood are predictive insights about customers who have made at least one purchase in your online store. While both tools forecast future buying behavior, how you think about them from a marketing perspective may differ. ::::LinkArray :::LinkArrayItem{headerType="COLOR" headerColor="#f00bf3"} [Customer Lifetime Revenue and Purchase Likelihood](docId:7C0gpeaYBzjwGadO3t2ib) ::: :::LinkArrayItem{headerType="COLOR" headerColor="#0af130"} [Customer Lifetime Revenue (CLR) Explanation](docId\:hpoMH0f8yKr1VksnejpEm) ::: :::LinkArrayItem{headerType="COLOR" headerColor="#0a27f1"} [Recency, Frequency, Monetary Value (RFM)](docId\:L91UpCbIucX4huAP2ByfI) ::: :::LinkArrayItem{headerType="COLOR" headerColor="#f00bf3"} [CLR and RFM Data Table Glossary](docId\:XzU-KFlDMlty4bseZIAiN) ::: :::LinkArrayItem{headerType="COLOR" headerColor="#0af130"} [CLR and RFM on the Chord Commerce Data Platform](docId\:soF9HUFLL1N0-7U4NvHro) ::: :::: [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] Using Quickstarts [path] Chord Data Platform/Analytics Features/ # Introduction Ready to hit the ground running? Our Quickstarts are designed to take the guesswork out of your analytics reporting setup, so you can focus on what really matters—growing your business. Whether you're setting up a recurring report or organizing data for deep analysis, these templates get you from zero to launch in no time. # Feature overview ::loom{url="https://www.loom.com/embed/42a4d8def942440eb7bd8fcac5ecb3db?sid=0dc6bae4-d552-4a1a-a684-86a0115bfff6"} # Getting started ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-R6Y5oWknC0X11piAQyFx8-20241022-150130.png) 1. Navigate to the **Analytics** page on the Chord platform. 2. Locate the **Quickstarts** tab. 3. Search, browse, and filter Chord’s quickstart library for a dashboard or Look (explore). 4. Select any dashboard or Look (explore) to copy into **My Folder**. 5. You’re now ready to create and build your custom dashboard or Look! # Troubleshooting and FAQs - **What are the different categories I can search?** - You can search for different quickstarts in the following categories: - Customer - E-Commerce - Marketing - Product - Sales - **How can I tell what type of quickstart I am looking at on this page?** ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-Y04pbehtcB2vVcp7Kj4vT-20241018-144855.png "Example quickstart tile.") - Take the following example tile: ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-yy3URvO0fdRkeBRQbFPRZ-20241018-145019.png "Sample tile description.") - The icon on the left indicates that this is a dashboard quickstart template. If this were a Look template, the icon would change to this bar icon: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-4G128p1D5m6wkyF-Mq4tM-20241018-145109.png" size="10" width="55" height="53" position="center" darkWidth="55" darkHeight="53" showCaption="false"} [title] Creating Custom Calculations [path] Chord Data Platform/Analytics Features/ ::::ExpandableHeading ### Introduction This article will walk you through how to create custom metrics directly within an explore dataset. :::hint{type="success"} The default timezone in Looker for OMS timestamps is UTC, whereas the OMS UI displays EST. Within Looker, we've added additional timezone options for some of our timestamps but not for `Order Approved Date`. Custom time zones can be created with a custom field and can be submitted as a feature request. ::: :::: :::ExpandableHeading ### Create a custom calculation While Chord's data engineers have built plenty of out-of-the-box metrics for you to explore, we understand that you may find yourself needing to create custom calculations. Navigate to your Looker account and choose the 'Explore' page with the data points that you are looking to include in your custom metric. On the right-hand panel, select the measures that will be part of your calculation. For example, Abandoned Cart = # of Customers That Added Product to Cart- # of Customers who Check out, both of these measures will need to be selected in order to create a calculation. You will see the measures pop up in the 'Data' field at the bottom of the screen. 1. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/mfICy6kOXPhI4NiAVTqu1_1.png" size="52" width="630" height="1956" caption="Explore" position="flex-start" showCaption="true"} Hit 'Add Calculation' on the right hand side of the 'Data' bar. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/wDkCvq_AojPfSNPbu431e_3.png" size="56" width="874" height="406" caption="Add Calculation" position="flex-start" showCaption="true"} Create your custom calculation. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/RhK_T40C4T8DcIMXd3m20_222.png" size="58" width="1598" height="1258" caption="Edit Calculation" position="flex-start" showCaption="true"} Click Save You've just created a custom calculation! ::: :::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] 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: ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/BJD3bwQX1CdwlRvNAA_-v_image.png) :::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] 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] 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] Model Amplifications [path] Chord Data Platform/ # Introduction Chord's data models have been built from the team's expertise in the world of e-commerce. Currently, all data flows through the same models, delivering consistent outputs across brands. However, just like the wide range of e-commerce brands that sign on to Chord, there is variety in custom data that brands want to feed into and surface from the existing Chord data models. Chord now allows brands to extend their data by adding brand-specific mappings and settings via the Model Amplifications feature on the platform. Amplifications allow brands to structure some of their unique data inputs for modeling so they can represent metrics fitted to their business needs. Brands will see data added as additional fields in explores or see fields updated based on the configuration settings in the templates. Once a specific Amplification is enabled, it will process through the data models in the next scheduled run. Note that some data fields are required fields, and you'll see the following errors in case required fields are not completed. Please see an example below. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/-KAyzlKvKNtK6cTPtPyYM_screenshot-2024-07-12-at-22331-pm.png" size="46" width="368" height="346" position="center" darkWidth="800" darkHeight="752" showCaption="false"} :::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. ::: You can also use the **Download Template** button, open the template in Google Sheets, and populate the rows you need to then export it as a CSV file. You can then upload that CSV file and all valid rows will be automatically added to the configuration. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/JN_PwGYoNr5w7KAu2BqTd_screenshot-2024-08-27-at-133735.png" size="50" width="666" height="688" position="center" alt="upload csv modal" darkWidth="800" darkHeight="826" showCaption="false"} ## Sample Use Cases Brand operators and data analysts could use Model Amplifications to: - Manage additional dimensions for items in the brand's catalog by adding specific attributes to their products, which will in turn show up in the data models and allow them to customize what they see and analyze on Chord. - Reduce the need to create custom fields every time they want to report on the same dimension, like configuring the Shopify Order App IDs to a specific name. - Add sources that are not able to be directly connected through existing data connectors. This could include tracking marketing and advertising spend for Podcasts and Radio Ads. ## Getting Started Each Amplification available to you can be accessed through the Model Amplifications page. The first time you configure your Amplifications, you need to fill in the Amplification templates with your custom data mappings. ![](https://archbee-image-uploads.s3.amazonaws.com/gNLoD7dyLXCzJIXNd1_b8-wnLQPDamASdKhRU0MIPyB-20240823-150250.png) Once you have filled out each Amplification template with your custom data mappings, you can then enable them by requesting activation (templates that do not have any data will not be enabled) . ![](https://archbee-image-uploads.s3.amazonaws.com/gNLoD7dyLXCzJIXNd1_b8-WAiyNn8buSjk9_BRxIZil-20240823-150544.png) It will take about 48 hours for your Amplification to be enabled and for your custom data to be surfaced in your existing Chord data models. ![](https://archbee-image-uploads.s3.amazonaws.com/gNLoD7dyLXCzJIXNd1_b8-GyKSoQDOWGvuHown8TV2s-20240823-150702.png) Once the 48 hour activation period has taken effect, your Amplification will be enabled and will be available in your Chord data models. The activation process happens only once, adding additional data mappings to already enabled Amplifications will continue to automatically feed into your Chord data models. ![](https://archbee-image-uploads.s3.amazonaws.com/gNLoD7dyLXCzJIXNd1_b8--Xw2XBo4ERuUn1q-WjdpL-20240823-151226.png) Going back to the Model Amplifications page, you will be able to see which Amplifications you have enabled, which are in progess, and which still need to be enabled. ![](https://archbee-image-uploads.s3.amazonaws.com/gNLoD7dyLXCzJIXNd1_b8-8O4L5bgGYVaKr-0S25NZ5-20240823-151340.png) ## Bulk Uploading Data :::hint{type="warning"} **Data Upload Limitations** - **Users cannot upload files greater than 10MB**. Please ensure that your file upload doesn't exceed 10MB in size. This translates to roughly more than 30K rows of data. - **Please only upload CSV files**. The Chord platform will not be able to read any other file format for model amplifications. - **Please do not remove the "Key" column provided in the CSV template**. This column is used for internal purposes and should not be altered. ::: The Chord data platform also supports bulk upload of data, which in turn supports brands that need to upload many rows of data, or need to need to add thousands of new SKUs to a specific data model at any given time. :::hint{type="info"} **Note:** Once you bulk upload data to our amplifications feature, there may be a wait time to view the results on our platform. This is governed by the data refresh cadence set for your organization as well as the timing of the last data sync with Fivetran. ::: To bulk upload data, you can follow the steps below: ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-2ToWS-xPoQESGESQpItz6-20240917-213647.png) On a given model amplification template, **download the template, fill in the desired columns with your data, **and click the **Upload CSV **button on the template page. From here, you can attach a CSV file to upload. ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-NOp1pa3bh4JDlOQ2L5_XX-20240917-213859.png) Once you attach a valid CSV file, the CSV upload modal closes and you will see a message saying that the file is being processed. During processing, the Chord data platform will check the new file and validate all rows in the file to ensure that there are no duplicates (i.e. check required columns and uniqueness). Once validated, the information in the new sheet will be appended to the original file. :::hint{type="info"} All valid rows of data in the uploaded CSV file will be appended to the model amplification. Invalid rows of data will be provided in a new file that can be downloaded by the user to reconcile once the initial upload processing is complete. ::: ## Help & Troubleshooting - **Question: I need to update a previously uploaded / provided datapoint in an existing amplification. Will the model amplifications feature find and replace this information when a new sheet is uploaded with current information?** - **Answer:** The model amplifications will simply append the updated data as a new row to the sheet. ***Existing rows will neither be removed nor updated based on what’s provided in an uploaded CSV.*** In other words, model amplifications will not "find and replace" one datapoint in a pre-existing row at this time. - **Question: What is the best way to update a large number of rows via an upload without changing already uploaded data?** - **Answer:** If there are a large number of rows that would be too time-consuming to update manually (i.e. row by row directly in the Amplification UI), these rows can be updated via the **Upload CSV** functionality. - To prevent unnecessary modification, you can: 1. Download the amplification data in its entirety. 2. Make the necessary changes directly in the CSV. 3. Clear all of the data in the amplification and then re-upload. :::hint{type="info"} If you have any additional questions or require additional help, please reach out to [help@chord.co](mailto\:help@chord.co)! ::: ## Available Templates Listed in alphabetical order: | **Template Name** | **Fields Included** | **Notes** | **Release Date** | | -------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------ | | [Advertising Spend](https://docs.chord.co/advertising-spend) | Required fields: source, date, spend | This configuration enables you to include advertising spend for sources that are not able to be connected directly to data connectors, such as podcasts, newsletters, etc. | July 8, 2024 | | [Attribution Channel Mapping](https://docs.chord.co/attribution-channel-mapping) | At least one channel plus the condition | This configuration maps user-defined Channels and Sub-Channels to page utm and referrer details. | July 12, 2024 (select tenants) | | [Campaign Mapping](https://docs.chord.co/campaign-mapping) | Required field: Campaign Name | This configuration maps the campaign name to different attributes. It allows for only one row per campaign. | October 25, 2024 | | [Order App Name](https://docs.chord.co/order-app-name) | Order App ID | Only available to Chord Performance (Shopify) brands. This configuration maps the order app id from Shopify to a user-defined name. | July 8, 2024 | | [Order Filter ](https://docs.chord.co/order-filter) | At least one condition is required | This configuration applies specific conditions to create a flag for orders in the Orders, Line Items, and Sales Explores. This configuration is designed to flag orders you want to filter out. | July 8, 2024 | | [Planned Forecasts](https://docs.chord.co/planned-forecasts) | Required fields: Date and Forecast Version Name
| This configuration allows Chord Performance brands to upload their daily planned forecasts of gross and net revenue, along with number of orders and number of customers. | January 22, 2024 | | [Variant Attributes](https://docs.chord.co/variant-attributes) | Required fields: SKU, product name, variant name, and existing hierarchy fields (product type, product\_sub\_type) | This configuration maps additional attributes per variant that may not be available in the OMS, including hierarchy, size, function, and color
**Please note that this configuration only allows for one row per variant.** | July 8, 2024 | [title] Scheduling Reports [path] Chord Data Platform/Analytics Features/ :::ExpandableHeading ### Introduction Suppose you are looking to send metrics once or regularly automatically. Great news! Our platform allows you to save reports, both custom and out-of-the-box views, to your teammate's inboxes without requiring logins for your teammates. ::: :::ExpandableHeading ### Schedule a report The platform empowers you to schedule your report to send to yourself and/or others on a flexible basis in various formats. Let's go ahead and select a report that you have previously saved. To open the scheduler, click the ellipsis on the top right and select "Schedule delivery." ![](https://archbee-image-uploads.s3.amazonaws.com/iCsIrWE2VP6jmzs1DjUUy-daZK4nVCHLIuP8YscN9G9-20241205-211422.png) You will be directed to the "Schedule Delivery" window to set your schedule options. ![](https://archbee-image-uploads.s3.amazonaws.com/iCsIrWE2VP6jmzs1DjUUy-1z10w6JXCPFVWDKgmJL9A-20241205-211559.png) For the schedule options: - Schedule Name (optional): The schedule name defaults to the report name but can be customized to any desired name. - Recurrence: The default is daily, but the dropdown allows numerous other options. You can then choose your preferred send time. - Destination: Email (required) - Email address: This will default to your email address, but you can add or remove any desired email addresses. - Format: The default is PDF, and you can switch this to CSV or PNG visualization. There is also a "Filters" tab for optional filters that can be defined. The filters will only display the filters applied to your dashboard. If you want to add an additional filter, you must first add it to the dashboard. ![](https://archbee-image-uploads.s3.amazonaws.com/iCsIrWE2VP6jmzs1DjUUy-X4TtRbSwjkBGaA2sfc35E-20241205-212826.png) There is an "Advanced" tab for options like adding custom messages, customizing results or values, or changing your delivery timezone. ::: ![](https://archbee-image-uploads.s3.amazonaws.com/iCsIrWE2VP6jmzs1DjUUy-rpYgSMH-UDVokICkrxlkX-20241205-212942.png) Once you've configured your options, you can send a test send with "Test now," if you wish, or save the schedule by clicking "Save." [title] Planned Forecasts [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 Chord Performance brands can now upload their daily planned forecasts of gross and net revenue along with number of orders and number of customers. With this, brands can now track their store performance comparing their forecasts with actuals. # How It Works This amplification enables the input of data at varying levels of detail. 1. The fields `Date` and `Forecast Version Name `are **required **and cannot be left blank.  2. The fields `Is New Customer,` `Variant Product Category`, and `Variant Product Subcategory` can be left blank to forecast different level of details: 1. When `Is New Customer` is left blank it will be considered as ***All type of customers***, meaning both new and returning customers. 2. When `Variant Product Category` is left blank it will be considered as ***All product categories****.* 3. When `Variant Product Subcategory` is left blank it will be considered as ***All product subcategories.*** 3. Fill the rest of the fields with the forecasted value. Take into account the definition of each metric: 1. **Gross Revenue:** Gross revenue of the orders calculated as **item\_total + fulfillment\_total** 2. **Net Revenue:** Net revenue of the orders calculated as **item\_total + fulfillment\_total - promo\_total - refund\_total** 3. **Fulfillment Total:** The total shipping revenue 4. **Promo Total:** The total discounts applied to the price of the order 5. **Refund Total:** The total refund transactions applied to the order Based on the above, there are six (6) possible levels of detail in this amplification (with each level's required attribute(s)): - **Total Daily Forecast** - *No fields required* - **Customer Type Daily Forecast** - `Is New Customer` - **Subcategory Daily Forecast** - `Variant Product Subcategory` - NOTE: If the `Variant Product Subcategory` is filled, the corresponding `Variant Product Category` must be filled as well, otherwise it will appear as **NOT-PROVIDED**. - **Category Daily Forecast** - `Variant Product Category` - **Customer Type by Category Forecast** - `Is New Customer` - `Variant Product Category` - **Full Detail Forecast** - `Is New Customer` - `Variant Product Category` - `Variant Product Subcategory` # Planned Forecasts Variances Explore ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-do69ktc5YZm3I7h9N_Nqm-20250129-211725.png) With this amplification, Performance brands now have the ability to log forecasts at different levels of detail and can have several different forecast versions (tracked via the `Forecast Version Name` in the amplification). To correctly visualize the data and the variance metrics, you must first filter the explore by selecting one value for **Level Of Detail **and one for **Forecast Version Name** (both of these fields are under the group **Forecast Parameters**). Once the filters are set, you can drag and drop the desired dimensions and metrics. [title] Messaging Lists [path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Shopify/ | **Name** | **Description** | | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 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. | | 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. | [title] Conversions [path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Shopify/ ### 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. | | 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. | | Ts (Universal) | Timestamps representing when the order was completed - Universal Time Zone. | | Average Completed Order Count | Total count of orders completed per day, according to the orders' latest state. Orders are considered complete if they have been fulfilled. | | Average Created Order Count | Total count of orders created per day. | | Average Gross Revenue | Total gross revenue of orders completed per day. Gross revenue calculated as \`item\_total\` + \`fulfillment\_total\` | | Average Gross Sales | | | Average Net Revenue | Total gross revenue of orders completed per day. Net revenue of the order calculated as \`item\_total\` + \`fulfillment\_total\` - \`promo\_total\` - \`refund\_total\` | | Average Placed Gross Revenue | Total gross revenue of orders placed per day. Gross revenue calculated as \`item\_total\` + \`fulfillment\_total\` | | Average Placed Net Revenue | Total gross revenue of orders placed per day. Net revenue of the order calculated as \`item\_total\` + \`fulfillment\_total\` - \`promo\_total\` - \`refund\_total\` | | Completed Order Count | Total count of orders completed per day, according to the orders' latest state. Orders are considered complete if they have been fulfilled. | | Created Order Count | Total count of orders created per day. | | Gross Revenue | Total gross revenue of orders completed per day. Gross revenue calculated as \`item\_total\` + \`fulfillment\_total\` | | Gross Sales | | | Net Revenue | Total gross revenue of orders completed per day. Net revenue of the order calculated as \`item\_total\` + \`fulfillment\_total\` - \`promo\_total\` - \`refund\_total\` | | Placed Gross Revenue | Total gross revenue of orders placed per day. Gross revenue calculated as \`item\_total\` + \`fulfillment\_total\` | | Placed Net Revenue | Total gross revenue of orders placed per day. Net revenue of the order calculated as \`item\_total\` + \`fulfillment\_total\` - \`promo\_total\` - \`refund\_total\` | [title] Predictive Models [path] Chord Data Platform/ Chord's predictive models are generated with machine learning to provide predictive outputs for analysis, advanced segmentation, and personalization. Predictive models are continuing to expand and currently include the following: ::::LinkArray{contentSource="CUSTOM"} :::LinkArrayItem{headerType="COLOR" headerColor="#f00bf3"} [Customer Lifetime Revenue](docId:7C0gpeaYBzjwGadO3t2ib) ::: :::LinkArrayItem{headerType="COLOR" headerColor="#0af130"} [Product Recommendations](https://docs.chord.co/product-recommendations) ::: :::LinkArrayItem{headerType="COLOR" headerColor="#0a27f1"} [Revenue Forecasts](docId\:L91UpCbIucX4huAP2ByfI) ::: :::LinkArrayItem{headerType="COLOR" headerColor="#82EBFB"} [Session Conversion Probability](https://docs.chord.co/session-conversion-probability) ::: :::LinkArrayItem{headerType="COLOR" headerColor="#FFF85C"} [Predictive Marketing Attribution](https://docs.chord.co/predictive-marketing-attribution) ::: :::LinkArrayItem{headerType="COLOR" headerColor="#C3F45C"} [Marketing Mix Modeling](https://docs.chord.co/marketing-mix-modeling-mmm) ::: :::: [title] Order App Name [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 Shopify records the ID of the App that creates an order as the `app_id`. Brands want to be able to set the name associated with the id for easier readability and functionality in reporting. Some apps may be defined by the `source_name` while others are null. ## Sample Use Case This configuration allows Shopify brands to easily add or update their `app_ids`. If new apps are utilized by the brand, the new ID and name just need to be added to the configuration and will then process in the next scheduled data run. [title] Advertising Spend [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 Many advertising sources provide direct connections to our data warehouse, like Facebook, Google, Pinterest, TikTok, and YouTube. But what if your brand spends advertising dollars on other sources? The Advertising Spend configuration allows you to include any source in our Ads modeling. All that's needed to include a source is the date of the spend, the amount spent, and the name of the source. This allows the model to capture a high-level view of the spend by source. Unlike connected data sources, the configuration is limited to overall spend per source and does not drill down into more detailed information on campaign or metrics like views, clicks, and impressions. ## Sample Use Case Brands can easily extend their enriched Chord data set to include Ad Spend data and answer more robust business questions about return on investment by channel, campaign, and even demonstrate product interests by channel. [title] Marketing Attribution [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. | ### extend\_x\_fct\_trans\_orders\_for\_attribution | Name | Description | | --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Days From Order to First Fulfillment | Number of days between order creation and first fulfillment. | | Order Bill To Contact Id | ID of the Contact associated with the Order Summary. It represents the shopper in the storefront when not using person accounts. | | Order Billing City | Billing address city. | | Order Billing Country | Billing address country. | | Order Billing Email Address | Email address on the billing address. | | Order Billing State | Billing address state | | Order Billing State Country | The billing state or country of the order. Default to billing country if state is unavailable. | | Order Currency Iso Code | Available only for stores with the multicurrency feature enabled. Contains the ISO code for the currency of the original Order associated with the Order Summary. The default value is USD. Possible values are: DKK—Danish Krone, EUR—Euro, GBP—British Pound, USD—U.S. Dollar | | Order First Fulfillment Created At (Universal) Time | Timestamp when the first fulfillment for the order was created - Universal Time Zone. | | Order First Order Created At (Universal) Date | Timestamp when the first order was created at - Universal Time Zone. | | Order First Order Created At (Universal) Month | Timestamp when the first order was created at - Universal Time Zone. | | Order First Order Created At (Universal) Quarter | Timestamp when the first order was created at - Universal Time Zone. | | Order First Order Created At (Universal) Time | Timestamp when the first order was created at - Universal Time Zone. | | Order First Order Created At (Universal) Week | Timestamp when the first order was created at - Universal Time Zone. | | Order First Order Created At (Universal) Year | Timestamp when the first order was created at - Universal Time Zone. | | Order Fulfillment Ids | IDs generated by Chord to identify the fulfillments associated with the order. | | Order Fulfillment Numbers | The fulfillment numbers associated with the order. | | Order Fulfillment Statuses | The fulfillment statuses associated with the order. | | Order Has A Shipped Fulfillment (Yes / No) | A flag marking if an order has a shipped fulfillment. | | Order Hours To First Delivery | The number of hours between when the order was created and the first fulfillment was created. | | Order Hours To Last Delivery | The number of hours between when the order was created and the last, most recent, fulfillment was created. | | Order Is Canceled (Yes / No) | Whether an order is canceled. | | Order Is Completed (Yes / No) | Whether an order is 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. | | Order Is First Order (Yes / No) | Whether the order is first order associated with the account. | | Order Last Fulfillment Created At (Universal) Time | Timestamp when the most recent, or last, fulfillment for the order was created - Universal Time Zone. | | Order Last Modified Date (Universal) Date | The date the Order Summary was last modified - Universal Time Zone | | Order Number | Name of the Order Summary. | | Order Number Of Fulfillments | The total number of fulfillments associated with the order. | | Order Number Of Reimbursements | The number of reimbursements associated with an order. | | Order Oms Account Id | ID of the account or person account associated with the Order Summary. It represents the shopper in the storefront. | | Order Oms Fulfillment Ids | ID generated by the OMS to identify the order. | | Order Oms Order Id | The id generated by the OMS for the Order Summary. | | Order Oms Order Payment Summary Ids | IDs generated by the OMS to identify the payment summaries associated with the order. | | Order Oms Return Order Ids | IDs generated by the OMS to identify the returns associated with the order. | | Order Ordered Date (Universal) Date | Date of the original order associated with this Order Summary - Universal Time Zone. | | Order Payment Methods | The payment methods associated with the order. | | Order Payment Summary Ids | IDs generated by Chord to identify the payment summaries associated with the order. | | Order Payment Types | The payment types associated with the order. | | Order Po Number | Purchase order number associated with this Order Summary. | | Order Promotion Details Collection | The promotion details associated with the Order Summary. | | Order Return Order Ids | IDs generated by Chord to identify the returns associated with the order. | | Order Return Order Numbers | The return order numbers associated with the order. | | Order Sales Channel Id | ID of the Sales Channel associated with this Order Summary. | | Order Status | Status of the order summary. Unlike the Status and Status Category fields on the order and Fulfillment Order objects, this field is optional. | | Order Tax Locale Type | The system used to handle tax on the original Order associated with the Order Summary. Gross usually applies to taxes like value-added tax (VAT), and Net usually applies to taxes like sales tax. Possible values are: Gross (displays most prices and taxes as combined values), Net (displays most prices and taxes as separate values). | | Order Utm Campaign | The UTM Campaign associated with the Order Summary. | | Order Utm Medium | The UTM Medium associated with the Order Summary. | | Order Created At (Central) Date | The date the Order Summary was created - Cental Time Zone. | | Order Created At (Central) Month | The date the Order Summary was created - Cental Time Zone. | | Order Created At (Central) Quarter | The date the Order Summary was created - Cental Time Zone. | | Order Created At (Central) Time | The date the Order Summary was created - Cental Time Zone. | | Order Created At (Central) Week | The date the Order Summary was created - Cental Time Zone. | | Order Created At (Central) Year | The date the Order Summary was created - Cental Time Zone. | | Order Created At (Eastern) Date | The date the Order Summary was created - Eastern Time Zone. | | Order Created At (Eastern) Month | The date the Order Summary was created - Eastern Time Zone. | | Order Created At (Eastern) Quarter | The date the Order Summary was created - Eastern Time Zone. | | Order Created At (Eastern) Time | The date the Order Summary was created - Eastern Time Zone. | | Order Created At (Eastern) Week | The date the Order Summary was created - Eastern Time Zone. | | Order Created At (Eastern) Year | The date the Order Summary was created - Eastern Time Zone. | | Order Created At (Mountain) Date | The date the Order Summary was created - Mountain Time Zone. | | Order Created At (Mountain) Month | The date the Order Summary was created - Mountain Time Zone. | | Order Created At (Mountain) Quarter | The date the Order Summary was created - Mountain Time Zone. | | Order Created At (Mountain) Time | The date the Order Summary was created - Mountain Time Zone. | | Order Created At (Mountain) Week | The date the Order Summary was created - Mountain Time Zone. | | Order Created At (Mountain) Year | The date the Order Summary was created - Mountain Time Zone. | | Order Created At (Pacific) Date | The date the Order Summary was created - Pacific Time Zone. | | Order Created At (Pacific) Month | The date the Order Summary was created - Pacific Time Zone. | | Order Created At (Pacific) Quarter | The date the Order Summary was created - Pacific Time Zone. | | Order Created At (Pacific) Time | The date the Order Summary was created - Pacific Time Zone. | | Order Created At (Pacific) Week | The date the Order Summary was created - Pacific Time Zone. | | Order Created At (Pacific) Year | The date the Order Summary was created - Pacific Time Zone. | | Order Created At (Universal) Date | The date the Order Summary was created - Universal Time Zone. | | Order Created At (Universal) Month | The date the Order Summary was created - Universal Time Zone. | | Order Created At (Universal) Quarter | The date the Order Summary was created - Universal Time Zone. | | Order Created At (Universal) Time | The date the Order Summary was created - Universal Time Zone. | | Order Created At (Universal) Week | The date the Order Summary was created - Universal Time Zone. | | Order Created At (Universal) | The date the Order Summary was created - Universal Time Zone. | ### user\_completed\_oms\_order\_ids | Name | Description | | ---------------------------- | ----------- | | User Completed Oms Order Ids | | [title] Session Conversion Probability [path] Chord Data Platform/Predictive Models/ ### Introduction Session Conversion Probability refers to predicting the likelihood that a customer will purchase during their session. Chord’s session conversion probability feature leverages your store’s data into deep insights about your customers’ behavior. In turn, this rich data can help operators, marketers, and analysts to create and optimize business strategies to improve conversion rates to bolster your store’s performance. ### How the Model Works Chord’s session conversion probability feature takes data inputs from session activity and session events and page views to create the predictive models. We model session conversion as a function of session activity (including activity count, session duration, time of session, and device) and marketing inputs (such as source, channel, and medium). ### Interpreting Chord’s Conversion Probability This new predictive feature is composed of the following summary statistics: - **Session activity count:** Marketers can compare session activity counts understand likelihood to convert. Chord will provide different buckets of session activity counts and the conversion predictions. This is different than the metrics related to `Number of Sessions` (see below). - **Session duration:** Chord’s session conversion probability will display a chart that shows conversion probability associated with different session durations. - **Number of Sessions:** This value refers to the the aggregate number of sessions for an anonymous user ID. - **Has Referral:** This value indicates if the first page event of the session has a referrer host. - **Has UTM:** This measure indicates if the session first page has a UTM. - **Has GCLID:** Similar to `Has UTM`, this measure indicates that first session has a Google click ID. - **Device Type:** Displays session conversions by device used (ex. desktop, tablet, Android, iPhone). - **Session Attribution Channel:** Displays session conversions by attribution channel (ex. SMS, e-mail, organic search, paid search, etc). - **Session Medium:** Displays session conversions by session medium (ex. Affiliate, CPC, e-mail, paid, etc). - **Session Source:** Displays session conversion by session source (TikTok, Instagram, Facebook, Google, etc). - **Paid or Organic Search:** Displays session conversion by paid or organic search. ### Use Cases and Applications Chord’s session conversion predictions can be applied to many business scenarios. A few examples are included below. - **On-Site Personalization:** Brands can dynamically adjust the customer experience in real-time using Chord’s session conversion predictions. For example, stores can offer a discount code if conversion probability is high using Chord's Audiences API. - **Personalized Marketing:** Similar to adjusting customer experience in real-time, brands can use Chord’s predictive feature to send targeted offers or reminders to customers to further engage them to get them closer to checking out. - **Ad Spend Optimization:** Take advantage of high-probability conversion sessions by setting up smart retargeting efforts via ad spend. ### Getting Started The session prediction feature is available for all Chord brands that are qualified to unlock our baseline data science features. Brands must have the following requirements: - 2,000 completed CDP-attributed session transactions; - At least 90 days of event data collected through our CDP; - At least 200k sessions; and - Session conversions greater than or equal to 1% (or, at least 2k converted sessions). If you have any questions, please reach out to your account manager. ### Glossary - **Session:** A time-bounded period during which an anonymous user interacts with your website. - **Conversion:** When a session results in a paid event, such as a checkout or subscription. [title] Ads [path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Shopify/ ### 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] Marketing Attribution [path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Shopify/ ### x\_fct\_trans\_order | 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. | | First Fulfillment Id | Unique identifier for a Shopify Fulfillment at a specific point in time | | First Fulfillment Oms Fulfillment Id | Unique key generated by Shopify that identifies a fulfillment. | | First Fulfillment Shipment Status | Represent the status of the shipment. | | First Fulfillment Status | The status of the fulfillment. | | First Fulfillment Tracking Company | The name of the tracking company. | | First Fulfillment Tracking Numbers | A list of tracking numbers provided by the tracking company. | | First Fulfillment Tracking Urls | The URLs of tracking pages for the fulfillment. | | Last Transaction Amount | The amount of money included in the transaction. | | Last Transaction Error Code | The error code explaining why the transaction failed. | | Last Transaction Gateway | The name of the gateway the transaction was issued through. | | Last Transaction Id | Unique identifier for a Shopify Transaction at a specific point in time | | Last Transaction Is Failed | Whether or not the transaction / payment has failed. | | Last Transaction Is Successful | Whether or not the transaction / payment has succeeded. | | Last Transaction Is Test | Whether this is a test transaction or not. | | Last Transaction Kind | The type of transaction. | | Last Transaction Message | Additional information provided the payment provider about the transaction. | | Last Transaction Oms Transaction Id | Unique key generated by Shopify that identifies a transaction. | | Last Transaction Status | The status of the transaction. | | Location Id | Unique identifier for a Shopify Location at a specific point in time | | Location Is Active | Whether the location is active or not. | | Location Is Online | Whether or not this location represents an online location. | | Location Is Physical | Whether or not this location represents a physical location. | | Location Name | The name of a location. | | Location Oms Location Id | Unique key generated by Shopify that identifies a location. | | Order Admin Url | Contains the full URL directing to the admin dashboard of Shopify for that given order. | | Order App Id | The ID of the app from Shopify that created the order. | | Order App Name | App name associated with the app id. This field will be generated if the Hub Configuration is enabled and the value has been set. | | Order Applied Discount Codes | The discount 'codes' applied or a given order. | | Order Applied Discount Codes Count | The total number of applied discount code for a given order. | | Order Cancel Reason | The reason as to why the order was cancelled. | | Order Cart Website Locale | When available, this is the shopify international site activated prior to cart creation. | | Order Completed Order Rank By User | Allows to rank customer carts by completion date. In other words, this will rank the customer's completed order from 1 to X (X being the most recent order that was completed). | | Order Completed Subscription Order Rank By User | Allows to rank customer subscription orders by completion date. | | Order Contains First Subscription Order | A boolean value to indicate whether an order contains the first subscription order or not. An order may contain a mix of first and recurring subscriptions. | | Order Created Order Rank By User | Allows to rank customer carts by creation date. In other words, this will rank the customer's creation order from 1 to X (X being the last order that was created). An order can be created but never completed. | | Order Created Subscription Order Rank By User | Allows to rank customer subscription orders by creation date. | | Order Customer Lifetime Month | Number of months between the current order's creation date and the user's first order creation date. First orders have a value of 1. | | Order Customer Lifetime Week | Number of weeks between the current order's creation date and the user's first order creation date. First orders always have a value of 1. | | Order Filtered Order | Whether or not this order will be flagged by custom filter. | | Order Financial State | The status of transaction associated with the order. | | Order Fulfillment State | The summarized status of the 'shipment/fulfillment' associated with the order. | | Order Has Discount | Whether or not the order has had a discount applied to it. | | Order Has Order Tag | Whether or not the order has an order tag applied to it. | | Order Id | Unique identifier generated by Chord for an order. | | Order Included Fulfillment Codes | Aggregated array of fulfillment codes, represented as a string. | | Order Included Fulfillment Methods | Aggregated array of fulfillment methods, represented as a string. | | Order Included Payment Gateways | This is the rolled up successful payment gateway for an order. Successful payments are included if they are sale or capture transactions. | | Order Included Source Subscription Ids | String list of included source subscription ids per order. Subscription information received from tenant-enabled platforms including Recharge and Shopify Plus. | | Order Included Subscription Ids | String list of included subscription ids per order. Subscription information received from tenant-enabled platforms including Recharge and Shopify Plus. | | Order Is Admin | Whether or not the order was created by an admin. | | Order Is Cancelled | Whether or not the order was cancelled. If \`cancelled\_at\` is non-null then we consider the order has being cancelled. | | Order Is Completed | Whether or not the order was completed. An order is considered completed if it has a closed\_at timestamp and has been fully fulfilled. Closed\_at 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. | | Order Is First Completed Order | Whether the order was the customer's first completed order or not. | | Order Is First Order | Whether the order was the customer's first order or not. | | Order Is First Subscription Completed Order | Whether the order was the customer's first completed subscription order or not. | | Order Is First Subscription Order | Whether the order was the customer's first subscription order or not. | | Order Is Part Of Subscription | Boolean flag to indicate whether the order was a part of a subscription plan or not. | | Order Is Test | Whether this is a test order or not. | | Order Item Id | Unique identifier generated by Chord for an order. | | Order Item Is First Product Type Order | Whether this order contains the first product type basket for the user. | | Order Item Is Last Product Type Order | Whether this order contains the last, most recent, product type basket for the user. | | Order Item Is Repeat Product Type Order | Whether this order contains a repeat product type basket for the user. | | Order Item Product Basket Count | The count of products for a given order. | | Product Basket | The titles of products for a given orderarray converted to a string. | | Order Item Product Purchased Quantity | The total number of product purchased for a given order. | | Order Item Rank Product Type Order | Rank orders with the same product type basket per user. | | Order Item Unique Product Basket Count | The count of unique products for a given order. | | Unique Product Basket | The unique titles of products for a given order array converted to a string. | | Order Item Unique Product Type | The unique line item product types for a given order. | | Order Item Unique Variant Basket Count | The count of unique SKUs for a given order. | | Unique Variant Basket | The unique SKUs of variants for a given order array converted to a string. | | Order Item Variant Basket Count | The count of variants for a given order. | | Variant Basket | The SKUs of variants for a given order array converted to a string. | | Order Item Variant Purchased Quantity | The total number of variants purchased for a given order. | | Order Name | Unique name generated by Shopify that is displayed to the customer (e.g. | | Order Number Of Non Reactivated Subscriptions | Number of non reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Order Number Of Reactivated Subscriptions | Number of reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Order Oms Order Id | Unique key generated by Shopify that identifies an order. | | Order Tags | The order tags applied to a given order, in alphabetical order. | | Order Tags Count | The total number of order tags for a given order. | | Order Processing Method | How the payment was processed. | | Order Segment Anonymous Id | When available, this is where we store Segment's anonymous\_id at the time of checkout. | | Order Source Name | Where did the order get created from. | | 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. | | 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 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. | | Order Cancelled At (Universal) | Reflects when the order was cancelled in Shopify - Universal Time Zone. | | Order Completed At (Central) | The timestamp when this order became completed - Cental Time Zone. | | Order Completed At (Eastern) | The timestamp when this order became completed - Eastern Time Zone. | | Order Completed At (Mountain) | The timestamp when this order became completed - Mountain Time Zone. | | Order Completed At (Pacific) | The timestamp when this order became completed - Pacific Time Zone. | | Order Completed At (Universal) | The timestamp when this order became completed - Universal Time Zone. | | Order Created At (Central) | Reflects when the entity was first created in Shopify - Cental Time Zone. | | Order Created At (Eastern) | Reflects when the entity was first created in Shopify - Eastern Time Zone. | | Order Created At (Mountain) | Reflects when the entity was first created in Shopify - Mountain Time Zone. | | Order Created At (Pacific) | Reflects when the entity was first created in Shopify - Pacific Time Zone. | | Order Created At (Universal) | Reflects when the entity was first created in Shopify - Universal Time Zone. | | Order Last Fulfillment At (Universal) | The maximum timestamp for the last update order fulfillment - Universal Time Zone. | | Order Updated At (Universal) | Reflects when the entity was last updated in Shopify - Universal Time Zone. | | 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 Additional Tax Total | When taxes are not included in the subtotal, this is total tax added to the order. | | Average Fulfillment Tax Total | Total tax applied to the order's fulfillment fee. | | 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 Line Item Tax Total | Total tax applied to the line items of the 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 Non Reactivated Subscription Unit Total | Sum of unit price for non reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Average Payment Capture Total | Sum of successful capture transactions. | | Average Payment Total | Sum of all sales transaction with gateway of type 'shopify\_payments'. | | Average Product Basket Count | The count of products for a given order. | | Average Product Purchased Quantity | The total number of product purchased for a given order. | | Average Promo Total | The total discounts applied to the price of the order in the location's currency. | | Average Reactivated Subscription Unit Total | Sum of unit price for reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Average Refund Total | Sum of all the transactions that are of kind 'refund' applied to the order. | | Average Tax Total | The sum of all the taxes applied to the order in the location's currency. | | Average Total Price | The sum of all line item prices, discounts, shipping, taxes, and tips in the | | Average Transaction Total | Sum of all sale transactions for the order. | | Average Variant Basket Count | The count of variants for a given order. | | Average Variant Purchased Quantity | The total number of variants purchased for a given order. | | Additional Tax Total | When taxes are not included in the subtotal, this is total tax added to the order. | | Fulfillment Tax Total | Total tax applied to the order's fulfillment fee. | | 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. | | Line Item Tax Total | Total tax applied to the line items of the 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\` | | Non Reactivated Subscription Unit Total | Sum of unit price for non reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Payment Capture Total | Sum of successful capture transactions. | | 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 | | Product Basket Count | The count of products for a given order. | | Product Purchased Quantity | The total number of product purchased for a given order. | | Promo Total | The total discounts applied to the price of the order in the location's currency. | | Reactivated Subscription Unit Total | Sum of unit price for reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Refund Total | Sum of all the transactions that are of kind 'refund' applied to the order. | | 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. | | Variant Basket Count | The count of variants for a given order. | | Variant Purchased Quantity | The total number of variants purchased for a given order. | ### x\_fct\_acc\_anonymous | 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. | | Current User Address 1 | The first line of the street address. | | Current User Address 2 | The optional second line of the address. | | Current User Address City | The city of the address. | | Current User Address Country | The country of the address. | | Current User Address Name | The full name of the customer, based on firstName and lastName. | | Current User Address State | The region of the address, such as the province, state, or district. | | Current User Address Zip | The postal code of the address. | | Current 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. | | Current 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. | | Current 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. | | Current User Email | The email associated with the user. | | Current 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. | | Current 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` ]. | | Current User Ip | IP address associated with the user. | | Current 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` ]. | | Current User Last Segment Anonymous Id | This column is not documented. | | Current User Segment User Id | The unique ID of the user. | | Current 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` ]. | | Current 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. | | First Page Browser Locale | Locale of browser. | | First Page Date Day Num Of Year | The number representing the day of the year. | | First Page Date Id | Unique key that uniquify a date. | | First Page Date Month Num Of Year | The month number of the year. | | First Page Device | The device on which the event was sent from. | | First 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', | | First Page Event Table Name | The properly formatted name of the table of the event. | | First Page Event Text | The name of the event. | | First Page Event Text Id | The slug of the event name, mapping to the page or track event table. | | First 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. | | First Page Id | Unique key generated by Segment for each tracking or page event. | | First Page Oms Id | Unique key generated by our models that uniquifies an OMS. | | First 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. | | First 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`.) | | First Page Query | The query string portion of the URL of the page. | | First Page Referrer | The referrer of the page. The referrer is the webpage that sends visitors to the site using a link. In | | First Page Title | The title/name of the page. | | First Page Url | The URL of the page. | | First 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. | | First Page Segment User Id | The unique ID of the user. | | First Page Store Id | Unique key generated by our models that uniquifies a store. | | First Page Tenant Id | Unique key generated by Chord that uniquifies a tenant. | | First 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 | | First Page User Id | Unique key generated by Chord to identify the user. | | First Page Utm Campaign | The campaign name represented by the UTM tags. | | First Page Utm Content | The campaign content represented by the UTM tags. | | First Page Utm Medium | The campaign medium represented by the UTM tags. | | First Page Utm Source | The campaign source represented by the UTM tags. | | First Page Utm Term | The campaign term represented by the UTM tags. | | First Page Website Locale | Locale of website. This will either be collected from the url or from the drop-down link on the store | | First Session Activity Count | Total count of activities, pave views and tracked events within the session. | | First 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. | | First 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'. | | First Session Attribution First Page Url Has Gclid | Indicates if the first page event of the session has a Google Click ID. | | First Session Attribution First Page Url Has Utm | Indicates if the first page event of the session has any utm information. | | First Session Attribution Has Referrer | Indicates if the first page event of the session has a referrer host. | | First Session Attribution Medium | The campaign medium represented by the UTM tags for the first page event of the session. | | First Session Attribution Source | The campaign source represented by the UTM tags for the first page event of the session. | | First Session Attribution Sub Channel | Sub-Channel is a granular level of attribution. | | First 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. | | First Session Completed Order Ids | Array of order IDs associated to the session\_id, as collected by order completed or checkout completed front-end events. | | First Session Completed Order Numbers | Array of order numbers associated to the session\_id, as collected by order completed or checkout completed front-end events. | | First Session Days Since Last Session End | The days between the last session's end and the start of this session. | | First Session Device | The device on which the event was sent from. | | First 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', | | First Session Duration In Seconds | Total seconds between start and end activities within the session. | | First 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. | | First Session Has Order Completion | Flag for sessions with an order completed or checkout completed front-end events | | First Session Id | Unique ID for the session. | | First Session Number | Session number per anonymous id. | | First 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. | | First 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. | | Last Page Browser Locale | Locale of browser. | | Last Page Date Day Num Of Year | The number representing the day of the year. | | Last Page Date Id | Unique key that uniquify a date. | | Last Page Date Month Num Of Year | The month number of the year. | | 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 | | 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. | | Current User Created At (Universal) | The timestamp when the user was created - Universal Time Zone. | | Current 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. | | First Page Ts (Universal) | The timestamp calculated by Segment correcting clock skew - Universal Time Zone. | | First Session End Ts (Universal) | Last activity timestamp for a session - Universal Time Zone. | | First 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. | | First 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. | | First Session Start Ts (Central) | First activity timestamp for a session - Cental Time Zone. | | First Session Start Ts (Eastern) | First activity timestamp for a session - Eastern Time Zone. | | First Session Start Ts (Mountain) | First activity timestamp for a session - Mountain Time Zone. | | First Session Start Ts (Pacific) | First activity timestamp for a session - Pacific Time Zone. | | First Session Start Ts (Universal) | First activity timestamp for a session - Universal Time Zone. | | Last Page Ts (Universal) | The timestamp calculated by Segment correcting clock skew - Universal Time Zone. | | User Anonymous Last Seen Ts (Central) | The last timestamp the anonymous ID was registered, seen, on the site - Cental Time Zone. | | User Anonymous Last Seen Ts (Eastern) | The last timestamp the anonymous ID was registered, seen, on the site - Eastern Time Zone. | | User Anonymous Last Seen Ts (Mountain) | The last timestamp the anonymous ID was registered, seen, on the site - Mountain Time Zone. | | User Anonymous Last Seen Ts (Pacific) | The last timestamp the anonymous ID was registered, seen, on the site - Pacific Time Zone. | | User Anonymous Last Seen Ts (Universal) | The last timestamp the anonymous ID was registered, seen, on the site - Universal Time Zone. | [title] Sales [path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Shopify/ ### extend\_x\_fct\_trans\_orders\_multipay | Name | Description | | ------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Order Contains Fulfillment Order | Whether the order contains a fulfillment order. | | Order Contains Multipay Subscription Installment | Whether the order contains a multipay order. | | Order Contains Payment Order | Whether the order contains a payment order. | | Order Installment Charge Ids | Array of Recharge charge ids for the installments in the order, if there is more than one multipay subscription represented, there will be a unique array per installment. | | Order Installment Recharge Order Ids | Array of Recharge order ids for the installments in the order, if there is more than one multipay subscription represented, there will be a unique array per installment. | | Order Installment Shopify Order Ids | Array of the Shopify order ids for the installments in the order, if there is more than one multipay subscription represented, there will be a unique array per installment. | | Order Included Installment Count | Count of total installments in the order. | | Order Included Payment Plans | Array of payment plans included in the order. If an order contains multiple subscriptions, each subscription will be represented. | | Average Total Child Refunds | The total adjusted dollars that were refunded to a child installment order for paid orders. | | Average Total Child Shipping Received | Total shipping paid for child orders within an installment. Shipping is included for the first installment order of a child-only order if the order is mixed. If the order contains a fulfillment order, the shipping will remain attached to the fulfillment order. | | Average Total Child Unit Price Received | The total unit price received for child order payments for the installment. Payments are included if the payment status is recorded as 'success', 'refunded', or 'partially\_refunded'. | | Average Total Fulfillment Unit Price Received | The total unit price received for fulfillment order payments for the installment. Payments are included if the payment status is recorded as 'success', 'refunded', or 'partially\_refunded'. | | Average Total Subscription Installment Value | The total unit price of the installment, calculated as fulfillment order (unit price \* quantity) \* total expected payments. | | Average Total Unit Price Remaining | The total installment value minus the total fulfillment and child payments received. | | Average Total Estimated Shipping Price | The total estimated shipping across all installments in the order. | | Average Total Estimated Item Tax | The total estimated item tax across all installments in the order. | | Average Total Estimated Shipping Tax | The total estimated shipping tax across all installments in the order. | | Total Child Refunds | The total adjusted dollars that were refunded to a child installment order for paid orders. | | Total Child Shipping Received | Total shipping paid for child orders within an installment. Shipping is included for the first installment order of a child-only order if the order is mixed. If the order contains a fulfillment order, the shipping will remain attached to the fulfillment order. | | Total Child Unit Price Received | The total unit price received for child order payments for the installment. Payments are included if the payment status is recorded as 'success', 'refunded', or 'partially\_refunded'. | | Total Fulfillment Unit Price Received | The total unit price received for fulfillment order payments for the installment. Payments are included if the payment status is recorded as 'success', 'refunded', or 'partially\_refunded'. | | Total Subscription Installment Value | The total unit price of the installment, calculated as fulfillment order (unit price \* quantity) \* total expected payments. | | Total Unit Price Remaining | The total installment value minus the total fulfillment and child payments received. | | Total Estimated Shipping Price | The total estimated shipping across all installments in the order. | | Total Estimated Item Tax | The total estimated item tax across all installments in the order. | | Total Estimated Shipping Tax | The total estimated shipping tax across all installments in the order. | ### x\_fct\_trans\_sales | 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. | | 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. | | First Fulfillment Id | Unique identifier for a Shopify Fulfillment at a specific point in time | | First Fulfillment Oms Fulfillment Id | Unique key generated by Shopify that identifies a fulfillment. | | First Fulfillment Shipment Status | Represent the status of the shipment. | | First Fulfillment Status | The status of the fulfillment. | | First Fulfillment Tracking Company | The name of the tracking company. | | First Fulfillment Tracking Numbers | A list of tracking numbers provided by the tracking company. | | First Fulfillment Tracking Urls | The URLs of tracking pages for the fulfillment. | | Last Transaction Amount | The amount of money included in the transaction. | | Last Transaction Error Code | The error code explaining why the transaction failed. | | Last Transaction Gateway | The name of the gateway the transaction was issued through. | | Last Transaction Id | Unique identifier for a Shopify Transaction at a specific point in time | | Last Transaction Is Failed | Whether or not the transaction / payment has failed. | | Last Transaction Is Successful | Whether or not the transaction / payment has succeeded. | | Last Transaction Is Test | Whether this is a test transaction or not. | | Last Transaction Kind | The type of transaction. | | Last Transaction Message | Additional information provided the payment provider about the transaction. | | Last Transaction Oms Transaction Id | Unique key generated by Shopify that identifies a transaction. | | Last Transaction Status | The status of the transaction. | | Location Id | Unique identifier for a Shopify Location at a specific point in time | | Location Is Active | Whether the location is active or not. | | Location Is Online | Whether or not this location represents an online location. | | Location Is Physical | Whether or not this location represents a physical location. | | Location Name | The name of a location. | | Location Oms Location Id | Unique key generated by Shopify that identifies a location. | | Order Admin Url | Contains the full URL directing to the admin dashboard of Shopify for that given order. | | Order App Id | The ID of the app from Shopify that created the order. | | Order App Name | App name associated with the app id. This field will be generated if the Hub Configuration is enabled and the value has been set. | | Order Applied Discount Codes | The discount 'codes' applied or a given order. | | Order Applied Discount Codes Count | The total number of applied discount code for a given order. | | Order Cancel Reason | The reason as to why the order was cancelled. | | Order Cart Website Locale | When available, this is the shopify international site activated prior to cart creation. | | Order Completed Order Rank By User | Allows to rank customer carts by completion date. In other words, this will rank the customer's completed order from 1 to X (X being the most recent order that was completed). | | Order Completed Subscription Order Rank By User | Allows to rank customer subscription orders by completion date. | | Order Contains First Subscription Order | A boolean value to indicate whether an order contains the first subscription order or not. An order may contain a mix of first and recurring subscriptions. | | Order Created Order Rank By User | Allows to rank customer carts by creation date. In other words, this will rank the customer's creation order from 1 to X (X being the last order that was created). An order can be created but never completed. | | Order Created Subscription Order Rank By User | Allows to rank customer subscription orders by creation date. | | Order Customer Lifetime Month | Number of months between the current order's creation date and the user's first order creation date. First orders have a value of 1. | | Order Customer Lifetime Week | Number of weeks between the current order's creation date and the user's first order creation date. First orders always have a value of 1. | | Order Filtered Order | Whether or not this order will be flagged by custom filter. | | Order Financial State | The status of transaction associated with the order. | | Order Fulfillment State | The summarized status of the 'shipment/fulfillment' associated with the order. | | Order Has Discount | Whether or not the order has had a discount applied to it. | | Order Has Order Tag | Whether or not the order has an order tag applied to it. | | Order Id | Unique identifier generated by Chord for an order. | | Order Included Fulfillment Codes | Aggregated array of fulfillment codes, represented as a string. | | Order Included Fulfillment Methods | Aggregated array of fulfillment methods, represented as a string. | | Order Included Payment Gateways | This is the rolled up successful payment gateway for an order. Successful payments are included if they are sale or capture transactions. | | Order Included Source Subscription Ids | String list of included source subscription ids per order. Subscription information received from tenant-enabled platforms including Recharge and Shopify Plus. | | Order Included Subscription Ids | String list of included subscription ids per order. Subscription information received from tenant-enabled platforms including Recharge and Shopify Plus. | | Order Is Admin | Whether or not the order was created by an admin. | | Order Is Cancelled | Whether or not the order was cancelled. If \`cancelled\_at\` is non-null then we consider the order has being cancelled. | | Order Is Completed | Whether or not the order was completed. An order is considered completed if it has a closed\_at timestamp and has been fully fulfilled. Closed\_at 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. | | Order Is First Completed Order | Whether the order was the customer's first completed order or not. | | Order Is First Order | Whether the order was the customer's first order or not. | | Order Is First Subscription Completed Order | Whether the order was the customer's first completed subscription order or not. | | Order Is First Subscription Order | Whether the order was the customer's first subscription order or not. | | Order Is Part Of Subscription | Boolean flag to indicate whether the order was a part of a subscription plan or not. | | Order Is Test | Whether this is a test order or not. | | Order Item Id | Unique identifier generated by Chord for an order. | | Order Item Is First Product Type Order | Whether this order contains the first product type basket for the user. | | Order Item Is Last Product Type Order | Whether this order contains the last, most recent, product type basket for the user. | | Order Item Is Repeat Product Type Order | Whether this order contains a repeat product type basket for the user. | | Order Item Product Basket Count | The count of products for a given order. | | Product Basket | The titles of products for a given orderarray converted to a string. | | Order Item Product Purchased Quantity | The total number of product purchased for a given order. | | Order Item Rank Product Type Order | Rank orders with the same product type basket per user. | | Order Item Unique Product Basket Count | The count of unique products for a given order. | | Unique Product Basket | The unique titles of products for a given order array converted to a string. | | Order Item Unique Product Type | The unique line item product types for a given order. | | Order Item Unique Variant Basket Count | The count of unique SKUs for a given order. | | Unique Variant Basket | The unique SKUs of variants for a given order array converted to a string. | | Order Item Variant Basket Count | The count of variants for a given order. | | Variant Basket | The SKUs of variants for a given order array converted to a string. | | Order Item Variant Purchased Quantity | The total number of variants purchased for a given order. | | Order Name | Unique name generated by Shopify that is displayed to the customer (e.g. | | Order Number Of Non Reactivated Subscriptions | Number of non reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Order Number Of Reactivated Subscriptions | Number of reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Order Oms Order Id | Unique key generated by Shopify that identifies an order. | | Order Tags | The order tags applied to a given order, in alphabetical order. | | Order Tags Count | The total number of order tags for a given order. | | Order Processing Method | How the payment was processed. | | Order Segment Anonymous Id | When available, this is where we store Segment's anonymous\_id at the time of checkout. | | Order Source Name | Where did the order get created from. | | 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. | | 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 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. | | Order Cancelled At (Universal) | Reflects when the order was cancelled in Shopify - Universal Time Zone. | | Order Completed At (Central) | The timestamp when this order became completed - Cental Time Zone. | | Order Completed At (Eastern) | The timestamp when this order became completed - Eastern Time Zone. | | Order Completed At (Mountain) | The timestamp when this order became completed - Mountain Time Zone. | | Order Completed At (Pacific) | The timestamp when this order became completed - Pacific Time Zone. | | Order Completed At (Universal) | The timestamp when this order became completed - Universal Time Zone. | | Order Created At (Central) | Reflects when the entity was first created in Shopify - Cental Time Zone. | | Order Created At (Eastern) | Reflects when the entity was first created in Shopify - Eastern Time Zone. | | Order Created At (Mountain) | Reflects when the entity was first created in Shopify - Mountain Time Zone. | | Order Created At (Pacific) | Reflects when the entity was first created in Shopify - Pacific Time Zone. | | Order Created At (Universal) | Reflects when the entity was first created in Shopify - Universal Time Zone. | | Order Last Fulfillment At (Universal) | The maximum timestamp for the last update order fulfillment - Universal Time Zone. | | Order Updated At (Universal) | Reflects when the entity was last updated in Shopify - Universal Time Zone. | | 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 Additional Tax Total | When taxes are not included in the subtotal, this is total tax added to the order. | | Average Fulfillment Tax Total | Total tax applied to the order's fulfillment fee. | | 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 Line Item Tax Total | Total tax applied to the line items of the 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 Non Reactivated Subscription Unit Total | Sum of unit price for non reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Average Payment Capture Total | Sum of successful capture transactions. | | Average Payment Total | Sum of all sales transaction with gateway of type 'shopify\_payments'. | | Average Product Basket Count | The count of products for a given order. | | Average Product Purchased Quantity | The total number of product purchased for a given order. | | Average Promo Total | The total discounts applied to the price of the order in the location's currency. | | Average Reactivated Subscription Unit Total | Sum of unit price for reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Average Refund Total | Sum of all the transactions that are of kind 'refund' applied to the order. | | Average Tax Total | The sum of all the taxes applied to the order in the location's currency. | | Average Total Price | | | Average Transaction Total | Sum of all sale transactions for the order. | | Average Variant Basket Count | The count of variants for a given order. | | Average Variant Purchased Quantity | The total number of variants purchased for a given order. | | Additional Tax Total | When taxes are not included in the subtotal, this is total tax added to the order. | | Fulfillment Tax Total | Total tax applied to the order's fulfillment fee. | | 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. | | Line Item Tax Total | Total tax applied to the line items of the 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\` | | Non Reactivated Subscription Unit Total | Sum of unit price for non reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Payment Capture Total | Sum of successful capture transactions. | | Payment Total | Sum of all sales transaction with gateway of type 'shopify\_payments'. | | Total Price | | | Product Basket Count | The count of products for a given order. | | Product Purchased Quantity | The total number of product purchased for a given order. | | Promo Total | The total discounts applied to the price of the order in the location's currency. | | Reactivated Subscription Unit Total | Sum of unit price for reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Refund Total | Sum of all the transactions that are of kind 'refund' applied to the order. | | 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. | | Variant Basket Count | The count of variants for a given order. | | Variant Purchased Quantity | The total number of variants purchased for a given order. | ### order\_applied\_discount\_codes | Name | Description | | ---------------------------- | ----------------------------------- | | Order Applied Discount Codes | Discount code applied to the order. | ### order\_tags | Name | Description | | ---------- | ---------------------------------- | | Order Tags | Order tag(s) applied to the order. | [title] Orders [path] Chord Data Platform/Data Models/Chord Data Attribute Definitions/Salesforce/ ### x\_fct\_orders | Name | Description | | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Order Account Id | ID generated by chord to identify the account. | | Order Bill To Contact Id | ID of the Contact associated with the Order Summary. It represents the shopper in the storefront when not using person accounts. | | Order Billing City | Billing address city. | | Order Billing Country | Billing address country. | | Order Billing Email Address | Email address on the billing address. | | Order Billing State | Billing address state. | | Order Billing State Country | The billing state or country of the order. Default to billing country if state is unavailable. | | Order Currency Iso Code | Available only for stores with the multicurrency feature enabled. Contains the ISO code for the currency of the original Order associated with the Order Summary. The default value is USD. Possible values are: DKK—Danish Krone, EUR—Euro, GBP—British Pound, USD—U.S. Dollar. | | Order Fulfillment Ids | IDs generated by Chord to identify the fulfillments associated with the order. | | Order Fulfillment Numbers | The fulfillment numbers associated with the order. | | Order Fulfillment Statuses | The fulfillment statuses associated with the order. | | Order Has A Shipped Fulfillment | A flag marking if an order has a shipped fulfillment. | | Order Hours To First Delivery | The number of hours between when the order was created and the first fulfillment was created. | | Order Hours To Last Delivery | The number of hours between when the order was created and the last, most recent, fulfillment was created. | | Order Id | ID generated by Chord to identify the order. | | Order Is Canceled | Whether an order is canceled. | | Order Is Completed | Whether an order is 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. | | Order Number Of Fulfillments | The total number of fulfillments associated with the order.
| | Order Number Of Reimbursements | The number of reimbursements associated with an order. | | Order Oms Account Id | ID of the account or person account associated with the Order Summary. It represents the shopper in the storefront. | | Order Oms Fulfillment Ids | ID generated by the OMS to identify the order. | | Order Oms Order Id | The id generated by the OMS for the Order Summary. | | Order Oms Order Payment Summary Ids | IDs generated by the OMS to identify the payment summaries associated with the order. | | Order Oms Return Order Ids | IDs generated by the OMS to identify the returns associated with the order. | | Order Is First Order | Whether the order is first order associated with the account. | | Order Number | Name of the Order Summary. | | Order Payment Summary Ids | IDs generated by Chord to identify the payment summaries associated with the order. | | Order Original Order Id | ID of the original order associated with this Order Summary. | | Order Payment Methods | The payment methods associated with the order. | | Order Payment Types | The payment types associated with the order. | | Order Po Number | Purchase order number associated with this Order Summary. | | Order Promotion Details Collection | The promotion details associated with the Order Summary. | | Order Return Order Ids | IDs generated by Chord to identify the returns associated with the order. | | Order Return Order Numbers | The return order numbers associated with the order. | | Order Sales Channel Id | ID of the Sales Channel associated with this Order Summary. | | Order Status | Status of the order summary. Unlike the Status and Status Category fields on the order and Fulfillment Order objects, this field is optional. | | Order Tax Locale Type | The system used to handle tax on the original Order associated with the Order Summary. Gross usually applies to taxes like value-added tax (VAT), and Net usually applies to taxes like sales tax. Possible values are: Gross (displays most prices and taxes as combined values), Net (displays most prices and taxes as separate values). | | Order Utm Campaign | The UTM Campaign associated with the Order Summary. | | Order Utm Medium | The UTM Medium associated with the Order Summary. | | Order Created At (Central) | The date the Order Summary was created - Cental Time Zone. | | Order Created At (Eastern) | The date the Order Summary was created - Eastern Time Zone. | | Order Created At (Mountain) | The date the Order Summary was created - Mountain Time Zone. | | Order Created At (Pacific) | The date the Order Summary was created - Pacific Time Zone. | | Order Created At (Universal) | The date the Order Summary was created - Universal Time Zone. | | Order First Fulfillment Created At (Universal) | Timestamp when the first fulfillment for the order was created - Universal Time Zone. | | Order First Order Created At (Universal) | Timestamp when the first order was created at - Universal Time Zone. | | Order Last Fulfillment Created At (Universal) | Timestamp when the most recent, or last, fulfillment for the order was created - Universal Time Zone. | | Order Last Modified Date (Universal) | The date the Order Summary was last modified - Universal Time Zone. | | Order Ordered Date (Universal) | Date of the original order associated with this Order Summary - Universal Time Zone. | | Average Adjusted Product Total | The total adjusted product amount associated with the Order Summary. | | Average Fulfillment Total | The total adjusted filfillment amount associated with the Order Summary. | | Average Gross Revenue | Gross Revenue is the pre-tax, pre-adjusted total line item price (unit price \* quantity) + the fulfillment total. | | Average 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. | | Average Promo Total | The total adjustment amount associated with the Order Summary. | | Average Refund Total | | | Average Tax Total | Total tax on all Order Item Summaries belonging to this Order Summary. Equal to Total Adjusted Delivery Tax Amount plus Total Adjusted Product Tax Amount. | | Average Total Basket Value | Total line itemamount in the order. This is the equivalent of the unit price \* quantity. | | Average Total Items | Total items in order. | | Average Total Price | Total amount, including adjustments and tax, of the Order Summary. | | Adjusted Product Total | The total adjusted product amount associated with the Order Summary. | | Total Basket Value | Total line itemamount in the order. This is the equivalent of the unit price \* quantity. | | Fulfillment Total | The total adjusted filfillment amount associated with the Order Summary. | | Gross Revenue | Gross Revenue is the pre-tax, pre-adjusted total line item price (unit price \* quantity) + the fulfillment total. | | Total Items | Total items in order. | | 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. | | Total Price | Total amount, including adjustments and tax, of the Order Summary. | | Promo Total | The total adjustment amount associated with the Order Summary. | | Refund Total | | | Tax Total | Total tax on all Order Item Summaries belonging to this Order Summary. Equal to Total Adjusted Delivery Tax Amount plus Total Adjusted Product Tax Amount. | [title] CLR and RFM on the Chord Commerce Data Platform [path] Chord Data Platform/Predictive Models/Customer Lifetime Revenue (CLR)/ ### Introduction We can examine the customer lifetime value (CLV) information within the Chord Hub. Upon logging in, we can access our example plant store and navigate to the business overview and customer segmentation pages to view our revenue segmentation data. ::loom{url="https://www.loom.com/embed/5efd4eae6a35487cb83710f11d7dcd8d"} On the splash page, we can include any relevant updates we wish to showcase. Using the explore function, we can navigate to the user table, which contains all the data we have been discussing, including the RFM measures of recency, frequency, and monetary value for each user. Additionally, we can select a specific user data point to view all the relevant scores for that user. We can also match these scores to specific RFM groups, such as the 111 group. Furthermore, we can mix this data with other user attributes, such as predicted lifetime net revenue or CLV. By running these analyses, we can determine which groups have the highest average CLV and explore further as needed. ### Hub Example 2: Geo Analysis  We may want to consider examining another measure by delving into user attributes and segmenting our data accordingly. One possible way to segment our data is by geography. Here, we will examine the average probability alive per geography for our example plant store, along with the average lifetime revenue. It's worth noting that results may differ from store to store. Nevertheless, this demonstrates the numerous attributes that we can use to segment our customers and the various ways in which we can analyze our data over time. For instance, we can filter by cohort and explore how different attributes are distributed among our customers. ::loom{url="https://www.loom.com/embed/02c646d33118413e8d6bd7d965a0f497"} [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{headerType="COLOR" headerColor="#08eb0d"} [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) ::: :::LinkArrayItem{headerType="COLOR" headerColor="#280df1"} [Sharing Data from an Existing Looker Instance](https://docs.chord.co/sharing-data-from-an-existing-looker-instance) ::: :::: [title] Revenue Forecasts [path] Chord Data Platform/Predictive Models/ ### Introduction Time series forecasts generate day-level forecasts for input series. Forecasts are generated a daily level in an ensemble time series forecasting system that blends weights via out-of-sample accuracy. Series are forecasted for the next 24 months. While series are generated on a daily level, they can be aggregated to the weekly or monthly level by aggregating over various time periods using the date dimension. Confidence intervals are based on variability of input series and do not include large system variability, such as macroeconomic changes. Note: Forecasts provided by Chord are best guess predictions based on the input data, are provided “as is” for analytics purposes, and do not constitute any guarantee explicit or implied of actualization of forecasts. Current forecasted series: - **Net Revenue**: total daily revenue for all customers. - **Reoccurring Revenue**: revenue generated by non-first purchase or "repeat" customers. - **First-Time Purchase Revenue**: revenue from first-time purchase customers. - **Number of First-Time Customers**: total number of new customers. ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/iOcYIOvMT3IOLIsB23CNK_screenshot-2024-04-16-at-125607-pm.png) ### Ensemble Model and Out of Sample Accuracies Time series models are generated using a range of time series modeling procedures, including ARIMA, Regression, and Theta models, and control for a range of seasonality indices and special events, such as holidays and common retailing events (Black Friday). These models are evaluated using out-of-sample (or “holdout”) periods that folded across short- and long- range holdouts into “best guess” forecasts. The variation for our confidence intervals is generated from the variation in the ranges of input ensemble models. Our models do not include exogenous variation outside of the series itself. This means that we are forecasting that series in isolation of outside influences. These exogenous influences include the macroeconomy and any other factors that could impact the series, including changes in a store’s product assortment or pricing. Similar to nearly all-time series forecasting models, these models should be interpreted as “all else equal” analyses; that is, everything outside the variation on this single series stays the same; these are the “best guess” estimates for the input series. ### Accuracy Accuracy is calculated via out-of-sample forecasts. 30, 60, and 90 day forecast are generated by holding the hold-out time periods from the data and forecasting from the new end date. The forecast of these models is compared with the actuals that happened during the hold-out period, along with the average mean absolute percentage error (MAPE). ### Horizon Forecasts are generated daily for the next two years. ### Eligibility Tenant stores are eligible if they have two years of history and over 1k transactions. [title] Product Recommendations [path] Chord Data Platform/Predictive Models/ ### Introduction Product recommendations are generated from a recommendation engine to increase repeat purchase rate and frequency, focusing on advancing first-purchase customers to repeat customers. Product recommendations on Chord can be found in the** Users **explore under the **Product Recommendations \[BETA]** field. ![]() The recommendation engine is generated with a combination of different algorithms, including user clustering in combination with predictions of future product purchases, to produce the following outputs: - **Advanced Segmentation Clusters:** user-level segmentation clusters useful for segmented targeting and A/B segment testing. - **Cross-Product Weights: **Tabulation of product cross-sales is useful for answering the question, “Customers that bought x also bought y.” - **Top-n Product Recommendations:** user-level product recommendations for the most likely next purchase based on product and user similarity, as well as input weights and rules. ### User Clustering Hierarchical clustering is used to generate segments of similar customers. It allows us to rank order how similar one customer is to all other customers. Hierarchical clustering utilizes user attributes, such as: - Purchase Behavior - Demographics  - Geography - Predicted Revenue Features Chord then adds a distance metric, for which the user attributes are fed into an agglomerative distance algorithm to minimize “close” and maximize “far” relationships. ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/6RCMfS5ptqsQ-Z3nwLYom_screenshot-2024-04-11-at-101946-am.png) ### Predicting Future Product Purchases Once these similarities are generated, we can use them to identify what other similar users have purchased. ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/hM2NHONA3LiDJ9UUsPfAJ_screenshot-2024-04-16-at-122747-pm.png) Another view into future behavior is the relationship between what one customer has purchased and related “cross-product” purchases. Collectively known as collaborative filtering, this process builds weight from user-item relationships and uses them to predict likely future purchase behavior.  ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/z7X5idxISzF-d5RK1H6GW_screenshot-2024-04-16-at-123911-pm.png) The final output is the top five product recommendations per user. These predictions are running daily and updated based on new or learned data points. These outputs can be activated in a variety of ways, such as email campaigns with personalized product content. [title] Attribution Channel Mapping [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 Chord provides an out-of-the-box mapping for pages to the attribution channel. However, brands sometimes have sources and channels that they want to track outside the standard Chord mapping. This configuration replaces the Chord mapping with the brand's custom mapping and adds the additional detail of being able to assign a Sub-Channel to the sources. ## How It Works The configuration allows the brand to define the channel of the page based on a combination of the following options: - **Medium** - the UTM Medium for the page - **Source** - the UTM Souce for the page - **GCLID **- whether the page view has a google click id (GCLID) or not - **Query** - any additional UTM parameters in the query including things like utm\_campaign, product or variant id, utm\_term, or utm\_content. - **Referrer** - any referrer details. For each of these, the brand can define the listed field condition's operator - Equal, Not Equal, Contains, Does Not Contain. For example- `Medium Does Not Contain Paid` and `Source Equals Facebook` could be `Organic Social`.The configuration first evaluates the page utm details and then evaluates the referrer. [title] Modifying a Report [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**). ::: Chord enables you to create custom analyses using our modeled data. You can visualize your data, gain insights, and share those insights with others. You can share these reports with others and let them view the data or give them edit access to change report filters and other content. See below for more details on editing different report types on Chord: - **Modifying a Dashboard** - **Modifying a Look** # Modifying a dashboard There are a few different ways to modify or edit an existing dashboard. View the instructions below. ## From My Reports ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/HTbETugZE0nMtWSVpkFWS_screenshot-2024-11-25-at-15038-pm.png) ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/nYvDTYwvMiWt9L5BdJCiG_screenshot-2024-11-25-at-20725-pm.png) 1. Navigate to **My Reports** under the **Analytics** homepage. 2. Select the dashboard in your reports folder that you want to edit via the dropdown menu on the top left. 3. Click the icon with three vertical dots to open up the menu dropdown for the dashboard. 4. Select **Edit Dashboard.** 5. From the pink menu bar, select a new visualization, text, or other option to add and modify your existing dashboard. 6. Don’t forget to save your new dashboard! ## From Shared Reports :::hint{type="info"} If you edit a shared dashboard, **the updated data will appear immediately upon saving**. Make sure that you are editing the correct dashboard on the **Shared Reports **page! ::: ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/bNggq8q4y9f1qyDx0k8eM_screenshot-2024-11-25-at-21056-pm.png) 1. Navigate to **Shared Reports** under the **Analytics** homepage. 2. Select the dashboard in the shared reports folder that you want to edit via the dropdown menu on the top left. 3. Click the icon with three vertical dots to open up the menu dropdown for the dashboard. 4. Select **Edit Dashboard.** 5. From the pink menu bar, select a new visualization, text, or other option to add and modify the existing shared dashboard. 6. Don’t forget to save your new dashboard! ## From Quickstarts ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/VECH17Vi402lZQsZk_BsZ_screenshot-2024-11-25-at-21601-pm.png) ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/4n4ahtg4v8wRnoZ8QdyR8_screenshot-2024-11-25-at-21616-pm.png) 1. Navigate to **Quickstarts** under the **Analytics** homepage. 2. Change the filter to see quickstarts that are dashboards. 3. Select a dashboard quickstart to use as your baseline report. 4. Give your new dashboard a new title and/or description. 5. Click **Create Dashboard**. 6. You’ll be taken to your new dashboard in your personal folder that you can edit using the instructions above! # Modifying a Look There are a few different ways to modify or edit an existing Look. View the instructions below. ## From My Reports ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/trwt57C0xav8gNpT7aTI0_screenshot-2024-11-25-at-15058-pm.png) 1. Navigate to **My Reports** under the **Analytics** homepage. 2. Select the Look in your reports folder that you want to edit via the dropdown menu on the top left. 3. Click the gear icon to open up the menu dropdown for the Look. 4. From here, you have two options to modify a Look: **Explore from Here** and **Edit**. We will review the two options below. ### Modifying a custom/personal Look: Explore from Here :::hint{type="info"} **Explore from Here** is a great option if you aren’t quite sure what you want to modify yet but want to test different metrics and dimensions. ::: ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/_ZwvQUjOWJvrE1d_NDa01_screenshot-2024-11-25-at-30510-pm.png) 1. If you select **Explore from Here**, you will see our familiar **Explores** screen with the relevant filters for your underlying Look preselected. 2. Select any fields on the lefthand side to try out different types of filters to edit your Look. 3. Don’t forget to save your edits once complete! You can save your Look as a starter metric for a new dashboard, save to an existing dashboard, or a create a new Look altogether. ### Modifying a custom/personal Look: Edit ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/cyNeA0EPeuWR12kPCKJ-u_screenshot-2024-11-25-at-30529-pm.png) ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/iaZO41oQ6zxuIoUOpOgG8_screenshot-2024-11-25-at-20703-pm.png) 1. If you select **Edit**, you will see a screen very similar to the one that displays if you had selected **Explore from Here.** 2. The key difference with choosing to **Edit** rather than **Explore from Here** is that you are directly editing the chosen Look rather than seeking to create an entirely new Look. 3. Once you make your necessary edits, you can save this Look or select any additional options, such as saving it as a new or existing dashboard or as a new Look. ## From Shared Reports :::hint{type="info"} If you edit a shared Look, the updated data will appear immediately upon saving. Make sure that you are editing the correct Look on the **Shared Reports** page! ::: ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/VUaYqkZwgSsU0PA6XsHQH_screenshot-2024-11-25-at-30403-pm.png) 1. Navigate to **Shared Reports** under the **Analytics** homepage. 2. Select the Look in your shared reports folder that you want to edit via the dropdown menu on the top left. 3. Click the gear icon to open up the menu dropdown for the Look. 4. From here, you have two options to modify a Look: **Explore from Here** and **Edit**. We will review the two options below. ### Modifying a Shared Look: Explore from here :::hint{type="info"} **Explore from Here** is a great option if you aren’t quite sure what you want to modify yet but want to test different metrics and dimensions. ::: ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/U6wENMYZPMuVn312dep9E_screenshot-2024-11-25-at-30430-pm.png) 1. If you select **Explore from Here**, you will see our familiar **Explores** screen with the relevant filters for your underlying Look preselected. 2. Select any fields on the lefthand side to try out different types of filters to edit your Look. 3. Don’t forget to save your edits once complete! You can save your Look as a starter metric for a new dashboard, save to an existing dashboard, or a create a new Look altogether. ### Modifying a Shared Look: Edit ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/nlFzuGyjzxeFm04G9dIZK_screenshot-2024-11-25-at-30413-pm.png) 1. If you select **Edit**, you will see a screen very similar to the one that displays if you had selected **Explore from Here.** 2. The key difference with choosing to **Edit** rather than **Explore from Here** is that you are directly editing the chosen Look rather than seeking to create an entirely new Look. 3. Once you make your necessary edits, you can save this Look or select any additional options, such as saving it as a new or existing dashboard or as a new Look. ## From Quickstarts ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/Q5DS_SD2dVQjh1clADND-_screenshot-2024-11-25-at-21635-pm.png) ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/rLVbLznyuiwFluWEtUres_screenshot-2024-11-25-at-21644-pm.png) 1. Navigate to **Quickstarts** under the **Analytics** homepage. 2. Change the filter to see quickstarts that are Looks. 3. Select a Look quickstart to use as your baseline metric. 4. Give your new Look a new title and/or description. 5. Click **Create Look.** 6. You’ll be taken to your new Look in your personal folder that you can edit using the instructions above! # FAQs and troubleshooting Q: How can I pin a new report that I just created and edited? A: You must be an admin-level user in order to pin reports. To do so, make sure that your new report is in your organization’s Shared Reports folder. Once the report has been shared, an admin-level user can pin it by clicking into the report and pinning it via the pin icon. For additional information on pinning and unpinning reports, please check out [this document](https://docs.chord.co/pinning-and-unpinning-reports). [title] Customer Lifetime Revenue and Purchase Likelihood [path] Chord Data Platform/Predictive Models/Customer Lifetime Revenue (CLR)/ ### Introduction Customer lifetime revenue and purchase likelihood are predictive insights about customers who have made at least one purchase in your online store. While both tools forecast future buying behavior, how you think about them from a marketing perspective may differ. This article explains how CLR and purchase likelihood work and offers suggestions for using them in marketing engagement, time-based ROI evaluation of marketing channels, and as high-level KPIs. ### About Chord’s Predictive User Features Chord's Customer Lifetime Revenue (CLR) and purchase likelihood are advanced segmentation tools that use historical data to predict a customer's likely purchase behavior in the future. CLR and purchase likelihood are commonly applied to segmentation for re-engagement actions, better understanding and targeting of new customer acquisition, and—at a high level—can be used as a nearly real-time metric for predicting a customer's long-term relationship with a brand. At the core of predictive revenue analysis is the tried-and-true marketing concept of RFM. RFM is a simple measure of a customer's recency, frequency, and monetary statistics. Generally, RFM describes the metrics businesses benefit from optimizing, and CLR is a bundle of tools used to measure progress on those optimizations. These metrics and how they can be used with CLR tools will be covered in more detail below. ### Accessing Chord’s Predictive Data Features CLR and purchase likelihood are available to Chord customers who have at least: - 2000 completed transactions and nine months of transaction history - 90 cumulative days containing transactions - 500 completed transactions from the last 90 days and - transactions completed in the past 30 days RFM is included in Chord’s predictive revenue toolbox and can be combined with CLR and purchase likelihood. ### Predictive Revenue Analysis overview CLR refers to a customer's total revenue for a business throughout their relationship. This includes all the customer's historical purchases and their predicted future purchases. Purchase likelihood refers to the probability that a customer will make another purchase from a business in the future. A high purchase likelihood indicates that a customer is likelier to become a loyal, repeat customer. In contrast, a low purchase likelihood suggests that a customer may be less likely to return and make additional purchases. ### Recency, Frequency, and Monetary (RFM) RFM are staples of predictive marketing segmentation and are core building blocks of CLR and purchase likelihood. They are baked into Chord’s revenue customer segmentation toolbox. These tools are related: RFM represents summary statistics of historical data, while CLR and purchase likelihood model historical data to make future predictions. RFM consists of the following: - **Recency**: how recently a customer has made a purchase - **Frequency**: how often a customer has purchased - **Monetary Value**: how much the customer has spent Together these estimates can be combined to create segmentation models. Chord’s revenue segmentation toolbox includes simplified buckets for generating segments. The categories are broken down into 5 buckets where 1 is always the “best” or most valuable, and 5 is the lowest. For instance, **Recency** bucket 1 represents customers that have purchased most recently, and bucket 5 are those that purchased the least recently. **Frequency** bucket 1 is those customers who buy the most frequently, and 5 is the least frequent. And **Monetary** value bucket 1 represents the highest total spenders while bucket 5 customers are the lowest. ### How RFM categories work ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-HccZAaFm79yfCsd3Bj4Ox-20250312-143240.png "R-F-M Graph: 1 is best; 5 is worst ") Every customer is categorized into buckets 1-5 for all three categories. The graph above shows groups of customers that fall into each R-F-M bucket. We refer to them in the order R-F-M, so a “1-1-1” is a customer who purchased most recently, is in your store’s highest frequency, and also in your store’s highest monetary spend compared to all customers. **1-1-1 (top right) are star customers:** they have spent the most with the most transactions and have engaged recently **5-5-5 (bottom left) are at-risk customers:** they have spent in the lowest 20% of spenders, only made one purchase, and have not purchased in a long time (relative to the store’s age) In between these two extremes are groups of customers on a gradation of value and engagement. The broad goal of the RFM matrix is to push customers to the upper right of the graph, as represented above. ### How to use RFM A store’s 1-1-1’s and 5-5-5’s for R-F-M are the most valuable and least valuable customers. Still, the most effective application of R-F-M usually comes with a combination of categories. For example, a 1-3-3 is a very recent customer who spent in the store’s middle statistical range and spent an average amount of money. You might label this customer as a “potential rising star” and plan their marketing engagements accordingly. A 2-1-2 is a high-frequency customer that could be at risk of slipping into an inactive state. You might label this customer as a “high impact potential risk” and tweak their engagement touches accordingly. The core of R-F-M is that these different groups represent different levels of engagement and realized value. ### How CLR and Purchase Likelihood work To determine CLR and purchase likelihood, a store’s historical data is modeled and then model parameters are applied to individual users. The model considers classic RFM attributes as well as customer segmentation demographics. Some attributes used in the model include: - Customer age - How recently the customer has purchased - How often the customer has purchased - Total amount the customer has spent - Customer engagement in promotional events A customer’s purchase likelihood and corresponding CLR can change based on their attributes and activity. For instance, if a customer makes a new purchase then their CLR will increase both for their historical value and for what we expect them to spend in the future. New predictions are updated weekly and include both new customers over that time period and updated estimates of existing customers. ### Using CLR for advanced segmentation Segmentation actions from predictive data should be used at a grouping level. For example, you may want to target all customers who have a predicted repurchase percentage between 65% and 75%. This segment can be further spliced by user attributes, such as geographic location or demographics, and can be combined with RFM analysis to generate detailed segments of your data. Because an idea of future behavior is built into the statistics, one of the most powerful levers of prediction analysis is that it can be used for evaluating the outcome of retargeting events. For example, imagine a company used the purchase likelihood slice mentioned above (repurchase likelihood between 65% and 75%), held out a portion of the segment to calibrate evaluation, and then ran a retargeting campaign for those customers. At the end of the campaign, they can test whether the initial segments stayed true to their predictions—they were expected to repurchase between 65% and 75%—and then compare those with the group that got the campaign (see caveats below). The delta between these two groups is the efficiency measure of the campaign. Relatedly, the delta between the CLR of the two groups at the end of the campaign is the increase in total expected revenue and can be compared to the cost of the campaign to calculate ROI. ### How the models are evaluated Evaluation of the accuracy of the predictive models is achieved using an out of sample strategy where we hold out a certain portion of the data, make predictions using the training data, and then evaluate how accurate our models were in predicting the evaluation period. For example, a customer level view of our training and evaluation data is in the graph below. **Model Evaluation: Customer First and Subsequent Purchases** ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-_HcugGjs8Y-Cw8gbh5-QQ-20250312-143533.png "The x-axis shows time, the dots on the left show the first transaction date for any customer, and a subsequent dot shows the repeat purchase activity for any customer who does purchase again. Training Period data is used to train statistical models, and the holdout period (on the right) is used to evaluate how well the model performs.") The graph above represents how we use historical data to train models to predict the future purchases. ### Caveats It is important to note that our models—like all statistical models—cannot perfectly predict the future. Many variables are beyond the control of any store, e.g., macroeconomic influences and ever-changing customer preferences. There are also variables within a store’s control—changes in marketing spend, promotion, price changes, product catalog changes—that Chord has no knowledge of and, therefore, cannot account for in its models. However, our models use stores’ historical variation to make predictions capturing trends in customer behavior. Batches run at regular intervals to keep predictions fresh and leverage as much data as we have access to deliver the most accurate predictions possible. ### How to find and use CLR metrics ![]() 1. Login to Chord and navigate to **Analytics**. 2. Click on **Explores**. 3. Within the **Users Explore**, navigate to the **User Predictions \[BETA]** to use RFM and CLR metrics for your analysis. ### Frequently Asked Questions **Q: How often is this refreshed / how up to date are the predictions?** A: Predictions are updated weekly and include both new customers over that time period and updated estimates of existing customers **Q: How far out are the predictions cast?** A: Two years **Q: Is the predicted revenue gross or net?** A: Our predictions use net revenue. **Q: Can I filter out / normalize customer lifetime revenue? If we had an initial launch sale or a big holiday promotion, I’d like to exclude those transactions and users from the data set because they’ll skew the averages.** A: There are no easy controls available for this right now, but Looker’s baked-in filters allow for lots of customization by filtering on date, repeat purchase vs. first-time purchase, promo code applied, etc. **Q: Is there a glossary for reference?** A: Check out our [CLR and RFM data table legend](https://app.archbee.com/doc/XzU-KFlDMlty4bseZIAiN/3QtswyzpzkDnu_3-A1nl8) [title] Customer Lifetime Revenue (CLR) Explanation [path] Chord Data Platform/Predictive Models/Customer Lifetime Revenue (CLR)/ ### Introduction Once we have established the recency, frequency, and monetary value summary statistics, we can input these into algorithms to estimate the total customer lifetime revenue. This encompasses the sum of their previous spending up until the time the model is run. Additionally, we forecast the customer's likelihood of re-engagement and repurchasing based on their behavioral patterns. The sum of these two estimates creates the customer lifetime value, representing the anticipated lifetime engagement and spending of a customer with the company. ::loom{url="https://www.loom.com/embed/2f3e3a8f3e0048a089ede57047307ba6"} This measure can be used to evaluate the ROI of customer acquisition costs, measure the overall increase or decrease in the company's customer lifetime revenue, and track changes in customer lifetime revenue over time. The customer lifetime revenue can further be used to determine the appropriate amount of investment in new customer acquisition. By analyzing each customer's data, we train models to identify patterns in their behavior and predict their likelihood of repurchasing. Our goal is to accurately identify customers who are likely to repurchase and those who are not and assign weights accordingly to assess the accuracy of our models. ### Probability re-engagement  Calculating the probability of a customer's re-engagement or repurchase is a crucial aspect of customer lifetime value estimation. A representative customer who made multiple purchases from a store exemplifies this concept. The likelihood of their engagement with the store at the time of purchase is 100%, but as time passes, this probability diminishes. With increasing temporal distance from their last purchase, the likelihood of re-engagement also declines. ::loom{url="https://www.loom.com/embed/dd9c7753e808454f94239a3feb484fc8"} ### ### Example probability re-engagement usage An important aspect of customer lifetime value is determining the probability of a customer reengaging or repurchasing from a store. For instance, if a company scores the reengagement probability for all its customers, it can conduct a targeted campaign for customers with a moderate probability of reengagement, say 40% to 60%. This group can then be divided into an A/B component, with the treatment marketing campaign or email campaign only given to the A group while the B group is not engaged. ::loom{url="https://www.loom.com/embed/9a12bf85c59c43b28a4ea31abd0ed1d5"} At the conclusion of the campaign, a causal difference can be measured between the two groups. It is expected that the A group's performance would be what was predicted, with the delta between the two groups representing the impact of the A/B group. The probability of reengagement is a powerful segmentation tool that can be spiced by different segments within the group. The general idea is to use it as a predictive tool, with a good idea of how the two buckets will perform in the test, and then evaluate the causal impact of the test by assessing the delta on the other side. [title] Sharing Data from an Existing Looker Instance [path] Chord Data Platform/Analytics Features/ If your organization already runs Looker, Chord can connect to it directly using an API3 key. This guide walks you through generating that key and getting it to your Chord contact securely. **What you'll need** - Admin access to your Looker instance (or a Looker Admin who can do this step for you) - A password manager or secrets vault to store the credentials - About 5 minutes **How to get your Looker API3 key** 1. Log in to your Looker instance as an Admin. If you don't have admin access, ask your Looker Admin to complete these steps on your behalf. 2. Go to the Admin panel (gear icon in the left nav). 3. Under Users, find your account and click Edit. 4. Scroll down to the API3 Keys section. 5. Click New API3 Key. Looker will generate a Client ID and Client Secret. 6. Copy both values immediately. The Client Secret is only shown once and can't be retrieved again later. If it's lost, you'll need to delete the key and generate a new one. Store both values securely in a password manager or secrets vault. This is what Chord will use for API authentication. **Note**: API3 keys are tied to the permissions of the user they're created under. Make sure the account has the appropriate role and permissions for whatever API access is needed (for example, read access to the specific models and explores Chord will query). **Sharing the credentials with Chord** Once you have your Client ID and Client Secret, send both values to your Chord contact through a secure channel (a shared secrets vault or an encrypted message) rather than plain email or chat. Avoid sending the ID and Secret in the same message thread as other unrelated credentials. Questions or feedback? Reach out to help\@chord.co. [title] CDP Sources [path] Chord CDP/ A CDP (Customer Data Platform) source is any system or touchpoint where customer data originates before being collected and unified in the CDP. CDP sources include ecommerce platforms, server-side applications, or third-party tools that generate customer interactions and behavioral data. # Source types ## Browser sources A browser source captures data directly from a customer's browser in real-time as they interact with your website. This includes page views, product views, completed orders, and other front-end interactions. Browser sources use JavaScript SDKs to track customer behavior as it happens. ## Server sources A server source sends data from your backend systems or applications to the CDP. This includes order data, customer account information, subscription updates, or any events that happen on your servers rather than in the customer's browser. Server sources give you more control over data quality, aren't affected by ad blockers or browser restrictions, and are ideal for tracking sensitive information or backend processes that don't have a user interface. Please see the [Server Events Overview](docId\:IkQZVvht-BFBSKyISgKJo) documenation for more information. # Understanding write keys Each CDP source uses one or more write keys to authenticate and route data into the Chord platform. Write keys are unique identifiers that ensure data is sent to the correct source and CDP workspace account. When implementing tracking via SDKs or APIs, you'll need to use the appropriate write key(s) for your configured source. :::hint{type="danger"} Write keys are sensitive credentials. Treat them like passwords and never expose them in public repositories. ::: # Viewing your sources Sources are configured and managed by the Chord team during your initial CDP setup and integration process. To view your configured sources: 1. Navigate to the **CDP Overview** page on Chord. 2. View **Sources** on the left hand side of the page. # Working with Sources If you need to add a new source, modify an existing source configuration, or have questions about your source setup, please contact your Chord integration team or [reach out to Chord support](mailto\:help@chord.co). [title] Applovin Axon [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ # Introduction AppLovin Axon is a measurement and audience platform that helps advertisers track conversions, optimize campaigns, and build targeted audiences. The Axon pixel collects event data from your website to power AppLovin's ad optimization engine. # Getting Started This is a device-mode destination requiring an Axon Event Key for connection. You can obtain the Event Key from your AppLovin dashboard. # Initialization When the Axon destination is enabled, p.js injects the Axon pixel scripts into the page on first event: - `https://s.axon.ai/pixel.js` - `https://c.albss.com/p/l/loader.iife.js` Before the scripts load, a `window.axon` stub is created that queues all calls. Once the real SDK loads it replays the queue automatically, so no events are lost during initialization. `axon("init")` is called immediately after the stub is created to begin the SDK initialization handshake. Preconnect and DNS-prefetch hints for `https://s.axon.ai` and `https://c.albss.com` are also injected to reduce script load latency. # Connecting to the Axon 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 **AppLovin Axon** from the destination catalog. 5. Enter the destination name and **Axon Event Key**. 6. Click **"Create"** to connect. # Events ## Event Mapping Chord event names are mapped to Axon standard event names. Unmapped event names are passed through as-is. ### Required Events (Purchase Sites) | Chord Event | Axon Event | | ---------------- | --------------- | | Product Viewed | view\_item | | Product Added | add\_to\_cart | | Checkout Started | begin\_checkout | | Order Completed | purchase | ### Recommended Events | Chord Event | Axon Event | | -------------------------- | ------------------ | | Payment Info Entered | add\_payment\_info | | Cart Viewed | view\_cart | | Product Removed | remove\_from\_cart | | Products Searched | search | | Signed Up | sign\_up | | Logged In / User Logged In | login | | Subscribe / Subscribed | subscribe | | Lead Generated | generate\_lead | # Event Details ## Page Fires an Axon page view tracking call. **Axon SDK call:** `axon("track", "page_view")` No additional attributes are sent with page events. *** ## Identify Sends user identity to Axon. **Axon SDK call:** `axon("identify", userId, traits?)` | Axon Attribute | Chord Source (Priority Order) | Notes | | -------------- | ----------------------------- | -------------------------------------------- | | `userId` | `userId` > `anonymousId` | Required; event is skipped if neither is set | | `traits` | `traits` | Optional; only sent if non-empty | *** ## Track Sends a tracked event to Axon. The payload structure varies by event type. ### Common Attributes (All Track Events) The following attributes are included on every track event when the source data is available: | Axon Attribute | Chord Source (Priority Order) | Notes | | ------------------- | ---------------------------------------------------- | ------------------------------------------------------------------------------------------- | | `user_data.email` | `properties.email` > `context.traits.email` | `user_data` object is only included if at least one of email, phone, or user\_id is present | | `user_data.phone` | `properties.phone` > `context.traits.phone` | | | `user_data.user_id` | `userId` > `traits.userId` > `context.traits.userId` | | ### Common Attributes (Item-Based Events) The following events also include items, currency, and value: `view_item`, `add_to_cart`, `begin_checkout`, `purchase`, `add_payment_info`, `view_cart`, `remove_from_cart`. | Axon Attribute | Chord Source (Priority Order) | Notes | | -------------- | ----------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ | | `items` | `properties.products` | Array of Axon items (see Item Attributes below). Products without an identifiable ID are filtered out. | | `currency` | `properties.currency` > `properties.meta.i18n.currency` > `"USD"` (default) | | | `value` | `properties.total` > `properties.revenue` > `properties.value` > `properties.price` > sum of product prices | | ### Item Attributes Each product in `properties.products` is transformed to an Axon item: | Axon Attribute | Chord Source (Priority Order) | Notes | | ------------------ | -------------------------------------------------------- | --------------------------------------------- | | `item_id` | `product_id` / `productId` > `id` / `sku` / `variant_id` | Required; product is excluded if none resolve | | `item_name` | `name` / `productName` / `product_name` | | | `price` | `price` / `productPrice` | | | `quantity` | `quantity` / `productQuantity` | | | `image_url` | `image_url` | | | `item_variant_id` | `variant_id` | | | `item_brand` | `brand` | | | `affiliation` | `affiliation` | | | `discount` | `discount` | | | `item_category_id` | `item_category_id` | | *** ## Order Completed Fires a purchase event. Includes the common item-based attributes above, plus: **Axon SDK call:** `axon("track", "purchase", properties)` | Axon Attribute | Chord Source (Priority Order) | Notes | | ---------------- | -------------------------------------------- | ----- | | `transaction_id` | `properties.order_id` / `properties.orderId` | | | `tax` | `properties.tax` | | | `shipping` | `properties.shipping` | | *** ## Payment Info Entered Fires an add payment info event. Includes the common item-based attributes above, plus: **Axon SDK call:** `axon("track", "add_payment_info", properties)` | Axon Attribute | Chord Source (Priority Order) | Notes | | -------------- | ------------------------------------------------------- | ----- | | `payment_type` | `properties.payment_type` > `properties.payment_method` | | *** ## Products Searched Fires a search event. **Axon SDK call:** `axon("track", "search", properties)` | Axon Attribute | Chord Source (Priority Order) | Notes | | -------------- | --------------------------------------------------------------------------- | ------------------------------------------------------- | | `search_term` | `properties.search_term` > `properties.query` > `properties.term` | | | `results` | `properties.results` | Array of items, transformed using the same item mapping | | `currency` | `properties.currency` > `properties.meta.i18n.currency` > `"USD"` (default) | Optional | | `value` | `properties.value` | Optional | *** ## Signed Up Fires a sign-up event. **Axon SDK call:** `axon("track", "sign_up", properties)` | Axon Attribute | Chord Source | Notes | | -------------- | ------------------- | -------- | | `method` | `properties.method` | Optional | *** ## Subscribe / Subscribed Fires a subscribe event. **Axon SDK call:** `axon("track", "subscribe", properties)` | Axon Attribute | Chord Source | Notes | | -------------- | --------------------- | -------- | | `currency` | `properties.currency` | Optional | | `value` | `properties.value` | Optional | *** ## Logged In / User Logged In **Axon SDK call:** `axon("track", "login")` No additional attributes are sent. *** ## Lead Generated **Axon SDK call:** `axon("track", "generate_lead")` No additional attributes are sent. *** ## Unmapped Events Events not listed in the event mapping tables are passed through to Axon using the original event name, with `properties` forwarded as-is. **Axon SDK call:** `axon("track", eventName, properties)` # CSP Requirements If your site uses a Content Security Policy, allow the following domains: | Directive | Domain | | ------------- | ------------------------------------------ | | `script-src` | `https://s.axon.ai`, `https://c.albss.com` | | `connect-src` | `https://s.axon.ai`, `https://c.albss.com` | *** **Updated 14 Apr 2026** [title] Chord CDP vs. Shopify Native - Biz Version [path] Chord CDP/ # The problem in plain terms Most Shopify merchants end up with a patchwork of tools bolted onto their store over time: an app for Meta ads, another for TikTok, a Google Analytics tag, an attribution vendor, an email platform syncing customers on its own schedule. Each one was installed separately, watches the store in its own way, and reports its own version of what happened. That's why Meta says one thing, Shopify says another, and your attribution vendor says a third — and why reconciling them usually falls to whoever has to explain the gap. It's also why switching a vendor means losing your history, why every new integration means another app and another set of numbers to reconcile, and why nobody can say with confidence what a "sale" even means across your reporting. Chord's Customer Data Platform (CDP) fixes this at the source. Instead of every tool watching the store independently, one system captures each customer event a single time, enriches it with everything needed to identify and credit it correctly, and then distributes it to every tool that needs it — ad platforms, analytics, email/CRM, attribution, and your own data warehouse. Everyone works from the same facts. This document walks through what that's worth to the business, and is equally honest about where a standalone Shopify app is still the right tool for the job. ## Two ways of wiring up your store **The way most stores are set up today:** every app connects to the storefront independently and reports on its own terms. ```mermaid flowchart LR subgraph native["Shopify-native model"] S1[Storefront + Checkout] --> A1[Meta app] S1 --> A2[TikTok app] S1 --> A3[GA4 tag] S1 --> A4[Attribution app] S1 --> A5[ESP app] end ``` **The way it works with a CDP:** one capture point, one shared understanding of the customer, distributed everywhere it's needed. ```mermaid flowchart LR subgraph cdp["Chord CDP model"] S2[Storefront + Checkout] --> P[Chord Pixel] P --> C[Chord CDP
tracking plan, identity,
consent, mappings] C --> D1[Ad platforms
pixel + Conversions API] C --> D2[Analytics] C --> D3[ESP / CRM] C --> D4[Attribution] C --> D5[Warehouse] end ``` In the first model, you have five separate pipelines, each with its own definition of a sale. In the second, you have one pipeline and one definition, with the differences each destination needs handled automatically behind the scenes. ## Side-by-side comparison | | **Apps installed one by one** | **Chord CDP** | | -------------------------------------------------- | --------------------------------------------------------- | ----------------------------------------------------- | | Definition of a sale | Different in every app | One definition, consistently applied everywhere | | Ad platform matching | Limited to what each app can see in the moment | Richer, more complete — captured from the first click | | Resilience to ad blockers / browser privacy limits | Data is lost | Delivered independent of the browser | | Combining pixel + direct server data | Not coordinated — leads to double-counting or picking one | Coordinated automatically | | Impact on site speed | One load per app | One lightweight script; server-side has none | | Ability to diagnose problems | Little to none | Full visibility into every event and every delivery | | Recovery from temporary failures | None | Automatic retries | | Privacy/consent compliance | Managed separately per app | Centralized and consistent | | Adding a new tool | New app, new setup project | Configuration change on data you already have | | Ownership of your own data | Held by each vendor | Held by you | | Switching vendors | Historical data lost | Data retained and reusable | ## One consistent definition of a sale, everywhere When every app collects data independently, every app also decides for itself what counts as a "purchase." One counts it the moment checkout completes; another waits until the order is marked paid. One counts the discounted total; another counts the order total including tax and shipping. One recognizes a customer by their email; another only by a browser cookie. No single tool is doing anything wrong — but the result is that you're stuck reconciling several different, incompatible answers to the same question, usually while someone is asking why your ad platform and your store disagree by 8%. Chord CDP solves this by defining each event — like "Order Completed" — exactly once, and then translating that single definition into whatever format each destination expects. When numbers differ across platforms after that, it's because of genuinely different measurement windows or matching methods, not because two systems counted different things. ## Better ad performance through better matching This is usually the single biggest financial impact, because how well ad platforms can match a sale back to the ad that drove it directly determines how efficiently your ad spend gets credited — and how well the platforms' own optimization algorithms perform. A typical Shopify app only sees the order and checkout, plus whatever browser cookie happens to be present at that exact moment. It has no visibility into the ad click that brought that customer to your site three days earlier, and generally cannot connect anonymous browsing activity to the person who eventually bought. Chord's pixel captures that ad click information the moment a visitor lands on your site, holds onto it for the entire session, connects it to the customer once they identify themselves (by logging in, checking out, or subscribing), and then attaches all of that context to every downstream report. This means your ad platforms receive richer, more complete information about each sale than they would from a standalone app — which typically translates into better attribution, better optimization, and more efficient ad spend. ## Your reporting doesn't depend on the customer's browser behaving Pixels that run in the customer's browser are unreliable by nature: ad blockers strip them out, Safari's privacy settings limit what they can see, cookie consent banners can block them entirely, and something as small as an unrelated bug elsewhere on the page can stop them from firing. Any Shopify app built around a browser pixel inherits all of these blind spots. Chord CDP instead sends data directly, server-to-server, to the platforms that support it — including Meta, TikTok, Snapchat, Pinterest, and Microsoft — so those conversions are recorded no matter what happened in the customer's browser. Where it's valuable to use both the pixel and this direct server connection together, Chord coordinates between them so the platform counts each sale once, with the benefit of both data sources — something that's only possible when one system controls both sides. Two separately installed apps can't do this coordination, which is usually why merchants end up either double-counting conversions or giving up one of the two methods entirely. ## A faster storefront Every app that adds a tracking script to your site adds a delay to how quickly the page loads, because each one brings its own software to run in the visitor's browser. Ten integrations means ten separate pieces of code loading before the page is fully usable. On a store that depends on paid traffic, that slowdown shows up first in page speed and then in your conversion rate. Chord loads a single lightweight script. Everything that can be handled through the direct server connection described above adds no load time to the page at all. ## Visibility when something breaks When a Shopify app quietly stops working, you usually find out weeks later, as a gap in an ad platform's reporting — with no record of what was sent and no way to recover what was lost. With Chord CDP, every single event can be inspected end to end. You can see the original event, exactly what was sent to each destination, and how that destination responded. A single ID follows each event through the whole journey, so a customer complaint about a missing order confirmation, for example, can be traced precisely rather than guessed at. Temporary failures — a destination being briefly unavailable, for instance — are automatically retried until they succeed, and you're alerted if a delivery problem persists, so a broken connection surfaces in hours rather than showing up as a mystery in next month's numbers. And if one destination has a problem, it doesn't affect delivery to any of the others — unlike a single script error in your theme, which can silently take down several tracking tools at once. ## Privacy compliance handled in one place, not five When every app manages its own data collection, keeping track of your privacy and consent compliance means checking each app's settings individually — and every new app you add quietly expands how much customer data is being shared without your team necessarily seeing it happen. Chord CDP enforces consent centrally instead. You define your consent categories once, connect them to whatever consent banner tool you use, and Chord makes sure that no destination receives data from a customer until that customer has actually granted the relevant permission — including preventing certain tracking scripts from loading in the browser at all until consent is given. This applies automatically and consistently across every destination, rather than depending on someone manually configuring each app correctly. ## You own your data, not just a report about it In the app-by-app model, every vendor holds its own private copy of your customer data, and you never hold the underlying record yourself. That has two consequences that don't show up until later: if you ever switch away from a vendor, you have no history to bring with you and have to start from zero; and every new tool you add is, again, another app, another script, and another definition of what a sale is. With Chord CDP, your data warehouse receives the full stream of customer events directly, and every other tool — ad platforms, email, attribution, analytics — is simply reading from that same stream. That means adding a new attribution vendor, switching email providers, or testing a second ad platform becomes a configuration change on data you already own, rather than a new integration project. And because your analytics and your ad platforms are reading from the same underlying events, the numbers your team sees internally and the numbers your ad platforms report have the same origin — so they're far more likely to agree. ## Where a standalone Shopify app is still the right call The CDP isn't meant to replace every app in your store, and it would be dishonest to suggest otherwise. The simple test is this: if the tool's job is to *receive* customer data, it should go through the CDP. If its job is to *do* something inside your Shopify storefront or backend, it should stay a standalone app. | **Situation** | **Better fit** | **Why** | | ---------------------------------------------------------------- | -------------- | --------------------------------------------------------------------- | | Storefront experience — reviews, upsells, subscriptions, loyalty | Shopify app | It has to actually appear on your storefront | | Store operations — fulfillment, inventory, returns, shipping | Shopify app | It needs to make changes inside Shopify itself | | Analytics, ad platforms, attribution, email/CRM, data warehouse | Chord CDP | These tools only need to receive data, and everything above applies | | A vendor with no way to receive data automatically | Shopify app | But route the same data through the CDP too, so you still keep a copy | | A very small store with one or two tools and no paid advertising | Shopify app | The coordination problem the CDP solves hasn't come up yet | ## Questions we hear often **"Our apps are already installed and working — why change anything?"** They're delivering something, just not everything. The real question is what they're missing: sales lost to ad blockers, the ad click that happened before checkout, or the outage nobody was alerted to because there was no way to see it. Chord's event-level visibility makes that gap something you can actually measure, rather than something you have to take on faith. **"Doesn't this just add another layer on top of what we already have?"** It replaces layers rather than adding one — you go from several separate tools each doing their own tracking to one system doing it consistently, and from several different definitions of a sale to one. **"Doesn't Shopify's own tracking already solve this?"** Shopify's built-in event tracking is a real improvement over apps injecting scripts directly into your theme, and it's a better place to collect data from. But on its own, it doesn't get you direct server-to-server delivery, ad-click tracking that persists across a customer's visit, identity resolution beyond a single order, coordinated pixel and server-side matching, automatic retries, consent enforcement per destination, or a warehouse copy of your raw data. Chord can use it as an input, but it isn't a substitute for the rest. **"Could the CDP itself create duplicate data?"** Chord is built the same way as other established customer data platforms in this space: every event carries a unique ID that destinations use to avoid double-counting, even in the rare case an event is sent more than once. [title] Dotdigital (Tag) [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ Dotdigital is a marketing automation platform for email, SMS and cross-channel programs. The Dotdigital Tag destination loads Dotdigital in the browser and feeds it your Chord events, so it can track web behaviour, recover abandoned browses and abandoned carts, and report orders. This is the surface that makes abandonment work. Dotdigital's abandoned-cart program starts its timer from the last cart update it saw in the browser, and abandoned browse depends on the visitor session the Tag establishes — neither can be driven from a server. For contact data fields, address book membership and consent records, pair this with the [Dotdigital](#) destination. # Getting Started You need one value, and one thing removed. **Your Tag URL.** In Dotdigital go to **Connect > Connect website**, select **View code**, and copy the `src` value out of the script tag. It looks like `https://r1.ddlnk.net/DM-0000000000-01/ddgtag`, or `https://emails.yourbrand.com/DM-0000000000-01/ddgtag.js` if your account uses a branded domain. Dotdigital generates this per account, so use the one your account shows rather than adapting an example — the host varies, and it is the host your storefront's Content Security Policy has to allow. **Remove any Dotdigital Tag you installed yourself**, including one added through a commerce-platform app. This is not a preference: two tags on one page create two sessions, double every page view, and split one shopper's behaviour across both. This destination replaces that installation rather than complementing it. Three settings are optional but worth filling in: - **Abandoned Cart Delay** and **Abandoned Cart Program ID** — how long Dotdigital waits after the last cart update, and which program to enrol into. Find the program ID in the URL when you open it under **Automation > Programs**. Without them Dotdigital applies your account defaults. - **Cart URL** — your storefront's cart page. Required. Dotdigital rejects a cart update unless *every line* carries a product URL, and this is what Chord falls back to for a line that has none, so leaving it empty stops cart tracking working at all. It is also the link a shopper follows out of an abandoned cart email. - **Site Brand** — only if your account uses Dotdigital Personalization. # Connecting to the Dotdigital 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 **Dotdigital Tag** from the destination catalog. 5. Enter the destination name and your **Tag URL**, plus any of the optional settings above. 6. Click **"Create"** to connect. 7. Connect it to your **front-end** site. 8. Remove your own Dotdigital Tag from the storefront. # Using Alongside the Dotdigital Destination The [Dotdigital](#) destination talks to Dotdigital's v3 API server-side. The two are complementary rather than duplicates, and both can run on the same Dotdigital account: - **This destination** owns web behaviour tracking, abandoned browse and abandoned cart. None of that is reproducible server-side. - **The Dotdigital destination** owns the contact record — data fields, address book membership, consent records — which this destination's identify call cannot write. It is also unaffected by ad blockers. **One thing to know before you enable both: order and cart data lands in two places.** This destination writes into Dotdigital's own order and cart collections — the ones its abandoned-cart program and its order content blocks read. Dotdigital's Events API is not permitted to write into those same collections, so when the server-side destination reports an order it creates a separate, generically-named Insight data collection instead. That is not double-counting in Dotdigital's order reporting, but it does mean an order reported by both surfaces exists as two records in two collections. If you segment or build content on order data, decide which surface is your source of truth and use that collection. If you only want one, this destination is the one to keep for abandonment, and the server-side destination is the one to keep if reliability against ad blockers matters more. # Deduplication Custom events carry a `messageId` attribute — a unique identifier for that event. If you also push events into the same Dotdigital account from another system, that is the value to deduplicate against. Commerce calls are different, and the limitation is Dotdigital's rather than Chord's: `cartUpdate`, `checkout` and `purchaseComplete` accept no per-call event identifier. The order's own `orderId` and the cart's `cartId` are the only handles available, and **Dotdigital does not document deduplicating on either** — it describes them only as unique identifiers. So treat "report each order once" as the rule rather than relying on Dotdigital to sort out a repeat. Chord skips an `Order Completed` that carries no `order_id` for the same reason: an order with no reference cannot be deduplicated or reconciled by anyone. # Event Mapping | Chord event | Dotdigital | | --------------------------------------------------------- | --------------------------------------------------- | | `Page Viewed` | Page view | | `Product Viewed` | Product browse | | `Product List Viewed` | Product list | | `Product Added`, `Product Removed`, `Cart Viewed` | Cart update | | `Checkout Started` | Checkout | | `Order Completed` | Purchase, with the order reference and cart | | `identify`, `Email Captured`, `Signed Up`, `User Created` | Contact identification | | Any other `track` event | Custom event under its own name — see Custom Events | # Product and Cart Data Dotdigital uses two different product shapes, and Chord sends the right one for each call. **Product browse and product list** send: | Chord event property | Dotdigital field | | ----------------------------------- | ---------------------------------- | | `product_id` | `productId` | | `sku` | `sku` | | `name` | `name` | | `url`, falling back to the page URL | `url` | | `image_url` | `imageUrl` and `imageThumbnailUrl` | | `price` | `price` | | `currency` | `currency` | | `brand` | `brand` | | `category` | `categories` | | `description` | `description` | | `variant_id` | `variantId` | `imageThumbnailUrl` is filled from the same image as `imageUrl` because Chord's tracking plan carries one product image. Dotdigital's default content blocks read the thumbnail, so an empty one renders a blank image in a browse-abandonment email. **Cart lines** send: | Chord event property | Dotdigital field | | ------------------------------------------------------------------------------------------------- | ---------------- | | `product_id` | `productId` | | `sku`, falling back to `variant_id` then `product_id` | `sku` | | `name` | `name` | | `price` | `price` | | `quantity` | `quantity` | | `price` × `quantity` | `totalPrice` | | `image_url` | `imageUrl` | | `url`, falling back to the event's `url` for the line that changed, then the **Cart URL** setting | `url` | | `brand` | `brand` | | `category` | `categories` | | `variant_id` | `variantId` | **Cart totals** send: | Chord event property | Dotdigital field | | ------------------------------------------------------ | ---------------- | | `cart_id`, falling back to `order_id` or `checkout_id` | `cartId` | | `currency` | `currency` | | `subtotal`, falling back to the sum of the line totals | `subtotal` | | `total` | `grandTotal` | | `cart_url`, falling back to the **Cart URL** setting | `cartUrl` | | `shipping` | `shipping` | | `discount` | `discountAmount` | | `tax` | `taxAmount` | A product line with no resolvable product ID is dropped rather than sent blank, because Dotdigital keys its catalogue and its abandonment content off the product ID. ## Fields Dotdigital requires Dotdigital rejects a call outright when any of these is missing, and Chord's tracking plan marks them optional. Chord fills each one so your events are not refused, but **the substituted value is a fallback, not your data** — send the real one and it is always preferred. | Field | Substituted with | What you lose by relying on it | | ---------------------------- | ----------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Product `url` on a browse | The URL of the page the event fired on | Nothing, normally. On a `Product Viewed` the page *is* the product's page. | | Product `url` on a cart line | The event's own `url` for the line that changed, then your **Cart URL** | Every other line links to your cart page instead of its product. The shopper still returns to their basket, but not to the item they were looking at. | | `sku` on a cart line | `variant_id`, then `product_id` | If your Dotdigital catalogue is keyed on real SKUs, the line will not match a catalogue entry, so merchandising blocks in your emails have nothing to render. | | Cart `subtotal` | The sum of the line totals | Nothing, normally — it is arithmetic on the lines you sent, and excludes tax and shipping exactly as Dotdigital's own subtotal does. If no line carries a price, Chord sends no subtotal and Dotdigital refuses the cart, rather than reporting it as free. | **Sending **`sku`** and **`url`** on your cart lines is worth the effort.** They are the two whose fallbacks change what a shopper sees in an email. Note that Chord's tracking plan currently documents a product `url` at the event level but not inside the `products` array — so per-line URLs are something to add to your event payload deliberately. **Every cart update sends your whole basket, not just the line that changed.** Dotdigital's cart update *replaces* the cart it has stored, and its abandonment timer runs against that. So if your `Product Added` event carries a `products` array, Chord sends all of it. Send the full basket on those events, or Dotdigital's cart will be narrower than your shopper's. A cart update with no `cart_id` is skipped, because Dotdigital tracks abandonment against the cart identifier and a cart with no stable ID looks like a new abandoned cart on every change. # Identity Dotdigital receives the email address, mobile number and name **in plaintext**, and this is deliberate. Dotdigital has to actually deliver mail and SMS to the person, so unlike an advertising pixel it accepts no hashed identifier — hashing would break delivery rather than protect anything. If your security review needs to know exactly what leaves the page, that is the list. | Chord trait | Dotdigital field | | -------------------------- | ---------------- | | `email` | `email` | | `phone` | `mobileNumber` | | `first_name` | `firstName` | | `last_name` | `lastName` | | `first_name` + `last_name` | `fullName` | **Mobile numbers must be in E.164 format** — `+14155550123`. A number with no country code is skipped rather than guessed at: completing it would mean assuming a country, and a wrong assumption can resolve to a real contact somewhere else and send them someone else's messages. Formatting like spaces, dashes and brackets is fine; a leading `00` is treated the same as `+`. An identify with neither an email nor a valid E.164 mobile number is skipped, since Dotdigital has no contact to attach it to. The name fields are Personalization-only. Dotdigital's Marketing platform ignores them, so they matter only if your account uses Personalization. # Custom Events Dotdigital's event taxonomy is **open**: an event Chord has no specific mapping for is forwarded under its own name, and Dotdigital creates an Insight data collection for it. `Loyalty Tier Changed` becomes a `Loyalty_Tier_Changed` collection — Dotdigital replaces non-alphanumeric characters with underscores when it names the collection. Two limits: - **Custom events need the CXDP package** on your Dotdigital account. Without it Dotdigital cannot accept them, and because the Tag's calls are fire-and-forget the rejection is invisible from the page. Turn **Send Custom Events** off if your account does not have CXDP. Turning it off does not affect any of the mapped commerce events. - **Nine collection names are reserved** by Dotdigital for its own features: `cartInsight`, `catalog`, `consentInsight`, `easyEditorExtensions`, `nostoEmailCampaigns`, `orders`, `productCategories`, `webInsight` and `wishList`. An event whose name matches one of those is skipped, and the reason is logged to the browser console. # Property Mappings You can map any event property onto a destination field from the connection's mapping configuration. Mapped properties use a **bare path** on this destination — `properties.customer_type → customer_type`, with no `properties.` prefix on the destination side. **Mapped properties reach custom events only.** They are forwarded as attributes on the custom-event call, and nowhere else. That is a Dotdigital constraint rather than a Chord choice: `identify`, the product calls and every cart call take a fixed set of fields with no property bag anywhere, so an extra key has nowhere to go. A mapping you configure will not appear on a product view, a cart update or an order. Mapping onto a field Dotdigital *does* accept still works — a mapping that rewrites `properties.sku` changes what Chord reads for the product's `sku`, because mappings are applied before the payload is built. It is only destination keys with no Dotdigital equivalent that have nowhere to land. Personal fields — `email`, `phone`, `first_name`, `last_name` and their camelCase forms — are never forwarded as custom attributes. They go through the identification call above instead. # Content Security Policy If your storefront sets a Content Security Policy, the Dotdigital Tag will not load until its hosts are allowed. The symptom is silence: no tracking, no abandonment, and a `Refused to load` or `Refused to connect` message in the browser console. **The first host to allow is the one in your own Tag URL, and it is account-specific.** Dotdigital serves the Tag from `ddlnk.net` for some accounts and from a domain of your own for others — an account configured with a branded sending domain gets a Tag URL like `https://emails.yourbrand.com/DM-0000000000-01/ddgtag.js`. Read the host off the **Tag URL** you pasted into the destination and allow that one, rather than assuming the table below covers you. | Directive | Host | | ------------- | ---------------------------------------------------------------------------------- | | `script-src` | the host from your Tag URL, plus `https://*.ddlnk.net` | | `connect-src` | the host from your Tag URL, plus `https://*.ddlnk.net`, `https://*.trackedweb.net` | Both directives are required. `script-src` lets the Tag load; `connect-src` lets it report — and a policy that allows only the first fails in a way that looks like it worked, because the script runs and nothing reaches Dotdigital. **This list was confirmed on a live account**, with one addition worth knowing: the account tested had a branded domain, and its Tag URL host had to be allowed in `script-src` on top of the two Dotdigital domains. That host differs per account, which is why it cannot be listed here. Dotdigital does not publish its CSP requirements, and the Tag routes to a regional host at runtime, so treat the table as a starting point rather than a complete list. Verify it during setup: load a page with the destination active, then fire a product view, a cart update and an order, and add any host named in a violation. Check the Network tab as well as the console — a blocked image beacon can be quieter than a blocked script. # Gotchas **Two tags is the most common problem.** If page views look doubled or abandonment fires against a cart that does not match, check whether a hand-installed Dotdigital Tag or a platform app is still on the page. **Dotdigital's calls are fire-and-forget.** They return nothing and throw nothing, by design, so a rejected call does not surface on the page. To confirm a call succeeded, inspect the request in your browser's Network tab: a `200` means Dotdigital accepted it, a `4xx` means something is misconfigured. **Cart abandonment needs a cart update on every page.** Dotdigital's timer runs from the last cart update it saw, so a storefront that only reports the cart on the cart page will trigger abandonment early. Fire a cart-bearing event as the shopper continues browsing. **An empty **`Order Completed`** is skipped.** An order event with no products is not sent, because it would write an empty order into the collection your post-purchase programs and order content blocks read — an email with nothing in it. **Consent gating applies.** If the destination is configured with required consent categories, no Dotdigital call is made for visitors who have not accepted them. **Updated 9 September 2026** [title] Amplitude [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ # Introduction Chord CDP supports two Amplitude destination modes that share the same default event routing and custom action mappings. Most importantly, the Device Mode destination ensures that the session is passed along to the cloud mode destination. The device mode destination need to be enabled for accurate session tracking in the Cloud Mode, even if only the cloud mode is used to send events. With the device mode destination, the CDP event will contain `context.clientIds.amplitudeSessionId` with the current users session ID. # Requirements | Feature | Requires | | ----------------------- | ------------------------------------------------ | | Basic event tracking | API Key | | User identification | API Key | | Group analytics | API Key + Secret Key + Amplitude Accounts add-on | | User aliasing (mapUser) | API Key + Secret Key | # Destination modes | Mode | ID | Description | | --------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------- | | **Cloud Mode** | amplitude-cloud | Server-side integration using Amplitude HTTP API v2. Events are sent from Chord's servers directly to Amplitude. | | **Device Mode** | amplitude-pixel | Client-side integration that loads the Amplitude SDK in the browser. Enables session tracking and real-time event capture. | ## Connecting to an Amplitude CDP destination 1. Log into the Chord data platform. 2. Navigate to the CDP. 3. Click the **"Add"** button next to Destinations. 4. Select **Amplitude (Cloud Mode) **or** Amplitude (Device Mode) **from the destination catalog. 5. For the **Amplitude (Cloud Mode)** destination, enter in the destination name and the **Project API Key. **You can also include the Project Secret Key, Region, and Custom Action Mappings. 6. For the **Amplitude (Device Mode)** destination, enter in the destination name and the **Amplitude API key.** You can also toggle track configurations. 7. Click **"Create" **to connect. :::hint{type="warning"} Please reach out to ***help\@chord.co ***if you are looking to utilize Amplitude's advanced features like [Autocapture](https://amplitude.com/docs/data/autocapture) & [Visual Labeling](https://amplitude.com/docs/data/visual-labeling)***, ***as the implementation will vary. ::: ## Configuration ### Cloud mode settings | Field | Required | Description | | ---------------------- | -------- | ----------------------------------------------------------------------------------------------------- | | **Project API Key** | Yes | Your Amplitude Project API Key. Found in Amplitude under Data > Sources & Destinations. | | **Project Secret Key** | No | Required only for group identify and user mapping operations. Found in Data > Sources & Destinations. | | **Region** | No | north\_america (default) or europe. Select Europe if your Amplitude project is in the EU data center. | ### Device mode settings | Field | Default | Description | | --------------------------------- | ------- | ----------------------------------------------------------------------------- | | **API Key** | — | Your Amplitude project's API Key | | **Track All Pages** | false | Send a "Loaded a Page" event for every page() call | | **Track Named Pages** | true | Send "Viewed \[Name] Page" when page name is provided | | **Track Categorized Pages** | true | Send "Viewed \[Category] Page" when category is provided | | **Track UTM Properties** | true | Automatically capture UTM parameters from the URL | | **Track Referrer** | false | Include referrer information in events | | **Use Anonymous ID as Device ID** | false | Use Chord's anonymousId as Amplitude's device\_id for cross-platform tracking | | **Session Timeout** | 30 | Minutes of inactivity before starting a new session | ## Default event routing Both Cloud and Device modes use the same default routing: | Source Event | Amplitude Action | Notes | | --------------- | ----------------- | ----------------------------------------------- | | track | logEventV2 | All track events except Order Completed | | Order Completed | logPurchase | Includes revenue tracking | | identify | identifyUser | Updates user properties | | page / screen | logEventV2 | Sent as "Viewed \[name]" | | group | groupIdentifyUser | Requires Amplitude Accounts add-on & Secret Key | | alias | mapUser | Merges user identities. Requires Secret Key | ## Default field mappings The following tables show how Chord CDP event fields are automatically mapped to Amplitude fields. ### User & device identification | Source Field | Amplitude Field | Notes | | ----------------- | --------------- | ------------------------------ | | userId | user\_id | Primary user identifier | | context.device.id | device\_id | Falls back to anonymousId | | anonymousId | device\_id | Used when device.id is not set | | messageId | insert\_id | Deduplication key | ### Device & platform | Source Field | Amplitude Field | Fallback | | --------------------------- | -------------------- | ----------------------------------------------- | | context.device.type | platform | user.deviceType, or "Web" for analytics.js | | context.os.name | os\_name | user.deviceOs, parsed from User-Agent | | context.os.version | os\_version | user.deviceOsVersion, parsed from User-Agent | | context.device.brand | device\_brand | — | | context.device.manufacturer | device\_manufacturer | user.deviceManufacturer, parsed from User-Agent | | context.device.model | device\_model | user.deviceModel, parsed from User-Agent | | context.network.carrier | carrier | user.deviceCarrier | | context.userAgent | user\_agent | — | | context.app.version | app\_version | — | ### Location & locale | Source Field | Amplitude Field | Fallback | | -------------------------- | --------------- | -------------------- | | context.location.country | country | user.address.country | | context.location.region | region | user.address.state | | context.location.city | city | user.address.city | | context.location.dma | dma | — | | context.location.latitude | location\_lat | user.deviceLatitude | | context.location.longitude | location\_lng | user.deviceLongitude | | context.locale | language | user.locale | | context.ip | ip | user.ip | ### Event data | Source Field | Amplitude Field | Notes | | ------------------------------------ | ----------------- | --------------------------------- | | event | event\_type | For page/screen: "Viewed \[name]" | | timestamp | time | Converted to milliseconds | | properties | event\_properties | All event properties | | context.clientIds.amplitudeSessionId | session\_id | For session tracking | | context.library.name | library | Defaults to "chordcdp" | | context.groups | groups | For group analytics | ### Mobile advertising IDs | Source Field | Amplitude Field | Notes | | ---------------------------- | --------------- | ---------------------- | | context.device.advertisingId | idfa | iOS Advertising ID | | context.device.idfa | idfa | Alternative source | | context.device.advertisingId | adid | Android Advertising ID | | context.device.adid | adid | Alternative source | | context.device.id | idfv | iOS Vendor ID | ### Revenue fields (logPurchase action) | Source Field | Amplitude Field | Notes | | ------------------------ | ----------------- | --------------------------------------------- | | properties.revenue | revenue | Total revenue amount | | properties.price | price | Unit price | | properties.quantity | quantity | Number of items | | properties.productId | productId | Product identifier | | properties.revenueType | revenueType | e.g., "purchase", "refund" | | properties.products\[\*] | Individual events | Creates "Product Purchased" event per product | ### UTM & campaign tracking Campaign parameters are mapped to user properties with both current and initial values: | Source Field | $set Property | $setOnce Property | | ------------------------ | ------------- | ---------------------- | | context.campaign.source | utm\_source | initial\_utm\_source | | context.campaign.medium | utm\_medium | initial\_utm\_medium | | context.campaign.name | utm\_campaign | initial\_utm\_campaign | | context.campaign.term | utm\_term | initial\_utm\_term | | context.campaign.content | utm\_content | initial\_utm\_content | | context.page.referrer | referrer | initial\_referrer | User traits from identify calls are also set via user\_properties.$set. ## Amplitude actions reference | Action | Description | | ----------------- | -------------------------------------------------------------------- | | logEventV2 | Track a standard event with properties | | identifyUser | Update user properties without tracking an event | | logPurchase | Track a revenue event (includes revenue, price, quantity, productId) | | mapUser | Merge two user identities (alias). Requires Secret Key | | groupIdentifyUser | Update group properties. Requires Secret Key | | logEvent | Legacy event tracking (use logEventV2 instead) | ## Custom action mappings Override the default routing or add field transformations using **Custom Action Mappings**. ### Use cases - **Route specific events** — Send Subscription Started to logPurchase instead of logEventV2 - **Rename events** — Transform Button Clicked → CTA Interaction - **Map custom fields** — Map any property to Amplitude fields using dot notation - **Filter events** — Use $drop as target event name to exclude events ### Mapping fields | Field | Description | | --------------------- | ---------------------------------------------------------------------------------------------- | | **Source Event(s)** | Event(s) to match. Comma-separated for multiple (e.g., Purchase,Subscription). Use \* for all. | | **Amplitude Action** | Which Amplitude API to call | | **Target Event Name** | Override the event name. Leave empty for original. Use $drop to filter out. | | **Field Mappings** | Map source properties to Amplitude fields | ### Property path examples :::BlockQuote properties.product\_id → Access a top-level property properties.products\[0].sku → Access first item in an array properties.products\[\*].sku → Access ALL items in an array (wildcard) context.campaign.source → Access nested context fields traits.email → Access user traits (for identify events) ::: ### Target property examples :::BlockQuote event\_properties.item\_id → Set an event property user\_properties.$set.plan → Set a user property revenue → Set the revenue field productId → Set the product ID ::: ### Match priority 1. **Exact match** — Event name matches exactly (e.g., Order Completed) 2. **Type match** — Event type matches (e.g., track matches all track events) 3. **Wildcard** — \* matches all events (lowest priority) ## Examples ### Route subscription events to revenue tracking :::BlockQuote Source Event: Subscription Started, Subscription Renewed Action: logPurchase ::: ### Rename an event :::BlockQuote Source Event: Button Clicked Action: logEventV2 Target Event: CTA Interaction ::: ### Map custom fields for purchase events :::BlockQuote Source Event: Order Completed Action: logPurchase Field Mappings: \- properties.order\_id → event\_properties.order\_id \- properties.items\[\*].sku → event\_properties.product\_ids \- properties.total → revenue ::: ### Drop unwanted events :::BlockQuote Source Event: Internal Debug Event Action: logEventV2 Target Event: $drop ::: :::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] Klaviyo [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ # Introduction Klaviyo is a marketing automation platform built specifically for e-commerce brands, designed to help them deliver personalized customer experiences through email and SMS. It empowers marketers to build targeted campaigns, automate messaging flows, and measure performance using rich customer data. By integrating directly with e-commerce platforms and pulling in behavioral and transactional data, Klaviyo enables brands to turn insights into action—driving higher engagement, loyalty, and revenue. # Getting started Before connecting your Klaviyo account as a CDP destination, a custom ***Private API Key*** must be generated with a specific set of configured scopes: ::Image[]{src="https://api.archbee.com/api/optimize/TmutqdeXiIw-V3gBZXVjd/XqYoeOqe3OBdoRcxm2aPO_image.png" size="80" width="3174" height="1804" position="center" darkWidth="3174" darkHeight="1804" showCaption="false"} Once you have navigated to create a new private API Key (*Settings *> *Account* > *API Keys*), the scopes to configure are: - **Events API **scope must be set to `Read/Write Access` - All other API scopes can be set to `Read Access` ::Image[]{src="https://api.archbee.com/api/optimize/VPxpEoMPxDsnmxOyjOdWV-ATniMZHlo2xXr5SwGVX5x-20250514-215853.png" size="80" width="2890" height="1558" position="center" darkWidth="2890" darkHeight="1558" showCaption="false"} Once configured, click **Create** in the top-right corner. The API key permissions for you newly created key will appear as follows: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-sPZrWt135KCw2i487GaRk-20250514-220026.png" size="48" width="1398" height="428" position="center" darkWidth="1398" darkHeight="428" showCaption="false"} # Connecting to the Klaviyo CDP destination 1. Log into the Chord data platform. 2. Navigate to the CDP. 3. Click the **"Add" **button next to Destinations. 4. Select **Klaviyo** from the destination catalog. 5. Enter in the destination name and the** Klaviyo** API key. 6. Click **"Create"** to connect. # Chord events relevant for destination While typically not all Chord Tracking events are used downstream in your configured destinations, Klaviyo is an exception. As a SMS and email marketing platform, Chord passes through all availalbe/possible *track* events that are passed through any configured sources upstream. **All track events are sent to Klaviyo's **[Custom Events API](https://developers.klaviyo.com/en/reference/events_api_overview)** with their original name.** The use cases supported by Klaviyo's Custom Events API include: - *Creating custom events that can be used to trigger flows (e.g., a Reset Password event that triggers an email with a reset password URL).* - *Getting Klaviyo events that can be used for data analysis (e.g., retrieving engagement events tracked by native Klaviyo metrics, such as Opened Email and Clicked SMS).* - *Getting a specific profile’s events to power an activity feed.* - *Getting related profile and/or metric data for a given event.* Chord will only send events through to Klaviyo if either `email` or `phone` is present in the event payload. Without this identifying attributes, events are skipped. **Note: **Attentive's Custom Events API is specifically designed to ingest *user action events*. Considering this, *page view *events **are not** passed through. | **Chord Tracking Event** | *Destination Event/Action* | | ------------------------ | --------------------------------------------------- | | **All Track Events** | *Event name passed as is* | | **Identify** | *Upsert Profile (to create or update user profile)* | :::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] Google Analytics 4 (Device Mode) [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ Google Analytics 4 (GA4) is a web and app analytics tool that tracks user behavior across digital properties. The platform enables event-based tracking, cross-platform insights, and predictive metrics to help organizations understand and optimize customer journeys. # Getting Started This is a device mode destination requiring the Measurement ID from your Google Analytics property. To locate this identifier, refer to [Google's support documentation](https://support.google.com/analytics/answer/9539598?hl=en). # Connecting to the Google Analytics 4 (Device Mode) 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 **Google Analytics 4** from the destination catalog. 5. Enter the destination name and **Measurement ID**. 6. Click **"Create"** to connect. # Event Mapping 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. # Supported Events | Chord Tracking Event | GA4 Event | | ------------------------- | ------------------------- | | Cart Viewed | `view_cart` | | Checkout Started | `begin_checkout` | | Custom Events | snake\_case name (direct) | | Generate Lead | `generate_lead` | | Order Completed | `purchase` | | Order Refunded | `refund` | | Page | `page_view` | | Payment Info Entered | `add_payment_info` | | Product Added | `add_to_cart` | | Product Added to Wishlist | `add_to_wishlist` | | Product Clicked | `select_item` | | Product List Viewed | `view_item_list` | | Product Removed | `remove_from_cart` | | Product Viewed | `view_item` | | Products Searched | `search` | | Promotion Clicked | `select_promotion` | | Promotion Viewed | `view_promotion` | | Signed In | `login` | | Signed Up | `sign_up` | # Event Attributes # Order Completed (`purchase`) | GA4 Attribute | Chord Source (in priority order) | Notes | | ---------------- | --------------------------------------------------------------------------- | ----------------------------------------- | | `transaction_id` | `properties.order_id` / `properties.orderId` | Order identifier | | `value` | `properties.total` > `properties.revenue` | Conversion value | | `currency` | `properties.currency` > `properties.meta.i18n.currency` > `"USD"` (default) | | | `coupon` | `properties.coupon` | Coupon code; omitted if not present | | `shipping` | `properties.shipping` | Shipping cost; omitted if not present | | `tax` | `properties.tax` | Tax amount; omitted if not present | | `discount` | `properties.discount` | Discount amount; omitted if not present | | `affiliation` | `properties.affiliation` | Store affiliation; omitted if not present | | `items` | `properties.products[]` | Array of product items (see below) | # Product Added (`add_to_cart`) | GA4 Attribute | Chord Source (in priority order) | Notes | | ------------- | --------------------------------------------------------------------------- | --------------------------------------- | | `value` | `properties.value` > `properties.total` > `properties.revenue` | Conversion value | | `currency` | `properties.currency` > `properties.meta.i18n.currency` > `"USD"` (default) | | | `discount` | `properties.discount` | Discount amount; omitted if not present | | `items` | `properties.products[]` | Array of product items (see below) | # Checkout Started (`begin_checkout`) | GA4 Attribute | Chord Source (in priority order) | Notes | | ------------- | --------------------------------------------------------------------------- | ----------------------------------- | | `value` | `properties.value` > `properties.total` > `properties.revenue` | Conversion value | | `currency` | `properties.currency` > `properties.meta.i18n.currency` > `"USD"` (default) | | | `coupon` | `properties.coupon` | Coupon code; omitted if not present | | `items` | `properties.products[]` | Array of product items (see below) | # Order Refunded (`refund`) | GA4 Attribute | Chord Source (in priority order) | Notes | | ---------------- | --------------------------------------------------------------------------- | ---------------- | | `transaction_id` | `properties.order_id` / `properties.orderId` | Order identifier | | `value` | `properties.total` > `properties.revenue` | Refund value | | `currency` | `properties.currency` > `properties.meta.i18n.currency` > `"USD"` (default) | | | `coupon` | `properties.coupon` | | | `shipping` | `properties.shipping` | | | `tax` | `properties.tax` | | | `affiliation` | `properties.affiliation` | | | `items` | `properties.products[]` | | # Product Viewed (`view_item`), Cart Viewed (`view_cart`), Product Removed (`remove_from_cart`), Product Added to Wishlist (`add_to_wishlist`) | GA4 Attribute | Chord Source (in priority order) | Notes | | ------------- | --------------------------------------------------------------------------- | ----- | | `value` | `properties.value` > `properties.total` > `properties.revenue` | | | `currency` | `properties.currency` > `properties.meta.i18n.currency` > `"USD"` (default) | | | `items` | `properties.products[]` | | # Payment Info Entered (`add_payment_info`) | GA4 Attribute | Chord Source (in priority order) | Notes | | -------------- | --------------------------------------------------------------------------- | ----- | | `value` | `properties.value` > `properties.total` > `properties.revenue` | | | `currency` | `properties.currency` > `properties.meta.i18n.currency` > `"USD"` (default) | | | `coupon` | `properties.coupon` | | | `payment_type` | `properties.payment_method` | | | `items` | `properties.products[]` | | # Products Searched (`search`) | GA4 Attribute | Chord Source | Notes | | ------------- | ------------------ | ----- | | `search_term` | `properties.query` | | # Signed In (`login`) / Signed Up (`sign_up`) | GA4 Attribute | Chord Source | Notes | | ------------- | --------------------------------------- | ----- | | `method` | `properties.type` > `properties.method` | | # Product Item Attributes Each item in the `items` array contains: | GA4 Item Attribute | Chord Source | Notes | | ------------------ | ------------------------------- | ---------------- | | `item_id` | product `id` | Required | | `item_name` | product `name` | Required | | `item_brand` | product `brand` | | | `item_category` | product `category` | | | `item_variant` | product `variant` | | | `price` | product `price` | | | `quantity` | product `quantity` | | | `coupon` | product `coupon` | | | `discount` | product `discount` | | | `affiliation` | product `affiliation` | | | `index` | product `position` | | | `currency` | Inherited from order `currency` | Set on each item | # Identify Identify events set GA4 user properties from `context.traits`. Reserved properties (`first_open_time`, `first_visit_time`, `last_deep_link_referrer`, `user_id`, `first_open_after_install`) and properties prefixed with `google_`, `ga_`, or `firebase_` are excluded. # CSP Requirements If your site uses a Content Security Policy, allow the following domains: | Directive | Domain | | ------------- | ---------------------------------------------------------------------- | | `script-src` | `https://www.googletagmanager.com` | | `connect-src` | `https://www.googletagmanager.com`, `https://www.google-analytics.com` | *** **Updated 09 Mar 2026** [title] Google Analytics 4 (Measurement Protocol) [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ # Introduction The Google Analytics 4 (GA4) Measurement Protocol is a set of rules that lets you send event data directly to GA4 from a server or backend system, rather than from a browser or app. It’s useful for tracking events that happen outside of a user’s device—like purchases from a third-party payment system or offline interactions. It complements client-side tracking and helps bridge gaps in your analytics data. # Getting started You will need the relevant API Secret and Measurement ID of your Google Analytics property to connect this destination. ## Obtain the API secret An API SECRET generated in the Google Analytics UI. To create a new secret, navigate to: **Admin > Data Streams > choose your stream > Measurement Protocol API Secrets > Create** ## Obtain the Measurement ID The GA4 Measurement ID associated with a stream. - **For Web: **Locate this in the Google Analytics UI under **Admin > Data Streams > choose your stream > Measurement ID** - **For Apps**: Locate the the Firebase App ID, found in the Firebase console under **Project Settings > General > Your Apps > App ID** # Connecting to the Google Analytics 4 (Measurement Protocol) CDP destination 1. Log into the Chord data platform. 2. Navigate to the CDP. 3. Click the **"Add" **button next to Destinations. 4. Select **Google Analytics 4 (Measurement Protocol) **from the destination catalog. 5. Enter in the destination name, **API Secret**, and the **Measurement ID**. 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 [Google Analytics 4 (Measurement Protocol)](https://developers.google.com/analytics/devguides/collection/protocol/ga4/reference/events) destination are: | **Chord Tracking Event** | *Destination Event* | | ----------------------------- | --------------------------- | | **Cart Viewed** | *view\_cart* | | **Checkout Started** | *begin\_checkout* | | **Custom Events** | *snake\_case name (direct)* | | **Generate Lead** | *generate\_lead* | | **Order Completed** | *purchase* | | **Order Refunded** | *refund* | | **Page** | *page\_view* | | **Payment Info Entered** | *add\_payment\_info* | | **Product Added** | *add\_to\_cart* | | **Product Added to Wishlist** | *add\_to\_wishlist* | | **Product Clicked** | *select\_item* | | **Product List Viewed** | *view\_item\_list* | | **Product Removed** | *remove\_from\_Cart* | | **Product Viewed** | *view\_item* | | **Products Searched** | *search* | | **Promotion Clicked** | *select\_promotion* | | **Promotion Viewed** | *view\_promotion* | | **Signed In** | *login* | | **Signed Up** | *sign\_up* | :::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] Facebook Conversions API Diagnostic Guide [path] Chord CDP/CDP Destinations/CDP Destination Catalog/Facebook (Meta) CAPI/ If you're experiencing issues with your Facebook Conversions API (CAPI) destination, this guide will walk you through common problems and how to resolve them. Each flow below addresses a specific issue with step-by-step troubleshooting instructions. ## Events not appearing in events manager **Symptoms:** - Expected server events (like `Purchase`) are not visible in Meta Events Manager. - You’ve recently configured CAPI but see no activity. **How to troubleshoot:** 1. Confirm the CAPI destination is created in Chord CDP and has an active connection with a back end source. 1. Verify the Pixel ID and Access Token values for the destination correspond with the values listed in your Meta Business/Events Manager account 2. Go to Meta’s **Test Events tool** and trigger a known action. 3. Look for **HTTP 200 responses** and verify no errors like: - `401 Unauthorized` → Invalid token or app config - `400 Bad Request `→ Missing or incomplete payload 4. Retry with a minimal payload (just `event_name`, `event_time`, and `user_data`) to isolate the issue. ## Duplicate events or overcounting **Symptoms:** - Conversion counts appear inflated in Meta Ads Manager. - Same action appears twice under “Received Events.” **How to troubleshoot:** 1. Check whether **Pixel and CAPI are both firing** the same event. 2. Confirm the `event_id` field is included in both and matches exactly. 3. Visit Meta Events Manager → **Diagnostics tab** to see any deduplication warnings. 4. Use the **Test Events tool** and look for a single deduplicated instance of the event. ## Low match rate or inaccurate attribution **Symptoms:** - Meta Ads Manager reports poor attribution for key campaigns. - Low conversion match rates despite CAPI being enabled. **How to troubleshoot:** 1. Confirm that `user_data `includes identifiers like: - `fbc `/ `fbp` - Array of hashed external\_ids including Anonymous ID and User ID - Hashed email (`em`) - Hashed Phone (`ph`) - Hashed zip code (`zp`) - Hashed country (`ct`) - Hashed first name (`fn`) - Hashed last name (`ln`) 2. Turn on **Advanced Matching** in the Meta Pixel settings. 3. Optionally, A/B test campaigns with vs. without CAPI enabled to evaluate impact. ## Best practices recap | **Recommendation** | **Why It Helps** | | ------------------------ | ------------------------------------- | | Use CAPI + Pixel | Covers blind spots, improves accuracy | | Use matching `event_id` | Prevents overcounting | | Include full `user_data` | Boosts attribution match rates | | Monitor Diagnostics tab | Flags misconfigurations | | Test frequently | Verifies end-to-end setup | [title] AWIN Pixel [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ # Introduction The AWIN Pixel (formerly the ShareASale Pixel) is a piece of tracking code used to record conversions and attribute sales or leads generated through affiliate marketing campaigns on the AWIN network. It enables advertisers to measure which publishers or partners drove each transaction, track performance metrics like order value and commission, and optimize affiliate payouts accordingly. # Getting started You will need the AWIN Merchant ID in order to connect this destination. You can find this ID in your AWIN Account under the drop-down menu when you click on the tab labeled "Overview". Your Merchant ID (MID) will be shown underneath your account name. # Connecting to the AWIN Pixel CDP destination :::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. *** ::: 1. Log into the Chord data platform. 2. Navigate to the CDP. 3. Click the **"Add" **button next to Destinations. 4. Select **AWIN Pixel **from the destination catalog. 5. Enter in the destination name and the AWIN Merchant ID. 6. Click **"Create" **to connect. # Events This destination does not forward individual page, track, or identify events. The Awin SDK is loaded on the first event received from any type, and from that point the SDK handles all affiliate tracking autonomously. ## Initialization The plugin loads the SDK on the first event it receives, regardless of event type. It does not queue or process subsequent events — its sole purpose is to ensure the Awin script is loaded once. The plugin manages SDK loading state (`fresh` → `loading` → `loaded`/`failed`) to prevent duplicate script loads. If the script fails to load, no further load attempts are made. ## CSP requirements If your site uses a Content Security Policy, allow the following domains: | Directive | Domain | | ------------- | ----------------------- | | `script-src` | `https://www.dwin1.com` | | `connect-src` | `https://www.dwin1.com` | [title] Get started with Chord CDP [path] Chord CDP/ # Overview Getting started with Chord CDP is seamless. In the sections below, we'll guide you through the following: - Understanding the CDP onboarding process - Connecting a destination and viewing event streams # Chord CDP onboarding All new Chord customers **after January 2025** will be able to leverage Chord CDP upon signing up for the Chord platform. No additional work beyond the initial implementation period will be required from your team. Legacy Chord customers **prior to January 2025** who are eligible to use Chord CDP will be migrated to the CDP by our implementation team. The Chord team will work with your development team to replace the existing CDP snippet with a Chord CDP snippet and work with you to understand any impacts to how you are currently handling consent management. # CDP overview Chord brands will be able to manage their CDP sources and destinations through the CDP page on the Chord data and analytics platform. With Chord CDP, you will be able to take the following actions: - View all connected sources and destinations that were set up during initial implementation. - View event streams for incoming and destination events for event monitoring. - Add additional destinations using the Chord destination catalog (**admin users only**). - Edit or delete connected destinations (**admin users only**). ## Connecting a destination The Chord CDP [destinations catalog](https://docs.chord.co/cdp-destination-catalog) has a number of key destinations that you can connect to, including (but not limited to): - Attentive - Braze - Facebook Conversions API - GA4 - GA4 (device mode) - Klaviyo :::hint{type="info"} Note: We will continually add additional destinations to the catalog. Is your desired destination not in our CDP catalog? Send us a note and we’ll consider adding it to our catalog! ::: See more information about CDP Destinations [here](https://docs.chord.co/cdp-destinations). To add destinations, admin-level users can take the following steps to set up destinations via our [destination catalog](https://docs.chord.co/cdp-destination-catalog): 1. On the CDP overview page, click the “**Add”** button on the right. 2. You will be taken to the destinations catalog. Scroll to view the destination options in the catalog and select the destination you’d like to connect. 3. Complete the destination connection steps as provided on the screen. Click “**Create**” to complete your destination set up. ## Event stream monitoring You can easily view all incoming and destination events through our CDP. ### Incoming events To view all incoming events (tracked events from both your storefront and checkout), click on the **Incoming Events** tab. The following filters can be applied to view specific events: - **Sites**: If you have multiple source connectors, you can select to view events from a specific source connector. - **Status:** Can see all events or filter and see events with errors. - **Start and End Date:** Can view specific incoming events over a certain timeframe by using these filters. ### Destination events To view all destination events (events that are getting sent to specific connected destinations), click on the **Destination Events** tab. The following filters can be applied to view specific events: - **Connection:** Select a specific destination event stream you’d like to view. - **Status:** Can see all events or filter and see events with errors. - **Mode:** Can filter by Batch or Stream options. - **Start and End Date:** Can view specific destination events over a certain timeframe by using these filters. # Troubleshooting and FAQs - **Question: Will there be significant differences in tracked events with Chord CDP?** - There will be no differences in tracked events. The events API will remain exactly the same. - **Question: Will there be any differences in user identification or how Chord unifies customer profiles given Chord CDP?** - There will be no differences in user identification or user stitching processes on the Chord side, as this is all handled by our data modeling layer which is unchanged. [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] Braze [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ # Chord x Braze Integration The Chord’s Customer Data Platform (CDP) integrates with Braze to automatically forward ecommerce event data, such as purchases, user behavior, and identity updates, directly into Braze. This enables marketers to trigger personalized campaigns based on real-time shopper actions without manual data pipelines.  This integration is maintained by Chord.  ## About this integration Chord's CDP captures and standardizes customer events from your ecommerce storefront. By connecting Chord to Braze, marketers gain access to rich behavioral data (such as completed orders, product interactions, and customer identity updates) that can power personalized messaging at scale. Chord acts as the data layer that feeds Braze with clean, structured ecommerce events so your campaigns reflect what customers are actually doing. ## Use cases - **Post-purchase messaging**: Trigger order confirmation flows, upsell sequences, or review requests in Braze when a customer completes an order in Chord. - **Customer attribute sync**: Keep Braze user profiles updated with the latest customer data from Chord to improve segmentation accuracy. - **Behavioral retargeting**: Use Chord event data to power win-back or re-engagement campaigns in Braze for customers who haven't converted recently. ## Prerequisites Before you start, you need the following: | **Prerequisite** | **Description** | | --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | A Chord account | A Chord account is required to take advantage of this partnership.  | | A Braze REST API key | A Braze REST API key with the appropriate permissions.

* For **cloud mode**: find this key under **Developer Console** in the Braze dashboard.  * For **device mode**: find this key under **Settings > App Settings > Web > API Key**. 
***Note these are two distinct API keys.*** | | A Braze REST endpoint | Chord sends data to the following Braze endpoints: `/users/track` and `/users/identify`. The base URL depends on your Braze cluster and follows the format `https://rest.iad-0#.braze.com`. For example: `https://rest.iad-01.braze.com/users/track` and `https://rest.iad-01.braze.com/users/identify`. | ## Integrate Chord with Braze Chord supports two connection modes: **Cloud Mode** and **Device Mode**. Follow the steps for your preferred mode. ### Cloud Mode ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/R7DOFQnyV-_vzXt8ohiUV_.blob) ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/9gtXN7F-8kpSuJGPaxRCt_.blob) **Step 1: Navigate to Destinations in the Chord CDP** 1. Log into the Chord Data Platform. 2. Navigate to the **CDP**. 3. Click the **Add** button next to **Destinations**. **Step 2: Connect Braze (Cloud Mode) as a destination** 1. Select **Braze** from the destination catalog. 2. Enter a destination name and your Braze API key (found under **Developer Console** in the Braze dashboard). Click **Create** to connect. ### Device Mode ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/13Z-V7sf1pqqhD4MVQ89A_.blob) ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/nqDvmb9bDmVD4vWn9nHbG_.blob) **Step 1: Navigate to Destinations in the Chord CDP** 1. Log into the Chord Data Platform. 2. Navigate to the **CDP**. 3. Click the **Add** button next to **Destinations**. **Step 2: Connect Braze (Device Mode) as a destination** 1. Select **Braze (Device Mode)** from the destination catalog. 2. Enter a destination name and your Braze API key (found under **Settings > App Settings > Web > API Key** — note this is distinct from your classic Braze API key). 3. Click **Create** to connect. ## Customize Chord + Braze ### Step 1: Select SDK Version 1. Select the version of the Braze SDK to use. 2. Braze SDK Versions 4.1 through 5.9 available. ### Step 2: Select Endpoint 1. Select the correct [Braze SDK endpoint](https://www.braze.com/docs/user_guide/administer/personal/sdk_endpoints?redirected=1) for your application. 2. Braze endpoints US-01 through US-09 & EU-01 through EU-02 are available. ### Step 3: Select Event Config Options 1. Enable Order Completed Calls 2. Enable Track Calls 3. Enable Identify Calls 4. Send Page Events 5. Page Event Name 6. Allowed User Supplied JavaScript 7. Automatically Send In App Messages 8. Eager SDK Initialization 9. Consent Requirements 10. Send Null Consent Events ## Use Chord with Braze Once connected, Chord maps its tracking events to Braze as follows (Device Mode): | **Chord Event** | **Braze Event** | | ---------------------- | ----------------------------------- | | `order_completed` | `logPurchase` | | All other track events | `logCustomEvent` | | `identify` | `getUser` (updates user attributes) | **Step 1: Access event data in Braze.** After setup, Chord events will begin flowing into Braze automatically. Navigate to your Braze dashboard to verify event receipt under your user profiles or event stream. **Step 2: Build campaigns using Chord data.** Use the synced events and user attributes in Braze to create segments, trigger Canvas flows, or power message personalization based on real customer behavior from your Chord storefront. ## Considerations - **Avoid duplicate events:** Before connecting Braze through the Chord CDP, confirm with all destination owners that any non-Chord CDP configured destinations sending to Braze are disabled. Running external destinations alongside Chord CDP destinations can result in duplicate events downstream. - Not all Chord tracking events are forwarded to Braze. Only the events mapped in the Chord tracking plan are relayed to configured destinations. ## Troubleshooting If you are unable to verify events properly being passed through to Braze from Chord, there are a few checks to be made to confirm that data is properly to and from Chord into Braze.  - **Ensure that live tracking events are arriving in the Chord CDP**: Verify in the [Live Events](https://docs.chord.co/cdp-live-events) tab of the Chord CDP that there are live events being fired from all relevant sources. Without live events, there will be nothing to pass through to Braze. - **Ensure that these live events are properly being passed to your configured Braze destinations:** - First, validate that your configured Braze destinations are configured correctly with the appropriate API key, SDK braze version and endpoint. ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/677SiCNpFhxzBjIVeA2pl_.blob) :::Paragraph{listStyleType="disc" indent="2"} Second, validate that your configured Braze destinations are properly *connected *to a corresponding *source* in the Chord CDP ::: ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/xXTA797lutUnV5lBP9qnz_.blob) :::Paragraph{listStyleType="circle" indent="2"} Once validated, confirm that events are firing AND are successfully sending to the Braze API endpoint (*Live Events > API Destinations & Function Logs*). ::: :::Paragraph{listStyleType="circle" indent="2"} Verify successful hits to the `/users/track` and `/users/identify` endpoints. ::: ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/Vd2WvL5byxHw5Lx-VyKz1_.blob) :::Paragraph{listStyleType="disc" indent="2"} Confirm events in your Braze dashboard. ::: - Additional destination documentation can be found here: - [Braze (Cloud Mode)](docId\:dYuyxHKXLBUsGlbJaWkmT) - [Braze (Device Mode)](docId\:e9N1bM5ceV1XTC2rByk8z) [title] Microsoft CAPI [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ The **Microsoft Conversions API** (CAPI) is a server-side integration that sends event data directly from Chord CDP to Microsoft Advertising's servers. Unlike the Bing Ads UET Tag (which runs in the browser), the Conversions API operates in cloud mode — events are sent server-to-server, making them immune to ad blockers and browser tracking restrictions. Microsoft recommends using the Conversions API alongside the UET Tag for maximum data coverage. When both are configured, Microsoft automatically deduplicates events using the `eventId` field. Use this destination if: - You run paid media through Microsoft Advertising - You want improved signal reliability independent of browser limitations or ad blockers - You want to support Microsoft's automated bidding and optimization with high-quality server-side event data # Getting Started This is a cloud-mode destination. You will need: - **UET Tag ID** — found in your Microsoft Ads dashboard under Conversion tracking > UET tags. We recommend creating a dedicated tag for the Conversions API - **Access Token** — select "Use Conversions API" on your UET tag in the Microsoft Ads dashboard to generate a token. Contact your Microsoft account manager if this option is not available - **Site URL** — your storefront URL, e.g. `https://www.example.com`. - **Optional in general**, but **required for back-end (server-side) connections**: Microsoft rejects events with an empty `eventSourceUrl`, and server-side events carry no page URL, so this value is used as the fallback. Browser connections don't need it (the event's own page URL is used). Without it, back-end purchase events are rejected with a `400 ValidationError`. # Connecting to the Microsoft 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 **Microsoft Conversions API** from the destination catalog. 5. Enter the destination name, **UET Tag ID**, and **Access Token**. 6. Click **"Create"** to connect. # Event Architecture Microsoft CAPI requires a `pageLoad` event to establish page context. Chord CDP handles this automatically: - **Page events** send a single `pageLoad` event - **Track events** send a `pageLoad` + `custom` event pair, linked by a shared page load ID This means Microsoft receives the page context needed for accurate attribution without any additional configuration. # Events # Event Mapping By default the event action (`eventName`) sent to Microsoft is the Chord event's **own name** (e.g. `Order Completed`). This matches the Bing UET device-mode pixel, which sends the raw event name, so the two surfaces can share a single conversion goal. Recognized commerce events additionally get a `pageType`: | Chord Event | Page Type | | ---------------------- | --------------- | | Product Viewed | `product` | | Products Searched | `searchresults` | | Product Added | `cart` | | Checkout Started | `cart` | | Order Completed | `purchase` | | Order Placed | `purchase` | | *(other track events)* | *(none)* | Page and track events are forwarded. Identify and screen events are ignored. ## Overriding the event action The **Event Mapping** config setting overrides the event action for specific events. Unmapped events keep the raw-name default, so this is purely additive. Use it when a conversion goal expects a different action string — for example a customer who prefers snake\_case, or a goal keyed on `order_completed`: ```javascript { "Order Completed": "order_completed", "Product Added": "product_added" } ``` Goal matching in Microsoft Ads is **case-sensitive**, so the value must match the goal's Event Action rule exactly. # Common Event Fields These fields are included on every event sent to Microsoft. | Microsoft Field | Chord Source (Priority Order) | Notes | | ---------------- | -------------------------------------------------------- | ------------------------------------------- | | `eventType` | *(derived)* | `pageLoad` or `custom` | | `eventId` | `messageId` + suffix | `-pl` for page load, `-ce` for custom event | | `eventTime` | `timestamp` | Converted to Unix seconds | | `eventSourceUrl` | `page.url` > `context.page.url` > `properties.url` | | | `referrerUrl` | `page.referrer` > `context.page.referrer` | | | `pageTitle` | `page.title` > `context.page.title` > `properties.title` | | # User Data PII fields are SHA256-hashed using Microsoft-specific normalization rules before sending. | Microsoft Field | Chord Source (Priority Order) | Notes | | ----------------- | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- | | `em` (email) | `properties.email` > `context.traits.email` | Microsoft-specific hashing: dots removed from user portion, +aliases stripped, lowercased, SHA256 | | `ph` (phone) | `properties.phone` > `context.traits.phone` | Validated, normalized to E.164 format, SHA256-hashed. Invalid phones are silently dropped | | `externalId` | `userId` | SHA256-hashed (lowercased) | | `anonymousId` | `anonymousId` | **Not hashed** — Microsoft uses as guest UUID | | `clientUserAgent` | `context.userAgent` | Not hashed | | `clientIpAddress` | `context.ip` | Not hashed | | `msclkid` | URL parameter `msclkid` > `properties.msclkid` > `integrations["Microsoft CAPI"].msclkid` | Microsoft click ID for attribution | # Phone Validation Phone numbers are validated before hashing. The following are silently rejected: - Common junk values: `n/a`, `na`, `undefined`, `null`, `none`, `unknown`, `test` - Numbers with fewer than 7 digits - All-repeated-digit numbers (e.g., `1111111`) # Custom Data (Track Events) The `custom` event in each pair includes conversion properties: | Microsoft Field | Chord Source (Priority Order) | Notes | | --------------- | -------------------------------------------------------------- | ---------------------------------------------------------------------------- | | `value` | `properties.revenue` > `properties.total` > `properties.price` | First numeric value found; `Order Completed` has no `properties.value` field | | `currency` | `properties.currency` | | | `transactionId` | `properties.orderId` / `properties.order_id` | For deduplication | | `searchTerm` | `properties.query` > `properties.search_term` | | | `eventCategory` | `properties.category` | | | `eventLabel` | `properties.label` | | | `pageType` | *(from event mapping table)* | E.g., `product`, `cart`, `purchase` | | `items` | See Item Attributes below | | # Item Attributes For **single-product events** (Product Viewed, Product Added), item data is extracted from top-level properties: | Microsoft Field | Chord Source | | --------------- | ------------------------------------------------------------ | | `id` | `properties.sku` > `properties.product_id` > `properties.id` | | `quantity` | `properties.quantity` | | `price` | `properties.price` | | `name` | `properties.name` | For **multi-product events** (Checkout Started, Order Completed, Order Placed), items come from the `properties.products` array: | Microsoft Field | Chord Source | | --------------- | ------------------------------------------------------------ | | `id` | `products[].sku` > `products[].product_id` > `products[].id` | | `quantity` | `products[].quantity` | | `price` | `products[].price` | | `name` | `products[].name` | # Required Fields For purchase events (Order Completed / Order Placed) to be accepted by Microsoft, the following fields must be present: - Event name and event time (populated automatically by Chord CDP) - `properties.currency` - `properties.value`, `properties.revenue`, or `properties.total` (at least one) - `properties.order_id` or `properties.orderId` - At least one user identifier: `properties.email`, `properties.phone`, or `msclkid` (from URL parameter) # Testing and Validation After connecting the destination: 1. Use **Microsoft Ads event diagnostics** (in the UET tags section of your dashboard) to confirm events are being received 2. Verify match rates — higher match rates indicate user identifiers (email, phone, msclkid) are being sent correctly 3. Confirm revenue values and order counts align with your expectations If discrepancies appear: - Confirm `msclkid` is being captured in your page URLs (Microsoft appends this to ad click-through URLs) - Ensure required fields listed above are populated in your events - Check that your access token has not expired — regenerate in the Microsoft Ads dashboard if needed # Property Mappings Use custom property mappings if the default field resolution does not match your data model: | Destination Path | Description | | -------------------------------- | ------------------------------------------------------- | | `properties.email` | Email for enhanced conversions | | `properties.phone` | Phone for enhanced conversions (E.164 format preferred) | | `properties.value` | Primary conversion value | | `properties.revenue` | Fallback conversion value (subtotal) | | `properties.currency` | Currency code (e.g., `USD`) | | `properties.order_id` | Transaction ID for deduplication | | `properties.products[].sku` | Product item IDs | | `properties.products[].price` | Per-item price | | `properties.products[].quantity` | Per-item quantity | | `properties.products[].name` | Product display name | *** **Updated 12 Mar 2026** [title] Contentsquare Heap (Pixel) [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ ## Introduction The **Heap Pixel** destination loads the Heap browser SDK directly in the visitor's browser (device mode) and sends events client-side. Unlike the [server-side Heap destination](#), device-mode events originate from the browser, enabling Heap's automatic interaction capture, session replay, and heatmap features. Use this destination alongside the [server-side Heap destination](#) for maximum coverage. ## Getting Started This is a device-mode destination. The Heap JavaScript SDK is loaded automatically — no manual script installation is required. You will need: - **App ID (Environment ID)** — found in **Account > Manage > Projects** in the Heap dashboard. Each project (environment) has its own App ID. ## Connecting to the Heap Pixel CDP Destination :::hint{type="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 **Heap (Device Mode)** from the destination catalog. 5. Enter the destination name and **App ID**. 6. Click **"Create"** to connect. ## Events ### Event Mapping | Chord Event Type | Heap SDK Method | Notes | | ---------------- | ------------------------------------------------------------ | --------------------------------------------- | | `track` | `heap.track(eventName, properties)` | Event name and properties forwarded as-is | | `page` | `heap.track("Page View", properties)` | Page metadata included in properties | | `identify` | `heap.identify(identity)` + `heap.addUserProperties(traits)` | Identity resolved from `userId` > email trait | ### Track Events Track events call `heap.track()` with the event name and properties. | Heap Argument | Chord Source | Notes | | ------------- | -------------------- | ------------------------------ | | `eventName` | `event` (event name) | | | `properties` | `properties` | All event properties forwarded | ### Page Events Page events call `heap.track("Page View", ...)` with page metadata merged into properties. | Heap Argument | Chord Source | Notes | | ------------- | ------------------------------------- | --------------------------------------------------------------- | | `eventName` | *(hardcoded)* `"Page View"` | | | `properties` | `properties` merged with page context | Includes `url`, `path`, `referrer`, `title` from `context.page` | ### Identify Events Identify events call both `heap.identify()` to set the user identity and `heap.addUserProperties()` to attach traits. | Heap Method | Chord Source (Priority Order) | Notes | | -------------------------------- | -------------------------------------------------- | --------------------------------------------------- | | `heap.identify(identity)` | `userId` > `context.traits.email` > `traits.email` | If no identity can be resolved, the call is skipped | | `heap.addUserProperties(traits)` | `traits` merged with `context.traits` | All user traits forwarded | ## Initialization On first event, the plugin: 1. Injects the Heap SDK stub queue (`window.heap`) into the page 2. Loads the Heap SDK script from `https://cdn.heapanalytics.com/js/heap-0.js` 3. Calls `heap.load(appId)` to initialize Heap with your App ID The plugin tracks SDK loading state (`fresh` → `loading` → `loaded` / `failed`) using a shared state flag (`window.__chordCDPHeapState`) to prevent duplicate script loads across concurrent events. Events that arrive while the SDK is loading are queued and processed after initialization completes. If the SDK 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://cdn.heapanalytics.com` | | `connect-src` | `https://cdn.heapanalytics.com` `https://heapanalytics.com` | | `img-src` | `https://heapanalytics.com` | ## Combining with Server-Side Heap Running both the Heap Pixel (device mode) and the [server-side Heap destination](#) provides redundancy: - **Device mode** captures browser-native interactions and enables session replay / heatmaps - **Server-side** captures events that may be blocked by ad blockers or occur outside the browser Heap deduplicates events that share the same identity and timestamp, so duplicate counting is generally not a concern when running both in parallel. [title] MNTN Tracking Pixel (Web Pixel) [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ ## Introduction **MNTN Tracking Pixel** is MNTN's site-wide audience building and attribution pixel for Connected TV (CTV) advertising. This destination fires a JavaScript pixel on every page view, enabling MNTN to build audiences and attribute site visits to CTV ad exposure. There is no server-side component. For conversion tracking (purchases, sign-ups, leads), use this destination alongside the [MNTN Conversion Pixel](#). ## Getting Started This is a device-mode destination. The pixel fires by dynamically inserting a ` ``` ## 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] The Trade Desk [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ **The Trade Desk** is a programmatic advertising platform for display, video, audio, and connected TV campaigns. This destination loads The Trade Desk Universal Pixel JavaScript SDK in the browser and forwards page views, e-commerce events, and conversion data for measurement and audience targeting. There is no server-side component. # Getting Started This is a device-mode destination. The Trade Desk Universal Pixel SDK is loaded automatically — no manual script installation is required. You will need: - **Advertiser ID** — your Trade Desk advertiser ID, found in your Trade Desk account. - **Universal Pixel ID** — your Trade Desk Universal Pixel ID, found in your Trade Desk account under **Pixels**. All page views and conversion events fire against this single pixel. TTD classifies conversion events based on URL patterns and dynamic parameters (such as `order_id` and `revenue`). # Connecting to the Trade Desk 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 **The Trade Desk Pixel** from the destination catalog. 5. Enter the destination name, **Advertiser ID**, and **Universal Pixel ID**. 6. Click **"Create"** to connect. # Events # Event Mapping All events include the TTD `event_name` field, mapped from the CDP event name to a [TTD predefined event name](https://partner.thetradedesk.com/v3/portal/data/doc/TrackingTagsEvents#predefined-item-events). Every forwarded event also includes a `pixelIds` array scoped to the Universal Pixel ID. | Chord Event | TTD `event_name` | Revenue Data | Item Data | Notes | | --------------------------- | -------------------- | ------------ | --------- | -------------------------- | | `page` | `sitevisit` | | | | | `Order Completed` | `purchase` | Yes | Yes | | | `Checkout Started` | `startcheckout` | Yes | Yes | | | `Product Added` | `addtocart` | | Yes | | | `Product Viewed` | `viewitem` | | Yes | | | `Cart Viewed` | `viewcart` | | Yes | | | `Product Added to Wishlist` | `addtowishlist` | | Yes | | | `Products Searched` | `searchitem` | | | Search query sent as `td1` | | `identify` | *(not forwarded)* | | | | | *(other track events)* | *(silently skipped)* | | | | All events fire against the Universal Pixel ID. TTD infers the conversion type based on URL patterns and dynamic parameters included with each event. # Page Events Fires a conversion event with `event_name: "sitevisit"`, scoped to the Universal Pixel ID. **TTD SDK call:** `ttdConversionEvents("event", { event_name: "sitevisit", pixelIds: [""] })` # Revenue Data For `purchase` and `startcheckout` events, order-level revenue data is included: | TTD Attribute | Chord Source (Priority Order) | Notes | | ------------- | ----------------------------------------- | ---------------------- | | `order_id` | `properties.order_id` | Omitted if not present | | `value` | `properties.total` > `properties.revenue` | Omitted if not present | | `currency` | `properties.currency` | Omitted if not present | # Item Data For events with product information, an `items` array is sent with item-level detail. Multi-product events (`Order Completed`, `Cart Viewed`, `Checkout Started`) map from `properties.products[]`. Single-product events (`Product Added`, `Product Viewed`, `Product Added to Wishlist`) extract from the event properties directly. | TTD Item Attribute | Chord Source | Notes | | ------------------ | --------------------------- | ----------------------------------------------------- | | `item_code` | `product_id` / `sku` / `id` | Required; products without an identifier are excluded | | `name` | `name` | Defaults to empty string | | `qty` | `quantity` | Defaults to `1` | | `price` | `price` | Defaults to `0` | | `cat` | `category` | Defaults to empty string | # Products Searched Fires an event with `event_name: "searchitem"`. If `properties.query` is present, it is included as the `td1` dynamic parameter. # Unmapped Events Track events not listed above are silently skipped. Identify events are not forwarded. # Initialization The plugin loads `https://js.adsrvr.org/up_loader.3.0.0.js` and calls `ttdConversionEvents("init", { advertiserId, pixelIds: [""] })`. Before the script loads, a queue (`ttdConversionEventsLayer`) buffers any events. The plugin manages SDK loading state (`fresh` → `loading` → `loaded`/`failed`) to prevent duplicate script loads. Concurrent events during loading are queued and processed after initialization completes. 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://js.adsrvr.org` | | `connect-src` | `https://js.adsrvr.org` | *** **Updated 5 May 2026** [title] Chord Data Ingestor App [path] Chord Event Tracking/Getting started/Shopify/Shopify installation/ # Creating Custom Shopify Apps on behalf of Chord ## Step 1: Create the App 1. Go to your **Shopify Dev Dashboard** ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/UBqX2VPeJ5Z3PspeluUt0_image.png" size="100" isUploading="false" width="1733" height="843" darkWidth="1733" darkHeight="843" showCaption="false" indent="1"} 2. In the navigation menu, click **Apps** → **Create app** 3. Under **Start from Dev Dashboard**, enter the app name `Chord Data Ingestor` ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/N2wa1hloX4iBZemk_B6Vw_image.png" size="100" isUploading="false" width="3834" height="1918" darkWidth="3834" darkHeight="1918" showCaption="false" indent="1"} 4. Click **Create** ## Step 2: Configure Access Scopes 1. Leave the form settings as-is 2. In the **API Access** section, paste the following scopes: :::BlockQuote{indent="1"} read\_all\_orders,read\_reports,read\_assigned\_fulfillment\_orders,read\_customers,read\_discounts,read\_fulfillments,read\_inventory,read\_locations,read\_merchant\_managed\_fulfillment\_orders,read\_orders,read\_product\_feeds,read\_product\_listings,read\_products,read\_returns,read\_shipping,read\_third\_party\_fulfillment\_orders ::: 3. Click **Release** ## Step 3: Install the App 1. On the app **Home** page, click **Install app** ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/b67mutDG3fVg7eQMu7RSq_image.png" size="100" isUploading="false" width="1638" height="811" darkWidth="1638" darkHeight="811" showCaption="false" indent="1"} 2. Select your store 3. Review the application scopes 4. Click **Install** ## Step 4: Store your client credentials in Hub data sources You can find the client credentials by visiting the app **Settings** page. You will need both the “Client ID” and “Secret”. ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/1GTjZ7kLoJB22RoodwGcI_image.png) You will also need your store URL in the following format: your-store-url.myshopify.com. You can find your-store-url by visiting the store Admin page. The Admin landing page URL will look similar to the following: :::BlockQuote https\://admin.shopify.com/store/\{\{your-store-url}}/orders ::: The portion of the URL after store, is your store name that you will want to provide. Now with the requisite information, navigate to the Hub data sources page. Click “Add New Source”, select “Shopify” and complete the form with the client ID, secret and URL. ![]() [title] Subscription Auto-Renewed [path] Chord Event Tracking/Server Events/Track/ This event is triggered when a customer subscription auto-renews. # 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 Auto-Renewed", "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 Auto-renewed", "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] Subscription Order Skipped [path] Chord Event Tracking/Server Events/Track/ This event is triggered when a customer skips their upcoming installment. # 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 Order Skipped", "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 Order Skipped", "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] Subscription Paused [path] Chord Event Tracking/Server Events/Track/ This event is triggered when a subscription is paused. # 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 Paused", "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 Paused", "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] Shipment Delivered [path] Chord Event Tracking/Server Events/Track/ This event is triggered when an order shipment was delivered to the customer. # Properties | **Name** | **Type** | **Description** | **Required** | | -------------- | -------- | ------------------------------------------------- | ------------ | | `currency` | `string` | ISO currency code of the transaction (e.g. `USD`) | Yes | | `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_number` | `string` | Order ID or number | Yes | | `shipment` | `object` | Products in the order | Yes | ## Shipment | **Name** | **Type** | **Description** | **Required** | | ----------------------- | ---------- | ------------------------------------------------------------------------------------------ | ------------ | | `tracking` | `string` | Tracking code of the shipment | No | | `carrier` | `string` | Name of the carrier fulfilling the shipment | No | | `number` | `string` | Shipment ID/number | Yes | | `cost` | `number` | Shipment cost | No | | `adjustment_total` | `number` | Total of all adjustments/discounts of the shipment | No | | `additional_tax_total` | `number` | | No | | `promo_total` | `number` | Total of all promotions of the shipment | No | | `included_tax_total` | `number` | | No | | `pushed` | `string` | Indicates if the shipment record has been sent to the warehouse/fulfillment centre/carrier | No | | `fulfilled_by` | `string` | ISO date when the shipment was fulfilled/pushed | No | | `tracking_detail` | `string` | Additional tracking information | No | | `external_tracking_url` | `string` | URL for customer to tracking shipping status | No | | `label_url` | `string` | URL of electronically generated label | No | | `products` | `object[]` | Products/inventory in the shipment | No | | `address` | `object` | 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 | ## 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` | `string` | Customer name | No | | `state_name` | `string` | ISO state code for the shipping address | No | | `zipcode` | `string` | Zip or postal code for the shipping address | No | # Sample Payload ```json { "type": "track", "event": "Shipment Delivered", "properties": { "currency": "USD", "email": "test@example.com", "order_number": "O1234567890", "first_name": "John", "last_name": "Doe", "shipment": { "tracking": "T1234567890", "carrier": "UPS", "number": "H1234567890", "cost": 9.99, "state": "ready", "adjustment_total": 9.99, "additional_tax_total": 9.99, "promo_total": 9.99, "included_tax_total": 9.99, "pushed": "true", "fulfilled_by": "2026-01-01T00:00:00.000Z", "tracking_detail": null, "external_tracking_url": null, "label_url": null, "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" } ], "address": { "name": "John Doe", "address1": "123 Fake St", "address2": null, "city": "Oak Lawn", "zipcode": "60532", "phone": "1234567890", "state_name": "IL", "company": null } } } } ``` # 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": "Shipment Delivered", "properties": { "currency": "USD", "email": "test@example.com", "order_number": "O1234567890", "first_name": "John", "last_name": "Doe", "shipment": { "tracking": "T1234567890", "carrier": "UPS", "number": "H1234567890", "cost": 9.99, "state": "ready", "adjustment_total": 9.99, "additional_tax_total": 9.99, "promo_total": 9.99, "included_tax_total": 9.99, "pushed": "true", "fulfilled_by": "2026-01-01T00:00:00.000Z", "tracking_detail": null, "external_tracking_url": null, "label_url": null, "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" } ], "address": { "name": "John Doe", "address1": "123 Fake St", "address2": null, "city": "Oak Lawn", "zipcode": "60532", "phone": "1234567890", "state_name": "IL", "company": null } } } } ' ``` [title] Server Events Overview [path] Chord Event Tracking/Server Events/ In addition to client events, customers may send server events to Chord. These events will be processed by the Chord CDP and forwarded onto connected destinations, just like client events. Server events provide an HTTP endpoint for backend systems to send ad-hoc events or webhooks. The examples below show the data required for each event to be correctly processed by Chord. :::hint{type="info"} Customers using Shopify or Chord OMS have their server events automatically routed to Chord CDP. These documents are for customers using a non-Shopify/non-Chord OMS or want to customize the data sent to Chord. ::: # Endpoint The URL to send server events to depends on the type of event being sent: - Track: `https://production.cdp.ingest.chord.co/api/track` - Identify: `https://production.cdp.ingest.chord.co/api/identify` # Authorization Requests sent to Chord use an API key for authorization. There are multiple options for providing the API key in the request - customers may choose the version that is most compatible with their source system. Chord recommends that, where possible, customers use 1. HTTP header `X-Write-Key` 2. `writekey` query parameter (note all characters are lowercase). 3. `writeKey` property in the request body (note the uppercase `K`). Chord recommends customers use the `X-Write-Key` header for authorization where possible. # Automatic Properties When an event is ingested, the properties below are added automatically to the payload. There is no need for customers to include these values, however they can be overridden by equivalent properties in the request payload if required. ```json { ..., "timestamp": "2024-01-01T00:00:00.000Z", "requestIp": "2604:3d09:1180:1581:3c4a:bc9d:8027:a450", "context": {...}, "receivedAt": "2025-09-12T19:04:50.541Z", "messageId": "0c43c13c-692b-46c6-9152-3962871b1009" } ``` # Event Types - [Track](docId\:z57EPqMJDr7cJ3wQ1JxDO) - [Identify](docId\:tMw87hJF-N6g5lJLK1eKv) [title] Web Pixel [path] Chord Event Tracking/Using with Shopify/ Chord's tracking can be easily installed on Shopify stores using a Shopify custom web pixel. A Shopify custom web pixel is a JavaScript code snippet that runs on Shopify themes and on Shopify checkouts. Pixels are managed through the **Customer events** page in Shopify. Chord's web pixel includes: - Pre-checkout tracking from the Shopify theme storefront (e.g., "Product Viewed" track events, page views) - Checkout tracking from Shopify checkout (e.g., "Payment Info Entered" track events, page views) Chord's web pixel can only add pre-checkout tracking to your storefront if your storefront uses a Shopify theme. If your storefront is headless: 1. add pre-checkout tracking using the [analytics SDK npm package](docId\:XDo-mGzIP_SQ_feVf6RUI) instead. 2. continue to use the web pixel for checkout tracking. Keep reading to for an in-depth guide to adding the Chord web pixel to your Shopify store: - [Installation](docId\:zuG-19SU0RUfAEs0k_0Ix) - [Configuration](docId\:qMM8Kz1WShyJhs9qbh0vm) - [Usage](docId\:gvuGCbQHfkHEUhE58wpKe) - [Consent Management](docId\:dbKzUyYJsHKX7dzHiSfeZ) [title] Enabling Subscription Events [path] Chord Event Tracking/Using with Shopify/Server Event Tracking/ Chord typically sends tracking events to the CDP from two sources via your storefront: - Your **website front-end source**, either using the Chord Shopify web pixel or `@chordcommerce/analytics`, and - Chord's **server events service source**, which sends tracking events from a Shopify custom source function in your CDP workspace in response to webhook triggers from Shopify. When Chord provisions your CDP workspace, it will include Chord's Shopify webhook source. This code listens for webhook events from Shopify and transforms them into CDP events. # Subscription Webhook Topics Shopify makes availalbe *subscription-specific* webhook topics that can be emitted via your store to the Chord CDP (much like order & checkout creation), however **Shopify limits **`subscription contracts`** events to the app that created the contract (i.e. Shopify Subscriptions, Recharge).** :::hint{type="warning"} **Shopify limits Subscription Contracts events to the app that created the contract (i.e. Shopify Subscriptions, Recharge).** ::: As a result, the ***Chord webhook event app*** installed within your Shopify store will be unable to listen for subscription-specific webhook events; given this, a workaround to faciliate ingestion of these events is possible through the use of ***Shopify Flow***. The following *subscription *webhook topics are supported through this implementation: - `subscription_contracts/create`**: **sends Chord's `Subscription Created` event - `subscription_contracts/cancel`**: **sends Chord's `Subscription Canceled` event - `subscripton_contracts/pause`**: **sends Chord's `Subscription Paused` event - `subscripton_contracts/expire`**: **sends Chord's `Subscription Expired` event - `subscription_billing_attempts/failure`: sends Chord's `Subscription Payment Failed` event # Shopify Flow [Shopify Flow](https://apps.shopify.com/flow) is your automation and integration platform for ecommerce. Flow makes it easy to build custom workflows to automate marketing, order fulfillment, inventory management, fraud prevention, and more. Boost productivity and reclaim your time by automating tasks, streamlining business processes, customizing how your store works, or connecting to your favorite apps and external services. - Automate with hundreds of workflow templates for ecommerce tasks. - Add custom logic and unlimited actions to any automation. - Integrate with tags, metafields, B2B, Slack, Google Sheets, and more. ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/HxKGnNUVvktvQO9dt5_Ck_image.png) :::hint{type="info"} The ***Shopify Flow app*** can be used to create workflows that listen for/ingest Subscription-specific webhook events and sends them through to your Chord CDP backend source. ::: ## Assumptions Before installing the Shopify Flow App and creation of the subscription-specific webhook events, confirm with your Chord implementation team that the corresponding[ back-end webhook eventing app](https://docs.chord.co/server-event-tracking#creating-an-admin-api-key) has been installed on your Shopify store. **The following steps are assumed:** - Chord already has access to your Shopify store; - You have access to the Chord CDP; - Shopify Flow app is either already in-use or is installed; and - The subscription events to be configured are: - `Subscription Created` - `Subscription Cancelled` - `Subscription Paused` - `Subscription Expired` - `Subscription Payment Failed` ## Installation As a free app, you should be able to easily install* Shopify Flow* within your Shopify store. It is possible that your Chord implementation team has already installed the app and if so, will have already installed the flows below. If there are any questions on whether the app is present or if these flows have already been set-up, please reach out to [help@chord.co](mailto\:help@chord.co)***.*** ### Importing Flows Click `Import Flow`and import the provided ***.flow*** files below: ::Image[]{src="https://api.archbee.com/api/optimize/TmutqdeXiIw-V3gBZXVjd/6QkTXuCVCER9C6e-KkZ2y_image.png" size="80" width="1422" height="811" position="center" darkWidth="1422" darkHeight="811" showCaption="false"} ::Image[]{src="https://api.archbee.com/api/optimize/TmutqdeXiIw-V3gBZXVjd/-OEWGi--9ofn5wVQHTC1k_image.png" size="80" width="3326" height="1908" position="center" darkWidth="3326" darkHeight="1908" showCaption="false"} ### .flow Files Take these .flow files and ipmort them into your Shopify Flow app import modal: ::File{src="https://archbee-doc-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/5y7G4qZsJN9ZdROhB0Z04_chord-subscription-contract-created.flow" label="[CHORD] - Subscription Contract Created.flow" isUploading="false"} ::File{src="https://archbee-doc-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/yGLJXe9CVt4o1hXUayzka_chord-subscription-updated-cancelled-expired-paused.flow" label="[CHORD] - Subscription Updated (Cancelled __ Expired __ Paused).flow" isUploading="false"} ::File{src="https://archbee-doc-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/mUHVzuGKRt8aYNiLFWt-X_chord-subscription-payment-failed.flow" label="[CHORD] - Subscription Payment Failed.flow" isUploading="false"} **Validate & Review** - Verify the configuration in Shopify: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/L2899i4aO8gZMxQol5edq_image.png" size="100" isUploading="false" width="2808" height="1758" darkWidth="2808" darkHeight="1758" showCaption="false" indent="1"} - Verify the successful delivery of events in Chord CDP from your configured Back-End Source: ::Image[]{src="https://api.archbee.com/api/optimize/TmutqdeXiIw-V3gBZXVjd/hTPOVXSXnrn61SBlMSjGa_image.png" size="80" width="1433" height="813" position="center" darkWidth="1433" darkHeight="813" showCaption="false"} ::Image[]{src="https://api.archbee.com/api/optimize/TmutqdeXiIw-V3gBZXVjd/TyECDCV4qTEPLCwR4eZEl_image.png" size="80" width="3326" height="1918" position="center" darkWidth="3326" darkHeight="1918" showCaption="false"} :::hint{type="danger"} If you are experiencing any issues with configuring webhooks in Shopify or do not see Subscription events in your CDP back-end source, please reach out to [help@chord.co](mailto\:help@chord.co) with any questions/concerns. ::: [title] Formatters [path] Chord Event Tracking/Getting started/ Formatters are Javascript functions that are used to construct tracking event data. There are two types of formatters, `objects` and `events`. You must define `object` formatters. `event` formatters are optional. ## Object formatters When you look at Chord's tracking events, you'll see some event properties are used over and over. Names and values of event properties are expected to be consistent between events. In other words, different events have different properties, but a given property name should have the same value wherever it's used. For example, the two events `Product Added` and `Product Clicked` share most of the same event properties. `product_id` is a property of both events, and the value of `product_id` is expected to be the same for both events. It should not be a product SKU for one event and a database identifier for another event. Chord ensures consistency in property names and values by creating a standard set of object models that are used over and over throughout events. There are four: `cart`, `checkout`, `lineItem`, and `product`. When you install Chord's analytics library, you write a formatter function for each of these four types. Your formatter function will receive as an argument the input from the event tracking function, and your formatter must return an object in the format that Chord expects. Then Chord uses this formatter to generate the correct event payload. ### Available object formatters | Method | Type | Description | | -------- | -------------------------------------- | ---------------------------------- | | cart | (props: `CartInput`) => `Cart` | Returns a Chord `Cart` object. | | checkout | (props: `CheckoutInput`) => `Checkout` | Returns a Chord `Checkout` object. | | lineItem | (props: `LineItemInput`) => `LineItem` | Returns a Chord `LineItem` object. | | product | (props: `ProductInput`) => `Product` | Returns a Chord `Product` object. | ### Example object formatter Let's walk through an example of a `cart` formatter. In your website code, you might want to send a `Cart Viewed` tracking event. The code used to send `Cart Viewed` looks like this: ```typescript var cart = await getCartFromShopifyStorefrontApi() // the `cart` object here can be any type chord.trackCartViewed({ cart }) ``` But how does Chord create a standard `Cart Viewed` event when you can pass any arbitrary cart object as the value? You'll define a formatter that converts your `cart` object into a format that Chord understands. See the `Cart` Typescript type exported by `@chordcommerce/analytics` to see what the return type of the cart formatter should be. Here's an example of a cart formatter that converts a [Shopify Storefront API cart response](https://shopify.dev/docs/api/storefront/2023-10/objects/Cart) into Chord's `Cart` object: ```typescript import { CartInput, Cart, ChordAnalytics } from '@chordcommerce/analytics' const cartFormatter: (props: CartInput) => Cart = ({ cart }) => { const products = cart?.lines?.map((line, i) => { const lineItem = line?.node return { ...lineItemFormatter({ lineItem }), // your `lineItem` formatter position: i + 1, } }) return { cart_id: cart?.id?.replace('gid://shopify/Cart/', ''), currency: 'USD', products, value: Number(cart?.cost?.subtotalAmount?.amount) || 0, } } // When creating an instance of `ChordAnalytics`, set `formatters.objects.cart` to `cartFormatter` const chord = new ChordAnalytics({ ... formatters: { objects: { cart: cartFormatter, ... }, } }) ``` ## Event formatters Event formatters are optional. You can supply an event formatter for any event-specific tracking method of `ChordAnalytics`; for example, for `chord.trackProductAdded`, you can set an event formatter with the key `productAdded`. Chord's library will call your event formatter after constructing the tracking event but before sending to the CDP. This is the easiest way to customize a Chord tracking event, if you're not able to get the effect you want with object formatters. A common use case is to add additional properties to a specific tracking event. ### Available event formatters All event formatters are optional. Event formatters have two arguments: `props`, which is the argument passed to the related tracking function (for example, `chord.trackProductClicked(props))`, and `event`, which is the finished event payload Chord has constructed to send to the CDP. | Method | Type | Description | | --------------------- | -------------------------------------------------------------------------------------- | -------------------------------------------------------- | | `cartViewed` | `(props: CartViewedInput, event: CartViewed) => CartViewed` | Event triggered when a cart is viewed. | | `checkoutStarted` | `(props: CheckoutStartedInput, event: CheckoutStarted) => CheckoutStarted` | Event triggered when the checkout process starts. | | `couponApplied` | `(props: CouponAppliedInput, event: CouponApplied) => CouponApplied` | Event triggered when a coupon is successfully applied. | | `couponDenied` | `(props: CouponDeniedInput, event: CouponDenied) => CouponDenied` | Event triggered when a coupon is denied. | | `couponEntered` | `(props: CouponEnteredInput, event: CouponEntered) => CouponEntered` | Event triggered when a coupon code is entered. | | `couponRemoved` | `(props: CouponRemovedInput, event: CouponRemoved) => CouponRemoved` | Event triggered when a coupon is removed. | | `emailCaptured` | `(props: EmailCapturedInput, event: EmailCaptured) => EmailCaptured` | Event triggered when an email is captured. | | `productAdded` | `(props: ProductAddedInput, event: ProductAdded) => ProductAdded` | Event triggered when a product is added to the cart. | | `productClicked` | `(props: ProductClickedInput, event: ProductClicked) => ProductClicked` | Event triggered when a product is clicked. | | `productListFiltered` | `(props: ProductListFilteredInput, event: ProductListFiltered) => ProductListFiltered` | Event triggered when a product list is filtered. | | `productListViewed` | `(props: ProductListViewedInput, event: ProductListViewed) => ProductListViewed` | Event triggered when a product list is viewed. | | `productRemoved` | `(props: ProductRemovedInput, event: ProductRemoved) => ProductRemoved` | Event triggered when a product is removed from the cart. | | `productViewed` | `(props: ProductViewedInput, event: ProductViewed) => ProductViewed` | Event triggered when a product is viewed. | | `productsSearched` | `(props: ProductsSearchedInput, event: ProductsSearched) => ProductsSearched` | Event triggered when products are searched. | | `signedIn` | `(props: SignedInInput, event: SignedIn) => SignedIn` | Event triggered when a user signs in. | | `signedOut` | `(props: SignedOutInput, event: SignedOut) => SignedOut` | Event triggered when a user signs out. | | `signedUp` | `(props: SignedUpInput, event: SignedUp) => SignedUp` | Event triggered when a user signs up. | ### Example event formatter In this example, let's add an additional property to the "Signed In" event to track whether the user signed in by clicking the yellow button or the purple button. The code used to send "Signed In" looks like this: ```typescript chord.trackSignedIn({ email: 'hello@chord.co', button: 'purple' }) ``` As written, Chord will ignore the `button` property and not include it in the event sent to the CDP, because it's not part of Chord's tracking plan. To include the `button` property in the event, add an event formatter: ```typescript import { CartInput, Cart, ChordAnalytics } from '@chordcommerce/analytics' const signedInFormatter: (props: SignedInInput, event: SignedIn) => SignedIn = (props, event) => { return { ...event, button: props.button } } const chord = new ChordAnalytics({ ... formatters: { events: { signedIn: signedInFormatter, ... }, } }) ``` # [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] Webhook Event Payloads [path] Chord Event Tracking/Using with Shopify/Server Event Tracking/ Chord's server events service subscribes to Shopify webhook topics and transforms each one into a CDP event. This page documents which topics produce which events, and the properties Chord adds that aren't present in the raw Shopify payload. For the core property tables shared across all sources — client, Shopify, and Chord OMS — see the individual pages under [Server Events > Track](docId\:z57EPqMJDr7cJ3wQ1JxDO). # Supported webhook topics | Shopify webhook topic | Chord event | Customer properties | | ------------------------------- | ---------------------- | ------------------- | | `orders/create` | Order Completed | Yes | | `orders/cancelled` | Order Cancelled | Yes | | `orders/fulfilled` | Order Fulfilled | Yes | | `checkouts/create` | Checkout Started | Yes | | `refunds/create` | Order Refunded | Yes | | `subscription_contracts/create` | Subscription Created | Yes | | `subscription_contracts/cancel` | Subscription Cancelled | Yes | | `subscription_contracts/pause` | Subscription Paused | Yes | | `fulfillments/create` | Fulfillment Created | No | | `fulfillments/update` | Fulfillment Updated | No | | `orders/delete` | Order Deleted | No | | `customers/delete` | Customer Deleted | No | | `customers/merge` | Customer Merged | No | | `locations/delete` | Location Deleted | No | | `products/delete` | Product Deleted | No | :::hint{type="info"} Subscription contract topics are limited by Shopify to the app that created the contract. See [Enabling Subscription Events](docId\:F9xrfOppDl8EFLEBeDuXg) for details. ::: # Customer properties Shopify removed lifetime customer statistics such as `orders_count` from webhook payloads in the 2025-01 API version, and no webhook payload carries them today. Chord looks the customer up through the Shopify Admin API and adds the following properties to every event that carries a customer ID. | Name | Type | Description | | ------------------------------------ | ---------- | -------------------------------------------------------------- | | `repeat` | `boolean` | Whether the customer had ordered before this event | | `is_new_customer` | `number` | The same signal as `repeat`, inverted, as `0` or `1` | | `customer_order_count` | `number` | Lifetime order count as Shopify reports it | | `customer_lifetime_revenue` | `number` | Total the customer has spent across their lifetime | | `customer_lifetime_revenue_currency` | `string` | ISO currency code for `customer_lifetime_revenue` | | `customer_since` | `string` | Date and time the customer record was created in Shopify | | `customer_tags` | `string[]` | Tags applied to the customer in Shopify | | `customer_subscriber_status` | `string` | Product subscriber status, e.g. `ACTIVE` or `NEVER_SUBSCRIBED` | Both `repeat` and `is_new_customer` describe the same thing in two shapes, so destinations can read whichever convention they already expect without a migration. ## New versus returning `repeat` and `is_new_customer` answer a single question: *had this customer ordered before the event being reported?* Shopify counts an order against the customer as soon as it is created, so an order-scoped webhook reports a `customer_order_count` that already includes the order in the event. A first-time buyer's `orders/create` therefore arrives with `customer_order_count: 1`, and Chord excludes that order before deciding the flags: ```json { "repeat": false, "is_new_customer": 1, "customer_order_count": 1 } ``` A returning customer placing their third order arrives as: ```json { "repeat": true, "is_new_customer": 0, "customer_order_count": 3 } ``` On Checkout Started and the subscription events there is no order in the event, so no adjustment is made and the flags describe the customer's order history as it stands. `customer_order_count` is always the raw figure Shopify returned, never adjusted. ## Requirements The Admin API access token must include the `read_customers` scope in addition to `read_orders`. Without it, Shopify rejects the customer lookup and events are delivered without these properties. :::hint{type="warning"} Customer properties are added on a best-effort basis. If the lookup fails for any reason — a missing scope, an expired access token, a Shopify outage — Chord delivers the event without them rather than dropping or delaying it. If these properties are missing from your events, check the access token and its scopes first. ::: ## Timing These values are read from Shopify at the moment the event is processed, rather than being carried in the webhook payload. If an event is retried after a delivery failure, it is enriched with the customer's state at retry time. In practice this only differs from the original attempt if the customer's order history changed in between. # Verifying Shopify's webhook testing doesn't send a payload that matches a real webhook, so complete a test transaction in your store to confirm events are flowing. You can view the delivered events in the **Debugger** tab of the Shopify webhook source in your CDP workspace. [title] CDP Consent Categories (Consent Management Category Mapping) [path] Chord CDP/ :::hint{type="warning"} **Map every destination to a consent category.** Chord applies consent filtering only to destinations that have at least one consent category. A destination with no consent category receives all events, including from visitors who declined consent. After adding a CDP destination, assign its consent categories before turning it on. ::: :::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 ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-h-9wJNvVvd-oBP2kyrAMG-20250911-211642.png) 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 ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-dU_tUBpesYg4AtO-nFmQH-20250911-211454.png) 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] CDP Live Events [path] Chord CDP/ The CDP Live Events view provides real-time visibility into all events captured by Chord CDP, filterable by source. Use this view to monitor data collection, debug integration issues, and verify that events are being tracked correctly. # Overview Incoming events are the raw data signals collected by [CDP Sources](docId\:Ho4HIWVPV4IbGWwn67IAh). These include page views, track events and identify events. Each event is captured, processed, and then routed to your [CDP Destinations](docId:8Q9LBD5xxsaBWfr5xsA1Y). ## Viewing Events The events table displays the following information for each captured event: - **Date (UTC):** The timestamp when the event was received by Chord CDP - **Type:** The event type (e.g., page, track, identify) - **Page Path:** The URL path on your site where the event originated - **Summary:** Quick reference chips showing key event context ## Filtering Events :::hint{type="info"} The **Live Events** graph is designed as a **real-time debugging tool **showing the past 12 hours of data with fast, responsive search. For historical event analysis, we recommend querying your data warehouse (eg. Snowflake) or destination systems, which are optimized for that purpose without impacting real-time event processing ::: Use the toolbar to filter and search your events: - **Sites**: Select which source to view events from (if you have multiple sites configured) - **Status**: Filter by "All" events or only "Errors" to quickly find issues - **Search**: Search within event data (searches events from the past 12 hours) - **Refresh**: Reload the event list to see the latest data ## Event Details Click any row to open the event details drawer, which shows: **Core Information** - **Date (UTC)**: When the event was received - **Source**: Origin of the event (browser for client-side, s2s for server-to-server) - **Message ID**: Unique identifier for this event - **Type** - **Event Name** **User Information** - User ID / Anonymous ID - Email **Page Context** - Page Title - Page URL **Routing Information** - **Destinations**: Which [CDP Destinations](docId:8Q9LBD5xxsaBWfr5xsA1Y) will receieve this event - **Chord CDP Domain**: The CDP domain that processed the event - **Write Key**: The API key used for this event stream **Technical Details** - **HTTP Headers**: Request headers sent with the event - **Event Payload**: The complete raw event data in JSON format ## Common Use Cases **Debugging Integration Issues** Filter by "Errors" status to quickly find events that failed processing. The error message will help identify configuration problems. **Verifying Event Tracking** After implementation, use this view to confirm events are being captured with the correct properties. **Monitoring Data Flow** Verify that events are being routed to the expected destinations. [title] OpenAI Ads (Pixel) [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ **OpenAI Ads Pixel** is OpenAI's browser measurement pixel for ChatGPT Ads. This destination loads the OpenAI measurement SDK (`oaiq`) in the browser and forwards ecommerce and engagement events to OpenAI Ads. Pair it with the **OpenAI Ads Conversions API** destination. The two are complementary rather than redundant, and the pixel does one thing the server-side API cannot: it captures and persists OpenAI's `oppref` click identifier, which is what links a conversion back to the ad that produced it. # Getting Started This is a device-mode destination. The OpenAI SDK is loaded automatically — no manual script installation is required. You will need: - **Pixel ID** — created in **OpenAI Ads Manager** under **Tools > Conversions**. Use the same value in the OpenAI Ads Conversions API destination, so OpenAI can deduplicate a conversion reported by both. This destination needs no key of its own. The **Conversion Key** shown alongside the Pixel ID is only for the server-side Conversions API destination, and the key under **Settings** is a third credential that Chord never uses. Optionally: - **Enable Advanced Matching** — sends the visitor's email, phone, customer ID and name to OpenAI as SHA-256 hashes to raise the match rate. Nothing is sent in plaintext. - **Custom Event Mapping** — routes a Chord event that OpenAI has no standard equivalent for onto a custom event you have registered in Ads Manager. - **Debug Logging** — turns on the OpenAI SDK's own browser console logging. Useful while verifying an installation; leave off in production. :::BlockQuote **Important:** If you are also using the **OpenAI Ads Conversions API** destination, both must be configured with the **same Pixel ID** and the **same Custom Event Mapping**. OpenAI deduplicates on the combination of pixel ID, event name and event ID — with a different pixel ID, one purchase is counted twice. ::: # Connecting to the OpenAI Ads 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 **OpenAI Ads Pixel** from the destination catalog. 5. Enter the destination name and your **Pixel ID**. 6. Optionally enable **Advanced Matching** and configure **Custom Event Mapping**. 7. Click **"Create"** to connect. # Deduplication Every event carries `event_id`, set to the Chord `messageId`. OpenAI deduplicates on the combination of **pixel ID**, **event name** and **event ID**, keeping the first event it receives for a matching key and ignoring later duplicates. The Conversions API destination sends the same `messageId` as its event ID, so a conversion reported by both the browser and your server is recorded once. This also protects you if you are sending your own events to OpenAI alongside Chord: reuse the Chord `messageId` as your `event_id` and OpenAI will merge them rather than double-counting. # Event Mapping OpenAI accepts a fixed set of event names. A Chord event with no equivalent is skipped and logged — it is not forwarded under a made-up name, because OpenAI silently discards an unregistered event name, which is indistinguishable from a successful send. | Chord Event | OpenAI Event | `data.type` | | ---------------------- | ------------------------ | ----------------- | | `page` | `page_viewed` | `contents` | | `Product Viewed` | `contents_viewed` | `contents` | | `Product Added` | `items_added` | `contents` | | `Checkout Started` | `checkout_started` | `contents` | | `Order Completed` | `order_created` | `contents` | | `Signed Up` | `registration_completed` | `customer_action` | | `Email Captured` | `lead_created` | `customer_action` | | `Subscription Created` | `subscription_created` | `plan_enrollment` | To forward anything else, first create a custom event in ChatGPT Ads Manager, then add a **Custom Event Mapping** entry pointing your Chord event name at it. Names are lowercased and spaces become dashes, so `Wishlist Added` becomes `wishlist-added`; the result must be 1–64 characters of lowercase letters, numbers, underscores or dashes. # Event Attributes Every event sends an `eventData` object whose `type` matches the table above. | OpenAI Attribute | Chord Source (Priority Order) | Notes | | ---------------- | -------------------------------------------------------------- | ------------------------------------------------------------ | | `type` | — | Set from the event mapping table. Required by OpenAI | | `amount` | `properties.total` → `properties.revenue` → `properties.value` | **Minor currency units.** See below | | `currency` | `properties.currency` | Defaults to `USD`. Required whenever `amount` is present | | `contents` | `properties.products[]` | Omitted for `customer_action` events, which do not accept it | | `plan_id` | `properties.subscription_id` → `properties.plan_id` | `subscription_created` only | Each entry in `contents` is built from a product: | OpenAI Attribute | Chord Source (Priority Order) | | ---------------- | --------------------------------------------------- | | `id` | `properties.products[].product_id` → `.sku` → `.id` | | `name` | `properties.products[].name` | | `content_type` | `properties.products[].category` | | `quantity` | `properties.products[].quantity` (defaults to `1`) | | `amount` | `properties.products[].price`, in minor units | | `currency` | The order currency | ## Amounts are sent in minor units OpenAI expects every monetary amount as an **integer in the currency's minor unit**, so `$129.99` is sent as `12999`. Chord converts this for you. Zero-decimal currencies are handled correctly: `1000 JPY` is sent as `1000`, not `100000`. This matters because OpenAI accepts either value without complaint — a mistake here would silently report every conversion 100 times too high. # Advanced Matching When **Enable Advanced Matching** is on, visitor identifiers are SHA-256 hashed in the browser before being sent. Plaintext PII is never transmitted. | OpenAI Attribute | Chord Source (Priority Order) | Normalization | | --------------------- | ----------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | | `email_sha256` | `context.traits.email` → `properties.email` | Trimmed and lowercased, then hashed | | `phone_number_sha256` | `context.traits.phone` → `properties.phone` | Country code kept; whitespace, punctuation, a leading `+` and leading zeroes removed. Must be 8–15 digits | | `external_id_sha256` | `userId` | Trimmed, **case preserved**, then hashed | | `first_name_sha256` | `context.traits.first_name` → `properties.first_name` | Lowercased, whitespace and ASCII punctuation removed, accents preserved | | `last_name_sha256` | `context.traits.last_name` → `properties.last_name` | Same as first name | | `city` | `context.traits.address.city` | Sent unhashed | | `region` | `context.traits.address.state` | Sent unhashed | | `postal_code` | `context.traits.address.zipcode` | Sent unhashed | | `country` | `context.traits.address.country` | Sent unhashed | A value that cannot be used is omitted rather than hashed — placeholders such as `n/a` or `unknown`, and phone numbers too short to be real, are dropped, since hashing them would send a digest that matches nobody. A value that is already a SHA-256 hash is passed through rather than hashed twice. These normalization rules match the OpenAI Ads Conversions API destination exactly, so the same person produces the same digest on both surfaces. Note that the pixel's field names are **singular** (`email_sha256`) while the Conversions API's are plural lists (`emails_sha256`) — both are correct for their own surface. Advanced matching is supplied at initialization, which is the only point at which the pixel accepts user data. An `identify` call re-initializes the pixel with the newly known identifiers, raising the match rate for the rest of the session; `identify` itself is not reported as a conversion. # Attribution OpenAI appends an `oppref` query parameter to ad click-through URLs. The pixel captures it on the landing page and persists it in a first-party `__oppref` cookie, along with its own `__obref` browser reference, so later events in the session remain attributable. Chord also captures both values onto the event, which is what allows the **OpenAI Ads Conversions API** destination to attribute server-side conversions — OpenAI's documentation is explicit that the Conversions API does not collect `oppref` on its own. # Custom Properties Are Not Forwarded OpenAI validates each event against a closed schema. The conversion data accepts only `type`, `amount`, `currency`, `contents` and `plan_id`, and there is no custom-data field on the event either — unlike most ad platforms, which provide one. An unrecognized field is not ignored. OpenAI rejects the whole event, and the pixel logs `validation failed; event dropped` in the browser console. So Chord deliberately sends **no** custom properties to this destination; forwarding them would discard the conversion entirely. Custom property mappings that target a field OpenAI *does* accept still work normally. Remapping the source of the order total or currency, for example, reaches OpenAI as usual — it is only destination fields with no OpenAI equivalent that cannot be delivered. The same applies to the OpenAI Ads Conversions API destination. If you need to segment on a property OpenAI has no field for, register a custom event in Ads Manager and route the event to it with **Custom Event Mapping** instead. # Empty Cart Protection An `Order Completed` event with no products is skipped with a warning rather than sent. An empty purchase is a data-quality problem upstream, not a conversion, and forwarding it would corrupt your conversion counts and revenue reporting. # Initialization The plugin loads `https://bzrcdn.openai.com/sdk/oaiq.min.js` and calls `oaiq("init", { pixelId })`. Before the script loads, a queue buffers any calls to `oaiq` so nothing is lost during load. 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. The OpenAI SDK does **not** fire a page view on initialization. Chord sends `page_viewed` explicitly for each `page` call, so page views are neither missed nor doubled. # CSP Requirements If your site uses a Content Security Policy, allow the following domains: | Directive | Domain | | ------------- | --------------------------- | | `script-src` | `https://bzrcdn.openai.com` | | `connect-src` | `https://bzr.openai.com` | # Troubleshooting **No events appear in Ads Manager** - Confirm the **Pixel ID** matches the `pixel_id` returned when the pixel was created. - Enable **Debug Logging** and check the browser console for the SDK's own output. - Check the Chord CDP **Live Events** stream to confirm the event reached the CDP at all. **Events appear but conversions are attributed to no campaign** - Confirm `oppref` is present in the landing page URL when arriving from an ad. - Check that the `__oppref` cookie is being set and is not blocked by a consent tool. **A conversion is counted twice** - Confirm the **OpenAI Ads Conversions API** destination uses the **same Pixel ID**. - Confirm any events you send to OpenAI outside Chord reuse the Chord `messageId` as their `event_id`. **An event is missing entirely** - Check the browser console for a "Skipping unsupported event" warning. OpenAI accepts only the fixed event set above; anything else needs a registered custom event and a **Custom Event Mapping** entry. *** **Updated 31 August 2026** [title] OpenAI Ads (Conversions) [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ **OpenAI Ads Conversions API** is OpenAI's server-side conversion API for ChatGPT Ads. This destination sends conversion events directly from Chord to OpenAI, so measurement is unaffected by ad blockers, browser tracking restrictions and cookie expiry. Pair it with the **OpenAI Ads Pixel** destination. The two are complementary: the pixel captures OpenAI's `oppref` click identifier in the browser, which the Conversions API needs but does not collect for itself. # Getting Started You will need: - **Pixel ID** — your OpenAI Ads pixel ID. - **API Key** — your OpenAI Ads Conversions API key. Create both in **OpenAI Ads Manager** under **Tools > Conversions**, which offers a **Conversion Key** and a **Pixel ID**. :::BlockQuote **Use the Conversion Key — not the API key under Settings.** Ads Manager exposes three credentials and only two of them belong here. The key under **Settings** authenticates OpenAI's separate management API, and the Conversions API rejects it as unauthorized. Chord never needs it. ::: The Conversion Key is **per ad account, not per pixel** — one key covers every pixel in the account. Optionally: - **Custom Event Mapping** — routes a Chord event that OpenAI has no standard equivalent for onto a custom event you have registered in Ads Manager. - **Validate Only** — OpenAI validates each event and records nothing. Use it to confirm an integration end to end without affecting reporting, then turn it off. :::BlockQuote **Important:** If you are also using the **OpenAI Ads Pixel** destination, both must be configured with the **same Pixel ID** and the **same Custom Event Mapping**. OpenAI deduplicates on the combination of pixel ID, event name and event ID — with a different pixel ID, one purchase is counted twice. ::: # Connecting to the OpenAI Ads 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 **OpenAI Ads Conversions API** from the destination catalog. 5. Enter the destination name, your **Pixel ID** and your **API Key**. 6. Optionally configure **Custom Event Mapping** and **Validate Only**. 7. Click **"Create"** to connect. # Verifying an Integration Enable **Validate Only** before sending live traffic. OpenAI will validate the full shape of every event and record nothing, so you can confirm the integration is correct against a production pixel without affecting reporting. Turn it off once you are satisfied. # Deduplication Every event carries `id`, set to the Chord `messageId`. OpenAI deduplicates on the combination of **pixel ID**, **event name** and **event ID**, keeping the first event it receives for a matching key and ignoring later duplicates. The **OpenAI Ads Pixel** destination sends the same `messageId` as its `event_id`, so a conversion reported by both the browser and your server is recorded once. This also protects you if you are sending your own events to OpenAI alongside Chord: reuse the Chord `messageId` as your event ID and OpenAI will merge them rather than double-counting. # Event Mapping OpenAI accepts a fixed set of event names. A Chord event with no equivalent is skipped and logged — it is not forwarded under a made-up name, because OpenAI silently discards an unregistered event name, which is indistinguishable from a successful send. | Chord Event | OpenAI Event | `data.type` | | ---------------------- | ------------------------ | ----------------- | | `page` | `page_viewed` | `contents` | | `Product Viewed` | `contents_viewed` | `contents` | | `Product Added` | `items_added` | `contents` | | `Checkout Started` | `checkout_started` | `contents` | | `Order Completed` | `order_created` | `contents` | | `Signed Up` | `registration_completed` | `customer_action` | | `Email Captured` | `lead_created` | `customer_action` | | `Subscription Created` | `subscription_created` | `plan_enrollment` | To forward anything else, first create a custom event in ChatGPT Ads Manager, then add a **Custom Event Mapping** entry pointing your Chord event name at it. Names are lowercased and spaces become dashes, so `Wishlist Added` becomes `wishlist-added`; the result must be 1–64 characters of lowercase letters, numbers, underscores or dashes. # Event Attributes | OpenAI Attribute | Chord Source (Priority Order) | Notes | | ------------------- | --------------------------------------------------- | -------------------------------- | | `id` | `messageId` | The deduplication key | | `type` | — | Set from the event mapping table | | `custom_event_name` | **Custom Event Mapping** | Custom events only | | `timestamp_ms` | `timestamp` → `receivedAt` | Milliseconds since epoch | | `action_source` | — | Always `web` | | `source_url` | `context.page.url` | | | `oppref` | `properties.oppref` → the captured click identifier | See **Attribution** below | | `data` | See below | | ## Conversion Data | OpenAI Attribute | Chord Source (Priority Order) | Notes | | ---------------- | -------------------------------------------------------------- | ------------------------------------------------------------ | | `type` | — | Set from the event mapping table. Required by OpenAI | | `amount` | `properties.total` → `properties.revenue` → `properties.value` | **Minor currency units.** See below | | `currency` | `properties.currency` | Defaults to `USD`. Required whenever `amount` is present | | `contents` | `properties.products[]` | Omitted for `customer_action` events, which do not accept it | | `plan_id` | `properties.subscription_id` → `properties.plan_id` | `subscription_created` only | Each entry in `contents` is built from a product: | OpenAI Attribute | Chord Source (Priority Order) | | ---------------- | --------------------------------------------------- | | `id` | `properties.products[].product_id` → `.sku` → `.id` | | `name` | `properties.products[].name` | | `content_type` | `properties.products[].category` | | `quantity` | `properties.products[].quantity` (defaults to `1`) | | `amount` | `properties.products[].price`, in minor units | | `currency` | The order currency | ## Amounts are sent in minor units OpenAI expects every monetary amount as an **integer in the currency's minor unit**, so `$129.99` is sent as `12999`. Chord converts this for you. Zero-decimal currencies are handled correctly: `1000 JPY` is sent as `1000`, not `100000`. This matters because OpenAI accepts either value without complaint — a mistake here would silently report every conversion 100 times too high. # Conversion Matching Visitor identifiers are SHA-256 hashed before being sent. Plaintext PII is never transmitted. | OpenAI Attribute | Chord Source (Priority Order) | Normalization | | ---------------------- | ----------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | | `emails_sha256` | `context.traits.email` → `properties.email` | Trimmed and lowercased, then hashed | | `phone_numbers_sha256` | `context.traits.phone` → `properties.phone` | Country code kept; whitespace, punctuation, a leading `+` and leading zeroes removed. Must be 8–15 digits | | `external_ids_sha256` | `userId` | Trimmed, **case preserved**, then hashed | | `first_names_sha256` | `context.traits.first_name` → `properties.first_name` | Lowercased, whitespace and ASCII punctuation removed, accents preserved | | `last_names_sha256` | `context.traits.last_name` → `properties.last_name` | Same as first name | | `cities` | `context.traits.address.city` | Sent unhashed | | `regions` | `context.traits.address.state` | Sent unhashed | | `postal_codes` | `context.traits.address.zipcode` | Sent unhashed | | `countries` | `context.traits.address.country` | Sent unhashed | | `obref` | The `__obref` cookie set by the OpenAI Ads Pixel | Sent unhashed | | `ip_address` | `requestIp` → `context.ip` | Sent unhashed | | `user_agent` | `context.userAgent` | Sent unhashed | A value that cannot be used is omitted rather than hashed — placeholders such as `n/a` or `unknown`, and phone numbers too short to be real, are dropped, since hashing them would send a digest that matches nobody. A value that is already a SHA-256 hash is passed through rather than hashed twice. These normalization rules match the **OpenAI Ads Pixel** destination exactly, so the same person produces the same digest on both surfaces. Note that the Conversions API's field names are **plural lists** (`emails_sha256`) while the pixel's are singular (`email_sha256`) — both are correct for their own surface. Chord sends one value per identifier. OpenAI accepts up to three per list and ignores the rest. Android advertising IDs are forwarded as `android_advertising_id` on Android traffic only. OpenAI has no equivalent field for an iOS advertising ID, so one is omitted rather than sent in the wrong place. # Attribution OpenAI appends an `oppref` query parameter to ad click-through URLs, and OpenAI's documentation is explicit that — unlike the pixel — **the Conversions API does not capture it for you**. Chord handles this: the browser library captures `oppref` from the landing page URL, along with the `__oppref` and `__obref` cookies the OpenAI Ads Pixel sets, and carries them on every subsequent event including the purchase. Installing the **OpenAI Ads Pixel** destination alongside this one is therefore the recommended setup — without a source of `oppref`, server-side conversions cannot be attributed to the ad that produced them. If your storefront resolves the click identifier itself, send it as `properties.oppref` and it will be used in preference. # Timestamps OpenAI rejects an event timestamped more than 7 days in the past or more than 10 minutes in the future. If an event carries no parseable timestamp, Chord falls back to the time it was received and then to the current time — an approximate time is better than a rejected batch, which would lose the event entirely. # Retries Rate limits (`429`) and OpenAI server errors (`5xx`) are retried. A rejected event — a validation failure such as a malformed field — is not retried, because the same payload would be rejected again; it is logged instead so it appears in the CDP function logs. # Property Mappings OpenAI validates each event against a closed schema: the conversion data accepts only `type`, `amount`, `currency`, `contents` and `plan_id`, and there is no custom-data field. An unrecognized field causes OpenAI to reject the event, so Chord forwards no custom properties to this destination. Mappings that change **where a supported field is read from** work normally — that is what the table below is for. If you need to segment on a property OpenAI has no field for, register a custom event in Ads Manager and route to it with **Custom Event Mapping** instead. Use custom property mappings if the default field resolution does not match your data model: | Destination Path | Description | | ---------------------------------- | ------------------------------------------------------- | | `properties.email` | Email for conversion matching | | `properties.phone` | Phone for conversion matching | | `properties.first_name` | First name for conversion matching | | `properties.last_name` | Last name for conversion matching | | `properties.total` | Primary conversion value | | `properties.revenue` | Fallback conversion value | | `properties.currency` | Currency code (e.g. `USD`) | | `properties.oppref` | OpenAI click identifier, if your storefront resolves it | | `properties.subscription_id` | Plan ID for subscription events | | `properties.products[].product_id` | Product content IDs | | `properties.products[].price` | Per-item price | | `properties.products[].quantity` | Per-item quantity | | `properties.products[].name` | Product display name | | `properties.products[].category` | Product content type | # Troubleshooting **No events appear in Ads Manager** - Confirm the **API Key** is the **Conversion Key** from the Conversions section, not the API key from **Settings**. The Settings key belongs to OpenAI's management API and is rejected here. - Confirm the **Pixel ID** and the key belong to the same ad account. - Confirm **Validate Only** is switched off. While it is on, OpenAI validates events and records nothing. - Check the CDP function logs for the response OpenAI returned. **Conversions are attributed to no campaign** - Confirm the **OpenAI Ads Pixel** destination is installed on the storefront, since it is what captures `oppref`. - Confirm the `__oppref` cookie is being set and is not blocked by a consent tool. **A conversion is counted twice** - Confirm the **OpenAI Ads Pixel** destination uses the **same Pixel ID**. - Confirm any events you send to OpenAI outside Chord reuse the Chord `messageId` as their event ID. **An event is missing entirely** - Check the CDP function logs for a "Skipping unsupported event" warning. OpenAI accepts only the fixed event set above; anything else needs a registered custom event and a **Custom Event Mapping** entry. *** **Updated 31 August 2026** [title] CDP Notifications (Event Alerts) [path] Chord CDP/ # Overview CDP Event Alerts allow your team to stay informed when specific customer behavior or data events occur in your Chord-connected ecosystem. Whether you’re monitoring for conversion milestones, failed transactions, or custom triggers unique to your brand, Event Alerts provide real-time visibility into what matters most. :::hint{type="info"} **No support for client-side destinations**: Chord does **not **provide monitoring for events sent directly from the browser to external tools (e.g., client-side destinations), since these events do **not **pass through the CDP. ::: # What It Does Chord CDP Event Alerts notify you via email when a configured event alert is captured by Chord’s data infrastructure. This ensures you can take timely action—or simply stay aware—when high-impact behaviors are observed via Chord CDP. Event alerts give you peace of mind by making sure your data is always moving where it needs to go. The first set of alerts covers two key failure points: if no source events are recorded for an hour (or other chosen option), or if no events are delivered to a destination for a specified period of time. These alerts act as an early warning system—helping your team catch issues quickly so you can trust that your data is complete and reliable. Additionally, **users will only receive one notification per site (source) or connection (destination) every 24 hours if an issue is detected**. For example: 1. User subscribes to notifications for missing data on Source A (or Destination A). 2. Source A (or Destination A) doesn't receive any events for over an hour (or other specified timeframe). 3. Chord CDP will send an email notification to the user who set up an alert for Source A (or Destination A). 4. Chord CDP will send another notification in 24 hours (assuming Source A or Destination A continues not to receive any events). :::hint{type="info"} **Note: **You will not receive an email confirming that the issue has been resolved. Once you receive an alert and resolve it, you will not receive any additional alerts (unless the source or destination error perists or occurs again). ::: Lastly, this version of CDP alerts **does not include** monitoring for: - Unexpected spikes or drops in source event volume; or - Delivery drops or delays for events sent successfully to destinations. # Getting Started ## Requirements - Your sites (sources) and destination connections must be instrumented on Chord CDP. - You must have appropriate permissions to access alert configurations. ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-yVKcz38jJvNuOaJEzhbHE-20250911-211407.png) ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/XDCOCuSoOIte5XF8XUsG2-20260127-225009.png) :::hint{type="info"} You can now customize the threshold for when you’ll be alerted if no data is ingested from a source or delivered to a destination. Previously, the default was one hour. This update helps reduce noise from false positives — especially for connections that naturally receive data less frequently. ::: To access and set event alerts, follow the instructions below: 1. Log into the Chord data platform and navigate to the **Chord CDP** page. 2. Click on the **Notifications** tab on the Chord CDP page. 3. Review the list of available sites (sources) and connections (destinations) that you’d like to receive alerts about. 4. As you check (or uncheck) the alerts you would like to receive, you will see a dropdown menu with timeframes. 5. For each selected source or destination connection, choose the when to be alerted when your data hasn't been flowing from sources or into destinations: **1 hour, 2 hours, 4 hours, or 8 hours**. 6. When no source events are ingested and/or no events are successfully delivered to a destination for the duration of your selected window, you will receive an email from Chord CDP identifying which site or connection is experiencing issues. [title] Rokt Conversions API [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ Rokt is an advertising and offer-placement network. The Rokt Events API destination sends conversions and page views to Rokt from Chord's servers, so Rokt can attribute a purchase or signup back to the campaign that drove it and build retargeting audiences. Because it runs server-side it is unaffected by ad blockers and browser tracking restrictions. For the browser equivalent, see [Rokt Pixel](https://rokt-pixel.md). The two can run together — see **Using Alongside the Rokt Pixel** below. This replaces Rokt's deprecated Conversions API. # Getting Started You need an **API key and API secret** for Rokt's Events API. Rokt provisions these — contact your Rokt account manager if you do not have them. They are a different credential from the API key used by the Rokt Pixel destination, and the two are not interchangeable. Note that Rokt's self-serve integration wizard only offers the browser snippet. The Events API is not self-serve, so the credentials come from your account manager rather than from **my.rokt.com**. Three settings are optional: - **Custom Event Mapping** — route an additional Chord event onto a Rokt conversion type. See **Event Mapping** below. - **Send Page View Events** — on by default, sending page views as `screen_view` conversions for retargeting audiences. Turn it off if you only want purchase, signup and subscription conversions; page views are high volume. - **API URL** — only if Rokt has provisioned your account in a region other than the default. # Connecting to the Rokt Events 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 **Rokt Events API** from the destination catalog. 5. Enter the destination name, your **API Key** and your **API Secret**. 6. Click **"Create"** to connect. 7. Connect it to your event sources. # Event Mapping Rokt records a conversion as a single event named `conversion`, with a `conversiontype` attribute saying what kind it was. Chord maps events like this: | Chord event | Rokt `conversiontype` | | --------------------------- | --------------------- | | `Order Completed` | `purchase` | | `Signed Up`, `User Created` | `signup` | | `Subscription Created` | `subscription` | | Page and screen views | `screen_view` | **Anything not in that table is skipped**, and the skip is logged so you can see it in Live Events. Use **Custom Event Mapping** to route an additional event onto one of the four conversion types — for example `Trial Started` → `subscription`. A mapping naming anything outside those four values is ignored. If you also run the Rokt Pixel destination, **configure the same mapping on both**. Otherwise the same conversion is classified one way from the server and another way in the browser. :::BlockQuote Rokt's public documentation describes `conversiontype` as free text and lists further example values elsewhere, without publishing a definitive set. Chord sends only the four above until Rokt confirms which values their reporting acts on. If you need another one, ask your Rokt account manager to confirm it and we will add it to both destinations together. ::: # Identity and User Attributes Rokt matches a conversion to a campaign on the shopper's email address, so a conversion without one will not attribute. Chord sends the address both in plain text and as a SHA-256 hash, which is what Rokt's identity model expects, along with your internal user ID. Alongside the email, Chord sends Rokt's recommended user attributes when your events carry them — first name, last name, mobile number, city, state and postal code — each with its SHA-256 counterpart where Rokt defines one. Rokt's own canonicalization rules are applied before hashing: lowercase and trim for email and names, digits only for the mobile number. # The Rokt Click ID Rokt appends a Click ID (`rtid`) to the landing page URL when a shopper arrives from a Rokt placement. Chord's JS SDK captures it and stores it for 30 days, so a purchase that happens several pages later still carries it, and passes it back to Rokt on the conversion. You do not need to configure this — it works as long as Chord's SDK is installed on the storefront. It matters most for conversions that happen on a later page view than the click, which is nearly all of them. # Deduplication Rokt deduplicates on `confirmationref`. Chord sends your order ID there for purchases, and for conversions with no order — a signup, say — it sends the event's `messageId` instead, so every conversion carries a stable reference. That is also what makes it safe to run this destination alongside the Rokt Pixel: both derive `confirmationref` the same way, so Rokt sees one conversion rather than two. If you push conversions into the same Rokt account from another system, `confirmationref` is the value to deduplicate against. # Using Alongside the Rokt Pixel Both destinations report to the same Rokt account and deduplicate on the same key, so running both is supported and is the more reliable setup: - **This destination** survives ad blockers and browser tracking restrictions, and reports conversions that never touch a browser — a subscription renewal, or an order placed by support. - **The **[Rokt Pixel](https://rokt-pixel.md) establishes the browser session Rokt uses for retargeting, and captures the Rokt Click ID itself. Use the same **Custom Event Mapping** on both. That is the one setting where a difference between them changes what Rokt records. # Errors and Retries Rokt acknowledges an accepted batch with `202`. Rate limits (`429`) and Rokt-side errors (`5xx`) are retried with backoff. A rejected payload or bad credentials (`400`, `401`, `403`) is not retried, because no retry would fix it — check the error in Live Events. [title] Rokt Pixel [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ Rokt is an advertising and offer-placement network. The Rokt Pixel destination loads Rokt's Web SDK in the browser and records conversions and page views, so Rokt can attribute a purchase or signup back to the campaign that drove it and build retargeting audiences. For the server-side equivalent, see [Rokt Events API](https://rokt-conversions.md). The two can run together — see **Using Alongside the Rokt Events API** below. # Getting Started ou need one value, and one thing removed. **Your Rokt credential.** Rokt runs two browser SDKs and provisions an account for one or the other, so paste whichever value **my.rokt.com > Integrations > Set up the Snippet** gave you and Chord loads the matching integration: - If your snippet loads from `apps.rokt-api.com` and carries an **API Key**, put it in **API Key**. - If your snippet calls `createLauncher({ accountId })` and loads `launcher.js`, put that value in **Account ID**. Fill in one, not both. They are not interchangeable — an Account ID in the API Key field produces a `404` from Rokt's CDN and nothing loads. Neither is the API key and secret pair the [Rokt Events API](https://rokt-conversions.md) destination uses. :::BlockQuote **The Account ID integration can display Rokt offers on your site.** Its only entry point is Rokt's offer-selection call, so on each conversion Chord asks Rokt for a placement and Rokt may render an overlay, an embedded unit, or an interstitial on your confirmation page. What renders, and whether anything does, is controlled by what you configure in Rokt. The API Key integration records conversions without requesting placements. ::: **Remove any Rokt snippet you installed yourself.** This destination replaces it. Two copies of Rokt's SDK on one page initialize twice and report every conversion twice. Two settings are worth a decision: - **Email Format** — whether the shopper's email is sent raw or as a SHA-256 hash. Rokt matches conversions to campaigns on the email address and accepts either, and their own setup wizard recommends the raw address, so that is the default here. Switch to hashed if your security policy does not allow a plain email address in the page's network traffic — Rokt matches either form, so this costs you nothing in attribution. - **Development Mode** — routes events to Rokt's development data environment. Turn it on while you are testing and off before launch. Rokt does not report on development data. **Custom Event Mapping** is optional. See **Event Mapping** below for when you need it. # Connecting to the Rokt 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 **Rokt Pixel** from the destination catalog. 5. Enter the destination name and either your **API Key** or your **Account ID**, and choose an **Email Format**. 6. Click **"Create"** to connect. 7. Connect it to your **front-end** site. 8. Remove your own Rokt snippet from the storefront. # Event Mapping Rokt records a conversion as a single event named `conversion`, with a `conversiontype` attribute saying what kind it was. Chord maps events like this: | Chord event | Rokt `conversiontype` | | --------------------------- | ---------------------------------------------------------------------------- | | `Order Completed` | `purchase` | | `Signed Up`, `User Created` | `signup` | | `Subscription Created` | `subscription` | | Page views | `screen_view`, sent through Rokt's page view call (API Key integration only) | On the Account ID integration, page views are not sent: Rokt's offer-selection call is the only entry point it has, and asking for a placement on every page is not what it is for. Conversions are sent identically on both. **Anything not in that table is skipped**, and the skip is written to the browser console so you can see it happened. Use **Custom Event Mapping** to route an additional event onto one of the four conversion types — for example `Trial Started` → `subscription`. A mapping naming anything outside those four values is ignored. If the Rokt Events API destination has been enabled for your store, **configure the same mapping on both**. Otherwise the same conversion is classified one way in the browser and another way from the server. :::BlockQuote Rokt's public documentation describes `conversiontype` as free text and lists further example values elsewhere, without publishing a definitive set. Chord sends only the four above until Rokt confirms which values their reporting acts on. If you need another one, ask your Rokt account manager to confirm it and we will add it to both destinations together. ::: # Identity and User Attributes Rokt matches a conversion to a campaign on the shopper's email address, so a conversion without one will not attribute. The address is lowercased and trimmed before it is sent, which is the same rule Rokt specifies before hashing. That means switching **Email Format** does not change which shopper Rokt resolves — only whether the address is readable in the page's network traffic. Alongside the email, Chord sends Rokt's recommended user attributes when your events carry them — first name, last name, mobile number, city, state and postal code — each with its SHA-256 counterpart where Rokt defines one. Rokt's own canonicalization rules are applied before hashing: lowercase and trim for email and names, digits only for the mobile number. The Rokt Click ID needs no configuration here. Rokt's SDK captures it itself when it initializes and attaches it to conversions. # Deduplication Rokt deduplicates on `confirmationref`. Chord sends your order ID there for purchases, and for conversions with no order — a signup, say — it sends the event's `messageId` instead, so every conversion carries a stable reference. It is also what makes it safe to run this destination alongside the Rokt Events API destination, where that has been enabled: both derive `confirmationref` the same way, so Rokt sees one conversion rather than two. If you push conversions into the same Rokt account from another system, `confirmationref` is the value to deduplicate against. # Custom Properties Rokt accepts custom attributes on a conversion, so any property mapping you configure is forwarded alongside the standard attributes. Use a bare property path in the mapping's destination field. Mapped properties cannot overwrite the attributes Rokt defines itself — `conversiontype`, `confirmationref`, `amount` and `currency` are reserved and always carry Chord's computed values. # Empty Carts An `Order Completed` with no products does not fire a conversion. An empty purchase is almost always a tracking fault rather than a real order, and reporting it inflates Rokt's conversion count with something you cannot reconcile. # Content Security Policy If your storefront enforces a Content Security Policy — every Hydrogen storefront does by default — Rokt will not load until these hosts are allowed. The symptom of a missing entry is a destination that looks connected and sends nothing. | Directive | Hosts | Needed for | | ------------- | -------------------------------------------------------------------------------------- | --------------------------------------------- | | `script-src` | `https://apps.rokt.com`, `https://apps.rokt-api.com`, `https://apps.roktecommerce.com` | loading the SDK | | `connect-src` | `https://apps.rokt.com`, `https://apps.rokt-api.com`, `https://apps.roktecommerce.com` | sending conversions | | `frame-src` | `https://apps.rokt.com` | the offer placement, which renders in a frame | | `font-src` | `https://apps.rokt.com` | the icon font the placement uses | `apps.rokt.com` serves the Account ID integration; `apps.rokt-api.com` and `apps.roktecommerce.com` serve the API Key one. Allowing all three covers either, and costs nothing if you only use one. `apps.roktecommerce.com` is Rokt's documented fallback host — the API Key SDK retries there when the primary CDN is blocked, so omitting it removes the fallback that keeps the pixel working behind some ad blockers. `frame-src`** and **`font-src`** are only needed for the Account ID integration**, and only because it renders an offer. They are not in Rokt's published CSP guidance — we found them by watching the network tab during a live conversion, where the placement pulled an HTML document and `rokt-icons.woff` from `apps.rokt.com`. If your policy does not set `font-src` explicitly it will inherit your `default-src`, which may already permit it. Your storefront team applies this, usually in a different repository from your Chord configuration. If you use a Rokt first-party collection domain, allow that host too. This list was confirmed against a live storefront for the Account ID integration. The API Key integration's hosts come from Rokt's published guidance and have not been exercised live, so treat those as a starting point and check the browser console for violations on your first test. [title] Functions [path] Chord CDP/ :::hint{type="info"} Due to the technical nature of this feature, functions are only available to Chord users who are assigned a **Team Admin** or **Developer **platform role. For additional support, please reach out to [help@chord.co](mailto\:help@chord.co). ::: # Introduction ![](https://archbee-image-uploads.s3.amazonaws.com/VPxpEoMPxDsnmxOyjOdWV-Z-iOdsI4OZ8xa0W0Q2dqS-20250911-211622.png) Functions are customizable data workflows that process, transform, or enrich the raw event data flowing through the CDP. Functions are written in JavaScript and run before data is sent to destinations. They let you tailor how data is handled—whether it's standardizing event names, enriching user profiles, or formatting data for downstream tools—so you can keep your insights clean, consistent, and actionable. In other words... - For **Marketers**, CDP functions are more like custom-built control panels. They give your team the flexibility to reshape data in real time, enrich it with external info, or even decide what gets sent where—perfect for brands needing more control, precision, and adaptability. - For **Developers**, CDP functions offer broader execution power. They act like real-time serverless functions with support for external API calls, persistent key-value storage, and conditional logic. You can reshape event streams on the fly, enrich payloads, or build highly dynamic routing logic—ideal for engineering teams looking for full control over their pipeline behavior. Some additional use cases for functions include: - **Filtering** - Exclude unwanted events, such as dropping events from test sources or internal traffic - **Normalizing** - Standardize event data (e.g., "page\_view", "pageview", "pageView" → "page") to keep downstream schemas clean - **Enrichment** - Add geo-location data, parse user agents, or pull additional data from external APIs - **Routing** - Dynamically change which table or destination an event is sent to based on event properties ## Function Anatomy Every CDP function follows this structure: ```javascript export default async function(event, context) { // Your transformation logic here return event; // or "drop" to filter out the event } ``` ## Parameters ### event (Object) The event object being processed. This is the raw event data coming from your sources. Common properties include: - event (string) - The event name (e.g., "Page Viewed", "Product Added") - userId (string) - The unique identifier for the user - anonymousId (string) - Anonymous identifier if userId is not available - timestamp (string) - ISO 8601 timestamp of when the event occurred - properties (object) - Custom properties associated with the event - context (object) - Contextual information about the event (IP, user agent, etc.) - type (string) - The event type (e.g., "track", "identify", "page") ### context (Object) The function context provides access to various services: **Logging** - context.log.debug(message) - Debug-level logging - context.log.info(message) - Info-level logging - context.log.warn(message) - Warning-level logging - context.log.error(message) - Error-level logging **Storage** - context.store - Persistent key-value storage that maintains data between function calls **Network & External Services** - context.fetch(url, options) - Standard Fetch API for making HTTP requests to external services ### Return Values The function's return value controls what happens to the event: - **Return an object** - The returned object becomes the new event sent to destinations - **Retun an array of objects - **Only the final function in a function chain can return an array of objects. Each object becomes a new event sent to destinations. - **Return "drop"** - The event is filtered out and won't be forwarded to the downstream destination - **Return nothing/undefined** - The original event (or its modified copy) is used # Create a Function To create a function, follow the steps below: 1. Navigate to **CDP**. 2. Navigate to the **Functions** tab. 3. Click the **"+ New Function"** button. 4. Click into the function name field at the top left and give your function a name. Click the ✔️ icon to save the function name. 5. Add your function code into the WYSIWYG editor. 6. Click the **"Save"** button to save your function. # Debugging Functions Chord CDP comes with a debugger and editor that allows you to run a function on sample data. Within a function, you have access to **Logs** which will emit debug / information messages. Here, you can instrument your JavaScript to print out event contents, branching logic, and intermediate values to help trace what the function is doing. Additionally, you can check the **Last Run Result** tab within a specific Function to see what the function returned - whether it dropped the event, modified it, or forwarded it. This tab will include logs, errors, or additional metadata about that run. You will be able to see exactly how the function behaved for the latest event and catch transform/filter mistakes. # Edit Functions 1. Navigate to **CDP**. 2. Navigate to the **Functions** tab. 3. Find the existing function you'd like to edit. 4. Click the ✏️ icon under the **Actions** column next to the function you want to edit. # Delete Functions 1. Navigate to** CDP**. 2. Navigate to the **Functions** tab. 3. Find the existing function you'd like to delete. 4. Click on the three vertical dots under the **Actions** column next to the function you want to delete. 5. Click the 🗑️ icon to delete the desired function. # Connecting / Environment Variables Functions chains are created on connections between sources and destinations. 1. Navigate to** CDP**. 2. For a given destination, click the three dots next to the destination title then select **"View Connected Streams"**. 3. Select the ✏️ icon under **Actions** to edit the connection. 4. Functions can be added to the pipeline from the functions library. Functions will run in the order specified in this interface. 5. Click **"Save changes"**. Environment variables are configured on a **per connection basis**. Define envrionment variable names and values for the connection below the function library in the **"Edit Connection"** drawer. Environment variables may be referenced in code like so: ```javascript process.env.VARIABLE_NAME ``` # Persistent Storage for Custom Functions Persistent Storage allows functions to cache data between invocations, enabling use cases like rate limiting, deduplication, enrichment caching, and maintaining state across events. When enabled, your CDP functions have access to a `store` object that provides a key-value cache with TTL (time-to-live) support. The store is backed by an in-memory cache and persists data across function invocations within the same workspace. ## Using the Store in Custom Functions ### Basic Operations The store provides the following methods: ```javascript // Get a value (returns undefined if not found or expired) const value = await store.get("my-key"); // Set a value with default TTL (31 days) await store.set("my-key", { foo: "bar" }); // Set a value with custom TTL await store.set("my-key", { foo: "bar" }, "1h"); // 1 hour await store.set("my-key", { foo: "bar" }, "7d"); // 7 days await store.set("my-key", { foo: "bar" }, 3600); // 3600 seconds await store.set("my-key", { foo: "bar" }, "inf"); // No expiration // Delete a value await store.del("my-key"); // Get TTL remaining (in seconds) const ttl = await store.ttl("my-key"); // Returns: positive number = seconds remaining, -1 = no expiry, -2 = key doesn't exist // Get value with TTL info const result = await store.getWithTTL("my-key"); // Returns: { value: any, ttl: number } or undefined ``` ### Complete Example ```javascript export default async function(event, { log, fetch, store }) { let key = "my-key"; let ttl = "10s"; // Retrieve the value from the cache let value = await store.get(key); // If the value was cached, display it. // Else, put the value in the cache that will expire in 10s. if (value) { log.info(`Cache hit! Value is ${value}`); } else { let newValue = Math.random().toString(36).substring(2) log.info(`Cache miss! Adding ${newValue} to cache; TTL ${ttl}.`); await store.set(key, newValue, ttl); } } ``` ## TTL Format The TTL parameter accepts several formats: | Format | Example | Description | | --------------- | ------------------------------- | ----------------------- | | Number | `3600` | Seconds | | Duration string | `"30s"`, `"5m"`, `"2h"`, `"7d"` | Human-readable duration | | Infinite | `"inf"` | No expiration | | Default | (omitted) | 31 days | Maximum TTL is approximately 68 years (2,147,483,647 seconds). ## Cache Availability and Graceful Degradation The Persistent Storage feature is designed to be resilient. If the cache becomes temporarily unavailable: - **Functions continue to work**: Your custom functions will not fail or be retried due to cache issues - **Cache operations degrade gracefully**: - `get()` returns `undefined` (treated as a cache miss) - `set()` silently fails (data won't be cached) - `del()` silently fails (key may not be deleted) - `ttl()` returns `-2` (key doesn't exist) - **Warnings are logged**: Cache failures are logged for monitoring, but don't interrupt event processing This means your functions should be written to handle cache misses gracefully, as they may occur due to: 1. Key not existing (normal cache miss) 2. Key expired (TTL reached) 3. Cache temporarily unavailable (graceful degradation) ### Writing Resilient Functions Always write your functions assuming the cache might be empty: ```javascript // Good: Handles cache miss gracefully const cached = await ctx.store.get("my-key"); if (!cached) { // Regenerate or fetch the data const freshData = await fetchData(); await ctx.store.set("my-key", freshData, "1h"); return processEvent(event, freshData); } return processEvent(event, cached); // Avoid: Assuming cache always has data const cached = await ctx.store.get("my-key"); return processEvent(event, cached.someProperty); // May fail if cached is undefined ``` ### Key Naming and Uniqueness **Important:** Storage keys are shared across all functions in your CDP workspace. This means: - A key set by one function can be read, modified, or deleted by any other function in the same workspace - You must ensure your keys are unique to avoid unintended collisions between functions ### Best Practices for Key Naming **Use function-specific prefixes** to namespace your keys: ```javascript // Good: Namespaced keys await store.set("rate-limiter:user:123", count); await store.set("enrichment-cache:company:456", data); // Avoid: Generic keys that might collide await store.set("user:123", count); await store.set("cache:456", data); ``` **Use environment variables** when you have multiple versions of the same function (e.g., development and production): ```javascript // Set FUNCTION_ENV as an environment variable: "dev" or "prod" const keyPrefix = process.env.FUNCTION_ENV || "dev"; await store.set(`${keyPrefix}:rate-limit:${userId}`, count); // Results in "dev:rate-limit:123" or "prod:rate-limit:123" ``` # Code Examples ### Basic Filter: Drop Events Without User IDs ```javascript export default async function(event, context) { // Filter out any events that don't have a userId if (!event.userId) { context.log.debug(`Dropped event without userId: ${event.event}`); return "drop"; } return event; } ``` ### Allowlist Filter: Only Forward Specific Events ```javascript export default async function(event, context) { // Define which events should be forwarded const allowedEvents = [ "Order Completed", "Product Viewed", "Cart Updated" ]; if (!allowedEvents.includes(event.event)) { context.log.debug(`Dropped disallowed event: ${event.event}`); return "drop"; } return event; } ``` ### External API Enrichment ```javascript export default async function(event, context) { // Enrich user data with information from an external API // Uses environment variables for secure credential management try { const userId = event.userId; if (!userId) { return event; // Skip enrichment if no userId } // Access environment variables via context.props // These are configured in the Chord CDP UI for each function const apiKey = process.env.API_KEY; const apiBaseUrl = process.env.API_BASE_URL; if (!apiKey) { context.log.warn('API_KEY not configured, skipping enrichment'); return event; } const response = await context.fetch( `${apiBaseUrl}/users/${userId}`, { headers: { 'Authorization': `Bearer ${apiKey}`, 'Content-Type': 'application/json' } } ); if (response.ok) { const userData = await response.json(); // Add enriched data to event properties event.properties.lifetimeValue = userData.ltv; context.log.info(`Enriched user ${userId} with external data`); } else { context.log.warn(`API returned ${response.status}: ${response.statusText}`); } } catch (error) { context.log.error(`Failed to enrich event: ${error.message}`); // Continue processing even if enrichment fails } return event; } ``` ## Support For questions or assistance with CDP Functions, please contact [help@chord.co](mailto\:help@chord.co). [title] Nosto CAPI [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ Nosto is an onsite personalization engine: it learns from what shoppers browse and buy, then renders product recommendations into your pages. This destination sends that behaviour to Nosto server-side, over Nosto's GraphQL API — unaffected by ad blockers, and able to report an order even when checkout happens on a domain your storefront does not control. # Getting Started You need a Nosto **Apps token**, created in Nosto under **Settings > Authentication Tokens**. The token is scoped to one Nosto account. If you also use the [Nosto Tag](#) destination, the token must come from the **same account** as the Account ID configured there — that is what lets both write to a single visitor session instead of two. # Connecting to the Nosto CDP Destination 1. In Chord, add the **Nosto** destination. 2. Enter your **API Token**. 3. Connect it to your back-end site. Read the deduplication note below before connecting it alongside the Nosto Tag. # Using Alongside the Nosto Tag Destination The [Nosto Tag](#) destination does the same job in the browser, and also renders Nosto's recommendations. The two are designed to run together: the tag establishes Nosto's visitor session, Chord forwards that session identifier, and this destination updates **the same** session rather than creating a second one. Browsing, cart and identity updates are safe to send from both — writing the same cart twice leaves one cart. **Orders are the exception. Do not report them from both.** Nosto publishes no deduplication rule for order submission — no dedup key, and no documented behaviour when the same order arrives twice — so running both destinations reports each order twice. Choose one surface for orders. This one is the more reliable of the two; the tag is the more like-for-like if you are replacing an existing Nosto installation. **Without the tag**, this destination still reports orders, identifying the customer by your own customer reference. It cannot contribute browsing behaviour, because there is no browser session for it to attach to. # Deduplication Chord sends your order's own reference as the order `ref`, so that is the value to deduplicate against if another system also sends orders to Nosto. Nosto does not document its behaviour on a repeat submission, so treat "send each order once" as the rule. # Event Mapping | Chord event | Nosto mutation | | ------------------------------------------------------ | ------------------------------------------------------------ | | `Page Viewed` (home page) | Session update — front page view | | `Page Viewed` (any other page) | Not sent — the specific view event covers it | | `Product Viewed` | Session update — product view | | `Product List Viewed` | Session update — category view | | `Products Searched` | Session update — search | | `Cart Viewed` | Session update — cart page view | | `Product Added`, `Product Removed`, `Checkout Started` | Session update — cart contents, without counting a page view | | `identify`, `Signed Up`, `Email Captured` | Session update — customer details | | `Order Completed` | Order placement, with line items | | `Order Refunded` | Order status update | **One view is recorded per navigation.** Your storefront fires `Page Viewed` *and* a specific event like `Product Viewed` on the same page load, and recording both would report every product page to Nosto twice. The specific event records the view; the generic `Page Viewed` carries nothing else Nosto can store, so no call is made at all. The home page is the exception — it has no specific event of its own, so there `Page Viewed` records the front-page view. This matches the Nosto Tag destination exactly, so running both does not reintroduce the double count for views. Browsing and cart events need the visitor's Nosto session, so they are only sent when the Nosto Tag is also running and has established one. Orders do not. # Order Values Line items send the product ID, variant ID, name, unit price, quantity and currency. Values are sent as decimal amounts in the order's own currency — a $22.43 line is sent as `22.43`, not in cents. Currency is sent when your event carries one and omitted otherwise, so Nosto applies your account's default rather than Chord guessing. Order status and payment provider are likewise sent only when your event includes them. # Identity Nosto receives email address, first and last name, and your customer reference **in plaintext**, deliberately. Nosto resolves a shopper to a stored profile and addresses them by name in the experiences it renders, so unlike an advertising API it accepts no hashed identifier — hashing would break the product rather than protect it. If your security review needs to know exactly what is transmitted, that is the list. Marketing permission is sent only when your event carries one; Chord assumes no default. # Gotchas **Refunds are this destination's job.** Nosto exposes order-status transitions only through its GraphQL API, so the Nosto Tag cannot report them. If refunds matter to your reporting, this destination is the only way to send them. **Emptying a cart does not clear it in Nosto.** Chord's `Product Removed` carries the removed line, not the cart that remains, so Chord cannot distinguish "the cart is now empty" from "this event had no products". Rather than risk clearing real carts, Nosto's cart is left alone in that case and updates on the next cart-bearing event. **Nosto's event set is fixed.** There is no arbitrary custom event. Chord events with no Nosto equivalent are not sent, and the reason is recorded in the destination's logs. **Sessions expire after 30 minutes** of inactivity. An event arriving after that has no live session to update; orders are unaffected, since they identify the customer directly. **Consent gating applies.** Nosto's session cookie is only set after consent, so before a visitor consents there is no session for this destination to update. Orders identified by customer reference are unaffected. **Updated 1 September 2026** [title] Reddit Conversions API [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ **Reddit Conversions API** is Reddit's server-side conversion endpoint. This destination sends events to Reddit from Chord's servers rather than the browser, so measurement is unaffected by ad blockers and browser tracking restrictions. For browser-side tracking and click-ID capture, see the [Reddit Pixel](#) destination. This destination uses **Conversions API v3**. # Getting Started You will need: - **Pixel ID** — the identifier for your Reddit pixel, found in the Reddit Ads dashboard under **Events Manager**. It starts with `t2_`. Use the same Pixel ID as your Reddit Pixel destination. - **Conversion Token** — generate it in the Reddit Ads dashboard under **Events Manager > Conversions API**. Treat it as a secret. # Connecting to the Reddit 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 **Reddit Conversions API** from the destination catalog. 5. Enter the destination name, your **Pixel ID**, and your **Conversion Token**. 6. Optionally enter a **Test ID** to route events to Reddit's test view instead of production reporting. 7. Click **"Create"** to connect. # Using Alongside the Reddit Pixel Destination Reddit recommends running the pixel and the Conversions API together, and this destination is built for that. The pixel supplies browser context and the Reddit click ID; the Conversions API reports conversions that never reach the browser or are blocked there. **Configure both destinations with the same Pixel ID.** Chord sends each event's unique message ID as the deduplication key on both surfaces, and Reddit deduplicates on the combination of that key and the event name. Running both does **not** double-count conversions, and no extra configuration is required. # Deduplication Every event this destination sends carries Chord's unique message ID for that event in `metadata.conversion_id`. The [Reddit Pixel](#) destination sends the same value in its `conversionId` field, which is what lets the two run together safely. This matters if you send events to Reddit from anywhere else as well — your own pixel, another tool, or a platform app. Reddit deduplicates on the combination of the conversion ID and the event name, so to deduplicate against Chord's events you must send the **same conversion ID** for the same underlying action. If you cannot, expect Reddit to count those conversions twice. # Event Mapping | Chord Event | Reddit Event | | --------------------------- | ----------------- | | `page` | `PAGE_VISIT` | | `Product Viewed` | `VIEW_CONTENT` | | `Products Searched` | `SEARCH` | | `Product Added` | `ADD_TO_CART` | | `Product Added to Wishlist` | `ADD_TO_WISHLIST` | | `Order Completed` | `PURCHASE` | | `Email Captured` | `LEAD` | | `Signed Up` | `SIGN_UP` | Event types other than `page` and `track` — `identify`, `group`, `screen` — are not sent. Reddit has no equivalent endpoint for them; identity travels on the events themselves. # Identity and Matching Every event carries whatever identifiers are available, which is what determines how much of your Reddit spend can be attributed. Reddit requires at least one. | Identifier | Source | Sent as | | --------------------- | -------------------------------------------------------------------------- | -------------------------------------------------- | | Email | Event traits or properties | SHA-256 hash | | Customer ID | `userId` | SHA-256 hash | | Phone number | Event traits or properties | SHA-256 hash, normalized to E.164 | | IP address | Request IP | SHA-256 hash | | User agent | Event context | Plain text | | Reddit click ID | `rdt_cid` from the landing-page URL, or an `rdt_cid` / `click_id` property | Plain text | | Mobile advertising ID | Device context | SHA-256 hash, sent as `aaid` or `idfa` by platform | All personal data is hashed before it leaves Chord. Values that carry no matching signal — `n/a`, `unknown`, `null`, phone numbers that are too short or all one digit — are dropped rather than hashed, because a hash of a placeholder becomes a permanent false match. **The Reddit click ID is the strongest signal.** It is set on the landing-page URL when someone clicks a Reddit ad, and the [Reddit Pixel](#) destination stores it in first-party storage for up to 30 days. Running the pixel alongside this destination therefore improves server-side attribution as well. # Purchase Events `Order Completed` sends Reddit's `PURCHASE` event with the order value, currency, item count, and a product list carrying each line item's ID, name, category, quantity, and unit price. Currency values are sent as decimal amounts — `149.50` means $149.50. # Limited Data Use Reddit supports Limited Data Use (LDU) for privacy-restricted regions. Chord forwards it only when the storefront explicitly asks for it, by including `modes: ["LDU"]` on the event — optionally with a `country` and `region`. LDU is never inferred, because applying it silently would restrict processing for every event. # Test Mode Setting a **Test ID** attributes events to that Reddit test instead of production reporting, so an integration can be verified without polluting campaign data. Leave it empty for live traffic. Test mode is a per-destination setting, so use a separate destination for testing rather than switching one back and forth. # Click Attribution Reddit appends its click identifier, `rdt_cid`, to the ad's landing-page URL. It appears there and nowhere else — a visitor who lands on `/product?rdt_cid=...` and buys three pages later has no click id in the URL by the time the purchase happens. Chord persists the value when the landing page is tracked and attaches it to every later event in the session, so a conversion reported minutes or days after the click still carries the click id Reddit needs to attribute it. The stored value lasts 30 days and is cleared after a completed order. Nothing is required of you for this to work beyond tracking the landing page. If the **ClickID** row in Reddit's match key coverage reads 0%, the usual explanation is simply that the traffic did not come from a Reddit ad — organic and direct visits have no click id to capture. # Gotchas **Revenue metadata is only sent on revenue events.** Reddit validates event metadata per event type, marks value, currency and item count as applying to revenue-related events only, and reports anything else as "Unsupported metadata" in Events Manager. `Product Viewed` is not a revenue event, so Chord sends product details and the deduplication ID but no value, currency or item count. This matches the [Reddit Pixel](#) destination exactly — the two surfaces have to agree, or the same conversion reports differently depending on which one Reddit kept. **Reddit's event set is fixed.** Reddit recognizes only the eight standard events in the mapping table above. Chord events with no Reddit equivalent — `Checkout Started`, `Product Removed`, `Order Refunded` — are not sent, and the reason is recorded in the destination's logs. Reddit does support a `CUSTOM` event type, but a custom event is discarded unless its name is registered in your Reddit account first, so Chord does not send one. This matches the Reddit Pixel destination's behaviour: what the pixel skips, the Conversions API skips too. **Refunds are not reported.** Reddit has no refund event on either surface. **Search terms are not sent.** Reddit's `SEARCH` event takes no query parameter. **Failures are retried only when retrying can help.** Rate limits and Reddit server errors are retried. A rejected payload or a bad credential is not — those would fail identically on a second attempt, and the error is recorded in the destination's logs instead. **Both credentials are required.** A missing Pixel ID or Conversion Token fails the event with an explicit error rather than silently dropping it. **Updated 1 September 2026** [title] Reddit Pixel [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ **Reddit Pixel** is Reddit's browser tag for measuring conversions from Reddit Ads campaigns. This destination loads the Reddit pixel in the browser and forwards page views, product, and purchase events to Reddit. For server-side measurement that is unaffected by ad blockers, see the [Reddit Conversions API](#) destination. # Getting Started This is a device-mode destination. The Reddit pixel is loaded automatically — no manual script installation is required. You will need: - **Pixel ID** — the identifier for your Reddit pixel, found in the Reddit Ads dashboard under **Events Manager**. It starts with `t2_`. # Connecting to the Reddit 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 **Reddit Pixel** from the destination catalog. 5. Enter the destination name and your **Pixel ID**. 6. Optionally enable **Advanced Matching** (see below). 7. Click **"Create"** to connect. # Using Alongside the Reddit Conversions API Destination The Reddit Pixel and the [Reddit Conversions API](#) destination are designed to run together, and Reddit recommends it — the pixel captures browser context and the click ID, while the server-side destination reports conversions that ad blockers or browser tracking restrictions would otherwise hide. **Both destinations must be configured with the same Pixel ID.** Chord sends each event's unique message ID as the deduplication key on both surfaces, and Reddit deduplicates on the combination of that key and the event name. Running both therefore does **not** double-count conversions, and no extra configuration is needed to make deduplication work. # Deduplication Every event this destination sends carries Chord's unique message ID for that event in Reddit's `conversionId` field. The [Reddit Conversions API](#) destination sends the same value as `conversion_id`, which is what lets the two run together safely. This matters if you send events to Reddit from anywhere else as well — your own pixel, another tool, or a platform app. Reddit deduplicates on the combination of the conversion ID and the event name, so to deduplicate against Chord's events you must send the **same conversion ID** for the same underlying action. If you cannot, expect Reddit to count those conversions twice. # Event Mapping | Chord Event | Reddit Event | | --------------------------- | ------------------------------------------------------- | | `page` | `PageVisit` | | `identify` | *no event — identity is sent through Advanced Matching* | | `Product Viewed` | `ViewContent` | | `Products Searched` | `Search` | | `Product Added` | `AddToCart` | | `Product Added to Wishlist` | `AddToWishlist` | | `Order Completed` | `Purchase` | | `Email Captured` | `Lead` | | `Signed Up` | `SignUp` | # Purchase Events `Order Completed` fires Reddit's `Purchase` event with the order total, currency, item count, transaction ID, and a product list carrying each line item's ID, name, and category. Two cases are skipped rather than sent, and both log a message to the browser console: - **An order with no products.** An empty cart produces a conversion with no basket, which distorts Reddit's reporting. - **An order with no order ID.** Reddit deduplicates purchases by transaction ID, so a purchase without one risks being counted more than once. Currency values are sent as decimal amounts — `49.99` means $49.99, not 49.99 cents. # Advanced Matching Advanced Matching sends identifiers Reddit calls **match keys** to improve the share of conversions Reddit can attribute. It is off by default; enable it in the destination configuration. Chord sends every match key Reddit accepts, and each one is SHA-256 hashed in the browser before it leaves the page — Reddit treats a pre-hashed value identically to one it hashes itself: | Match key | Source | | --------------- | ----------------------------------------- | | `email` | the visitor's email address | | `phoneNumber` | the visitor's phone number, in E.164 form | | `externalId` | your customer ID for the visitor | | `aaid` / `idfa` | mobile advertising ID, when present | Nothing is sent in plaintext. Reddit's own setup wizard shows a snippet that passes these in plaintext; that snippet is for a manual pixel install and does not apply here. :::BlockQuote **Do not also paste Reddit's install snippet into your site.** Reddit's setup wizard offers a ` ``` **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] Pinterest Conversions [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ The **Pinterest Conversions API** destination sends event data directly from Chord CDP to Pinterest's servers, bypassing the browser entirely. Unlike the [Pinterest Tag (device mode)](#), server-side events are immune to ad blockers and browser tracking restrictions, providing more reliable signal for campaign measurement, audience building, and automated bidding optimization. Use this destination alongside the [Pinterest Tag destination](#) for maximum data coverage. Pinterest deduplicates events using the `event_id` field. # Getting Started This is a cloud-mode destination. You will need: - **Ad Account ID** — your Pinterest Ads account ID, found in your Pinterest Ads dashboard URL or under **Ads > Account settings**. - **Conversion Token** — a conversion access token generated in **Pinterest Ads > Conversions**. See [Pinterest's documentation](https://developers.pinterest.com/docs/conversions/conversions/) for instructions on creating a server-side access token. - **App Name** — a name identifying your application or integration (e.g. `"my-storefront"`). Used as the `partner_name` in the event payload. # Connecting to the Pinterest 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 **Pinterest Conversions API** from the destination catalog. 5. Enter the destination name, **Ad Account ID**, **Conversion Token**, and **App Name**. 6. Click **"Create"** to connect. # Event Mapping | Chord Event | Pinterest Event | | --------------------------- | ----------------------------- | | `page` | `PageVisit` | | `Order Completed` | `checkout` | | `Checkout Started` | `InitiateCheckout` | | `Product Added` | `AddToCart` | | `Product Viewed` | `ViewContent` | | `Products Searched` | `Search` | | `Product Added to Wishlist` | `AddToWishlist` | | *(other track events)* | Chord event name passed as-is | Page, track, and screen events are forwarded. Identify events are ignored. # User Data (All Events) All personally identifiable information (PII) is sent to Pinterest as raw values; Pinterest's API hashes them server-side according to its data processing requirements. Fields that cannot be resolved are omitted. | Pinterest Field | Chord Source (Priority Order) | Notes | | ------------------- | --------------------------------------------------------------------- | ------------------------------------------ | | `email` | `properties.email` > `context.traits.email` | Array; omitted if not present | | `phone` | `properties.phone` > `context.traits.phone` | Array; omitted if not present | | `first_name` | `properties.first_name` > `context.traits.firstName` | Array; omitted if not present | | `last_name` | `properties.last_name` > `context.traits.lastName` | Array; omitted if not present | | `city` | `context.traits.address.city` > `properties.address.city` | Array; omitted if not present | | `state` | `context.traits.address.state` > `properties.address.state` | Array; omitted if not present | | `zip` | `context.traits.address.postalCode` > `properties.address.postalCode` | Array; omitted if not present | | `country` | `context.traits.address.country` > `properties.address.country` | Array; omitted if not present | | `external_id` | `userId` > `anonymousId` | Array; omitted if neither is present | | `client_ip_address` | `context.ip` | Not hashed | | `client_user_agent` | `context.userAgent` | Defaults to `"Mozilla/5.0"` if not present | | `click_id` | `epik` query parameter from `context.page.url` | Pinterest click ID | | `partner_id` | `properties.partner_id` > `context.campaign.name` | | # Custom Data (Track Events) Track events include a `custom_data` block with the following structured schema fields. Additionally, any `properties.*` destination mappings configured in Hub that target non-schema fields are forwarded as custom properties alongside the structured fields. | Pinterest Field | Chord Source (Priority Order) | Notes | | --------------- | ---------------------------------------------------------------------------------------------------------- | ---------------------------------------- | | `value` | `properties.value` > `properties.price` > `properties.revenue` > sum of `price × quantity` across products | String; omitted if not resolvable | | `currency` | `properties.currency` > `properties.meta.i18n.currency` | Defaults to `"USD"` | | `order_id` | `properties.order_id` > `properties.cart_id` | | | `content_ids` | Product IDs from `properties.products[]` or `properties.product_id` / `properties.sku` | Falls back to page title for page events | | `contents` | Array of `{ id, item_price, quantity, item_name, item_category, item_brand }` per product | Omitted if no products | | `num_items` | `properties.quantity` > sum of quantities across `properties.products[]` | | | `search_string` | `properties.query` > `properties.search_term` | Relevant for Products Searched | # Custom Property Forwarding Configure destination mappings in Hub with `properties.*` destination paths to forward additional event properties into `custom_data`. 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, `custom_data.loyalty_tier` will appear in the payload sent to Pinterest. **What is excluded:** - Schema fields already handled by the destination transform (e.g. `currency`, `value`, `order_id`, `content_ids`, `contents`) — these flow through the structured transform - PII fields (`email`, `phone`, `first_name`, `last_name`) — these are handled via `user_data` 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. # Testing and Validation After connecting the destination: 1. Trigger events from your storefront or use the **Live Events** tab in the Chord CDP to confirm events are flowing. 2. In Pinterest Ads Manager, navigate to **Ads > Conversions** and open your conversion tag to verify events are received. 3. Confirm revenue values and order counts align with your expectations. 4. If you are running both the Conversions API and the Pinterest Tag, ensure `event_id` values match across both to prevent duplicate counting. Chord CDP handles this automatically by using `messageId` as the `event_id` for both destinations. *** **Updated 27 May 2026** [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. ## 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] Error handling & retries [path] Chord CDP/ As events flow through Chord they are processed (enrichment, transformation, filtering) and then delivered to one or more destinations. Either stage can fail. This document explains how Chord classifies those failures, which ones are retried, how retries are scheduled, and what happens when a connection's property mappings are misconfigured. ## Delivery Model Chord provides **at-least-once delivery**. When a recoverable failure occurs, the affected event is re-queued and delivered again later. Because of this, an event may occasionally be delivered more than once — see [Deduplication](https://deduplication.md) for how destinations should handle duplicates using `messageId`. Each event is delivered independently per **connection** (a source → destination pairing). A failure delivering an event to one destination does not affect delivery of the same event to any other destination. ## Recoverable vs Unrecoverable Errors Chord divides failures into two categories, and only one of them is retried. **Recoverable (transient) errors** are failures that are expected to resolve on their own without any change to configuration or code — for example a destination API returning a `5xx`, a request timing out, a rate-limit response, or a temporary network blip. These errors are **retried**. **Unrecoverable errors** are failures that retrying cannot fix — for example malformed event data a destination will never accept, an authentication failure, or a logic error in a custom function. These are **not retried**. Depending on the failure the event is dropped, recorded as failed, or (for a function that throws a standard error) still delivered — and in each case a notification is sent to any configured connection monitors. The table below summarizes how the most common outcomes are handled. | Outcome | Source | Retried | Result | | ---------------------------------------------------------------------- | ------------------------------------ | ------- | --------------------------------------------------------------- | | Transient delivery failure (`5xx`, timeout, rate limit, network error) | Destination | **Yes** | Re-queued with backoff; delivered once the destination recovers | | Recoverable failure raised by a function | UDF (`RetryError`) | **Yes** | Re-queued with backoff | | Permanent destination rejection (`4xx`, auth/validation failure) | Destination | No | Not delivered to that destination, monitors notified | | Unrecoverable failure raised by a function | UDF (`NoRetryError`) | No | Event dropped, monitors notified | | Unexpected logic error | UDF (standard `Error`) | No | Event still delivered, monitors notified | | Intentional filtering | UDF (`return null` / `false` / `[]`) | No | Event silently dropped, no notification | Functions (UDFs) can deliberately raise either a retryable or a non-retryable error to control this behavior. That mechanism is documented in detail in [Functions](#); this document covers only how the pipeline acts on those signals. ## How Retries are Scheduled When an event fails with a recoverable error, Chord does not retry it immediately. Instead it computes a future **retry time** and re-queues the message on a dedicated retry topic. The message waits there until its scheduled retry time passes, at which point it is reprocessed. Retries use **exponential backoff** so that a struggling destination is given progressively more time to recover between attempts: - A fixed number of retry attempts is made per event (default: **3**). - The delay before each attempt grows exponentially from a base interval (default base: **10 minutes**), so successive attempts are delayed roughly **10 minutes**, then **\~1.7 hours**, then **\~16.7 hours**. - Every delay is capped at a maximum (default: **24 hours**), so no single retry is ever scheduled further out than the cap. These values are operational defaults and may be tuned per environment. On a retry, processing resumes at the stage that failed rather than from the beginning. A failure during destination delivery re-attempts delivery only, without re-running the function pipeline. A failure inside the function pipeline re-runs the whole function pipeline together with destination delivery. This avoids duplicating the side effects of stages that already completed successfully. ## The Dead Letter Queue Retries are not infinite. Once an event has exhausted its retry attempts and still cannot be delivered, it is moved to a **dead-letter queue** rather than being retried forever or silently discarded. This keeps the live pipeline healthy while preserving the failed event for inspection and potential manual replay. A move to the dead-letter queue is recorded in the pipeline metrics and surfaced to any configured connection monitors, so persistent delivery failures are visible rather than hidden. ## Property Mapping Problems A misconfigured connection property mapping does **not** stop the event. Mappings are applied per connection, so a bad mapping affects only that one destination — every other destination still receives the event as normal. **A source path that does not exist on the event** is the most common misconfiguration: you map `properties.loyalty_tier` but the event never carries it, or it only carries it on some events. When that happens, that single mapping is skipped, a warning is logged, and the event is delivered with all of its other mappings applied. The destination simply does not receive that one field. Where the warning appears depends on how the destination runs: - **Browser (device-mode) destinations** — pixels and tags that run in the visitor's browser — log a warning to the **browser console**. It names the destination and the mapping, and ends with `source path "" does not exist on event — mapping skipped`. These warnings do not appear in Live Events. - **Server-side (cloud-mode) destinations** log the same warning to **Live Events** in the Chord Console. A warning on every event usually means the mapping is too broad rather than wrong. Use the mapping's **Event Scope** to restrict it to the event types and names that actually carry the property, and the warnings stop. **Static-value mappings never warn**, because there is no source property to look up. In the rare case that a mapping fails in an unexpected way rather than simply missing its source, the error is logged and that event is not sent to that destination. Other destinations are unaffected. If you see this, contact Chord support — it indicates a problem on our side, not in your configuration. ## Monitoring Failures Recoverable and unrecoverable errors alike are recorded in the pipeline's metrics and, where connection monitors are configured, generate notifications. You can inspect individual failures and the errors that caused them in **Live Events** within the Chord Console. Intentional filtering (an event dropped by a function returning a falsy value) is recorded as `dropped` and does **not** generate a notification — it is treated as normal pipeline behavior, not a failure. ## Related Topics - [Functions](#) — how custom functions raise retryable and non-retryable errors - [Deduplication](https://deduplication.md) — handling the duplicate deliveries that at-least-once retries can produce [title] Server Events [path] Chord Event Tracking/ [title] Using with Shopify [path] Chord Event Tracking/ [title] @chordcommerce/analytics [path] Chord Event Tracking/Release Notes/ ## v1.23.1 (2026-08-10) **Bug Fixes** - dedupe `Consent Preferences Updated` event so it fires on actual consent transitions instead of once per page load ## v1.23.0 (2026-06-25) **Features** - add support for Cookiebot as a consent management platform ## v1.22.2 (2026-05-04) **Bug Fixes** - `identify/track/page` now await in-flight `reset()` before sending, eliminating identity-bleed when events fire immediately after logout ## v1.22.1 (2026-03-20) **Bug Fixes** - allow postMessages from null-origin sandboxed iframes in web pixel listener ## v1.22.0 (2026-03-20) **Features** - unified custom web pixel ## v1.21.3 (2026-03-06) **Bug Fixes** - prevent duplicate CDP script injection in React StrictMode ## v1.21.2 (2026-02-19) **Bug Fixes** - race condition in OneTrust consent adapter ## v1.21.1 (2026-02-11) *(internal release tooling — no user-facing changes)* ## v1.21.0 (2026-01-20) **Features** - add `sessionStorage` persistence for consent event queue (events queued during consent wait now survive instance recreation) ## v1.20.0 (2026-01-12) **Features** - add `trackOrderCompleted` convenience method ## v1.19.0 (2025-12-08) **Features** - consent: stamp events with fresh consent via CDP configure - consent: add g`etCategories` / `isConsentReady` to all adapters - consent: add OneTrust API utilities module **Bug Fixes** - add awaits to fix race conditions - stamp initial consent event after CDP fully initialized ## v1.18.1 (2025-10-10) **Bug Fixes** - retry** OneTrust **consent handler setup ## v1.18.0 (2025-09-23) **Features** - create a CommonJS build for sites on older Node/Webpack ## v1.17.0 (2025-09-04) **Features** - add `addSourceMiddleware` (Segment parity) ## v1.16.1 (2025-08-28) **Bug Fixes** - track method waits for CDP ready ## v1.16.0 (2025-08-21) **Features** - add configurable `awaitConsentTimeout` option ## v1.15.0 (2025-07-31) **Features** - add Segment support **Bug Fixes** - guard Chord CDP `dontSend` configuration when API not yet available ## v1.14.1 (2025-07-23) **Bug Fixes** - normalize `cdpDomain` to avoid double slashes in URLs ## v1.14.0 (2025-07-21) **Features** - add Consent Preferences Updated event **Bug Fixes** - prevent duplicate consent processing on page load ## v1.13.0 (2025-06-30) **Features** - add optional `props` argument to `page` method ## v1.12.2 (2025-05-30) **Bug Fixes** - `awaitConsent` option ## v1.12.1 (2025-05-27) **Bug Fixes** - add `isResetting` - Chord CDP called first - resolve event only after both CDP promises resolved - increase speed of consent management check ## v1.12.0 (2025-05-01) **Features** - add support for OneTrust CMP ## v1.11.0 (2025-04-23) **Bug Fixes** - wait before setting initial consent **Features** - add support for Ketch CMP ## v1.10.0 (2025-04-10) **Features** - add built-in consent managment support, Shopify ## v1.9.1 (2025-04-09) **Bug Fixes** - support Chord CDP and Segment in parallel ## v1.9.0 (2025-03-24) **Features** - add Chord CDP support ## v1.8.0 (2024-03-21) **Features** - add `trackNavigationClicked` - add `trackCheckoutStepCompleted` - add `trackCheckoutStepViewed` - add `trackVariantClicked` - add `trackLoginStarted` - add `trackSubscriptionCancelled` - add `trackPaymentInfoEntered` ## v1.7.0 (2024-03-07) **Features** - add type parameter to ChordAnalytics ## v1.6.0 (2024-03-05) **Features** - publish to npm registry ## v1.5.1 (2024-02-14) **Bug Fixes** - address linter errors and warnings - remove no longer needed eslint disableds ## v1.5.0 (2024-01-19) **Features** - add cdp and logger methods to ChordAnalytics - add comments for cdp() and logger() ## v1.4.0 (2024-01-18) **Features** - add enableLogging option ## v1.3.0 (2024-01-17) **Features** - add page method to ChordAnalytics ## v1.2.0 (2024-01-16) **Features** - support function to return the CDP instance ## v1.1.1 (2023-12-07) **Bug Fixes** - clean up input types ## v1.1.0 (2023-12-07) **Features** - set up eslint config for core package ## v1.0.3 (2023-12-05) **Bug Fixes** - semantic release config file format - update package for node compatibility ## v1.0.2 (2023-12-05) **Bug Fixes** - add missing dep to liquid package - update module type to support imports ## v1.0.1 (2023-12-05) **Bug Fixes** - remove zero price fallback - strip null values from arrays - update tracking plan to latest ## v1.0.0 (2023-12-05) **Features** - rename package - initial release [title] Guides [path] Chord Event Tracking/ [title] Setting Up a Shopify Custom App for Chord [path] Chord Event Tracking/Getting started/Shopify/Shopify installation/ # Creating Custom Shopify Apps on behalf of Chord ## Step 1: Create the App 1. Go to your **Shopify Dev Dashboard** ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/UBqX2VPeJ5Z3PspeluUt0_image.png" size="100" isUploading="false" width="1733" height="843" darkWidth="1733" darkHeight="843" showCaption="false" indent="1"} 2. In the navigation menu, click **Apps** → **Create app** 3. Under **Start from Dev Dashboard**, enter the app name ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/N2wa1hloX4iBZemk_B6Vw_image.png" size="100" isUploading="false" width="3834" height="1918" darkWidth="3834" darkHeight="1918" showCaption="false" indent="1"} 4. Click **Create** ## Step 2: Configure Access Scopes 1. Leave the form settings as-is 2. In the **API Access** section, select/paste the relevant **API Access scopes** 3. Click **Release** ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/NxLNPOeP7RaGdyts_g9Tx_image.png" size="100" isUploading="false" width="1657" height="817" darkWidth="1657" darkHeight="817" showCaption="false" indent="1"} ## Step 3: Install the App 1. On the app **Home** page, click **Install app** ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/b67mutDG3fVg7eQMu7RSq_image.png" size="100" isUploading="false" width="1638" height="811" darkWidth="1638" darkHeight="811" showCaption="false" indent="1"} 2. Select your store 3. Review the application scopes 4. Click **Install** ## Step 4: Store/Share Credentials You can find the client credentials by visiting the app **Settings** page. You will need both the “Client ID” and “Secret”. ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/1GTjZ7kLoJB22RoodwGcI_image.png) You will also need your store URL in the following format: your-store-url.myshopify.com. You can find your-store-url by visiting the store Admin page. The Admin landing page URL will look similar to the following: :::BlockQuote https\://admin.shopify.com/store/\{\{your-store-url}}/orders ::: The portion of the URL after store, is your store name that you will want to provide. ## Step 5: Share your client credentials with Chord team Your app's ***Client ID & Secret*** along with your Store's ***Shopify subdomain*** needs to be shared with the Chord team. These values will be used to facilitate either Data Ingestion or the support of server side webhook events. Please reach out to ***help\@chord.co*** if there are any questions. [title] Order Completed [path] Chord Event Tracking/Server Events/Track/ This event is triggered when a customer completes a purchase. # 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 Completed", "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 Completed", "properties": {} "meta": {}, "userId": "123456", "anonymousId": "7a76b270-c318-4477-b1e1-33eac94dbd1e" } ``` [title] Klaviyo [path] Chord Event Tracking/Guides/Integrations/ Klaviyo has a [Segment destination](https://segment.com/docs/connections/destinations/catalog/klaviyo/) that can be connected to both website front-end and server Chord Segment sources. We recommend connecting both sources for maximum reliability. When the destination is enabled, Klaviyo will receive customer information and tracking events from your Segment sources after an email address has been captured for the user. A customer typically provides their phone number or email address either by logging in, entering this information in some other field like a newsletter signup, or placing an order. ## Configuration We recommend the following Klaviyo destination configuration, available under **Other Settings** in the Segment destination settings: ![Klaviyo settings](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/PUwtk7dPj75uz3g8S20_e_untitled-3.png) ### Confirm Optin This flag determines whether someone is sent an email with a confirmation link before they are added to the list. Defaults to true (checked). This should only be set to false or unchecked if you have already received explicit permission from that person to add them to this list. ### Enforce Email as Primary Identifier This option is enabled by default to ensure duplicate profiles are not being created inside of Klaviyo. This option ensures email addresses are treated as the unique primary identifier. If this setting is enabled, Klaviyo will ignore any events that don’t have a customer email address attached. This means Chord tracking events received before an email address is known will be ignored. ### Fallback on Anonymous ID This option should always be “Off”. ### Send Placed Order Events as Order Completed This option should always be “On”. ## Order Completed When Chord sends Segment an `Order Completed` event, Segment sends Klaviyo a `Placed Order` event and a `Ordered Product` event for each item listed in the `properties.products` array. Segment also attaches `customer_properties` with the `userId` set as `$id` for each of those Klaviyo events. ## Implementation Notes To add a customer to a Klaviyo list from a server event, pass a second argument to the `identify` method that looks like this: ```javascript { integrations: { Klaviyo: { listId: "ABCDEF", // confirmOptin: false, // more details here: https://segment.com/docs/connections/destinations/catalog/klaviyo/#confirm-opt-in }, }, } ``` [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] Facebook Pixel [path] Chord Event Tracking/Guides/Integrations/ ## Overview Chord’s Facebook integration works best when both browser and server events are sent to Facebook. We recommend configuring two Facebook Segment destinations: 1. A [Facebook Pixel destination](https://segment.com/docs/connections/destinations/catalog/facebook-pixel/), connected to your website front-end Segment source. 2. A [Facebook Conversions API destination](https://segment.com/docs/connections/destinations/catalog/actions-facebook-conversions-api/), connected to your server Segment source. Alternatively, you can connect a second Facebook Conversions API destination to your website front-end Segment source and omit the Facebook Pixel destination. This setup results in pre-checkout events (ex. `Product Added`) and one post-checkout event, `Order Completed`, being sent to Facebook from your website front end source, and post-checkout events (ex. `Order Completed`) being sent to Facebook from your server source. `Order Completed` is duplicated from both sources for maximum reliability. For Chord tracking events, Facebook [handles duplicate events](https://developers.facebook.com/docs/marketing-api/conversions-api/deduplicate-pixel-and-server-events) by comparing the event name and the `external_id` property, which should be set to Segment’s`userId` (or `anonymousId` if not present). See instructions below for how to configure your Facebook Pixel and Conversions API destinations to use `userId`/`anonymousId` as Facebook’s `external_id`. ## Facebook Pixel destination This destination loads the Facebook Pixel Javascript library in the browser and sends Chord events to it client-side, without hitting Segment’s servers first. First, configure the Facebook Pixel destination [according to Segment documentation](https://segment.com/docs/connections/destinations/catalog/facebook-pixel/#getting-started). ### Event Mapping To map Chord Segment events to standard Facebook events, create the mappings in the destination setting “Map Your Events to Standard FB Events”. The following mapping is recommended as a minimum: - `Order Completed`, which Segment sends to Facebook as `Purchase` - `Product Added`, which Segment sends as `AddToCart` - `Product List Viewed`, which Segment sends as `ViewContent` - `Product Viewed`, which Segment sends as `ViewContent` - `Products Searched`, which Segment sends as `Search` - `Checkout Started`, which Segment sends as `InitiateCheckout` In Segment, this should look like: ![Segment event mapping](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/jW3aAxbCcNouZxbINGWHu_untitled.png "Segment Event Mapping") You can add additional mappings here if you need them, too. ### External IDs Enable two settings under **Advanced Settings**: “Enable Advanced Matching” and “Use User ID or Anonymous ID as External ID”. Enabling both of these sends the Segment `userId` (or `anonymousId` if not present) as the `external_id` to Facebook, which improves Facebook’s ability to connect Segment events from various sources to the same user. ### Implementation Checklist - [ ] Connect Facebook Pixel destination to website front-end source - [ ] Create event mappings in the destination setting “Map Your Events to Standard FB Events” - [ ] Enable the destination settings “Enable Advanced Matching” and “Use User ID or Anonymous ID as External ID” ## Facebook Conversions API destination The [Facebook Conversions API destination](https://segment.com/docs/connections/destinations/catalog/actions-facebook-conversions-api/) sends Chord events to Facebook via Facebook’s Conversions API. Chord events are sent to Segment, and then Segment sends the events to Facebook. This destination can be connected to either browser or server event sources. If connected to a browser event source, the Facebook Pixel destination should not be used for that same browser event source, because that will gather duplicate data. First, configure the Facebook Conversions API destination [according to Segment documentation](https://segment.com/docs/connections/destinations/catalog/actions-facebook-conversions-api/#getting-started). Next, the Facebook Conversions API destination requires you to map Chord Segment events to Facebook standard events. **Using with Chord’s server source** At a minimum, we recommend mapping the following Chord server source events to Facebook standard events: - `Order Completed`, which Segment sends as `Purchase` When you’re creating event mappings, you’re required to provide a value for the **Action Source** property in the **Select mappings** section. Select “SYSTEM GENERATED” as the action source. See [Facebook’s documentation](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/server-event) of the `action_source` property for descriptions of the different options. **Using with Chord’s website front-end source** At a minimum, we recommend mapping the following Chord website front-end events to Facebook standard events: - `Order Completed`, which Segment sends as `Purchase` - `Product Added`, which Segment sends as `AddToCart` - `Product List Viewed`, which Segment sends as `ViewContent` - `Product Viewed`, which Segment sends as `ViewContent` - `Products Searched`, which Segment sends as `Search` - `Checkout Started`, which Segment sends as `InitiateCheckout` When you’re creating event mappings, you’re required to provide a value for the **Action Source** property in the **Select mappings** section. Select “WEBSITE” as the action source. See [Facebook’s documentation](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/server-event) of the `action_source` property for descriptions of the different options. ![Select "WEBSITE" as the action source](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/8LH1VFtngvKWITxV_-cN-_untitled-1.png) ### External IDs By default, the Conversions API destination correctly maps Facebook’s `external_id` property to Segment’s `userId` (or `anonymousId` if not present). Don’t make changes to this configuration. ![Map to externalID](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/JXY5Vu5KJNttCMBnpiNJQ_untitled-2.png) ### Implementation Checklist - [ ] Connect the Facebook Conversions API destination to the server source - [ ] If not using the Facebook Pixel destination, connect the Facebook Conversions API destination to the website front-end source as well - [ ] Create event mappings, following the minimum recommended mapping listed above, and remember to specify the correct “Action Source” property for each mapping [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] Attentive Mobile [path] Chord Event Tracking/Guides/Integrations/ ## Overview Attentive Mobile has a [Segment destination](https://segment.com/docs/connections/destinations/catalog/attentive-mobile/) that can be connected to both website front-end and server Chord Segment sources. We recommend connecting both sources for maximum reliability. ## Sending data to Attentive Once connected and configured [according to Segment’s documentation](https://segment.com/docs/connections/destinations/catalog/attentive-mobile/), Attentive will automatically receive customer data from Chord events that will be added as attributes to the Attentive subscriber. These attributes are used to target Attentive subscribers in the [Attentive Segments product](https://help.attentivemobile.com/hc/en-us/categories/360004558392-Subscriber-segments). Attentive will also receive all Chord tracking events and save them as custom events to the Attentive subscriber. These events are usable in both the [Attentive Segments product](https://help.attentivemobile.com/hc/en-us/categories/360004558392-Subscriber-segments) and the [Attentive Journeys product](https://help.attentivemobile.com/hc/en-us/categories/6084285157396). Tracking events sent before a customer has been identified by a phone number or email address will be ignored. A customer typically provides their phone number or email address either by logging in, entering this information in some other field like a newsletter signup, or placing an order. [title] Consent Management [path] Chord Event Tracking/Using with Shopify/Web Pixel/ :::hint{type="warning"} **Map every destination to a consent category. **Chord applies consent filtering only to destinations that have at least one consent category. A destination with no consent category receives all events, including from visitors who declined consent. After adding a CDP destination, assign its consent categories before turning it on. ::: The Chord web pixel integrates native consent management features from Shopify and the CDP so you can accurately comply with your customer's privacy preferences. On your Shopify storefront, you will typically gather data processing permissions from your customers using Shopify's [Customer Privacy API](https://shopify.dev/docs/api/customer-privacy). It's available on both Shopify themes and headless Shopify sites. When you install the Chord web pixel on your Shopify storefront, you can configure the customer privacy settings for the web pixel. These settings control whether the Chord tracking pixel will capture data and send it to the CDP. For example, to require customer consent for data collection for marketing and analytics purposes before any data is captured, you can adjust your web pixel settings to load the web pixel only after receiving this consent. The Chord web pixel also includes granular information about the customer's data processing permissions on every tracking event that goes to the CDP. In the CDP, you can configure how these customer permissions should impact data delivery to CDP destinations. For example, if you use a destination where data could be considered as being sold, you can configure consent in the CDP to ensure that tracking events from customers who have consented to their data being sold are the only ones sent to this specific CDP destination. Please reach out to a local attorney who may be better equipped to answer any specific questions you may have concerning data privacy laws and applicability. ## Customer privacy settings for web pixel You can configure the customer privacy setting of the Chord web pixel on your store. This will determine when the pixel code actually executes and can collect tracking data. ### Configuring in Shopify To configure the customer privacy setting for the web pixel, go to **Settings** > **Customer events** in your Shopify store admin and select the Chord web pixel. Review the customer privacy settings. There are two main categories: - **Permission**: Controls whether the pixel collects data in cases where customer permission has been granted. - **Data sale**: Controls whether the pixel collects data in cases where the customer has opted out of their data being sold. Configure the settings and select **Save**. The settings will take effect immediately, so make sure you are gathering customer preferences with the Customer Privacy API before you do so. For more details about the functionality, see Shopify's documentation on [pixel customer privacy settings](https://help.shopify.com/en/manual/promoting-marketing/pixels/custom-pixels/manage#customer-privacy) and an overview of Shopify [customer privacy](https://help.shopify.com/en/manual/privacy-and-security/privacy/customer-privacy-settings/privacy-settings). ## CDP consent management The Chord web pixel automatically adds customer privacy preferences from Shopify's Customer Privacy API to a consent object on all CDP events. This allows you to enforce the customer's privacy preferences when routing events to CDP destinations. It won't have an impact until you configure consent management in the CDP. *Please ask the Chord team for assistance in doing so.* [title] Consent management [path] Chord Event Tracking/ # Overview The Chord CDP enforces user consent before forwarding events to destinations. When a destination has consent requirements configured, no event is sent to that destination — and no destination script is loaded in the browser — until the user has granted the required consent categories. This document explains how consent categories are defined, how the CDP receives consent decisions from the browser, and how those decisions gate event delivery in both device mode and cloud mode. # The Consent Lifecycle in Brief What happens, in order, on a visit to a storefront with a CMP configured: 1. **Before the CMP publishes a consent state, events are held in a browser queue and nothing reaches Chord.** This covers the time the CMP script takes to load — not the time the visitor spends reading the banner. 2. **Once the CMP publishes a state, the queue flushes.** That first state is the jurisdiction default the CMP is configured with: typically permissive under an opt-out model (common in the US) and denied-except-strictly-necessary under an opt-in model (common in the UK and EU). 3. **From that point on, every event is sent to Chord — whether consent was granted or denied.** A denial is recorded on the event; it does not stop collection. Enforcement happens per destination, not in the browser's decision to send. 4. **Consent is read fresh and stamped immediately before each send**, including when a queued event is replayed. A queued event can therefore carry the visitor's actual choice rather than the default it was queued under. 5. **When the visitor changes their choice, the new preferences apply to every later event**, and Chord Pixel fires a `Consent Preferences Updated` event. That event bypasses consent requirements and reaches every destination, so a destination can act on a revocation. 6. **Chord decides delivery per destination.** A destination receives an event only if every category in its **Consent Requirements** is `true`. A destination with an empty requirements list receives everything. 7. **Nothing is retroactive.** Events already delivered under a permissive default stay delivered. 8. **All of the above requires the **`consent`** option to be set** when Chord Pixel is initialized. Without it there is no queue and no consent stamp — events are collected and forwarded with no consent data at all. ## What a Full Denial Does — and Doesn't — Stop If a visitor declines every category in the CMP banner, **the browser still sends every event to Chord.** Collection does not stop. Each event carries `categoryPreferences` with every category set to `false`, and Chord records it like any other event. What stops is delivery: - A destination with one or more **Consent Requirements** receives nothing. In device mode, its third-party script is never loaded. - A destination with an **empty** Consent Requirements list still receives every event. A full denial does not gate it — configuring the requirements list is what makes consent enforceable for that destination. - `Consent Preferences Updated` still reaches every destination, so a platform can act on the revocation. If you need collection itself to stop, your storefront has to stop calling Chord Pixel. No setting in the Console turns a denial into non-collection. # Consent Categories Consent categories are the units of permission that users grant or deny. Before configuring consent requirements on a destination, you must define your categories in the Chord Console under **CDP → Consent Categories**. Each category has: - **Name** — human-readable label shown in the Console - **External ID** — the category identifier used by your consent management platform (CMP). Must match exactly what your CMP emits. - **Description** — optional explanation of what data collection this category covers - **Active** — whether this category is currently enforced The **External ID** is the field that connects CDP categories to your CMP. For example, OneTrust uses category codes like `C0002` for analytics cookies — the External ID for your analytics category must be set to `C0002` for the mapping to work. # Consent Management Platform (CMP) Integration Chord Pixel bridges your CMP and the CDP. It reads the user's current consent state from the CMP, stamps each outgoing event with the user's category preferences, and updates those stamps dynamically as consent changes. ## Support CMPs - **OneTrust** — detected via `window.OneTrust`; categories read from `window.OnetrustActiveGroups` - **Cookiebot** — detected via `window.Cookiebot` - **Ketch** — detected via `window.ketch` and `window.ketchConsent` - **Shopify** — detected via `window.Shopify.customerPrivacy` - **Segment** — detected via `window.segmentConsent` The CMP integration is configured when you initialize Chord Pixel: ```javascript const chord = new ChordAnalytics({ consent: 'onetrust', // 'cookiebot' | 'ketch' | 'onetrust' | 'shopify' | 'segment' awaitConsent: true, cdpDomain: process.env.CHORD_DOMAIN, cdpWriteKey: process.env.CHORD_WRITE_KEY, // rest of your configuration }) ``` If the `consent` option is not set, Chord Pixel does not read your CMP at all. Events are still collected and forwarded, but they carry no consent information — see **Events with no consent data** below. ## Consent Readiness and Event Queueing When a CMP is configured, Chord Pixel checks whether that CMP has published a consent state before sending each event. If it has not, **the event is held in a queue** rather than being dropped. Chord Pixel polls every 100 ms and flushes the queue as soon as the state is available. This queue covers the short window while the CMP script is still loading — not the period before the visitor answers the banner. Most CMPs publish a default state as soon as they load, so events typically resume immediately, stamped with those defaults rather than with the visitor's eventual choice. OneTrust, for example, is considered ready once `window.OnetrustActiveGroups` is populated, which happens before any banner interaction. The queue is held in memory and is not capped. It is also mirrored to `sessionStorage` so it survives navigation within the session; that mirror keeps only the most recent 50 events and is skipped entirely if it would exceed 100 KB. There is no time-based expiry — queued events are delivered whenever the CMP state becomes available. Setting `awaitConsent: true` additionally defers consent setup until the CMP itself has loaded. Chord Pixel polls every 50 ms and gives up after 60 seconds; override that with `awaitConsentTimeout` (in milliseconds). If the CMP never loads within that window, consent setup is abandoned and subsequent events are sent without a consent stamp. ## Consent Stamping On every event, Chord Pixel fetches the user's current category preferences directly from the CMP (no caching). The result is added to the event under `context.consent.categoryPreferences`: ```json { "context": { "consent": { "categoryPreferences": { "C0001": true, "C0002": true, "C0003": false } } } } ``` The keys in `categoryPreferences` are the **External IDs** of your consent categories. Values are `true` (granted) or `false` (denied). Note that denying consent does not stop Chord Pixel from sending the event. The event is still collected, stamped with the denial, and forwarded to the CDP, where consent requirements decide which destinations receive it. This preserves a record of the decision and lets enforcement stay configurable. # Configuring Consent Requirements on a Destination Open the destination's configuration in the Chord Console and add one or more consent categories to the **Consent Requirements** list. Each required category must resolve to `true` in the event's `categoryPreferences` for the event to be forwarded. A destination with an empty **Consent Requirements** list receives every event that passes host and event filters, whatever the user's consent preferences say. Stamping consent on an event does nothing by itself — the categories have to be configured here as well. ## Requiring all consent categories Consent requirements use **AND logic**: if you specify two categories, both must be granted. There is no OR operator — if you want a destination to fire when any one of several categories is granted, create separate destination configurations. ## Events with no consent data: the `Send Null Consent Events` option By default, if an event arrives with no `categoryPreferences` at all, the destination treats consent as implicitly granted and forwards the event. This preserves backward compatibility for destinations that predate consent configuration. Events arrive with no consent data in two common situations: - A storefront that has no CMP configured in Chord Pixel. - Server-to-server sources such as Shopify webhooks. Consent APIs are browser APIs, so a webhook carries no consent signal. To block those events, disable **Send Null Consent Events** on the destination configuration. With this option disabled, any event that lacks `categoryPreferences` is dropped, regardless of what consent requirements are set: - No `categoryPreferences`, option enabled (the default) — event forwarded - No `categoryPreferences`, option disabled — event dropped - `categoryPreferences` present — consent requirements are evaluated, and this option is not consulted The option is a property of the destination, so it applies to every source connected to that destination. It cannot be scoped to one source. If you need to block server-side events while continuing to accept browser events that carry no consent data, configure a separate destination for the server-side traffic. # How Consent Gates Event Delivery ## Device-mode Device mode destinations run as browser plugins — the destination's third-party script (e.g., a pixel or SDK) loads in the visitor's browser, and events are sent directly from the browser to the destination's servers. Before any device mode plugin processes an event, the CDP SDK calls `applyFilters()`, which: 1. Checks host and event-type filters (unrelated to consent) 2. If the destination has `consentRequirements`, evaluates them against the event's `categoryPreferences` 3. Returns `false` if any required category is not granted When `applyFilters()` returns `false`, the plugin's handler is never invoked. The event is silently dropped for that destination. **Third-party scripts are loaded lazily.** A device mode destination's script is only loaded after the first event passes all filters, including consent. If the user never grants the required consent, the destination script is never injected into the page. ## Cloud-mode Cloud mode destinations receive events server-side via the Chord CDP pipeline. The same consent logic runs in the pipeline before the event is dispatched to the destination function. Events that do not satisfy the consent requirements are dropped before the destination function executes. # The `Consent Preferences Updated` Event When a user changes their consent choices, Chord Pixel fires a `Consent Preferences Updated` event. This event **always bypasses consent requirements** and is forwarded to all destinations regardless of current category preferences. This allows destinations to register the updated preferences — for example, to update suppression lists or unsubscribe records in a marketing platform — even when the user has revoked consent for that destination's category. # Example: SFMC Collect.js Salesforce Marketing Cloud Collect.js is a device mode destination. If it is configured with a consent requirement of `C0002` (analytics cookies): 1. A visitor arrives and has not yet interacted with the consent banner — no `categoryPreferences` in events. If **Send Null Consent Events** is enabled (the default), events flow to SFMC. If it is disabled, events are held until consent is given. 2. The visitor dismisses the banner and denies analytics cookies — `categoryPreferences: { "C0002": false }`. All subsequent events for SFMC are dropped. The Collect.js script is not loaded if it hasn't been already. 3. The visitor accepts analytics cookies — `categoryPreferences: { "C0002": true }`. Events resume flowing to SFMC. If the Collect.js script was never loaded, it is loaded now on the next passing event. 4. The visitor later revokes consent. A `Consent Preferences Updated` event is fired and delivered to SFMC regardless of the new consent state. All subsequent track and page events are again blocked. # Troubleshooting **Events are not reaching a destination even though consent was granted.** Check that the External IDs configured on your consent categories in the Chord Console exactly match the category codes your CMP emits. A mismatch (e.g., `c0002` vs `C0002`) causes every event to fail the consent check. **Events are flowing to a destination even though the user denied consent.** Verify that the destination has consent requirements configured. A destination with no consent requirements set will receive all events that pass host and event filters, regardless of the user's consent preferences. **Events arrive with no consent object at all.** Confirm that the `consent` option is set when Chord Pixel is initialized. Without it, Chord Pixel never reads your CMP, and every event is treated as having no consent data. **The destination script loads before consent is given.** This indicates that at least one event is passing the consent filter before consent is granted — most likely because `categoryPreferences` is absent and **Send Null Consent Events** is enabled. Disable that option on the destination if you require explicit opt-in before the script loads. *** **Updated 22 September 2026** [title] Server Event Tracking [path] Chord Event Tracking/Using with Shopify/ When installed on your storefront, Chord typically sends tracking events to the CDP from two sources: - Your website front-end, either using the Chord Shopify web pixel or `@chordcommerce/analytics`, and - Chord's server events service, which sends tracking events from a Shopify custom source function in your CDP workspace in response to webhook triggers from Shopify. When Chord provisions your CDP workspace, it will include Chord's Shopify webhook source. This code listens for webhook events from Shopify and transforms them into CDP events. ## Requirements Locate Chord's webhook source in your CDP workspace, named "Shopify Webhooks." Chord typically creates this webhook source as part of your CDP workspace provisioning. You'll need to update the settings of this source during the **Create an Admin API Key** step, and you'll need the webhook URL of this source during the **Create Webhook Subscriptions** step. If you can't find the source or aren't sure which one it is, please contact Chord. ## Installation There are two steps to configuring server events: creating an Admin API key and adding it to the CDP source; and subscribing the CDP source to Shopify webhook events. ### Creating an Admin API key Chord's CDP source requires an admin API key with the `read_orders` scope to retrieve order details from Shopify. To generate this admin API key, we recommend creating a custom Shopify app in your Shopify account for Chord, and using the Admin API access token from this custom app. This makes it easy to manage access. Create a new custom app in your Shopify admin by navigating to **Settings** > **Apps and sales channels** > **Develop apps** > **Create an app**. Once the app is created, click **Configure Admin API Scopes**. Choose `read_orders` only and hit **Save.** On the **Overview** tab, you should see a prompt to **Install to get your access token**. Click **Install app**. Now you should see this: ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/-HtEyo6KDxhwiwkkLSvnM_untitled-5.png) Copy the Admin API access token. In your CDP workspace, navigate to your Chord webhook source and view the settings under **Settings** > **Connection**. Enter the Admin API access token you just created in the **Access Token** or **accessToken** settings field, and **Save Changes**. ### Creating Webhook Subscriptions In your CDP workspace, navigate to your Chord webhook source and find the webhook URL for the source under the **Configure your webhook** heading. Now you'll create webhook subscriptions in Shopify. You can create webhook subscriptions either via the [Shopify admin](https://help.shopify.com/en/manual/orders/notifications/webhooks) or the [Admin API](https://shopify.dev/docs/api/admin-rest/2024-01/resources/webhook#post-webhooks). You can use the Admin API access token you created for Chord to create the subscription via the Admin API. Create a subscription for each server event you'd like Chord to send to the CDP. Each subscription will have the same address, which is the URL you copied from your CDP source. Please see the [Webhook Event Payloads](docId\:yPb3xYAkaZuf0hBmfTW7S) page for the list of supported topics. Shopify's webhook testing doesn't include a payload that matches a real webhook payload, so we recommend completing a test transaction in your Shopify store to verify that server events are flowing as expected. You can view the CDP events in the **Debugger** tab of the Shopify webhook source in your CDP workspace. ## Storefront configuration To associate server events and front-end storefront events with the same session, 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. See [Unifying Data Across Sources](docId\:FYmI5G8eWB-YYpyh-GU4o) for more details. [title] OMS Schema [path] Chord Event Tracking/Getting started/Custom storefront/ # Overview This document outlines the complete data schema requirements for integrating custom OMS data into the Chord analytics pipeline. Each section represents a different data entity with its required and optional fields. Use this specification to map your source OMS data to Chord’s standardized schema for seamless analytics integration. # Data Provision Guidelines **Field Requirements:** - **Required Fields**: Must be provided with valid, non-null data. - **Recommended**: Optional, but strongly encouraged. *Omitting these fields reduces accuracy in Chord's data science features, including customer matching and predictive modeling.* - **Optional Fields**: Can be omitted or provided as null. **Data Format Standards:** - **Timestamps**: ISO 8601 format (YYYY-MM-DDTHH\:MM\:SSZ) - **Numeric values**: Standard decimal notation without currency symbols - **Boolean values**: Lowercase `true` or `false` - **String values**: UTF-8 encoded, properly escaped for special characters - **NULL values**: Use NULL (not empty strings) for missing data in non-string fields ### Data Delivery Requirements **File Format**: - Parquet - One file per data entity (orders, customers, products, etc.) ### Special Considerations 1. **Variant Logic**: If your system doesn’t have separate variant IDs, use product\_id for both id and variant\_id in the variants table 2. **Location Data**: If not tracking physical locations, leave as NULL 3. **Vendor Values**: Provide your company/brand name as the vendor for products and line items, or leave as NULL if not applicable # Data Transformation Requirements ### Status Mappings Required **Order Fulfillment Status:** Map your `order_status` values to one of: - `fulfilled` - `restocked` - `partial` **Product Status:** Map your `item_status` values to one of: - `active` - `archived` - `draft` **Transaction Kind:** Map your `payment_type` values to one of: - `capture` - `void` - `refund` - `sale` - `change` - `authorization` **Transaction Status:** Map your `response_code `values to one of: - `success` - `pending` - `failure` - `error` **Financial Status (if available):** - `authorized` - `partially_paid` - `paid` - `refunded` - `pending` - `partially_refunded` - `voided` ### Data Transformation Guidance **Calculated Fields** (if not available directly in your system): 1. **shipping\_address\_name**: Concatenate shipping\_first\_name + space + shipping\_last\_name 2. **billing\_address\_name**: Concatenate billing\_first\_name + space + billing\_last\_name 3. **taxes\_included**: Derive from your tax calculation logic (whether product prices include tax) 4. **cancelled\_at**: If order status indicates cancellation, provide the cancellation timestamp **Address Normalization**: - Validate country codes against ISO 3166-1 alpha-2 standard - Validate state/province codes where applicable ### Default Values for Optional Fields When optional fields are not available in your system: - **String fields**: NULL - **Numeric fields**: NULL where appropriate - **Boolean fields**: false as default - **Timestamp fields**: NULL - **Array fields**: Empty array \[] - **JSONB fields**: NULL ### Note on Fulfillment Data If your system tracks fulfillment and shipment data, Sections 10-12 (Fulfillments, Fulfillment Order Lines, Fulfillment Orders) are **optional.** ## 1. Orders Data Schema **Purpose**: Order records represent transaction information, including customer details, pricing, and addresses. **Primary Key**: id ### Core Order Fields | Field Name | Data Type | Description | | --------------- | --------- | ----------------------------------------------- | | id | STRING | \*Unique order identifier (required) | | location\_id | STRING | Location/store identifier (optional) | | customer\_id | STRING | \*Reference to customer record (required) | | name | STRING | \*Order number displayed to customer (required) | | email | STRING | \*Customer email address (required) | | source\_name | STRING | Order origination source | | is\_test | BOOLEAN | Test order flag | | app | STRING | Application that created the order | | tags | JSONB | Order tags | | discount\_codes | JSONB | Applied discount codes | ### Financial Fields | Field Name | Data Type | Description | | ------------------------- | --------- | ----------------------------------------------------------- | | total\_price | NUMERIC | \*Complete order total including all charges (required) | | total\_line\_items\_price | NUMERIC | \*Sum of all line items before adjustments (required) | | total\_tax | NUMERIC | Total tax amount (optional, 0 if no tax) | | total\_shipping\_price | NUMERIC | Total shipping charges (optional, 0 if free shipping) | | total\_discounts | NUMERIC | Total discount amount applied (optional, 0 if no discounts) | | processing\_method | STRING | Payment processing method | | financial\_status | STRING | Payment status (authorized, paid, refunded, etc.) | | taxes\_included | BOOLEAN | Whether taxes are included in subtotal | ### Order Status Fields | Field Name | Data Type | Description | | ------------------- | --------- | -------------------------------------------------- | | fulfillment\_status | STRING | Fulfillment status (fulfilled, restocked, partial) | | cancel\_reason | STRING | Reason for cancellation if applicable | ### Shipping Address Fields | Field Name | Data Type | Description | | --------------------------------- | --------- | ---------------------- | | shipping\_address\_name | STRING | Full recipient name | | shipping\_address\_first\_name | STRING | Recipient first name | | shipping\_address\_last\_name | STRING | Recipient last name | | shipping\_address\_company | STRING | Company name | | shipping\_address\_phone | STRING | Contact phone number | | shipping\_address\_address\_1 | STRING | Primary address line | | shipping\_address\_address\_2 | STRING | Secondary address line | | shipping\_address\_city | STRING | City name | | shipping\_address\_province | STRING | State/Province | | shipping\_address\_province\_code | STRING | Province/state code | | shipping\_address\_zip | STRING | Postal code | | shipping\_address\_country | STRING | Country name | | shipping\_address\_country\_code | STRING | ISO country code | | shipping\_address\_latitude | STRING | GPS latitude | | shipping\_address\_longitude | STRING | GPS longitude | ### Billing Address Fields | Field Name | Data Type | Description | | -------------------------------- | --------- | ------------------------- | | billing\_address\_name | STRING | Full billing name | | billing\_address\_first\_name | STRING | Billing first name | | billing\_address\_last\_name | STRING | Billing last name | | billing\_address\_company | STRING | Company name | | billing\_address\_phone | STRING | Billing phone number | | billing\_address\_address\_1 | STRING | Primary billing address | | billing\_address\_address\_2 | STRING | Secondary billing address | | billing\_address\_city | STRING | Billing city | | billing\_address\_province | STRING | Billing state/province | | billing\_address\_province\_code | STRING | Province/state code | | billing\_address\_zip | STRING | Billing postal code | | billing\_address\_country | STRING | Billing country | | billing\_address\_country\_code | STRING | Billing ISO country code | | billing\_address\_latitude | STRING | GPS latitude | | billing\_address\_longitude | STRING | GPS longitude | ### Order Timestamps | Field Name | Data Type | Description | | ------------- | --------- | ---------------------------------------- | | created\_at | TIMESTAMP | \*Order creation timestamp (required) | | processed\_at | TIMESTAMP | Order processing timestamp (optional) | | updated\_at | TIMESTAMP | \*Last modification timestamp (required) | | closed\_at | TIMESTAMP | Order completion timestamp | | cancelled\_at | TIMESTAMP | Cancellation timestamp (if cancelled) | ## 2. Customers Data Schema **Purpose**: Customer records contain account and contact information. **Primary Key**: id | Field Name | Data Type | Description | | -------------------- | --------- | ------------------------------------------------------------------------------------------------------------------- | | id | STRING | \*Unique customer identifier (required) | | email | STRING | \*Customer email address (required) | | first\_name | STRING | Customer first name
*(Recommended - improves accuracy of Chord AI identity matching and predictive modeling)* | | last\_name | STRING | Customer last name
*(Recommended - improves accuracy of Chord AI identity matching and predictive modeling)* | | phone | STRING | Customer phone number | | type | STRING | Customer account type | | has\_verified\_email | BOOLEAN | Email verification status | | created\_at | TIMESTAMP | Account creation date | | updated\_at | TIMESTAMP | Last account update | ## 3. Products Data Schema **Purpose**: Product catalog information for all sellable items. **Primary Key**: id | Field Name | Data Type | Description | | ---------------- | --------- | -------------------------------------- | | id | STRING | \*Unique product identifier (required) | | title | STRING | \*Product display name (required) | | handle | STRING | URL handle/slug | | product\_type | STRING | Product category | | vendor | STRING | Product vendor name | | published\_scope | STRING | Publication scope | | status | STRING | Product status (active/archived/draft) | | created\_at | TIMESTAMP | Product creation date | | updated\_at | TIMESTAMP | Last product update | ## 4. Product Variants Data Schema **Purpose**: Product variant details including pricing and inventory attributes. **Primary Key**: id **Note**: If your system doesn’t use variants, create one variant per product with the same ID. | Field Name | Data Type | Description | | ----------- | --------- | -------------------------------------------------------------------------- | | id | STRING | \*Variant identifier (required; use Product ID if no separate variant IDs) | | product\_id | STRING | \*Parent product reference (required) | | title | STRING | \*Variant display name (required) | | sku | STRING | Stock keeping unit (optional but recommended) | | barcode | STRING | Product barcode | | price | NUMERIC | Retail price | | grams | NUMERIC | Weight in grams | | option\_1 | STRING | First variant option | | option\_2 | STRING | Second variant option | | option\_3 | STRING | Third variant option | | is\_taxable | BOOLEAN | Taxability flag | | created\_at | TIMESTAMP | Variant creation date | | updated\_at | TIMESTAMP | Last variant update | ## 5. Order Line Items Data Schema **Purpose**: Individual items within each order. **Primary Key**: id | Field Name | Data Type | Description | | ------------------------------ | --------- | ---------------------------------------- | | id | STRING | \*Unique line item identifier (required) | | order\_id | STRING | \*Parent order reference (required) | | product\_id | STRING | \*Product reference (required) | | variant\_id | STRING | \*Product variant reference (required) | | subscription\_id | STRING | \*Parent subscription reference | | title | STRING | \*Line item product name (required) | | variant\_title | STRING | Line item variant name | | name | STRING | Full line item name with quantity | | sku | STRING | Product SKU | | vendor | STRING | Product vendor | | grams | NUMERIC | Total weight in grams | | price | NUMERIC | \*Unit price (required) | | quantity | INTEGER | \*Quantity ordered (required) | | is\_taxable | BOOLEAN | Item taxability | | variant\_inventory\_management | STRING | Inventory management method | | properties | ARRAY | Custom properties | | promo\_total | NUMERIC | Line-level discount amount | ## 6. Locations Data Schema (If Available) **Purpose**: Location records for stores, warehouses, or other fulfillment locations. **Primary Key**: id **Note**: This entity is optional. If you don’t track physical locations, you can omit this table. | Field Name | Data Type | Description | | ----------- | --------- | -------------------------- | | id | STRING | Unique location identifier | | name | STRING | Location name | | is\_active | BOOLEAN | Active status | | created\_at | TIMESTAMP | Location creation date | | updated\_at | TIMESTAMP | Last location update | ## 7. Payment Transactions Data Schema **Purpose**: Financial transactions associated with orders. **Primary Key**: id | Field Name | Data Type | Description | | ----------- | --------- | ---------------------------------------------------- | | id | STRING | \*Transaction identifier (required) | | order\_id | STRING | \*Parent order reference (required) | | refund\_id | STRING | Associated refund ID if applicable | | amount | NUMERIC | \*Transaction amount (required) | | kind | STRING | \*Transaction type (required; see status mappings) | | status | STRING | \*Transaction status (required; see status mappings) | | is\_test | BOOLEAN | Test transaction flag | | created\_at | TIMESTAMP | Transaction timestamp | ## 8. Order Line Refunds Data Schema **Purpose**: Refunded line items from orders. **Primary Key**: id **Note**: Only provide if your system tracks refunds. | Field Name | Data Type | Description | | --------------- | --------- | ---------------------------- | | id | STRING | Refund line identifier | | refund\_id | STRING | Parent refund reference | | order\_line\_id | STRING | Original line item reference | | quantity | INTEGER | Quantity refunded | | subtotal | NUMERIC | Refund amount | ## 9. Return Line Items Data Schema **Purpose**: Returned items from orders. **Primary Key**: id **Note**: Only provide if your system tracks returns separately from refunds. | Field Name | Data Type | Description | | -------------------- | --------- | ---------------------------- | | id | STRING | Return line identifier | | return\_id | STRING | Parent return reference | | order\_line\_id | STRING | Original line item reference | | quantity | INTEGER | Total quantity returned | | refundable\_quantity | INTEGER | Quantity eligible for refund | | refunded\_quantity | INTEGER | Quantity already refunded | | return\_reason | STRING | Return reason category | | return\_reason\_note | STRING | Detailed return explanation | ## 10. Fulfillments Data Schema (If Available) Fulfillment records for order shipments. | Field Name | Data Type | Description | | ----------------- | --------- | ----------------------------- | | id | STRING | Unique fulfillment identifier | | order\_id | STRING | Parent order reference | | status | STRING | Fulfillment status | | tracking\_company | STRING | Shipping carrier name | | shipment\_status | STRING | Current shipment status | | tracking\_numbers | ARRAY | Array of tracking numbers | | tracking\_urls | ARRAY | Array of tracking URLs | | created\_at | TIMESTAMP | Fulfillment creation date | | updated\_at | TIMESTAMP | Last fulfillment update | ## 11. Fulfillment Order Lines Data Schema (If Available) Links between fulfillments and order line items. | Field Name | Data Type | Description | | --------------- | --------- | ---------------------------------- | | id | STRING | Unique fulfillment line identifier | | fulfillment\_id | STRING | Parent fulfillment reference | | order\_line\_id | STRING | Order line item reference | ## 12. Fulfillment Orders Data Schema (If Available) Fulfillment order groupings for location-based fulfillment. | Field Name | Data Type | Description | | --------------- | --------- | ---------------------------- | | id | STRING | Fulfillment order identifier | | order\_id | STRING | Parent order reference | | status | STRING | Fulfillment order status | | request\_status | STRING | Fulfillment request status | | fulfill\_at | TIMESTAMP | Scheduled fulfillment date | | created\_at | TIMESTAMP | Creation timestamp | | updated\_at | TIMESTAMP | Last update timestamp | ## 13. Subscription History Data Schema **Purpose**: Recurring subscription or auto-ship orders. **Primary Key**: id **Note**: Only provide if your system supports recurring subscriptions or auto-ship functionality. | Field Name | Data Type | Description | | -------------------------------------------- | --------- | ------------------------------------------------------------------------------------------------- | | id | STRING | Unique ID per subscription (e.g., subscription\_id + \_ + line\_item\_no if tracking per product) | | customer\_id | STRING | Reference to customer record | | address\_id | STRING | Reference to customer shipping address (if applicable) | | oms\_product\_id | STRING | Product identifier | | oms\_variant\_id | STRING | Variant identifier (use product\_id if no variants) | | created\_at | TIMESTAMP | When subscription was created | | price | NUMERIC | Price per delivery | | quantity | INTEGER | Units delivered each cycle | | status | STRING | Status (active, paused, cancelled, etc.) | | subscription\_interval\_frequency | NUMERIC | How often deliveries occur (e.g., 1, 2, 3) | | order\_interval\_unit | STRING | Time unit (day, week, month, year) | | order\_interval\_frequency | NUMERIC | Same as subscription\_interval\_frequency | | order\_day\_of\_month | NUMERIC | Specific day for monthly subscriptions (1-31) | | order\_day\_of\_week | NUMERIC | Specific day for weekly subscriptions (0-6) | | expire\_after\_specific\_number\_of\_periods | NUMERIC | Number of deliveries before auto-cancellation (if applicable) | | updated\_at | TIMESTAMP | When subscription was last updated | | next\_run\_scheduled\_at | TIMESTAMP | Scheduled date for next order | | cancelled\_at | TIMESTAMP | When subscription was cancelled (if applicable) | | cancellation\_reason | STRING | Reason for cancellation | | cancellation\_reason\_comments | STRING | Additional cancellation details | [title] Enabling the read_users Scope for Chord on Shopify Plus [path] Chord Event Tracking/Using with Shopify/Untitled/ :::hint{type="info"} *For Shopify Plus brands only* ::: # What we need We need your Shopify store to enable one additional permission, called `read_users`, for the Chord app installed on your store. Enabling this requires a request to Shopify Support. This page outlines exactly what to ask for. # Why we need it We're adding new point-of-sale data to your reporting, including which sales associate handled each in-store sale. Pulling that information requires access to Shopify's staff data, which sits behind a restricted permission called `read_users`. Shopify doesn't grant this permission automatically. It's only available to stores on Shopify Plus or Advanced, and Shopify Support has to turn it on manually for each app. If you're on Shopify Plus, you qualify. The remaining step is asking Shopify to enable it. # How to request it Requests like this tend to move faster when they come directly from a store admin or owner, so we'd like to ask that person to submit it. Here's how: 1. Go to help.shopify.com 2. Click "Chat with a human." 3. Since your store is on Shopify Plus, you should see an option for "Chat with Plus Support." Choose that. 4. Ask them to enable the read\_users scope for this app: `App client ID:`` b76b70aa4ffbb11f602a73eb17a467e9 ` 5. Let them know the reason: you need it to bring in point-of-sale data, such as the sales associate on each order. **Note:** You shouldn't need to give Shopify a detailed technical spec. The scope name and the general use case above should be enough for them to process the request. # What happens next Once Shopify confirms the scope is enabled on your store, let us know. We'll take it from there and finish connecting the point-of-sale data on our end. # Questions? If Shopify asks for anything beyond what's listed here, or if you run into any issues during the chat, reach out and we'll help you work through it. [title] Untitled [path] Chord Event Tracking/Getting started/ [title] Shopify Customer Privacy API [path] Chord Event Tracking/Consent Management/ Shopify's [Customer Privacy API](https://shopify.dev/docs/api/customer-privacy) is available as a Javascript API on Shopify themes. If you have enabled Shopify's default cookie banner or data sales opt-out page, or you have installed a cookie banner or consent management Shopify app, you're likely capturing customer data preferences with the Customer Privacy API. Chord offers a consent management wrapper that retrieves customer data preferences from the Customer Privacy API and adds them to Chord CDP events as the [consent object](https://docs.chord.co/installation). Within Chord CDP, you can map how data preferences should be applied to Chord CDP destinations. Follow these steps to configure consent management with Shopify's Customer Privacy API and Chord CDP: 1. Configure customer privacy in Shopify. 2. Configure consent categories in Chord CDP and map to destinations. 3. Implement Chord's Web Pixel which integrates native consent management features from Shopify and the CDP. ## Configuring Shopify To implement consent management on a Shopify site using the Customer Privacy API, navigate to **Settings > Customer privacy** in your Shopify store admin. You’ll see three available privacy settings. The cookie banner privacy setting **must** be enabled if you’re using Chord's Web Pixel. If it isn’t, the Customer Privacy API is unavailable, and Chord will never send events to Chord CDP for any visitor. Learn more about [Shopify’s customer privacy settings](https://help.shopify.com/en/manual/privacy-and-security/privacy/customer-privacy-settings). The following two privacy settings are recommended by Shopify and should be configured: ### Cookie banner Add a banner to ask visitors for permission to manage their data. You can either enable Shopify’s default cookie banner, or add a custom cookie banner from the Shopify app store. To enable Shopify’s cookie banner, select **Cookie banner** > **Activate cookie banner**, choose regions, and select **Activate**. To use a custom cookie banner, select **Cookie banner** > **More actions** > **Use custom cookie banner**, choose regions, and select **Activate**. ### Data sales opt-out page Allow visitors to define how their data can be shared. To enable Shopify’s data sales opt-out page, select **Data-sales opt-out page**, choose regions, and select **Activate.** ## Configuring Chord CDP Shopify’s Customer Privacy API supports four categories of consent from users: - `analytics`: Customer analytics about how the storefront was used and interactions made on the storefront. By default, this preference is collected by Shopify’s cookie banner as “performance cookies.” - `marketing`: Marketing, attribution and targeted advertising from the merchant. By default, this preference is collected by Shopify’s cookie banner as “marketing cookies.” - `preferences`: Customer preferences such as language, currency, size, and more. By default, this preference is collected by Shopify’s cookie banner as “preference cookies.” - `sale_of_data`: Sharing data with third parties, usually for behavioral advertising. By default, this preference is collected by Shopify’s data sales opt-out page. You can decide how these four categories map to your Chord CDP destinations. Add the four categories below as category mappings in the Chord CDP by navigating to **CDP** > **Consent Categories** > **Create Your First Consent Category**. You can customize the “Category name” for these category mappings, but the “Category ID” must be exactly the values listed below to connect preferences from Shopify to Chord CDP: | Category Name (can be customized) | Category ID | | --------------------------------- | ----------------- | | Performance cookies
| `analytics` | | Marketing cookies | `marketing`
| | Preference cookies | `preferences` | | Sale of data | `sale_of_data` | For each category, choose the mapped destinations. Mapping a destination to a category means that the destination will only receive the Chord CDP event if Shopify’s Customer Privacy API reports that processing is allowed for that category. Once you’ve created and enabled the four categories, you should see this in Chord CDP: ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/rjNjq-Bb3Rotg4XiHKf2R_image.png) ## Installing on your site The [Chord web pixel integrates](https://docs.chord.co/dbKz-consent-management) native consent management features from Shopify and the CDP so you can accurately comply with your customer's privacy preferences. Before the Chord Web Pixel is loaded is loaded, Chord's checks to see if user tracking is allowed at all. The Chord Web Pixel will load and send events to the Chord CDP only if `window.Shopify.customerPrivacy.marketingAllowed()` and `window.Shopify.customerPrivacy.analyticsProcessingAllowed()` both return `true`. This typically means the customer is: - Browsing from a region that does not require a cookie banner, or; - In a region that does require a cookie banner, but has consented to both analytics and marketing cookies. If the Customer Privacy API doesn't allow user tracking, Chord will silently fail and events will not be sent. Next, if the Chord Web Pixel is loaded, a `consent` object is added describing the customer’s consent preferences to each Chord CDP event. Chord CDP will use the consent category mapping we configured earlier in the Chord CDP consent categories configuration along with the destination-level configuration to determine which destinations will receive events based on this `consent` object. The pixel uses the `Allowed` methods of Shopify’s Customer Privacy API to construct the `consent`object and [obtain the values for each category](https://shopify.dev/docs/api/customer-privacy#check-data-processing-permissions): ```jsx { analytics: window.Shopify.customerPrivacy.analyticsProcessingAllowed(), marketing: window.Shopify.customerPrivacy.marketingAllowed(), preferences: window.Shopify.customerPrivacy.preferencesProcessingAllowed(), sale_of_data: window.Shopify.customerPrivacy.saleOfDataAllowed() } ``` ## FAQs **Is Global Privacy Control (GPC) supported?** Chord CDP recognizes the [Global Privacy Control signal](https://globalprivacycontrol.org/) as an opt-out of data sales in regions where opting out is supported. The `sale_of_data` category in the `consent` object will be `false` if the customer has activated the Global Privacy Control signal in their browser and is browsing from a region where opting out of data sales is an option. [title] Introduction [path] Chord Event Tracking/Using with Shopify/ ## Client events Adding Chord tracking to a Shopify storefront differs based on whether it uses a Shopify theme or is "headless". ### 1. Web pixel (all stores) All Shopify stores - Shopify theme or headless - will need to install the [Shopify custom web pixel](docId\:YbZ9CC0qUadUpZfcfvO96). On stores built with a Shopify theme, this will handle all tracking events. On headless stores, this will only handle tracking in checkout. In both cases, the checkout events will work regardless of whether you're on Checkout Extensibility or checkout.liquid. ### 2. Analytics SDK (headless stores only) Headless stores will need to implement the [analytics SDK npm package](docId\:XDo-mGzIP_SQ_feVf6RUI) within the codebase that serves the storefront. :::hint{type="info"} On headless stores, it is important to add both the web pixel and Analytics SDK to accurately track the full conversion journey. ::: ## Server events In addition to the client tracking events from your store, Chord also sends server events to the CDP in response to webhook triggers from Shopify. Currently, Chord's server events include `identify` events and these `track` events: - "Checkout Started" - "Order Completed" - "Order Refunded" - "Order Cancelled" Server events need to be configured for all Shopify sites. The process is the same for headless sites and sites using Shopify themes. For instructions on configuring, see [enabling server events](docId\:q6xVtfkfFiPMHVVI2QcG0). [title] Usage [path] Chord Event Tracking/Using with Shopify/Web Pixel/ The Chord web pixel automatically sends the following events to the CDP: - A `page` event for every page view - An `identify` event when a customer submits contact information during checkout, or logs into their account - The following `track` events: - "Cart Viewed" - "Checkout Started" - "Checkout Step Completed" - "Order Completed" - "Payment Info Entered" - "Product List Viewed" - "Product Added" - "Product Removed" - "Product Viewed" - "Products Searched" You can customize the web pixel code to add additional custom events or event properties. We recommend keeping track of changes you make to the web pixel code, so you can upgrade in the future. ## Adding custom events You may want to add custom events from the [Chord tracking plan](https://docs.chord.co/tracking-plan) to your storefront to track any other events users perform on your store. These custom events will be added to the Chord data warehouse. :::hint{type="warning"} Other CDP destinations (e.g. third party services) do not support sending custom events - they will only respond to events within Chord's tracking plan. ::: **1) Publish custom event from theme** First, from your Shopify theme, publish a custom Shopify event with all the data you'll need to construct the Chord tracking event, using `Shopify.analytics.publish` in 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] The Context object [path] Chord Event Tracking/ # The Context Object 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 and ad click IDs, read from cookies, from the landing page URL, and from vendor SDKs already loaded on the page **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 populated when GeoIP resolution is configured. 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 Identifiers for third-party tracking tools, including ad click IDs. These are what let a destination attribute a conversion back to the ad click, email, or session that caused it. They are also written to the warehouse, so they are available for attribution modelling even when no destination reads them. They come from three places. ### From browser cookies Read on every event from cookies the vendor's own script sets. A field is absent until that script has run — and, where the vendor gates on consent, until the visitor has consented. An absent value is a normal state, not an error. | Field | Type | Cookie | Description | | -------------------- | ------ | -------------- | ---------------------------------------- | | `ga4.clientId` | string | `_ga` | Google Analytics 4 client ID | | `ga4.sessionIds` | any | `_ga_*` | GA4 session IDs, keyed by measurement ID | | `fbc` | string | `_fbc` | Facebook click ID | | `fbp` | string | `_fbp` | Facebook browser ID | | `gcl_aw` | string | `_gcl_aw` | Google Ads click cookie | | `ttclid` | string | `ttclid` | TikTok click ID | | `ttp` | string | `_ttp` | TikTok browser ID | | `epik` | string | `_epik` | Pinterest click ID | | `openai_oppref` | string | `__oppref` | OpenAI Ads click identifier | | `openai_obref` | string | `__obref` | OpenAI Ads browser reference | | `nosto_cid` | string | `2c.cId` | Nosto session identifier | | `amplitudeSessionId` | number | `_amp_session` | Amplitude session ID (Unix ms) | ### From the landing page URL Click identifiers usually appear only on the URL of the page the visitor lands on. The SDK stores each one in the browser and replays it on every later event, so a visitor who lands on an ad and converts several pages later still carries the identifier that earned the conversion. Stored values last 30 days. Most are cleared once an `Order Completed` event has been sent, so one click is not credited to two separate orders. Clearing happens *after* the event is sent, so the order event itself still carries the identifier. | URL parameter | Field | Cleared at purchase | Description | | ------------- | ---------------- | ------------------- | --------------------------------------------------- | | `irclickid` | `irclickid` | Yes | Impact click ID | | `im_ref` | `impact` | Yes | Impact UTT referrer | | `_kx` | `klaviyo_kx` | No | Klaviyo exchange ID, set on links in Klaviyo emails | | `brid` | `meta_brid` | Yes | Meta in-app-browser reference | | `oppref` | `openai_oppref` | Yes | OpenAI Ads click identifier | | `rdt_cid` | `reddit_rdt_cid` | Yes | Reddit Ads click ID | `_kx` is the exception to the clear-at-purchase rule. It identifies a Klaviyo profile rather than crediting a single click, so there is nothing to de-duplicate at purchase, and it is kept for the full 30 days. UTM parameters are captured by the same mechanism but surface under `context.campaign` rather than here. ### From a vendor SDK on the page Read directly from the vendor's SDK when it is already loaded, which avoids a race with cookie writes during SDK startup. | Field | Type | Description | | -------------------- | ------ | ------------------------------------------------------------ | | `amplitudeSessionId` | number | Amplitude session ID, overriding the cookie value | | `amplitudeDeviceId` | string | Amplitude device ID | | `posthog.sessionId` | string | PostHog session ID, for joining events to session recordings | | `posthog.distinctId` | string | PostHog distinct ID | ### Forwarded from a storefront integration Shopify storefronts capture click IDs on the landing page, write them to cart attributes, and forward them with the order. These arrive on the event without the browser SDK having seen them, and include `gclid`, `wbraid`, `gbraid`, `msclkid`, `fbclid`, `twclid`, `dclid`, `li_fat_id`, `sc_cid`, `irclickid`, and `im_ref`. `context.clientIds` is open-ended — a destination or transformation may add fields beyond those listed above. ## 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 18 Aug 2026** [title] Granting Chord Access to Your Shopify Store [path] Chord Event Tracking/Using with Shopify/ ## Overview Follow the steps below to grant Chord access to your Shopify store. This allows us to install custom apps, set up event tracking, and support your implementation. :::hint{type="info"} **Note: **Shopify updated their permissions structure on January 1, 2026. The steps below reflect the current process for granting access. ::: **All steps in this guide must be completed** before the Chord team can verify access to your store. Once complete, we'll confirm that we have: - The ability to add custom pixels via Customer Events; and - Access to the developer dashboard via Apps. ### Step 1: Create a custom Store role for Chord 1. Your brand's Shopify Store Admin should log into your Shopify store. 2. Once logged in, your brand’s Store Admin can navigate to **Users** on the lefthand menu and click **Roles**. 3. The Store Admin should **add a role** using the **Add role** button on the top right. 4. The new role should be for `access@chord.co` created under the **Store role** category. Your store admin can name this custom role whatever they would like. In the example above, we created a **Chord Commerce Test** role under **Store**. 5. Additionally, your store admin will need to assign the following scopes to this specific role **(if a scope is not listed, it is not required): ** ::::ExpandableHeading ### Scopes (expand for full list) :::Paragraph{indent="2"} **A. Orders** ::: :::Paragraph{listStyleType="disc" indent="3"} View ::: :::Paragraph{listStyleType="disc" indent="3"} Cancel ::: :::Paragraph{listStyleType="disc" indent="3"} Returns and refunds ::: :::Paragraph{listStyleType="disc" indent="4"} Return ::: :::Paragraph{listStyleType="disc" indent="4"} Refund to original payment ::: :::Paragraph{listStyleType="disc" indent="4"} Refund to store credit ::: :::Paragraph{indent="2"} **B. Drafts** ::: :::Paragraph{listStyleType="disc" indent="3"} View ::: :::Paragraph{indent="2"} **C. Products** ::: :::Paragraph{listStyleType="disc" indent="3"} View ::: :::Paragraph{listStyleType="disc" indent="4"} View Cost ::: :::Paragraph{indent="2"} **D. Gift cards** ::: :::Paragraph{listStyleType="disc" indent="3"} View ::: :::Paragraph{listStyleType="disc" indent="3"} Create and edit ::: :::Paragraph{indent="2"} **E. Customers** ::: :::Paragraph{listStyleType="disc" indent="3"} View ::: :::Paragraph{indent="2"} **F. Marketing** ::: :::Paragraph{listStyleType="disc" indent="3"} View, create, and delete marketing activities and automations ::: :::Paragraph{listStyleType="disc" indent="3"} Campaigns ::: :::Paragraph{listStyleType="disc" indent="4"} View ::: :::Paragraph{listStyleType="disc" indent="4"} Create and edit ::: :::Paragraph{listStyleType="disc" indent="4"} Delete ::: :::Paragraph{indent="2"} **G. Discounts** ::: :::Paragraph{listStyleType="disc" indent="3"} View, create, and delete ::: :::Paragraph{indent="2"} **H. Content** ::: :::Paragraph{listStyleType="disc" indent="3"} Files ::: :::Paragraph{listStyleType="disc" indent="4"} View ::: :::Paragraph{listStyleType="disc" indent="4"} Create ::: :::Paragraph{listStyleType="disc" indent="4"} Edit ::: :::Paragraph{listStyleType="disc" indent="4"} Delete ::: :::Paragraph{indent="2"} **I. Finance** ::: :::Paragraph{listStyleType="disc" indent="3"} View Shopify Payments payouts ::: :::Paragraph{indent="2"} **J. Analytics** ::: :::Paragraph{listStyleType="disc" indent="3"} Reports ::: :::Paragraph{listStyleType="disc" indent="3"} Dashboards ::: :::Paragraph{indent="2"} **K. Online Store** ::: :::Paragraph{listStyleType="disc" indent="3"} Themes ::: :::Paragraph{listStyleType="disc" indent="4"} Edit code (including generating theme blocks) ::: :::Paragraph{listStyleType="disc" indent="3"} Blog posts and pages ::: :::Paragraph{indent="2"} **L. App development** ::: :::Paragraph{listStyleType="disc" indent="3"} View apps developed by staff and collaborators ::: :::Paragraph{listStyleType="disc" indent="4"} Develop ::: :::Paragraph{listStyleType="disc" indent="4"} Enable development ::: :::Paragraph{indent="2"} **M. Store settings** ::: :::Paragraph{listStyleType="disc" indent="3"} Manage settings ::: :::Paragraph{listStyleType="disc" indent="3"} Locations ::: :::Paragraph{listStyleType="disc" indent="3"} View customer events ::: :::Paragraph{listStyleType="disc" indent="4"} Manage and add custom pixels ::: :::Paragraph{indent="2"} **N. App and sales channel permissions** ::: :::Paragraph{listStyleType="disc" indent="3"} Manage and install apps and channels ::: :::: ### Step 2: Assign App Developer - Organization role for Chord Your brand’s Store Admin will also need to assign `access@chord.co` to an** App Developer** role under the **Organization role** category. *This should be a default role that is available.* This role will allow Chord to access the developer dashboard to create custom apps for eventing webhooks and Chord Ingestor. [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] Subscription Reminder Sent [path] Chord Event Tracking/Server Events/Track/ This event is triggered when a reminder about an upcoming subscription installment is generated/sent. # 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 Reminder Sent", "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 Reminder Sent", "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] 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] User Created [path] Chord Event Tracking/Server Events/Track/ This event is triggered when a customer creates a user account. # Properties | **Name** | **Type** | **Description** | **Required** | | ---------------------- | ---------- | --------------------------------------------- | ------------ | | `user_id` | `string` | Unique ID of the user | Yes | | `email` | `string` | Email of the user | Yes | | `roles` | `string[]` | List of roles assigned to the user | No | | `ship_address` | `object` | Shipping address of the user | No | | `bill_address` | `object` | Billing address of the user | No | | `store_credit_balance` | `number` | Balance of store credit available to the user | No | ## Ship 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` | `string` | Customer name | No | | `state_name` | `string` | ISO state code for the shipping address | No | | `zipcode` | `string` | Zip or postal code for the shipping address | No | ## Bill 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` | `string` | Customer name | No | | `state_name` | `string` | ISO state code for the shipping address | No | | `zipcode` | `string` | Zip or postal code for the shipping address | No | # Sample Payload ```json { "type": "track", "event": "User Created", "properties": { "user_id": "U1234", "email": "test@example.com", "roles": [], "store_credit_balance": 0.00, "ship_address": { "name": "John Doe", "address1": "123 Fake St", "address2": null, "city": "Oak Lawn", "zipcode": "60532", "phone": "1234567890", "state_name": "IL", "company": null }, "bill_address": { "name": "John Doe", "address1": "123 Fake St", "address2": null, "city": "Oak Lawn", "zipcode": "60532", "phone": "1234567890", "state_name": "IL", "company": null } } } ``` # 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": "User Created", "properties": { "user_id": "U1234", "email": "test@example.com", "roles": [], "store_credit_balance": 0.00, "ship_address": { "name": "John Doe", "address1": "123 Fake St", "address2": null, "city": "Oak Lawn", "zipcode": "60532", "phone": "1234567890", "state_name": "IL", "company": null }, "bill_address": { "name": "John Doe", "address1": "123 Fake St", "address2": null, "city": "Oak Lawn", "zipcode": "60532", "phone": "1234567890", "state_name": "IL", "company": null } } } ``` [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] Configuration [path] Chord Event Tracking/Using with Shopify/Web Pixel/ The Chord web pixel has a few settings that appear as `const` variables at the top of the web pixel code you copied into Shopify: ```javascript const CHORD_OMS_ID = '' const CHORD_STORE_ID = '' const CHORD_TENANT_ID = '' const DEFAULT_LOCALE = 'en-US' const CDP_DOMAIN = '' const CDP_WRITE_KEY = '' const STORE_DOMAIN = '' ``` All of these variables should be updated with the appropriate values. See the reference below for a description of what ### Configuration variable reference | Variable | Type | Description | | ----------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------- | | `CHORD_OMS_ID` | string | A UUID assigned by Chord. This identifier is unique to the store, and will be the same across every environment and CDP source for a given store. | | `CHORD_STORE_ID` | string | A UUID assigned by Chord. This identifier is unique to the store, and will be the same across every environment and CDP source for a given store. | | `CHORD_TENANT_ID` | string | A UUID assigned by Chord. This identifier is unique to the store, and will be the same across every environment and CDP source for a given store. | | `DEFAULT_LOCALE` | string | The default order locale. For example, `en-US`. See the [usage guide](docId\:gvuGCbQHfkHEUhE58wpKe) for more details. | | `CDP_DOMAIN` | string | Provided by Chord. The domain for your CDP website source. | | `CDP_WRITE_KEY` | string | Provided by Chord. The write key for your CDP website source. | | `STORE_DOMAIN` | string | The store slug that comes before `.myshopify.com` in the Shopify URL. | [title] ShopMy [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ **ShopMy** is an affiliate marketing platform for creator partnerships. This destination loads the ShopMy affiliate click-tracking script in the browser and sends order confirmations to ShopMy when a visitor was referred by a ShopMy affiliate or used a creator's discount code. No credentials are required — ShopMy attribution is based on cookies set by the click-tracking script and/or discount codes on the order. # Getting Started This is a device-mode destination. No credentials are required. The ShopMy click-tracking script is loaded automatically. # Connecting to the ShopMy 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 **ShopMy** from the destination catalog. 5. Enter the destination name. 6. Click **"Create"** to connect. # Events # Event Mapping | Chord Event | ShopMy Action | Notes | | ----------------- | --------------------------------------------------- | ---------------------------------------------------------------- | | `page` | Loads click-tracking script | No data forwarded | | `Order Completed` | `POST https://api.shopmy.us/api/order_confirmation` | Fired if `sms_click_id` cookie **or** a discount code is present | All other events are silently skipped. Page and identify events do not send data to ShopMy — they only trigger the script to load. # Page Events Loads the ShopMy click-tracking script. No data is sent to ShopMy — the script manages affiliate attribution cookies (`sms_click_id`) autonomously. # Order Completed Sends an order confirmation to the ShopMy API. The event is **skipped** only if **neither** an `sms_click_id` cookie **nor** a discount code is present. This ensures orders are reported for both click-based attribution (affiliate link) and code-based attribution (creator discount code). **API call:** `POST https://api.shopmy.us/api/order_confirmation` | ShopMy Attribute | Chord Source (Priority Order) | Notes | | ----------------------- | ----------------------------------------------------------------- | ----------------------------------------------- | | `orderAmount` | `properties.subtotal` > `properties.revenue` > `properties.total` | Defaults to `0` | | `orderId` | `properties.order_id` | | | `clickId` | `sms_click_id` cookie | Optional; only included in payload when present | | `currency` | `properties.currency` | Defaults to `"USD"` | | `is_returning_customer` | `properties.is_returning_customer` | Defaults to `false` | | `page_url` | `window.location.href` | Current page URL at time of event | | `code` | `properties.coupon` > `properties.discount_code` | Coupon/discount code; `null` if not present | The API request has a 5-second timeout. If the request times out or fails, a warning is logged and the event is dropped. # Initialization The plugin loads `https://static.shopmy.us/Affiliates/sms_aff_clicktrack.js` on the first event of any type. This script handles affiliate click attribution by reading URL parameters and setting the `sms_click_id` cookie. The plugin manages SDK loading state (`fresh` → `loading` → `loaded`/`failed`) to prevent duplicate script loads. Concurrent events during loading are queued and processed after initialization completes. 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://static.shopmy.us` | | `connect-src` | `https://api.shopmy.us` | *** **Updated 14 Apr 2026** [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] PostHog [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ # Introduction PostHog is an open-source product analytics platform that helps teams understand how users interact with their web or mobile apps. It combines event tracking, session replays, heatmaps, feature flags, and A/B testing into a single platform—allowing product and engineering teams to analyze behavior, test features, and ship improvements faster. Unlike many analytics tools, PostHog can be self-hosted, giving teams full control over their data and compliance. It’s especially popular with teams that want powerful analytics without sending data to third-party servers. # Getting started You need your Project API Key to connect to this destination. You can find your Project API Key under [Project Settings](https://app.posthog.com/project/settings) in PostHog. # Connecting to the PostHog CDP destination 1. Log into the Chord data platform. 2. Navigate to the CDP. 3. Click the **"Add" **button next to Destinations. 4. Select **PostHog **from the destination catalog. 5. Enter in the destination name and the **PostHog Project 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 the [Posthog](https://posthog.com/docs/data/events) destination are: | **Chord Tracking Event** | *Destination Event* | | ------------------------ | ----------------------------------------- | | **Identify** | *No event specified, user identification* | | **Page** | *pageview* | | **All Track Events** | *Event name passed as is* | :::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] Retention.com [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ **Retention.com** is a visitor identification and retargeting platform that matches anonymous website visitors to contact records for email and direct mail remarketing. This destination loads the Retention.com pixel in the browser and forwards page views, identify events, order data, and product interactions. There is no server-side component. # Getting Started This is a device-mode destination. The Retention.com pixel is loaded automatically — no manual script installation is required. You will need: - **Site ID** — your Retention.com site ID, found in your Retention.com account settings. # Connecting to the Retention.com 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 **Retention.com** from the destination catalog. 5. Enter the destination name and your **Site ID**. 6. Click **"Create"** to connect. # Events # Event Mapping | Chord Event | Retention.com SDK Call | | ----------------- | -------------------------------------------------- | | `page` | `geq.page()` | | `identify` | `geq.suppress(email)` | | `Email Captured` | `geq.suppress(email)` | | `Order Completed` | `geq.trackOrder(orderData)` | | `Product Added` | `geq.addToCart(productData)` | | `Product Viewed` | `geq.event("Viewed Product Reclaim", productData)` | # Page Events Fires a Retention.com page view call. **Retention SDK call:** `geq.page()` No additional attributes are sent with page events. # Identify Events Suppresses Retention.com anonymous visitor collection for known users. When a user is identified with an email, Retention.com stops collecting anonymous data for that email. **Retention SDK call:** `geq.suppress(email)` | Parameter | Chord Source (Priority Order) | Notes | | --------- | ------------------------------------------------------------ | ---------------------------------- | | `email` | `properties.email` > `context.traits.email` > `traits.email` | Event is skipped if no email found | # Email Captured Suppresses Retention.com collection when an email is captured (same behavior as Identify). **Retention SDK call:** `geq.suppress(email)` | Parameter | Chord Source (Priority Order) | Notes | | --------- | ----------------------------------- | ---------------------------------- | | `email` | `properties.email` > `traits.email` | Event is skipped if no email found | # Order Completed Sends an order tracking call to Retention.com. **Retention SDK call:** `geq.trackOrder(orderData)` | Retention Attribute | Chord Source (Priority Order) | Notes | | ------------------- | ------------------------------------------------------------ | ------------------------------------ | | `order_number` | `properties.order_id` | | | `order_amount` | `properties.total` > `properties.value` | Defaults to `0`; converted to string | | `order_email` | `properties.email` > `context.traits.email` > `traits.email` | | # Product Added Sends an add-to-cart event. Uses the first product from `properties.products[]`, or falls back to extracting product data from root-level `properties`. **Retention SDK call:** `geq.addToCart(productData)` | Retention Attribute | Chord Source (Priority Order) | Notes | | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | ------------------- | | `Name` | `properties.products[0].name` > `properties.name` | | | `Price` | `properties.products[0].price` > `properties.price` | Converted to string | | `ProductID` | `properties.products[0].product_id` > `properties.products[0].sku` > `properties.products[0].id` > `properties.product_id` > `properties.sku` | | | `Categories` | `properties.products[0].category` > `properties.category` | | | `ImageURL` | `properties.products[0].image_url` > `properties.image_url` | | | `URL` | `properties.products[0].url` > `properties.url` | | | `Brand` | `properties.products[0].brand` > `properties.brand` | | # Product Viewed Sends a product viewed event using Retention.com's Reclaim feature. **Retention SDK call:** `geq.event("Viewed Product Reclaim", productData)` Same attributes as **Product Added** above. # Initialization The plugin loads `https://s3-us-west-2.amazonaws.com/jsstore/a/{siteId}/ge.js` on the first event received. The plugin manages SDK loading state (`fresh` → `loading` → `loaded`/`failed`) to prevent duplicate script loads. Concurrent events during loading are queued and processed after initialization completes. 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. Note that `script-src` covers where the SDK file is downloaded from, while `connect-src` covers where the SDK sends tracking data to at runtime — these are different hosts and both must be allowed. | Directive | Domain | Purpose | | ------------- | ----------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | | `script-src` | `https://s3-us-west-2.amazonaws.com` | Downloads `ge.js` (the Retention.com SDK) | | `connect-src` | `https://*.execute-api.us-west-2.amazonaws.com` | Outbound event, order, and suppression calls to Retention.com's tracking API | | `connect-src` | `https://alocdn.com` | Per-account configuration fetch | | `connect-src` | `https://pro.ip-api.com` | Geo/VPN validation (only if `enable_geo_check` or `enable_vpn_check` is enabled in your Retention.com account) | | `connect-src` | `https://a.usbrowserspeed.com` | Fingerprint fallback for anonymous visitor resolution | | `connect-src` | `https://b-code.liadm.com` | LiveIntent identity resolution (only if enabled in your Retention.com account) | Verify against your Retention.com account's current configuration — additional domains may be required if you have optional features enabled that aren't listed above. *** **Updated 6 Apr 2026** [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] Release Notes [path] Chord Event Tracking/ [title] Shipment Shipped [path] Chord Event Tracking/Server Events/Track/ This event is triggered when an order shipment has shipped. # Properties | **Name** | **Type** | **Description** | **Required** | | -------------- | -------- | ------------------------------------------------- | ------------ | | `currency` | `string` | ISO currency code of the transaction (e.g. `USD`) | Yes | | `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_number` | `string` | Order ID or number | Yes | | `shipment` | `object` | Products in the order | Yes | ## Shipment | **Name** | **Type** | **Description** | **Required** | | ----------------------- | ---------- | ------------------------------------------------------------------------------------------ | ------------ | | `tracking` | `string` | Tracking code of the shipment | No | | `carrier` | `string` | Name of the carrier fulfilling the shipment | No | | `number` | `string` | Shipment ID/number | Yes | | `cost` | `number` | Shipment cost | No | | `adjustment_total` | `number` | Total of all adjustments/discounts of the shipment | No | | `additional_tax_total` | `number` | | No | | `promo_total` | `number` | Total of all promotions of the shipment | No | | `included_tax_total` | `number` | | No | | `pushed` | `string` | Indicates if the shipment record has been sent to the warehouse/fulfillment centre/carrier | No | | `fulfilled_by` | `string` | ISO date when the shipment was fulfilled/pushed | No | | `tracking_detail` | `string` | Additional tracking information | No | | `external_tracking_url` | `string` | URL for customer to tracking shipping status | No | | `label_url` | `string` | URL of electronically generated label | No | | `products` | `object[]` | Products/inventory in the shipment | No | | `address` | `object` | 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 | ## 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` | `string` | Customer name | No | | `state_name` | `string` | ISO state code for the shipping address | No | | `zipcode` | `string` | Zip or postal code for the shipping address | No | # Sample Payload ```json { "type": "track", "event": "Shipment Shipped", "properties": { "currency": "USD", "email": "test@example.com", "order_number": "O1234567890", "first_name": "John", "last_name": "Doe", "shipment": { "tracking": "T1234567890", "carrier": "UPS", "number": "H1234567890", "cost": 9.99, "state": "ready", "adjustment_total": 9.99, "additional_tax_total": 9.99, "promo_total": 9.99, "included_tax_total": 9.99, "pushed": "true", "fulfilled_by": "2026-01-01T00:00:00.000Z", "tracking_detail": null, "external_tracking_url": null, "label_url": null, "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" } ], "address": { "name": "John Doe", "address1": "123 Fake St", "address2": null, "city": "Oak Lawn", "zipcode": "60532", "phone": "1234567890", "state_name": "IL", "company": null } } } } ``` # 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": "Shipment Shipped", "properties": { "currency": "USD", "email": "test@example.com", "order_number": "O1234567890", "first_name": "John", "last_name": "Doe", "shipment": { "tracking": "T1234567890", "carrier": "UPS", "number": "H1234567890", "cost": 9.99, "state": "ready", "adjustment_total": 9.99, "additional_tax_total": 9.99, "promo_total": 9.99, "included_tax_total": 9.99, "pushed": "true", "fulfilled_by": "2026-01-01T00:00:00.000Z", "tracking_detail": null, "external_tracking_url": null, "label_url": null, "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" } ], "address": { "name": "John Doe", "address1": "123 Fake St", "address2": null, "city": "Oak Lawn", "zipcode": "60532", "phone": "1234567890", "state_name": "IL", "company": null } } } } ' ``` [title] Twitter Ads [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ **Twitter Ads** (now X Ads) is X's advertising platform for promoted content, conversion campaigns, and audience targeting. This destination loads the X/Twitter Universal Website Tag (UWT) JavaScript SDK in the browser and forwards conversion events based on a configurable event mapping. Page and identify events are not forwarded. There is no server-side component. # Getting Started This is a device-mode destination. The Twitter/X UWT SDK is loaded automatically — no manual script installation is required. You will need: - **Pixel ID** — your Twitter/X Pixel ID, found in your X Ads account under **Tools > Conversion Tracking**. Optionally: - **Event Mapping** — maps Chord event names to Twitter Event IDs (e.g., `{ "Product Added": "tw-abc12-def34" }`). **Only events with an explicit entry in this mapping are forwarded.** All unmapped events are silently skipped. - **Identifier** — which product field to use as the content ID (`product_id`, `sku`, or `id`). Defaults to `product_id` > `id` > `sku` fallback chain. # Connecting to the Twitter Ads 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 **Twitter Ads** from the destination catalog. 5. Enter the destination name and your **Pixel ID**. 6. Configure the **Event Mapping** to specify which Chord events should fire which Twitter Event IDs. 7. Optionally configure the **Identifier** field. 8. Click **"Create"** to connect. # Events Page and identify events are **not** forwarded to Twitter Ads. Only track events with an explicit entry in the **Event Mapping** configuration are forwarded. All unmapped events are silently skipped. # Track Events **Twitter SDK call:** `twq("event", twitterEventId, eventPayload)` ## User Parameters | Twitter Attribute | Chord Source (Priority Order) | Notes | | ----------------- | ------------------------------------------------------------ | --------------------------------------- | | `email_address` | `properties.email` > `context.traits.email` > `traits.email` | Automatically hashed by the Twitter SDK | | `phone_number` | `properties.phone` > `context.traits.phone` > `traits.phone` | Automatically hashed by the Twitter SDK | ## Order Parameters | Twitter Attribute | Chord Source (Priority Order) | Notes | | ----------------- | -------------------------------------------------------------- | ---------------------- | | `value` | `properties.revenue` > `properties.total` > `properties.value` | | | `currency` | `properties.currency` | Defaults to `"USD"` | | `conversion_id` | `properties.cart_id` / `properties.order_id` | Used for deduplication | ## Product Contents Each product in `properties.products[]` is mapped to a Twitter content item: | Twitter Attribute | Chord Source (Priority Order) | Notes | | ------------------ | ---------------------------------------------------------------------------------------- | ----- | | `content_id` | Configured `identifier` field from `properties.products[]` > `product_id` > `id` > `sku` | | | `content_name` | `properties.products[].name` | | | `content_price` | `properties.products[].price` | | | `num_items` | `properties.products[].quantity` | | | `content_type` | `properties.products[].category` | | | `content_group_id` | `properties.products[].variant_id` | | All undefined values are filtered out before sending. # Initialization The plugin sets up the `twq` function queue, then loads `https://static.ads-twitter.com/uwt.js`. After the script loads, it calls `twq("config", pixelId)` to initialize the pixel. 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://static.ads-twitter.com` | | `connect-src` | `https://static.ads-twitter.com` | *** **Updated 6 Apr 2026** [title] Nosto Tag [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ Nosto is an onsite personalization engine: it learns from what shoppers browse and buy, then renders product recommendations into your pages. The Nosto Tag destination loads Nosto in the browser and keeps each visitor's Nosto session up to date from your Chord events. # Getting Started You need one value, and one thing removed. **Your Nosto account ID** is shown in the top-right corner of the Nosto dashboard, under your shop name. **Remove any Nosto script you installed yourself**, including the Nosto app if you installed one through your commerce platform. This is not a preference — Nosto honours only the first session initialized on a page, so two scripts produce two sessions, double your page views, and split one shopper's behaviour across both. This destination replaces that installation rather than complementing it. Your existing shopper profiles carry over. Nosto identifies returning visitors by its own first-party cookie, which this destination leaves Nosto to manage, so the history behind your recommendations survives the switch. # Connecting to the Nosto CDP Destination 1. In Chord, add the **Nosto Tag** destination. 2. Enter your **Account ID**. 3. Leave **Load Recommendations** on unless you want Nosto to receive behavioural data without displaying anything. 4. Connect it to your front-end site. 5. Remove your own Nosto script. Nothing else is configured. In particular there is no placement setup: Nosto finds the placement elements already in your page markup and injects into them, which is why the switch is a drop-in. # Using Alongside the Nosto Destination The [Nosto](#) destination sends the same information server-side, over Nosto's GraphQL API. Both can run together, and they write to the **same** visitor session as long as both use the same Nosto account — this destination owns Nosto's session cookie, and Chord forwards it so the server-side half updates that session rather than creating another. **One exception, and it matters: do not report orders from both.** Nosto publishes no deduplication rule for order submission — no dedup key, and no documented behaviour when the same order arrives twice. Running both destinations therefore reports each order twice. Pick one surface for orders: - **This destination** is the natural choice if you are replacing a Nosto tag, because it behaves like the installation you already had. - **The Nosto destination** is more reliable — server-side reporting is unaffected by ad blockers, and it still works when checkout happens on a domain your storefront does not control. # Deduplication Chord sends your order's own reference as `external_order_ref`, so it is the value to deduplicate against if you also send orders to Nosto from another system. As above, Nosto does not document what it does with a repeat, so treat "send each order once" as the rule rather than relying on Nosto to sort it out. # Event Mapping | Chord event | Nosto | | ------------------------------------------------------ | --------------------------------------------- | | `Page Viewed` (home page) | Front page view | | `Page Viewed` (any other page) | Session refresh — no view recorded, see below | | `Product Viewed` | Product view, with the product ID | | `Product List Viewed` | Category view, with the category path | | `Products Searched` | Search, with the search term | | `Cart Viewed` | Cart page view | | `Product Added`, `Product Removed`, `Checkout Started` | Cart contents update | | `identify`, `Signed Up`, `Email Captured` | Customer details | | `Order Completed` | Order, with line items | | `Order Refunded` | Not supported in the browser — see Gotchas | **One view is recorded per navigation, not two.** Your storefront fires `Page Viewed` *and* a specific event like `Product Viewed` on the same page load. Recording both would report every product page to Nosto twice and inflate the page counts it merchandises on, so the specific event is the one that records the view and `Page Viewed` only keeps the session alive. The home page is the exception: it has no specific event of its own, so there `Page Viewed` records the front-page view. The trade-off is that a page with no specific Chord event — a blog post, an about page — is not recorded as a view in Nosto. It still refreshes the shopper's session, so their browsing continuity and recommendations are unaffected. # Product and Category Data Each order and cart line sends the product ID, variant ID, name, unit price, quantity and currency. A line with no resolvable product ID is dropped rather than sent blank, because Nosto keys recommendations off the product ID and a blank one is unusable. Category views send a slash-delimited path, which is the form Nosto expects. Chord's tracking plan carries a single category label, so `Dresses` is sent as `/Dresses` and `Womens > Dresses` as `/Womens/Dresses`. If your recommendations depend on a deeper hierarchy, send the full path in the event's `category` property using `>` between levels. # Identity Nosto receives email address, first and last name, and your customer reference **in plaintext**, and this is deliberate. Nosto has to resolve a shopper to a stored profile and address them by name in the experiences it renders, so unlike an advertising pixel it accepts no hashed identifier — hashing would break the product rather than protect it. If your security review needs to know exactly what leaves the page, that is the list. Marketing permission is sent only when your event carries one. Chord does not assume a default in either direction. # Content Security Policy If your storefront sets a Content Security Policy, Nosto will not load until its hosts are allowed. The symptom is silence: no recommendations, no data, and a `Refused to load` message in the browser console. | Directive | Host | | ------------- | --------------------------- | | `script-src` | `https://connect.nosto.com` | | `connect-src` | `https://*.nosto.com` | Both directives are required. `script-src` lets the library load; `connect-src` lets it report — and a policy that allows only the first fails in a way that looks like it worked, because the script runs, recommendations render, and nothing reaches Nosto. This list is what a Chord reference storefront needs to deliver product views, cart updates and orders. Nosto also loads recommendation images from wherever your product images are hosted, and may request further hosts depending on the features your account has enabled. Those are not published, so read them off your own browser console during setup: load a page with the destination active, fire a product view and an order, and add any host named in a violation. # Custom Properties **Custom property mappings are not forwarded to Nosto, and cannot be.** Nosto's browser API has no general-purpose property bag — each call takes a fixed set of fields, and the cart, customer and order objects are closed shapes with nowhere for an extra key to go. A mapping you configure on this destination will not reach Nosto. If you need Nosto to act on something outside the fields above, that is a conversation with Nosto about their catalog or segment data rather than something Chord can pass through. # Gotchas **Refunds need the server-side destination.** Nosto models a refund as a status change on an existing order, and it exposes order-status updates only through its GraphQL API. `Order Refunded` is skipped here with a console message; connect the [Nosto](#) destination to report refunds. **Emptying a cart does not clear it in Nosto.** Chord's `Product Removed` carries the line that was removed, not the cart that remains, so Chord cannot tell "the cart is now empty" apart from "this event had no products". Rather than risk clearing real carts, Chord leaves Nosto's cart alone in that case, and it updates on the shopper's next cart-bearing event. **Nosto's event set is fixed.** Nosto accepts the page types above plus cart, customer and order updates, and has no arbitrary custom event. Chord events with no Nosto equivalent — `Product Clicked`, `Product List Filtered`, `Coupon Applied` and similar — are skipped, and the reason is logged to the browser console. **Sessions expire after 30 minutes** of inactivity. A shopper who returns later starts a new session; their profile and history persist, but that visit's browsing begins fresh. **Consent gating applies.** If the destination is configured with required consent categories, no Nosto call is made for visitors who have not accepted them. Nosto's own session cookie is only set after consent, which also means the server-side destination has no session to update until then. **Updated 1 September 2026** [title] Yotpo [path] Chord Event Tracking/Guides/Integrations/ :::ExpandableHeading ### Introduction This document will walk through integrating Chord's OMS with Yotpo. Once you integrate, your customers will be able to use a powerful data-driven tools that makes it very easy for your customers to provide their feedback so you can transform every purchase made into a review. ::: :::ExpandableHeading ### What is Yotpo The Yotpo destination function is used to sync completed orders from the Chord's OMS platform to Yotpo to be able to collect higher-quality reviews addressing high-converting topics that actually inspire purchases and grow your business For more information about Yotpo and custmizing the request flows please refer to their document [here](https://support.yotpo.com/en/article/creating-a-review-request-premium-enterprise) ::: :::ExpandableHeading ### Creating the function Before starting the creation of the function ensure that you are using the correct code template. There are two different code templates for [Autonomy](https://github.com/chordcommerce/segment-functions/blob/main/destinations/yotpo-autonomy/index.js) vs [Performance](https://github.com/chordcommerce/segment-functions/blob/main/destinations/yotpo-performance/index.js) customers. It is important to choose the right one. Copy the correct code Navigate to Segment and click Catalog -> Functions -> New Function ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/5yqyVsByw_31SELGs438W_image-10-4-2022-at-1040-am.jpg "New Function ") Select "Destination Function" and click Build Paste in the function code from above ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/akw9ZWt0q02TocpHqE1mm_image-10-4-2022-at-1055-am.jpg "Function Type - Destination") and click Settings - Add Setting Label = apikey Name = apikey Unanmed = \ (found in Yotpo settings) Click **Add Setting** ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/DDXTSLOx6zyThwmXFB_FF_image-10-4-2022-at-337-pm.jpg "Adding Setting") Label = secretkey Name = secretkey Unamed = \ (found in Yopto settings) Click **Add Setting** ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/rhdCDrANUPzxgW-cadGEx_image-10-4-2022-at-344-pm.jpg) Label = secretkey Name = secretkey Unamed = \ (found in Yopto settings) Click Array In the First Item event field paste **Order Completed** Remove Second and Third Item fields Click **Add Setting** ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/4ux8VJVTpYnyHPaHrkLOU_image-10-4-2022-at-357-pm.jpg "Events Setting") Click Configure Provide a Name, we recommend **Yotpo Function** Provide a Description, and even a logo and click create Function ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/A8d8RnW56Nn07krd-lLWV_image-10-4-2022-at-406-pm.jpg "Creating Function") ::: ::::ExpandableHeading ### Connect Function to Source Your Function has been created! Click **Connect Destination** ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/8R8opOV4AfB0jX2frZFbq_image-10-4-2022-at-614-pm.jpg "Connecting the Destination") For Autonomy customers, the destination function should be connected to the **Ruby back-end source**. ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/auXfcHtjZ7IlsN7xTutul_image-10-4-2022-at-630-pm.jpg "example of Ruby autonomy back-end") For Performance customers, the destination function should be connected to the **Javascript front- end source**. ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/ibn6ZoOD3uJnjjassodZn_image-10-4-2022-at-632-pm.jpg "example of JS Performance front-end") When you connect the destination function, you'll need to provide values for the settings you configured above. Select your Destination and click Next Provide a Destination Name, we recommend something like "Yotpo Production" Click Save Enter the Yotpo API key and secret key (found in the Yotpo admin), and Order Completed for the events setting. :::hint{type="info"} Make sure to enable the function ::: :::: ::::ExpandableHeading ### Verify your Function You can test that the function is working correctly in the "Event Tester" tab. You'll need an example event, so find (or place a test order) a recent **Order** **Completed** event in the Segment Debugger for the source that you connected to the Yotpo function, and copy the entire event JSON from the "Raw" tab: ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/I0Yvf_22Yzg_4pp53y9wI_image-10-5-2022-at-859-am.jpg "Order Completed Debugger") Navigate to the "Event Tester" tab of the Yotpo destination function you just created, and replace the dummy JSON with the event JSON you copied: ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/l-usVHaeU7cUjPUT5zg3U_image-10.png "Event Tester") :::hint{type="danger"} The order from the Order Completed event you copied will be synced to Yotpo, so if Yotpo is configured to send automatic review requests, the customer will receive one. ::: Hit "Send Event" and make sure you see a 200: ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/l9uGJxz6kPvJMpP4PJMhZ_image-11.png "Event Lifecycle") :::ExpandableHeading ### Verify API Order If you would like to query the Yotpo API to see what orders have been submitted from the function, here's how: - **Get an access token** Populate the API\_KEY and the SECRET\_KEY in the code snippet: curl --request POST \      --url https://api.yotpo.com/core/v3/stores/API_KEY/access_tokens \      --header 'Accept: application/json' \      --header 'Content-Type: application/json' \      --data '{ "secret": "SECRET_KEY" }' Copy the `access_token`from the output and use it in the next step. - **Get the list of orders** Populate the API\_KEY and the TOKEN (from access\_token above) in the code snippet: curl --request GET \ --url https://api.yotpo.com/core/v3/stores/API_KEY/orders \ --header 'Accept: application/json' \ --header 'Content-Type: application/json' \ --header 'X-Yotpo-Token: TOKEN' You should get a JSON list of orders from Yotpo. Your connection is now successfully created! ::: :::: [title] Sendlane [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ # Introduction Sendlane helps eCommerce brands drive revenue with intelligent automation, real-time behavior tracking, and multichannel marketing workflows. The Sendlane destination allows you to send rich, real-time customer behavior and conversion events from your store (via Chord) to your Sendlane account. This unlocks personalized email and SMS marketing journeys, better audience segmentation, and advanced analytics in Sendlane. ## Getting started To connect Sendlane, you will need: - Admin access to your Sendlane account. - Permission to create or manage API credentials. - A clear understanding of which customer attributes you want to send. If you’re unsure about attribute mapping or segmentation strategy, that’s okay. Most brands refine this during setup. # Connecting to the Sendlane CDP destination 1. Log into the Chord data platform. 2. Navigate to the CDP. 3. Click the **"Add"** button next to Destinations. 4. Select **Sendlane **from the destination catalog. 5. Enter in the destination name and the 6. Click **"Create" **to connect. :::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] 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] 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. ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/FZh4gGzLXGbhmpuVV-dRQ-20251020-203807.jpg) 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: ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/kwd4i89kEZWI0No2-jr-O-20251020-203831.jpg) 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. ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/7V79Ju3N9GQg8CxiI82Oe-20251020-203855.png) ## 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. ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/ciGlfevHmabFnrM9lq-4M-20251020-203955.png) [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] Snapchat Conversions API [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ The **Snapchat Conversions API** (CAPI) is a server-side integration that sends event data directly from Chord CDP to Snapchat's servers. Unlike the Snap Pixel (which runs in the browser), the Conversions API operates in cloud mode — events are sent server-to-server, making them resilient to ad blockers and browser tracking restrictions. Snapchat recommends using the Conversions API alongside the Snap Pixel for maximum data coverage. When both are configured, Snapchat automatically deduplicates events using the `client_dedup_id` field, which Chord CDP sets to the event's `messageId` on both sides. # Getting Started This is a cloud-mode destination. You will need: - **Pixel ID** — found in your Snapchat Ads Manager under **Events Manager > Pixel Details** - **Access Token** — your Conversions API token, found in **Snapchat Ads Manager > Business Details** Optionally: - **Test Mode** — when enabled, events are sent to Snapchat's `/validate` endpoint and appear in the Snap Events Manager debug tool without affecting live reporting - **Product Content ID Field** — which product field to use as `item_id` when sending events: `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`. **This must match the Item ID format in your Snap product catalog and must be set to the same value as the Snap Pixel destination.** # Connecting to the Snapchat 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 **Snapchat Conversions API** from the destination catalog. 5. Enter the destination name, **Pixel ID**, and **Access Token**. 6. Optionally configure **Test Mode** and **Product Content ID Field**. 7. Click **"Create"** to connect. # 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, track, and screen events are forwarded. Identify events are not forwarded. # Common Event Fields These fields are included on every event sent to Snapchat. | Snap Field | Chord Source | Notes | | ------------------------- | --------------------------------------- | ------------------------------------------ | | `event_name` | *(mapped from event — see table above)* | | | `event_time` | `timestamp` | | | `event_id` | `messageId` | Used for deduplication with the Snap Pixel | | `event_source_url` | `context.page.url` | | | `data_processing_options` | *(hardcoded)* `false` | | # User Data | Snap Field | Chord Source (Priority Order) | Notes | | ------------------- | --------------------------------------------------------------------------------------------------------------- | ------------------------- | | `external_id` | `userId` > `anonymousId` | Array | | `email` | `context.traits.email` | | | `phone` | `context.traits.phone` | | | `gender` | `context.traits.gender` | | | `firstName` | `context.traits.firstName` | | | `lastName` | `context.traits.lastName` | | | `birthday` | `context.traits.birthday` | | | `city` | `context.traits.address.city` | | | `state` | `context.traits.address.state` | | | `zip` | `context.traits.address.zip` > `context.traits.address.postalCode` | | | `country` | `context.traits.address.country` | | | `client_ip_address` | `context.ip` | Not hashed | | `client_user_agent` | `context.userAgent` | Not hashed | | `madid` | `context.device.advertisingId` | Mobile ad ID | | `idfv` | `context.device.id` | iOS identifier for vendor | | `sc_click_id` | `properties.click_id` > `integrations["Snap Conversions Api"].click_id` > `ScCid` query parameter from page URL | Snap click ID | | `sc_cookie1` | `integrations["Snap Conversions Api"].uuid_c1` | Snap cookie value | # Custom Data These fields are sent in the `custom_data` block on all events. | Snap Field | Chord Source (Priority Order) | Notes | | --------------- | ----------------------------------------------- | ---------------------------------------------------------------------- | | `currency` | `properties.currency` | Defaults to `"USD"` | | `value` | `properties.value` | Total value after quantity (`price × qty` per the Chord tracking plan) | | `num_items` | Count of products with a resolvable `item_id` | | | `order_id` | `properties.order_id` | | | `search_string` | `properties.query` > `properties.search_string` | | # Products Sent as a `products` array on events that include product data. Omitted if no products are present. | Snap Field | Chord Source (Priority Order) | Notes | | --------------- | ------------------------------------------------------------- | ---------------------------------- | | `item_id` | Configured field → `sku` → `variant_id` → `product_id` → `id` | Must match Item ID in Snap catalog | | `item_category` | `properties.products[].category` | | | `brand` | `properties.products[].brand` | | # Deduplication Chord CDP sends the same `messageId` as `client_dedup_id` on both the Snap Pixel and the Conversions API. Snapchat uses this field to automatically deduplicate events when both destinations process the same user action. For **Purchase** events, Snapchat additionally deduplicates on `transaction_id`. Chord CDP sets this to `properties.order_id` on both the Pixel and CAPI, so no additional configuration is required. For deduplication to work correctly: - Both the Snap Pixel and Snapchat Conversions API destinations must be enabled in Chord CDP - **Product Content ID Field** must be set to the same value in both destinations # Testing and Validation After connecting the destination: 1. Enable **Test Mode** in the destination settings to send events to Snapchat's `/validate` endpoint 2. Trigger test events and confirm they appear in the **Snap Events Manager debug tool** 3. Disable Test Mode before going live 4. After 24–48 hours, check **Events Manager > Diagnostics** to verify match rates and deduplication rates *** **Updated 23 Apr 2026** [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. ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/4STyUgw8GnVE79q9eXm9N_image.png) ## 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] 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] Cookies [path] Chord Event Tracking/ ## Overview Chord CDP uses browser cookies for two separate purposes: 1. **Cookies Chord writes:** First-party cookies on your own domain that keep a visitor's identity and attribution stable across pages, sessions, and devices. 2. **Cookies Chord reads:** Cookies set by advertising and analytics platforms (Meta, Google, TikTok, Pinterest, and others). **Chord never creates or modifies these**; it copies their values onto the event so server-side destinations can attribute conversions as accurately as the platform's own pixel would. Everything Chord writes is a **first-party** cookie scoped to the top level of your storefront domain. Chord sets no third-party cookies. This document is the complete inventory, intended for privacy policy disclosures, cookie banner configuration, and consent category mapping. ## Cookies Chord writes ### Identity cookies These five cookies carry the visitor's identity. They are created on the first page view (anonymous ID) and on the first `identify` / `group` call (the rest). | **Cookie** | **Contents** | **Purpose** | **Lifetime** | | ----------------- | --------------------- | ------------------------------------------------------------------------------------ | ------------ | | `__eventn_id` | UUID | Anonymous ID. Ties all events from this browser together before and after login. | 5 years | | `__eventn_uid` | Your user identifier | Known user ID, set once the visitor is identified. | 5 years | | `__eventn_id_usr` | URL-encoded JSON | User traits captured at identify time (email, name, and any custom traits you send). | 5 years | | `__group_id` | Your group identifier | Group / account ID for B2B or multi-account storefronts. | 5 years | | `__group_traits` | URL-encoded JSON | Traits of the current group. | 5 years | All five share the same attributes: | **Attribute** | **Value** | | ------------- | ----------------------------------------------------------------------------------------------------------------------- | | **Domain** | Top level of the current domain — a pixel on `shop.example.com` writes to `.example.com`. Override with `cookieDomain`. | | **Path** | `/` | | **SameSite** | `None; Secure` on HTTPS, `Lax` on HTTP | | **HttpOnly** | No — the pixel must read these from JavaScript | | **Expiry** | 5 years, refreshed on every write | The cookie names are defaults. Any of them can be renamed with the `cookieNames` option, for example if your CMP or CDN requires a specific naming convention. ### Attribution cookies Chord persists click and campaign parameters from the landing URL so that a conversion later in the session is still credited to the campaign that drove it. Each provider gets one cookie named `__url_param_`, holding the captured value plus the timestamp it was captured. | **Cookie** | **Captured from** | **Surfaced on the event as** | **Default lifetime** | | -------------------------- | ----------------- | ---------------------------- | ------------------------------------ | | `__url_param_impact` | `im_ref` | `context.clientIds.impact` | 30 days, cleared on order completion | | `__url_param_utm_source` | `utm_source` | `context.campaign.source` | 30 days | | `__url_param_utm_medium` | `utm_medium` | `context.campaign.medium` | 30 days | | `__url_param_utm_campaign` | `utm_campaign` | `context.campaign.name` | 30 days | | `__url_param_utm_content` | `utm_content` | `context.campaign.content` | 30 days | | `__url_param_utm_term` | `utm_term` | `context.campaign.term` | 30 days | Behavior worth knowing: - Parameters are captured on **page events only**, so a single-page app must fire a page event on route changes for capture to happen. - The **first value wins** per provider for the lifetime of the cookie. A later visit with a different `utm_source` does not overwrite the stored one until it expires. - UTM values still present in the current URL always take precedence over the stored ones on that event. - `im_ref` is cleared after `Order Completed` (and the equivalent `order complete` / `purchase` names) so the next order is not credited to the same click. Additional parameters, such as Rakuten's `ranMID`, CJ's `cjevent`, or anything else you need, can be added with the `urlParamCapture` option, with a per-provider expiry, clear-on-event list, and optional URL pattern restriction. ### Session cookie | **Cookie** | **Contents** | **Purpose** | **Lifetime** | | -------------- | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | | `_amp_session` | Unix timestamp in ms | Amplitude session ID. Written by Chord so that server-side and browser-side Amplitude events share one session, even before Amplitude's own SDK finishes loading. | 30 minutes, sliding — refreshed on each event | This cookie is `SameSite=Lax` and scoped to the top level of your domain. Note that the pixel writes it on initialization regardless of whether an Amplitude destination is configured, so include it in your cookie declaration even if you do not use Amplitude today. Only Amplitude destinations consume its value. ## Cookies Chord reads Chord copies these values onto every event under `context.clientIds`, where server-side destinations use them for conversion attribution. Chord does not set, refresh, or delete them. They exist only if the corresponding platform's own script has already set them. | **Cookie** | **Set by** | **Surfaced on the event as** | | ---------------------- | -------------------------- | -------------------------------------------------------------------------------------- | | `_fbc` | Meta Pixel | `context.clientIds.fbc` | | `_fbp` | Meta Pixel | `context.clientIds.fbp` | | `_gcl_aw` | Google Ads | `context.clientIds.gcl_aw` | | `_ga` | Google Analytics 4 | `context.clientIds.ga4.clientId` | | `_ga_` | Google Analytics 4 | `context.clientIds.ga4.sessionIds` (keyed by measurement ID) | | `_ttp` | TikTok Pixel | `context.clientIds.ttp` | | `ttclid` | TikTok click ID | `context.clientIds.ttclid` | | `_epik` | Pinterest Tag | `context.clientIds.epik` | | `_amp_session` | Chord or the Amplitude SDK | `context.clientIds.amplitudeSessionId` | | `sms_click_id` | ShopMy | Used by the ShopMy destination for order attribution; not added to `context.clientIds` | To capture a cookie that is not on this list, add it with the `cookieCapture` option: a map of the field name you want on the event to the cookie name to read. ### Values read from live SDKs rather than cookies A few identifiers are read directly from a platform's in-page SDK, not from a cookie, because the SDK's own value is authoritative and available earlier than its cookie. These appear alongside the cookie-derived values in `context.clientIds`: | **Field** | **Source** | | ----------------------------------------- | ----------------------------------------------------------------- | | `amplitudeSessionId`, `amplitudeDeviceId` | Amplitude SDK, when loaded — takes precedence over `_amp_session` | | `posthog.sessionId`, `posthog.distinctId` | PostHog SDK, when loaded | ## Local Storage Cookies alone are not durable enough for identity. Safari's Intelligent Tracking Prevention caps script-written cookies at 7 days, and browser cookie clearing is common. Chord therefore keeps a backup copy of identity state in `localStorage` and restores the cookie from it whenever the cookie is missing. | **Key** | **Mirrors** | | ------------------------------ | ---------------------------------------------------------------------------- | | `jitsu___eventn_id` | `__eventn_id` | | `jitsu___eventn_uid` | `__eventn_uid` | | `jitsu___eventn_id_usr` | `__eventn_id_usr` | | `jitsu___group_id` | `__group_id` | | `jitsu___group_traits` | `__group_traits` | | `jitsu___url_param_` | The matching attribution cookie | | `_cdp_debug` | Not identity data; a flag that turns on verbose pixel logging in the console | Only identity and attribution keys are mirrored. If `localStorage` is unavailable (private browsing, storage quota exhausted, or blocked by browser settings) Chord falls back to cookies alone without erroring. ### Server-set cookies for Safari Cookies set by a server response are not subject to the same ITP 7-day cap as cookies written by JavaScript. If you configure the `idEndpoint` option to point at a Chord identity endpoint on your own domain, Chord additionally sets: | **Cookie** | **Purpose** | **Lifetime** | | ------------------- | -------------------------------------------- | ------------ | | `__eventn_id_srvr` | HttpOnly server-set copy of the anonymous ID | 5 years | | `__eventn_uid_srvr` | HttpOnly server-set copy of the user ID | 5 years | These are written by an HTTP response, are `HttpOnly` (unreadable from JavaScript), and are used to restore the browser-side cookie if it has been evicted. The endpoint must be served from the same domain as your storefront for this to work. ## Consent and privacy controls ### What consent categories gate Consent categories gate **event delivery to destinations** and **device-mode script loading** (see [Consent Management](docId\:kcbqXL1zcpJdHR9i2LiJW)). They do not by themselves stop Chord from writing its own first-party identity cookies. To suppress identity collection itself, use the privacy options below. ### Privacy options | **Option** | **Effect on cookies** | | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `privacy.disableUserIds` | No third-party cookies are read (`context.clientIds` is omitted), `identify` and `group` become no-ops so no user or group cookies are written, `_amp_session` is not created, and `userId` / `anonymousId` are stripped from every payload. | | `privacy.dontSend` | No events are sent at all. | | `privacy.ipPolicy` | Controls IP handling, not cookies. | Turning `disableUserIds` back off (for example after a visitor accepts your banner) generates a **new** anonymous ID rather than resurrecting the previous one, so the pre-consent and post-consent sessions are deliberately not linked. ### Clearing cookies Calling `reset()` on the pixel deletes all five identity cookies and their `localStorage` mirrors, and issues a fresh anonymous ID. This is the right call to make on logout. ### Declaring Chord cookies in your cookie banner For CMP configuration, Chord's cookies group as follows. Confirm the final classification with your own privacy counsel. | **Cookies** | **Typical category** | | ------------------------------------------------------------------------------------------------ | ----------------------------------------------------------- | | `__eventn_id`, `__eventn_uid`, `__eventn_id_usr`, `__group_id`, `__group_traits`, `_amp_session` | Analytics / performance | | `__url_param_*` | Marketing / advertising | | Third-party cookies Chord reads | Declared under the platform that sets them, not under Chord | [title] Installation [path] Chord Event Tracking/Using with Shopify/Web Pixel/ To install the Chord web pixel on your Shopify store: 1. Ask the Chord team for the full web pixel code (see the example below). 2. Navigate to **Settings** > **Customer events** in your Shopify store. 3. Select **Add custom pixel**. 4. Enter "Chord Analytics" as the name for your pixel. 5. Select **Add pixel**. 6. Review the customer privacy settings, and see our guide to [consent management](docId\:dbKzUyYJsHKX7dzHiSfeZ) to understand how these settings will impact your event tracking. 7. In the **Code** text box, copy and paste the provided web pixel code. 8. Before you publish the provided web pixel, you need to update the settings `const` variables at the very top of the JavaScript code. See the [configuration guide](docId\:qMM8Kz1WShyJhs9qbh0vm) for a detailed explanation of each `const` variable. After you've updated the `const` variables, select **Save**. 9. Once the pixel has been saved successfully, you can select **Connect** to enable the pixel on your Shopify store. Once you select **Connect**, the pixel will immediately load and start tracking events, so make sure you finalize the pixel settings first. ::::CodeDrawer{title="Shopify web pixel code (EXAMPLE ONLY)" isResponseExpanded="false" autoGeneratedAnchorSlug="shopify-web-pixel-code-example-only" legacyHash="6FPBlIHJ__YC4LBSYdosk"} :::CodeblockTabsExamples ```javascript const CDP_WRITE_KEY = '' const CDP_DOMAIN = 'https://production.cdp.ingest.chord.co' const CHORD_OMS_ID = '' const CHORD_STORE_ID = '' const CHORD_TENANT_ID = '' const DEFAULT_LOCALE = 'en-US' const STORE_DOMAIN = '' const PIXEL_VERSION = '1.0.0' let customerPrivacyStatus = init.customerPrivacy let currency = init.data.cart?.cost?.totalAmount.currencyCode let locale = DEFAULT_LOCALE function getStorefrontAnonymousId() { return document.cookie .split('; ') .find((c) => c.startsWith('__eventn_id=')) ?.split('=')[1] } // ============================================================================ // CDP Initialization (lazy — loads p.js on first checkout event) // ============================================================================ let cdpInitialized = false function initCdp() { if (cdpInitialized) return if (!CDP_WRITE_KEY || !CDP_DOMAIN) return cdpInitialized = true window.chordQ = window.chordQ || [] window.chord = window.chord || { identify: (...args) => window.chordQ?.push((cdp) => cdp?.identify(...args)), page: (...args) => window.chordQ?.push((cdp) => cdp?.page(...args)), track: (...args) => window.chordQ?.push((cdp) => cdp?.track(...args)), } const script = document.createElement('script') script.async = true script.src = `${CDP_DOMAIN}/p.js` script.setAttribute('data-init-only', 'true') script.setAttribute('data-namespace', 'chord') script.setAttribute('data-write-key', CDP_WRITE_KEY) document.head.appendChild(script) const cdpUserId = window.chord?.user?.()?.userId const userId = init.data.customer?.id if (userId && userId !== cdpUserId) { const traits = getInitCustomerTraits(init) cdpIdentify(userId, traits) } } // ============================================================================ // Consent Management // ============================================================================ api.customerPrivacy.subscribe('visitorConsentCollected', (event) => { customerPrivacyStatus = event.customerPrivacy }) ;(function identifyOnLoad() { const customer = init.data.customer if (!customer?.id) return const traits = {} if (customer.email) traits.email = customer.email if (customer.firstName) traits.firstName = customer.firstName if (customer.lastName) traits.lastName = customer.lastName if (customer.phone) traits.phone = customer.phone if (customer.ordersCount) traits.ordersCount = customer.ordersCount forward('identify', customer.id, traits) })() // ============================================================================ // Event Subscriptions — All 13 Shopify events // ============================================================================ // --- Storefront-only events (postMessage only) --- analytics.subscribe('page_viewed', (event) => { forward('page', { path: event.context.document.location.pathname, url: event.context.document.location.href, title: event.context.document.title, }) }) analytics.subscribe('product_viewed', (event) => { const { productVariant } = event.data forward('track', 'Product Viewed', formatProduct(productVariant)) }) analytics.subscribe('product_added_to_cart', (event) => { const { cartLine } = event.data if (!cartLine) return const product = formatCartLine(cartLine) forward('track', 'Product Added', { ...product, products: [product], }) }) analytics.subscribe('product_removed_from_cart', (event) => { const { cartLine } = event.data if (!cartLine) return const product = formatCartLine(cartLine) forward('track', 'Product Removed', { ...product, products: [product], }) }) analytics.subscribe('cart_viewed', (event) => { const { cart } = event.data if (!cart) return forward('track', 'Cart Viewed', { cart_id: cart.id, currency: cart.cost.totalAmount.currencyCode, value: cart.cost.totalAmount.amount, products: cart.lines.map(formatCartLine), }) }) analytics.subscribe('collection_viewed', (event) => { const { collection } = event.data forward('track', 'Product List Viewed', { list_id: collection.id, item_list_id: collection.id, list_name: collection.title, item_list_name: collection.title, products: collection.productVariants.map(formatProduct), }) }) analytics.subscribe('search_submitted', (event) => { forward('track', 'Products Searched', { query: event.data.searchResult.query, }) }) // --- Checkout events (postMessage + direct CDP) --- analytics.subscribe('checkout_started', async (event) => { const { checkout } = event.data // postMessage (sync, fire-and-forget) forward('track', 'Checkout Started', formatCheckout(checkout)) // Direct CDP const coupon = getCoupon(checkout) const discount = getDiscount(checkout) const props = { checkout_type: 'Shopify', coupon, currency: checkout.currencyCode, discount, products: checkout.lineItems.map(getLineItem), revenue: checkout.subtotalPrice.amount, shipping: checkout.shippingLine?.price.amount, tax: checkout.totalTax.amount, value: checkout.subtotalPrice.amount, } await cdpTrack('Checkout Started', props) }) analytics.subscribe('checkout_contact_info_submitted', async (event) => { const { checkout } = event.data // postMessage (sync, fire-and-forget) // Use undefined for userId — email is not a stable ID; the real customer ID // is set at checkout_completed when checkout.order.customer.id is available. forward('identify', undefined, { email: checkout.email, phone: checkout.phone, }) forward('track', 'Checkout Step Completed', { checkout_id: checkout.token, step: 1, step_name: 'Contact Info', }) // Direct CDP const checkoutTraits = getCheckoutTraits(checkout) const initTraits = getInitCustomerTraits(init) const traits = { ...initTraits, ...checkoutTraits, } const userId = traits.id || undefined await cdpIdentify(userId, traits) const props = { checkout_id: checkout.token, step: 1, } await cdpTrack('Checkout Step Completed', props) }) analytics.subscribe('checkout_address_info_submitted', async (event) => { // postMessage (sync, fire-and-forget) forward('track', 'Checkout Step Completed', { checkout_id: event.data.checkout.token, step: 2, step_name: 'Shipping Address', }) // Direct CDP const props = { checkout_id: event.data.checkout.token, step: 2, } await cdpTrack('Checkout Step Completed', props) }) analytics.subscribe('checkout_shipping_info_submitted', async (event) => { // postMessage (sync, fire-and-forget) forward('track', 'Checkout Step Completed', { checkout_id: event.data.checkout.token, step: 3, step_name: 'Shipping Method', }) // Direct CDP const props = { checkout_id: event.data.checkout.token, step: 3, } await cdpTrack('Checkout Step Completed', props) }) analytics.subscribe('payment_info_submitted', async (event) => { const { checkout } = event.data // postMessage (sync, fire-and-forget) forward('track', 'Payment Info Entered', { checkout_id: checkout.token, step: 4, currency: checkout.currencyCode, value: checkout.subtotalPrice.amount, products: checkout.lineItems.map(formatLineItem), }) // Direct CDP const coupon = getCoupon(checkout) const props = { checkout_id: checkout.token, coupon, currency: checkout.currencyCode, products: checkout.lineItems.map(getLineItem), step: 4, value: checkout.subtotalPrice.amount, } await cdpTrack('Payment Info Entered', props) }) analytics.subscribe('checkout_completed', async (event) => { const { checkout } = event.data // postMessage (sync, fire-and-forget) const userId = checkout.order?.customer?.id || undefined forward('identify', userId, { email: checkout.email, phone: checkout.phone, firstName: checkout.shippingAddress?.firstName, lastName: checkout.shippingAddress?.lastName, }) forward( 'track', 'Order Completed', formatOrderCompleted(checkout, event.timestamp) ) // Direct CDP const coupon = getCoupon(checkout) const discount = getDiscount(checkout) const orderProps = { checkout_id: checkout.token, checkout_type: 'Shopify', coupon, currency: checkout.currencyCode, discount, email: checkout.email || undefined, first_name: checkout.shippingAddress?.firstName || undefined, last_name: checkout.shippingAddress?.lastName || undefined, order_date: event.timestamp, order_id: checkout.order?.id, phone: checkout.phone || undefined, products: checkout.lineItems.map((item, i) => { const price = item.variant?.price.amount const itemDiscount = item.discountAllocations.reduce( (acc, { amount }) => acc + (amount.amount || 0), 0 ) const revenue = price ? (item.quantity || 1) * price - itemDiscount : 0 return { ...getLineItem(item, i), revenue, } }), revenue: checkout.subtotalPrice.amount, shipping: checkout.shippingLine?.price.amount, shipping_city: checkout.shippingAddress?.city || undefined, shipping_country: checkout.shippingAddress?.country || undefined, shipping_state: checkout.shippingAddress?.province || undefined, shipping_zipcode: checkout.shippingAddress?.zip || undefined, subtotal: checkout.subtotalPrice.amount, tax: checkout.totalTax.amount, total: checkout.totalPrice.amount, } const checkoutTraits = getCheckoutTraits(checkout) const initTraits = getInitCustomerTraits(init) const traits = { ...initTraits, ...checkoutTraits, } const cdpUserId = traits.id || undefined await cdpIdentify(cdpUserId, traits) await cdpTrack('Order Completed', orderProps) }) function forward(type, ...args) { try { const target = typeof window !== 'undefined' && window.top ? window.top : self target.postMessage( { source: 'chord-web-pixel', type, payload: args, }, '*' ) } catch (err) { // Silently fail if postMessage is not available } } // ============================================================================ // Lightweight Data Formatters (for postMessage forwarding) // ============================================================================ function formatProduct(variant) { const product = variant?.product return { product_id: product?.id, sku: variant?.sku, name: product?.title || product?.untranslatedTitle, price: variant?.price?.amount, currency: variant?.price?.currencyCode, category: product?.type, brand: product?.vendor, variant: variant?.title || variant?.untranslatedTitle, variant_id: variant?.id, image_url: variant?.image?.src, url: product?.url, } } function formatCartLine(cartLine) { const variant = cartLine.merchandise const product = variant?.product return { product_id: product?.id, sku: variant?.sku, name: product?.title || product?.untranslatedTitle, price: variant?.price?.amount, currency: cartLine.cost.totalAmount.currencyCode, quantity: cartLine.quantity, category: product?.type, brand: product?.vendor, variant: variant?.title || variant?.untranslatedTitle, variant_id: variant?.id, image_url: variant?.image?.src, url: product?.url, value: cartLine.cost.totalAmount.amount, } } function formatLineItem(item, index) { const variant = item.variant const product = variant?.product return { product_id: product?.id, sku: variant?.sku, name: product?.title || product?.untranslatedTitle, price: variant?.price?.amount, quantity: item.quantity, category: product?.type, brand: product?.vendor, variant: variant?.title || variant?.untranslatedTitle, variant_id: variant?.id, image_url: variant?.image?.src, url: product?.url, position: typeof index === 'number' ? index + 1 : undefined, } } function formatCheckout(checkout) { const discount = checkout.lineItems.reduce((acc, item) => { return ( acc + item.discountAllocations.reduce( (sum, d) => sum + (d.amount.amount || 0), 0 ) ) }, 0) const coupon = checkout.discountApplications.find((d) => { if ('amount' in d.value) return d.value.amount > 0 return d.value.percentage > 0 })?.title return { checkout_id: checkout.token, currency: checkout.currencyCode, value: checkout.subtotalPrice.amount, revenue: checkout.subtotalPrice.amount, shipping: checkout.shippingLine?.price?.amount, tax: checkout.totalTax?.amount, discount, coupon, products: checkout.lineItems.map(formatLineItem), } } function formatOrderCompleted(checkout, timestamp) { const base = formatCheckout(checkout) return { ...base, order_id: checkout.order?.id, order_date: timestamp, total: checkout.totalPrice.amount, subtotal: checkout.subtotalPrice.amount, email: checkout.email, phone: checkout.phone, first_name: checkout.shippingAddress?.firstName, last_name: checkout.shippingAddress?.lastName, shipping_city: checkout.shippingAddress?.city, shipping_state: checkout.shippingAddress?.province, shipping_country: checkout.shippingAddress?.country, shipping_zipcode: checkout.shippingAddress?.zip, } } // ============================================================================ // Direct CDP Methods (for checkout events in the sandbox) // ============================================================================ function cdpEnabled() { if (window.chord) return true if (!CDP_WRITE_KEY || !CDP_DOMAIN) return false initCdp() return !!window.chord } async function cdpIdentify(userId, traits) { if (!cdpEnabled()) return const options = await getOptions() const anonymousId = getStorefrontAnonymousId() await window.chord.identify(userId, traits, { ...options, ...(anonymousId && { anonymousId, }), context: { page: options.page, }, }) } async function cdpTrack(event, props) { if (!cdpEnabled()) return const options = await getOptions() const meta = await getMeta() const anonymousId = getStorefrontAnonymousId() await window.chord.track( event, { ...props, meta, context: { page: options.page, }, }, { ...options, ...(anonymousId && { anonymousId, }), } ) } // ============================================================================ // CDP Options & Metadata // ============================================================================ async function getCategoryPreferences() { return { analytics: customerPrivacyStatus?.analyticsProcessingAllowed, marketing: customerPrivacyStatus?.marketingAllowed, preferences: customerPrivacyStatus?.preferencesProcessingAllowed, sale_of_data: customerPrivacyStatus?.saleOfDataAllowed, } } async function getOptions() { const categoryPreferences = (await getCategoryPreferences()) || {} return { consent: { categoryPreferences, }, page: { path: init.context.document.location.pathname, url: init.context.document.location.href, }, } } async function getMeta() { if (!currency) { currency = await browser.cookie.get('cart_currency') } return { i18n: { currency, locale, }, ownership: { oms_id: CHORD_OMS_ID, store_id: CHORD_STORE_ID, tenant_id: CHORD_TENANT_ID, }, platform: { name: 'Shopify', type: 'web', }, store: { domain: STORE_DOMAIN, }, version: { major: 3, minor: 0, patch: 0, }, } } // ============================================================================ // Rich Data Formatters (for direct CDP — adapted from legacy pixel) // ============================================================================ function getLineItem(item, position) { const variant = 'variant' in item ? item.variant : item.merchandise const product = variant?.product const discountAllocations = 'discountAllocations' in item ? item.discountAllocations : undefined const coupon = discountAllocations?.find((al) => al?.amount?.amount > 0) ?.discountApplication.title return { brand: product?.vendor, category: product?.type || undefined, coupon, image_url: variant?.image?.src, line_item_id: 'id' in item ? item.id : undefined, name: product?.title || product?.untranslatedTitle, position: typeof position === 'number' ? position + 1 : undefined, price: variant?.price.amount, product_id: product?.id, quantity: ('quantity' in item && item.quantity) || undefined, sku: variant?.sku || undefined, url: product?.url, variant: variant?.title || variant?.untranslatedTitle || undefined, variant_id: variant?.id, } } function getDiscount(checkout) { return checkout.lineItems.reduce((acc, item) => { const { discountAllocations } = item const discount = discountAllocations.reduce((innerAcc, { amount }) => { return innerAcc + (amount.amount || 0) }, 0) return acc + discount }, 0) } function getCoupon(checkout) { return checkout.discountApplications.find(({ value }) => { if ('amount' in value) return value.amount > 0 return value.percentage > 0 })?.title } function getCheckoutTraits(checkout) { const traits = {} if (checkout.email) traits.email = checkout.email if (checkout.phone) traits.phone = checkout.phone const customerId = checkout.order?.customer?.id if (customerId) traits.id = customerId return traits } function getInitCustomerTraits(init) { const { customer } = init.data const traits = {} if (customer?.email) traits.email = customer.email if (customer?.firstName) traits.firstName = customer.firstName if (customer?.id) traits.id = customer.id if (customer?.lastName) traits.lastName = customer.lastName if (customer?.ordersCount) traits.ordersCount = customer.ordersCount if (customer?.phone) traits.phone = customer.phone return traits } ``` ::: :::CodeblockTabsResponses ```javascript ``` ::: :::: [title] Triple Whale [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ ## Introduction Triple Whale is a unified e-commerce attribution and analytics platform that offers advanced tracking, attribution modeling, and real-time insights across channels and customer touchpoints. Connecting Triple Whale as a destination allows you to send user-level events and interactions collected via Chord directly to Triple Whale — enabling centralized attribution, funnel analysis, and behavioral insights while preserving your brand’s data context. ## Getting started As a **device-mode** destination, Triple Whale receives data from client-side tracking implemented via Chord. Before connecting, ensure: - You already have a Triple Whale account and the appropriate site or store configured; - Your site’s frontend includes necessary tracking setup (tracking code or pixel) compatible with Triple Whale; and - You have authorization to add or change tracking destinations. ## Connecting to the Triple Whale CDP destination :::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. *** ::: 1. Log into the **Chord Data Platform.** 2. Go to the **CDP → Destinations** section. 3. Click **“Add”** to browse available destinations. 4. Select **Triple Whale** from the catalog. 5. Enter a **Destination Name** (e.g., “Triple Whale — Production”). 6. Provide the **Store Identifier **and **Platform **your store is running on. 7. Click **Create** to activate the destination. Once connected, Chord will automatically route relevant user events and interactions (page views, conversions, identity data, etc.) to Triple Whale. ## Best practices & conflict avoidance Before enabling Triple Whale via Chord, we recommend: - Disabling any legacy or manually added Triple Whale tracking scripts/pixels to avoid **duplicate event firing and inflated data** - Coordinating with your engineering or analytics team to ensure single source-of-truth for tracking and user identity (avoid multiple overlapping tracking solutions) - Confirming tracking consent and privacy compliance if you manage user data under GDPR/CCPA or similar regulations Running parallel tracking outside of Chord’s configuration may lead to inconsistent analytics, inaccurate attribution, or data duplication. ## Troubleshooting & FAQs **Q: I’m seeing duplicate pageviews or conversions in Triple Whale — what should I check?** - Verify that you haven’t also installed Triple Whale tracking manually (outside of Chord). Duplicate scripts/pixels can cause double-counting. **Q. What if some user attributes or events aren’t appearing in Triple Whale?** - Ensure that the Chord tracking configuration includes the necessary signals, and that your user identity mapping (e.g., user ID, email) is properly populated in Chord before events fire. **Q. Does Triple Whale overwrite my existing data warehouse or analytics stack?** - No — Triple Whale operates as a destination for analytic and attribution data. If you rely on a separate warehouse or BI stack, treat Triple Whale as a complementary analytics solution rather than a full replacement. [title] Custom storefront consent management [path] Chord Event Tracking/Getting started/Custom storefront/ For custom storefronts, Chord supports consent management through third-party consent management platforms (CMPs). This guide covers integrating your CMP with Chord's analytics library. ## Supported Consent Providers The `@chordcommerce/analytics` library supports the following consent adapters: | Provider | `consent` Value | | -------- | --------------- | | OneTrust | `"onetrust"` | | Ketch | `"ketch"` | ## Configuration To enable consent management, add the `consent` and optionally `awaitConsent` options when initializing: ```typescript const chord = new ChordAnalytics({ consent: 'onetrust', // Your consent provider awaitConsent: true, // Wait for consent before sending events cdpDomain: process.env.CHORD_DOMAIN, cdpWriteKey: process.env.CHORD_WRITE_KEY, // ... rest of config }) ``` ### Options | Option | Type | Default | Description | | -------------- | --------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `consent` | `string` | — | The consent adapter to use: `"onetrust"` or `"ketch"` | | `awaitConsent` | `boolean` | `false` | If `true`, delays sending events until consent is given. Events will queue but not forward to destinations until consent is granted. Timeout is 1 minute — if consent is not given within that time, events are dropped. | ## How It Works When a consent adapter is configured: 1. Chord reads the customer's consent preferences from your CMP. 2. A consent object is attached to every event sent to Chord. 3. Chord uses your configured consent category mappings to determine which destinations receive each event. ## Configuring Consent Categories in Chord Navigate to **Consent Categories** in the Chord platform to create consent category mappings. Map each category from your CMP to the appropriate destinations. For each category, choose which destinations should receive events when the customer has consented to that category. Destinations not mapped to any category will receive all events regardless of consent. | ***Consent Value*** | ***Category Keys Reported*** | ***Source*** | | ------------------- | --------------------------------------------------------------------------- | ---------------------------------------- | | `onetrust` | OneTrust group IDs — `C0001`, `C0002`, `C0003`, … plus any custom group IDs | `GetDomainData().Groups[].CustomGroupId` | | `cookiebot` | `necessary`, `preferences`, `statistics`, `marketing` | `window.Cookiebot.consent` | | `ketch` | Your Ketch purpose keys — no fixed list, whatever is in the object | `window.ketchConsent` | | `shopify` | `analytics`, `marketing`, `preferences`, `sale_of_data` | Customer Privacy API | | `segment` | `customPreference`s keys merged with `destinationPreferences` keys | `window.segmentConsent` | | | | | ## OneTrust If using OneTrust as your CMP: 1. Install and configure OneTrust on your site according to their documentation. 2. Set `consent: "onetrust"` in your Chord configuration. 3. Chord will automatically read consent preferences from OneTrust's API and include them with events. ## Without a Supported CMP If your consent management platform is not in the supported list, you can manage consent manually using the generic `track` method to include consent data, or contact [help@chord.co](mailto\:help@chord.co) to discuss adding support for your provider. [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] TikTok Pixel [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ The **TikTok Pixel** destination loads the TikTok Pixel JavaScript SDK in the browser and forwards ecommerce and engagement events client-side to TikTok Ads. Unlike the [server-side TikTok Conversions API destination](#), device-mode events originate from the browser and can leverage the full TikTok Pixel feature set. Use this destination alongside the [TikTok Conversions API destination](#) for maximum signal coverage. # Getting Started This is a device-mode destination. The TikTok Pixel SDK is loaded automatically — no manual script installation is required. You will need: - **Pixel Code** — your TikTok Pixel ID, found in your TikTok Ads Manager under **Assets > Events > Web Events**. Optionally: - **Limited Data Use (LDU)** — enable Limited Data Use mode for CCPA compliance. Defaults to `false`. - **Auto Page View** — automatically fire a page view on pixel initialization. Defaults to `true`. - **Product Content ID Field** — which product field to use as the content ID: `product_id`, `sku`, `variant_id`, or `id`. Defaults to `sku` > `product_id` > `id` fallback chain. # Connecting to the TikTok 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 **TikTok Pixel** from the destination catalog. 5. Enter the destination name and your **Pixel Code**. 6. Configure optional settings as needed. 7. Click **"Create"** to connect. # Events Every event first calls `ttq.identify()` with available user data before sending the conversion event. # Event Mapping | Chord Event | TikTok Event | Notes | | --------------------------- | ----------------------------- | ------------------------------------------------------------------------------------------------------------------- | | `page` | *(auto page view on init)* | Fires during initialization when **Auto Page View** is `true`; subsequent page events send user identification only | | `identify` | `ttq.identify()` | Sets user data; no conversion event fired | | `Order Completed` | `CompletePayment` | Multi-product | | `Checkout Started` | `InitiateCheckout` | Multi-product | | `Payment Info Entered` | `AddPaymentInfo` | Multi-product | | `Product Added` | `AddToCart` | Single-product | | `Product Viewed` | `ViewContent` | Single-product | | `Product Clicked` | `ClickButton` | Single-product | | `Product Added to Wishlist` | `AddToWishlist` | Single-product | | `Products Searched` | `Search` | Single-product | | `Signed Up` | `CompleteRegistration` | No product data | | `Subscription Created` | `Subscribe` | No product data | | *(any other track event)* | Chord event name passed as-is | See [Custom Events](#) | # Identify Sets user identity on the TikTok pixel for enhanced matching. No conversion event is fired. **TikTok SDK call:** `ttq.identify(userData)` | TikTok Attribute | Chord Source (Priority Order) | Notes | | --------------------------------------- | ------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------- | | `email` or `sha256_email` | `properties.email` > `context.traits.email` > `traits.email` | Routed to `sha256_email` if value is a SHA-256 digest; otherwise sent to `email` and TikTok hashes automatically | | `phone_number` or `sha256_phone_number` | `properties.phone` > `context.traits.phone` > `traits.phone` | Routed to `sha256_phone_number` if value is a SHA-256 digest; otherwise sent to `phone_number` in E.164 format | | `external_id` | `userId` > `anonymousId` | | | `first_name` | `properties.first_name` > `context.traits.first_name` > `traits.first_name` | Lowercased, whitespace removed | | `last_name` | `properties.last_name` > `context.traits.last_name` > `traits.last_name` | Lowercased, whitespace removed | | `city` | `properties.address.city` > `context.traits.address.city` | Lowercased, non-alphanumeric chars removed | | `state` | `properties.address.state` > `context.traits.address.state` | Lowercased, non-alphanumeric chars removed | | `country` | `properties.address.country` > `context.traits.address.country` | Lowercased, non-alphanumeric chars removed | | `zip_code` | `properties.address.zipcode` > `context.traits.address.zipcode` > `traits.address.zipcode` | Lowercased, whitespace removed | Identify is automatically called before every track event if any user data is available. # PII Handling TikTok's `track()` event schema does not include PII fields. Email, phone, and name belong exclusively in `ttq.identify()`, where TikTok automatically hashes them client-side using SHA-256 before transmission. To prevent accidental PII exposure, the following fields are **always stripped** from track event payloads even if they appear in `event.properties` or are written there by a property mapping: | Field | Why stripped | | -------------- | --------------------------- | | `email` | Handled by `ttq.identify()` | | `phone` | Handled by `ttq.identify()` | | `phone_number` | Handled by `ttq.identify()` | | `first_name` | Handled by `ttq.identify()` | | `last_name` | Handled by `ttq.identify()` | If you have a property mapping that writes to one of these fields (e.g. `properties.email → properties.email`), the value will still flow to `ttq.identify()` through the normal user data extraction path — it will not appear in the `track()` payload. # Multi-Product Events (Order Completed, Checkout Started, Payment Info Entered) **TikTok SDK call:** `ttq.instance(pixelCode).track(eventName, eventProperties, { event_id: messageId })` | TikTok Attribute | Chord Source (Priority Order) | Notes | | ---------------- | --------------------------------------- | ------------------------------------------------------- | | `content_type` | *(hardcoded)* `"product"` | | | `currency` | `properties.currency` | Defaults to `"USD"` | | `value` | `properties.value` > `properties.total` | Falls back to sum of `price × quantity` across products | | `order_id` | `properties.order_id` | | | `shop_id` | `properties.shop_id` | | | `description` | `properties.products[0].description` | From first product | | `contents` | `properties.products[]` mapped as below | | **Product contents** — each item in `properties.products[]`: | TikTok Attribute | Chord Source | | ------------------ | -------------------------------------------------------------------- | | `content_id` | Configured field from `properties.products[]` > `sku` > `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 (Product Added, Product Viewed, Product Clicked, Product Added to Wishlist, Products Searched) Product data is extracted from top-level `properties` (not `properties.products[]`). **TikTok SDK call:** `ttq.instance(pixelCode).track(eventName, eventProperties, { event_id: messageId })` | TikTok Attribute | Chord Source (Priority Order) | Notes | | ---------------- | ------------------------------------------------------------ | ---------------------- | | `content_type` | *(hardcoded)* `"product"` | | | `currency` | `properties.currency` | Defaults to `"USD"` | | `value` | `properties.value` > `properties.total` > `properties.price` | | | `order_id` | `properties.cart_id` / `properties.order_id` | Omitted if not present | | `shop_id` | `properties.shop_id` | Omitted if not present | | `description` | `properties.description` | | | `query` | `properties.query` | Products Searched only | | `contents` | Single-element array from top-level `properties` | | **Single product content:** | TikTok Attribute | Chord Source (Priority Order) | | ------------------ | ------------------------------------------------------------------------------- | | `content_id` | Configured field from `properties` > `properties.sku` > `properties.product_id` | | `content_name` | `properties.name` | | `content_category` | `properties.category` | | `price` | `properties.price` | | `quantity` | `properties.quantity` — defaults to `1` | | `brand` | `properties.brand` | # No-Product Events (Signed Up, Subscription Created) Same event-level attributes as multi-product events above, but `contents` is an empty array. # 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. This includes events like `Form Submitted`, `Callback Started`, `Download Link Clicked`, and any other custom event names your storefront fires. **TikTok SDK call:** `ttq.instance(pixelCode).track(eventName, eventProperties, { event_id: messageId })` The payload uses the same structure as multi-product events — if the event carries `products`, `currency`, `value`, or order data in its properties, those are extracted and forwarded. Custom properties from property mappings are also included. | TikTok Attribute | Chord Source | Notes | | ---------------- | --------------------------------------------------------- | ----------------------------------------------------------- | | `content_type` | *(hardcoded)* `"product"` | | | `currency` | `properties.currency` | Defaults to `"USD"` | | `value` | `properties.value` > `properties.total` | Falls back to sum of `price × quantity` if products present | | `order_id` | `properties.order_id` | Omitted if not present | | `contents` | `properties.products[]` if present, otherwise empty array | | 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. # Custom Property Forwarding Configure destination mappings in Hub with `properties.*` destination paths to forward additional event properties alongside the computed schema fields in the `ttq.instance(...).track(...)` payload. 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 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`) — see [PII Handling](#); these are always stripped from track event payloads and handled by `ttq.identify()` instead 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 sets up the `ttq` function queue, then loads `https://analytics.tiktok.com/i18n/pixel/events.js`. The partner name is set to `"Chord"`. If **Auto Page View** is `true` (default), an initial page view is fired immediately after initialization. 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://analytics.tiktok.com` | | `connect-src` | `https://analytics.tiktok.com` | *** **Updated 27 May 2026** [title] Google Analytics 4 [path] Chord Event Tracking/Guides/Integrations/ Segment has two GA4 destinations, the [Google Analytics 4 Web Destination](https://segment.com/docs/connections/destinations/catalog/actions-google-analytics-4-web/) and the [Google Analytics 4 Cloud Destination](https://segment.com/docs/connections/destinations/catalog/actions-google-analytics-4/). The Google Analytics 4 Web destination can only be connected to website front-end Segment sources. When enabled, Segment will load the gtag.js library for you and sends tracking events to GA4 via gtag.js. The Google Analytics 4 Cloud destination can be connected to any Segment source, and sends tracking events directly to [Google’s Measurement Protocol API](https://developers.google.com/analytics/devguides/collection/protocol/ga4). We recommend configuring two GA4 Segment destinations to capture events from both the website front-end, which sends events for browsing activity, and from Chord's server source, which sents events for transactions in the OMS. This will give you the fullest picture of user activity in GA4. ## Using with Chord’s server source Add a [Google Analytics 4 Cloud Destination](https://segment.com/docs/connections/destinations/catalog/actions-google-analytics-4/) destination and connect to your Chord server source. Be sure to enter your **Measurement ID** and **API Secret** in the destination settings. To send Segment events to GA4 events, we need to add mappings. Select **Add Mapping** in the destination configuration to add pre-built mappings and actions. The following pre-built mappings are supported by the Chord server source: - `Begin Checkout` maps to Chord’s `Checkout Started` - `Purchase` maps to Chord’s `Order Completed` - `Refund` maps to Chord’s `Order Refunded` ### Identifying users The default mappings for the Google Analytics 4 Cloud destination do not include the enough data for GA4 to be able to connect the events to website front-end activity. There are two additional event mappings you can add to fix this, the Google Client ID and the user's ID. **Client ID** To tie together front-end and server Segment events as one session within GA4, you can send the Gtag-generated Client ID from the front end as the Client ID with the server events. Chord includes the Gtag-generated Client ID from the front-end on server events as the property `integrations.Google Analytics.clientId`. To sent the Client ID to GA4, edit each mapping and find the **Client ID** property. It is blank by default: ![Client ID mapping](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/kyZWmt6cL_U24MzUHZzVg_image.png) Select the text input to the left, and in the **Event Variables** search bar, enter the text `integrations.Google Analytics.clientId`. Unless you have test data loaded, it will likely say "Not matches found," which is fine. Select **Use "integrations.Google Analytics.clientId" as an event variable**: ![Client ID mapping selected](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/l5BUeghjfg2wz2Xju0FIg_image.png) Now you should see this: ![Client ID mapping completed](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/pKeccOQrHglXRVJchAMWR_image.png) If events throw "Client ID is required for web streams" errors, it is because the destination requires a Client ID for all events. This is happening because the corresponding session must not have had front end events with a synced Client ID. To remedy this, you can use Segment's `coalesce` function to fall back to the `userId`, similar to what the destination would have used by default, as documented [here](https://segment.com/docs/connections/destinations/catalog/actions-google-analytics-4/#user-identification). ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/zJp4uRztsWllThUl6jYSn_screenshot-2024-10-10-at-92212-am.png) **User ID** Optionally, you can send the Segment user ID, which is typically the user or customer ID from the OMS, to GA4 with every event for an authenticated user. (The user ID is not available for guest activity.) This allows [GA4 to connect user behavior](https://support.google.com/analytics/answer/9213390) across sessions and devices. To sent the user ID to GA4, edit each mapping and find the **User ID** property. It is blank by default. Select the text input to the left, and in the **Event Variables** search bar, enter the text `userId`. Now you should see: ![User ID mapping](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/8YKex9iXof9wNjfaKXWPX_image.png) ## Using with Chord’s website front-end source Add a [Google Analytics 4 Web destination](https://segment.com/docs/connections/destinations/catalog/actions-google-analytics-4-web/) and connect to your website front-end source. Select **Add Mapping** in the destination configuration to add pre-built mappings and actions. The following pre-built actions can be added without any adjustment to the mappings, if Chord is sending the corresponding event to Segment: - `Add to Cart` maps to Chord’s `Product Added` - `Search` maps to Chord’s `Products Searched` - `Select Item` maps to Chord’s `Product Clicked` - `View Item List` maps to Chord’s `Product List Viewed` - `Sign Up` maps to Chord’s `Signed Up` - `View Cart` maps to Chord’s `Cart Viewed` - `Purchase` maps to Chord’s `Order Completed` - `View Promotion` maps to Chord’s `Promotion Viewed` - `Add to Wishlist` maps to Chord’s `Product Added to Wishlist` - `Remove from Cart` maps to Chord’s `Product Removed` - `Select Promotion` maps to Chord’s `Promotion Clicked` - `View Item` maps to Chord’s `Product Viewed` - `Begin Checkout` maps to Chord’s `Checkout Started` - `Login` maps to Chord’s `Signed In` ### Identifying users Optionally, you can send the Segment user ID, which is typically the user or customer ID from the OMS, to GA4 with every event for an authenticated user. (The user ID is not available for guest activity.) This allows [GA4 to connect user behavior](https://support.google.com/analytics/answer/9213390) across sessions and devices. To sent the user ID to GA4, edit each mapping and find the **User ID** property. It is blank by default. Select the text input to the left, and in the **Event Variables** search bar, enter the text `userId`. Now you should see: ![User ID mapping](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/8YKex9iXof9wNjfaKXWPX_image.png) [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] Custom events [path] Chord Event Tracking/ A **custom event** is any event Chord receives that is not part of the Chord tracking plan — either an event whose name is not one of the canonical events (`Order Completed`, `Product Viewed`, `Checkout Started`, `Product Added`, …) or a canonical event carrying non-standard properties. This document explains what happens to those events: how they are processed, what transformation (if any) is applied, and which destinations forward them. # The short answer **Chord does not validate events against the tracking plan, and it does not** **reject, quarantine, or strip events for being non-compliant.** Every event that is ingested flows through the same pipeline. Custom events are processed **as-is**, with only the minimal, optional transformations described below, and are forwarded to destinations. What a custom event ultimately looks like at a destination depends entirely on that destination, because each destination decides how to map an event to its own schema. Some forward custom events verbatim; some only act on a fixed set of canonical events and silently ignore everything else. :::BlockQuote **The tracking plan is a convention, not a schema validator.** It defines a set of canonical event names and snake\_case field names (`email`, `phone`, `first_name`, `address1`, `zipcode`, …). Destination code uses these canonical names as *fallback lookups* when extracting properties. There is no component anywhere in ingest, Rotor, or the destination functions that checks an incoming event against the plan and blocks it for failing to match. ::: # How an event is processed Every event — canonical or custom — travels the same path: ```javascript Chord SDK / S2S → Ingest → Kafka → Rotor (function chain) → Destination ``` Inside Rotor, the function chain applies a series of transformations. **None of** **these steps inspect whether an event complies with the tracking plan.** They treat a custom event exactly as they treat a canonical one: | Step | What it does | Applies to custom events? | | ------------------------ | --------------------------------------------------------------------- | -------------------------------------------------------------------------------- | | **Geo enrichment** | Resolves `context.ip` to `context.geo` (browser events only) | Yes, identically | | **User recognition** | Merges anonymous events with known identity (if configured) | Yes, identically | | **Connection filters** | Drop/allow rules matching on event type, name, or property values | Yes — *can* drop a custom event if a rule names it, but not because it is custom | | **Property mappings** | Customer-defined field remapping (`@jitsu/mapping-engine`) | Yes, identically | | **Consent filtering** | Drops events lacking required consent categories | Yes, identically | | **Deduplication** | Skips repeat messages within a Redis-backed window (if enabled) | Yes, identically | | **UDFs** | Custom JavaScript transforms that can modify, drop, or fan-out events | Yes, identically | | **Destination function** | Maps the event to the destination's API/schema | **Destination-specific — see below** | The only places an event is ever dropped are: a connection filter rule, consent enforcement, a UDF returning `null`/`"drop"`, deduplication, or a destination deliberately not firing. A custom event is **never** dropped merely for being absent from the tracking plan. # How destinations handle custom events This is where behavior diverges. There are two delivery modes, and within each, destinations fall into a few distinct patterns. ## Cloud-mode destinations (server-side) These run as functions in Rotor. The dominant pattern is **passthrough**: the event name and properties are forwarded with little or no transformation, so custom events arrive intact. | Pattern | Behavior for custom events | Examples | | -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | | **Passthrough** | Event forwarded as-is; the event name is used directly | Webhook, Segment, MongoDB, Data Warehouse / Bulker, June, Intercom, Heap, Mixpanel, PostHog | | **Canonical mapping + fallback** | Canonical events are translated to the destination's standard event; unmapped (custom) events still go through via a `default` fallback | GA4 (custom name is handelized/kebab-cased, standard props filtered), Facebook Conversions (custom name passed through unchanged) | | **Configurable mapping** | The destination acts only on events the customer has explicitly mapped | Amplitude (supports a `$drop` mapping), Braze (purchase-event list, otherwise generic track) | | **Identity / fixed-purpose** | Built around `identify`/`group` or a small set of events; track-style custom events get generic treatment or none | Klaviyo (special-cases `Order Completed`, all other tracks become generic metrics), HubSpot, Salesforce | Data warehouse destinations are the most permissive: a custom track event simply gets its own table named after the event (e.g. `my_custom_event`), or its raw document inserted (MongoDB). :::BlockQuote Even canonical-mapping destinations like GA4 and Facebook do **not** drop custom events — they fall through to a default branch that still sends the event under its own (optionally normalized) name. ::: ## Device-mode destinations (client-side) Device-mode plugins (`libs/jitsu-js/src/destination-plugins/`) fire directly from the browser via each vendor's pixel/SDK. Per the forwarding policy above, every plugin handles the unrecognized-event case explicitly — it either forwards the event or logs an explicit skip. | Pattern | Behavior for custom events | Examples | | ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Passthrough** | An unrecognized event name is forwarded to the vendor SDK under its own name (or as a generic "custom event") | Facebook Pixel (`trackSingleCustom`), TikTok Pixel, Pinterest Tag, Insider Pixel, Bing Ads, StackAdapt Pixel, Dotdigital Tag (`event()`), Google Tag Manager (pushed to the Data Layer as `event: ""`; triggers and tags decide what happens next) | | **Fixed-taxonomy (explicit skip)** | Only the platform's recognized events fire; unrecognized events are skipped with a `console.warn` | Snap Pixel, Northbeam Pixel, Reddit Pixel, Retention.com, Postie, Spotify Ad Analytics Pixel, OpenAI Ads Pixel and Conversions API, Nosto Tag and Nosto | | **Config-driven** | Fires only for events the customer mapped in the plugin's configuration; everything else (including unmapped canonical events) is skipped | Twitter Ads (`eventMapping`), Google Ads (`clickConversions` / `pageLoadConversions`) | :::BlockQuote **If you need to send high-cardinality or custom-named events to an ad platform, choose a passthrough plugin.** Fixed-taxonomy plugins (Snap, Reddit, Spotify, etc.) are scoped to the conversion events the vendor's backend recognizes; they will skip anything outside that set and log a warning so the skip is visible. ::: ## Custom property mappings Custom *property* mappings are a separate mechanism from custom event names. When a customer maps a property in Hub (e.g. `properties.customer_type →` `customer_type`), the dispatcher writes it as a top-level key on the event. A plugin only carries it into the outgoing payload if the plugin spreads `getCustomMappedProperties` / `getCustomDataProperties` — in which case the custom property reaches the destination even on a fixed event set. **Not every plugin does this.** Plugins that build a hardcoded payload from formatters (`formatOrderData`, etc.) without that spread silently drop custom-mapped properties. Today the plugins that forward them are `facebook-pixel`, `snap-pixel`, `tiktok-pixel`, `pinterest-tag`, `twitter-ads`, `bing-ads`, `google-ads`, `reddit-pixel`, and `dotdigital-tag` (on its custom-event call only — see below); fixed-taxonomy plugins such as `spotify-ad-analytics-pixel`, `postie`, `retention`, `northbeam-pixel`, `sfmc-collect`, `thetradedesk-pixel`, and `yahoo-pixel` do not. (PII fields like email and phone are excluded from this passthrough regardless.) **Forwarding is not the same as being used.** `reddit-pixel` forwards custom properties and Reddit accepts them without error, but Reddit publishes a fixed metadata list (`conversion_id`, `currency`, `item_count`, `value`, `products`) with no general-purpose container, and does not document what becomes of anything else. So the property reaches the vendor and may still be inert. Where a vendor neither documents a passthrough field nor rejects unknown keys, say so in the destination doc rather than implying the mapping works — an operator who builds reporting on a silently-discarded property is worse off than one who was told nothing. **A closed vendor schema can make forwarding impossible, not merely absent.** `openai-ads-pixel` is the first plugin in this category. OpenAI validates the event against a fixed schema — the conversion data accepts only `type`, `amount`, `currency`, `contents` and `plan_id`, and there is no `custom_data` slot like Meta's or TikTok's. An unknown key is not ignored: the SDK logs `validation failed; event dropped` and the conversion never leaves the browser. So for that destination the convention inverts. It exists to stop custom properties being silently lost; here, forwarding them silently loses the entire event, which is strictly worse. The plugin therefore sends none, and its `custom-property-mapping.test.ts` asserts the *exclusion* so the exception reads as a decision rather than an oversight. **A closed vendor API can make forwarding impossible, not merely absent.** `nosto-tag` is the second plugin in this category and the clearer case: Nosto's browser API has no property bag *at all*. Each method takes a fixed signature, and its cart, customer and order objects are closed shapes — there is no `custom_data` like Meta's, no `properties` like TikTok's, and no key Nosto would read. A custom property has nowhere to go on either Nosto surface, so both skip it and both public docs say so rather than leaving an operator to discover it. **A vendor can have an extensibility field on some calls and none on others.** `dotdigital-tag` is the case that does not fit either bucket cleanly. Dotdigital's `event()` takes an arbitrary attribute bag, so custom properties are forwarded there — but every other method it exposes (`identify`, `productBrowse`, `productList`, `cartUpdate`, `checkout`, `purchaseComplete`) takes a fixed signature with no property bag, so they get none. The plugin therefore spreads on exactly one call, and its `custom-property-mapping.test.ts` asserts both halves: that mapped properties arrive on the custom-event path, and that they cannot appear on a commerce payload where Dotdigital defines the field names itself. The public doc states the split, because an operator configuring a mapping needs to know which events it reaches. Before adding the usual spread to a new plugin, check whether the vendor has an extensibility field at all — and check it per call, not per vendor. If it does not, omit the spread and pin that with a test. # Custom event forwarding policy Across destinations, the behaviors above are not all intentional — some are genuine vendor constraints and some are implementation gaps. To keep current and future destinations consistent, Chord follows one rule: :::BlockQuote **Every destination must handle the unrecognized-event case explicitly. It either forwards the event or logs an explicit skip — it must never fall through silently.** ::: A silent fall-through (a `switch` with no `default`) is the thing to avoid: it drops events with no signal in the logs, so a custom event that never arrives at a destination looks identical to one that was delivered. That is the worst outcome for debugging. ## Two buckets Each destination belongs to one of two buckets, chosen by **what the receiving** **platform actually does with an unrecognized event** — not by whether the event *can* be transmitted: | Bucket | Default for unrecognized events | Why | | ----------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------- | | **Passthrough-capable** — general-purpose collectors and platforms with a real custom-event API | **Forward** the event under its own name (with custom-mapped properties) | The platform stores or acts on arbitrary events, so forwarding is useful | | **Fixed-taxonomy** — attribution pixels whose backend only recognizes a closed set of events | **Skip with an explicit **`console.warn` | The platform discards or rejects unrecognized events, so forwarding would be a no-op that falsely reads as "delivered" | Examples of **passthrough-capable**: Webhook, Data Warehouse / Bulker, MongoDB, Mixpanel, PostHog, GA4, Facebook (pixel via `trackSingleCustom` / Conversions API via a custom `event_name`), TikTok, Pinterest, Insider, Bing, Dotdigital (the Tag's `event()` and the v3 events import both create an Insight data collection for any non-reserved name). Examples of **fixed-taxonomy**: Snap (closed enum + five `CUSTOM_EVENT_n` slots), Spotify Ad Analytics (`view`/`purchase`/`lead` only), Postie (Snowplow schemas it has registered), Retention.com (fixed case-sensitive "Reclaim" names), Northbeam (custom goals must be pre-registered vendor-side), Nosto (a closed set of page types plus cart, customer and order updates, with no custom event at all), Reddit (eight standard events; a `Custom` event is discarded unless its name is registered in the advertiser's Reddit account), OpenAI Ads (closed enum plus a `custom` type whose name must be registered in Ads Manager). Some fixed-taxonomy platforms offer a **registered custom event** as an escape hatch, which is fixed-taxonomy and config-driven at once. OpenAI Ads is the clearest example: it accepts a `custom` event type, but only for names the advertiser has already created in Ads Manager, and it silently discards any other name. So the destination skips an unmapped event by default, and forwards it only when the operator has supplied a **Custom Event Mapping** entry — an explicit statement that the name exists vendor-side. Forwarding on a guess would look like delivery and be a no-op. Reddit has the same `Custom` escape hatch vendor-side, but Chord's Reddit destinations expose no event-mapping credential, so they always skip an unrecognized event rather than guess at a registered name. ## Decide by platform, not by transport A destination's bucket is a property of the **platform**, and the **pixel** **(device-mode) and Conversions-API (server-side) implementations for the same** **platform must make the same choice.** Server-side / CAPI delivery is permissive by construction — `event_name` is just a string field in an HTTP body, with no client SDK enum to satisfy — so it is tempting to forward everything server-side. But transmitting an event the platform ignores is still a no-op; it just happens over HTTP instead of a JS call. Facebook accepts custom events on **both** its pixel and its Conversions API, so both forward. A fixed-taxonomy platform like Snap would skip on both. There is no case where the CAPI side should forward what the pixel side drops for the same platform. OpenAI Ads shows why this is not merely tidy. Its two surfaces deduplicate on (pixel ID, event name, event ID), so they must agree on the *name* as well as the decision to send: if the pixel skipped an event that the Conversions API forwarded under a name of its own, the conversion would be recorded once under a name that matches no conversion goal — worse than dropping it, because it reads as delivered. Both surfaces therefore resolve event names through one shared table and honor the same **Custom Event Mapping**. :::BlockQuote **Why custom-mapped properties are always forwarded regardless of bucket:** the bucket decision is about the *event name*. Custom *properties* mapped by the customer are merged into every outgoing call (see below), because a fixed-set platform still accepts extra fields on the events it does recognize. ::: # Practical guidance - **Sending a custom event to a warehouse or a passthrough destination?** It will arrive with its original name and properties. No tracking-plan compliance is required. - **Sending a custom event to an ad platform via a device-mode pixel?** Confirm the plugin is passthrough or that you have mapped the event in the plugin's configuration. Fixed-taxonomy plugins will skip it and log a `console.warn`. - **Want a custom event to look like a canonical one at a destination?** Use a property mapping or a UDF in the connection to reshape it before it reaches the destination function. - **Want to stop a custom event from reaching a destination?** Add a connection filter rule, or drop it in a UDF — there is no automatic rejection to rely on. # Summary Chord is a flexible, schema-less pipeline. It accepts any well-formed event, transforms it only as explicitly configured, and forwards it. The tracking plan provides canonical names that destinations \*prefer\* when present, but compliance is never enforced. Custom events are first-class citizens of the pipeline; the only meaningful variation is how individual destinations choose to map — or ignore — events they were not built to recognize. [title] Subscription Generated [path] Chord Event Tracking/Server Events/Track/ Fired when **any **subscription is created after an order is completed, regardless of type. This includes regular, prepaid, gifted, and converted-from-prepaid subscriptions. For regular subscriptions, this event fires **in addition to **`Subscription Created`. # 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 Created", "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 Created", "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] 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] Statsig [path] Chord CDP/CDP Destinations/CDP Destination Catalog/ The **Statsig** destination sends events to [Statsig](https://www.statsig.com/) using the server-side [`log_event HTTP API`](https://docs.statsig.com/api/content/api-reference/events/log-custom-events), so that Chord CDP events can be used as metrics for Statsig experiments and feature gates. This is a **cloud-mode (server-side) destination only**, and deliberately so. The metrics that decide a Statsig experiment are revenue events — `Order Completed`, refunds, subscription renewals — and in Chord CDP those frequently arrive from backend sources (Shopify webhooks, server-to-server ingest) that never touch a browser. A device-mode plugin could not see them, which would leave you with an experiment that cannot measure its own success metric. Segment ships Statsig the same way, cloud-mode only. Feature gate and experiment **evaluation stays in your storefront's own Statsig SDK.** This destination only ever calls `log_event`; it never calls `check_gate`, because that endpoint automatically logs exposure events and would double-count exposures the storefront SDK already records. You will need: - **Server Secret Key** — found in **Project Settings > API Keys** in the Statsig console. It starts with `secret-`. Do not use a client SDK key here. # Connecting to the Statsig 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 **Statsig** from the destination catalog. 5. Enter the destination name and your **Server Secret Key**. 6. Confirm the **Anonymous ID Key** matches your experiment unit (see [Identity and experiment units](#) below). 7. Click **"Create"** to connect. # Identity and experiment units This is the setting that most often breaks a Statsig integration, so it is worth getting right before you ship. Statsig randomizes each experiment on a **unit ID**. If the storefront's Statsig SDK assigns a visitor to a variant using one ID, but Chord CDP sends the conversion event under a different one, the event will not join to the experiment group — every readout comes back flat, with no error anywhere to explain why. The destination sends: | Statsig field | Chord source | | ----------------------------------- | ------------- | | `user.userID` | `userId` | | `user.customIDs.` | `anonymousId` | The **Anonymous ID Key** defaults to `stableID`, which is Statsig's own convention for an anonymous unit. For this to line up, your storefront must be configured to pass the Chord `anonymousId` as Statsig's `stableID` rather than letting the Statsig SDK generate its own. If your experiments are randomized on a different custom ID, set the Anonymous ID Key to match it. Migrating off Segment? Whatever field you mapped to Statsig's `userID` in the Segment destination is the unit your existing experiments are already keyed on. Carry that exact mapping over, or your readouts will break at cutover. # Event Mapping Statsig has no fixed event taxonomy — custom event names are first class — so **track events pass through under their own name**. No allowlist, no renaming. | Chord Event Type | Statsig `eventName` | Notes | | ---------------- | ------------------------------ | -------------------------------------------------------------------- | | `track` | The Chord event name, verbatim | Custom events pass through unchanged | | `page` | `Page View` | Sent only when **Send page events** is enabled (default on) | | `identify` | `Identify` | Sent only when **Send identify events** is enabled (default **off**) | Any other event type (`group`, `screen`, …) is skipped with an explicit log line, never dropped silently. ## Track Events | Statsig Field | Chord Source | Notes | | ------------- | -------------------------------------------------------------- | -------------------------------------------------------------------------------------- | | `eventName` | `event` | Passed through verbatim | | `value` | `properties.revenue` > `properties.total` > `properties.value` | Overridable via the **Value Property** setting. Numeric strings are coerced to numbers | | `time` | `timestamp` | Unix milliseconds | | `metadata` | `properties` | See [Metadata flattening](#) | | `user` | Identity + context | See [Identity and experiment units](#) | ## Page Events | Statsig Field | Chord Source | Notes | | ------------------------------------------------- | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | | `eventName` | *(hardcoded)* `Page View` | Page identity lives in `metadata`, so a single metric can be filtered per page rather than fragmenting into one metric per page name | | `metadata.url` / `.path` / `.title` / `.referrer` | `context.page` | Explicit `properties` of the same name win over the context values | | `metadata.name` | `name` | Present when the page event is named | `value` is never set on page events. ## Identify Events Statsig has no user-profile API, so an identify call is logged as an ordinary `Identify` event with the user's traits in `metadata`. This is **off by default** to avoid inflating event volume for no analytical gain — enable it only if you want identify calls to be countable as a metric. # Metadata flattening Statsig's `metadata` is a flat key/value map. Nested values (`products[]`, `address`, …) are **JSON-stringified rather than dropped**, so the data still reaches Statsig and remains queryable as a string instead of silently disappearing. Primitives (string, number, boolean) pass through unchanged; `null` and `undefined` are omitted. Because `metadata` accepts arbitrary keys, any custom property mappings you configure in Hub flow through automatically — there is no destination-side schema to add them to. # Email and PII The **Email Handling** setting controls where a user's email address goes: | Mode | Behavior | | ------------------- | ------------------------------------------------------------------------------------------------------- | | `Private` (default) | Sent as `user.privateAttributes.email` — usable for targeting, but never written to Statsig's event log | | `Attribute` | Sent as `user.email`, which **is** logged | | `Omit` | Never sent | In `Private` and `Omit` mode, `email` is also stripped from `metadata`, so a value arriving via traits or properties cannot defeat the setting. **Email Handling covers email and nothing else.** Every other trait and property is forwarded to `metadata` verbatim, and `metadata` **is** written to Statsig's event log. An identify event carrying `phone`, `firstName`, `lastName` or `address` sends those to Statsig in plaintext, with no setting to suppress them. This matters most for identify events, which carry a full trait set — one reason **Send identify events** is off by default. If a trait must not reach Statsig, drop it upstream in a transformation function rather than relying on this destination to filter it. # Environments The **Environment Tier** setting is sent as `user.statsigEnvironment.tier`. Set it to `staging` or `development` on non-production connections — otherwise staging traffic silently pollutes your production experiment metrics, which is painful to unwind after the fact. # Retry Behavior | Response | Behavior | | ----------------- | ----------------------------------------------------------------------------------------------------- | | `202` | Accepted | | `429`, `5xx` | Retried | | Other `4xx` | Not retried — a bad secret key or malformed payload cannot be fixed by sending the same request again | | Transport failure | Retried | [title] Connection property mappings [path] Chord CDP/ # Connection Property Mappings Property Mappings let you rename, move, or inject properties on events before they reach a destination — without writing code. Mappings are configured per-connection and work for both **device-mode** (client-side) and **cloud-mode** (server-side) destinations. ## How It Works Each mapping defines a transformation that copies a value from one path on the event to another, or injects a static string value. Mappings run in order and each one sees the result of the previous mapping. **Processing order for cloud-mode destinations (Rotor):** ```javascript Incoming Event → Filters → Property Mappings → Destination Function → Destination API ``` **Processing order for device-mode destinations (jitsu-js):** ```javascript Incoming Event → Property Mappings → Destination Plugin → Third-Party SDK ``` Mappings are applied **before** destination functions, so any mapped values are available on the event when your function code runs. ## Configuring Mappings Open a connection in the Console and expand the **Property Mappings** section. Each mapping has the following fields: | Field | Description | | -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Enabled** | Toggle to enable or disable the mapping without deleting it | | **Event Scope** | Which events the mapping applies to: All Events, Track, Page, or Identify. For Track events, you can optionally specify an event name (e.g., "Order Completed") | | **Source** | Either a **Property** path on the event, or a **Static Value** string | | **Destination Path** | The path where the value will be written on the event | ### Path Syntax Use dot notation to reference nested properties: - `properties.sku` — the `sku` field inside `properties` - `context.device.type` — deeply nested path - `properties.products.0.name` — array index access Use `[]` to iterate over arrays: - `properties.products.[].name` — collects `name` from every element, producing an array of values - `properties.orders.[].items.[].sku` — nested array iteration ### Static Value Mappings Instead of copying from a source path, you can inject a fixed string value. Toggle the source type to **Static Value** and enter the value. This is useful for tagging events with metadata like a source system identifier. ## Examples ### Renaming a Property Map `properties.sku` to `properties.product_id`: **Input:** ```json { "type": "track", "event": "Product Viewed", "properties": { "sku": "ABC-123", "name": "Blue Widget" } } ``` **Output:** ```json { "type": "track", "event": "Product Viewed", "properties": { "sku": "ABC-123", "name": "Blue Widget", "product_id": "ABC-123" } } ``` Note that the original `sku` field is preserved. Mappings copy values — they do not remove the source. ### Array Iteration Map `properties.products.[].name` to `properties.products.[].title`: **Input:** ```json { "type": "track", "event": "Order Completed", "properties": { "products": [ { "name": "Widget", "price": 9.99 }, { "name": "Gadget", "price": 24.99 } ] } } ``` **Output:** ```json { "type": "track", "event": "Order Completed", "properties": { "products": [ { "name": "Widget", "price": 9.99, "title": "Widget" }, { "name": "Gadget", "price": 24.99, "title": "Gadget" } ] } } ``` ### Static Value Injection Map static value `"jitsu_cdp"` to `properties.source_system`: **Input:** ```json { "type": "track", "event": "Product Viewed", "properties": { "sku": "ABC-123" } } ``` **Output:** ```json { "type": "track", "event": "Product Viewed", "properties": { "sku": "ABC-123", "source_system": "jitsu_cdp" } } ``` ### Scoped Mapping A mapping with **Event Scope** set to `Track` and **Event Name** set to `Order Completed` will only apply to `Order Completed` track events. All other events pass through unchanged. ## Testing Mappings The mapping editor includes a **Test** panel where you can paste a sample JSON event and preview the transformed output before saving. ## Error Handling ### Missing Source Path If a source path does not exist on the incoming event, that mapping is **skipped** and a warning is logged — the event continues to the destination with all other mappings applied. This means a misconfigured or overly-broad mapping will not silently block event delivery. Where the warning appears depends on the destination mode: - **Cloud-mode (Rotor):** A warning is logged in Live Events: `Mapping "": source path "" does not exist on event — mapping skipped`. - **Device-mode (browser SDK):** A `console.warn` is emitted in the browser console — this does not appear in Live Events. Use **Event Scope** to restrict mappings to only the event types and names where the source path is guaranteed to exist. This avoids spurious warnings and keeps your mapping configuration intentional. ### Validation Errors Mappings are validated when you save the connection. The following conditions will prevent saving: - A mapping has neither a source path nor a static value - A mapping has both a source path and a static value - The destination path is blank - The destination path targets a protected field (see below) - Two enabled mappings write to the same destination path within the same event scope - More than 50 mappings on a single connection ## Mappings and Functions Mappings run **before** destination functions in the processing chain. This means: 1. Your destination function receives the event with all mappings already applied 2. Mapped properties are available for the function to read and use 3. If a mapping's source path is missing, that mapping is skipped and a warning is logged — the function is still called with the partially-mapped event This is useful when a destination function expects properties in a specific shape. Instead of modifying the function to handle different source schemas, you can use mappings to normalize the event first. ## Connections Table Connections with active mappings display badges in the **Mappings** column on the connections list page. Each badge shows the mapping number, and hovering reveals the source-to-destination path. ## Limitations | Constraint | Detail | | ----------------------------- | --------------------------------------------------------------------------------------------------------------------------- | | **Maximum mappings** | 50 per connection | | **Protected fields** | Cannot write to `type`, `messageId`, `writeKey`, `receivedAt`, or `sentAt` | | **Static values are strings** | Static value mappings always inject a string; no type coercion is performed | | **No value removal** | Mappings copy values to new paths but do not delete the original source path | | **No conditional logic** | Mappings cannot branch based on values; use Event Scope to filter by event type/name, or write a function for complex logic | | **Ordering matters** | Mappings run sequentially; a later mapping can read a path written by an earlier one, but reordering may change results | | **Shallow clone** | The mapping engine creates a shallow clone of the event; deeply nested reference types are shared with the original | [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 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] Subscription Created [path] Chord Event Tracking/Server Events/Track/ Fired when a **regular (non-prepaid, non-gifted) **subscription is created after an order is completed. This event does **not **fire for prepaid subscriptions, gifted subscriptions, or subscriptions converted from prepaid. # 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 Created", "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 Created", "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] 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/parsing 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. [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] Events Tracked by the Web Pixel [path] Chord Event Tracking/Using with Shopify/ The custom web pixel subscribes to Shopify's customer events and delivers them to Chord as tracking plan events. This page lists what you get without writing any theme code. These thirteen events are the complete set of [standard customer events](https://shopify.dev/docs/api/web-pixels-api/standard-events) Shopify exposes to web pixels — not a subset Chord selected. If an interaction you care about is not in this list, Shopify does not publish an event for it, and it has to be instrumented in the theme. See [Custom Events on Shopify](https://shopify.dev/docs/api/web-pixels-api/emitting-data). ## Storefront events These fire on your theme's pages. The pixel forwards them to `@chordcommerce/analytics` on the top window, which delivers them to Chord and to any device-mode destinations. | Shopify event | Chord event | Notes | | --------------------------- | ------------------- | ----------------------------------------------------- | | `page_viewed` | `page()` call | Sends path, URL, and title | | `product_viewed` | Product Viewed | Product detail pages | | `collection_viewed` | Product List Viewed | Includes the collection's product variants | | `search_submitted` | Products Searched | Sends the search query | | `cart_viewed` | Cart Viewed | Only on the `/cart` page — see [Mini-cart drawers](#) | | `product_added_to_cart` | Product Added | | | `product_removed_from_cart` | Product Removed | | ## Checkout events These fire on Shopify-hosted checkout pages. The pixel sends them directly to Chord via cloud mode *and* forwards them by `postMessage`, so they are captured whether or not your storefront library is present on the page. | Shopify event | Chord event | Notes | | ---------------------------------- | -------------------------------- | ----------------------------------------------------------- | | `checkout_started` | Checkout Started | Includes line items, coupon, discount, tax, and shipping | | `checkout_contact_info_submitted` | Checkout Step Completed (step 1) | Also sends an `identify` with the shopper's email and phone | | `checkout_address_info_submitted` | Checkout Step Completed (step 2) | | | `checkout_shipping_info_submitted` | Checkout Step Completed (step 3) | | | `payment_info_submitted` | Payment Info Entered (step 4) | | | `checkout_completed` | Order Completed | Also sends an `identify` with the Shopify customer ID | Device-mode destinations cannot run on Shopify-hosted pages, so checkout events reach those destinations through cloud mode only. This is a Shopify platform restriction, not a Chord one. ## Customer identification The pixel sends an `identify` call in three situations: 1. **On load**, when Shopify reports a logged-in customer. Traits come from Shopify's customer object: email, first and last name, phone, and order count. 2. **At **`checkout_contact_info_submitted`, with the email and phone entered in checkout. No user ID is set here — an email is not a stable identifier. 3. **At **`checkout_completed`, with the Shopify customer ID as the user ID. Shopify's event bus has no sign-in event, so a shopper who logs in mid-session is not identified until the next page load. To identify them at the moment they sign in, add an `identify()` call to your storefront. See [Identify Users on Sign-In](#). ## What the pixel does not track Three gaps come up on most themes. ### Sign-in Covered above — Shopify publishes no login event. Instrument it in the storefront. ### Mini-cart drawers Shopify fires `cart_viewed` only when a shopper navigates to `/cart`. A theme that opens the cart in a slide-out drawer never triggers it, so Cart Viewed will be missing. Call `window.chord.trackCartViewed()` when the drawer opens. ### Merchandising interactions No standard event covers clicks within a collection grid, quick-add buttons, wishlist actions, or variant switching on a product page. These are theme-specific and must be tracked from theme code. See [Custom Events on Shopify](https://shopify.dev/docs/api/web-pixels-api/emitting-data). ## Related - [Server Event Tracking](docId\:q6xVtfkfFiPMHVVI2QcG0) — order and refund events delivered from Shopify webhooks - [Custom Events on Shopify](https://shopify.dev/docs/api/web-pixels-api/emitting-data) — adding events Shopify does not publish - [SDK Reference](docId\:RR6OU_MAMBvVhmDqlyGH8) — the typed tracking methods available on `window.chord` [title] Chord Event Tracking [path] / Chord is a commerce data platform for modern brands that streamlines the unification and activation of data across various business teams. As such, Chord has a recommended set of tracking events that commerce sites can implement to collect transactional and behavioral data. The following documentation enables modern brands to easily implement Chord event tracking on their sites, which in turn powers the comprehensive data analytics and insights presented on the Chord platform. ## How-to guides for the Chord Commerce Event Tracking ### Getting Started - [Installing Chord Analytics](https://docs.chord.co/analytics-developer-docs) - [API Reference](https://docs.chord.co/sdk-api-reference) - [Implementation Checklist](https://docs.chord.co/analytics-developer-docs/implementation-checklist) - [Formatters](https://docs.chord.co/formatters) ### Server Events - [Server Events Overview](docId\:IkQZVvht-BFBSKyISgKJo) - [Track](docId\:z57EPqMJDr7cJ3wQ1JxDO) ### Using with Shopify - [Introduction](https://docs.chord.co/introduction) - [Web Pixel](docId\:YbZ9CC0qUadUpZfcfvO96) - [Server Event Tracking](docId\:q6xVtfkfFiPMHVVI2QcG0) ### Guides - [Unifying Data Across Sources](https://docs.chord.co/unifying-data-across-sources) - [Integrations](https://docs.chord.co/integrations) ### Consent Management ([overview](https://docs.chord.co/consent-management)) - [Shopify Customer Privacy API](https://docs.chord.co/shopify-customer-privacy-api) - [Custom storefront consent management](docId\:NnS7HQreREyTGuQiQ7FoW) ### Release Notes - [Chord Commerce Analytics](https://docs.chord.co/chordcommerceanalytics) ### Chord Commerce Tracking Plan - [Tracking Plan](https://docs.chord.co/tracking-plan) [title] Untitled [path] Chord Event Tracking/ [title] Untitled [path] / [space] Chord Commerce Analytics (/analytics-developer-docs) [title] Untitled [path] / [title] Implementation Checklist [path] Getting Started/ At a minimum, for Chord to model analytics data correctly, the following must be implemented: - CDP script loaded on every site page (see [**Installing Chord Analytics**](docId:1nV6KpJcW0tgvWZw1SoRK)) - `page` events sent to CDP from the website front-end - CDP anonymous ID added as a cart attribute (see [**Unifying Data Across Sources**](docId\:FYmI5G8eWB-YYpyh-GU4o)) - These `track` events from the website front-end: - "Product Added" - "Cart Viewed" - "Checkout Started" - "Order Completed" In order for CDP destinations to work well, the following should also be implemented: - `identify` events sent to CDP whenever identifying information is captured - `track` events required by CDP destinations (see the CDP destination documentation for information on which events are needed by which destinations) [title] Installing in a Shopify Theme [path] Using with Shopify/ ## Requirements Chord's Shopify theme analytics library assumes that a CDP Javascript library is already installed on the site. Segment's [**analytics.js**](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/) library is currently the only supported option. You can install Segment's [**analytics.js**](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/) by pasting [**Segment's code snippet**](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/quickstart/#step-2b-add-the-segment-snippet) into the `` tag of your theme. It should be added to every page of the site, so you'll likely choose to include it in `layout/theme.liquid` and `layout/checkout.liquid` (if using). See [**Segment's instructions**](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/quickstart/#step-2a-add-the-segment-snippet) for adding the code snippet. You can find the latest version of the Segment snippet in the **Overview** tab of your Javascript source in your Segment workspace. Remove `analytics.page();` from the snippet after you paste it into your theme. Chord will handle calling `analytics.page();` and add some extra metadata. ## Installation In the theme code, add create a Liquid file called `snippets/chord.liquid` and paste in this code: ::::CodeDrawer{title="chord.liquid" codeEditorData="[object Object]" responsesEditorData="[object Object]" isResponseExpanded="false" autoGeneratedAnchorSlug="chordliquid" legacyHash="ZkUVGn9DiPvx5XAJEjnUf"} :::CodeblockTabsExamples Chord Liquid snippet ```html ``` ::: :::CodeblockTabsResponses ```javascript ``` ::: :::: ### Add your store identifiers Before the code is deployed to production, there are four variables at the top of the snippet that need to be updated with different values: ```text var CHORD_OMS_ID = ''; // Chord will provide. var CHORD_STORE_ID= ''; // Chord will provide. var CHORD_TENANT_ID = ''; // Chord will provide. var STORE_DOMAIN = ''; // comes before .myshopify.com ``` The value of `STORE_DOMAIN` should be the Shopify store name that comes before `.myshopify.com`. For example, if the store is `https://chord-store.myshopify.com`, it should be `chord-store`. Chord will provide the values for the other three variables. ### Add snippet to your layout Include the Chord snippet on every page of the Shopify theme by rendering it inside the `` tag in `layout/theme.liquid`: :::CodeblockTabs layout/theme.liquid ```html {% render 'chord' %} ``` ::: To add tracking events to Shopify checkout and send an "Order Completed" tracking event from the order confirmation page, render the Chord snippet inside the `` tag on `layout/checkout.liquid`, with the `order_completed` variable set to `true`: :::CodeblockTabs layout/checkout.liquid ```html {% render 'chord' order_completed: true %} ``` ::: :::hint{type="warning"} Chord tracking cannot currently be installed on Shopify checkouts that have been upgraded to [**Checkout Extensibility**](https://help.shopify.com/en/manual/checkout-settings/checkout-extensibility/checkout-upgrade). ::: ## Usage Without any further code changes to your theme, Chord's snippet will send the CDP: - A `page` event for every page view - An `identify` event for every page view for a logged in user - The following `track` events: - "Cart Viewed" - "Checkout Started" - "Email Captured" - "Order Completed" (if Chord's snippet is added to `checkout.liquid`) - "Product Clicked" - "Product Viewed" You can add more events using the global `window.chord` object. See the [**Shopify Theme API Reference**](docId\:w1JcCHTdf49P8u7lWVuJM) for a complete list of available methods. You can also customize the DOM selectors used for the `track` events that Chord automatically sends. ## Configuration Chord's Liquid tracking library can be configured with the following options. To modify the default options, change the `options` object argument passed to `chord.load()`: | Property | Type | Required | Description | | ----------------------- | ---------------------------------------------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | autoInstrument | boolean | no | Defaults to `true`. When set to `false`, `track` events are not automatically sent. | | autoInstrumentSelectors | object (see **Auto-Instrument Selectors **below) | no | Provide custom DOM selectors for automatic instrumentation of events. | | baseUrl | string | no | The base URL of the Shopify site, to use in Shopify Ajax API requests. Ex. `https://example.myshopify.com`. If not provided, the current origin will be used. | | cdp | function or object | yes | A reference to the CDP library, or a function that returns a reference to the CDP library. For example, if using Segment's [**analytics.js**](https://www.npmjs.com/package/@segment/analytics-next) library, this could be `window.analytics` or `() => window.analytics`. If omitted, no tracking events are sent. | | debug | boolean | no | Defaults to `false`. When set to `true`, events are validated against Chord's tracking plan. An error is logged using `console.log` if the event doesn't match the tracking plan and the `enableLogging` option is set to `true`. We recommend enabling `debug` and `enableLogging` for development and disabling for production. | | enableLogging | boolean | no | Defaults to `true`. When set to `true`, Javascript and `debug` errors are logged using `console.log`. We recommend enabling `debug` and `enableLogging` for development and disabling for production. | | metadata | object (see **Metadata **below) | yes | Event metadata. See below for details. | | stripNull | boolean | no | Defaults to `true`. When set to `true`, event properties with a `null` value are removed. CDPs typically treat `null` and `undefined` as separate values, so be sure you intend to send `null` values before setting to false. | | syncIdentifiers | object (see **Sync Identifiers **below) | no | Enable adding integration identifiers as cart attributes, so they can be included in server-side events. Each integration defaults to `false`. | **Auto-Instrument Selectors ** This optional object allows you to customize the DOM selector that Chord uses to automatically track certain events. Events related to page view, such as "Cart Viewed," aren't configurable here, because they are based on the current URL instead of an interaction with the page. Each event property can be a boolean or a string. When set to `false`, Chord won't send that event automatically. To customize the DOM element that triggers the event, set the matching event property to the DOM selector you want to use. That selector will be passed to `document.querySelectorAll(selector)` and an event listener will be added that the library will use to trigger the event. If the selector is a `
` element, the event will be triggered when the form is submitted. Otherwise, the event will be triggered when the element is clicked. | Property | Type | Required | Description | | -------------------------------------------- | ------------------ | -------- | -------------------------------------------------------------------------------------------------------------------------------------- | | autoInstrumentSelectors\['Checkout Started'] | string or boolean | no | The default selector is `form[action="/cart" i][method="post"]`. | | autoInstrumentSelectors\['Email Captured'] | string or boolean | no | The default selector is `form[action="/contact#contact_form" i][method="post"], form[action="/contact#contactform" i][method="post"]`. | | autoInstrumentSelectors\['Product Clicked'] | string or boolean | no | The default selector is `a[href*="/products/" i]`. | **Metadata** This required object provides metadata about the event context that is appended to every event. Chord uses this metadata when providing insights. | Property | Type | Required | Description | | --------------------------- | ------ | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | metadata.i18n.currency | string | yes | The order currency in ISO 4217 currency code, uppercase. For example, `USD`. | | metadata.i18n.locale | string | yes | The order locale. For example, `en-US`. | | metadata.ownership.omsId | string | yes | A UUID assigned by Chord. This identifier is unique to the store, and will be the same across every environment and Segment source for a given store. | | metadata.ownership.storeId | string | yes | A UUID assigned by Chord. This identifier is unique to the store, and will be the same across every environment and Segment source for a given store. | | metadata.ownership.tenantId | string | yes | A UUID assigned by Chord. This identifier is unique to the store, and will be the same across every environment and Segment source for a given store. | | metadata.platform.name | string | yes | The name of the e-commerce platform used. For example, `Shopify`. | | metadata.platform.type | string | yes | The type of platform where the event originated. Either `web` or `pos`. | | metadata.store.domain | string | yes | The store slug that comes before `.myshopify.com`. | **Sync Identifiers ** This optional object allows Chord's library to save identifiers from other libraries and integrations as attributes on the cart. Chord will use these attributes to connect your front-end website events with your server events. Read more about this in [**Unifying Data Across Sources**](docId\:FYmI5G8eWB-YYpyh-GU4o). Each integration defaults to `false`. Set the integration to `true` if you plan to send both front-end and server events to the integration via the CDP. Currently, only the Google Analytics 4 identifier is supported. Contact Chord to request help adding more identifiers. | Property | Type | Required | Description | | -------------------------------------- | ------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | syncIdentifiers\['Google Analytics 4'] | boolean | no | When set to `true`, adds the client ID from the `_ga` cookie as a cart attribute. Chord will include this client ID on server events for the order, so sessions can be tied together in GA4. | [title] Installing Chord Analytics [path] Getting Started/ The `@chordcommerce/analytics` library provides simple methods for sending tracking events to Chord from your website, with an optional debugging mode to validate event properties. `@chordcommerce/analytics` is intended to be installed alongside a customer data platform (CDP) tracking library like Segment's [**analytics.js**](https://www.npmjs.com/package/@segment/analytics-next). `@chordcommerce/analytics` sends Chord tracking events to the CDP tracking library, so they’re available for all connected integrations. ## Requirements Chord's analytics library assumes that a CDP Javascript library is already installed on the site. Segment's [**analytics.js**](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/) library is currently the only supported option. You can install analytics.js either via a [**code snippet**](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/quickstart/#step-2b-add-the-segment-snippet) or [**npm package**](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/quickstart/#step-2a-install-segment-as-a-npm-package) that Segment offers. You'll pass a reference to the `analytics` object created by Segment's [**analytics.js**](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/) library when you configure Chord tracking. ## Installation To install `@chordcommerce/analytics`, run the following command in your project directory: ```shell npm install @chordcommerce/analytics # or yarn add @chordcommerce/analytics ``` ## Usage First, ensure that a CDP Javascript library is installed and configured in your project. Then, initialize `@chordcommerce/analytics` as follows: ```typescript import { ChordAnalytics } from '@chordcommerce/analytics' const chord = new ChordAnalytics(options) // see below for configuration options chord.trackCartViewed({ cart }) // sends a "Cart Viewed" event to the CDP ``` Once loaded, `window.chord` will be available in the browser and will contain the `ChordAnalytics` instance. ## Configuration `@chordcommerce/analytics` can be initialized with the following options: | Property | Required | Description | | --------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `cdp` | true | A reference to the CDP library, or a function that returns a reference to the CDP library. For example, if using Segment's [**analytics.js**](https://www.npmjs.com/package/@segment/analytics-next) library, this could be `window.analytics` or `() => window.analytics`. If omitted, no tracking events are sent. | | `debug` | false | Defaults to `false`. When set to `true`, events are validated against Chord's tracking plan and errors are logged. We recommend enabling this for development and disabling for production. | | `enableLogging` | false | Defaults to `true`. When set to `true`, errors are logged using `console.log`. | | `formatters` | true | Functions that are used to construct tracking events. There are two types of formatters, objects and events. `formatters.objects` is required. See [**Formatters**](docId\:jtVWPDz7_oCApD7glEMID) for more details. | | `metadata` | true | Event metadata. See below for details. | | `stripNull` | false | Defaults to `true`. When set to `true`, event properties with a `null` value are removed. CDPs typically treat `null` and `undefined` as separate values, so be sure you intend to send `null` values before setting to false. | **Metadata** | Property | Required | Description | | ----------------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | `metadata.i18n.currency` | true | The order currency in ISO 4217 currency code, uppercase. For example, `USD`. | | `metadata.i18n.locale` | true | The order locale. For example, `en-US`. | | `metadata.ownership.omsId` | true | A UUID assigned by Chord. This identifier is unique to the store, and will be the same across every environment and Segment source for a given store. | | `metadata.ownership.storeId` | true | A UUID assigned by Chord. This identifier is unique to the store, and will be the same across every environment and Segment source for a given store. | | `metadata.ownership.tenantId` | true | A UUID assigned by Chord. This identifier is unique to the store, and will be the same across every environment and Segment source for a given store. | | `metadata.platform.name` | true | The name of the e-commerce platform used. For example, `Shopify`. | | `metadata.platform.type` | true | The type of platform where the event originated. Either `web` or `pos`. | | `metadata.store.domain` | true | The domain of the site where the event originated. For Shopify, this should be the store slug that comes before `.myshopify.com`. | ### Formatters Formatters are Javascript functions that are used to construct tracking event properties. There are two types of formatters, objects and events. You must define object formatters. Event formatters are optional. See [**Chord’s documentation**](https://docs.chord.co/analytics-getting-started#fgWx7) for more details and example formatters. **Object Formatters** A formatter must be provided for each of the four core data types that are used in Chord events. This formatter function transforms input data into the type Chord expects. See [**Formatters**](docId\:jtVWPDz7_oCApD7glEMID) for more details on object formatters. | Property | Required | Description | | ----------------------------- | -------- | ------------------------------------------- | | `formatters.objects.cart` | true | A function that creates a cart object. | | `formatters.objects.checkout` | true | A function that creates a checkout object. | | `formatters.objects.lineItem` | true | A function that creates a line item object. | | `formatters.objects.product` | true | A function that creates a product object. | **Event Formatters** A formatter can be provided for each event. This formatter is used to transform the event properties of a specific event after Chord constructs the event, just before it's sent to the CDP. See [**Formatters**](docId\:jtVWPDz7_oCApD7glEMID) for more details on event formatters. ## Using with Typescript Optionally, you can instantiate `ChordAnalytics` with a custom type argument describing your data to improve type safety for formatters and SDK functions. For instance, if you're working with objects like `cart`, `product`, etc., from a Shopify storefront API query, you might already have types like `StorefrontCart` defined for the response. Instantiate `ChordAnalytics` with a type argument: ```js interface ObjectTypes { Cart: StorefrontCart Checkout: StorefrontCart LineItem: StorefrontLineItem Product: StorefrontProduct } const chord = new ChordAnalytics({ options }) ``` Now, when you use an SDK method like `chord.trackCartViewed({ cart })`, `cart` has the `StorefrontCart` type. Formatter types also support an optional generic type parameter for the function argument: ```js import type { CartFormatter } from '@chordcommerce/analytics' export const cartFormatter: CartFormatter = (props) => { const { cart } = props // `cart` has type `StorefrontCart` return { ... } } ``` [title] Untitled [path] / [title] Enabling Server Events [path] Using with Shopify/ When installed on your storefront, Chord typically sends tracking events to the CDP from two sources: - Your website front-end, either using Chord's Shopify theme snippet or `@chordcommerce/analytics`, and; - Chord's server events service, which sends tracking events from a Shopify custom source function in your Segment workspace in response to webhook triggers from Shopify. When Chord provisions your Segment workspace, it will include Chord's Shopify webhook source. This code listens for webhook events from Shopify and transforms them into Segment events. ## Requirements Locate Chord's webhook source in your Segment workspace, named "Shopify Webhooks." Chord typically creates this webhook source as part of your Segment workspace provisioning. You'll need to update the settings of this source during the **Create an Admin API Key** step, and you'll need the webhook URL of this source during the **Create Webhook Subscriptions** step. If you can't find the Segment source or aren't sure which one it is, please contact Chord. ## Installation There are two steps to configuring server events: creating an Admin API key and adding it to the Chord Segment source; and subscribing the Segment source to Shopify webhook events. ### Create an Admin API key Chord's Segment source requires an admin API key with the `read_orders` scope to retrieve order details from Shopify. To generate this admin API key, we recommend creating a custom Shopify app in your Shopify account for Chord, and using the Admin API access token from this custom app. This makes it easy to manage access. Create a new custom app in your Shopify admin by navigating to **Settings** > **Apps and sales channels** > **Develop apps** > **Create an app**. Once the app is created, click **Configure Admin API Scopes**. Choose `read_orders` only and hit **Save.** On the **Overview** tab, you should see a prompt to **Install to get your access token**. Click **Install app**. Now you should see this: ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/-HtEyo6KDxhwiwkkLSvnM_untitled-5.png) Copy the Admin API access token. In your Segment workspace, navigate to your Chord webhook source and view the settings under **Settings** > **Connection**. Enter the Admin API access token you just created in the **Access Token** or **accessToken** settings field, and **Save Changes**. ### Create Webhook Subscriptions In your Segment workspace, navigate to your Chord webhook source and find the webhook URL for the source under the **Configure your webhook** heading. Now you'll create webhook subscriptions in Shopify. You can create webhook subscriptions either via the [**Shopify admin**](https://help.shopify.com/en/manual/orders/notifications/webhooks) or the [**Admin API**](https://shopify.dev/docs/api/admin-rest/2024-01/resources/webhook#post-webhooks). You can use the Admin API access token you created for Chord to create the subscription via the Admin API. Create a subscription for each server event you'd like Chord to send to Segment. Each subscription will have the same address, which is the URL you copied from your Chord Segment source. The following webhook topics are supported: - **checkouts/create**: sends Chord's "Checkout Created" event - **orders/create**: sends Chord's "Order Completed" event - **refunds/create**: sends Chord's "Order Refunded" event Shopify's webhook testing doesn't actually include a payload that matches a real webhook payload, so we recommend completing a test transaction in your Shopify store to verify that server events are flowing as expected. You can view the Segment events in the **Debugger** tab of the Shopify webhook source in your Segment workspace. [title] API Reference [path] Getting Started/ ### trackCartViewed The `trackCartViewed` method sends a "Cart Viewed" event to the CDP. ```typescript chord.trackCartViewed({ cart }): Promise ``` The library will call the cart formatter with the `cart` argument and use the returned object to construct and send the "Cart Viewed" event. | Property | Type | Required | Description | | -------- | ---- | -------- | ---------------------------------------- | | cart | any | yes | An object representing the current cart. | ### trackCheckoutStarted The `trackCheckoutStarted` method sends a "Checkout Started" event to the CDP. ```typescript chord.trackCheckoutStarted({ checkout }): Promise ``` The library will call the checkout formatter with the `checkout` argument and use the returned object to construct and send the "Checkout Started" event. | Property | Type | Required | Description | | -------- | ---- | -------- | -------------------------------------------- | | checkout | any | yes | An object representing the current checkout. | ### trackCheckoutStepCompleted The trackCheckoutStepCompleted method sends a "Checkout Step Completed" event to the CDP. ```typescript chord.trackCheckoutStepCompleted({ checkoutId, step, paymentMethod, shippingMethod, }) ``` | Property | Type | Required | Description | | -------------- | ------ | -------- | ----------------------------- | | checkoutId | string | yes | The ID of the checkout. | | step | number | yes | The checkout step number. | | paymentMethod | string | no | The payment method used. | | shippingMethod | string | no | The shipping method selected. | ### trackCheckoutStepViewed The trackCheckoutStepViewed method sends a "Checkout Step Viewed" event to the CDP. ```typescript chord.trackCheckoutStepViewed({ checkoutId, step, paymentMethod, shippingMethod, }) ``` | Property | Type | Required | Description | | -------------- | ------ | -------- | ----------------------------- | | checkoutId | string | yes | The ID of the checkout. | | step | number | yes | The checkout step number. | | paymentMethod | string | no | The payment method used. | | shippingMethod | string | no | The shipping method selected. | ### trackCouponApplied The `trackCouponApplied` method sends a "Coupon Applied" event to the CDP. This event should be sent immediately after the coupon has been successfully applied to the cart. ```typescript chord.trackCouponApplied({ cartId, couponId, couponName, discount, orderId, }) ``` | Property | Type | Required | Description | | ---------- | ------ | -------- | -------------------------------------------- | | cartId | string | no | Cart ID, if applicable | | couponId | string | no | Coupon ID | | couponName | string | no | Coupon name | | discount | number | no | Monetary discount applied through the coupon | | orderId | string | no | Order or transaction ID, if applicable | ### trackCouponDenied The `trackCouponDenied` method sends a "Coupon Denied" event to the CDP. This event should be sent when a coupon could not be applied to the cart. ```typescript chord.trackCouponDenied({ cartId, couponId, couponName, orderId, reason, }) ``` | Property | Type | Required | Description | | ---------- | ------ | -------- | -------------------------------------- | | cartId | string | no | Cart ID, if applicable | | couponId | string | no | Coupon ID | | couponName | string | no | Coupon name | | orderId | string | no | Order or transaction ID, if applicable | | reason | string | no | Reason the coupon was denied | ### trackCouponEntered The `trackCouponEntered` method sends a "Coupon Entered" event to the CDP. This event should be sent immediately after the coupon was entered, usually upon the customer clicking a button to submit, but before the coupon was applied or denied. ```typescript chord.trackCouponEntered({ cartId, couponId, couponName, discount, orderId, }) ``` | Property | Type | Required | Description | | ---------- | ------ | -------- | -------------------------------------- | | cartId | string | no | Cart ID, if applicable | | couponId | string | no | Coupon ID | | couponName | string | no | Coupon name | | orderId | string | no | Order or transaction ID, if applicable | ### trackCouponRemoved The `trackCouponRemoved` method sends a "Coupon Removed" event to the CDP. This event should be sent immediately after the coupon was removed from the cart. ```typescript chord.trackCouponRemoved({ cartId, couponId, couponName, discount, orderId, }) ``` | Property | Type | Required | Description | | ---------- | ------ | -------- | -------------------------------------- | | cartId | string | no | Cart ID, if applicable | | couponId | string | no | Coupon ID | | couponName | string | no | Coupon name | | orderId | string | no | Order or transaction ID, if applicable | ### trackEmailCaptured The `trackEmailCaptured` method sends an "Email Captured" event to the CDP. This event should be sent anywhere a customer enters an email address, like a newsletter sign-up or a product wait list. ```typescript chord.trackEmailCaptured({ email, placementComponent, placementPage }) ``` | Property | Type | Required | Description | | ------------------ | ------ | -------- | -------------------------------------------------------------------------------------------------- | | email | string | no | The email address that was captured. | | placementComponent | string | no | An identifier for the UI component where the email was captured. For example, `footer-newsletter`. | | placementPage | string | no | An identifier for the page where the email was captured. For example, `homepage`. | ### trackLoginStarted The trackLoginStarted method sends a "Login Started" event to the CDP. ```typescript chord.trackLoginStarted({ email, }) ``` | Property | Type | Required | Description | | -------- | ------ | -------- | ------------------------- | | email | string | no | The email used for login. | ### trackNavigationClicked The trackNavigationClicked method sends a "Navigation Clicked" event to the CDP. ```typescript chord.trackNavigationClicked({ category, label, navigationPlacement, navigationTitle, navigationUrl, }) ``` | Property | Type | Required | Description | | ------------------- | ------ | -------- | ------------------------------------------------------ | | category | string | no | The category of the navigation item. | | label | string | no | The label of the navigation item. | | navigationPlacement | string | no | The placement of the navigation (e.g. header, footer). | | navigationTitle | string | no | The title of the navigation. | | navigationUrl | string | no | The URL of the navigation item. | ### trackOrderCompleted The trackOrderCompleted method sends a "Order Completed" event to the CDP. ```typescript chord.trackOrderCompleted({ orderId, orderDate, currency, revenue, total, products }) ``` | Property | Type | Required | Description | | --------- | ----------------- | -------- | ------------------------------------------------ | | orderId | string | yes | The ID of the order. | | orderDate | string | yes | The date order was completed. | | currency | string | yes | The currency of the order. | | revenue | number | yes | The revenue associated with the transaction | | total | number | yes | The revenue with discounts and coupons added in. | | products | array of products | yes | The products in the order. | ### trackPaymentInfoEntered The trackPaymentInfoEntered method sends a "Payment Info Entered" event to the CDP. ```typescript chord.trackPaymentInfoEntered({ checkoutId, coupon, currency, orderId, paymentMethod, products, shippingMethod, step, value, }) ``` | Property | Type | Required | Description | | -------------- | ----------------- | -------- | ------------------------------------- | | checkoutId | string | no | The ID of the checkout. | | coupon | string | no | The coupon code applied to the order. | | currency | string | no | The currency of the order. | | orderId | string | no | The ID of the order. | | paymentMethod | string | no | The payment method used. | | products | array of products | no | The products in the order. | | shippingMethod | string | no | The shipping method selected. | | step | number | yes | The checkout step number. | | value | number | no | The total value of the order. | ### trackProductAdded The `trackProductAdded` method sends a "Product Added" event to the CDP. This event should be sent when a product is added to the cart. It should only be sent when the product is initally added, not when the quantity is incremented for an existing cart item. ```typescript chord.trackProductAdded({ cart, product: { position, product, quantity, variantId } }) ``` | Property | Type | Required | Description | | ---------------- | ------ | -------- | ------------------------------------------------------------------ | | cart | any | yes | The current cart. | | product.position | number | no | The position in a list of the product that was added, if relevant. | | product.product | any | yes | Product and variant details, like product name and variant SKUs. | | quantity | number | no | The quantity of the product added to the cart. | | variantId | any | no | The unique identifier of the product variant. | ### trackProductClicked The `trackProductClicked` method sends a "Product Clicked" event to the CDP. This event should be sent when a product link is clicked on the site. ```typescript chord.trackProductClicked({ cart, listId, listName, product: { position, product, quantity, variantId } }) ``` | Property | Type | Required | Description | | ---------------- | ------ | -------- | -------------------------------------------------------------------- | | cart | any | yes | The current cart. | | listId | any | no | An identifier for the list where the product was clicked. | | listName | string | no | A name for the list where the product was clicked. | | product.position | number | no | The position in a list of the product that was clicked, if relevant. | | product.product | any | yes | Product and variant details, like product name and variant SKUs. | | quantity | number | no | The quantity of the product clicked, if relevant. | | variantId | any | no | The unique identifier of the product variant. | ### trackProductListFiltered The `trackProductListFiltered` method sends a "Product List Filtered" event to the CDP. This event should be sent when a filter is applied to a list of products. | Property | Type | Required | Description | | -------- | ------------------------------------------ | -------- | ---------------------------------------------------------------- | | category | string | no | Product category being viewed | | listId | string | no | The ID of the list in which the item was presented to the user | | listName | string | no | The name of the list in which the item was presented to the user | | filters | array of \{ type?\:string, value?: string} | no | Product filters selected by the customer | | sorts | array of \{ type?\:string, value?: string} | no | Product sorts selected by the customer | ```typescript chord.trackProductListFiltered({ category, listId, listName, filters, sorts }) ``` ### trackProductListViewed The `trackProductListViewed` method sends a "Product List Viewed" event to the CDP. This event should be sent when a list of products is viewed. ```typescript chord.trackProductListViewed({ category, listId, listName, products }) ``` | Property | Type | Required | Description | | -------- | ----------------- | -------- | ---------------------------------------------------------------- | | category | string | no | Product category being viewed | | listId | string | no | The ID of the list in which the item was presented to the user | | listName | string | no | The name of the list in which the item was presented to the user | | products | array of products | yes | Products being viewed | ### trackProductRemoved The `trackProductRemoved` method sends a "Product Removed" event to the CDP. This event should be sent when a product is removed from the cart. ```typescript chord.trackProductRemoved({ cart, lineItem }) ``` | Property | Type | Required | Description | | -------- | ---- | -------- | ---------------------------------------------------------------- | | cart | any | yes | An object representing the cart after the line item was removed. | | lineItem | any | yes | An object representing the line item that was removed. | ### trackProductViewed The `trackProductViewed` method sends a "Product Viewed" event to the CDP. This event should be sent whenever a product page is viewed. ```typescript chord.trackProductViewed({ cart, product: { position, product, quantity, variantId } }) ``` | Property | Type | Required | Description | | ---------------- | ------ | -------- | ------------------------------------------------------------------ | | cart | any | yes | The current cart. | | product.position | number | no | The position in a list of the product that was added, if relevant. | | product.product | any | yes | Product and variant details, like product name and variant SKUs. | | quantity | number | no | The quantity of the product added to the cart. | | variantId | any | no | The unique identifier of the product variant. | ### trackProductsSearched The `trackProductsSearched` method sends a "Products Searched" event to the CDP. This event should be sent whenever a search is submitted. ```typescript chord.trackProductsSearched({ currency, price, productId, quantity, query, }) ``` | Property | Type | Required | Description | | --------- | ------ | -------- | -------------------------------------------------------------------------------- | | currency | string | no | Currency of the transaction (must be a valID ISO 4217 three-digit currency code) | | price | number | no | Price ($) of the product searched for | | productId | any | no | Database ID of the product searched for | | quantity | number | no | Quantity of the product searched for | | query | string | no | Query the user searched with | ### trackSignedIn The `trackSignedIn` method sends a "Signed In" event to the CDP. This event should be sent when the customer signs in successfully. ```typescript chord.trackSignedIn({ email, method }) ``` | Property | Type | Required | Description | | -------- | ------ | -------- | ---------------- | | email | string | no | The user's email | | method | string | no | The method used | ### trackSignedOut The `trackSignedOut` method sends a "Signed Out" event to the CDP. This event should be sent when the customer signs out successfully. ```typescript chord.trackSignedOut({ email }) ``` | Property | Type | Required | Description | | -------- | ------ | -------- | ---------------- | | email | string | no | The user's email | ### trackSignedUp The `trackSignedUp` method sends a "Signed Up" event to the CDP. This event should be sent when the customer signs up successfully. ```typescript chord.trackSignedUp({ email, method }) ``` | Property | Type | Required | Description | | -------- | ------ | -------- | ---------------- | | email | string | no | The user's email | | method | string | no | The method used | ### trackSubscriptionCancelled The trackSubscriptionCancelled method sends a "Subscription Cancelled" event to the CDP. ```typescript chord.trackSubscriptionCancelled({ actionableDate, address, brand, email, endDate, intervalLength, intervalUnits, products, state, subscriptionId, currency, }) ``` | Property | Type | Required | Description | | -------------- | ----------------- | -------- | ---------------------------------------------------------- | | actionableDate | string | no | The date when the subscription can be actioned. | | address | Address | no | The address associated with the subscription. | | brand | string | no | The brand associated with the subscription. | | email | string | no | The email associated with the subscription. | | endDate | string | no | The end date of the subscription. | | intervalLength | number | no | The length of the subscription interval. | | intervalUnits | string | no | The units of the subscription interval (e.g. month, year). | | products | array of products | no | The products in the subscription. | | state | string | no | The state of the subscription (e.g. active, cancelled). | | subscriptionId | string | no | The ID of the subscription. | | currency | string | no | The currency of the subscription. | ### trackVariantClicked The trackVariantClicked method sends a "Variant Clicked" event to the CDP. ```typescript chord.trackVariantClicked({ product, cart, lineItemId, coupon, }) ``` | Property | Type | Required | Description | | ---------- | ------ | -------- | ------------------------------------- | | product | any | yes | The product variant that was clicked. | | cart | any | yes | The cart associated with the event. | | lineItemId | string | no | The ID of the line item. | | coupon | string | no | The coupon code applied to the cart. | ### identify The `identify` method sends an `identify` event to the CDP: ```typescript chord.identify(userId, { ...traits }) // or chord.identify({ ...traits }) ``` We recommend sending an `identify` event whenever the following happens: - After a user creates an account - After a user logs into their account - When a user submits any identifying information, like an email address or a phone number - When a user adds or updates profile information It’s not typically necessary to send an `identify` event on page load. If you’re sending a `track` event at the same time as an `identify` event, we recommend sending `identify` first and the `track` event second. Some integrations require an `identify` event before they can process `track` events. ### reset The `reset` method sends a `reset` event to the CDP tracking library. This does not result in an event appearing in the CDP. It resets the user’s session in the browser, which means the user will receive a new anonymous identifier and any previous user data will be cleared. We recommend calling the `reset` method after a user has successfully logged out of their account. ### track The `track` method sends a `track` event to the CDP: ```typescript chord.track('Navigation Clicked', { label: 'Home', location: 'main nav', url: '/' }) ``` `track` can be used to send any event to the CDP, including events in the Chord tracking plan. However, we recommend using an event-specific method like `trackProductViewed` instead if one is available, so that Chord's library can construct the event body to match the tracking plan. See the individual event tracking methods above. `track` does not use event or object formatters and simply sends the second argument directly to the CDP as the event body. `track` does not transform property names from camel case to snake case; event properties will be sent to the CDP exactly as written. We recommend using snake case for all event properties. `null` values will be stripped by default unless `stripNull` is set to `false` in the `ChordAnalytics` options. [title] Getting Started [path] / What [title] Formatters [path] Getting Started/ Formatters are Javascript functions that are used to construct tracking event data. There are two types of formatters, `objects` and `events`. You must define `object` formatters. `event` formatters are optional. ## Object formatters When you look at Chord's tracking events, you'll see some event properties are used over and over. Names and values of event properties are expected to be consistent between events. In other words, different events have different properties, but a given property name should have the same value wherever it's used. For example, the two events `Product Added` and `Product Clicked` share most of the same event properties. `product_id` is a property of both events, and the value of `product_id` is expected to be the same for both events. It should not be a product SKU for one event and a database identifier for another event. Chord ensures consistency in property names and values by creating a standard set of object models that are used over and over throughout events. There are four: `cart`, `checkout`, `lineItem`, and `product`. When you install Chord's analytics library, you write a formatter function for each of these four types. Your formatter function will receive as an argument the input from the event tracking function, and your formatter must return an object in the format that Chord expects. Then Chord uses this formatter to generate the correct event payload. ### Available object formatters | Method | Type | Description | | -------- | -------------------------------------- | ---------------------------------- | | cart | (props: `CartInput`) => `Cart` | Returns a Chord `Cart` object. | | checkout | (props: `CheckoutInput`) => `Checkout` | Returns a Chord `Checkout` object. | | lineItem | (props: `LineItemInput`) => `LineItem` | Returns a Chord `LineItem` object. | | product | (props: `ProductInput`) => `Product` | Returns a Chord `Product` object. | ### Example object formatter Let's walk through an example of a `cart` formatter. In your website code, you might want to send a `Cart Viewed` tracking event. The code used to send `Cart Viewed` looks like this: ```typescript var cart = await getCartFromShopifyStorefrontApi() // the `cart` object here can be any type chord.trackCartViewed({ cart }) ``` But how does Chord create a standard `Cart Viewed` event when you can pass any arbitrary cart object as the value? You'll define a formatter that converts your `cart` object into a format that Chord understands. See the `Cart` Typescript type exported by `@chordcommerce/analytics` to see what the return type of the cart formatter should be. Here's an example of a cart formatter that converts a [**Shopify Storefront API cart response**](https://shopify.dev/docs/api/storefront/2023-10/objects/Cart) into Chord's `Cart` object: ```typescript import { CartInput, Cart, ChordAnalytics } from '@chordcommerce/analytics' const cartFormatter: (props: CartInput) => Cart = ({ cart }) => { const products = cart?.lines?.map((line, i) => { const lineItem = line?.node return { ...lineItemFormatter({ lineItem }), // your `lineItem` formatter position: i + 1, } }) return { cart_id: cart?.id?.replace('gid://shopify/Cart/', ''), currency: 'USD', products, value: Number(cart?.cost?.subtotalAmount?.amount) || 0, } } // When creating an instance of `ChordAnalytics`, set `formatters.objects.cart` to `cartFormatter` const chord = new ChordAnalytics({ ... formatters: { objects: { cart: cartFormatter, ... }, } }) ``` ## Event formatters Event formatters are optional. You can supply an event formatter for any event-specific tracking method of `ChordAnalytics`; for example, for `chord.trackProductAdded`, you can set an event formatter with the key `productAdded`. Chord's library will call your event formatter after constructing the tracking event but before sending to the CDP. This is the easiest way to customize a Chord tracking event, if you're not able to get the effect you want with object formatters. A common use case is to add additional properties to a specific tracking event. ### Available event formatters All event formatters are optional. Event formatters have two arguments: `props`, which is the argument passed to the related tracking function (for example, `chord.trackProductClicked(props))`, and `event`, which is the finished event payload Chord has constructed to send to the CDP. | Method | Type | Description | | --------------------- | -------------------------------------------------------------------------------------- | -------------------------------------------------------- | | `cartViewed` | `(props: CartViewedInput, event: CartViewed) => CartViewed` | Event triggered when a cart is viewed. | | `checkoutStarted` | `(props: CheckoutStartedInput, event: CheckoutStarted) => CheckoutStarted` | Event triggered when the checkout process starts. | | `couponApplied` | `(props: CouponAppliedInput, event: CouponApplied) => CouponApplied` | Event triggered when a coupon is successfully applied. | | `couponDenied` | `(props: CouponDeniedInput, event: CouponDenied) => CouponDenied` | Event triggered when a coupon is denied. | | `couponEntered` | `(props: CouponEnteredInput, event: CouponEntered) => CouponEntered` | Event triggered when a coupon code is entered. | | `couponRemoved` | `(props: CouponRemovedInput, event: CouponRemoved) => CouponRemoved` | Event triggered when a coupon is removed. | | `emailCaptured` | `(props: EmailCapturedInput, event: EmailCaptured) => EmailCaptured` | Event triggered when an email is captured. | | `productAdded` | `(props: ProductAddedInput, event: ProductAdded) => ProductAdded` | Event triggered when a product is added to the cart. | | `productClicked` | `(props: ProductClickedInput, event: ProductClicked) => ProductClicked` | Event triggered when a product is clicked. | | `productListFiltered` | `(props: ProductListFilteredInput, event: ProductListFiltered) => ProductListFiltered` | Event triggered when a product list is filtered. | | `productListViewed` | `(props: ProductListViewedInput, event: ProductListViewed) => ProductListViewed` | Event triggered when a product list is viewed. | | `productRemoved` | `(props: ProductRemovedInput, event: ProductRemoved) => ProductRemoved` | Event triggered when a product is removed from the cart. | | `productViewed` | `(props: ProductViewedInput, event: ProductViewed) => ProductViewed` | Event triggered when a product is viewed. | | `productsSearched` | `(props: ProductsSearchedInput, event: ProductsSearched) => ProductsSearched` | Event triggered when products are searched. | | `signedIn` | `(props: SignedInInput, event: SignedIn) => SignedIn` | Event triggered when a user signs in. | | `signedOut` | `(props: SignedOutInput, event: SignedOut) => SignedOut` | Event triggered when a user signs out. | | `signedUp` | `(props: SignedUpInput, event: SignedUp) => SignedUp` | Event triggered when a user signs up. | ### Example event formatter In this example, let's add an additional property to the "Signed In" event to track whether the user signed in by clicking the yellow button or the purple button. The code used to send "Signed In" looks like this: ```typescript chord.trackSignedIn({ email: 'hello@chord.co', button: 'purple' }) ``` As written, Chord will ignore the `button` property and not include it in the event sent to the CDP, because it's not part of Chord's tracking plan. To include the `button` property in the event, add an event formatter: ```typescript import { CartInput, Cart, ChordAnalytics } from '@chordcommerce/analytics' const signedInFormatter: (props: SignedInInput, event: SignedIn) => SignedIn = (props, event) => { return { ...event, button: props.button } } const chord = new ChordAnalytics({ ... formatters: { events: { signedIn: signedInFormatter, ... }, } }) ``` # [title] Introduction [path] Using with Shopify/ ## Using Chord with a Shopify theme Chord offers a Javascript tracking library designed specifically for Shopify themes. Just copy and paste the Chord tracking snippet into your theme (see [**Installing in a Shopify Theme**](docId\:rinNaZDf89r6M_QK4V21_)), and you'll immediately see your storefront send these events to the CDP: - A `page` event for every page view - An `identify` event for every page view for a logged in user - The following `track` events: - "Cart Viewed" - "Checkout Started" - "Email Captured" - "Order Completed" - "Product Clicked" - "Product Viewed" You can also add more `track` events from Chord's tracking plan, or any of your own custom events. You'll also need to configure your store to send server events. See [**Enabling Server Events**](docId\:WcF7IQZjgR3JSnU9IU0pZ). ## Using Chord with a headless Shopify site For headless sites, Chord recommends using the `@chordcommerce/analytics` package. See [**Installing Chord Analytics**](docId:1nV6KpJcW0tgvWZw1SoRK) to get started. If you're using `checkout.liquid`, you'll need to add Chord's Liquid tracking snippet to track your Shopify Checkout flow. This will provide `page` events, `identify` events, and "Order Completed" `track` events. See [**Installing in a Shopify Theme**](docId\:rinNaZDf89r6M_QK4V21_). You'll also need to configure your store to send server events. See [**Enabling Server Events**](docId\:WcF7IQZjgR3JSnU9IU0pZ). ## Server events In addition to the front-end tracking events from your theme, Chord also sends server events to the CDP in response to webhook triggers from Shopify. Currently, Chord's server events include `identify` events and these `track` events: - "Checkout Started" - "Order Completed" - "Order Refunded" Server events need to be configured for all Shopify sites. The process is the same for headless sites and sites using Shopify themes. For instructions on configuring, see [**Enabling Server Events**](docId\:WcF7IQZjgR3JSnU9IU0pZ). [title] Untitled [path] / [title] Enabling Subscription Events [path] Using with Shopify/Untitled/ Chord typically sends tracking events to the CDP from two sources via your storefront: - Your **website front-end source**, either using the Chord Shopify web pixel or `@chordcommerce/analytics`, and - Chord's **server events service source**, which sends tracking events from a Shopify custom source function in your CDP workspace in response to webhook triggers from Shopify. When Chord provisions your CDP workspace, it will include Chord's Shopify webhook source. This code listens for webhook events from Shopify and transforms them into CDP events. # Subscription Webhook Topics Shopify makes availalbe *subscription-specific* webhook topics that can be emitted via your store to the Chord CDP (much like order & checkout creation), however **Shopify limits **`subscription contracts`** events to the app that created the contract (i.e. Shopify Subscriptions, Recharge).** :::hint{type="warning"} **Shopify limits Subscription Contracts events to the app that created the contract (i.e. Shopify Subscriptions, Recharge).** ::: As a result, the ***Chord webhook event app*** installed within your Shopify store will be unable to listen for subscription-specific webhook events; given this, a workaround to faciliate ingestion of these events is possible through the use of ***Shopify Flow***. The following *subscription *webhook topics are supported through this implementation: - `subscription_contracts/create`**: **sends Chord's `Subscription Created` event - `subscription_contracts/cancel`**: **sends Chord's `Subscription Canceled` event - `subscripton_contracts/pause`**: **sends Chord's `Subscription Paused` event - `subscripton_contracts/expire`**: **sends Chord's `Subscription Expired` event - `subscription_billing_attempts/failure`: sends Chord's `Subscription Payment Failed` event # Shopify Flow [**Shopify Flow**](https://apps.shopify.com/flow) is your automation and integration platform for ecommerce. Flow makes it easy to build custom workflows to automate marketing, order fulfillment, inventory management, fraud prevention, and more. Boost productivity and reclaim your time by automating tasks, streamlining business processes, customizing how your store works, or connecting to your favorite apps and external services. - Automate with hundreds of workflow templates for ecommerce tasks. - Add custom logic and unlimited actions to any automation. - Integrate with tags, metafields, B2B, Slack, Google Sheets, and more. ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/HxKGnNUVvktvQO9dt5_Ck_image.png) :::hint{type="info"} The ***Shopify Flow app*** can be used to create workflows that listen for/ingest Subscription-specific webhook events and sends them through to your Chord CDP backend source. ::: ## Assumptions Before installing the Shopify Flow App and creation of the subscription-specific webhook events, confirm with your Chord implementation team that the corresponding[** back-end webhook eventing app**](https://docs.chord.co/server-event-tracking#creating-an-admin-api-key) has been installed on your Shopify store. **The following steps are assumed:** - Chord already has access to your Shopify store; - You have access to the Chord CDP; - Shopify Flow app is either already in-use or is installed; and - The subscription events to be configured are: - `Subscription Created` - `Subscription Cancelled` - `Subscription Paused` - `Subscription Expired` - `Subscription Payment Failed` ## Installation As a free app, you should be able to easily install* Shopify Flow* within your Shopify store. It is possible that your Chord implementation team has already installed the app and if so, will have already installed the flows below. If there are any questions on whether the app is present or if these flows have already been set-up, please reach out to [**help@chord.co**](mailto\:help@chord.co)***.*** ### **Importing Flows** Click `Import Flow`and import the provided ***.flow*** files below: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/6QkTXuCVCER9C6e-KkZ2y_image.png" signedSrc size="80" width="1422" height="811" position="center" caption darkWidth="1422" darkHeight="811"} ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/-OEWGi--9ofn5wVQHTC1k_image.png" signedSrc size="80" width="3326" height="1908" position="center" caption darkWidth="3326" darkHeight="1908"} ### .flow Files Take these .flow files and ipmort them into your Shopify Flow app import modal: ::File[]{src="https://archbee-doc-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/5y7G4qZsJN9ZdROhB0Z04_chord-subscription-contract-created.flow" signedSrc="https://archbee-doc-uploads.s3.us-east-1.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/5y7G4qZsJN9ZdROhB0Z04_chord-subscription-contract-created.flow?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIAYQNQCIXNP4ETOSXW%2F20260210%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260210T155749Z&X-Amz-Expires=86400&X-Amz-Signature=4baf4322c82dd4d16c5bad23284b44c88aa850ec092cfb4a546c5822423af0f2&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject" label="[CHORD] - Subscription Contract Created.flow" isUploading="false"} ::File[]{src="https://archbee-doc-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/yGLJXe9CVt4o1hXUayzka_chord-subscription-updated-cancelled-expired-paused.flow" signedSrc="https://archbee-doc-uploads.s3.us-east-1.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/yGLJXe9CVt4o1hXUayzka_chord-subscription-updated-cancelled-expired-paused.flow?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIAYQNQCIXNP4ETOSXW%2F20260210%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260210T155756Z&X-Amz-Expires=86400&X-Amz-Signature=e7bad3cb4b88f59da324e00c2d14751f52c0d791a48c671cd267b85b696f5366&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject" label="[CHORD] - Subscription Updated (Cancelled __ Expired __ Paused).flow" isUploading="false"} ::File[]{src="https://archbee-doc-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/mUHVzuGKRt8aYNiLFWt-X_chord-subscription-payment-failed.flow" signedSrc="https://archbee-doc-uploads.s3.us-east-1.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/mUHVzuGKRt8aYNiLFWt-X_chord-subscription-payment-failed.flow?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIAYQNQCIXNP4ETOSXW%2F20260210%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260210T155813Z&X-Amz-Expires=86400&X-Amz-Signature=d9c16cf64bc151c90728e6ca62c27bcff31d0e96cd05259e4ef7e2ea0dfe0058&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject" label="[CHORD] - Subscription Payment Failed.flow" isUploading="false"} **Validate & Review** - Verify the configuration in Shopify: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/L2899i4aO8gZMxQol5edq_image.png" signedSrc="https://archbee-image-uploads.s3.us-east-1.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/L2899i4aO8gZMxQol5edq_image.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIAYQNQCIXNP4ETOSXW%2F20260210%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260210T152320Z&X-Amz-Expires=86400&X-Amz-Signature=87a072f2b82ada77e07e4e423419113a886f00b7b3c1001ccda0d19bf4360503&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject" size="100" caption isUploading="false" width="2808" height="1758" darkWidth="2808" darkHeight="1758" indent="1"} - Verify the successful delivery of events in Chord CDP from your configured Back-End Source: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/hTPOVXSXnrn61SBlMSjGa_image.png" signedSrc size="80" width="1433" height="813" position="center" caption darkWidth="1433" darkHeight="813"} ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/TyECDCV4qTEPLCwR4eZEl_image.png" signedSrc size="80" width="3326" height="1918" position="center" caption darkWidth="3326" darkHeight="1918"} :::hint{type="danger"} If you are experiencing any issues with configuring webhooks in Shopify or do not see Subscription events in your CDP back-end source, please reach out to [**help@chord.co**](mailto\:help@chord.co) with any questions/concerns. ::: [title] Shopify Theme API Reference [path] Using with Shopify/ ### trackCartViewed The “Cart Viewed” event is sent automatically from a page with `/cart` in the URL. If you’re using a cart overlay on other pages, here’s an example of how you can add the event: ```tsx chord.trackCartViewed() ``` If an object with a `cart` property is not provided as an argument, Chord fetches data about the cart from [**Shopify’s Ajax API**](https://shopify.dev/docs/api/ajax/reference/cart#get-locale-cart-js). ### trackCheckoutStarted The “Checkout Started” event is sent automatically when the `submit` [**event**](https://developer.mozilla.org/en-US/docs/Web/API/HTMLFormElement/submit_event) fires on a form with CSS selector `form[action="/cart" i][method="post"]`. This selector works with Shopify’s `{% form 'cart', cart %}` tag ([**see docs**](https://shopify.dev/docs/api/liquid/tags/form#form-cart)). If the site is using custom “Check out” buttons or forms, you can either adjust the CSS selector or add the event in Javascript. If the CSS selector is a `form` element, the event will be sent when the form’s `submit` event fires. Otherwise, the event will be sent when the `click` event fires. ```jsx const chord = new ChordAnalytics({ autoInstrumentSelectors: { 'Checkout Started': 'form#checkout' }, ...rest }); ``` If the element is added after `ChordAnalytics` is initialized, call `chord.autoInstrument()` to rescan the page and re-attach event handlers. Here’s how you can add the event in Javascript: ```tsx chord.trackCheckoutStarted() ``` ### trackCouponApplied The “Coupon Applied” event is not sent automatically. Here’s an example of how you can add the event: ```tsx chord.trackCouponApplied({ couponName: '50off' }) ``` ### trackCouponDenied The “Coupon Denied” event is not sent automatically. Here’s an example of how you can add the event: ```tsx chord.trackCouponDenied({ couponName: '50off', reason: 'expired' }) ``` ### trackCouponEntered The “Coupon Entered” event is not sent automatically. Here’s an example of how you can add the event: ```tsx chord.trackCouponEntered({ couponName: '50off' }) ``` ### trackCouponRemoved The “Coupon Removed” event is not sent automatically. Here’s an example of how you can add the event: ```tsx chord.trackCouponRemoved({ couponName: '50off' }) ``` ### trackEmailCaptured The “Email Captured” event is sent automatically when the `submit` [**event**](https://developer.mozilla.org/en-US/docs/Web/API/HTMLFormElement/submit_event) fires on a form with CSS selector `form[action="/contact#contact_form" i][method="post"], form[action="/contact#contactform" i][method="post"]`. The email address is read from the `contact[email]` input element in the form. This selector works with Shopify’s `{% form 'contact' %}` and `{% form 'customer' %}` tags ([**see docs**](https://shopify.dev/docs/api/liquid/tags/form#form-contact)). If the site is using other methods to capture email addresses, you can either adjust the CSS selector or add the event in Javascript. If you adjust the CSS selector, keep it mind it has to be a selector of a `form` element, because the listener is listening for a `submit` event. Here’s how you can adjust the CSS selector: ```jsx const chord = new ChordAnalytics({ autoInstrumentSelectors: { 'Email Captured': 'form#newsletter' }, ...rest }); ``` If the element is added after `ChordAnalytics` is initialized, call `chord.autoInstrument()` to rescan the page and re-attach event handlers. Here’s how you can add the event in Javascript: ```tsx chord.trackEmailCaptured({ email: 'test@chord.co', placementComponent: 'footer' }) ``` ### trackProductAdded The “Product Added” event is not sent automatically. Here’s an example of how you can add the event: ```text chord.trackProductAdded({ product: { handle: formData.get("handle"), quantity: formData.get("quantity"), variantId: formData.get("id"), } }) ``` We recommend sending the event after the product has been successfully added to the cart, not before. ### trackProductClicked The “Product Clicked” event is sent automatically when an HTML element matching the CSS selector `a[href*="/products/" i]` is clicked. The product handle is read from the `href` element and used to fetch product details from [**Shopify’s Ajax API**](https://shopify.dev/docs/api/ajax/reference/cart#get-locale-cart-js). You can customize the CSS selector. If you adjust the CSS selector, keep it mind it has to be a selector of an element with an `href` to the product page that will be the target of a `click` event. Here’s how you can adjust the CSS selector: ```jsx const chord = new ChordAnalytics({ autoInstrumentSelectors: { 'Product Clicked': 'a.product[href*="/products/" i]' }, ...rest }); ``` If the element is added after `ChordAnalytics` is initialized, call `chord.autoInstrument()` to rescan the page and re-attach event handlers. Here’s how you can add the event in Javascript: ```text chord.trackProductClicked({ listName: 'Related Products', product: { handle: 'product-1', }, }) ``` ### trackProductViewed The “Product Viewed” event is sent automatically from a page with `/product` in the URL. Here’s an example of how you can add the event elsewhere: ```jsx chord.trackProductViewed({ product: { handle: 'product-1', }, }) ``` ### trackProductListViewed The “Product List Viewed” event is not sent automatically. Here’s an example of how you can add the event: ```text {% assign selectedCollection = block.settings.collection %} ``` `products` can be either an array of product handles, in which case Chord will fetch the product details from [**Shopify’s Ajax API**](https://shopify.dev/docs/api/ajax/reference/cart#get-locale-cart-js), or an array of product objects, like this: ```tsx ``` `products` represents the products that were actually viewed, not every product in the collection. ### trackProductsSearched Sends a “Products Searched” event. ```tsx chord.trackProductsSearched({ query: 'pizza' }) ``` ### trackSignedIn This event should be sent after the user successfully signs in. Here’s how you can add the event in Javascript: ```tsx chord.trackSignedIn({ email: 'test@chord.co' }) ``` ### trackSignedOut This event should be sent after the user successfully signs out. Here’s how you can add the event in Javascript: ```tsx chord.trackSignedOut({ email: 'test@chord.co' }) ``` ### trackSignedUp This event should be sent after the user successfully signs up. Here’s how you can add the event in Javascript: ```tsx chord.trackSignedUp({ email: 'test@chord.co' }) ``` ### Identify Your website should send an `identify` event to the CDP every time identifying information is captured about the current user. This library automatically sends an `identify` event in these scenarios: - On every page load by an authenticated user. This code is in `chord.liquid` and can be modified if desired. - When the `Email Captured` event is sent automatically. `identify` is not sent when you call `chord.trackEmailCaptured` manually. If you're capturing identifying information like an email address in a situation that's not covered above, we recommend you add the `identify` event in Javascript to send this information to the CDP. For example, you might have a newsletter sign up form or a form where users can change their default shipping address. Here’s how you can add the `identify` event in Javascript: ```jsx chord.identify(userId, { name: "Chord Commerce", email: "test@chord.co" }); ``` `userId` in the above example is the stringified [**Shopify customer id**](https://shopify.dev/docs/api/liquid/objects/customer#customer-id). The second argument is an object representing user traits. If the `userId` is not available, omit this argument and send the object of user traits as the first argument. *Never* send an email address or other value as the user ID. For example, if you are adding an `identify` event to a newsletter signup form, it should look like this: ```jsx chord.identify({ email: "test@chord.co" }); ``` If you’re sending a `track` event at the same time as an `identify` event, we recommend sending `identify` first and the `track` event second. Some integrations require an `identify` event before they can process `track` events. ### reset The `reset` method sends a `reset` event to the CDP tracking library. This does not result in an event appearing in the CDP. It resets the user’s session in the browser, which means the user will receive a new anonymous identifier and any previous user data will be cleared. We recommend calling the `reset` method after a user has successfully logged out of their account. ### track The `track` method sends a `track` event to the CDP: ```typescript chord.track('Navigation Clicked', { label: 'Home', location: 'main nav', url: '/' }) ``` `track` can be used to send any event to the CDP, including events in the Chord tracking plan. However, we recommend using an event-specific method like `trackProductViewed` instead if one is available, so that Chord's library can construct the event body to match the tracking plan. See the individual event tracking methods above. `track` simply sends the second argument directly to the CDP as the event body. `track` does not transform property names from camel case to snake case; event properties will be sent to the CDP exactly as written. We recommend using snake case for all event properties. `null` values will be stripped by default unless `stripNull` is set to `false` in the library options. [title] Unifying Data Across Sources [path] 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 Segment, 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 Segment events. For Shopify sites, these identifiers should be added as cart attributes. If using the Shopify Storefront API, this can be done using the [`cartAttributesUpdate`](https://shopify.dev/docs/api/storefront/2023-10/mutations/cartAttributesUpdate) mutation. :::hint{type="info"} Chord's analytics library for [**Introduction**](docId\:F1GgUYhQkivbDBBoTaDZS) saves identifiers as cart attributes automatically. If you're using this library, you don't need to do anything else. ::: At minimum, a cart attribute named `segmentId` or `_cdpAnonymousId` must be added with the value being the anonymous ID assigned to the user in the browser. 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 with the key `googleClientId` or `_googleClientId` and 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] Untitled [path] / [title] Release Notes [path] / [title] @chordcommerce/analytics [path] Release Notes/ ## v1.8.0 (2024-03-21) **Features** - add `trackNavigationClicked` - add `trackCheckoutStepCompleted` - add `trackCheckoutStepViewed` - add `trackVariantClicked` - add `trackLoginStarted` - add `trackSubscriptionCancelled` - add `trackPaymentInfoEntered` ## v1.7.0 (2024-03-07) **Features** - add type parameter to ChordAnalytics ## v1.6.0 (2024-03-05) **Features** - publish to npm registry ## v1.5.1 (2024-02-14) **Bug Fixes** - address linter errors and warnings - remove no longer needed eslint disableds ## v1.5.0 (2024-01-19) **Features** - add cdp and logger methods to ChordAnalytics - add comments for cdp() and logger() ## v1.4.0 (2024-01-18) **Features** - add enableLogging option ## v1.3.0 (2024-01-17) **Features** - add page method to ChordAnalytics ## v1.2.0 (2024-01-16) **Features** - support function to return the CDP instance ## v1.1.1 (2023-12-07) **Bug Fixes** - clean up input types ## v1.1.0 (2023-12-07) **Features** - set up eslint config for core package ## v1.0.3 (2023-12-05) **Bug Fixes** - semantic release config file format - update package for node compatibility ## v1.0.2 (2023-12-05) **Bug Fixes** - add missing dep to liquid package - update module type to support imports ## v1.0.1 (2023-12-05) **Bug Fixes** - remove zero price fallback - strip null values from arrays - update tracking plan to latest ## v1.0.0 (2023-12-05) **Features** - rename package - initial release [title] Untitled [path] / [space] Chord Data Attribute Definitions (/chord-data-definitionschord-oms) [title] Sales [path] Shopify/ ### extend\_x\_fct\_trans\_orders\_multipay | Name | Description | | ------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Order Contains Fulfillment Order | Whether the order contains a fulfillment order. | | Order Contains Multipay Subscription Installment | Whether the order contains a multipay order. | | Order Contains Payment Order | Whether the order contains a payment order. | | Order Installment Charge Ids | Array of Recharge charge ids for the installments in the order, if there is more than one multipay subscription represented, there will be a unique array per installment. | | Order Installment Recharge Order Ids | Array of Recharge order ids for the installments in the order, if there is more than one multipay subscription represented, there will be a unique array per installment. | | Order Installment Shopify Order Ids | Array of the Shopify order ids for the installments in the order, if there is more than one multipay subscription represented, there will be a unique array per installment. | | Order Included Installment Count | Count of total installments in the order. | | Order Included Payment Plans | Array of payment plans included in the order. If an order contains multiple subscriptions, each subscription will be represented. | | Average Total Child Refunds | The total adjusted dollars that were refunded to a child installment order for paid orders. | | Average Total Child Shipping Received | Total shipping paid for child orders within an installment. Shipping is included for the first installment order of a child-only order if the order is mixed. If the order contains a fulfillment order, the shipping will remain attached to the fulfillment order. | | Average Total Child Unit Price Received | The total unit price received for child order payments for the installment. Payments are included if the payment status is recorded as `success`, `refunded`, or `partially_refunded`. | | Average Total Fulfillment Unit Price Received | The total unit price received for fulfillment order payments for the installment. Payments are included if the payment status is recorded as `success`, `refunded`, or `partially_refunded`. | | Average Total Subscription Installment Value | The total unit price of the installment, calculated as `fulfillment order (unit price * quantity) * total expected payments`. | | Average Total Unit Price Remaining | The total installment value minus the total fulfillment and child payments received. | | Average Total Estimated Shipping Price | The total estimated shipping across all installments in the order. | | Average Total Estimated Item Tax | The total estimated item tax across all installments in the order. | | Average Total Estimated Shipping Tax | The total estimated shipping tax across all installments in the order. | | Total Child Refunds | The total adjusted dollars that were refunded to a child installment order for paid orders. | | Total Child Shipping Received | Total shipping paid for child orders within an installment. Shipping is included for the first installment order of a child-only order if the order is mixed. If the order contains a fulfillment order, the shipping will remain attached to the fulfillment order. | | Total Child Unit Price Received | The total unit price received for child order payments for the installment. Payments are included if the payment status is recorded as `success`, `refunded`, or `partially_refunded`. | | Total Fulfillment Unit Price Received | The total unit price received for fulfillment order payments for the installment. Payments are included if the payment status is recorded as `success`, `refunded`, or `partially_refunded`. | | Total Subscription Installment Value | The total unit price of the installment, calculated as `fulfillment order (unit price * quantity) * total expected payments`. | | Total Unit Price Remaining | The total installment value minus the total fulfillment and child payments received. | | Total Estimated Shipping Price | The total estimated shipping across all installments in the order. | | Total Estimated Item Tax | The total estimated item tax across all installments in the order. | | Total Estimated Shipping Tax | The total estimated shipping tax across all installments in the order. | ### x\_fct\_trans\_sales | 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. | | 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. | | First Fulfillment Id | Unique identifier for a Shopify Fulfillment at a specific point in time | | First Fulfillment Oms Fulfillment Id | Unique key generated by Shopify that identifies a fulfillment. | | First Fulfillment Shipment Status | Represent the status of the shipment. | | First Fulfillment Status | The status of the fulfillment. | | First Fulfillment Tracking Company | The name of the tracking company. | | First Fulfillment Tracking Numbers | A list of tracking numbers provided by the tracking company. | | First Fulfillment Tracking Urls | The URLs of tracking pages for the fulfillment. | | Last Transaction Amount | The amount of money included in the transaction. | | Last Transaction Error Code | The error code explaining why the transaction failed. | | Last Transaction Gateway | The name of the gateway the transaction was issued through. | | Last Transaction Id | Unique identifier for a Shopify Transaction at a specific point in time | | Last Transaction Is Failed | Whether or not the transaction / payment has failed. | | Last Transaction Is Successful | Whether or not the transaction / payment has succeeded. | | Last Transaction Is Test | Whether this is a test transaction or not. | | Last Transaction Kind | The type of transaction. | | Last Transaction Message | Additional information provided the payment provider about the transaction. | | Last Transaction Oms Transaction Id | Unique key generated by Shopify that identifies a transaction. | | Last Transaction Status | The status of the transaction. | | Location Id | Unique identifier for a Shopify Location at a specific point in time | | Location Is Active | Whether the location is active or not. | | Location Is Online | Whether or not this location represents an online location. | | Location Is Physical | Whether or not this location represents a physical location. | | Location Name | The name of a location. | | Location Oms Location Id | Unique key generated by Shopify that identifies a location. | | Order Admin Url | Contains the full URL directing to the admin dashboard of Shopify for that given order. | | Order App Id | The ID of the app from Shopify that created the order. | | Order App Name | App name associated with the app id. This field will be generated if the Hub Configuration is enabled and the value has been set. | | Order Applied Discount Codes | The discount `codes` applied or a given order. | | Order Applied Discount Codes Count | The total number of applied discount code for a given order. | | Order Cancel Reason | The reason as to why the order was cancelled. | | Order Cart Website Locale | When available, this is the shopify international site activated prior to cart creation. | | Order Completed Order Rank By User | Allows to rank customer carts by completion date. In other words, this will rank the customer's completed order from 1 to X (X being the most recent order that was completed). | | Order Completed Subscription Order Rank By User | Allows to rank customer subscription orders by completion date. | | Order Contains First Subscription Order | A boolean value to indicate whether an order contains the first subscription order or not. An order may contain a mix of first and recurring subscriptions. | | Order Created Order Rank By User | Allows to rank customer carts by creation date. In other words, this will rank the customer's creation order from 1 to X (X being the last order that was created). An order can be created but never completed. | | Order Created Subscription Order Rank By User | Allows to rank customer subscription orders by creation date. | | Order Customer Lifetime Month | Number of months between the current order's creation date and the user's first order creation date. First orders have a value of 1. | | Order Customer Lifetime Week | Number of weeks between the current order's creation date and the user's first order creation date. First orders always have a value of 1. | | Order Filtered Order | Whether or not this order will be flagged by custom filter. | | Order Financial State | The status of transaction associated with the order. | | Order Fulfillment State | The summarized status of the `shipment/fulfillment` associated with the order. | | Order Has Discount | Whether or not the order has had a discount applied to it. | | Order Has Order Tag | Whether or not the order has an order tag applied to it. | | Order Id | Unique identifier generated by Chord for an order. | | Order Included Fulfillment Codes | Aggregated array of fulfillment codes, represented as a string. | | Order Included Fulfillment Methods | Aggregated array of fulfillment methods, represented as a string. | | Order Included Payment Gateways | This is the rolled up successful payment gateway for an order. Successful payments are included if they are sale or capture transactions. | | Order Included Source Subscription Ids | String list of included source subscription ids per order. Subscription information received from tenant-enabled platforms including Recharge and Shopify Plus. | | Order Included Subscription Ids | String list of included subscription ids per order. Subscription information received from tenant-enabled platforms including Recharge and Shopify Plus. | | Order Is Admin | Whether or not the order was created by an admin. | | Order Is Cancelled | Whether or not the order was cancelled. If \`cancelled\_at\` is non-null then we consider the order has being cancelled. | | Order Is Completed | Whether or not the order was completed. An order is considered completed if it has a closed\_at timestamp and has been fully fulfilled. Closed\_at 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. | | Order Is First Completed Order | Whether the order was the customer's first completed order or not. | | Order Is First Order | Whether the order was the customer's first order or not. | | Order Is First Subscription Completed Order | Whether the order was the customer's first completed subscription order or not. | | Order Is First Subscription Order | Whether the order was the customer's first subscription order or not. | | Order Is Part Of Subscription | Boolean flag to indicate whether the order was a part of a subscription plan or not. | | Order Is Test | Whether this is a test order or not. | | Order Item Id | Unique identifier generated by Chord for an order. | | Order Item Is First Product Type Order | Whether this order contains the first product type basket for the user. | | Order Item Is Last Product Type Order | Whether this order contains the last, most recent, product type basket for the user. | | Order Item Is Repeat Product Type Order | Whether this order contains a repeat product type basket for the user. | | Order Item Product Basket Count | The count of products for a given order. | | Product Basket | The titles of products for a given orderarray converted to a string. | | Order Item Product Purchased Quantity | The total number of product purchased for a given order. | | Order Item Rank Product Type Order | Rank orders with the same product type basket per user. | | Order Item Unique Product Basket Count | The count of unique products for a given order. | | Unique Product Basket | The unique titles of products for a given order array converted to a string. | | Order Item Unique Product Type | The unique line item product types for a given order. | | Order Item Unique Variant Basket Count | The count of unique SKUs for a given order. | | Unique Variant Basket | The unique SKUs of variants for a given order array converted to a string. | | Order Item Variant Basket Count | The count of variants for a given order. | | Variant Basket | The SKUs of variants for a given order array converted to a string. | | Order Item Variant Purchased Quantity | The total number of variants purchased for a given order. | | Order Name | Unique name generated by Shopify that is displayed to the customer (e.g. | | Order Number Of Non Reactivated Subscriptions | Number of non reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Order Number Of Reactivated Subscriptions | Number of reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Order Oms Order Id | Unique key generated by Shopify that identifies an order. | | Order Tags | The order tags applied to a given order, in alphabetical order. | | Order Tags Count | The total number of order tags for a given order. | | Order Processing Method | How the payment was processed. | | Order Segment Anonymous Id | When available, this is where we store Segment's anonymous\_id at the time of checkout. | | Order Source Name | Where did the order get created from. | | 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. | | 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 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. | | Order Cancelled At (Universal) | Reflects when the order was cancelled in Shopify - Universal Time Zone. | | Order Completed At (Central) | The timestamp when this order became completed - Cental Time Zone. | | Order Completed At (Eastern) | The timestamp when this order became completed - Eastern Time Zone. | | Order Completed At (Mountain) | The timestamp when this order became completed - Mountain Time Zone. | | Order Completed At (Pacific) | The timestamp when this order became completed - Pacific Time Zone. | | Order Completed At (Universal) | The timestamp when this order became completed - Universal Time Zone. | | Order Created At (Central) | Reflects when the entity was first created in Shopify - Cental Time Zone. | | Order Created At (Eastern) | Reflects when the entity was first created in Shopify - Eastern Time Zone. | | Order Created At (Mountain) | Reflects when the entity was first created in Shopify - Mountain Time Zone. | | Order Created At (Pacific) | Reflects when the entity was first created in Shopify - Pacific Time Zone. | | Order Created At (Universal) | Reflects when the entity was first created in Shopify - Universal Time Zone. | | Order Last Fulfillment At (Universal) | The maximum timestamp for the last update order fulfillment - Universal Time Zone. | | Order Updated At (Universal) | Reflects when the entity was last updated in Shopify - Universal Time Zone. | | 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 Additional Tax Total | When taxes are not included in the subtotal, this is total tax added to the order. | | Average Fulfillment Tax Total | Total tax applied to the order's fulfillment fee. | | 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 Line Item Tax Total | Total tax applied to the line items of the 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 Non Reactivated Subscription Unit Total | Sum of unit price for non reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Average Payment Capture Total | Sum of successful capture transactions. | | Average Payment Total | Sum of all sales transaction with gateway of type `shopify_payments`. | | Average Product Basket Count | The count of products for a given order. | | Average Product Purchased Quantity | The total number of product purchased for a given order. | | Average Promo Total | The total discounts applied to the price of the order in the location's currency. | | Average Reactivated Subscription Unit Total | Sum of unit price for reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Average Refund Total | Sum of all the transactions that are of kind `refund` applied to the order. | | Average Tax Total | The sum of all the taxes applied to the order in the location's currency. | | Average Total Price | | | Average Transaction Total | Sum of all sale transactions for the order. | | Average Variant Basket Count | The count of variants for a given order. | | Average Variant Purchased Quantity | The total number of variants purchased for a given order. | | Additional Tax Total | When taxes are not included in the subtotal, this is total tax added to the order. | | Fulfillment Tax Total | Total tax applied to the order's fulfillment fee. | | 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. | | Line Item Tax Total | Total tax applied to the line items of the 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` | | Non Reactivated Subscription Unit Total | Sum of unit price for non reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Payment Capture Total | Sum of successful capture transactions. | | Payment Total | Sum of all sales transaction with gateway of type `shopify_payments`. | | Total Price | | | Product Basket Count | The count of products for a given order. | | Product Purchased Quantity | The total number of product purchased for a given order. | | Promo Total | The total discounts applied to the price of the order in the location's currency. | | Reactivated Subscription Unit Total | Sum of unit price for reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Refund Total | Sum of all the transactions that are of kind `refund` applied to the order. | | 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. | | Variant Basket Count | The count of variants for a given order. | | Variant Purchased Quantity | The total number of variants purchased for a given order. | ### order\_applied\_discount\_codes | Name | Description | | ---------------------------- | ----------------------------------- | | Order Applied Discount Codes | Discount code applied to the order. | ### order\_tags | Name | Description | | ---------- | ---------------------------------- | | Order Tags | Order tag(s) applied to the order. | [title] Transactions [path] 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] Conversions [path] 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] Sessions [path] 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 | | 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] Ads [path] Shopify/ ### 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] Forecasts [path] / ### dim\_tenant\_store\_daily\_forecasts | Name | Description | | ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Forecasted First Month Revenue | Forecasted First Month Revenue is a sum of the `best guess` forecasts of net revenue that will generated by users in their first month. | | Forecasted New Users Count | Forecasted New Users Count is the `best guess` forecast for the period. New users is a sum of all first time purchase users in the period. | | Forecasted Re-engaged Users Revenue | Forecasted Re-engaged Users Revenue is a sum of the `best guess` forecasted net revenue from non-first time users over the period. | | Forecasted Net Revenue | Forecasted Net Revenue is the `best guess` forecast for the period. | | Historic New Users Count | Historic New Users Count is the sum of all first time purchase users in the period. | | Historic First Month Revenue | Historic First Month Revenue is the sum all net revenue from users in their first one of purchasing. | | Historic Re-engaged Users Revenue | Historic Re-engaged Users Revenue is a sum of the non-first time user net revenue over the period. | | Historical Net Revenue | Historical Net Revenue is the sum of historical net revenue for the period. | | Forecasted Lower Bound First Month Revenue | Forecasted Lower Bound First Month Revenue is an estimated lower bound of the forecast, assuming all other factors stay constant and excluding exogenous factors such as the changes in the macro economy. | | Forecasted Lower Bound New Users | Forecasted Lower Bound New Users is an estimated lower bound of the forecast, assuming all other factors stay constant and excluding exogenous factors such as the changes in the macro economy. | | Forecasted Lower Bound Reengage Revenue | Forecasted Lower Bound Reengage Revenue is an estimated lower bound of the forecast, assuming all other factors stay constant and excluding exogenous factors such as the changes in the macro economy. | | Forecasted Lower Bound Net Revenue | Forecasted Lower Bound Net Revenue is an estimated lower bound of the forecast, assuming all other factors stay constant and excluding exogenous factors such as the changes in the macro economy. | | Forecasted Upper Bound First Month Revenue | Forecasted Upper Bound First Month Revenue is an estimated upper bound of the forecast, assuming all other factors stay constant and excluding exogenous factors such as the changes in the macro economy. | | Forecasted Upper Bound New Users | Forecasted Upper Bound New Users is an estimated upper bound of the forecast, assuming all other factors stay constant and excluding exogenous factors such as the changes in the macro economy. | | Forecasted Upper Bound Reengage Revenue | Forecasted Upper Bound Reengage Revenue is an estimated upper bound of the forecast, assuming all other factors stay constant and excluding exogenous factors such as the changes in the macro economy. | | Forecasted Upper Bound Net Revenue | Forecasted Upper Bound Net Revenue is an estimated upper bound of the forecast, assuming all other factors stay constant and excluding exogenous factors such as the changes in the macro economy. | | Date (Universal) | Date is the day that measure was completed in - Universal Time Zone. | | Forecasted First Month Revenue | Forecasted First Month Revenue is a sum of the `best guess`forecasts of net revenue that will generated by users in their first month. | | Forecasted Lower Bound First Month Revenue | Forecasted Lower Bound First Month Revenue is an estimated lower bound of the forecast, assuming all other factors stay constant and excluding exogenous factors such as the changes in the macro economy. | | Forecasted Lower bound Net Revenue | Forecasted Lower Bound Net Revenue is an estimated lower bound of the forecast, assuming all other factors stay constant and excluding exogenous factors such as the changes in the macro economy. | | Forecasted Lower Bound New Users | Forecasted Lower Bound New Users is an estimated lower bound of the forecast, assuming all other factors stay constant and excluding exogenous factors such as the changes in the macro economy. | | Forecasted Lower Bound Reengage Revenue | Forecasted Lower Bound Reengage Revenue is an estimated lower bound of the forecast, assuming all other factors stay constant and excluding exogenous factors such as the changes in the macro economy. | | Forecasted Net Revenue | Forecasted Net Revenue is the `best guess` forecast for the period. | | Forecasted New Users Count | Forecasted New Users Count is the `best guess` forecast for the period. New users is a sum of all first time purchase users in the period. | | Forecasted Reengaged Users Revenue | Forecasted Re-engaged Users Revenue is a sum of the `best guess` forecasted net revenue from non-first time users over the period. | | Forecasted Upper Bound First Month Revenue | Forecasted Upper Bound First Month Revenue is an estimated upper bound of the forecast, assuming all other factors stay constant and excluding exogenous factors such as the changes in the macro economy. | | Forecasted Upper bound Net Revenue | Forecasted Upper Bound Net Revenue is an estimated upper bound of the forecast, assuming all other factors stay constant and excluding exogenous factors such as the changes in the macro economy. | | Forecasted Upper Bound New Users | Forecasted Upper Bound New Users is an estimated upper bound of the forecast, assuming all other factors stay constant and excluding exogenous factors such as the changes in the macro economy. | | Forecasted Upper Bound Reengage Revenue | Forecasted Upper Bound Reengage Revenue is an estimated upper bound of the forecast, assuming all other factors stay constant and excluding exogenous factors such as the changes in the macro economy. | | Historic First Month Revenue | Historic First Month Revenue is the sum all net revenue from users in their first one of purchasing. | | Historic New Users Count | Historic New Users Count is the sum of all first time purchase users in the period. | | Historic Reengaged Users Revenue | Historic Re-engaged Users Revenue is a sum of the non-first time user net revenue over the period. | | Historical Net Revenue | Historical Net Revenue is the sum of historical net revenue for the period. | [title] Chord OMS [path] / ### *Table names for customers utilizing the Chord OMS* - [Activities](https://docs.chord.co/chord-data-definitions/activities) - [Ads](https://docs.chord.co/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/marketing-attribution) - [Orders](https://docs.chord.co/order) - [Sales](https://docs.chord.co/sales) - [Sessions](https://docs.chord.co/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: ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/BJD3bwQX1CdwlRvNAA_-v_image.png) :::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] Orders [path] 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 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 | | ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 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. | | First Fulfillment Id | Unique identifier for a Shopify Fulfillment at a specific point in time | | First Fulfillment Oms Fulfillment Id | Unique key generated by Shopify that identifies a fulfillment. | | First Fulfillment Shipment Status | Represent the status of the shipment. | | First Fulfillment Status | The status of the fulfillment. | | First Fulfillment Tracking Company | The name of the tracking company. | | First Fulfillment Tracking Numbers | A list of tracking numbers provided by the tracking company. | | First Fulfillment Tracking Urls | The URLs of tracking pages for the fulfillment. | | Last Transaction Amount | The amount of money included in the transaction. | | Last Transaction Error Code | The error code explaining why the transaction failed. | | Last Transaction Gateway | The name of the gateway the transaction was issued through. | | Last Transaction Id | Unique identifier for a Shopify Transaction at a specific point in time | | Last Transaction Is Failed | Whether or not the transaction / payment has failed. | | Last Transaction Is Successful | Whether or not the transaction / payment has succeeded. | | Last Transaction Is Test | Whether this is a test transaction or not. | | Last Transaction Kind | The type of transaction. | | Last Transaction Message | Additional information provided the payment provider about the transaction. | | Last Transaction Oms Transaction Id | Unique key generated by Shopify that identifies a transaction. | | Last Transaction Status | The status of the transaction. | | Location Id | Unique identifier for a Shopify Location at a specific point in time | | Location Is Active | Whether the location is active or not. | | Location Is Online | Whether or not this location represents an online location. | | Location Is Physical | Whether or not this location represents a physical location. | | Location Name | The name of a location. | | Location Oms Location Id | Unique key generated by Shopify that identifies a location. | | Order Admin Url | Contains the full URL directing to the admin dashboard of Shopify for that given order. | | Order App Id | The ID of the app from Shopify that created the order. | | Order App Name | App name associated with the app id. This field will be generated if the Hub Configuration is enabled and the value has been set. | | Order Applied Discount Codes | The discount `codes` applied or a given order. | | Order Applied Discount Codes Count | The total number of applied discount code for a given order. | | Order Cancel Reason | The reason as to why the order was cancelled. | | Order Cart Website Locale | When available, this is the shopify international site activated prior to cart creation. | | Order Completed Order Rank By User | Allows to rank customer carts by completion date. In other words, this will rank the customer's completed order from 1 to X (X being the most recent order that was completed). | | Order Completed Subscription Order Rank By User | Allows to rank customer subscription orders by completion date. | | Order Contains First Subscription Order | A boolean value to indicate whether an order contains the first subscription order or not. An order may contain a mix of first and recurring subscriptions. | | Order Created Order Rank By User | Allows to rank customer carts by creation date. In other words, this will rank the customer's creation order from 1 to X (X being the last order that was created). An order can be created but never completed. | | Order Created Subscription Order Rank By User | Allows to rank customer subscription orders by creation date. | | Order Customer Lifetime Month | Number of months between the current order's creation date and the user's first order creation date. First orders have a value of 1. | | Order Customer Lifetime Week | Number of weeks between the current order's creation date and the user's first order creation date. First orders always have a value of 1. | | Order Filtered Order | Whether or not this order will be flagged by custom filter. | | Order Financial State | The status of transaction associated with the order. | | Order Fulfillment State | The summarized status of the `shipment/fulfillment` associated with the order. | | Order Has Discount | Whether or not the order has had a discount applied to it. | | Order Has Order Tag | Whether or not the order has an order tag applied to it. | | Order Id | Unique identifier generated by Chord for an order. | | Order Included Fulfillment Codes | Aggregated array of fulfillment codes, represented as a string. | | Order Included Fulfillment Methods | Aggregated array of fulfillment methods, represented as a string. | | Order Included Payment Gateways | This is the rolled up successful payment gateway for an order. Successful payments are included if they are sale or capture transactions. | | Order Included Source Subscription Ids | String list of included source subscription ids per order. Subscription information received from tenant-enabled platforms including Recharge and Shopify Plus. | | Order Included Subscription Ids | String list of included subscription ids per order. Subscription information received from tenant-enabled platforms including Recharge and Shopify Plus. | | Order Is Admin | Whether or not the order was created by an admin. | | Order Is Cancelled | Whether or not the order was cancelled. If \`cancelled\_at\` is non-null then we consider the order has being cancelled. | | Order Is Completed | Whether or not the order was completed. An order is considered completed if it has a closed\_at timestamp and has been fully fulfilled. Closed\_at 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. | | Order Is First Completed Order | Whether the order was the customer's first completed order or not. | | Order Is First Order | Whether the order was the customer's first order or not. | | Order Is First Subscription Completed Order | Whether the order was the customer's first completed subscription order or not. | | Order Is First Subscription Order | Whether the order was the customer's first subscription order or not. | | Order Is Part Of Subscription | Boolean flag to indicate whether the order was a part of a subscription plan or not. | | Order Is Test | Whether this is a test order or not. | | Order Item Id | Unique identifier generated by Chord for an order. | | Order Item Is First Product Type Order | Whether this order contains the first product type basket for the user. | | Order Item Is Last Product Type Order | Whether this order contains the last, most recent, product type basket for the user. | | Order Item Is Repeat Product Type Order | Whether this order contains a repeat product type basket for the user. | | Order Item Product Basket Count | The count of products for a given order. | | Product Basket | The titles of products for a given orderarray converted to a string. | | Order Item Product Purchased Quantity | The total number of product purchased for a given order. | | Order Item Rank Product Type Order | Rank orders with the same product type basket per user. | | Order Item Unique Product Basket Count | The count of unique products for a given order. | | Unique Product Basket | The unique titles of products for a given order array converted to a string. | | Order Item Unique Product Type | The unique line item product types for a given order. | | Order Item Unique Variant Basket Count | The count of unique SKUs for a given order. | | Unique Variant Basket | The unique SKUs of variants for a given order array converted to a string. | | Order Item Variant Basket Count | The count of variants for a given order. | | Variant Basket | The SKUs of variants for a given order array converted to a string. | | Order Item Variant Purchased Quantity | The total number of variants purchased for a given order. | | Order Name | Unique name generated by Shopify that is displayed to the customer (e.g. | | Order Number Of Non Reactivated Subscriptions | Number of non reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Order Number Of Reactivated Subscriptions | Number of reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Order Oms Order Id | Unique key generated by Shopify that identifies an order. | | Order Tags | The order tags applied to a given order, in alphabetical order. | | Order Tags Count | The total number of order tags for a given order. | | Order Processing Method | How the payment was processed. | | Order Segment Anonymous Id | When available, this is where we store Segment's anonymous\_id at the time of checkout. | | Order Source Name | Where did the order get created from. | | 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. | | 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 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. | | Order Cancelled At (Universal) | Reflects when the order was cancelled in Shopify - Universal Time Zone. | | Order Completed At (Central) | The timestamp when this order became completed - Cental Time Zone. | | Order Completed At (Eastern) | The timestamp when this order became completed - Eastern Time Zone. | | Order Completed At (Mountain) | The timestamp when this order became completed - Mountain Time Zone. | | Order Completed At (Pacific) | The timestamp when this order became completed - Pacific Time Zone. | | Order Completed At (Universal) | The timestamp when this order became completed - Universal Time Zone. | | Order Created At (Central) | Reflects when the entity was first created in Shopify - Cental Time Zone. | | Order Created At (Eastern) | Reflects when the entity was first created in Shopify - Eastern Time Zone. | | Order Created At (Mountain) | Reflects when the entity was first created in Shopify - Mountain Time Zone. | | Order Created At (Pacific) | Reflects when the entity was first created in Shopify - Pacific Time Zone. | | Order Created At (Universal) | Reflects when the entity was first created in Shopify - Universal Time Zone. | | Order Last Fulfillment At (Universal) | The maximum timestamp for the last update order fulfillment - Universal Time Zone. | | Order Updated At (Universal) | Reflects when the entity was last updated in Shopify - Universal Time Zone. | | 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 Additional Tax Total | When taxes are not included in the subtotal, this is total tax added to the order. | | Average Fulfillment Tax Total | Total tax applied to the order's fulfillment fee. | | 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 Line Item Tax Total | Total tax applied to the line items of the 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 Non Reactivated Subscription Unit Total | Sum of unit price for non reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Average Payment Capture Total | Sum of successful capture transactions. | | Average Payment Total | Sum of all sales transaction with gateway of type `shopify_payments`. | | Average Product Basket Count | The count of products for a given order. | | Average Product Purchased Quantity | The total number of product purchased for a given order. | | Average Promo Total | The total discounts applied to the price of the order in the location's currency. | | Average Reactivated Subscription Unit Total | Sum of unit price for reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Average Refund Total | Sum of all the transactions that are of kind `refund` applied to the order. | | Average Tax Total | The sum of all the taxes applied to the order in the location's currency. | | Average Total Price | The sum of all line item prices, discounts, shipping, taxes, and tips in the | | Average Transaction Total | Sum of all sale transactions for the order. | | Average Variant Basket Count | The count of variants for a given order. | | Average Variant Purchased Quantity | The total number of variants purchased for a given order. | | Additional Tax Total | When taxes are not included in the subtotal, this is total tax added to the order. | | Fulfillment Tax Total | Total tax applied to the order's fulfillment fee. | | 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. | | Line Item Tax Total | Total tax applied to the line items of the 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` | | Non Reactivated Subscription Unit Total | Sum of unit price for non reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Payment Capture Total | Sum of successful capture transactions. | | 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 | | Product Basket Count | The count of products for a given order. | | Product Purchased Quantity | The total number of product purchased for a given order. | | Promo Total | The total discounts applied to the price of the order in the location's currency. | | Reactivated Subscription Unit Total | Sum of unit price for reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Refund Total | Sum of all the transactions that are of kind `refund` applied to the order. | | 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. | | Variant Basket Count | The count of variants for a given order. | | Variant Purchased Quantity | The total number of variants purchased for a given order. | | 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] Activities [path] 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] Orders [path] Salesforce/ ### x\_fct\_orders | Name | Description | | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Order Account Id | ID generated by chord to identify the account. | | Order Bill To Contact Id | ID of the Contact associated with the Order Summary. It represents the shopper in the storefront when not using person accounts. | | Order Billing City | Billing address city. | | Order Billing Country | Billing address country. | | Order Billing Email Address | Email address on the billing address. | | Order Billing State | Billing address state. | | Order Billing State Country | The billing state or country of the order. Default to billing country if state is unavailable. | | Order Currency Iso Code | Available only for stores with the multicurrency feature enabled. Contains the ISO code for the currency of the original Order associated with the Order Summary. The default value is USD. Possible values are: DKK—Danish Krone, EUR—Euro, GBP—British Pound, USD—U.S. Dollar. | | Order Fulfillment Ids | IDs generated by Chord to identify the fulfillments associated with the order. | | Order Fulfillment Numbers | The fulfillment numbers associated with the order. | | Order Fulfillment Statuses | The fulfillment statuses associated with the order. | | Order Has A Shipped Fulfillment | A flag marking if an order has a shipped fulfillment. | | Order Hours To First Delivery | The number of hours between when the order was created and the first fulfillment was created. | | Order Hours To Last Delivery | The number of hours between when the order was created and the last, most recent, fulfillment was created. | | Order Id | ID generated by Chord to identify the order. | | Order Is Canceled | Whether an order is canceled. | | Order Is Completed | Whether an order is 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. | | Order Number Of Fulfillments | The total number of fulfillments associated with the order.
| | Order Number Of Reimbursements | The number of reimbursements associated with an order. | | Order Oms Account Id | ID of the account or person account associated with the Order Summary. It represents the shopper in the storefront. | | Order Oms Fulfillment Ids | ID generated by the OMS to identify the order. | | Order Oms Order Id | The id generated by the OMS for the Order Summary. | | Order Oms Order Payment Summary Ids | IDs generated by the OMS to identify the payment summaries associated with the order. | | Order Oms Return Order Ids | IDs generated by the OMS to identify the returns associated with the order. | | Order Is First Order | Whether the order is first order associated with the account. | | Order Number | Name of the Order Summary. | | Order Payment Summary Ids | IDs generated by Chord to identify the payment summaries associated with the order. | | Order Original Order Id | ID of the original order associated with this Order Summary. | | Order Payment Methods | The payment methods associated with the order. | | Order Payment Types | The payment types associated with the order. | | Order Po Number | Purchase order number associated with this Order Summary. | | Order Promotion Details Collection | The promotion details associated with the Order Summary. | | Order Return Order Ids | IDs generated by Chord to identify the returns associated with the order. | | Order Return Order Numbers | The return order numbers associated with the order. | | Order Sales Channel Id | ID of the Sales Channel associated with this Order Summary. | | Order Status | Status of the order summary. Unlike the Status and Status Category fields on the order and Fulfillment Order objects, this field is optional. | | Order Tax Locale Type | The system used to handle tax on the original Order associated with the Order Summary. Gross usually applies to taxes like value-added tax (VAT), and Net usually applies to taxes like sales tax. Possible values are: Gross (displays most prices and taxes as combined values), Net (displays most prices and taxes as separate values). | | Order Utm Campaign | The UTM Campaign associated with the Order Summary. | | Order Utm Medium | The UTM Medium associated with the Order Summary. | | Order Created At (Central) | The date the Order Summary was created - Cental Time Zone. | | Order Created At (Eastern) | The date the Order Summary was created - Eastern Time Zone. | | Order Created At (Mountain) | The date the Order Summary was created - Mountain Time Zone. | | Order Created At (Pacific) | The date the Order Summary was created - Pacific Time Zone. | | Order Created At (Universal) | The date the Order Summary was created - Universal Time Zone. | | Order First Fulfillment Created At (Universal) | Timestamp when the first fulfillment for the order was created - Universal Time Zone. | | Order First Order Created At (Universal) | Timestamp when the first order was created at - Universal Time Zone. | | Order Last Fulfillment Created At (Universal) | Timestamp when the most recent, or last, fulfillment for the order was created - Universal Time Zone. | | Order Last Modified Date (Universal) | The date the Order Summary was last modified - Universal Time Zone. | | Order Ordered Date (Universal) | Date of the original order associated with this Order Summary - Universal Time Zone. | | Average Adjusted Product Total | The total adjusted product amount associated with the Order Summary. | | Average Fulfillment Total | The total adjusted filfillment amount associated with the Order Summary. | | Average Gross Revenue | Gross Revenue is the pre-tax, `pre-adjusted total line item price (unit price * quantity) + the fulfillment total`. | | Average 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`. | | Average Promo Total | The total adjustment amount associated with the Order Summary. | | Average Refund Total | | | Average Tax Total | Total tax on all Order Item Summaries belonging to this Order Summary. Equal to Total Adjusted Delivery Tax Amount plus Total Adjusted Product Tax Amount. | | Average Total Basket Value | Total line itemamount in the order. This is the equivalent of the `unit price * quantity`. | | Average Total Items | Total items in order. | | Average Total Price | Total amount, including adjustments and tax, of the Order Summary. | | Adjusted Product Total | The total adjusted product amount associated with the Order Summary. | | Total Basket Value | Total line itemamount in the order. This is the equivalent of the `unit price * quantity`. | | Fulfillment Total | The total adjusted filfillment amount associated with the Order Summary. | | Gross Revenue | Gross Revenue is the `pre-tax, pre-adjusted total line item price (unit price * quantity) + the fulfillment total`. | | Total Items | Total items in order. | | 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`. | | Total Price | Total amount, including adjustments and tax, of the Order Summary. | | Promo Total | The total adjustment amount associated with the Order Summary. | | Refund Total | | | Tax Total | Total tax on all Order Item Summaries belonging to this Order Summary. Equal to Total Adjusted Delivery Tax Amount plus Total Adjusted Product Tax Amount. | [title] Ads [path] 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] Line Items [path] Salesforce/ ### x\_fct\_order\_lines | Name | Description | | --------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Order Account Id | ID generated by chord to identify the account. | | Order Bill To Contact Id | ID of the Contact associated with the Order Summary. It represents the shopper in the storefront when not using person accounts. | | Order Billing City | Billing address city. | | Order Billing Country | Billing address country. | | Order Billing Email Address | Email address on the billing address. | | Order Billing State | Billing address state. | | Order Billing State Country | The billing state or country of the order. Default to billing country if state is unavailable. | | Order Currency Iso Code | Available only for stores with the multicurrency feature enabled. Contains the ISO code for the currency of the original Order associated with the Order Summary. The default value is USD. Possible values are: DKK—Danish Krone, EUR—Euro, GBP—British Pound, USD—U.S. Dollar. | | Order Fulfillment Ids | IDs generated by Chord to identify the fulfillments associated with the order. | | Order Fulfillment Numbers | The fulfillment numbers associated with the order. | | Order Fulfillment Statuses | The fulfillment statuses associated with the order. | | Order Has A Shipped Fulfillment | A flag marking if an order has a shipped fulfillment. | | Order Hours To First Delivery | The number of hours between when the order was created and the first fulfillment was created. | | Order Hours To Last Delivery | The number of hours between when the order was created and the last, most recent, fulfillment was created. | | Order Id | ID generated by Chord to identify the order. | | Order Is Canceled | Whether an order is canceled. | | Order Is Completed | Whether an order is 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. | | Order Line Description | Description of the Order Item Summary. This field can be edited in the OMS. | | Order Line Fulfillment Ids | ID generated by Chord to identify the fulfillment ids associated with the order item. | | Order Line Fulfillment Item Ids | IDs generated by Chord to identify the fulfillment items associated with the order item. | | Order Line Gross Unit Price | Unit price, including tax, of the Order Item Summary. This value is equal to the `single Unit Price + the amount of tax on the single Unit Price`. Note that this field is rounded. | | Order Line Id | ID generated by Chord to identify the order line. | | Order Line Is Completed | Whether an order is 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. | | Order Line Number | The order line number assigned to this Order Item Summary. For example, if this object is the third in the displayed list of Order Item Summaries belonging to the Order Summary, this value is 3. | | Order Line List Price | List price of the product represented by this Order Item Summary. | | Order Line Name | Name of the Order Item Summary. | | Order Line Number Of Fulfillments | The number of fulfillments associated with the order item. | | Order Line Oms Fulfillment Ids | ID generated by the OMS to identify the fulfillment ids associated with the order item. | | Order Line Oms Fulfillment Item Ids | ID generated by the OMS to identify the fulfillment items associated with the order item. | | Order Line Oms Order Item Id | The ID generated by the oms for the order item summary. | | Order Line Oms Return Order Ids | IDs generated by the OMS to identify the return order.
| | Order Line Oms Return Order Item Ids | IDs generated by the OMS to identify the return items associated with the order item. | | Order Line Product Code | Product code of the product represented by this Order Item Summary. | | Order Line Product Id | ID generated by chord to identify the product associated with the order line. | | Order Line Promotion Details Collection | Promotion details to of the Order Item Summary. | | Order Line Return Order Ids | IDs generated by Chord to identify the return order. | | Order Line Return Order Item Ids | IDs generated by Chord to identify the return items associated with the order item. | | Order Line Sku | The stock keeping unit (SKU) of the Product2 associated with the Order Item Summary. | | Order Line Status | Status of the Order Item Summary. The default value is ORDERED. Possible values are: ALLOCATED—Allocated, CANCELED—Canceled, FULFILLED—Fulfilled, ORDERED—Ordered, PAID—Paid, PARTIALLYALLOCATED—Partially Allocated, PARTIALLYFULFILLED—Partially Fulfilled, RESHIPPED—Reshipped, RETURNED—Returned. | | Order Line Total Fulfillment Quantity | The quantity of item in the fulfillments. | | Order Line Type | Type of the Order Item Summary. Delivery Charge indicates that the Order Item Summary represents a delivery charge. Order Product indicates that it represents any other type of product, service, or charge. Each type corresponds to one type code, shown here in parentheses. Possible values are: Delivery Charge (Charge), Order Product (Product). | | Order Line Type Code | Type code of the Order Item Summary. Charge indicates that the Order Item Summary represents a delivery charge. Product indicates that it represents any other type of product, service, or charge. Possible values are: Charge, Product. | | Order Line Unit Price | Unit price of the product represented by the Order Item Summary. | | Order Number Of Fulfillments | The total number of fulfillments associated with the order. | | Order Number Of Reimbursements | The number of reimbursements associated with an order. | | Order Oms Account Id | ID of the account or person account associated with the Order Summary. It represents the shopper in the storefront. | | Order Oms Fulfillment Ids | ID generated by the OMS to identify the order. | | Order Oms Order Id | The id generated by the OMS for the Order Summary. | | Order Oms Order Payment Summary Ids | IDs generated by the OMS to identify the payment summaries associated with the order. | | Order Oms Return Order Ids | IDs generated by the OMS to identify the returns associated with the order. | | Order Is First Order | Whether the order is first order associated with the account. | | Order Number | Name of the Order Summary. | | Order Payment Summary Ids | IDs generated by Chord to identify the payment summaries associated with the order. | | Order Original Order Id | ID of the original order associated with this Order Summary. | | Order Payment Methods | The payment methods associated with the order.
| | Order Payment Types | The payment types associated with the order. | | Order Po Number | Purchase order number associated with this Order Summary. | | Order Promotion Details Collection | The promotion details associated with the Order Summary. | | Order Return Order Ids | IDs generated by Chord to identify the returns associated with the order. | | Order Return Order Numbers | The return order numbers associated with the order. | | Order Sales Channel Id | ID of the Sales Channel associated with this Order Summary. | | Order Status | Status of the order summary. Unlike the Status and Status Category fields on the order and Fulfillment Order objects, this field is optional. | | Order Tax Locale Type | The system used to handle tax on the original Order associated with the Order Summary. Gross usually applies to taxes like value-added tax (VAT), and Net usually applies to taxes like sales tax. Possible values are: Gross (displays most prices and taxes as combined values), Net (displays most prices and taxes as separate values). | | Order Utm Campaign | The UTM Campaign associated with the Order Summary. | | Order Utm Medium | The UTM Medium associated with the Order Summary. | | Product Color | Color of the product. | | Product Id | | | Product Oms Product Id | ID generated by the OMS to identify the product.
| | Product Sku | SKU for the product. | | Product Sku Description | Description of the product. | | Order Created At (Central) | The date the Order Summary was created - Cental Time Zone. | | Order Created At (Eastern) | The date the Order Summary was created - Eastern Time Zone. | | Order Created At (Mountain) | The date the Order Summary was created - Mountain Time Zone. | | Order Created At (Pacific) | The date the Order Summary was created - Pacific Time Zone. | | Order Created At (Universal) | The date the Order Summary was created - Universal Time Zone. | | Order First Fulfillment Created At (Universal) | Timestamp when the first fulfillment for the order was created - Universal Time Zone. | | Order First Order Created At (Universal) | Timestamp when the first order was created at - Universal Time Zone. | | Order Last Fulfillment Created At (Universal) | Timestamp when the most recent, or last, fulfillment for the order was created - Universal Time Zone. | | Order Last Modified Date (Universal) | The date the Order Summary was last modified - Universal Time Zone. | | Order Line Created At (Universal) | Date the Order Item Summary was created - Universal Time Zone. | | Order Line First Fulfillment Created At (Universal) | The first created at timestamp of a fulfillment item - Universal Time Zone.
| | Order Line First Fulfillment Expected Delivery Date (Universal) | The first expected delivery date of a fulfillment item - Universal Time Zone. | | Order Line Last Fulfillment Created At (Universal) | The most recent created at timestamp of a fulfillment item - Universal Time Zone. | | Order Line Last Fulfillment Expected Delivery Date (Universal) | The most recent expected delivery date of a fulfillment item - Universal Time Zone. | | Order Line Requested Delivery Date (Universal) | Requested delivery date for the item - Universal Time Zone. | | Order Ordered Date (Universal) | Date of the original order associated with this Order Summary - Universal Time Zone. | | Average Adjusted Total Price | Line Item total, including adjustments but not tax, of the Order Item Summary. | | Average Adjustment Total | Total of all non-order-level price adjustments applied to this Order Item Summary. This value includes Order Item Adjustment Line Summaries that don’t belong to an Order Adjustment Group Summary, or that belong to an Order Adjustment Group Summary of type Split Line. | | Average Quantity | Current total quantity of products represented by this order item summary. Equal to Quantity Ordered minus (Quantity Canceled and Quantit Returned). | | Average Quantity Allocated | Allocated quantity on this order item summary. This quantity is associated with one or more Fulfillment Order Line Items. | | Average Quantity Canceled | Canceled quantity on this Order Item Summary. | | Average Quantity Fulfilled | Fulfilled quantity on this Order Item Summary. This quantity can no longer be canceled. | | Average Quantity Ordered | Ordered quantity on this Order Item Summary. It includes the originally ordered quantity plus any quantity added to the order later. | | Average Quantity Return Initiated | Quantity returned or pending return on this Order Item Summary. | | Average Quantity Returned | Returned quantity on this Order Item Summary. | | Average Quantity Shipped | The quantity of items shipped. | | Average Total Price | Total, not including adjustments or tax, of the Order Item Summary. | | Average Total Tax Amount | Tax on the Total Price. | | Adjusted Total Price | Line Item total, including adjustments but not tax, of the Order Item Summary. | | Adjustment Total | Total of all non-order-level price adjustments applied to this Order Item Summary. This value includes Order Item Adjustment Line Summaries that don’t belong to an Order Adjustment Group Summary, or that belong to an Order Adjustment Group Summary of type Split Line. | | Total Price | Total, not including adjustments or tax, of the Order Item Summary. | | Quantity | Current total quantity of products represented by this order item summary. Equal to Quantity Ordered minus (Quantity Canceled and Quantit Returned). | | Quantity Allocated | Allocated quantity on this order item summary. This quantity is associated with one or more Fulfillment Order Line Items. | | Quantity Canceled | Canceled quantity on this Order Item Summary. | | Quantity Fulfilled | Fulfilled quantity on this Order Item Summary. This quantity can no longer be canceled. | | Quantity Ordered | Ordered quantity on this Order Item Summary. It includes the originally ordered quantity plus any quantity added to the order later. | | Quantity Return Initiated | Quantity returned or pending return on this Order Item Summary. | | Quantity Returned | Returned quantity on this Order Item Summary. | | Quantity Shipped | The quantity of items shipped. | | Total Tax Amount | Tax on the Total Price. | [title] Conversions [path] 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. `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. `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. `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] Orders [path] Shopify/ ### x\_fct\_trans\_orders | 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. | | First Fulfillment Id | Unique identifier for a Shopify Fulfillment at a specific point in time | | First Fulfillment Oms Fulfillment Id | Unique key generated by Shopify that identifies a fulfillment. | | First Fulfillment Shipment Status | Represent the status of the shipment. | | First Fulfillment Status | The status of the fulfillment. | | First Fulfillment Tracking Company | The name of the tracking company. | | First Fulfillment Tracking Numbers | A list of tracking numbers provided by the tracking company. | | First Fulfillment Tracking Urls | The URLs of tracking pages for the fulfillment. | | Last Transaction Amount | The amount of money included in the transaction. | | Last Transaction Error Code | The error code explaining why the transaction failed. | | Last Transaction Gateway | The name of the gateway the transaction was issued through. | | Last Transaction Id | Unique identifier for a Shopify Transaction at a specific point in time | | Last Transaction Is Failed | Whether or not the transaction / payment has failed. | | Last Transaction Is Successful | Whether or not the transaction / payment has succeeded. | | Last Transaction Is Test | Whether this is a test transaction or not. | | Last Transaction Kind | The type of transaction. | | Last Transaction Message | Additional information provided the payment provider about the transaction. | | Last Transaction Oms Transaction Id | Unique key generated by Shopify that identifies a transaction. | | Last Transaction Status | The status of the transaction. | | Location Id | Unique identifier for a Shopify Location at a specific point in time | | Location Is Active | Whether the location is active or not. | | Location Is Online | Whether or not this location represents an online location. | | Location Is Physical | Whether or not this location represents a physical location. | | Location Name | The name of a location. | | Location Oms Location Id | Unique key generated by Shopify that identifies a location. | | Order Admin Url | Contains the full URL directing to the admin dashboard of Shopify for that given order. | | Order App Id | The ID of the app from Shopify that created the order. | | Order App Name | App name associated with the app id. This field will be generated if the Hub Configuration is enabled and the value has been set. | | Order Applied Discount Codes | The discount `codes` applied or a given order. | | Order Applied Discount Codes Count | The total number of applied discount code for a given order. | | Order Cancel Reason | The reason as to why the order was cancelled. | | Order Cart Website Locale | When available, this is the shopify international site activated prior to cart creation. | | Order Completed Order Rank By User | Allows to rank customer carts by completion date. In other words, this will rank the customer's completed order from 1 to X (X being the most recent order that was completed). | | Order Completed Subscription Order Rank By User | Allows to rank customer subscription orders by completion date. | | Order Contains First Subscription Order | A boolean value to indicate whether an order contains the first subscription order or not. An order may contain a mix of first and recurring subscriptions. | | Order Created Order Rank By User | Allows to rank customer carts by creation date. In other words, this will rank the customer's creation order from 1 to X (X being the last order that was created). An order can be created but never completed. | | Order Created Subscription Order Rank By User | Allows to rank customer subscription orders by creation date. | | Order Customer Lifetime Month | Number of months between the current order's creation date and the user's first order creation date. First orders have a value of 1. | | Order Customer Lifetime Week | Number of weeks between the current order's creation date and the user's first order creation date. First orders always have a value of 1. | | Order Filtered Order | Whether or not this order will be flagged by custom filter. | | Order Financial State | The status of transaction associated with the order. | | Order Fulfillment State | The summarized status of the `shipment/fulfillment` associated with the order. | | Order Has Discount | Whether or not the order has had a discount applied to it. | | Order Has Order Tag | Whether or not the order has an order tag applied to it. | | Order Id | Unique identifier generated by Chord for an order. | | Order Included Fulfillment Codes | Aggregated array of fulfillment codes, represented as a string. | | Order Included Fulfillment Methods | Aggregated array of fulfillment methods, represented as a string. | | Order Included Payment Gateways | This is the rolled up successful payment gateway for an order. Successful payments are included if they are sale or capture transactions. | | Order Included Source Subscription Ids | String list of included source subscription ids per order. Subscription information received from tenant-enabled platforms including Recharge and Shopify Plus. | | Order Included Subscription Ids | String list of included subscription ids per order. Subscription information received from tenant-enabled platforms including Recharge and Shopify Plus. | | Order Is Admin | Whether or not the order was created by an admin. | | Order Is Cancelled | Whether or not the order was cancelled. If \`cancelled\_at\` is non-null then we consider the order has being cancelled. | | Order Is Completed | Whether or not the order was completed. An order is considered completed if it has a closed\_at timestamp and has been fully fulfilled. Closed\_at 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. | | Order Is First Completed Order | Whether the order was the customer's first completed order or not. | | Order Is First Order | Whether the order was the customer's first order or not. | | Order Is First Subscription Completed Order | Whether the order was the customer's first completed subscription order or not. | | Order Is First Subscription Order | Whether the order was the customer's first subscription order or not. | | Order Is Part Of Subscription | Boolean flag to indicate whether the order was a part of a subscription plan or not. | | Order Is Test | Whether this is a test order or not. | | Order Item Id | Unique identifier generated by Chord for an order. | | Order Item Is First Product Type Order | Whether this order contains the first product type basket for the user. | | Order Item Is Last Product Type Order | Whether this order contains the last, most recent, product type basket for the user. | | Order Item Is Repeat Product Type Order | Whether this order contains a repeat product type basket for the user. | | Order Item Product Basket Count | The count of products for a given order. | | Product Basket | The titles of products for a given orderarray converted to a string. | | Order Item Product Purchased Quantity | The total number of product purchased for a given order. | | Order Item Rank Product Type Order | Rank orders with the same product type basket per user. | | Order Item Unique Product Basket Count | The count of unique products for a given order. | | Unique Product Basket | The unique titles of products for a given order array converted to a string. | | Order Item Unique Product Type | The unique line item product types for a given order. | | Order Item Unique Variant Basket Count | The count of unique SKUs for a given order. | | Unique Variant Basket | The unique SKUs of variants for a given order array converted to a string. | | Order Item Variant Basket Count | The count of variants for a given order. | | Variant Basket | The SKUs of variants for a given order array converted to a string. | | Order Item Variant Purchased Quantity | The total number of variants purchased for a given order. | | Order Name | Unique name generated by Shopify that is displayed to the customer (e.g. | | Order Number Of Non Reactivated Subscriptions | Number of non reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Order Number Of Reactivated Subscriptions | Number of reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Order Oms Order Id | Unique key generated by Shopify that identifies an order. | | Order Tags | The order tags applied to a given order, in alphabetical order. | | Order Tags Count | The total number of order tags for a given order. | | Order Processing Method | How the payment was processed. | | Order Segment Anonymous Id | When available, this is where we store Segment's anonymous\_id at the time of checkout. | | Order Source Name | Where did the order get created from. | | 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. | | 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 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. | | Order Cancelled At (Universal) | Reflects when the order was cancelled in Shopify - Universal Time Zone. | | Order Completed At (Central) | The timestamp when this order became completed - Cental Time Zone. | | Order Completed At (Eastern) | The timestamp when this order became completed - Eastern Time Zone. | | Order Completed At (Mountain) | The timestamp when this order became completed - Mountain Time Zone. | | Order Completed At (Pacific) | The timestamp when this order became completed - Pacific Time Zone. | | Order Completed At (Universal) | The timestamp when this order became completed - Universal Time Zone. | | Order Created At (Central) | Reflects when the entity was first created in Shopify - Cental Time Zone. | | Order Created At (Eastern) | Reflects when the entity was first created in Shopify - Eastern Time Zone. | | Order Created At (Mountain) | Reflects when the entity was first created in Shopify - Mountain Time Zone. | | Order Created At (Pacific) | Reflects when the entity was first created in Shopify - Pacific Time Zone. | | Order Created At (Universal) | Reflects when the entity was first created in Shopify - Universal Time Zone. | | Order Last Fulfillment At (Universal) | The maximum timestamp for the last update order fulfillment - Universal Time Zone. | | Order Updated At (Universal) | Reflects when the entity was last updated in Shopify - Universal Time Zone. | | 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 Additional Tax Total | When taxes are not included in the subtotal, this is total tax added to the order. | | Average Fulfillment Tax Total | Total tax applied to the order's fulfillment fee. | | 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 Line Item Tax Total | Total tax applied to the line items of the 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 Non Reactivated Subscription Unit Total | Sum of unit price for non reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Average Payment Capture Total | Sum of successful capture transactions. | | Average Payment Total | Sum of all sales transaction with gateway of type `shopify_payments`. | | Average Product Basket Count | The count of products for a given order. | | Average Product Purchased Quantity | The total number of product purchased for a given order. | | Average Promo Total | The total discounts applied to the price of the order in the location's currency. | | Average Reactivated Subscription Unit Total | Sum of unit price for reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Average Refund Total | Sum of all the transactions that are of kind `refund` applied to the order. | | Average Tax Total | The sum of all the taxes applied to the order in the location's currency. | | Average Total Price | The sum of all line item prices, discounts, shipping, taxes, and tips in the | | Average Transaction Total | Sum of all sale transactions for the order. | | Average Variant Basket Count | The count of variants for a given order. | | Average Variant Purchased Quantity | The total number of variants purchased for a given order. | | Additional Tax Total | When taxes are not included in the subtotal, this is total tax added to the order. | | Fulfillment Tax Total | Total tax applied to the order's fulfillment fee. | | 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. | | Line Item Tax Total | Total tax applied to the line items of the 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` | | Non Reactivated Subscription Unit Total | Sum of unit price for non reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Payment Capture Total | Sum of successful capture transactions. | | 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 | | Product Basket Count | The count of products for a given order. | | Product Purchased Quantity | The total number of product purchased for a given order. | | Promo Total | The total discounts applied to the price of the order in the location's currency. | | Reactivated Subscription Unit Total | Sum of unit price for reactivated subscriptions per order. Reactivation is a customer who returned after having canceled the first subscription. | | Refund Total | Sum of all the transactions that are of kind `refund` applied to the order. | | 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. | | Variant Basket Count | The count of variants for a given order. | | Variant Purchased Quantity | The total number of variants purchased for a given order. | ### order\_applied\_discount\_codes | Name | Description | | ---------------------------- | ----------------------------------- | | Order Applied Discount Codes | Discount code applied to the order. | ### order\_tags | Name | Description | | ---------- | ---------------------------------- | | Order Tags | Order tag(s) applied to the order. | [title] Line Items [path] 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 (i.e. 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 (i.e., 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] Activities [path] Shopify/ ### 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. | [title] Subscription Events [path] 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] Subscriptions [path] 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] Sessions [path] 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] Salesforce [path] / ### *Table names for customers utilizing Salesforce.* - [Activities](https://docs.chord.co/activities) - [Braze Campaigns](https://docs.chord.co/braze-campaigns) - [Conversions](https://docs.chord.co/conversions) - [Line Items](https://docs.chord.co/line-items) - [Marketing Attribution](https://docs.chord.co/marketing-attribution) - [Orders](https://docs.chord.co/order) - [Sales](https://docs.chord.co/sales) - [Sessions](https://docs.chord.co/sessions) ### Accessing Chord Data Attribute Definitions: ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/BJD3bwQX1CdwlRvNAA_-v_image.png) :::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] Ads [path] 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] Shopify [path] / ### *Table names for customers utilizing Shopify* - [Activities](https://docs.chord.co/activities) - [Conversions](https://docs.chord.co/conversions) - [Line Items](https://docs.chord.co/line-items) - [Marketing Attribution](https://docs.chord.co/marketing-attribution) - [Orders](https://docs.chord.co/order) - [Sales](https://docs.chord.co/sales) - [Sessions](https://docs.chord.co/sessions) - [Users](https://docs.chord.co/users) ### Accessing Chord Data Attribute Definitions: ![](https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/BJD3bwQX1CdwlRvNAA_-v_image.png) :::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] Sales [path] 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] Variants [path] 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] Conversions [path] Shopify/ ### 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. | | 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. | | Ts (Universal) | Timestamps representing when the order was completed - Universal Time Zone. | | Average Completed Order Count | Total count of orders completed per day, according to the orders' latest state. Orders are considered complete if they have been fulfilled. | | Average Created Order Count | Total count of orders created per day. | | Average Gross Revenue | Total gross revenue of orders completed per day. Gross revenue calculated as \`item\_total\` + \`fulfillment\_total\` | | Average Gross Sales | | | Average Net Revenue | Total gross revenue of orders completed per day. Net revenue of the order calculated as `item_total + fulfillment_total - promo_total - refund_total` | | Average Placed Gross Revenue | Total gross revenue of orders placed per day. Gross revenue calculated as `item_total + fulfillment_total` | | Average Placed Net Revenue | Total gross revenue of orders placed per day. Net revenue of the order calculated as `item_total + fulfillment_total - promo_total - refund_total` | | Completed Order Count | Total count of orders completed per day, according to the orders' latest state. Orders are considered complete if they have been fulfilled. | | Created Order Count | Total count of orders created per day. | | Gross Revenue | Total gross revenue of orders completed per day. Gross revenue calculated as `item_total + fulfillment_total` | | Gross Sales | | | Net Revenue | Total gross revenue of orders completed per day. Net revenue of the order calculated as `item_total + fulfillment_total - promo_total - refund_total` | | Placed Gross Revenue | Total gross revenue of orders placed per day. Gross revenue calculated as `item_total + fulfillment_total` | | Placed Net Revenue | Total gross revenue of orders placed per day. Net revenue of the order calculated as `item_total + fulfillment_total - promo_total - refund_total` | [title] Activities [path] 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.