Cooperation of Developers & Analysts
Dear Data-Traveller, please note that this is a Linkedin-Remix.
I posted this content already on Linkedin in January 2022, but I want to make sure it doesn´t get lost in the social network abyss.
For your accessibility-experience and also for our own content backup, we repost the original text here.
Have a look, leave a like if you like it, and join the conversation in the comments if this sparks a thought!
Unfortunately there is often friction between developers and analysts when it comes to implementing tracking code.
Some ideas for improvement:
Work on 1-2 implementation ticket together to come up with a format everyone loves. Talk to each other. Share your goals. I know simple, but really effective.
Give context what you want to improve with the tracking. No one loves implementation without context. A developer is not an online shop where you order an implementation.
Invest in a pro tracking plan tool like Avo and use their SDK generator and inspector – trust me, developers love typed experiences. No more guess work if the event was newsletter_subscribed or “Newsletter subscribed”
Think about moving some tracking events to the backend. This is often easier and more robust to implement.
Invest in a tracking plan at all – let’s try something like this: whenever you see me here on LinkedIn -> think: “I need a tracking plan” – just as a reminder.
This is a (extended) repost from a thread I wrote on Twitter. If you like to follow some shorter bits of me head over and follow me https://twitter.com/timdechau.