![]() How does this affect timeline timestamps and audiences joined/left dates in AudienceStore? Since Omnichannel data is considered event data it will behave the same, meaning the event data will persist in the Event Database and chronologically be a part of the online event data. This means the master visitor profile will now have the Trait storing the customer_type. However, when AS reprocesses all the events, AudienceStream will use the latest AudienceStream profile definition and re-evaluated the Trait's enrichment. The Trait capturing customer_type will not have existed in either device's visitor profile. We stitch the desktop and mobile profiles together.2 weeks later the visitor authenticates on Mobile with the same customer_email value (but no customer_type is passed).1 week later a Trait is created that stores the customer_type.Visitor ID is assigned using customer_email.Customer registers on a website on their desktop.Typically, it is a very quick process.ĭoes this mean stitching is backwards compatible? Imagine this scenario of events: However, over the past couple of years Engineering has made numerous optimizations to make this stitching process more efficient. These have typically been correctly stitched in the past.ĭepending on how many events there are, stitching can take awhile to execute as it's an extremely complex and CPU heavy task to execute. Even though tally and list attributes look like they are merged, it's still just because they are setup using additive enrichments (i.e., add to list, increment tally, etc). You may be curious about more advanced attributes such as list and tally. So back to the question, whether the "Opt-In Status" flag will be set to “True” or “False”, the answer is that it depends on the outcome of all of the enrichments that will be reprocessed when AudienceStream replays all of these visitors' past events. When matching profiles are found, AudienceStream will load up all past events for all of the visitors being stitched, sort each event chronologically, and replay all events to create a master stitched profile. With that foundation set we can now discuss what occurs upon a stitching event. Over the lifetime of a visitor there can be hundreds or even thousands of events, and a majority of the time these persisted events are never used and will expire when the visitor profile expires.When a visitor’s visit expires, both the visitor and all of the events of their visit are stored in two different DB collections (separate from EventStore logs).As events feed into AudienceStream, these events are used to create a visitor profile.First, it’s important to note a few important system functionalities.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |