Expand my Community achievements bar.

Join us for the next Community Q&A Coffee Break on Tuesday April 23, 2024 with Eric Matisoff, Principal Evangelist, Analytics & Data Science, who will join us to discuss all the big news and announcements from Summit 2024!

In a single visit, How do I know if users are buying the product which they added to Cart?


Level 1

I am trying to understand if we have any velocity products.


I want to know if the users do the following in a single visit:

Visit the Product page, Add product to Cart and then Purchase the same product.


I do NOT want this for 1 particular product. That is possible using a simple segment where we use the "then" condition to add steps in addition to using the Product ID for mapping the product.


I need such a report for all the products available on the site. Can someone please chime in with the best approach?


Topics help categorize Community content and increase your ability to discover relevant content.

6 Replies


Level 3

Create a visit level segment with product view exists, cart additions exists and orders exists, and apply this segment to your product performance report. 




Level 1

I don't think this will work, as it will consider these 3 conditions without being specific to the Product.
If my understanding is correct, the Last Column in the following setup will show Orders for the particular product(in Row) when there was a "Product visit and Cart Add for any product during the visit" and NOT specific to the product seen in that row.




Community Advisor

I believe you could accomplish this with merchandising eVars bound to the product and expiring at the end of the visit.  Have one that's set with the product view and another with the cart add.  You could then report on each step with those merchandising eVars.  This would identify those orders placed during the same visit, or on subsequent visits.

In CJA, you can do this retroactively.  But in Analytics, I don't know of another way of doing this off hand.


Level 1

Thanks Josh.

The merch eVars approach is interesting, but I am unsure about how we would be able to use it for reporting.


What would the values in different merch eVars need to be so that we can tie it together? 

  • If we use "Visit ID" as the merch eVar value, the solution won't be scalable
  • If we use the "Date" as the merch eVar value, the solution won't be scalable
  • If we use generic values, how could we certainly assert that the events are happening in the same visit?



Community Advisor

hi @rsane1 - good thought exercise.  You might need to play around with it, but thinking aloud, or should I say typing aloud...

Let's say a customer has a product view for a KC Chiefs Jersey..

  -You set eVar15 to "1", on the product view, bound to the productID, with a visit expiration

In the same visit, the customer adds that item to cart

  -You set eVar87 to "1", on the cart add, bounce to the productID, with a visit expiration

In the same visit, the customer makes a purchase that includes the jersey.

In your reporting, you'd have the cart add where eVar15 = 1 (which I believe would only happen when same product was viewed during the same visit)

You'd also have the purchase where eVar15 = 1 and eVar87 = 1 (which I believe would indicate both the prodView and the cartAdd for that product happened in the same visit)

In the above scenarios, if the cart add and the purchase happened in subsequent visits, I believe your reporting would show you this where the eVar isn't set to 1.

Definitely test it out and might need to play around with it a bit, but seems like it should (or might) work.  You could validate it with using the segment you mentioned above for with a couple of different products.



Level 1

Hi @Josh__Stephens Conceptually, I agree it should work. My concern is about feasibility.


The goal was to report on it using Adobe workspace. As there will be millions of values in these 2 eVars, it would make it near impossible to segment in workspace.


If we need to use clickstream data, we can do it even without these two eVars as we could use the visitID to figure out the various activities in a single visit.