Managing Tag Communication between Analytics and Software team
I currently sit on an Analytics team and decide which items to tag as new configurations and features roll out in our app/website. After this decision is made, software engineers create and embed the tags in the app. My question concerns best practices for managing and communicating the "tag schema" that is passed from the Analytics team to the Software Engineers.
I currently put all the requirements in a Google Sheet, but it's becoming unwieldly. What are some best practices/tools for managing the "tag schema" (version control, etc.) and effectively communicating it (maybe some collapsible menus or something easily navigable) to Software engineers? Thanks for your thoughts!
Re: Managing Tag Communication between Analytics and Software team
Re: Managing Tag Communication between Analytics and Software team[ Edited ]
April 2016 - last edited April 2016
A spreadsheet (Excel/Google Sheet) is likely your best solution for now. You could try splitting up the tagging by different tag types (analytics, remarketing, etc) or by different website sections. Also, you could ask if your software developers have a issue/ticket tracking solution in place (JIRA, etc). You could then use that as a way to stay on top of change requests/updates/additions/etc.
As Theo mentions, migrating your tagging from on-page to a tag management system will ease a lot of this back and forth communication with your software developers. There are a number of solutions in the marketplace, but Google Tag Manager (GTM) is free and honestly pretty amazing.