Supported Destinations

SweetCode Cloud forwards tracking events to nine destinations — seven major ad platforms plus Google Analytics 4 and Mixpanel. All destinations are available on every plan, including the free tier. Configuration is automatically synced from Pixel Manager for WooCommerce — you never need to manually enter credentials in the SweetCode Cloud dashboard.

How Destination Sync Works

1. Configure your ad platform destinations in Pixel Manager for WooCommerce (API tokens, pixel IDs, etc.)
2. Paste your SweetCode Cloud Sync Token into the Pixel Manager settings
3. Pixel Manager pushes the destination configuration to SweetCode Cloud automatically
4. Credentials are encrypted with AES-GCM before storage — they’re never visible in the dashboard, only masked previews (e.g. sk-****...7f3a)

When you update credentials or add/remove a destination in Pixel Manager, changes sync automatically. You can also trigger a manual resync from the domain detail page.

Event Mapping

Each SSP event type is mapped to the corresponding platform-specific event name:

SSP Event	Meta (Facebook)	TikTok	Pinterest	Snapchat	Reddit	OpenAI	Nextdoor	Google GA4	Mixpanel
PageVisit	PageView	Pageview	page_visit	PAGE_VIEW	PageVisit	page_viewed	page_view	page_view	Page Viewed
ViewContent	ViewContent	ViewContent	view_category	VIEW_CONTENT	ViewContent	contents_viewed	view_content	view_item	Product Viewed
Search	Search	Search	search	SEARCH	Search	custom	search	search	Products Searched
AddToCart	AddToCart	AddToCart	add_to_cart	ADD_CART	AddToCart	items_added	add_to_cart	add_to_cart	Product Added to Cart
AddToWishlist	AddToWishlist	AddToWishlist	add_to_wishlist	ADD_TO_WISHLIST	AddToWishlist	custom	add_to_wishlist	add_to_wishlist	Product Added to Wishlist
Purchase	Purchase	CompletePayment	checkout	PURCHASE	Purchase	order_created	purchase	purchase	Order Completed
Lead	Lead	SubmitForm	lead	SIGN_UP	Lead	lead_created	lead	generate_lead	Lead Submitted
SignUp	CompleteRegistration	CompleteRegistration	signup	SIGN_UP	SignUp	registration_completed	sign_up	sign_up	Signed Up
Custom	CustomEvent	CustomEvent	custom	CUSTOM_EVENT_1	Custom	custom	custom_conversion_1	custom_event

---

Meta Conversions API

API: Facebook Graph API v21.0

SweetCode Cloud sends events to Meta’s Conversions API, which is used by Facebook Ads, Instagram Ads, and the broader Meta advertising ecosystem. Server-side events sent through the Conversions API are matched with browser-side pixel events for improved attribution and deduplication.

Required Configuration (in Pixel Manager)

| Field | Where to Find It | | --------------- | --------------------- | ---------------------------------------------------------- | | Access Token | Meta Events Manager → Settings → Generate Access Token | | Pixel ID | Meta Events Manager → Data Sources → Your Pixel → Pixel ID |

Optional

• Test Event Code — Used to send events to the Meta Test Events tool for debugging without affecting production data. Found in Events Manager → Test Events.

How It Works

Each event is sent as a POST request to https://graph.facebook.com/v21.0/{pixelId}/events with the access token as a query parameter. User data (email, IP, user agent, click IDs) is included for advanced matching.

---

TikTok Events API

API: TikTok Business API v1.3

SweetCode Cloud forwards events to TikTok’s Events API for server-side ad measurement and optimization. Like Meta, TikTok uses these events alongside browser-side pixel data for improved attribution.

Required Configuration (in Pixel Manager)

| Field | Where to Find It | | --------------- | --------------------- | ------------------------------------------------------- | | Access Token | TikTok Ads Manager → Assets → Events → Manage → Settings → Generate Access Token | | Pixel ID | TikTok Ads Manager → Assets → Events → Your Pixel ID |

Optional

• Test Event Code — Used to send events in test mode for debugging.

How It Works

Events are sent as a POST request to https://business-api.tiktok.com/open_api/v1.3/event/track/ with the access token in the Access-Token header.

---

Pinterest Conversions API

API: Pinterest API v5

