Other Platforms — PixelsCleared Help

Overview

PixelsCleared supports server-side event forwarding to several advertising platforms beyond Meta, GA4, TikTok, and webhooks. This article covers the current status and credential requirements for each.

LinkedIn Conversions API

LinkedIn Conversions API lets you send conversion events from your server to LinkedIn Campaign Manager for campaign optimization and attribution.

Credentials needed:

LinkedIn Pixel ID -- Found in LinkedIn Campaign Manager under Account Assets > Insight Tag > Conversions.
Access Token -- Generated via LinkedIn's OAuth 2.0 flow. Requires a LinkedIn Developer Application with the r_ads and r_ads_reporting permissions.

Status: Available as a built-in destination. Configure it under Gateway > Destinations > Add Destination > LinkedIn Conversions API.

Pinterest Conversions API

Pinterest Conversions API supports server-side event delivery for attribution and audience building.

Credentials needed:

Pinterest Tag ID -- Found in Pinterest Ads Manager under Ads > Conversions > Pinterest Tag. The tag ID is a numeric string.
Access Token -- Generated from the Pinterest Developer portal. Requires an app with ads:read and pins:read scopes.

Status: Available as a built-in destination. Configure it under Gateway > Destinations > Add Destination > Pinterest Conversions API.

Snapchat Conversions API

Snapchat's CAPI (Conversions API) receives server-side events for Snap Pixel attribution and campaign optimization.

Credentials needed:

Snap Pixel ID -- Found in Snapchat Ads Manager under Snap Pixel in the top menu. It is a UUID-format string.
Access Token -- Generated in Snapchat Ads Manager under Snap Pixel > Conversions API > Generate Token.

Status: Available as a built-in destination. Configure it under Gateway > Destinations > Add Destination > Snapchat Conversions API.

Twitter (X) Conversions API

Twitter's Conversions API (formerly X Ads API) supports server-side event forwarding for ad attribution.

Credentials needed:

Twitter Pixel ID -- Found in Twitter Ads under Tools > Events Manager. It is a numeric identifier.
OAuth 2.0 credentials -- A client ID and client secret generated via the Twitter Developer Portal, plus a bearer token for API access.

Status: Available as a built-in destination. The OAuth flow is handled during setup -- you will be prompted to authorize PixelsCleared in a popup window. Configure it under Gateway > Destinations > Add Destination > Twitter Conversions API.

Microsoft Ads (Bing) Offline Conversions

Microsoft Advertising supports server-side conversion tracking through the Offline Conversions API.

Credentials needed:

Universal Event Tracking (UET) Tag ID -- Found in Microsoft Advertising under Tools > UET tags. It is a long numeric string.
Client ID and Client Secret -- Generated from the Microsoft Advertising Developer portal. Requires an app with the https://ads.microsoft.com/ads.manage scope.

Status: Available as a built-in destination. Configure it under Gateway > Destinations > Add Destination > Microsoft Ads.

Requesting a New Platform

If you need server-side forwarding to a platform not listed here:

Check if a Custom Webhook destination can serve your use case -- most platforms accept webhook payloads.
If you need native integration, contact PixelsCleared support with the platform name and your expected event volume. Native destinations are prioritized based on customer demand.

Consent Across All Platforms

Regardless of which platform you connect, PixelsCleared applies the same consent-first rules:

No events are forwarded until the visitor grants consent.
Scrubbing removes PII, sensitive URLs, and flagged content before any destination receives the payload.
Consent state is included in the metadata sent to each platform so they can apply their own data processing restrictions.

You do not need to configure consent handling per destination. It is enforced centrally by the gateway.