Can our developers manage GTM without a setup engagement?
Yes. Your team can configure GTM independently and retain publishing responsibility. Our implementation help is optional and paid separately.
What should a tagging brief contain?
List the web or app containers, events, data destinations and required permissions. Explain which technical tasks you want our team to deliver.
Who approves and publishes container changes?
Agree on access, review and publishing responsibilities before work begins. These remain with your team unless a different implementation scope is commissioned.
Can we ask for help with an existing container?
Describe the current container and the specific changes required. Implementation is scoped against the actual work; access does not imply a complete rebuild.
Should we define events before adding tags?
Yes. Document the actions that matter and where the data needs to go. This gives the technical brief clear requirements and ownership.
Does GTM setup automatically include Analytics configuration?
No. Include any Analytics requirements explicitly so the event, tagging and reporting tasks can be scoped together without assuming they are all included.
How is implementation priced?
Pricing is provided on request for the agreed tasks, containers and requirements. Any product license or usage fees, where applicable, are confirmed separately.
What is the boundary between support and implementation?
Standard support does not include a full tagging rebuild. Configuration, event implementation and additional technical changes are separately scoped paid work.