The Twitter Ads pixel (also called the X Pixel) is a small piece of JavaScript code that you embed on your website to help measure, optimize, and target your advertising on the Twitter (X) platform.

This is a device mode destination. You will need the Twitter Ads Pixel ID to connect this destination. You can locate the Twitter Ads Pixel ID from the snippet created on the 

Connecting to the Twitter Ads CDP Destination

Enter in the destination name and the Pixel ID. 

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 availalbe event types included via the 

The corresponding Chord tracking plan events used by the 

The mapping listed above are not hardcoded within the destination itself, but rather must explicilty be configured within your destiantion set-up in the Chord CDP.

For example, map "Product Added" to "tw-qkno4-qkni5".

Each mapping must include the Chord tracking event name AND the 

. The Twitter event ID will be generated and collected via the Twitter Ads Manager.

Before connecting destinations in the Chord CDP, please verify with all Destination owners that all 

Running external destinations alongside configured Chord CDP destinations 

can result in duplicate events downstream. 

Triple Whale

Twitter Ads

CDP Functions

Chord Commerce

Chord AI Implementation Guide

Chord AI Technical Overview

Recommendations Agent

Chord Copilot Chat

Chord AI Charts

Chord AI Monitors

Chord AI Context

Available Expressions

Chord AI Modeling

Chord AI Use Cases

Chord AI FAQ

Chord AI

Analytics Homepage Overview

Browser Compatibility for Accessing the Chord Platform

Data Support for Multiple Stores

Setting up a Snowflake Share with Chord

Setting up a Transformed Data Share from Chord to Snowflake

Sharing Data with Chord from Cloud Storage

Chord Data Source Ingestion Guidelines

Dynamic Data Settings

User Management on the Chord Platform

Overview

Chord Reveal Data Attribute Definitions

Chord Reveal (Private Beta)

Pre-Built Audiences

Custom Audiences

Anonymous Audiences

Audiences API

Audiences

Data Activations

Connect Data Sources

Ads Module

Messaging Module

Sales Channel Module

E-commerce Data Ingestion

Data Sources

Marketing Attribution

Orders

Sessions

Time

Users

Chord Data Attribute Definitions

Chord's Methodology as Compared to Other Platforms

Data Models

Chord Predictive Intelligence Overview

Customer Lifetime Revenue (CLR)

Product Recommendations

Revenue Forecasts

Session Conversion Probability

Predictive Marketing Attribution

Marketing Mix Modeling (MMM)

Accessing Data Science Features

Predictive Models

Looks vs Dashboards

Creating Custom Reports

Building Cart Abandonment Audiences with the Product Abandoned Explore

Modifying a Report

Pinning and Unpinning Reports

Using Quickstarts

Downloading Reports

Scheduling Reports

Creating Custom Fields

Creating Custom Calculations

Analytics Glossary

Analytics Features

Advertising Spend

Attribution Channel Mapping

Campaign Mapping

Order App Name

Order Filter

Planned Forecasts

Variant Attributes

Model Amplifications

Chord Data Platform

Get Started with Chord CDP

CDP Sources

CDP Destination Catalog

CDP Destinations

CDP Live Events

CDP Notifications (Event Alerts)

CDP Consent Categories (Consent Management Category Mapping)

Chord CDP

Installing Chord Analytics

Verifying Your Chord Implementation

API Reference

Formatters

OMS Schema

Getting Started

Server Events Overview

Track

Server Events

Introduction

Web Pixel

Server Event Tracking

Using with Shopify

Unifying Data Across Sources

Integrations

Migrating from Segment to Chord CDP

Guides

Shopify Customer Privacy API

Consent Management

@chordcommerce/analytics

Release Notes

Chord Tracking Plan

Untitled

Chord Commerce Event Tracking

Chord OMS