StackAdapt Pixel

12 min

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 1\ page fires a stackadapt page view tracking call stackadapt sdk call saq("ts", pixelid) no additional attributes are sent with page events 2\ 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 true 244,244 left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type 3\ 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 true 162,162,164 left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type order level attributes true 162,162,164 left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type product attributes (single product) when properties products contains exactly one product, product fields are sent as flat attributes on the conversion payload true 162,162,164 left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type 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 true 244,244 left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type