Standard Events

Once Meta Pixel + CAPI is configured, the following events fire automatically. No extra code required.

ViewContent

• Trigger: visitor opens a product detail page
• Channel: Pixel JS (browser)
• Payload:

  {
    content_ids: ["product-id"],
    content_name: "Product Name",
    content_type: "product",
    value: 150000,
    currency: "IDR"
  }

AddToCart

• Trigger: click "Add to Cart" on product detail / quick view
• Channel: Pixel JS (browser)
• Payload: same as ViewContent + contents: [{id, quantity}]

InitiateCheckout

• Trigger: visitor enters /checkout
• Channel: Pixel JS (browser)
• Payload:

  {
    content_ids: ["id-1", "id-2"],
    num_items: 3,
    value: 450000,
    currency: "IDR"
  }

Purchase 🌟 (most important)

• Trigger: order status changes to paid via Midtrans webhook
• Channel: Pixel JS + CAPI (dedup via event_id = order.id)
• CAPI payload:

  {
    event_name: "Purchase",
    event_id: "order-uuid",     // dedup key
    user_data: {
      em: [sha256(email)],
      ph: [sha256(phone)],
      fn: [sha256(firstName)],
      country: [sha256("id")]
    },
    custom_data: {
      value: 750000,
      currency: "IDR",
      content_ids: [...],
      contents: [{id, quantity, item_price}],
      num_items: 4
    }
  }

• Browser Pixel: fires when buyer is redirected to /order/[id]/success

Subscribe

• Trigger: membership tier subscription becomes active (paid via Midtrans MBR-prefix order)
• Channel: Pixel JS + CAPI
• Payload: value = tier price, predicted_ltv (optional), subscription_id

PII Hashing Note

All identity data (email, phone, name, country) is hashed SHA-256 before being sent to CAPI — Meta only needs the hash to match against Facebook accounts, never sees raw values.