Settings Reference

This page lists every setting of the Pixel Manager for WooCommerce under the exact name shown in the plugin's settings, with a short explanation and a link to the detailed documentation. Settings marked Pro require a pro plan.

Tracking Pixels

Google (Ads & GA4) → Google Ads

Documentation.

• Conversion ID — Your Google Ads conversion ID (starts with AW-). In Google Ads go to Goals → Conversions → your conversion action → Tag setup. Required to track conversions. Documentation.
• Conversion Label — The conversion label for your Purchase action, shown beside the conversion ID in the same Google Ads tag setup. It pairs with the conversion ID to attribute purchases. Documentation.

Advanced settings:

• Merchant Center ID — Your Google Merchant Center ID. Enables Conversion Cart Data (cart contents sent with conversions) and, with a business vertical, dynamic remarketing. Documentation.
• Business Vertical (Pro) — Your store's category for Google dynamic remarketing. Options: “Retail”, “Education”, “Hotels and Rentals”, “Jobs”, “Local Deals”, “Real Estate”, “Travel”, “Custom”. Documentation.
• Phone Conversion Number (Pro) — The phone number shown on your site, for Google call-conversion tracking. Use the same format displayed to visitors. Documentation.
• Phone Conversion Label (Pro) — The conversion label for your Google Ads call/phone conversion action. Documentation.
• Conversion Adjustments: Conversion Name (Pro) — The exact Google Ads conversion action name used for conversion adjustments (e.g. correcting or retracting values after refunds). Documentation.
• Conversion Adjustments: Feed URL (Pro, read-only) — Read-only. Copy this URL into Google Ads → Tools → Conversions → conversion adjustments as the data source, so the Pixel Manager can supply adjustment data. Active once the conversion name above is set. Documentation.

Google (Ads & GA4) → Google Analytics 4

Documentation.

• Measurement ID — Your GA4 Measurement ID (starts with G-). In Google Analytics go to Admin → Data Streams → your web stream. Required to send data to GA4. Documentation.

Advanced settings:

• API Secret (for Measurement Protocol) (Pro) — Measurement Protocol API secret for server-side GA4 events. Create it in the same Data Stream → Measurement Protocol API secrets. Documentation.
• Data API Property ID (Pro) — Your numeric GA4 property ID (Admin → Property settings), used by the Data API to read attribution data back into your orders. Documentation.
• Data API Credentials (Pro)
• Page Load Time Tracking (Pro) — Measures page load time and sends it to GA4 as an event — useful for spotting slow pages that hurt conversions. Documentation.
• Enhanced Link Attribution — Lets GA4 distinguish multiple links pointing to the same URL in in-page analytics, for more accurate link reports. Documentation.

Google (Ads & GA4) → Shared Google settings

Used by both Google Ads and Google Analytics. Documentation.

• Enhanced Conversions (Pro) — Sends hashed first-party data (e.g. email) with conversions to improve match rates and recover conversions lost to cookie limits. Requires accepting Google's enhanced-conversions terms. Documentation.
• User ID Feature (Pro) — Sends a logged-in customer's User ID to GA4 so their sessions across devices are stitched into one user. Requires User-ID reporting enabled in GA4. Documentation.
• Google Tag ID (read-only) — The shared Google tag (gtag.js) ID used across Google Ads and Analytics. Read-only — derived automatically from your Google Ads Conversion ID (or your GA4 Measurement ID when no Ads ID is set). Documentation.
• Tag Gateway measurement path (beta) — First-party path for the Google Tag Gateway, which serves Google's tags from your own domain to improve measurement resilience against ad blockers. Advanced — leave blank unless you've set up the gateway. Format: a leading slash + letters/numbers, e.g. /metrics. Documentation.

Meta → Meta (Facebook)

Documentation.

• Pixel ID — Your Meta (Facebook) Pixel ID. In Meta Events Manager go to Data Sources → your pixel → Settings. Required for Meta tracking. Documentation.

