User Interaction Tracking

1 Overview

User Interaction Tracking records key steps in a shopper’s online experience, from browsing products to completing an order. It provides a unified view of customer behavior across touchpoints.

This tracking is powered by the Standalone Tracking. Once implemented, it automatically links events across sessions, allowing detailed analysis of engagement and conversions.

Prerequisites

Before you begin, make sure you have installed the Standalone Tracking.

Note:

Always trigger a pageView event before other tracking events (such as PDP, PLP, or Order) to ensure proper session linking and accurate reporting.

2 Tracking Events and Functions

Each of the following tracking methods captures the shopper’s key interactions. Use these calls to record the corresponding actions.

2.1 Page View Tracking

Tracks when a shopper views a page. This function is essential for linking all subsequent events, especially when the user has multiple tabs open.

Dressipi("track", "pageView");

2.2 Identify (Customer Identification)

Connects customer actions before and after login.
Use this function when a customer:

• Logs in

• Registers a new account

• You can also include customer identity details in the order event to link purchases with known users.

Dressipi("track", "identify", {
  email: "customer@example.com",   // pseudonymised automatically
  customerId: "id_from_your_database_here"
});

Parameters

Do not send raw names or other personally identifiable information (PII).

2.3 Product Detail Page (PDP) /itemView

Captures when a shopper views a specific product detail page or product view.
Use this function when a shopper:

• Opens a product detail page

• Switches to another product variant (for example, colour or size)

• Views products dynamically loaded through JavaScript (trigger a new PDP call for each view)

pdp and itemView are internally identical and can be used interchangeably.
Always ensure a pageView event is tracked before calling this function.

Dressipi("track", "pdp", { // you can use 'itemView'instead of 'pdp'
  sku: "ABC123",
  productCode: "XYZ789"
});

Parameters

Note:

Both sku and productCode are mandatory parameters. Always provide both for accurate tracking and reporting.

2.4 Product Listing Page (PLP)

Tracks interactions across product listing or search result pages. Required if the PLP widget or PLP API is in use.

You must track a pageView before calling this.

Dressipi("track", "plp", {
  items: [
    { sku: "ABC123", productCode: "XYZ" },
    { sku: "DEF456", productCode: "LMN" }
  ],
  filters: [
    { name: "Style", selected: ["Casual", "Evening"] }
  ],
  page: { number: 1 }
});

Parameters

2.5 Add to Basket / Remove from Basket

Use this function when a shopper adds or removes a product from their basket.

Dressipi("track", "addToBasket", {
  sku: "ABC123",
  quantity: 1,
  name: "Dress",
  category: "Dresses",
  unitPrice: 12.99,
  currency: "GBP"
});

Dressipi("track", "removeFromBasket", {
  sku: "ABC123",
  quantity: 1,
  name: "Dress",
  category: "Dresses",
  unitPrice: 12.99,
  currency: "GBP"
});

2.6 Order Confirmation

Captures completed orders. At least one line item with a valid sku and quantity is required.

Dressipi("track", "order", {
  orderId: "1234567",
  total: 104.99,
  tax: 19.99,
  shipping: 5,
  currency: "GBP",
  lineItems: [
    {
      sku: "ABC123",
      name: "Red Dress",
      price: 99.99,
      quantity: 1,
      currency: "GBP"
    }
  ]
}, { customerId: "CUST123", email: "customer@example.com" });

Order Validation
An order is considered invalid if:

• No line items are provided, or

• A line item has no sku or quantity.

Order Parameters

Line Item Parameters

Note: The list_price field is not supported.

3 Automatically Captured Parameters

In addition to the specified fields, the Standalone Tracking automatically captures contextual data such as:

No additional developer configuration is required.

4 Parameter Reference

5 Best Practices

• Always trigger a pageView before other events.

• Use identify when customers log in or complete an order to link activity across sessions.

• Ensure sku and productCode are provided for PDP tracking.

• Validate that each order includes at least one valid line item.

• Use consistent currency and orderId formats across systems.