Amplitude

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 log into the chord data platform navigate to the cdp click the "add" button next to destinations select amplitude (cloud mode) or amplitude (device mode) from the destination catalog 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 for the amplitude (device mode) destination, enter in the destination name and the amplitude api key you can also toggle track configurations click "create" to connect 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 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 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 exact match — event name matches exactly (e g , order completed) type match — event type matches (e g , track matches all track events) wildcard — matches all events (lowest priority) examples route subscription events to revenue tracking source event subscription started, subscription renewed action logpurchase rename an event source event button clicked action logeventv2 target event cta interaction map custom fields for purchase events 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 source event internal debug event action logeventv2 target event $drop 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