Overview
Abandoned Browse is a predefined eCommerce table that records products a contact has viewed on a website or app without further interaction. This data helps identify early purchase interest and supports targeted follow-up through segmentation, personalization, and automation.
Common Use Cases
Identifying contacts who have viewed products but did not continue to add them to the cart or complete a purchase
Segmenting contacts based on recent product browsing activity
Triggering follow-up campaigns that address early purchase interest
Personalizing messages with recently viewed products to encourage return visits
Supporting short-term re-engagement scenarios using time-limited browse data
Prerequisites
Account Setup
- Ensure that Mapp Engage and Mapp Intelligence accounts are connected.
- Enable user matching between Mapp Intelligence and Engage (refer to Mapp Cloud User Matching).
- Confirm that account settings are compatible with IPv6 and that tracking domains support it if applicable.
Tracking Pixel Configuration
- Configure the tracking pixel (see Smart Pixel Setup & Configuration).
- Integrate tracking for your website's customer behaviors (e.g., browse abandonment) using unique, consistent event names.
Mapp Engage
You can use either Product Catalog or Related Data to store product information. Ensure the eCommerce table Abandoned Browse and the Product Catalog / Related Data use the same product identifiers. In Mapp Engage, this identifier is represented by the
productSKUcolumn. In Mapp Intelligence, it is thebaparameter (productName).
Navigation path
Administration > eCommerce > Abandoned Browse
Behavior and Data Handling
Predefined eCommerce table: Stores products a contact has viewed without further interaction, such as adding to cart or purchasing.
Browse activity recording: Product views captured via the Mapp Intelligence Pixel are written to the Abandoned Browse table and made available for further use.
Usage across features: Recorded browse data can be used for:
Abandoned Browse campaigns in Whiteboard
Contact segmentation in the Segmentation Builder
Email personalization for targeted messaging
Product identification logic: Products are matched across systems using a shared identifier:
In Mapp Engage, the identifier is stored in the
productSKUcolumn.In Mapp Intelligence, the same identifier is passed using the
baparameter, which represents the product name.
Supported product data sources: Product information can be resolved from either Product Catalog or Related Data, as long as the same product identifiers are used.
Data lifecycle: Entries in the Abandoned Browse eCommerce table are retained for 30 days and then automatically deleted.