Define one
1
Open the metric library
Go to a video → Analytics → General, then click Customize metrics.
2
Create the metric
Give it a name, then choose what it counts.
3
Arrange the cards
Drag the cards into the order you want. The layout is saved per video.
What a metric counts
required
Which event to count: a built-in player event (
click, hover, scroll, and so on),
or custom for an event you send yourself via the Custom Events
API.el_href | el_text | event_name
Which part of the event to match against. For a click, match the link’s
href or its
visible text. For a custom event, match the event name.contains | equals | wildcard | regex
How to compare.
list
What to match, and what to explicitly rule out.
count | pct | sum
- count: how many times it happened.
- pct: as a percentage of a denominator you choose.
- sum: the total of a numeric field, e.g. the
valueon your custom events.
optional
Only count the event if it happened before or after a point in the video.
Declaring an event name
Defining a custom metric on thecustom event does double duty: it also declares that
event name so the browser is allowed to send it.
quiz_completed exists as a custom metric. See Custom Events
API for why the browser path works
this way.
Events sent from your backend do not need the declaration to be accepted: a token is
already proof of trust. They still need it to be charted. Define the metric either way.
