For agencies
Nothing comes back on you.
Tagyard runs your client’s server-side Tag Manager on their own subdomain, with the certificate and the traffic log included. The account is in your client’s name — unlike Stape, where the container belongs to whoever created it, and that is usually the agency.
02 · The split
Who owns what.
The account belongs to your client. The measurement server hangs off it. You are invited to administer that server.
Account
Your client creates it and owns it. They pay, and they are the only one who sees the invoices.
hangs off the account
Measurement server
The tagging and preview servers run on your client’s subdomain. One server, one subscription.
Agency
You get administrator rights on the measurement server. You work in it fully — by invitation, not as the owner.
You front nothing
Your client attaches their own payment details. No amount ever lands on your account.
Nothing keeps running
If the client leaves, their subscription stops. You are left with no contract and no cost to cancel.
No contract per client
You sign nothing per client. Every measurement server stands on its own, in the name of the client it belongs to.
And so, deliberately, not
Two things sit with the client, and only with the client.
That is not a restriction we impose on you. It is the same arrangement that means you front nothing and are left with nothing.
- You cannot reach the invoices
- You cannot change the plan
03 · Setting up
The first quarter of an hour.
Four steps to put one client on it. Who does which is written next to it — it starts with your client, and you do the technical part.
- Client
Creates an account and one measurement server~3 min
Your client registers in their own name and sets up one measurement server on their subdomain.
- Client
Invites you as an administrator
One invitation with your email address. From that moment you work in the measurement server in full.
- Agency
Measurement address, DNS record, checking that it measures
You set the measurement address, point the CNAME record and check on screen that the measurements arrive.
- Client
Payment details, when the trial ends
Only once the fourteen days are up does your client attach their payment details. Not before.
Hi [client name], For your server-side tagging I would like to set this up at Tagyard. Two small things at your end: 1. Create an account at tagyard.io and set up one measurement server there (~3 min). 2. Invite me as an administrator at: [your email address] The rest — measurement address, DNS and checking that it measures — is on me. You only attach payment details once the fourteen-day trial ends. Thanks,
Fill in two fields, forward it. Nothing else to explain.
04 · Looking it up
When a client calls to say the numbers are off.
Three screens you open yourself: the verdict, the traffic log and the Tag Manager check. Enough to see where it goes wrong, without having to call back to say you are looking into it.
The verdict
Not everything is arriving
1 in 12 measurements does not arrive
Measurement server responds
Security active
8% does not arrive
The traffic log
| Time | Path | Code | ms |
|---|---|---|---|
| 14:02:11 | /g/collect?v=2 | 200 | 41 |
| 14:02:11 | /mp/collect | 200 | 38 |
| 14:02:12 | /g/collect?v=2 | 502 | — |
| 14:02:12 | /gtm.js | 200 | 12 |
| 14:02:13 | /mp/collect | 200 | 44 |
| 14:02:14 | /g/collect?v=2 | 502 | — |
| 14:02:15 | /g/collect?v=2 | 200 | 39 |
| 14:02:16 | /mp/collect | 200 | 40 |
The Tag Manager check
Within the same minute you can see it is the 502s on /g/collect and not the Tag Manager. That saves your client a day of waiting, and you a riddle.
Sample traffic — this is what the screens look like, with your own measurement server’s numbers in them.
05 · Paperwork
What you have your client sign.
New clients ask for a data processing agreement and a list of sub-processors as a matter of course. They are here, and your client signs nothing for them: they apply as soon as an account is created.
06 · The honest part
And if we stop.
A fair question to ask before you put twenty clients with us. So here is the answer, without talking around it.
The containers are Google’s own images
The sGTM containers run on Google’s standard images. There is no Tagyard-specific construction in them that you cannot get elsewhere.
The configuration lives in your client’s Tag Manager
Your measurement plan, your tags and your triggers are in the client’s own Google Tag Manager, not with us. We do not touch it.
The measurement address is a CNAME you move yourself
The measurement address is a CNAME record in your client’s DNS. To move to another party, you repoint that record and set it up there — an hour’s work, and it can be done without us.
What your client does lose is their history
The traffic log built up with us does not travel along. Your tracking moves in an hour; your graphs do not.
And if it comes to that, you hear it three months ahead
If Tagyard stops, you get three months’ notice and an export of your configuration. That is a commitment that costs nothing as long as it is true — and a sentence you can pass on to your client.
That is the whole list. No penalty clause, no export fee, no conversation you have to have with us first.
07 · Price
What it costs, and who pays.
Three plans, per measurement server, paid by your client. All excluding VAT.
€9.99/ mo
Up to 500K requests per month
Two months free: € 19.98
€44.99/ mo
Up to 5M requests per month
Two months free: € 89.98
€84.99/ mo
Up to 20M requests per month
Two months free: € 169.98
There is no agency discount and no margin in between. Your client pays the price listed on the pricing page, and you earn nothing on it. That is not a confession but a selling point: your client can see that your advice was not bought.
One billing interval per account, and the user limit applies per account — your colleagues count towards your client’s allowance.
Put one client on it
The email from step 3 is ready to forward. You do not need much more than that to start.