Why another user event tracker?

Why another user event tracker?

User event trackers allow systems to log UserUser - User-level data, ActionAction - Action taken by a user. For example, when an item is clicked on. (e.g. clicks) and <<glossary:Context> (e.g. the URL) data.

Most available user event logging systems (e.g. Google Analytics, Mixpanel, and Snowplow) are designed for non-programmers to solve product analytic use cases. They are not designed for building and running real-time control systems. Promoted’s Metrics system is designed for this purpose.

Here are some major differences that set Promoted Metrics apart:

  1. Most user event logging systems require contexts to be denormalized onto each event when logging from the client. This is very inefficient and insecure. Promoted supports real-time joining of event log and contexts ( UserUser - User-level data, <<glossary:View (Page View)>> , RequestRequest - A request for a list of content, such as search, feed, or related items. , InsertionInsertion - A response list contains a list of item Insertions. We start with more potential Request Insertions, then narrow down to a subset of Response Insertions to return to the UI. Insertions differ from Impressions because Insertions may not get viewed. , ImpressionImpression - When an item is viewed on a screen long enough to count as an impression. E.g. >50% visible for >1s. ) in our pipeline.

    1. Promoted is more efficient. For complex systems, the contexts grow very large. Most user event logging systems encourage passing contexts to the client side. With Promoted, most of your user event logging data is sent directly from your backends (drastically improving client latencies and cost).

    2. Promoted is more secure. Relying on logging contexts from clients is dangerous. This is less of an issue for other trackers because they are not designed for real-time control systems. When using user events for real-time control systems, hackers can manipulate important data that can have a big impact on recommendations and pricing.

  2. We collect finer log records than most user event logging systems. Clients log events when an item is viewed long enough to count as an impression. This information is critical for building any real-time control system and is often missed with other systems.


What’s Next

How to integrate web events with Promoted metrics

Did this page help you?