Set Up Conversion Pixels
The Conversion Tracking page in your Phoenix Dashboard allows you to connect marketing pixels from platforms such as Meta, TikTok, Snap, AppLovin, Google Tag Manager, Newsbreak, Triple Whale, and more. Once added, these pixels help track visitor behavior and conversions across your store, ensuring accurate reporting and optimized ad performance.
Follow these steps to add and configure a conversion pixel:
-
Log in to your Phoenix Dashboard.
-
In the left navigation panel, go to Stores.
-
Click your Store URL to open its configuration.
-
Select the Conversion Tracking tab at the top of the page. You will see a list of all existing tracking configurations.
-
Click + Add Tracking.
-
Choose an Ad Platform. Each ad platform requires a different setup configuration:
| Ad Platform | Required Fields | Details (Expanded) |
|---|---|---|
| Meta | • Track Configuration• Pixel ID | Supports Pixel (browser-based) and Conversions API (CAPI) (server-side). • CAPI provides higher accuracy by reducing ad blockers and data loss. • Access Token is required only if CAPI is selected. • Pixel ID identifies your Meta Pixel for event tracking. |
| TikTok | • Track Configuration• Pixel ID | Uses TikTok Pixel for event tracking. • Typically set through TikTok Events Manager. • Track Configuration includes selecting pixel-type tracking. • No API token required. |
| Snap | • Track Configuration• Pixel ID | Uses Snap Pixel for tracking page views, conversions, and attribution. • Pixel ID must match the one generated inside Snap Ads Manager. • Only pixel-based tracking is supported. |
| Applovin | • Track Configuration• Pixel ID | Supports pixel-based conversion tracking for mobile-focused campaigns. • Ensure the Pixel ID matches the one from AppLovin dashboard. • No additional API/token fields required. |
| Google Tag Manager | • Track Configuration• Pixel ID | Pixel ID corresponds to your GTM Container ID (e.g., GTM-XXXXXXX). • GTM acts as a container for all your tags, triggers, and variables. • No tracking label is needed because GTM manages event routing internally. |
| Google Tag (No GTM) | • Track Configuration• Pixel ID• Tracking Label | Used when adding a Google Tag (gtag.js) directly, without GTM. • Pixel ID is your Google Tag ID (e.g., G-XXXXX). • Tracking Label is optional and used to classify or group event data. • Useful for setups that bypass GTM but still need event-level control. |
| Newsbreak | • Track Configuration• Pixel ID | Requires pixel-based tracking for campaign measurement. • Pixel ID links your events to the correct Newsbreak advertiser account. • Only browser-based tracking is supported. |
| Retention | • Track Configuration• Pixel ID | Requires a Pixel ID to sync customer events. • Used for customer tracking and audience enrichment. • Only pixel-based tracking is available here. |
| Triple Whale | • Track Configuration | Does not require a pixel, because Triple Whale uses its own server-side tracking and integrations. • Track Configuration enables the integration but no identifier is required. |
| • Track Configuration• Pixel ID | Uses Reddit Pixel for conversion tracking. • Pixel ID links events to your Reddit Ads Manager. • Supports page view and conversion tracking via pixel. |
For the most accurate and reliable tracking, always select Conversions API as the Track Configuration for Meta. This setup requires you to enter both your Pixel ID and your Token ID (the Conversions API Access Token from your Meta Ads Manager).
For most other platforms like Snap or Google Tag Manager, you will typically select Pixel and only need to enter the Pixel ID.
-
Click Add to save the configuration. The new tracking configuration will appear in the list.
With your conversion pixels correctly installed, you can accurately measure ad effectiveness and optimize your campaigns for better results
Related Guides
Continue setting up your store with these articles: