User Interaction Tracking FAQs

Overview

This page answers common questions about implementing and troubleshooting User Interaction Tracking with Standalone Tracking.

Use it to verify the correct setup, avoid common mistakes, and understand how event tracking behaves in specific scenarios.

Does Standalone Tracking automatically capture all events?

No. Only the events you explicitly implement using Dressipi("track", ...) are captured. However, some metadata, such as session ID, browser language, and timestamps, are collected automatically.

Do I need to include both SKU and productCode?

Yes. Both fields are required for Product Detail Page (PDP) and Product Listing Page (PLP) tracking. These identifiers ensure products are accurately matched in analytics and recommendation engines.

Can I send personally identifiable information (PII)?

No. You must not send raw names or other PII. Email addresses passed to Dressipi("track", "identify", {...}) are automatically pseudonymised (hashed) before being processed.

What happens if optional fields are not included?

If optional fields (such as category or unitPrice) are missing, tracking still works correctly. Only the required fields are needed for event linkage and analysis.

Are custom fields supported?

Currently, no. The tracking system will ignore any additional parameters that are not part of the supported schema.

Can I track variant selections (like size or color)?

Yes. When a shopper selects a new variant, trigger a new PDP event with the updated sku and productCode. This ensures correct tracking for variant-level analytics and recommendations.

Is there a way to test or verify events?

Yes. You can verify event firing using browser developer tools or network logs. After each tracked action, verify that a request to the tracking endpoint is sent and returns a successful response.

What happens if tracking is implemented on multiple tabs?

Each page view generates a separate event but is linked through the same session identifiers. This allows multi-tab browsing to be tracked as a single user journey.

Best Practices

• Test event firing in both staging and production environments.

• Ensure customerId remains consistent after login and across sessions.

• Review browser network logs for missing or duplicate events.

• Avoid sending unused or unsupported parameters.