Hi
Last month I posted this question: https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/acdl-and-the-quot-compone...
which unfortunately did not receive any answers yet.
To try and answer this myself I started doing some research about the limitations at first.
https://helpx.adobe.com/legal/product-descriptions/adobe-analytics.html
https://experienceleague.adobe.com/docs/analytics/technotes/low-traffic.html?lang=en#how-low-traffic...
Most importantly:
- 250 evars
- 1000 success events
- 500000 unique values per evar
I'm having a real hard time to take a fundamental decision on how to approach this given the above 3 limitations.
We've chosen to go with the Event Driven Data Layer way, using the ACDL extension for Adobe Launch. More exactly this solution https://webanalyticsfordevelopers.com/2020/11/17/lean-analytics-with-acdl/
At first I felt inspired by this tutorial series https://experienceleague.adobe.com/docs/experience-manager-learn/sites/integrations/analytics/track-... but in the tutorial, a condition is used to map component id to someType id based on the component resource type so there I divert. I just want to map it directly to
- evar1=componentId
- evar2=componentTitle
- evar3=componentResourceType
- event1=componentClicked
- event2=componentShowed
- event3=componentHid
(what I was asking for feedback / thoughts / advice about in my previous question https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/acdl-and-the-quot-compone...)
By doing it that way I would not spend a large part of my 250 evars on mapping each of the below eventInfo properties to their own eVar and similar events per type
- buttonId
- buttonTitle
- Button Clicked (event)
- tabId
- tabTitle
- Tab Clicked (event)
- tabPanelId
- tabPanelTitle
- Tab Panel Showed (event)
- Tab Panel Hid (event)
- listItemId,
- listItemTitle
- List Item Clicked (event)
- accordions, forms, hover/touch events etc... imagine how quickly you will run out of eVars and events (evars before events probably, but still).
We need to track a lot of (not just talking a few cta clicks) clicks and other user interaction events all over the UI, so I'm concerned how this will scale and can forsee how we will quickly run out of eVars if we follow that approach.
Which is why I thought it would work well to not use evars for each concrete type of component/element (button, tab, listitem, accordion etc) but breakdown the componentId dimension by another dimension / evar, component resource type. But then, if all components we track is mapped to evar1=componentId we might run into a scalability issue with the 500000 unique evar values and low traffic limitation.
So as I see it for AA to scale well with a pure EDDL based setup, we need A LOT more evars and events at our disposal, or we need that max unique evar limitation to be lifted? Is this just how it is for now, since evars / success events and the Adobe Analytics architecture was not built to support EDDL which is a somewhat new approach to tracking? Are there plans to support EDDL better (what can we expect and a rough ETA, so we might start today, in hopes it will scale when new features / limitations come later this year perhaps) or what am I missing?
