---
title: "What Is a Product Event"
description: "Understand how product events track contact interactions and keep product data up to date."
url: https://help.user.com/en/articles/94-what-is-a-product-event
collection: "Products"
updated: 2026-11-18
language: en
alternates: [fr, pl, de, it, es]
---

# What Is a Product Event

Understand how product events track contact interactions and keep product data up to date.

A product event captures a single interaction between a contact and a product - like a view, add to cart, or purchase. You can use product events to better understand buying intent, build more relevant automations, and personalize communication based on real product engagement.

Product events are built for high-volume tracking. They are designed to work efficiently with high volume of product interactions per month, while still keeping product data usable for segmentation and targeting.

## Definition

A **product event** is a dedicated version of event in Positive User that links a contact’s action to a specific product using a unique product ID and a defined event type. Each product event updates the product profile with the most recent attribute values, instead of storing historical values for every single event.

This approach ensures high performance even when you send high number of product-related interactions every month, while still allowing you to segment contacts, trigger automations, and personalize content based on product data.

> **Info:** Product events include several types. Please, remember, that it’s a closed list.

## Types of Product Events

Product events are differentiated by their event type. Each type represents a specific kind of interaction between a contact and a product. The available product event types are:

-   click
    
-   promo click
    
-   view
    
-   detail
    
-   liking
    
-   add to observation
    
-   reservation
    
-   add
    
-   add to cart
    
-   remove
    
-   checkout
    
-   checkout option
    
-   order
    
-   purchase
    
-   return
    
-   refund
    

Each event type helps you analyze a different stage of the product journey, from the first interaction to post-purchase actions.

> **Info:** Product data sent in a product event is not historically stored. It is updated with every new product event occurrence.

## How to Send a Product Event

Product events are set in a similar way to regular events, with a few important differences. To send a product event, you must:

-   Use the keyword _product\_event_.
    
-   Include the required attributes: _product\_id_ and _event\_type_.
    

Passing the product name is optional. If you do not include it and the product does not already exist, the product will be created without a name.

Product events can be sent using the JavaScript SDK or the REST API. You can also trigger them directly from HTML elements, for example, on a click action.

> **Info:** Because attribute values are always overwritten with the latest data, you should create separate products for each variation (for example, different sizes or colors) to ensure accurate tracking.

Product events can be sent:

-   Via the JavaScript SDK
    
-   Via the REST API
    
-   Directly from HTML elements (for example, on click actions)
    

Example (JavaScript SDK / widget API):

```javascript
userengage('product_event', {product_id: 'the_id', event_type: 'add to cart', 'name': 'product name', 'my_attribute': 'value', 'my_attribute_2': 'value_2'})
```

Example for the usage within HTML:

```javascript
<a href="#" onclick="userengage('product_event', {product_id: 'the_id', event_type: 'add to cart', 'name': 'product name', 'my_attribute': 'value', 'my_attrbiute_2': 'value_2'})">CLICK ME!</a>﻿
```

More info about sending product events can be found [here](https://help.user.com/en/articles/94-what-is-a-product-event.md).

## Product Events and REST API

Product events are fully accessible through the Positive User REST API, which allows you to retrieve and analyze product interaction data outside the application.

**Using the API, you can:**

-   [Retrieve a contact’s product events](https://apidocs.user.com/products/get-product-events.html)
    
-   [Retrieve product events by custom product ID](https://apidocs.user.com/products-custom-id/get-product-events.html)
    
-   Filter product events by event type
    

Filtering by event type is possible by adding the parameter: **?type=<product\_event\_type\_id>**

When working with the REST API, product event types are represented by numeric identifiers:

-   ADD\_TO\_CART = 1
    
-   PURCHASE = 2
    
-   LIKING = 3
    
-   ADD\_TO\_OBSERVATION = 4
    
-   ORDER = 5
    
-   RESERVATION = 6
    
-   RETURN = 7
    
-   VIEW = 8
    
-   CLICK = 9
    
-   DETAIL = 10
    
-   ADD = 11
    
-   REMOVE = 12
    
-   CHECKOUT = 13
    
-   CHECKOUT\_OPTION = 14
    
-   REFUND = 15
    
-   PROMO\_CLICK = 16
    

This API layer makes product events suitable for integrations, reporting, and external analytics, while keeping the core product data model efficient.

## Use Cases

-   **Behavior-Based Automations**: Use product events to trigger real-time actions based on customer behavior. For example, you can automatically send a reminder or offer when someone adds a product to their cart helping you recover abandoned carts and increase conversions.
    
-   **Highly Relevant Campaigns**: Use real product interactions to send campaigns that feel personal and well-timed. You can target recipients based on products they viewed, added to their cart, or purchased, and dynamically include product details in your messages to boost engagement and click-through rates.
    
-   **Segments Based on Buying Behavior**: Product events help you group contacts by what they actually do, not just who they are. This enables more accurate segmentation, such as:
    
    -   Contacts who added items to their cart but didn’t purchase
        
    -   Contacts interested in a specific product category
        
    -   Contacts who purchased discounted or promotional products
        
-   **Product-Based Filtering**: You can filter contacts using product events to quickly identify leads and customers with strong purchase intent. By combining event types with product attributes like category or price, you can create focused audiences for sales outreach, retargeting, or personalized messaging.
    

> **Info:** Product events are optimized for performance and scalability. Because historical attribute values are not stored, they are not suitable for use cases that require access to past product states, such as historical price comparisons. In such cases, consider modeling each variation as a separate product.

## Important Note

Product attributes always show the most recent value. Because of this, product events can’t tell the difference between earlier and later states of the same product.

If your product comes in multiple variations (such as different sizes, colors, or versions) make sure to create a separate product for each variant. This way, each variation is tracked correctly and its details won’t be overwritten by another one.

## Related Articles

-   [What Is a Product](https://help.user.com/en/articles/135-what-is-a-product.md)
    
-   [How to Send Product Events](https://help.user.com/en/articles/30-how-to-send-product-events.md)
    
-   [Introduction to Product Feeds](https://help.user.com/en/articles/183-introduction-to-product-feeds.md)
