## Metadata - Author: [[amplitude|Amplitude]] - Full Title:: Common Event Tracking Pitfalls and How to Avoid Them - Category:: #🗞️Articles - Document Tags:: [[Tracking plan|Tracking Plan]] - URL:: https://amplitude.com/blog/event-tracking-pitfalls#event-properties - Finished date:: [[2023-12-26]] ## Highlights > **Tip:** We recommend that your tracking plan should contain anywhere between 10 to 200 event types. Obviously complex multi-products might have a need for more, but we often see that companies can greatly slim down their data model by tidying up their event types. ([View Highlight](https://read.readwise.io/read/01hjhgcc8gqtw8z5ksc32ga5v6)) > **Tip:** Best practice is to treat your tracking like any other code and test it. Extend your QA to include event tracking as a part of your existing CI/CD and unit testing workflows. ([View Highlight](https://read.readwise.io/read/01hjhgdaqfrgw7e227va6p9yxt)) > **Tip:** Use a framework like Object Action as a best practice for governing the structure of your events (i.e. each event is associated with an Object in your application (e.g. Button) and an Action (e.g. Clicked). And use a system like Amplitude to enforce your naming convention across teams and during instrumentation ([View Highlight](https://read.readwise.io/read/01hjhgdhx37307y9kdffa5bz55))