Recommendation Events Mapping

Event Mapping lets you connect any tracked website event to the four standardized recommendation events that power Intempt's recommendation engine — without modifying your existing tracking implementation.

Find Event Mapping on your integration details page under the Event Mapping tab.

How It Works

Your custom events          →  Recommendation events
─────────────────────────────────────────────────────
item_seen                   →  Product Viewed
cart_add                    →  Added to Cart
remove_item                 →  Removed from Cart
checkout_complete           →  Product Ordered

For each mapping you:

1. Select your custom event name
2. Choose the corresponding recommendation event
3. Map your attributes (e.g. id → productId)

The recommendation engine then uses your events to power feeds and models — no code changes required.

Supported Recommendation Events

Product Viewed

Powers the Recently Viewed feed and view-based recommendation models.

• Required attribute: productId
• Map your product identifier field (e.g. sku, id, product_id) → productId

Added to Cart

Powers the Recently Added to Cart feed and cart-based recommendation logic.

• Required attribute: productId

Removed from Cart

Maintains accuracy of the Recently Added to Cart feed. When a user removes an item, this event ensures it no longer appears in cart-based feeds and keeps cart state consistent.

• Required attribute: productId
• Configure this if you use any cart-based recommendation feeds

Product Ordered

Powers purchase-based recommendation models, clears purchased items from cart feeds, and enables post-purchase recommendations.

• Required attribute: productId

Attribute Mapping

For each mapped event, connect your incoming event attributes to the required recommendation attributes.

Example: if your event contains:

{
  "id": "SKU_123"
}

Map: id → productId

Attributes can come from three sources:

Benefits

• No implementation changes — Map existing events without touching your tracking code
• Accurate feeds — Recommendation feeds reflect real user behavior
• Clean cart state — Removed from Cart keeps cart-based signals accurate
• Consistent models — Standardized inputs across all recommendation strategies

Best Practices

1. Always map productId — it is required for every recommendation event
2. Configure Removed from Cart if you use cart-based recommendation feeds
3. Ensure mapped events reflect real user behavior — don't map unrelated events
4. Test after configuration — verify events are triggering correctly in the integration dashboard