Northbeam Pixel
10 min
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 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 pixel from the destination catalog enter the destination name and your data client id optionally configure custom goal ids for product viewed, add to cart, and checkout started events 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