Snowplow for retail part 2: what data do I track?
We recommend you you have read the first post in this series before diving into this one to ensure you have all the context you need!
There are also three more posts in this series that you can read next:
- What can we do with data when we’re getting started?
- What can we do with data when we’re growing?
- What can we do with the data when we’re well established?
What do I track?
With Snowplow, you can track entities as well as events.
Great, what events do I track?
The first (and hardest) step is to decide on what events you want to track. Creating a tracking design should start with thinking long and hard about what questions you want to ask of the data. With Snowplow BDP, you can access the Implementation Engineering team who leverage best practices from numerous implementations to help you get this foundation right.
Compared to designing a tracking strategy, implementing the tracking is simple. For instance, for tracking on the web we have a wealth of out of the box tracking that can be set up in minutes using a tool like Google Tag Manager.
For the purposes of this blog post, we will give some examples from what we have seen many clients in the retail sector do.
Some out of the box events you can track are:
- Page views
- Page pings
- Link clicks
You can track an unlimited number of custom events, each with an unlimited number of custom properties with varying data types. Some examples that could be useful are:
- Checkout flow
- Signup/signin flow
Remember, all Snowplow events (custom/out-of-the-box/web/mobile) are tracked with the same 130 properties (when they are available/relevant) collecting data on:
- Timestamp fields
- User identifiers
- Device and platform information
- Location fields
- Webpage information
- Marketing parameters
What are entities, and which ones do I track?
Once you have a list of events you want to track, you can decide on which entities to track. An entity is something that is attached to an event. Each entity describes the environment the event takes place in.
Multiple entities of different, or the same type can be sent with any event. The two main reasons to use an entity are as follows:
- You want to send multiple of the same entity with an event. For example, with a search event, you want to send multiple search result entities, one for each search result displayed. Each search result entity can have rich information about that search result such as order, name, vendor, price.
- You want to send the same custom information with many events. To standardize how this custom data is captured, you can create one entity and send this will many event types. For example, to know whether a user is a subscriber or not is useful with many events so this can be sent in a user entity with all events.
Some example entities often used by retailers are:
Read part 3 next: What can we do with data when we’re getting started?