The report builder is the central piece to data visualization in HockeyStack. Each report consists of the following top-level components:
- Date range
- User grouping
- Data grouping
All report types and their caveats are listed below.
- Bar Chart
- Line Chart
- Pie Chart
Line charts do not allow data groupings. They are inherently grouped by date. The date truncation changes depending on the date range of the report. For ≤48 hours, data is reported hourly. For ≤60 days, data is reported daily. Anything beyond, data is reported monthly.
Pie charts only allow a single data source.
Number reports only show total aggregated data; data groupings are not allowed.
Funnel reports allow you to bring funnels you’ve already defined into dashboards. They are different than all other types of reports.
Report pull their data based on a combination of 3 main parameters:
- The action
- The datapoint related to the action
- The aggregation method for the datapoint
These are defined, in order, in the 3 main data dropdowns.
All report types, except the pie chart, allow multiple data sources.
The action dropdown can take the following values:
- any action: All actions
- enter site: Any session start
- view page: Any pageview
- touchpoint: Used to combine sales & marketing touchpoints. Currently denotes sessions, calls, meetings, and emails.
- Goals: Goals you have already defined
- Pages: Views to specific pages
The datapoint defines which aspect of the chosen action to analyze. It can take the following values:
- Uniques: Number of unique users that have taken the chosen action. The way this is calculated changes according to the user grouping you select. If you group users according to company_domain, for example, this will count unique s that have done the chosen action.
- Sessions: Number of sessions that include the chosen action
- Pageviews: Number of pages views that include the chosen action
- Times done: Number of times the chosen action was done
- Bounces: Number of bounced sessions that include the chosen action
- Session duration: The duration of sessions that include the chosen action
- Time on page: The duration of page views that include the chosen action
- Paid Ads
- Ad Spend
- Action Properties
The following options pertain to ads integrations. Selecting one of them will hide the action dropdown.
The definition of “clicks” depends on the ad network itself, so we don’t recommend using this metric for analysis over multiple networks.
The total spend on the campaign/creative. The output of this datapoint is formatted using the main currency of your account. You can change your main currency in the settings.
All your numerical action properties can be used in the report. Make sure you choose the action accordingly, as the property will be pulled from the chosen action. As an example, if you want to sum deal_amount for won deals, you should choose “Deal Moved to Closed Won” or a similar goal for the action dropdown.
The output for the revenue property will be formatted using the main currency of your account and the currency that was passed through with the action with the currency property. You can change your main currency in the settings.
The aggregation defines how to roll up the datapoints collected from the action.
- Average per hour
- Average per day
- Average per week
- Average per month
The averaging aggregations calculate the total for every possible averaging range, and then average those values. For example, if you average per week over 30 days, it will calculate the value for all possible 7-day ranges (there are 24 of them in a 30-day range), and then output the average of those values.
Apart from these options, you can perform 2 other functions:
- Add a ratio
- Add an attribution model
Clicking the “Ratio” button opens up another set of 3 dropdowns that allow you to define the denominator of the ratio.
In certain cases (outlined in the Attribution section below), you can click the “Attribution model” button to attribute the selected data to the selected data grouping.
HockeyStack’s attribution function depends on the following models.
- First Touch: All value is assigned to the first touch
- Last Touch: All value is assigned to the last touch
- Linear: The total value is divided and distributed equally among all touches
- Uniform: The total value is assigned to each touch
- Position-Based: The first and last touches get 40% of the total value each, and the remaining 20% is distributed among the remaining touches
- Time Decay: The time decay model is the only model where the total value attributed doesn’t add up to the total actual value. It is designed to attribute less value to a touchpoint the further away it’s from the conversion action. Specifically, the value halves every 7 days.
For fellow nerds, the formula is (where is total value and is days from the conversion action).
The attribution function can be used on a data source if:
- The report grouping is one of: Source, Page URL, UTM Source, UTM Medium, UTM Campaign, UTM Term, UTM Content, Ref, Touchpoint, Date, Action Name, Form Name, Action Element, Action Type and all other Action Properties.
- The datapoint is not one of: Bounces, Pageviews, Time on page, Session duration
- Using attribution with a Page URL grouping will also attribute value to the page that the conversion happens on. If you don’t want this to happen, filter the last page out using group by filters (explained in the Report Grouping section below).
The report grouping breaks results down by the property or properties you select. It can take the following values:
- Page URL
- UTM Source
- UTM Medium
- UTM Campaign
- UTM Term
- UTM Content
- Form Name
- Action Type
- Action Name
- Action Element
- Custom User Properties
- Action Properties
Used to combine sales & marketing touchpoints. Currently denotes sessions, calls, meetings, and emails.
The referrer collected by our web tracker. Does not include UTMs / paid referrers. If you need to see paid and organic referrers together, group by UTM Source in addition to Source.
The ?ref parameter in the URL
The form name that you have defined in your form builder (HubSpot, Pardot, Marketo, etc.)
Takes the following values: onsearch, onsubmit, onclick, start-session, enter-page, custom.
The name of custom actions collected using the API or integrations.
The CSS selector collected from click and form submit actions
All user properties that were either collected using the API or integrations are available in report groupings.
The selected property might be a shared property, meaning it relates to an object that is not native to HockeyStack. An example is company_domain, because it relates to the Company object from CRM integrations. If only one user that carries a certain company_id has a company_domain defined, but there are 10 users that carry the same company_id, all users are able to inherit the same company_domain when analyzing data. If you would like this behavior in your report grouping, you need to group by the main property (which is company_id in our example) in addition to the shared property (which is company_domain in our example).
All action properties that were either collected using the API or integrations are available in report groupings.
In some cases, you might want to combine multiple groups together when analyzing their data. An example to this would be content clusters, where you would have to group multiple page URLs together.
You can do this by clicking the target icon next to the property you are grouping by.
Then, you will be able to create custom groups using certain filters. The report will go through the groups in order when calculating the custom groups, so if a property matches two filters in your custom groups, it will be assigned to the first one.
In some cases, you might want to filter out groups that are not relevant to the report. An example to this would be when trying to figure out blog posts’ influence on revenue, where you would want to discard non-blog pages.
You can do this by clicking the filter icon next to the property you are grouping by.
The filters you define are combined together by “and”, so every new filter will narrow down the result set. Filters are applied after custom groups are applied, so if your custom group includes a specific value you want to filter out, you will need to exclude it from that group by defining another group for it that precedes and overrides the current group.
When you start receiving custom user properties in your data, the user grouping dropdown will appear in the report builder. This selection tells the report what definition it should use for a user.
For example, selecting company_id will group all users who have the same company_id together, and use that to calculate metrics. If you’re using attribution with the company_id grouping the first touch will be the entire user group’s first touch, rather than each individual user’s first touch.