Analytics

Different data between analytics modules (trend)

To better understand this difference, look at the example below. We’re creating a simple query which shows us page visit events and customers who performed this action.

Screenshot from the Synerise analytics module presenting choose event

  • Click the Preview button. You will see the trend presenting customers who have visited the page (in monthly intervals). In this case, we’ve got 284,119 customers with page visit events in May.

Screenshot from the Synerise analytics module presenting trend result

  • To change the context tick the Events radio button.

Screenshot from the Synerise analytics module presenting trend result

In response to the same query, the chart shows that 737,545 page visit events have been recorded in May. This means that 284,119 clients generated 737,545 actions (page visits).

Yoi will find more information about segmentations at the link.

I meet both segment conditions, but I'm in only one segment in segmentation
Tip: If you build a segmentation based on two segments, you might be confused that you meet both conditions of the segments, but you are only in one of them. This situation is a result of logical operations on the data sets.

OR is the operator between segments in segmentation (which means we’ve got an alternative between segments). If customers meet conditions in the first segment, they should not appear in the next segment in this segmentation. Let’s look at the example below. We have built a segmentation that consists of two segments: users who made a purchase and users who added a product to a cart.

Screenshot from the Synerise analytics module presenting choose event

  • As a result we get two bars representing two groups. The first (from the left) shows the users who made a purchase OR added a product to cart. The second bar presents the users who added a product to a cart, but didn’t make a purchase.

Screenshot from the Synerise analytics module presenting segmentation result

  • Now, let’s change the order of conditions. You’ll get different data, because changes in the conditions affect the query logic. Now the first bar presents the users who made a purchase OR added a product to a cart. The second bar includes the users who made a purchase, but didn’t add product to a cart.

Screenshot from the Synerise analytics module presenting segmentation result

These logical rules result from the fact that customers cannot be included twice in one segmentation, even if they meet both conditions.

Metric returns "undefined" as a result in Analytics Dashboard

This situation may occur if the analytics query is built incorrectly (for example, it contains a logical or mathematical error, like dividing by zero).

Screenshot from the Synerise analytics module presenting dashboard result

If you are dealing with such a situation, check the points below:

  • Make sure your metric formula is correct.

  • Check the components of your query separately. You can calculate every single metric to find out if one of them returns zero.

Screenshot from the Synerise analytics module presenting metric query

Note: If you haven’t found the solution to your issue, please collect information and provide examples or screenshots to our help desk.