Amplitude Event Taxonomy Template - Instructions

What

This template will assist with the strategic planning of how to instrument y
application.

Why

Proper instrumentation enables you to more effectively analyze your applic

data. Instrumentation issues, such as, omitted events, poor naming, and m
properties can prevent you from realizing the full value of Amplitude and y

1. Read the Quick Start Guide

Amplitude Quick Start Guide
Prerequisites
2. Set business and analytics goals
1. Fill out the Event Group section on the next tab
Actions

2. Complete the Event List section (with properties) on the next tab

3. Complete the User Property List (for all user properties not sent with eve

ructions
planning of how to instrument your

re effectively analyze your application

itted events, poor naming, and misuse of
the full value of Amplitude and your data.

de Quick Start Guide

next tab

roperties) on the next tab

user properties not sent with events)

1. Event Groups
Definition:

Use groups to distinguish logical parts of your application. Event groups help
components of your application to instrument and can assist with event nam

No.
Event Group Name
1
2
3
4
5
6
(add more above if needed)

2. Event List

Amplitude Event Name: How the event will appear in Amplitude. Event group
assist with analysis.
Event Description: Explanation of how event is recorded (provide context for
Definitions:Priority: High, Medium, Low
Property type: Event, User
Property name: How the property will appear in Amplitude
Property value(s): Potential values the property can have
Amplitude Event Name
No.
(i.e., group_name - event)
1
2
3
4
5
6
7
8
9
10
11
12
13
14

Event Description

15
(add more above if needed)

n. Event groups help with prioritizing key

ssist with event naming (section below).

GUIDING PRINCIPLES FOR INSTRUMENTATION

1. Think of your application's 'critical user paths'. Each activity within each path should get it
2. All distinct user actions should be new events (i.e., user clicks).
3. Include 'Event Properties' to describe attributes of the same action (i.e., source: facebook,

mplitude. Event group can be added to name

(provide context for team members)

de
e
Priority

Type

Property 1 (optional)
Name

h path should get its own event.

, source: facebook, twitter, etc.).

Tip: Should a property be an 'event' or 'user' property?

Event Properties: are attached to events and reflect the state at which the event was triggere
Use these if you want to better understand characteristics of a given event.

User Properties: are attached to users and reflect the current state of the user. Use these if y
want to segment your users based on these properties. User Properties can be sent with an
event or send via the Identify API (see next tab).

ty 1 (optional)

Property 2 (optional)
Value

Type

at which the event was triggered.

a given event.

state of the user. Use these if you

Properties can be sent with an

Property 2 (optional)
Name

Property 3 (optional)
Value(s)

Type

Property 3 (optional)
Name

Value(s)

Type

Property 4 (optional)
Name

ptional)
Value(s)

Type

Property 5 (optional)
Name

Value(s)

Copy and paste columns S,T,U if you need to add more properties

1. User Properties

User Properties are attached to users and reflect the current state of the user
Definition: to segment your users based on these properties. User Properties can be sen
via the Identify API. Please record all user properties that are sent via the Ide

No.
User Property Name
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
(add more above if needed)

User Property Value(s)

rent state of the user. Use these if you want

Properties can be sent with an event or send
t are sent via the Identify API below.

Description