StackAdapt Pixel

introduction the stackadapt destination enables client side integration with stackadapt's universal pixel for programmatic advertising, retargeting, conversion tracking, and lookalike audience building getting started stackadapt is a device mode destination , meaning chord sends events directly from your website or frontend application to stackadapt’s api before connecting, ensure you have an active stackadapt account your stackadapt pixel id your stackadapt universal pixel id find this in your stackadapt account under pixels > universal pixel connecting to the stackadapt cdp destination 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 open the destinations tab click add and select stackadapt pixel from the destination catalog provide a recognizable destination name (e g , “stackadapt – production”) enter your pixel id click create to activate the destination events only supported event types will be sent; unsupported or redundant events may be dropped automatically page fires a stackadapt page view tracking call stackadapt sdk call saq("ts", pixelid) no additional attributes are sent with page events identify stores user identity traits in browser memory (keyed by pixelid ) these traits are not sent to stackadapt immediately instead, they are attached to all subsequent track conversion events for the duration of the browser session attribute mapping stackadapt trait chord source (in priority order) email properties email / properties emailaddress > context traits email > traits email first name properties first name / properties firstname > context traits first name > traits first name > first word of address name last name properties last name / properties lastname > context traits last name > traits last name > second word of address name phone properties phone / properties phonenumber > context traits phone > traits phone track sends a conversion event to stackadapt with ecommerce data and any previously stored user traits from identify calls stackadapt sdk call saq("conv", pixelid, conversiondata) conversion payload attributes always included stackadapt attribute chord source notes action event event the track event name (e g , "order completed" ) email stored from identify included if an identify call was made first name stored from identify included if an identify call was made last name stored from identify included if an identify call was made phone stored from identify included if an identify call was made order level attributes stackadapt attribute chord source (in priority order) notes order id properties cart id / properties cartid / properties order id / properties orderid / properties id included if present revenue properties revenue > properties total > properties value first defined value wins if none are set, falls back to calculated value from product prices x quantities currency properties currency > properties meta i18n currency > "usd" (default) included if present product attributes (single product) when properties products contains exactly one product, product fields are sent as flat attributes on the conversion payload stackadapt attribute chord source (in priority order) notes product id product product id / product productid > product id / product sku / product variant product category product category / product productcategory / product product category product name product name / product productname / product product name product price product price / product productprice product quantity product quantity / product productquantity defaults to 1 if not set product attributes (multiple products) when properties products contains two or more products, they are sent as a products array each element has the same fields as the single product mapping above empty product objects (no fields resolved) are filtered out csp requirements if your site uses a content security policy, allow the following domains directive domain connect src https //tags srv stackadapt com , https //qvdt3feo com script src https //tags srv stackadapt com style src https //tags srv stackadapt com