Signals Docs
Reference

Event property conventions

Canonical event names, value extraction, and destination mappings.

Conversion event names

These names are recognized as conversions and fan out to ad platforms:

PixelFox eventFacebookTikTokGA4
product_viewedViewContentViewContentview_item
product_added_to_cart (alias product_added)AddToCartAddToCartadd_to_cart
checkout_started (aliases checkout, initiate_checkout)InitiateCheckoutInitiateCheckoutbegin_checkout
order_placed (aliases order, purchase)PurchaseCompletePaymentpurchase
product_searched (alias search)SearchSearchsearch
leadLeadSubmitFormgenerate_lead
complete_registrationCompleteRegistrationCompleteRegistrationsign_up

Any other event name is still ingested, counted in your dashboard rollups, and matched by definitions - it just doesn't reach the ad platforms.

Monetary value

The conversion value is extracted from properties in this precedence order:

total → value → subtotal → cart_total → price → product_price

Numbers and numeric strings both work. currency is uppercased and truncated to a 3-letter code.

Commerce properties

PropertyUsed for
product_id / variant_idcontent_ids on Facebook/TikTok
order_idorder_id / transaction_id
email, phonehashed match data + identity stitching
search_querysearch events (auto-filled from form fields named q/query/search)

Envelope properties (added automatically)

Browser: $current_url, $pathname, $host, $screen_width/height, $viewport_width/height, $user_agent, $language, plus persisted super properties - UTM parameters, click ids (gclid, fbclid, msclkid, ttclid, li_fat_id), initial_referrer, and $ga_client_id when a _ga cookie exists.

Worker (at ingest): site_id, $ip, $geoip_country_code, $geoip_city_name, $geoip_subdivision_1_name, $geoip_time_zone, $geoip_latitude/longitude, and external_id once the visitor is stitched.

On this page