Workflow Triggers: Product Viewed and Added to Cart

Captivation Hub can capture pre-purchase shopper activity from your Ecommerce Stores and connected Shopify stores, then use that activity to automatically start workflows. These triggers let you act on shopper intent before a purchase is completed.

Product Viewed Trigger

The Product Viewed trigger starts a workflow when an identified shopper views a product, before they add it to their cart or make a purchase. This is useful for interest-based follow-up, such as sending a targeted email or SMS about a specific product or store.

You can filter qualifying activity by factors like duration, store, product, and order source.

Note: For Captivation Hub Ecommerce Stores, no additional setup is required. For Shopify, your store must be connected with the required Web Pixel installed.

Add Product to Cart Trigger

The Add Products To Cart trigger starts a workflow when an identified shopper adds a product to their cart, before they complete checkout. Since this event happens later in the buying journey than a product view, it indicates stronger purchase intent.

You can narrow workflows using cart-specific conditions, and filter by factors like duration, store, and checkout status.

How Identity-Based Activity Association Works

Shoppers sometimes view products or add items to their cart before Captivation Hub knows who they are. Here's how the platform handles that:

1. A shopper views a product or adds one to their cart.
2. If not yet identified, the activity is tracked anonymously.
3. The shopper later identifies themselves by logging in or checking out.
4. Previous activity from that browser is associated with the shopper's contact record.
5. The identified shopper's qualifying activity can then trigger the configured workflow.

Only identified visitors trigger these workflows. Unidentified browsing activity is retained for up to 14 days. If the shopper doesn't identify themselves within that window, the anonymous activity is discarded.

Activity association is browser-scoped. Activity captured in one browser does not carry over when the shopper identifies themselves on a different browser or device.