Defining data collection/tracking contracts in config files as code
Dear Data-Traveller, please note that this is a Linkedin-Remix.
I posted this content already on Linkedin in February 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!
Link to original post on LinkedIn
Plain text
Poll time:
When you could do “tracking plans as code” in which kind of definition/markup language would you like to do it?
Background – I am tinkering a bit with a concept of defining data collection/tracking contracts in config files as code.
Based on that I can do multiple crazy things:
– build a tracking plan in Avo
– create schema definitions for Snowplow
– create documentation in data catalogues
– and I am pretty sure a lot more.
I am just thinking what would be the best language to create these files. I tend a bit to YAML. But maybe JSON is better (open api uses JSON). I need your opinions.
The poll with results:
