Goals (NEW!)
A segment can be converted to a goal. Goals help you find the amount of and conversion rates for specific user behaviors within specific user segments. Learn more about goals in the docs.
Currently goals are only stored locally, in localStorage, not persistently in the database.
Temporary idea, if you want to uniquely store goals and segments per domain: You can add multiple DNS entries to your dashboard (e.g. stats.domain1.com and stats.domain2.com, or d2.stats.domain1.com). The localStorage data where the segments and goals are stored will be stored per domain.
What can you use goals for?
Here are some examples on how you can use goals to better understand your visitors:
Conversion rates See how many sessions purchased out of all the sessions.
Goal — [Tag: purchased]
Active segments: [All]
Conversion rates for different segments Easily compare how many sessions purchased for different sources.
Goal — [Tag: purchased]
Active segments: [All], [Referrer: t.co], [Referrer: *google*]
A/B test results Quickly compare A/B test results and see which variant is better.
Goal — [Page: /checkout]
Active segments: [All], [Tag: AB_test1_default], [Tag: AB_test1_Variant1]
Funnel-like data See step-by-step values. This also works combined with multiple active segments: you can see the funnel data per segment (e.g. funnel for All visitors vs Facebook visitors).
Goal — [Page: /pricing]
Goal — [Page: /pricing, Page: /checkout]
Goal — [Page: /pricing, Page: /checkout, Tag: purchased]
Active segments: [All], [Referrer: *facebook.com*]
Creating a goal
Goals are based on segments. Segments can be converted into goals and goals can be converted back into segments.
To create a new goal, create a user segment or use an existing one from the header menu. You can then convert the segment to a goal, from the segment menu.
The segment will then be removed from the header and a goal will be displayed in the dashboard:
A goal can be removed, or converted back into a segment for editing purposes.
How the goal value is calculated
Goals display the number of user sessions in the merged goal segment, over the number of user sessions in each of the currently active header segments.
The merged goal segment is computed individually for each active segment by merging the two segments as explained below.
How the goal segment is merged with the active segments
Simply put, the merged goal segment is computed by combining both the filters from the active segment with the goal filters.
Example of internal goal segment merging:
Let's say we want to see how many of the visitors that came from Twitter visited the pricing page.
Create a segment for "User visited the pricing page":
Create a segment "Referrer is Twitter":
Converting the "Pricing" segment above to a goal.
This is the internal merged segment that will be used to compute the goal values.
The merged segment is simply "Referrer is Twitter AND User visited the pricing page". The goal value is computed by counting the user sessions in this merged segment. This is how the final goal card will look like:
How filters are combined
An intelligent way to combine filters has been implemented. It should work as expected in most cases. This is how specific filters are combined
| Filter | Active Segment | Goal Segment | Merged Segment | Merge type |
|---|---|---|---|---|
IP | A | B | Has IP B | Last value set |
Tag | A, B | C | Has Tags A, B, C | Union (AND) |
Page | A, B | C | Visited Pages A, B, C | Union (AND) |
Country | US, RO | RO, DE | Is from RO | Intersection |
Referrer | A.com, B.com | B.com, C.com | Came from B.com | Intersection |
Session length | min: 5s max: 30s | min: 17s max: 49s | min: 17s max: 30s | Intersection |
In some cases, the goal value will be 0 when the intersection of two filters is null. For example, if the active segment is "Country: RO" and the goal is "Country: US", the goal will be 0.
Last updated
