Extract the events and their counts from an events string.
-This function explicitly ignores event properties, and retrieves just the counts of the top-level events.
-Generate the SQL statement that can be used to create an easily queryable view on events data.
events STRING
+project STRING, dataset STRING, events ARRAY<STRUCT<category STRING, event_name STRING>>
OUTPUTS
-ARRAY<STRUCT<index STRING, count INT64>>
+
-Source | Edit
+Source | Edit
+event_index_to_match_string (UDF)
+Given an event index string, create a match string that is an exact match in the events_daily table.
+Parameters
+INPUTS
+
+OUTPUTS
+
+Source | Edit
+aggregate_match_strings (UDF)
+Given an array of strings that each match a single event, aggregate those into a single regex string that will match any of the events.
+Parameters
+INPUTS
+match_strings ARRAY<STRING>
+
OUTPUTS
+
+Source | Edit
+
+Escape all metachars from a regex string. This will make the string an exact match, no matter what it contains.
+Parameters
+INPUTS
+
+OUTPUTS
+
+Source | Edit
+get_funnel_steps_sql (Stored Procedure)
+For a given funnel, get a SQL statement that can be used to determine if an events string contains that funnel.
+Parameters
+INPUTS
+project STRING, dataset STRING, funnel_name STRING, funnel ARRAY<STRUCT<step_name STRING, list ARRAY<STRUCT<category STRING, event_name STRING>>>>
+
OUTPUTS
+
+Source | Edit
create_funnel_steps_query (Stored Procedure)
Generate the SQL statement that can be used to create an easily queryable view on events data.
-Parameters
+Parameters
INPUTS
project STRING, dataset STRING, funnel ARRAY<STRUCT<list ARRAY<STRUCT<category STRING, event_name STRING>>>>
Parameters
Source | Edit
get_count_sql (Stored Procedure)
For a given funnel, get a SQL statement that can be used to determine if an events string contains that funnel.
-Parameters
+Parameters
INPUTS
project STRING, dataset STRING, count_name STRING, events ARRAY<STRUCT<category STRING, event_name STRING>>
Parameters
Source | Edit
+create_funnel_regex (UDF)
+Given an array of match strings, each representing a single funnel step, aggregate them into a regex string that will match only against the entire funnel. If intermediate_steps is TRUE, this allows for there to be events that occur between the funnel steps.
+Parameters
+INPUTS
+step_regexes ARRAY<STRING>, intermediate_steps BOOLEAN
+
OUTPUTS
+
+Source | Edit
Extract events with event properties and their associated counts.
Also extracts raw events and their counts. This allows for querying with and without properties in the same dashboard.
-Usage
+Usage
extract_event_counts_with_properties(
events STRING
)
@@ -4063,7 +4101,7 @@ Usage
events - A comma-separated events string,
where each event is represented as a string
of unicode chars.
-Example
+Example
See this query
for example usage.
Caveats
@@ -4071,7 +4109,7 @@ Caveats
and for all events without their properties.
This allows us to include both total counts for an event (with any
property value), and events that don't have properties.
-Parameters
+Parameters
INPUTS
@@ -4083,7 +4121,7 @@ create_events_view (Stored Procedur
Create a view that queries the events_daily table. This view currently supports both funnels and event counts.
Funnels are created as a struct, with each step in the funnel as a boolean column in the struct, indicating whether the user completed that step on that day.
Event counts are simply integers.
-Usage
+Usage
create_events_view(
view_name STRING,
project STRING,
@@ -4269,71 +4307,33 @@ Examples
GROUP BY
submission_date
Parameters
+Parameters
INPUTS
view_name STRING, project STRING, dataset STRING, funnels ARRAY<STRUCT<funnel_name STRING, funnel ARRAY<STRUCT<step_name STRING, events ARRAY<STRUCT<category STRING, event_name STRING>>>>>>, counts ARRAY<STRUCT<count_name STRING, events ARRAY<STRUCT<category STRING, event_name STRING>>>>
Source | Edit
-aggregate_match_strings (UDF)
-Given an array of strings that each match a single event, aggregate those into a single regex string that will match any of the events.
-Parameters
-INPUTS
-match_strings ARRAY<STRING>
-
OUTPUTS
-
-Source | Edit
-create_count_steps_query (Stored Procedure)
-Generate the SQL statement that can be used to create an easily queryable view on events data.
-Parameters
-INPUTS
-project STRING, dataset STRING, events ARRAY<STRUCT<category STRING, event_name STRING>>
-
OUTPUTS
-
-Source | Edit
-event_index_to_match_string (UDF)
-Given an event index string, create a match string that is an exact match in the events_daily table.
-Parameters
-INPUTS
-
-OUTPUTS
-
-Source | Edit
-create_funnel_regex (UDF)
-Given an array of match strings, each representing a single funnel step, aggregate them into a regex string that will match only against the entire funnel. If intermediate_steps is TRUE, this allows for there to be events that occur between the funnel steps.
-Parameters
-INPUTS
-step_regexes ARRAY<STRING>, intermediate_steps BOOLEAN
-
OUTPUTS
-
-Source | Edit
-
-Escape all metachars from a regex string. This will make the string an exact match, no matter what it contains.
-Parameters
-INPUTS
-
-OUTPUTS
-STRING
+
+Extract the events and their counts from an events string.
+This function explicitly ignores event properties, and retrieves just the counts of the top-level events.
+Usage
+extract_event_counts(
+ events STRING
+)
Source | Edit
-get_funnel_steps_sql (Stored Procedure)
-For a given funnel, get a SQL statement that can be used to determine if an events string contains that funnel.
+events - A comma-separated events string,
+where each event is represented as a string
+of unicode chars.
+Example
+See this dashboard
+for example usage.
Parameters
INPUTS
-project STRING, dataset STRING, funnel_name STRING, funnel ARRAY<STRUCT<step_name STRING, list ARRAY<STRUCT<category STRING, event_name STRING>>>>
+
OUTPUTS
-funnel_sql STRING
+ARRAY<STRUCT<index STRING, count INT64>>
Source | Edit
+Source | Edit
diff --git a/mozfun/glam/index.html b/mozfun/glam/index.html
index 687b21acad3..c48fdf002b3 100644
--- a/mozfun/glam/index.html
+++ b/mozfun/glam/index.html
@@ -75,7 +75,7 @@