Welcome to Your Amplitude Community

Self-serve analytics is the goal for many data teams. But Saish Redkar, Senior Product Manager at DataRobot, cautions that “Without proper data governance self serve product analytics is a myth.” Explaining that, “Anything which keeps your data more organized and data quality consistent, be it any tools or processes comes under data governance. But not everyone is willing to take the data governance first approach in their implementations. So teams are always looking to get to their MVP of event tracking and create dashboards for their stakeholders ASAP. And it's tempting to roll out data governance on the fly, but the earlier you implement it, the richer the rewards it will give you.” This is a snippet from 7 Lessons from 7 Years using Amplitude in which Saish shares his insights from using Amplitude and from leading over 1300 discussions on data governance and product analytics on the forum. Related Tips: What is Data Governance? Insights Are Only As Good As Your Schema and Instrumentation Getting Started Improving Data Quality with Collaboration

Changing your event naming convention can be a lot of work. But according to Thora Gudfinnsdottir, Product at Avo, “It is usually worth it if you have a really messy, confusing taxonomy, or the traffic plan is really difficult to understand.” But how do you go about migrating successfully? Thora says: “Start with a few events and a few properties that are important to you, and then gradually migrate to a better naming convention. You need to do it both on the taxonomy side and the implementation side. So it is a collaboration between different parts of the organization. And get reviews to make sure everything that you are doing makes sense. And of course, first, commit to and document what naming convention you are migrating to.” This is a snippet from Tracking Plan Tips: Event and Property Recommendations an Office Hours session with Thora Gudfinnsdottir and Anuj Sharma, discussing data design, data governance, and tracking plan best practices. Related Tips: To Track What Matters: Start with Why Generic Vs. Specific Events 4 Elements of a Good Event Name

Amplitude comes with many different chart types and ways to analyze data, but that doesn’t mean you need to use them all. Saish Redkar, Senior Product Manager at DataRobot, has found that “80 percent of your product insights will be always derived from 20 percent of the chart types.” But you shouldn’t feel pressure to use them all at any one time. “Sometimes I have seen that users try to force and extract insights from so many different chart types, but end up not having the best of experience. And that is totally acceptable - it's okay to not leverage all the charts out there in Amplitude.” This is a snippet from 7 Lessons from 7 Years using Amplitude in which Saish shares his insights from using Amplitude and from leading over 1300 discussions on data governance and product analytics on the forum. Related Tips: Insights Are Only As Good As Your Schema and Instrumentation Event Tracking is Not Product Analytics 3 Ingredients to Data Governance Success