We built the tool we wanted.
We set up and run tracking for lots of client sites. We kept finding broken tags too late. So we built a fix.
Broken tracking cost us too much
Here is a story we lived more than once.
Someone makes a small change in a client's container. The site looks fine. No one says a word.
Two weeks later, the client calls. Their leads are down in the reports. Did the ads stop working?
No. A tag stopped firing. We lost two weeks of data we could never get back. And we lost some trust, too.
Google Tag Manager is a great tool. But it does not warn you when a change breaks things.
So we made TagStrike
We wanted to know the moment something changed. We wanted to know what changed, in plain words.
We wanted a test that acts like a real visitor. And we wanted a quick way back when a change goes wrong.
That is what TagStrike does. You can read about each part on the features page.
A few rules we stick to
You stay in charge
We never make a change live on our own. A person on your team always clicks to confirm.
Plain words
Alerts should make sense to anyone on the team. Not just the one person who set up the tags.
Ask for little
We ask for each kind of access only when you turn on a feature that needs it.
Be honest
If we can't do something, we say so. For example, Google Tag Manager does not tell us who published.
We are in beta
That means we are still testing and fixing things. It is free while we do.
We read every note you send. Tell us what works, what breaks and what you wish it did. Write to jake@citamark.com.
Try it on your own containers
Sign in with Google, pick a container and connect Slack. You will hear about the next publish.