According to the "Instances on Merchandising Variables" help document (http://microsite.omniture.com/t2/help/en_US/sc/implement/var_merchandising_instances.html), three things must be present to capture an instance against a merchandising variable:
We've been instructed by Adobe to use an incrementing dummy product value (prodmerch#) in the product string, along with an event (event48 'Merchandising Instances), to capture instances against any Merchandising Evar. I've also seen this in use on other retail sites. However, there is no binding event present.
In this particular case, we are trying to count clickthroughs upon internal campaigns (event71). Internal campaigns are captured into Evar2, and typically result in a product listing page (before the prodView event). After a clicking upon an internal campaign, the resulting page is tagged as
s.events = event71,event48 s.products = ;productmerch123 eVar2 = 123456
My question is this. Since I want the Evar to bind to an actual SKU (not a dummy SKU), how can I meet all three criteria when using Conversion Variable Syntax?
Solved! Go to Solution.
Views
Replies
Total Likes
Just gathering info here - what's the current limitation(s) in setting your internal campaign variable to a standard non-merchandising eVar? Based on the current information provided, it looks like it would be the simplest solution.
Views
Replies
Total Likes
Just gathering info here - what's the current limitation(s) in setting your internal campaign variable to a standard non-merchandising eVar? Based on the current information provided, it looks like it would be the simplest solution.
Views
Replies
Total Likes
Certainly the simplest route, yes. For these internal campaigns, we're looking to associate the purchased SKUS for those promotions, not the entirety of the order.
The 'Instances' metric in itself is counted for the Merchandising Evar, but any other event will not increment for Conversion Variable Syntax.
Views
Replies
Total Likes
Views
Likes
Replies