Question about definition of "New visit" in AudienceStream

[christian_gutto]

Hi,

I have a question about definitioin of a “new visit” in AudienceStream.

• Lets say I start a session in a browser and login with my email (=visitorId). I get put into som badges/audiences
• I close the browser
• I start a new incognito browser after 10 minutes (or on a new device).
• If I then login with same email, will this visit in audiencestream be seen as a new visit or not? That is, if I trigger an action based on “new visit” condition, will that action trigger?

/Christian

[dan_george · Accepted solution]

Hi @christian_gutto,

When you start a session in your browser and log in with your email, that will be a new visitor with 1 visit and 1 device.

Then 10 minutes later when you start an incognito session, you will be considered another new visitor with 1 visit and 1 device.

At this point you've yet to authenticate yourself in the incognito session. So at this point you are seen as 2 visitors - with 1 visit and 1 device each - and any "new visit" rules will apply to the incognito session.

However, once you identify yourself in the incognito session (assuming you have visitor stitching enabled) we will take all events for both devices, chronologically sort each event, then run through the AudienceStream profile definition to re-apply attributes correctly. At this point you will be seen as 1 visitor with 1 visit and 2 devices.

This is seen as 1 visit because a session is considered 30 minutes. If you had waited 35 minutes then you would have been 1 visitor with 2 visits and 2 devices.

I understand this may be a lot of info, but please let me know if that answered your question.

Cheers,

-Dan

[christian_gutto]

Thank you very much, I think I got it now. :-)

/Christian

[jaredhislop]

@dan_george

Does the new visit event count towards Omnichannel events? For example, if I upload a file and a line is processed, does that start a "visit" for the user in that processed line?

[dan_george]

@jaredhislop yes, a short session will be spun up to process the Omnichannel event(s) for that visitor. Keep all events from a visitor grouped in consective rows so that only once session is spun up.