-
Notifications
You must be signed in to change notification settings - Fork 0
Analytics Guide
All aspects of the Try.com experience are exposed, so you can feed them to whichever BI/analytics tools you already use. This allows you the deepest level of integration, providing you ultimate flexibility as if you owned the Try.com codebase in house.
It is important to understand that some events are triggered on the customer's browser/app (frontend), and some are triggered on the server-side. These events are always mutually exclusive, we never send the same event from both the frontend and server-side.
For example, the frontend is responsible for capturing events like register.via_email.viewed to signify that the email registration page was presented to the user. However, user.registered is a server-side concept, so that is a server-side event.
We use dot notation to help analysts make sense of the huge amount of events we expose across all our apps, products and platforms.
There may be some exceptions, but normally, we aim to use the following naming strategy:
[feature].[entity.heirarchy].[optional_modifier].[action]
The important thing is that events always end in a verb in past tense. A feature is a major subcomponent of the Try.com ecosystem, for example, try_button, express_checkout, risk, merchant_portal, consumer_portal. Sometimes it doesn't make sense to include a feature, especially for server-side events.
In terms of English grammar, this usually means:
[noun].[noun].[optional adjective].[verb (past tense)]
// If you are using the Express Checkout product, when the user is presented with the Facebook Connect registration page, the following event gets fired from our Javascript SDK.
express_checkout.user.register.via_facebook.viewed
These events can be consumed by merchants via webhook. You are able to register your server-side analytics callback endpoint via the Merchant Portal.
- Full list of server-side events (coming soon)
If there is an event you would like us to expose, let us know at engineering@try.com and we can probably enable it pretty quickly.
These events can be consumed by merchants via our frontend SDKs (Javascript, iOS, Android).