In this article

Use the Tracking Pixel activation to fire a pixel to other platforms whenever users enter a cohort

You can send your user data to other platforms quickly and easily using a pixel. There are many applications for this, including

What the Pixel Does

We can use pixels to send audiences to almost any other platform, including all major

For some of these platforms, you can share data directly via one of our existing integrations. Where we don't have an integration with the 'receiver platform' you can set up pixels to achieve the same result.

To send your cohort to another platform, you will need a pixel, created by the 'receiver platform'.
Depending on the 'receiver platform' you will create the pixel by:

The pixel will be a URL link, for example, for Krux:

 https://beacon.krxd.net/event.gif?event_id=123456&event_type=default&Cohort=Cohort_Name/

To deploy the pixel, use the Tracking Pixel activation from within the Permutive dashboard (you may first need to enable this integration).

To set up the pixel, enter the pixel provided by the 'receiver platform' into the Pixel URL box and select a cohort for the pixel to activate to.

This is what the pixel should look like when finished:

Note: We recommend that the pixel URL includes a secure prefix (e.g. HTTPS://) where possible.

Pixels requiring user consent

If you're using our TCF framework integration then you can supply a TCF vendor ID. The Permutive SDK will then handle only allowing the Pixel to fire in environments where consent is required if the user has provided consent for the specified vendor.

When creating a new tracking pixel activation add the TCF vendor ID here:

The SDK will then handle attaching the user's TCF consent string and consent status as query parameters to the URL.

The final URL from the example above would be:

https://dash.permutive.com/tracking-pixel?pixel=test&gdpr=1&gdpr_consent=<user's consent string>