Advanced settings:

• Conversions API Token (Pro) — Conversions API access token for sending events to Meta server-side — more reliable against ad blockers and iOS limits. Generate it in Events Manager → your pixel → Settings → Conversions API. Documentation.
• CAPI Test Event Code (Pro) — Temporary code from Events Manager → Test Events to confirm your server-side events arrive. Remove it once verified. Documentation.
• Advanced Matching (Pro) — Sends extra hashed customer identifiers with events to improve match quality and attribution. Data is hashed before it leaves your server. Documentation.
• Domain Verification ID (Pro, beta) — The domain-verification value from Meta Business Manager, output as a meta tag to verify ownership of your domain. Documentation.

TikTok

(Pro) Documentation.

• Pixel ID (Pro) — Your TikTok Pixel ID. In TikTok Ads Manager go to Assets → Events → Web Events → your pixel. Required for TikTok tracking. Documentation.

Advanced settings:

• Events API Token (Pro) — TikTok Events API token for server-side events. Generate it in the same web-events pixel under Events API. Documentation.
• EAPI Test Event Code (Pro) — Test code from TikTok Events Manager to verify your server-side events. Remove it after testing. Documentation.
• Advanced Matching (Pro) — Sends extra hashed customer identifiers to improve TikTok event matching and attribution. Documentation.

Microsoft (Advertising & Clarity) → Microsoft Advertising

(Pro) Documentation.

• UET Tag ID (Pro) — Your Microsoft Advertising UET tag ID. In Microsoft Advertising go to Tools → UET tag. Required for conversion tracking and remarketing. Documentation.

Advanced settings:

• Enhanced Conversions (Pro) — Sends hashed first-party customer data with conversions to improve match rates in Microsoft Advertising. Documentation.

Microsoft (Advertising & Clarity) → Microsoft Clarity

(Pro, beta) Documentation.

