cid and Adverting Analytics | Community
Skip to main content
U
Uwe_Moeller-Goebel
March 4, 2021
Solved

cid and Adverting Analytics

  • March 4, 2021
  • 2 replies
  • 2254 views

Hi,

I am currently using cid to track paid search. Now I want to add the s_kwcid to gain more details for paid search. The question is, do you have any experience using both parameters simultaneously? Is there any kind of negativ interaction? From my understanding AMO and regular channel settings are completely different and should have no effect on each

    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 khurshid

    From Analytics perspective, there is negative impact of using multiple tracking codes.

    2 replies

    khurshid
    Adobe Employee
    khurshidAdobe EmployeeAccepted solution
    Adobe Employee
    March 4, 2021

    From Analytics perspective, there is negative impact of using multiple tracking codes.

      U
      Uwe_Moeller-GoebelAuthor
      March 4, 2021
      Hi Khurshid, thank you for the reply. How does this effect manifest in the reports? Will the counts differ or will there be complications with the capturing itself?
      jeff_bloomer
      Community Advisor and Adobe Champion
      jeff_bloomerCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      March 4, 2021

      To echo @khurshid's reply containing a typo, there is NO negative effect.  🙂

      You also have the ability, if you want, to send this parameter's value to a separate variable for analysis independent of other tracking codes.  I have seen this done and even set up internal campaign tracking codes to avoid cluttering up my external campaign tracking

      Just remember, if you decide to do it, to configure your other variable the same as your campaign tracking variable.  For instance, if your tracking codes don't expire for a month, you will want to set up your secondary eVar the same way.

       

        Terms & ConditionsAccessibility statement

        Loading footer...