Before we begin
Google Analytics has a plethora of different reports. There are many, but when integrated with bucket, you’ll most likely be feeding events to the Audiences report. For instance, if you want to know how many people visited your website from Austin, Texas, you can go into Audience and pull up the Geo Report. If you are new to events we recommend this article from Google Analytics help center https://support.google.com/analytics/answer/1033068?hl=en
GA allows bucket to record events with the following components: Event Category, Event Actions, Event label, and Event value. We suggest creating them in a cohesive way, for instance, you might want to track when someone becomes a potential lead after landing on your sales/results page so that it sends an Event hit with the following values:
A category is a name given to group information that you want to analyze. Usually, you’ll use the same category name multiple times over related events that you want to group under a given category. For instance, say you want to see all actions related to the integrations with a given funnel. You could use:
Category: "What’s your #1 Painting Skill" (funnel name)
Action: "Intermediate" (Name of the segment/bucket they landed on)
Label: "Seen"
In this case, there would be only one category—What’s your #1 Painting Skill—in your reports, and you could see aggregate metrics for user interaction with the total set of elements for that single funnel.
As with categories, the name you provide for actions is up to you, but keep in mind two important features of how an event action is used in the reports:
All actions are listed independently from their parent categories. This provides you with another useful way to segment the event data for your reports.
A unique event is determined by a unique action name. You can use duplicate action names across categories, but this can affect how unique events are calculated.
For instance, you might want to analyze all separate questions under the main category of "What’s your #1 Painting Skill" so that you get aggregate numbers for all question interactions.
Action does not always mean "action". You can supply any string for the action. In some situations, the actual event or action name is not as meaningful, so you might use the action parameter to analyze other elements.
As with categories and actions, there is a report that shows all the labels you create. Think of a label as a way to create an additional reporting dimension for user interaction with a page. For instance, say you have a question with five answers that you want to analyze. Each one of these unique responses addresses a paint point from your audience.
Use the "What’s your #1 Painting Skill” category with the "Q1" action, but each could also have a separate label (such as the exact response they chose) so that they appear as distinct elements in the report.
Category: "What’s your #1 Painting Skill”
Action: "Q1"
Label: "C"
The value component is an integer, and is used to assign a numerical value to a page object. For instance, you could use it to provide the times a “choice” from a given question has been selected.
Category: "What’s your #1 painting skill”
Action: "Q1"
Label: "C"
Value: 1
The value is interpreted as a number and the report adds the total values based on each event count. The report also determines the average value for the category.
The final form would look something similar to this: