Explore actual events

You can explore events as they arrive in Amplitude or Vero. This can be a very powerful tool to look at actual user data as it comes in, and it is the best way to start configuring campaigns.

Name normalization

For legacy reasons, naming conventions of events differ based on where the event is generated. E.g. Amplitude events generated directly from the apps will use _ as a separator between the words without classifying a subsystem/category the event belongs to, e.g. add_series_to_bookshelf. The core API instead uses a classification part of event names, which is separated from the rest by ., e.g. credential.verification_failed (credential is the category, verification_failed is the event name).

In external systems such as Vero and Amplitude, the separator between category and event name is translated from . to _. Some event names may therefore not correspond exactly. These events will be marked in their description using this callout:

<aside> <img src="/icons/translate_blue.svg" alt="/icons/translate_blue.svg" width="40px" /> This event name is normalized in external services. See our note on Name normalization.

</aside>

Flow of events

Events flow in multiple directions, and here is a simplified overview:

graph LR
  subgraph Beat
    API
    Apps
    Web
  end
  Web
  Vero
  Amplitude
  Stripe
  OneSignal --> Apps

  Stripe --> API
  API --> Vero
  API --> Amplitude
  Apps --> Amplitude
  Web --> Stripe
  Web --> API
  Amplitude -.-> OneSignal