Use camelCase when sending properties — the platform automatically converts to the format each destination requires.
Full Event Structure
A complete tracking event contains the event name, timestamp, user data, custom data, and automatically captured context.Core Properties
These properties work with most events.value
Monetary value of the event. Required for purchase, lead, subscribe.
currency
ISO 4217 currency code. Required with value.
transactionId
Unique order identifier. Required for purchase/refund.
orderName
Human-readable order number shown to customers.
Quick Reference
orderId and transactionId are interchangeable — use whichever fits your system. If both are provided, transactionId takes precedence.Customer Properties
Properties for identifying customers. Used for identity resolution and destination matching.Primary identifier for cross-device tracking.
phone
E.164 format for improved matching.
firstName / lastName
Customer name for identity resolution.
Address Fields
Shipping and billing address properties.
Quick Reference
Checkout & Pricing Properties
Additional properties for checkout and purchase events.subtotalPrice
Subtotal before tax/shipping.
tax
Tax amount applied.
shipping
Shipping cost.
discount
Total discount amount.
coupon
Promo code used.
paymentType
Payment method used.
shippingTier
Shipping speed selected.
Quick Reference
Content Properties
Properties for content-related events like search and page views.searchTerm
Search query entered by the user.
content_ids
Array of product IDs from search results.
Quick Reference
Promotional Properties
Properties for tracking promotions, campaigns, and affiliate activity.promotionId
Promotion/campaign identifier.
promotionName
Promotion display name.
creativeName
Creative/ad variant name.
creativeSlot
Placement position on page.
locationId
Store/affiliate/location ID.
Quick Reference
Detailed Property References
Items Array
Product details for e-commerce events — id, name, price, quantity, brand, category, variant.
Address Properties
Shipping and billing address fields — address1, city, province, country, zip.
SaaS Properties
B2B/SaaS properties — account, subscription, trial, payment, and churn tracking.
Auto-Captured Fields
Click IDs, UTMs, and context fields captured automatically by the pixel.
Naming Conventions
Input vs Output Format
Send properties in camelCase — the platform converts to each destination’s required format automatically.Legacy Snake Case Properties
Some properties use snake_case for compatibility with Meta and GA4 conventions:The platform accepts both formats and normalizes automatically. You can use either
contentIds or content_ids — both work.Event Names
Event names use snake_case (e.g.,add_to_cart, initiate_checkout, view_content).