Dear guys,I found a definition of return visits like below and it says
that it includes "non-cookied visitors."Return Visits Return VisitsShows
the number of visits where visit number is greater than 1 and includes
non-cookied visitors.Could anyone explain more about this? I don't
understand how they can include "non-cookied visitors".
Dear Arun,Did you mean this?1) Create data element which returns DomainA
and DomainB 2) In Settings Name Value cookieDomain = %data element%I set
this and get experience ID from DomainB too but they still don't match.
Dear Adobe Community,I have a question for you guys. Please give me a
hand, professionals!When I create a rule to a submit button and add an
event-based rule to generate an event, the tag fires whenever a user
clicks the button.So this can include an action that user clicks but
fails to submit because an alert message pop-up.In this case, how can I
modify my tag only to track true data that users submits and go well to
the database.Sincerely,Jaehong Kwon
Dear Arun,Thank you for your advice. I checked raw data from Data
Warehouse but different visitorID generated for each domain. I will use
this raw data to DMP implementation so I really need to identify unique
visitors across 2 different domains by one unique ID value. Is there any
solution for this?
Dear Arun,I really appreciate your sincere support. I solved the
cookieDomainPeriods problem and now I see "Y" in cookie supported on
domain B too. But Domain A is generating mid, which is experience cloud
id but Domain B is generating s_fid, which is fallback id.Now should I
tag AppendVisitorIDsTo ?
Dear all analytics professionals,I was trying my best to track
cross-domain tracking but I guess I ran into a deadlock.Here is my
case:I have a domain A. Several pages have iframed(?) form in the page
sourcing from Domain B.In other words, a page has domain A url but its
form contents are coming from Domain B.I am using DTM and I placed same
DTM embed code between Domain A and Domain B.Now I can implement Adobe
Analytics tags to Domain B's forms' submit button but this click call
does not includ...