About Tagyard

A page to check, not to believe.

You are considering putting your measurement setup — or your clients’ — with Tagyard. Then you want to know who is behind it, where your data sits, and what happens if it ceases to exist. It is below, without talking around it.

01Why this exists

Tagyard was built because per-container pricing did not work out for someone managing tracking on behalf of others.

It was made for our own work first: hosting server-side containers for clients, without a separate contract per client, and with a screen that says in plain language whether it measures. Once that worked, it was offered to others.

That is the whole origin story: no founding myth, no mission thought up afterwards. Tagyard has been running since 2025, the first year only for our own clients. That it has only recently been for sale does not mean it has only recently worked.

02Who makes it

Silvan

Maker of Tagyard

I build and run Tagyard myself. Before that I set up server-side tagging and measurement setups for agencies and web shops — the kind of work where you sit in a traffic log in the evening working out why one in ten measurements falls away.

If something goes wrong, you speak to me. Not to a ticket number.

Directly: [email protected]

03How small it is

Small, and that is the point.

People

1the maker, no team

Running since

2025the first year for our own work

If we stop

3 monotice, plus an export

What that means for you

  • You speak to the person who built it, and who knows what happens at your measurement address.
  • Decisions are quick, because there is no layer in between.
  • What changes, you hear from the same person.

What it explicitly is not

  • No round-the-clock staffing.
  • No support department with a queue.
  • No promise a large company can make and I cannot.

To be clear about scale: Stape reports more than 200,000 customers and TAGGRS more than 15,000. Tagyard is no competitor to that in size and does not pretend to be. The difference is the point: one point of contact who knows your measurement address, instead of a number in a large system.

04Where the data sits

The measurement servers run on European infrastructure, with Hetzner in Germany or Finland. There is no transfer outside the EU. Which of the two your measurement server uses is stated in your data processing agreement.

Hetzner · GermanyHetzner · Finland

The data processing agreement and the sub-processor list

05If we stop

Leaving works without us.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

That is the whole list. No penalty clause, no export fee, and no conversation you have to have with us first. If we stop, you hear it three months in advance and you get an export of your configuration.

06Company details

The colophon, to copy out.

Company
Piex Commerce
Product
Tagyard
Address
Frans Halsstraat 19, 2162 CK Lisse
Country
The Netherlands
Chamber of Commerce
93463480
VAT
NL005021587B30
Email
[email protected]

07Contact

One email address.

[email protected]

You get an answer from a person. If you have a technical question, include your measurement address — then the traffic log can be pulled up before anyone writes back.