Mintegral Pixel: Standard Events and Objects Guide

Mintegral Pixel: Required Events

These events are mandatory for accurate event and conversion attribution and campaign optimization.

Page View (page_view)

Description:

Triggered when a user visits any critical or product-related page.

Parameters:

Example:

mintegralPixel("track", {
  "type": "page_view",
  "data": {
    "url": "https://shop.example.com/product/123",
    "title": "Product Details - Blue Running Shoes"
  }
});

Product View (product_view)

Description:

Triggered when a user views the details of a specific product.

Parameters:

Example:

mintegralPixel("track", {
  "type": "product_view",
  "data": {
    "currency": "USD",
    "value": 89.99,
    "items": [
      {
        "item_variant_id": "sku123-blue-42",
        "item_id": "sku123",
        "item_name": "Air Sneakers",
        "price": 89.99,
        "quantity": 1,
        "image_url": "https://cdn.example.com/images/sku123.jpg"
      }
    ]
  }
});

⚠️ Note: For items like "item_variant_id", "item_id", "item_name", please insert your own internal product naming, SKU, or ID number in the field after each item.

 

For instance, our example above uses "item_name": "Air Sneakers". For your e-commerce store, the name of the item would be unique to what you're selling as well as the ID number and SKU of the items you're listing.

Add to Cart (product_add_to_cart)

Description:

Triggered when a user adds one or more products to the shopping cart.

Parameters:

Example:

mintegralPixel("track", {
  "type": "product_add_to_cart",
  "data": {
    "currency": "USD",
    "value": 179.98,
    "items": [
      {
        "item_variant_id": "sku123-blue-42",
        "item_id": "sku123",
        "item_name": "Air Sneakers",
        "price": 89.99,
        "quantity": 2,
        "image_url": "https://cdn.example.com/images/sku123.jpg"
      }
    ]
  }
});

Begin Checkout (begin_checkout)

Description:

Triggered when a user starts the checkout process.

Parameters:

Example:

mintegralPixel("track", {
  "type": "begin_checkout",
  "data": {
    "currency": "USD",
    "value": 179.98,
    "items": [
      {
        "item_variant_id": "sku123-blue-42",
        "item_id": "sku123",
        "item_name": "Air Sneakers",
        "price": 89.99,
        "quantity": 2,
        "image_url": "https://cdn.example.com/images/sku123.jpg"
      }
    ]
  }
});

Purchase (purchase)

Description:

Triggered when a user completes a transaction and payment is successful.

Parameters:

Example:

mintegralPixel("track", {
  "type": "purchase",
  "data": {
    "currency": "USD",
    "value": 179.98,
    "items": [
      {
        "item_variant_id": "sku123-blue-42",
        "item_id": "sku123",
        "item_name": "Air Sneakers",
        "price": 89.99,
        "quantity": 2,
        "image_url": "https://cdn.example.com/images/sku123.jpg"
      }
    ],
    "transaction_id": "ORDER10001",
    "shipping": 5.0,
    "tax": 0.0
  }
});

Mintegral Pixel: Recommended Events

These events are optional but highly recommended for enhancing event granularity and enabling full-funnel optimization.

Add Payment Info (add_payment_info)

Description:

Triggered when a user provides or updates their payment information.

Parameters:

Search (search)

Description:

Triggered when a user performs a product search.

Parameters:

Cart View (cart_view)

Description:

Triggered when a user opens or views the shopping cart.

Parameters:

Remove from Cart (product_remove_from_cart)

Description:

Triggered when a user removes one or more products from the shopping cart.

Parameters:

Product Item Object (`items[]`)

The `items[]` array is required in most e-commerce events. Each object in the array should represent a product with the following properties: 

Supported Payment Types

Below are the standardized payment type values to be used for the payment_type parameter in tracking events. Consistent use of these values helps ensure accurate reporting and analysis.

Usage Notes

• Always use the exact key strings listed above when passing the payment_type parameter.
• If the payment method does not match any listed type, use other.
• The payment_type parameter helps in campaign attribution and user payment behavior analysis.