How are single-page visits processed in AudienceStream?

[#1]

Question

I'm not seeing some records in AudienceStore and/or AudienceDB. What would cause this?

Answer

A single-page visit (session) occurs when a visitor leaves your website (or mobile app) from the landing page (or launch screen) without any further interaction. As a result, AudienceStream only receives one event for that visitor session. These "single-page visits" are handled differently from multi-page visits.

A single-page visit meets all of the following conditions:

• Only 1 Event Received at End of Visit
  The number of events received by the end of the visit is equal to 1.
• No Visitor Stitching
  The single event does not result in visitor stitching.
• No Badges Assigned
  The visit does not result in the assignment of a badge attribute.

If all of these conditions are met, the visit will be treated as a single-page visit. In addition, if a single-page visitor returns for a new session, it will be treated as a new visitor in AudienceStream.

Single-page visits and visitors are not persisted in AudienceStream, are not passed to AudienceStore, and therefore not stored in AudienceDB.

Things to consider:

• File Import
  These conditions do not apply to events received from an offline file import.
• EventStore and EventDB
  There will be records in EventStore and EventDB that do not have a matching record in AudienceStore and AudienceDB.