Northbeam

introduction northbeam is a marketing analytics and attribution platform that helps brands measure performance across channels using multi touch attribution, media mix modeling, and real time reporting connecting northbeam as a cdp destination allows chord to send eligible commerce events to northbeam, enabling more accurate attribution and downstream analytics northbeam only processes a limited set of events, and requires a customer id to be included in all payloads (email cannot be used as customer id) this document outlines how to configure the destination and how data flows from chord getting started northbeam is a device mode destination , which means chord sends events directly from the client side to northbeam’s api before connecting, ensure you have an active northbeam account your northbeam api key your northbeam data client id clarification on which customer id field your brand will use (must not be an email) northbeam offers both a production mode and a test mode test mode accepts any credentials and routes data to a northbeam sandbox environment, making it useful for integration checks before enabling production delivery connecting to the northbeam cdp destination log into the chord data platform navigate to the cdp select the destinations tab click “add” to open the destination catalog choose northbeam from the list enter a destination name (e g , “northbeam – production”) provide the required credentials api key data client id select test mode or production mode depending on your environment click create to save and activate the destination once configured, chord will begin sending eligible events based on your cdp tracking setup what data northbeam accepts northbeam strictly processes the following event types order completed order refunded chord will forward these events only when the event includes a valid customer id the customer id is not an email address required northbeam payload fields are present if customer id is missing or incorrectly formatted, northbeam will reject the event because of these constraints, ensure your chord identity configuration maps a consistent, non email customer id for all events event payload requirements each event sent to northbeam must include customer id (required; must not be an email) order details (order id, products, value, timestamps) refund details (when applicable) chord handles payload formatting, but your implementation must ensure customer id is present on all commerce events using test mode northbeam’s test mode accepts any api key or data client id (not validated) sends events to a sandbox server , not the production environment allows teams to confirm event structure and flow before enabling production delivery we recommend connecting first in test mode verifying that order completed and order refunded events appear as expected switching to production mode only after validation troubleshooting events not appearing in northbeam confirm customer id is being sent (and is not an email) check that only order completed and order refunded events are expected verify you are not still in test mode if reviewing production dashboards northbeam rejecting events validate customer id formatting ensure the required order fields exist in your chord implementation credentials not working test mode accepts any credentials — if test mode works and production does not, confirm your api key and data client id with northbeam need help? if you’re unsure whether your data meets northbeam’s requirements or need help validating your customer id mapping, contact us at mailto\ help\@chord co chord events relevant for destination not all chord 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 https //docs northbeam io/docs/orders api are chord tracking event destination event/action order completed creates order payload via api order refunded creates refund payload via api note the only specific chord track events which prompt action downstream in the northbeam api are order completed and order refunded all other track , identify and page events are ignored 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