-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatically map eVars, props and events without processing rules #668
Comments
@dancingcactus @vivasd What are your thoughts about this request? |
@marcvdbergh Is the desire to have an XDM mixin with props, evars and events. Or to just have a place where you can pass in props, evars and events for them just to land in Analytics? |
Just a place to pass props, evars and events directly to Analytics to avoid having to add extra maintenance in the processing rules to pass every metric one by one. |
@marcvdbergh, this has been implemented last week. If you use the Field Group "Adobe Analytics ExperienceEvent Full Extension" and set your props as |
was this mixin intended to use for front-end data collection? As I spoke with Adobe they told me it is not best practice to use this mixin as it was created for CJA to export data from AA into AEP? |
Sounds nice! Is it implemented for eVars/events also? Could you share the documentation when ready? Thanks! |
Expected Behaviour
Directly map eVars, props and events to Analytics in the same way name, server and siteSection are directly mapped without a processing rule.
Actual Behaviour
Some webPageDetails are mapped directly others must be added with a process rule which adds an extra maintenance level.
Reproduce Scenario (including but not limited to)
Steps to Reproduce
Platform and Version
WebSDK
Sample Code that illustrates the problem
desirable situation
Logs taken while reproducing problem
The text was updated successfully, but these errors were encountered: