Multiple Paid Search IDs under 1 Marketing Cloud Visitor ID | Community
Skip to main content
J
jarriesg
July 17, 2024
Question

Multiple Paid Search IDs under 1 Marketing Cloud Visitor ID

  • July 17, 2024
  • 1 reply
  • 461 views

Hello,

I am trying to pull a visits report. I noticed that there are instances where an MCID counts 1 visit on a particular day; however, when adding a paid search ID to that mcid, there are multiple IDs. I would assume that each paid search ID would count as it's own separate visit and roll up as the total for that MCID. Is there a reason why the MCID would only count as 1 visit despite multiple paid search IDs listed on that same day?

 

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

1 reply

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
July 17, 2024

I am not sure what the attribution is on your eVar, there could be one value carried forward from a previous visit (if you have it set up to expire based on number of days or months).. but no, there is nothing that says a new paid search will trigger a new visit. Adobe Visits timeout after 30 minutes of inactivity, so if someone is actively clicking on your paid search links (and have not left the site for more than 30 minutes), then they will have multiple ids in the same visit.

 

Let's assume that your eVar26 is set to the default "Visit" expiry (so no carry forward from a previous visit)

 

  • (user clicks on ad A)
  • Page 1 (eVar26 set to "A")
  • Page 2 (eVar26 maintains value of "A" due to visit level attribution)
  • (user does another search, clicks on ad B)
  • Page 3 (eVar26 set to "B")
  • (user does another search, clicks on ad C)
  • Page 4 (eVar26 set to "C")
  • etc

 

All of the above pages, the user was still in an active session, performing multiple searches, and therefore setting the eVar value multiple times within the same visit.

    Terms & ConditionsAccessibility statement

    Loading footer...