SweetCode Cloud sends conversion events to Pinterest’s API for ad measurement and optimization. Pinterest uses ad account IDs rather than pixel IDs for server-side event delivery.

Required Configuration (in Pixel Manager)

| Field | Where to Find It | | --------------- | --------------------- | -------------------------------------------------------- | | Access Token | Pinterest Business → Apps → Generate Token | | Ad Account ID | Pinterest Ads Manager → Your ad account ID |

Optional

• Test Event Code — Used to send events in test mode for debugging.

How It Works

Events are sent as a POST request to https://api.pinterest.com/v5/ad_accounts/{adAccountId}/events with the access token in the Authorization header.

Note

Pinterest uses adAccountId instead of a pixel ID. Make sure you’re entering the correct ad account ID in Pixel Manager, not a tag or pixel ID.

---

Snapchat Conversions API

API: Snapchat Conversions API v3

SweetCode Cloud forwards events to Snapchat’s Conversions API for ad attribution and optimization.

Required Configuration (in Pixel Manager)

| Field | Where to Find It | | --------------- | --------------------- | -------------------------------------------------------- | | Access Token | Snapchat Ads Manager → Business Settings → Generate Token | | Pixel ID | Snapchat Ads Manager → Events Manager → Your Pixel ID |

Optional

• Test Event Code — Used to send events in test mode for debugging.

How It Works

Events are sent as a POST request to https://tr.snapchat.com/v3/{pixelId}/events with the access token in the Authorization header.

---

Reddit Conversions API

API: Reddit Conversions API v3

SweetCode Cloud sends conversion events to Reddit’s Ads API for campaign measurement and optimization.

Required Configuration (in Pixel Manager)

| Field | Where to Find It | | --------------- | --------------------- | -------------------------------------------------------- | | Access Token | Reddit Ads → Pixel → Conversions API → Generate Token | | Pixel ID | Reddit Ads → Pixel → Your Pixel ID |

How It Works

Events are sent as a POST request to https://ads-api.reddit.com/api/v3/pixels/{pixelId}/conversion_events with the access token in the Authorization header.

Note

Reddit does not support a test event code. To verify events are being received, use Reddit’s Conversions API event verification tool in the Reddit Ads dashboard.

---

OpenAI Conversions API

API: OpenAI Conversions API

SweetCode Cloud sends conversion events to OpenAI’s Ads measurement API for campaign measurement and optimization.

Required Configuration (in Pixel Manager)

| Field | Where to Find It | | --------------- | --------------------- | -------------------------------------------------------- | | Access Token | OpenAI Ads Manager → Conversions tab → API key | | Pixel ID | OpenAI Ads Manager → Conversions tab → Your pixel ID |

How It Works

Events are sent as a POST request to https://bzr.openai.com/v1/events?pid={pixelId} with the access token in the Authorization header. Monetary values are sent as integer ISO 4217 minor units (e.g. 12999 for $129.99).

Note

OpenAI does not use a test event code. Credential health checks are sent with validate_only: true, which validates the event against your pixel and API key without recording any data.

---

Nextdoor Conversion API

API: Nextdoor Conversion API

SweetCode Cloud sends conversion events to Nextdoor’s Conversion API for campaign measurement and optimization.

Required Configuration (in Pixel Manager)

Field	Where to Find It
Access Token	Nextdoor Ads Manager → Ads API settings → Generate token
Pixel ID	Nextdoor Ads Manager → Assets → Pixels → Your pixel ID (a UUID)
Test Event Code	Optional. Any string; flags events as test events in Nextdoor

How It Works

Events are sent as a POST request to https://ads.nextdoor.com/v2/api/conversions/track with the access token in the Authorization header. Nextdoor accepts one event per request. The pixel ID is sent as data_source_id, and the event timestamp is stamped server-side as event_time_epoch (Unix seconds).

Pixel Manager sends the same event_id to the Nextdoor browser pixel and the Conversion API, so Nextdoor deduplicates the two channels automatically. The Nextdoor click ID (ndclid) is forwarded as customer.click_id for attribution.

Note

When a test event code is configured in Pixel Manager, every event is sent with test_event set and Nextdoor treats it as test traffic. Remove it after testing. Credential health checks always use a flagged test event so they never pollute real conversion data.

