Kenshoo Pixel (Cloud Destinations)

  • Cloud
  • Destinations

MetaRouter makes it easy to send your data to Kenshoo Conversion Pixel, which was recently enhanced with Kenshoo Infinity Tag. If you follow the steps below, your data will be routed through our platform and pushed to Kenshoo Pixel in the appropriate format.

What is Kenshoo Infinity Tag and how does it work?

Kenshoo, a global leader in agile marketing, recently released an upgraded conversion pixel that enables marketers to "better understand the role their digital campaigns played in customer transactions." The platform not only drives revenue but also improves efficiency by capturing detailed conversion data in a single platform.

Infinity Tag enhances campaign performance by moving beyond currently accepted KPIs, like total revenue, to more granular conversion and attribution insights that inform and improve organization strategy. The platform also allows retailers to share campaign details with manufacturers, which empower retailers to manage and boost co-op advertising and make a case for co-op dollars from the brand.

Learn more about Kenshoo Infinity Tag

Getting Started with Kenshoo and MetaRouter

Kenshoo Side

All you'll need from Kenshoo is your Account Id. Once you have this code, copy it to your clipboard and head over to your MetaRouter dashboard

MetaRouter Side

Once on our app, go ahead and add Kenshoo Infinity Pixel as a destination for your preferred source. Give the connection a unique name and paste both your Account Id and Server Id where prompted.

Now, just click Create Destination to activate your pipeline and begin pushing your clickstream data into Kenshoo.

© 2020 MetaRouter

Disclaimer: MetaRouter Cloud leverages code from several of Segment's fabulous library of open-source tools, including their source SDKs, destinations, and core Analytics.js library. As some of the core configurations outlined in our docs are largely identical to Segment's, we often re-purpose, and in some cases copy, directly from Segment's docs. In the cases where we have forked Segment's tools, we acknowledge and attribute all credit to Segment for their creation and subsequent documentation.