<aside> 💡 Use this template to define your Segment Data Tracking Plan.

With it a marketing or product manager can clearly, consistently, and easily define all events, identify, and group calls required to make your Segment instance useful and help you fulfill your analytics goals.

It includes instructions for creating your plan, pre-defined calls common to most use-cases, and recommendations for maximizing the value of your Segment instance.

The template helps you: 1. clearly define where tracking calls should happen and in what order 2. enforce consistent names for events, properties and traits 3. provide code examples to developers

After creating the tracking plan, you or your developers will be able to quickly implement the plan and start deriving insights from your data.

It will also serve as clear documentation of your analytics setup that you can easily update or share with others.

</aside>

This is the Segment analytics tracking plan for all our sites. Everything to do with our Segment analytics tracking is defined here.

Need help creating your Tracking Plan? Get in touch.

https://indify.co/widgets/live/button/QF0CPplqCJdiAq87Mc3W

Instructions

https://youtu.be/mUAF-7z-t8s

Goals

<aside> 1️⃣ The point of analytics is to help us derive insights from data. Put the goals of your Segment tracking plan at the top so you don’t forget them.

</aside>

1. Track web-analytics in our own data warehouse to see customer lifetime value by original traffic source, improving our ad-spend.
2. Send accurate, consistent data to all of our marketing tools like Facebook and Google Ads to improve conversion rates.
3. Track key-product engagement event to understand where our users struggle and how to improve the product.

Info

<aside> 2️⃣ Update the link with your Segment workspace, add your Segment sources, and define a naming convention.

</aside>

🔗  Segment Workspace

Sources

Naming Convention

Tracking Events

Events are how we record any actions our users or visitors perform, along with any properties that describe the action. Hover over the Name of an event and click OPEN to see its details. Go to the Events table directly to add and update events.

<aside> 3️⃣ Defining events is the bulk of the work in creating a tracking plan. When defining events, think about the actual thing that needs to be tracked like the user signed up instead of the user clicked the sign up button.

We’ve pre-defined recommended events for different use-cases like B2B SaaS apps and ecommerce stores.

Use the Specs column in the Events table to quickly remove events that aren’t relevant to your use-case. See the Specs table for details about each use-case.

</aside>

Events