Skip to main content

Server-side GTM and the Meta Conversions API · Part 1: Server-side GTM, from zero

Chapter 4.2 · 2 of 22 · 3 min

Stape, Pixelfly and Traggers: three routes, with prices and limits

Who runs the server container? There are three answers, and all three are valid.

Free to read

Who runs the server container? There are three answers, and all three are valid. Which one you pick depends on the client's event volume and on your own time.

Managed hosting: Stape and similar providers

Stape is the best-known name. You open an account, give them the container ID, and they give you an endpoint. Add a CNAME record in DNS and it becomes your own subdomain. Pixelfly and Traggers do the same job at different prices, and all three run the same Docker image. Pricing is based on request volume, and for client work it sits in the range of 20 to 100 dollars a month.

I am not writing down exact figures, because every provider changes its plans at least once a year, and quoting from old numbers would have you give the client the wrong price.

Screenshot: the pricing page of the provider you chose, showing the monthly request limit and price side by side

Self-hosting

A VPS, Docker, the image, and a reverse proxy in front. For 4 to 6 dollars a month you get a machine with 2 vCPU and 4 GB RAM, and that handles all the traffic of a mid-sized store. The cheapest option, and the most work: when the server goes down, your phone rings. The full steps are in 4.5.

Google Cloud Run

Google's own route: when you click Automatically provision tagging server in GTM, it creates a service in your Google Cloud account. Scaling is automatic, but if you keep the minimum instances at zero you get cold starts and lose events, and if you set one or more it costs 20 to 120 dollars a month. Cold starts are the whole subject of 4.7.

Steps

  1. Decide whether you are taking managed hosting for learning or going straight to a VPS.
  2. If managed, open an account, choose the lowest plan, and enter the server container ID.
  3. Note down the endpoint the provider gives you, and open it in a browser with /healthz added to the end. You should get a blank white page that says ok.
  4. If you choose a VPS, for now only get the machine and confirm you can log in over SSH. The rest is in 4.5.
  5. On a sheet of paper write three costs: the monthly price of the route you chose, what you will charge the client, and your one-off setup fee.

What not to do

  • Do not tell a client that server-side tracking runs for free. If you do not say this at the start, then when the provider's bill arrives three months later the client will think you hid it. In my first proposal I put hosting on its own line and state that it is not my fee.
  • Do not run a client's site on a free plan. When the request limit runs out, the container quietly stops answering requests, and you will not know until someone looks at a report and says the numbers have dropped.
  • Do not settle for memorizing three provider names. This list will change within five years. What will not change is the Docker image and the Client-Tag architecture.

Proof

You have a working server endpoint whose /healthz path shows ok. And on paper you have three numbers: the monthly hosting cost, your monthly price to the client, and the setup fee.

Want the full chapter list, or to jump to another chapter?

All chapters in the book