Server side and monitoring
Introduction
Server-side for GTM and Adobe Launch is a big deal for enterprises. It reduces the dependancy on third party tags and instead progresses companies into a first party landscape, where data can be processed effectively on their own servers before even being sent out to 3rd parties such as Google and Facebook.
However server-side architecture also comes with a large infrastructure overhead. At present there are two options when setting up server-side, either an automatic or a manual. The automated method will setup app engine infrastructure which is really handy, and great to get started with.
At large scale we believe companies will opt for a kubernetes approach, which comes with the advantage of being able to select infrastructure. This means companies can gain the benefit of volume discounts by purchasing upfront and sustained usage discounts.
Why monitor on server-side?
At present, on a server-side implementation the tags which need to be implemented are also more custom in nature, requiring more custom scripting.
We figured at Monita, if there is going to be more custom code, there would also be a higher chance of this code not operating as expected (hence the need for governance and constant monitoring.)
How can Monita be implemented server-side?
This can be done leveraging the Google APIs. Thankfully our architecture is already prepared for this scenario and we will be making slight modifications.
At present we use a Tag Template, however this will need to be updated to accomodate.
We also will need to add a client template (something Google has not yet supported yet see below)
Comments
Post a Comment