Northbeam

northbeam is a marketing attribution and analytics platform that provides multi touch attribution and media mix modeling this destination sends order and refund events server side from chord cdp to the northbeam orders api there is no device mode component getting started this is a cloud mode destination you will need api key — found in your northbeam dashboard under settings > api keys data client id — a uuid identifying your account, found in your northbeam dashboard under settings > api keys optionally test mode — when enabled, events are sent to northbeam's uat environment instead of production defaults to false connecting to the northbeam cdp destination 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 log into the chord data platform navigate to the cdp click the "add" button next to destinations select northbeam from the destination catalog enter the destination name, api key , and data client id optionally enable test mode during initial setup click "create" to connect events event mapping chord event northbeam action notes order completed create order order refunded create order with refunds all other events (page, identify, and other track events) are silently skipped order completed sends an order to the northbeam orders api the event is skipped if required fields are missing order attributes northbeam attribute chord source (priority order) notes order id properties order id required customer id userid > properties customer id required customer email properties email > context traits email > traits email required time of purchase timestamp iso 8601 format; falls back to current time purchase total properties total > properties revenue defaults to 0 currency properties currency defaults to "usd" tax properties tax defaults to 0 shipping cost properties shipping defaults to 0 product attributes each product in properties products\[] is required each product must have an id and name northbeam attribute chord source (priority order) notes id properties products\[] product id > properties products\[] sku required name properties products\[] name required quantity properties products\[] quantity defaults to 1 price properties products\[] price defaults to 0 ; coerced to number (accepts string values) variant id properties products\[] variant id > properties products\[] product id > properties products\[] sku always present variant name properties products\[] variant > properties products\[] name always present order refunded sends a refund to the northbeam orders api as an order payload with a refunds array the event is skipped if required fields are missing order attributes same as order completed above, except time of purchase prefers properties original timestamp over timestamp to preserve the original order date refund attributes the destination checks for an explicit properties refunds\[] array first if not present, it falls back to properties products\[] and treats all products as fully refunded from properties refunds\[] (preferred) northbeam attribute chord source (priority order) notes product id properties refunds\[] product id required variant id properties refunds\[] variant id quantity properties refunds\[] quantity defaults to 1 refund amount properties refunds\[] refund amount > properties refunds\[] amount > properties refunds\[] price required refund cost properties refunds\[] refund cost defaults to refund amount refund made at properties refunds\[] refund made at > timestamp iso 8601 format from properties products\[] (fallback) northbeam attribute chord source (priority order) notes product id properties products\[] product id > properties products\[] sku variant id properties products\[] variant id > properties products\[] product id > properties products\[] sku quantity properties products\[] quantity defaults to 1 refund amount properties products\[] price × properties products\[] quantity calculated refund made at timestamp validation both event types are validated before sending required fields order completed order id , customer id , customer email , non empty products\[] with each product having id and name order refunded order id , customer id , customer email , non empty refunds\[] with each refund having product id and refund amount testing and validation after connecting the destination, use the browser console and cdp live events to verify behavior no access to the northbeam dashboard is required order completed — happy path window\ chord track("order completed", { order id "test 001", email "test\@example com", total 89 97, tax 7 00, shipping 5 99, currency "usd", products \[ { product id "prod 001", name "classic t shirt", price 29 99, quantity 2, variant id "var 001 blk m", variant "black / medium" } ] }); in cdp live events, confirm a northbeam request payload info log appears containing the full transformed payload and messageid a 200 or 201 response log follows order completed — sku only product (no variant fields) window\ chord track("order completed", { order id "test 002", email "test\@example com", total 103 00, currency "usd", products \[ { sku "rvttg50", name "reverse tone correcting treatment", price 103, quantity 1 } ] }); in cdp live events, confirm the payload log shows id "rvttg50" , variant id "rvttg50" , variant name "reverse tone correcting treatment" (all falling back from sku and name ) no warnings are logged order refunded window\ chord track("order refunded", { order id "test 001", email "test\@example com", refunds \[ { product id "prod 001", quantity 1, refund amount 29 99 } ] }); in cdp live events, confirm the payload log shows a refunds array with the correct refund amount updated 29 apr 2026