---

Google Analytics 4 (Measurement Protocol)

API: GA4 Measurement Protocol

SweetCode Cloud forwards events to Google Analytics 4 via the Measurement Protocol. Unlike the ad platforms above, GA4 is an analytics destination — events appear in your GA4 property’s reports rather than feeding an ad network’s conversion optimization.

Required Configuration (in Pixel Manager)

| Field | Where to Find It | | --------------- | --------------------- | --------------------------------------------------------------------------------- | | Measurement ID | GA4 Admin → Data Streams → Your web stream → Measurement ID (looks like G-XXXXXXX) | | API Secret | GA4 Admin → Data Streams → Your web stream → Measurement Protocol API secrets → Create |

How It Works

Events are sent as a POST request to https://www.google-analytics.com/mp/collect with the Measurement ID and API secret as query parameters.

Note

The Measurement Protocol does not validate credentials server-side — events sent with a wrong API secret or Measurement ID are accepted with HTTP 2xx and silently discarded by Google. If events show success in SweetCode Cloud but don’t appear in GA4, double-check both values in Pixel Manager and verify with the GA4 Realtime report or DebugView.

---

Mixpanel Ingestion API

API: Mixpanel Ingestion API (/track)

SweetCode Cloud forwards purchases to Mixpanel via the Ingestion API. Like GA4, Mixpanel is an analytics destination: events land in your Mixpanel project’s reports rather than feeding an ad network’s conversion optimization.

Required Configuration (in Pixel Manager)

Field	Where to Find It
Project Token	Mixpanel → Settings → Project Settings → Project Token (32 hexadecimal characters)
Data Residency	The region your Mixpanel project lives in: US (default), EU or India

How It Works

Events are sent as a POST request to https://api.mixpanel.com/track?verbose=1, with the project token inside the event properties. Mixpanel authenticates /track with that token alone, so there is no second credential to configure.

The data residency setting decides which regional host receives the events: api.mixpanel.com for US projects, api-eu.mixpanel.com for EU projects and api-in.mixpanel.com for Indian projects. This matters more than it looks: Mixpanel does not ingest events that reach the wrong region, and it does not report an error either. EU projects have a Mixpanel URL starting with eu.mixpanel.com, Indian projects with in.mixpanel.com.

Event timestamps are stamped server-side as time in Unix milliseconds. Each purchase carries a deterministic $insert_id derived from the WooCommerce order ID, so a retried delivery can never be counted twice. Pixel Manager captures the Mixpanel distinct_id from the browser during checkout and sends it with the purchase, which keeps the server-side order on the same Mixpanel user as the browser events — without it, purchases would land on a separate anonymous user and every funnel ending in a purchase would break.

The customer’s IP address is forwarded as the ip event property, which Mixpanel uses for geolocation and then drops. Without it, Mixpanel would geolocate every proxied event to the Cloudflare edge instead of the customer.

Note

Mixpanel has no validation endpoint, so credential health checks post a SSP Health Check event with a fixed $insert_id and geolocation disabled. Repeated checks on the same day deduplicate instead of accumulating, and the event name keeps them out of every e-commerce report.

---

Verifying Destination Events

After connecting your destinations through Pixel Manager and SweetCode Cloud, verify that events are being received by each platform:

1. SweetCode Cloud Dashboard — Go to the Events page and check that events show a success outcome for each destination
2. Meta Events Manager — Check the “Server Events” tab for incoming events
3. TikTok Events Manager — View the event activity in your pixel’s dashboard
4. Pinterest Conversions — Check the conversion events in your ad account
5. Snapchat Events Manager — View events under your pixel
6. Reddit Ads Dashboard — Check the conversions tab in your pixel settings
7. OpenAI Ads Manager — Check the event activity in the Conversions tab
8. Nextdoor Ads Manager — Check the event activity under Assets → Pixels
9. Google Analytics 4 — Open the Realtime report (or DebugView for test traffic) in your GA4 property
10. Mixpanel — Open Events in your Mixpanel project and filter for Order Completed

If events show a failed outcome in SweetCode Cloud, click on the event to see the error message from the destination API. Common issues include expired access tokens and incorrect pixel/account IDs — see the Troubleshooting guide for fixes.