Feature request: Adobe Launch should remove the empty or undefined object from the XDM Object before sending the Web SDK Hit
Description
We just migrated from Adobe Analytics to the Web SDK, we are using the XDM Object Data Element to do the Mapping with the existing Data Elements. To decrease the amount of work required for that migration we found out that the best option was to do the Mapping at the value level for both eVars, pros & events.
Current Behaviour
We noticed that the Web SDK hits were sending empty string and empty object, what Adobe Analytics hits were eliminated by default. We did not have to worry about this before the Web SDK migration.
How would you like the feature to work
We would like that the Web SDK just work the same way the Adobe Analytics was working, just discard all the variables that are empty or undefined.
Why is this feature important to you
- Until now we were looking at the data only in Adobe Analytics and the reporting was working fine even without the non-optimized Web SDK hits, but now that we are trying to work with the Adobe Experience Platform, we noticed that all the Web SDK hits are failing because of syntax errors on at least a single field. For example: The message cannot be validated because a required property is missing: #/_experience/analytics/event1to100/event3: required key [value] not found.
- The current XDM Object structure around events is not ideal, we need to handle them at the "hundred parent level"
Why the structure is not like the eVars & props? If we just had one "events" parent object, we could make sure that we always have at least one event set and set each event on its own without handling a bigger object of 100 events. - The number of fields ingested through the Adobe Experience Platform has a direct impact on our Profile Richness Overage (we already reach out the limit
)
1 Comment
