Adobe Analytics Plugin Config - Web SDK Analytics | Community
Skip to main content
ajaxdinesh
ajaxdinesh
Level 2
June 20, 2024
Solved

Adobe Analytics Plugin Config - Web SDK Analytics

  • June 20, 2024
  • 1 reply
  • 621 views

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"

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by bjoern__koth

    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

    1. as part of the XDM schema, using the dedicated field group for adobe analytics
    2. using the data object (which will be the closest to what you see in above code snippet) e.g. data.__adobe.analytics.prop99 = "Social Media Organic".
      You may want to look at this video for a good step by step explanation
    3. as context data which will require manual mapping of data in Adobe Analytics processing rules (just don't do this!)

     

    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

    1 reply

    bjoern__koth
    Community Advisor and Adobe Champion
    bjoern__kothCommunity Advisor and Adobe ChampionAccepted solution
    Community Advisor and Adobe Champion
    June 21, 2024

    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

    1. as part of the XDM schema, using the dedicated field group for adobe analytics
    2. using the data object (which will be the closest to what you see in above code snippet) e.g. data.__adobe.analytics.prop99 = "Social Media Organic".
      You may want to look at this video for a good step by step explanation
    3. as context data which will require manual mapping of data in Adobe Analytics processing rules (just don't do this!)

     

    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

    Cheers from Switzerland!
      Terms & ConditionsAccessibility statement

      Loading footer...