Events Reference

Converlay automatically tracks 10 storefront events through Shopify's Web Pixels API. No manual event setup is required — all events fire automatically when a visitor interacts with your store.

Auto-tracked events

Event	Trigger	Key data
`page_view`	Every page load	URL, referrer, UTMs
`view_item`	Product page viewed	Product ID, name, price, variant
`view_item_list`	Collection / search results viewed	Item list ID, items
`add_to_cart`	Item added to cart	Product ID, quantity, price
`remove_from_cart`	Item removed from cart	Product ID, quantity
`search`	Search performed	Search term
`begin_checkout`	Checkout started	Cart value, items
`add_payment_info`	Payment info entered	Payment method
`add_shipping_info`	Shipping info entered	Shipping method
`purchase`	Order completed	Transaction ID, value, items, user data

Event payload structure

Every event sent to the Converlay collection endpoint follows this structure. Here's an example purchase event:

purchase event payload

{
  "event_id": "evt_abc123",
  "event_name": "purchase",
  "shop_domain": "my-store.myshopify.com",
  "page_url": "https://my-store.com/thank-you",
  "client_id": "clid_...",
  "session_id": "sid_...",
  "fbp": "fb.1.1700000000000.1234567890",
  "gclid": "CjwKCAiA...",
  "consent_data": {
    "analytics": true,
    "marketing": true,
    "ad_user_data": true,
    "ad_personalization": true
  },
  "ecommerce": {
    "transaction_id": "5678",
    "value": 129.99,
    "currency": "USD",
    "items": [
      {
        "item_id": "gid://shopify/ProductVariant/123",
        "item_name": "Classic Tee",
        "price": 29.99,
        "quantity": 2
      }
    ]
  },
  "user_data": {
    "email": "sha256:abc...",
    "phone": "sha256:def..."
  }
}

PII handling

User data (email, phone, address) is hashed with SHA-256 on the server before forwarding to ad platforms. Raw PII is never stored or shared. Country-specific normalization is applied before hashing.

Event enrichment

Before forwarding, each event is enriched with:

Click ID stitching — gclid, fbclid, ttclid are persisted across sessions
Facebook parameters — _fbp and _fbc are generated for Meta CAPI matching
Session context — 30-minute rolling session with persistent client ID
Consent signals — Google Consent Mode v2 signals mapped from Shopify's Customer Privacy API
Event deduplication — unique event_id prevents double-counting across pixel and webhook sources

Previous← Connect Destinations NextConsent & Privacy →