Until now, Vespucci consolidated the usage data of your systems based on two particular actions: "Application Opened" and "Application Backgrounded". These actions are quite natural if we consider a mobile application based on a transactional model. Let's imagine an e-commerce app, the customer opens the app, consults some products, makes a purchase and finally closes the app. In such a case, the notion of session is quite straightforward and defining it on the basis of Opened and Backgrounded tracks makes a lot of sense. However, there are some apps for which the notion of Session is less direct, so defining them on the basis of these elements probably makes less sense. Finally, and this is probably the most important point, some digital experiences (a support conversation, the viewing of an advertisement) cannot be understood through a definition based on the supposed opening or closing of an app (since the product is potentially no longer an app). That's why we deploy today a new way to consolidate your sessions in Vespucci. An approach that no longer requires to define actions to track the opening or closing of the app.
We call this new tracking method "Time Based Tracking". It consists in defining the session on the basis of a temporal criterion. Vespucci will analyze the timestamp of each of the DataLayers you are sending and try to consolidate them into concurrent events.
This approach is available today on your dashboard. To activate it, create a new project and specify "Time Based Tracking" in the new "Tracking Method" menu.
