What is a Filter (formerly Expression)?
A filter is an event-level filter that is usually applied to reports in order to scope the report to be calculated from only the events that match the applied filter.
How is Revenue defined?
Revenue is a special metric in Zaius. It can be defined to fit your needs but by default it is defined as Order Subtotal.
How is Revenue calculated?
Metrics Page, Lifecycle, Customer Report
The revenue displayed in the Metrics page is a sum of your revenue definition for all non-canceled orders.
Reports, Attribution, Campaign Reports
The revenue here is calculated using the following priority. Sum the given filter's engagement value. If no engagement value is specified for the filter then sum the account's revenue definition.
What is the difference between Metrics Overview and Reports?
The Metrics Overview page was created with the intention of being a complete view of specific metrics calculated from all events for a given identifier. At the time of loading the Metrics page, these results are filtered to your specific date range and presented to you. You cannot sort by Filter or by Segment in Metrics Overview. The Reports Page, on the other hand, allows you to display various metrics by any Dimension, sorted by any Filter, Segment and Date Range. This means that any given metric in the Report is only considering events that match the Filter, by users in the Segment for the Date Range.
Is Metrics Overview more correct than Reports?
Not necessarily. Each page is presenting similar information in a slightly different way. In general if you are looking for a metric over a period of time and how its performance changed when compared to a different period of time for all of your users in a given scope, then Metrics Overview will be the best source of information. However if you are looking for the performance of a metric for a specific type of event, or for a specific subset of people presented by a specific dimension, then Reports provides that flexibility.
What is the difference between Attribution and Campaign Report Attribution?
The Campaign Attribution Report is limited in the following ways:
- You cannot change the attribution model. The model is always a Last model. It will attribute a conversion to the last campaign engagement that led to the specified conversion.
- You cannot change the engagement. The only campaign engagements the report considers are Opens and Clicks.
The Attribution page allows you to change everything about the query, from the attribution model to the available engagements. See Attribution for more information.
How do I create a Segment of people who have purchased X times.
There are number of ways you can create these types of segments in Zaius and a few things you should be cautious of when dealing with Orders.
- Use Lifecycle to create a Lifecycle Segment.
- Use the Universal Segment Builder Order Count option to specify the number of Orders.
Do not use a filter to count Order Events
Zaius handles Order events in a special way that allows us to build reports for both Orders and Order Items. If an event with multiple line items comes in, then a filter of Order Events will count each of those line items as Order events. Expressions and Filters are crude event level filters that have no notion of an Order entity. See the Orders FAQ for a more detailed explanation as to why counting the number of Order events is NOT a representation of the number of Orders for a user.
How does Zaius handle Orders?
Order events in Zaius are manipulated into Order Events and Order entities. If an Order Event comes into Zaius with multiple line items there will be multiple Order Events for a singular Order entity. This means that using a filter that counts the occurrences of Order Events will be counting Order Items.
How can I easily get a count of all Orders in Reports > Rocket Table
The Purchases metric in reports will count individual orders. You may also choose to make use of the Unique Count metric which will count Unique pairs of fields.
What are all of the different Order Filters?
- The Order filter and Order Line Item Purchase filter have the same Predicate however there is a key distinction. The Order filter's value is Order Subtotal while Order Line Item Purchase's value is Order Item Subtotal. This means that when using filters to calculate revenue, the Order filter will aggregate the value of the Order while the Order Line Item Purchase filter will aggregate the value of all the individual line items.
- The Order Line Item Purchase Filter is explicit in only applying to events in which an item was purchased. The Order Line Item Filter does not make this distinction. Similarly, the Order Line Item Return Filter applies only to those items that were returned.