I would probably set up the following segments: Segment 1: INCLUDE Visits where page = "homepage"Segment 2: EXCLUDE Visits where page = "homepage" The exclude segment is important. If you say "include where page does not equal 'homepage'" and the visit includes views of "homepage" and "anotherpage",...

 Bounces: https://experienceleague.adobe.com/docs/analytics/components/metrics/bounces.html?lang=en Exits: https://experienceleague.adobe.com/docs/analytics/components/metrics/exits.html?lang=en Entries: https://experienceleague.adobe.com/docs/analytics/components/metrics/entries.html?lang=en 

@SS20  - The Adobe Analytics visit begins when Adobe receives the first beacon/hit. So, depending on how your implementation is set up and the timing of the first Analytics request, it could be at any point during or after the page load process.

For Target, you can look at using the mbox3rdPartyId approach: https://experienceleague.adobe.com/docs/target/using/audiences/visitor-profiles/3rd-party-id.html?lang=en

@parthgupta - Make sure you understand the potential impacts of setting a custom visitorID. For example, you probably won't have your custom login ID when the visitor lands on the login page. In this case, if you're sending data to Analytics on the login page, you'll have to use an anonymous identif...

@valtsai - Assuming your "search" event fires on load of the results page, and the page loads enough to fire the call to Adobe, then you will see all metrics and dimensions collect and increment in reports. If the page is reloading before the call to Adobe can fire, then you will not see the data co...

In your question, you listed the following for the second hit: Second click in homepage (gotoSpa):event:openPopEv, event:ctaClickEv (why not only ctaClickEv?)prop2 = goNameevar2 = goName I interpreted that as firing BOTH events on the same call. Based on that interpretation, both events would increm...

@AronoeleS - Taking those two sample hits into consideration, I agree with the numbers as you've listed them. Consider the following points:On the first hit, you populate both prop2 and eVar2 with "popName" AND you trigger the "openPopEv" event. This lets Adobe associate the event with the dimension...

@AronoeleS - I think you're close, but I would expect slightly different numbers:  In your sample/hypothetical session, you mixed page (s.t()) and link tracking (s.tl()) calls, which has an impact on Page View and Page Event metrics. Think of it as only s.t() calls increment Page Views and s.tl() ca...

@AronoeleS - I don't know that I answered your final question:  "If I just want to track click cta hit numbers split by cta name, the right setting is to set a prop and then match this prop with occurences, is it right?" You can go a lot of ways here. The way you suggest in your question is one, for...