It would be infinetely beneficial to enable processing rules to build/handle the product variable. This is something other 3rd party tools like Segment & mParticle are able to do. As our implementation becomes more complex and spans multiple platforms we are reliant on mutliple developers (web, ios, android, windows, etc) for implementation support. Asking our developers to update the product string for all new measurement requirements requires time & money. However, asking them to prgoramatically solve adding new variables to a product context variable (or any context variable) reduces developement resources and increases implementation speed & flexibility.
It would be great if we could pass an array of product data as a context variable that we could then use to build the product string with processng rules. See below for an example array.
Also, it would be an added bonus if we no longer had to set s.events for events existing wthin the product variable. But if this idea ever comes to fruition, I would hope the processing rule would automatically do the work for us. : )
{
category: xxxxx,
prooduct: xxxxx,
units: xxxxx,
revenue: xxxxx,
variable1: xxxxx,
variable2: xxxxx,
variable3: xxxxx,
etc
},
category: xxxxx
prooduct: xxxxx,
units: xxxxx,
revenue: xxxxx,
variable1: xxxxx,
variable2: xxxxx,
variable3: xxxxx,
etc
