> Page View Event

The “page view” is a universal event created to track every screen displayed in the app.

In the old version we had one different event for each screen using the “Viewed /,” + screen name as a pattern.

How to replace

For select a specific Page, use the “path” attribute to filter the path to be tracked. As a example:

For track users who visited the menu page:

• Instead of looking for users who performed: "Viewed /menu"

• Select users who performed: "Page view” where path = "/menu"

Open

> Checkout vs Ecommerce Checkout

Both events measures the moment where a user checks out the items within their cart. They are triggering in the same moment, and therefore have the same counting for frequency and users.
In the new “eCommerce checkout“ we added attributes related to the cart content ($Price, quantity, revenue, product count, tax amount, total amount). Attributes related to the page, session configuration or user were removed.

How to replace

Both events have the same amount of events and users. (fig. 1). So you can just replace one event for another in order to track the who performed the event or event occurrence.

Open

(fig.1)

For track events by attributes related to the user configuration (e.g. enableCheckoutUpsellItems2, or enableHomePageRecentItems) you can combine the event “flags Evaluated” to the analysis.

> Purchase vs Ecommerce Purchase

As the checkout vs Ecommerce Checkout, both events are triggering in the same moment, and therefore have the same counting for frequency and users.
In the new “eCommerce Purchase“ we added attributes related to the cart content ($Price, productId, quantity, revenue, product count, tax amount, total amount). Attributes related to the page, session configuration or user were removed.

How to replace

Both events have the same amount of events and users. (fig. 1). So you can just replace one event for another in order to track the who performed the event or event occurrence.

(fig.1)

For track events by attributes related to the user configuration (e.g. enableCheckoutUpsellItems2, or enableHomePageRecentItems) you can combine the event “flags Evaluated” to the analysis.

> Auth flow “Sign Up Submitted” vs “Sign Up Complete”

The Sign up complete it`s fired always as a response to the “Sign up Summited” event. Thus, you can use it for counting how many time a user enters in the Sign up Flow. Only exceptions should be some technical problems on the interface or even in the data transmission.

In addition to the count of the occurrences the “Sig up complete“ event collects the results of the sign up attempt using the Response attribute. Failure attempts are marked as “Failure“ and the Reason it`s also collect through the “Response Description” Attribute (fig. 2).

How to replace

Both events have the same amount of events and users. (fig. 1). So you can just replace one event for another in order to track the who performed the event or event occurrence.

(fig.1)

(fig.2)

> User States & Navigation

Events used for filtering how many times/users had viewed an certain modal can be replace using the object attributes. See some examples in the table below.

Empty events

Events without previous categorization and already with more than 12 months of data.