Setting Up & Testing Abandoned Activity: Cart, Wishlist & Browse

Prev Next

Goal

You will learn how to set up and verify Abandoned Cart, Wishlist, and Browse campaigns, ensuring that user activity is correctly tracked and processed across Mapp Intelligence and Mapp Engage.


Prerequisites

  1. Enable User Matching and Registration via Intelligence.

  2. Use the same product identifier in the eCommerce Product Catalog and the Abandoned Cart and Wishlist eCommerce tables.


How does it work?

User Matching Between Mapp Intelligence and Mapp Engage

If the user is already matched:

  • When the user's eid (device everID) or customer ID is known, the Abandoned Cart and Wishlist campaigns work correctly even if the user does not register or sign in during the session.

If the user is not matched:

  • If the user's eid (device everID) or customer ID is unknown, the Abandoned Cart and Wishlist campaigns work correctly only if the user registers during the session. The timing of the registration doesn't matter.

Examples:
  1. User visits the websiteadds an item to Wishlist/Cartregisters: This works.

  2. User visits the website → registers → adds an item to Wishlist/Cart: ✅ This works.

  3. User visits the websiteadds item to Wishlist/Cartleaves website: Information is lost.


Is my Setup working?

The table below provides guidelines for testing whether your Abandoned Cart and Wishlist setup works correctly.

User action

Mapp Cloud Action

How to test

User registers on the website

Mapp Cloud performs user-matching

They place a product in their Cart or add it to their Wishlist

The Mapp Intelligence Tracking script tracks the product with status (st) add

The product is added to the Abandoned Cart or Wishlist eCommerce table in Mapp Engage

They remove the product from the Cart or Wishlist

The Mapp Intelligence Tracking script tracks the product with status (st) delete

The product is removed from the Abandoned Cart or Wishlist eCommerce table in Mapp Engage


Configuration

Tracking

Step

Instructions

Documentation

Intelligence Pixel

Configure to send events:

  • add to cart

  • delete from cart

  • confirmation (triggers delete from cart)

  • add to wishlist

  • delete from wishlist

  • product view

Intelligence Mobile SDK

Configure to send events:

  • add to cart

  • delete from cart

  • add to wishlist

  • delete from wishlist

  • product view


Product Data

Step

Instructions

Documentation

Product Catalog

Ensure the product is saved with the same identifier across platforms:

  • In Intelligence: saved in the ba parameter (product name).

  • In Engage: saved in the productSku column.

eCommerce Tables

The Abandoned Cart, Wishlist and Abandoned Browse eCommerce tables are automatically updated by the Intelligence - Engage Integration.

Related Data

Use this option as an alternative to the Product Catalog


Whiteboards

Step

Instructions

Documentation

Entry Event

Set an Entry Event to the Abandoned Cart/Wishlist/Abandoned Browse add event:

  • For Abandoned Cart: react on add event.

  • For Wishlist: react on add event.

  • For Abandoned Browse: react on add event.

Whiteboard Goal

Set a Whiteboard goal for the Abandoned Cart/Wishlist/Abandoned Browse delete event to stop the campaign if a purchase is completed:

  • For Abandoned Cart: react on Last product deleted event.

  • For Wishlist: react on delete event.

  • For Abandoned Browse: react on delete event.

  • Or any other specified event to stop the job.


Email

Step

Instructions

Documentation

eCommerce-based personalization

Create emails using Abandoned Cart and Wishlist personalization