The .mapping feature looks really awesome, but seems a bit hamstrung. As a consumer, I would expect to be able to map not only the event name (for a particular integration) but also the attributes for a given track call. For example, GTM is quite happy accepting a nested json structure of attributes; however, Optimizely cannot. So in order to send the "same" data to optimizely as GTM, the attribute structure must be mutated for one or the other (or both) of the integrations.
It would be fantastic if there were a feature like .mapping but for attributes as well. Has there been any thought about this type of feature in the past? Any recommended alternatives? As best as I can tell, it would be presently implemented as a per-integration option. But having the capability to define it for all integrations would be fantastic.
The
.mappingfeature looks really awesome, but seems a bit hamstrung. As a consumer, I would expect to be able to map not only the event name (for a particular integration) but also the attributes for a given track call. For example, GTM is quite happy accepting a nested json structure of attributes; however, Optimizely cannot. So in order to send the "same" data to optimizely as GTM, the attribute structure must be mutated for one or the other (or both) of the integrations.It would be fantastic if there were a feature like
.mappingbut for attributes as well. Has there been any thought about this type of feature in the past? Any recommended alternatives? As best as I can tell, it would be presently implemented as a per-integration option. But having the capability to define it for all integrations would be fantastic.