There are a lot of cons when mixing development data with production data. In flux event and property names as well as values can clutter your production project. Combine that with the number of developers adding tracking logic trying to keep your data clean just doesn’t scale. Development is like writing a draft it will take several iterations to get your data to look correct. Production should always be final result. I can’t think of a Pro here other than not having to manage a dev key versus a prod key. I recommend always having a separate project for development and recommend each developer having their own project on their account. I will say there is a difference with tracking ineternal data in production. I would recommend tracking internal staff users just like any other user with your application. As long as you have a strategy to flag internal vs external to target just your client data. The benefit of tracking all production data is that you will be aware of all factors affecting your application.
Did you miss the live Webinar?
Join Corinne Pellows, Sr. User Success Lead at PatientPing, as she shares how her team uses data and messaging to create better customer experiences.