Boolean properties are good: True or false? According to Thora Gudfinnsdottir, Product at Avo, they’re best avoided. “If anyone ever creates a boolean property in our tracking plan, I will not be happy. Maybe even mad.”
Here’s why:
“When you start a product you maybe only have one authentication method and that's email and then you don't need a property for which method it is. Then you add facebook and then you add the property used facebook: true or false. And then you add google and then you have to add used google. And then you add github and then you have to add used github. So this doesn't scale. Then you have so many properties that are describing the same thing.”
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.
