Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Is it possible to keep "memory" of an eVar value recorded in a previous server call?


Level 1


A page is loaded with multiple products displayed, it creates a 1st server call. To record details about different products  presented on the page we send 2 additional server calls. In a report we need  information recorded in the first call and in the second and third calls to be associated. Specifically,  eVar Product Area Name recorded on the 1st call, evar Product Type for a group of products displayed on the page is recorded on the second call, how to make a connection between the two variables instances to enable breaking up one eVar by the another? If to record eVar Product Area Name again on the 2nd call we double counting the eVar instances.

2 Replies


Community Advisor



I'm still trying to wrap my head around why you need multiple server calls... so I will try and provide some insights once I figure that out...


I'm going to use this example, and see if this is something similar to what you are trying to achieve:


You have a "primary" product (maybe this is viewing the detail page, maybe this is on an "add to cart" action) and then you have a few suggested products for "you might also be interested in", or "these are frequently purchased together" type of thing?


If so, why can't you use the products notation to pass all three products at once... and use different events / merchandising evars to distinguish the "primary" viewed/interacted with item with the additional suggestions?


This would be a lot better for multiple reasons:

1. The correlation is right there... no need for fancy data stitching

2. Reducing your server calls (and therefore keeping you contract limits contained - less chance of overage charges at the end of the year)

3. More efficient coding



Unless I am missing something really big here that explains why you need multiple calls.....


In that case, if you set up your eVar with an "Expire After" (this could be set to Visit, or maybe to expire after a specific event is triggered - probably what you would use in this case... ensure that event only triggers in the correct place)

This would allow you to use the "Instance of the eVar" to get the initial call (this limits the data to where the value is set), and use other more "extended" metrics in correlation with the other server calls....



In case you are new to it:

Products Notation 


Merchanding eVars:


eVar Expiry: 


Level 1

Hi Jennifer,


Thank you for your help. We are looking into  a solution you suggested. It looks like it can work for us.