Implementation guidelines

These rules keep new analytics events consistent with the rest of the tracking plan.

When to fire events

• Page/screen view events fire after the page has fully loaded.
• User interaction events fire immediately after the interaction occurs.
• Conversion events fire after the server confirms the action.

Testing and validation

Validate every new event with:

1. The Segment Debugger.
2. The destination platform's debug mode (e.g. GA Debug Mode, or Amplitude's Data > Event Stream).

Event property best practices

• Properties use snake_case. Poll events are the one exception; they use camelCase.
• Boolean properties use an is prefix (e.g. is_active).
• Arrays are plural nouns (e.g. organizations).
• Currency values are always floats, with a separate currency property.
• Include the default custom properties on every event.

Related pages

• Analytics tracking plan
• Change management