E-com event implementation | Community
Skip to main content
P
PD10
Level 2
December 6, 2024
Solved

E-com event implementation

  • December 6, 2024
  • 1 reply
  • 440 views

Product upgrade Tracking within ecom

Userstory

1. A user accesses the checkout. He/she can upgrade the product within the checkout.

  1. He/she clicks on the upgrade button – the product in the checkout is upgraded

3.(Optional) The user can upgrade again to the next best product.

 

Business question:

1. How many times a product is upgraded? From which to which product?

  1. When an order is made, was there before an Upgrade to a Product? From which to which?

 

Current thoughts about implementation:
1. We want to setup a merchandise evar with values for upgrading in this specific syntax:

If we update the initial product one time to another product 

[initialProductId]_to_[updatedProductId]

If you somehow refresh or make the choice to update again:

[initialProductId]_to_[updatedProductId_1]_to_[updatedProductId_2]

We want to trigger an upgrade event at the point in the time the user clicks on the upgrading

AND we want to persist the value till the order

How do we need to setup the merchandising evar? Which syntax AND how can we influence the expiry that it will expire after purchase OR the user leaves the checkout page – to not wrongly attribute.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Jennifer_Dungan

So, because you are already dealing with "product" data, a simple Merchandising eVar using product syntax and the expiry you need (Visit? 1 Week? etc.... how long do items normally sit in your cart prior to the order being made?).

 

Interesting fact about s.products, is that the value set in a Merchandising eVar is maintained per product...

 

So if you have 

 

Product 1 / Merch eVar = "something"

and then

Product 2 / Merch eVar = "other value"

 

When you purchase both products (and don't pass a merch eVar with them), Product 1 will still stitch to the last value seen on it ("something") and Product 2 will still have "other value". The last touch per product is maintained, it's not the raw last value passed to that eVar; this is another powerful feature of Merchandising eVars.

 

 

Now, trying to maintain the full "upgrade path" of the product ([initialProductId]_to_[updatedProductId_1]_to_[updatedProductId_2])

 

That is going to be a challenge... the value of the eVar is maintained on the server... so it's not like you can append a new value to the existing value.

 

I don't know if this is going to be feasible... you could try and store the value in a cookie, session or local storage value... but if those are lost (deleted, destroyed between sessions, or the user changes devices, etc) then you won't have the information.

 

 

What about just tracking the "X to Y" upgrade on the upgrade (or even if it's always 1 > 2 > 3 > 4, as in they can't super upgrade from 1 > 4, just track the upgrade and not the original value... or track the "original" in one eVar and the upgrade in another?) , and looking at a custom attribution of Participation to see what upgrades the users interacted with on the path to subscription?

1 reply

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
December 6, 2024

So, because you are already dealing with "product" data, a simple Merchandising eVar using product syntax and the expiry you need (Visit? 1 Week? etc.... how long do items normally sit in your cart prior to the order being made?).

 

Interesting fact about s.products, is that the value set in a Merchandising eVar is maintained per product...

 

So if you have 

 

Product 1 / Merch eVar = "something"

and then

Product 2 / Merch eVar = "other value"

 

When you purchase both products (and don't pass a merch eVar with them), Product 1 will still stitch to the last value seen on it ("something") and Product 2 will still have "other value". The last touch per product is maintained, it's not the raw last value passed to that eVar; this is another powerful feature of Merchandising eVars.

 

 

Now, trying to maintain the full "upgrade path" of the product ([initialProductId]_to_[updatedProductId_1]_to_[updatedProductId_2])

 

That is going to be a challenge... the value of the eVar is maintained on the server... so it's not like you can append a new value to the existing value.

 

I don't know if this is going to be feasible... you could try and store the value in a cookie, session or local storage value... but if those are lost (deleted, destroyed between sessions, or the user changes devices, etc) then you won't have the information.

 

 

What about just tracking the "X to Y" upgrade on the upgrade (or even if it's always 1 > 2 > 3 > 4, as in they can't super upgrade from 1 > 4, just track the upgrade and not the original value... or track the "original" in one eVar and the upgrade in another?) , and looking at a custom attribution of Participation to see what upgrades the users interacted with on the path to subscription?

Terms & ConditionsAccessibility statement

Loading footer...