• Project ID (Pro) — Your Microsoft Clarity project ID, from Clarity → Settings → Setup (it's the value in the tracking URL, e.g. clarity.ms/tag/q9zk3x7p2w). Enables Clarity heatmaps and session recordings. Documentation.

LinkedIn

(Pro) Documentation.

• Partner ID (Pro) — Your LinkedIn Insight Tag partner ID. In Campaign Manager go to Account Assets → Insight Tag. Required for LinkedIn tracking. Documentation.

Advanced settings:

• View Content Conversion ID (Pro) — The LinkedIn conversion ID for the View Content event, from Campaign Manager → Conversions. Maps this store event to the matching LinkedIn conversion. Documentation.
• Add to Cart Conversion ID (Pro) — The LinkedIn conversion ID for the Add to Cart event, from Campaign Manager → Conversions. Documentation.
• Purchase Conversion ID (Pro) — The LinkedIn conversion ID for the Purchase event, from Campaign Manager → Conversions. The key one for conversion reporting. Documentation.

Pinterest

(Pro) Documentation.

• Tag ID (Pro) — Your Pinterest Tag ID. In Pinterest Ads go to Conversions → Pinterest tag. Required for Pinterest tracking. Documentation.

Advanced settings:

• Ad Account ID (Pro) — Your Pinterest ad account ID, required to send events via the Conversions API. Documentation.
• Conversions API Token (Pro) — Pinterest Conversions API token for server-side events. Generate it in Pinterest Ads → Conversions → API. Documentation.
• Enhanced Match (Pro) — Sends a hashed email with browser events to improve attribution (Pinterest Enhanced Match). Documentation.
• Advanced Matching (Pro) — Sends additional hashed customer data with Conversions API events to improve matching. Documentation.

Snapchat

(Pro) Documentation.

• Pixel ID (Pro) — Your Snapchat Pixel ID. In Snapchat Ads Manager go to Events Manager → your pixel. Required for Snapchat tracking. Documentation.

Advanced settings:

• Conversions API Token (Pro) — Snapchat Conversions API token for sending events server-side, improving reliability against browser limits. Documentation.
• Advanced Matching (Pro) — Sends extra hashed customer identifiers to improve Snapchat event matching. Documentation.

OpenAI

(Pro, beta) Documentation.

• Pixel ID (Pro) — Your OpenAI pixel ID. Create it in the conversions tab of OpenAI Ads Manager. Required for OpenAI tracking. Documentation.

Advanced settings:

• Conversions API Token (Pro) — OpenAI Conversions API token (API key) for sending events server-side. Documentation.
• Advanced Matching (Pro) — Sends extra hashed customer identifiers to improve OpenAI event matching. Documentation.

X → X (Twitter)

(Pro) Documentation.

• Pixel ID (Pro) — Your X (Twitter) Pixel ID. In X Ads go to Tools → Events Manager. Required for X conversion tracking. Documentation.

Advanced settings:

• View Content Event ID (Pro) — The X event ID for the View Content event, created in X Events Manager. Maps this store event to the matching X conversion. Documentation.
• Search Event ID (Pro) — The X event ID for the Search event, from X Events Manager. Documentation.
• Add to Cart Event ID (Pro) — The X event ID for the Add to Cart event, from X Events Manager. Documentation.
• Add to Wishlist Event ID (Pro) — The X event ID for the Add to Wishlist event, from X Events Manager. Documentation.
• Initiate Checkout Event ID (Pro) — The X event ID for the Initiate Checkout event, from X Events Manager. Documentation.
• Add Payment Info Event ID (Pro) — The X event ID for the Add Payment Info event, from X Events Manager. Documentation.
• Purchase Event ID (Pro) — The X event ID for the Purchase event, from X Events Manager. This is the key one for conversion reporting. Documentation.

Reddit

(Pro) Documentation.

• Advertiser ID (Pro) — Your Reddit Pixel (advertiser) ID. In Reddit Ads go to Events Manager. Required for Reddit tracking. Documentation.

Advanced settings:

• Conversions API Token (Pro) — Reddit Conversions API token for sending events server-side. Documentation.
• CAPI Test Event Code (Pro) — Test code to verify your Reddit server-side events. Remove it after testing. Documentation.
• Advanced Matching (Pro) — Sends extra hashed customer identifiers to improve Reddit event matching. Documentation.

Hotjar

Documentation.

• Site ID — Your Hotjar Site ID, from Hotjar → Sites & Organizations. Enables Hotjar heatmaps and session recordings. Documentation.

Crazy Egg

(Pro) Documentation.

• Account Number (Pro) — Your Crazy Egg account number, found in your Crazy Egg install script/account. Enables Crazy Egg heatmaps and recordings. Documentation.

AdRoll

(Pro, beta) Documentation.

• Advertiser ID (Pro) — Your AdRoll advertiser ID, from AdRoll → Settings → Pixel. Both the advertiser ID and pixel ID are required. Documentation.
• Pixel ID (Pro) — Your AdRoll pixel ID, shown next to the advertiser ID in AdRoll → Settings → Pixel. Documentation.

Outbrain

(Pro, beta) Documentation.

• Advertiser ID (Pro) — Your Outbrain marketer/advertiser ID, from the Outbrain Amplify dashboard. Required for Outbrain conversion tracking. Documentation.

Taboola

(Pro, beta) Documentation.

• Account ID (Pro) — Your Taboola account ID, from Taboola Ads → Tracking → your pixel. Required for Taboola conversion tracking. Documentation.

Contentsquare

(Pro, beta) Documentation.

• Tag ID (Pro) — Your Contentsquare tag ID, from your Contentsquare project settings. Enables Contentsquare experience analytics. Documentation.

AB Tasty

(Pro, beta) Documentation.

• Account ID (Pro) — Your AB Tasty account ID, from your AB Tasty tag/account settings. Enables AB Tasty experimentation. Documentation.

Optimizely

(Pro, beta) Documentation.

• Project ID (Pro) — Your Optimizely project ID, from your Optimizely snippet/project settings. Enables Optimizely experimentation. Documentation.

VWO

(Pro, beta) Documentation.

• Account ID (Pro) — Your VWO account ID, from VWO → Settings → SmartCode. Enables VWO testing and optimization. Documentation.

Triple Whale

(Pro, beta) Documentation.

• Enable Triple Whale (Pro) — Loads the Triple Pixel for visitor journey tracking and attribution. Triple Whale identifies the shop by its domain — it must match the Shop URL in Triple Whale under Settings → Store. No pixel ID is required. Documentation.

Advanced settings:

• Orders API Key (Pro) — Triple Whale API key with the "Orders: Write" scope, from Triple Whale under Data → APIs. When set, order records (including refunds) are synced server-side to the Triple Whale Orders API, which Triple Whale requires for attribution. Documentation.

GroundTruth

(Pro, beta) Documentation.

• GTID (Pro) — Your GroundTruth unique identifier (GTID), provided by your GroundTruth representative. One GTID covers all campaigns of your Ads Manager account. Enables omnichannel engagement and conversion tracking. Documentation.

General

General (General tab)

Settings that apply site-wide, regardless of your store platform.

• Lazy-load the Pixel Manager (Pro) — Defers the tracking library until the visitor's first interaction (click, scroll, key, touch), improving page-speed scores. Cart, checkout and order-received pages always load it immediately so conversions aren't missed. Small risk that very early events go untracked — leave off if in doubt. Documentation.
• Load deprecated functions — Keeps older Pixel Manager function and event names available for backward compatibility. Turn this off to ship less JavaScript — only keep it on if your custom front-end code relies on the old names. Documentation.

WooCommerce shop

Order configuration (General tab)

• Marketing value logic — The conversion value reported to your ad platforms (Google Ads, Meta, …); statistics pixels always receive the full order value. Subtotal is the most conservative (excludes tax, shipping, discounts, fees); Total is what the customer paid; Profit margin reports only margin and needs a cost-of-goods source. Options: “Order subtotal — excl. tax & shipping (default)”, “Order total — incl. tax & shipping”, “Profit margin (Pro)”. Documentation.
• Order duplication prevention — Stops the same order being counted again if the order-received page is reloaded or revisited, keeping conversion counts accurate. Leave on; disable only for testing (it re-enables automatically after 6 hours). Documentation.
• Show tracking info in the order list — Adds a Pixel Manager column to the WooCommerce orders list so you can see at a glance which orders were tracked — handy for spot-checking without opening each order. Documentation.

Product data (General tab)

• Product identifier — Which product ID is sent to the ad platforms for dynamic remarketing. It must match the IDs in your product catalog/feed or remarketing won't match products — pick the option that matches your feed plugin (Post ID is the WooCommerce default). Options: “Post ID (default)”, “SKU”, “Post ID with woocommerce_gpf_ prefix (Google Product Feed)”, “Post ID with gla_ prefix (Google Listings & Ads)”. Documentation.
• Output product variations as separate items — Reports the specific variation the customer viewed or bought (e.g. “Blue T-shirt, M”) for precise remarketing. Turn off only if your product feed contains parent products only, to avoid catalog mismatches. Documentation.

Subscriptions (General tab)

• Subscription value multiplier (Pro) — Multiplies the initial subscription's value to reflect revenue from future renewals, so your ROAS accounts for lifetime value. Set it to your average number of orders per subscription (1.00 = no adjustment). Documentation.

Customer lifetime value (General tab)

• Calculate LTV on orders (Pro, beta) — Calculates each customer's cumulative lifetime value and includes it in the order data — the basis for value-based bidding and high-value-customer audiences. After changing value or order-logic settings, run a recalculation below. Documentation.
• Automatic LTV recalculation (Pro) — Periodically recalculates lifetime value across all customers in the background so the figures stay accurate as orders change. Documentation.

Extra order data output (General tab)

• Output extra order data on order pages (Pro, beta) — Displays the data sent to the marketing pixels on the order details page (and via the order URL in the browser console), to help you debug and understand your tracking. It does not send any extra data to the pixels. Documentation.

Consent

Google Consent Mode v2 (Consent tab)

Control how Google tags behave based on the visitor's consent state.

• Enable Google Consent Mode v2 with standard settings — Google tags honour the visitor's consent. When consent is denied, Google still receives cookieless, anonymised pings it can use for conversion modelling — recovering a large share of otherwise-lost conversions. Documentation.
• Enable Google TCF support (Pro) — IAB Transparency & Consent Framework support for Google tags. Documentation.

Microsoft Ads Consent Mode (Consent tab)

• Enable Microsoft Ads Consent Mode with standard settings (Pro) — Microsoft tags check the visitor's consent (ad_storage granted/denied) before using cookies. There is no fallback modelling — unconsented conversions aren't tracked — so it's especially important in regions with mandatory consent (EU, UK, CH). Documentation.

Explicit consent (Consent tab)

Require explicit opt-in before any tracking fires.

• Enable Explicit Consent Mode — While active, no pixels fire until the visitor gives consent. Documentation.

• Enable Explicit Consent Mode and Restricted consent regions work together: the regions field (shown as Explicit Consent Regions in the documentation) limits Explicit Consent Mode to the selected countries. Documentation.

Server-Side

General (Server-Side tab)

These settings apply to all server-side (server-to-server) events.

• Send PageView events server-to-server (Pro) — Sends PageView events to Meta and Snapchat from your server, making PageView tracking more reliable when browser-side tracking is blocked. Because it runs on every page load it adds server load — enable it when browser PageViews are unreliable and your server can handle the traffic. Documentation.
• Always send server-side events (Pro) — Sends server-side events to the ad platforms even when the browser pixels never loaded (e.g. blocked by a consent banner or ad blocker). Browser tracking is unaffected — the server events fire independently. Use it to recover conversions on platforms that support cookieless / limited-data server integrations. Documentation.

The Server-Side tab also manages the SweetCode Cloud server-side proxy (SSP), which offloads server-side tracking events from your WooCommerce server to an edge network. Documentation.

Support

Logger (Support tab)

Plugin logging for debugging.

• Enable logger — Records the plugin's activity to a log file you can download below — turn it on when diagnosing a tracking issue or before contacting support. Documentation.
• Log level — How much detail to record. Use Error/Warning for normal use; switch to Info or Debug while reproducing a problem. Options: “Error”, “Warning”, “Info”, “Debug”. Documentation.
• Log HTTP requests (Pro) — Also records the outgoing server-side requests to the ad platforms — useful for debugging server-side (CAPI) delivery. Documentation.

Plugin data (Support tab)

Control what happens to the plugin's data when you delete the plugin.

• Delete all plugin data on uninstall — When enabled, deleting the plugin also removes all of its settings, backups, and stored data from the database. Leave off to keep your configuration if you reinstall later. This only takes effect when you delete (not just deactivate) the plugin. Documentation.

Other settings

• Disable tracking for user roles (Pro) (General tab) — Logged-in users in a checked role won't be tracked, keeping your own staff and admin visits out of your analytics and ad data. Documentation.
• Scroll tracker thresholds (Pro) (General tab) — Fires an engagement event in Google Analytics when visitors reach the configured scroll depths, e.g. 25, 50, 75, 100. Documentation.
• Restricted consent regions (Pro) (Consent tab) — Countries where cookie-based tracking only activates after the visitor gives consent; requires Explicit Consent Mode. Documented as Explicit Consent Regions. Documentation.
• Manual LTV recalculation (Pro, beta) (General tab) — Recalculates the customer lifetime value across all customers on demand. Documentation.