Where possible, a configured report is displayed in graphical format in the Chart window. You can create a chart for any report that contains no more than one dimension. Multi-dimensional charts are not currently supported.
Notes
- By default, Hour of Day is the default X-axis.
- Long chart labels can be truncated. You can change labels in the Options screen.
Event Data in Charts
This table describes the event data in charts:
Event data | Description |
---|---|
Zero filling | Zero-filling is used to prevent reporting gaps. Report data can be reported as a set of
zeros (0 ) if a time-based dimension is added to the report and data is not
available for some displayed time segments. For null dimension values that are zero-filled, two
dashes (-- ) are inserted in the report. Counts of these values are reported as
0 |
Events and timestamps | Hits are evaluated against the set of current set of events at the time of evaluation. If hits are spooled or otherwise not processed immediately, there can be effects in reporting if changes are made to event-related objects in the interim. A message is reported in the Portal. |
Summary calculations | Total and average values are calculated only if the event is configured to display count or
sum data. These summary calculations are not available for other event data types or added functions
(for example, same day average). The displayed calculations are based on the data available in the
detail table, which reflects the currently displayed report.
|
Effect of X-axis dimensions
By default, labels for dimensions on each axis are empty. For display purposes, chart labels for lengthy dimensional values can be trimmed.
Charts
- Bar Graphs
- Each first x-axis dimension value becomes a major unit on the x-axis. On charts, no second x-axis dimension is permitted.
- Each event gets a bar within the minor unit.
- The height of the bar is the count, sum, and so on.
- Line/Shaded Area Graphs - Each dimension segment of each event gets a separate line.
- Pie - You cannot have X-axis dimensions on a pie graph.
Tables
- The first X-axis dimension becomes the first column. Each dimension value gets a row.
- The second X-axis dimension becomes the second column. Each dimension value gets a row for each dimension value in the first X-axis dimension.
- The Y-axis dimension is listed next.
- Each event gets a column. Events are listed in the order in which they are added to the report.
- Each row must have the total value for that dimension combination.
- The first row must be the total value for all the dimensional values.
Example
For example, you have a Price event that is stored like this in the DB:
Member Type | Credit Card | Product | Price |
---|---|---|---|
Bronze | Amex | Plane | 72 |
Bronze | Disc | Plane | 63 |
Gold | Amex | Car | 24 |
Gold | Visa | Boat | 73 |
Gold | Visa | Car | 32 |
Silver | Amex | Boat | 43 |
If you add events to the report, set the Data Count to be Sum, and make Member Type and Credit Card the X-axis dimensions, the table then looks like:
Member Type | Credit Card | Price |
---|---|---|
Bronze | Amex | 72 |
Bronze | Disc | 63 |
Gold | Amex | 24 |
Gold | Visa | 105 |
Silver | Amex | 43 |
There are only 2 Gold rows where there were 3 in the database. This is because the 2 Gold+Visa rows in the DB get combined (73+32=105) since there is no longer the Product type to differentiate them.
Now let us say you have another event that tracks the Insurance. It looks like the following.
Member Type | Credit Card | Product | Insurance |
---|---|---|---|
Bronze | Amex | Plane | 25 |
Bronze | Visa | Car | 15 |
Gold | Amex | Car | 15 |
Gold | Disc | Boat | 20 |
Gold | Visa | Plane | 25 |
Silver | Visa | Car | 15 |
If you add this event to the report, you would get this table:
Member Type | Credit Card | Price | Insurance |
---|---|---|---|
Bronze | Amex | 72 | 25 |
Bronze | Disc | 63 | - |
Bronze | Visa | - | 15 |
Gold | Amex | 24 | 15 |
Gold | Disc | - | 20 |
Gold | Visa | 105 | 25 |
Silver | Amex | 43 | - |
Silver | Visa | - | 15 |
There are more rows than what is displayed in the first scenario. This is because the Insurance event had different Credit Card values for each Member Type than the Price Event. So the report table is like the union of 2 data tables.
Effect of Y-axis dimensions
Adding a dimension to the Y-axis can be used to create a stacked data report. Multiple Y-axis dimensions are not charted.
If you add a Y-axis dimension that contains many values, do not position the chart legend to be on top, which can corrupt the display. If the report contains many items, some values can not be displayed in the Legend.
Charts
- Bar Graphs - you get stacked bars, with each element of the stack being the dimension segment.
- Line/Shaded Area Graphs - Each dimension segment gets a line.
- Pie - The dimension values make up the slices of the pie.
Tables
The Y-axis dimension values each get a column after the X-axis dimensions.
Example
For example, assume that you set Member Type as the first X-axis dimension, Credit Card as the second X-axis dimension, and Product as the Y-axis dimension. You would get the following table:
Member Type | Credit Card | Boat | Car | Plane |
---|---|---|---|---|
Bronze | Amex | - | - | 72 |
Bronze | Disc | - | - | 63 |
Gold | Amex | - | 24 | - |
Gold | Visa | 73 | - | - |
Gold | Visa | - | 32 | - |
Silver | Amex | 43 | - | - |