Ecommerce Tracking

Just want to point out that while the Adobe Analytics Product String extension is a step in the right direction, the version currently available doesn't support merchandised evars or custom events so is of limited use

Search Discovery's AA Product String Builder is live in the production Launch extension catalog.

It's been a while in development, but I'm very pleased with the result.  There will be more docs and usage videos to come, but for now, there should be enough in-context help to get people rolling.

Enjoy!

Steve - You should check out the AA Product String Builder that just went live today.  It has full support for any number of merch evars and custom events.  Look for this in the Launch Extension Catalog.

Yes.  Today. Finally!  It's awesome.

Nice!

There is currently 3 extensions in the Launch catalog that help create the product string so we are closing this idea.

Ecommerce Tracking is essential for understanding how users move from product view → cart → checkout, and where they drop off. In Adobe Analytics/Commerce, this usually means setting up events like prodView, scAdd, scCheckout, and purchase, tied to proper product string variables so revenue and conversion data map correctly.

On my site, DiscountStars, we track this funnel closely to spot where deal-seekers abandon carts — often at shipping cost reveal — which then shapes how we position discounts earlier in the journey. Getting the tracking granular (not just "purchase complete") is what actually turns data into decisions.

Update for anyone finding this older thread:

Adobe now provides an Adobe Analytics Product String Builder extension for AEP Data Collection Tags. It adds a Set s.products action that reads product information from an object-based data layer and automatically constructs the correctly formatted s.products string.

It supports standard product fields such as product ID, category, quantity and price, as well as product-specific events and merchandising eVars. This avoids maintaining custom JavaScript for the product-string delimiters and formatting.

The typical rule sequence is:

1. Adobe Analytics Product String — Set s.products

2. Adobe Analytics — Set Variables for the corresponding success event

3. Adobe Analytics — Send Beacon

One limitation is that the extension expects an object-based data layer; it does not directly support every array-based data-layer structure. Therefore, some implementations may still need a data element to expose the expected paths.

For newer Web SDK implementations, Adobe’s recommended model is to send structured product information using the XDM commerce object and productListItems array. Adobe Analytics then maps that structured commerce data instead of requiring you to manually construct the legacy s.products string.

So, while there still is not a simple e-commerce checkbox inside the core Analytics extension, Adobe now provides supported options that remove most of the custom product-string work.

References: Product String Builder extension | Web SDK commerce data