How do we handle the below config in Web SDK AA? Do we need to add our own custom logic to achieve the below part?
/* Search Term De-Duplication Config */
s.successfulSearchEvent = 'eventX';
s.nullSearchEvent = 'eventY';
s.blockedSearchEvent = 'eventZ';
s.intraResultsSearchEvent = 'eventA';
s.searchTermVariable = 'eVarA';
s._channelDomain = "Social Media Organic";
s._channelPattern = ''Email|EM>Affiliates"
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Hi @ajaxdinesh
I assume you have set up dedicated events and custom Dimensions (prop/eVar) in Adobe Analytics for the above mentioned?
This would already not work on the classic AppMeasurement library without assigning the correct buckets to them e.g.
s.prop99 = "Social Media Organic";
s.events = "event11"; // assuming that e.g., the successfulSeachEvent is set up to be event11
// etc.
There are a couple of different approaches to handle this as explained here
Given the way you phrase your question, I presume you are still quite new to Analytics, correct?
In that case, 1. and 2. are the recommended approaches, 3. is out of question the most cumbersome, error prone and 0-debuggable approach.
If you ask me, 2. is the most intuitive way (see video linked above) and creates less overhead through a crazy bloated XDM schema.
Hope that helps
Hi @ajaxdinesh
I assume you have set up dedicated events and custom Dimensions (prop/eVar) in Adobe Analytics for the above mentioned?
This would already not work on the classic AppMeasurement library without assigning the correct buckets to them e.g.
s.prop99 = "Social Media Organic";
s.events = "event11"; // assuming that e.g., the successfulSeachEvent is set up to be event11
// etc.
There are a couple of different approaches to handle this as explained here
Given the way you phrase your question, I presume you are still quite new to Analytics, correct?
In that case, 1. and 2. are the recommended approaches, 3. is out of question the most cumbersome, error prone and 0-debuggable approach.
If you ask me, 2. is the most intuitive way (see video linked above) and creates less overhead through a crazy bloated XDM schema.
Hope that helps
Views
Likes
Replies