The marketing site
Page views, clicks, and scroll depth come from the web container. The site only loads the container script. It does not invent its own events.
Server-side tagging
A lane for your events, on a hostname you own.
Wendlane hosts the Google server container. Your site and your backend both send to a name on your domain, such as data.yourstore.com.
How it works
01
Create the container
In Google Tag Manager, provision a server container. Paste that config into Wendlane. The container runs on our host, under a name we give it.
02
Point your name at it
Add a hostname on your own domain and CNAME it to the container. Visitors and your server call that name, not a vendor domain.
03
Send from both sides
The web container uses that hostname as its server URL. Your backend posts to the same hostname. Google Tag Manager still decides where each event goes.
The name stays yours
A tagging hostname on your registrable domain is first-party. The browser loads the container script from that host, and collect requests go there too. You choose the label. Wendlane uses data.wendlane.com for its own site.
The slug host Wendlane assigns is only the CNAME target. You do not put it in the web container. After the CNAME verifies, that custom hostname is the address you publish.
Google Tag Manager stays in charge
Wendlane does not replace your tags. The server container still has the clients and tags you publish in Google Tag Manager. A page view from the website and a sign-up from your application can arrive at the same container, then fan out to the tools you already use.
Preview still works. A published container is what forwards ordinary hits onward. When you are testing, the server container preview shows the request, and GA4 DebugView shows the event once the tag and measurement id match.
What you run it for
The application
Registration, login, and other server actions never appear in the browser’s network panel. The application posts them to the same hostname the website uses.
A store
Orders, refunds, and other events that happen outside the browser take the same path. The container sees them because your server sent them, not because a pixel happened to load.
More than one container
Each container has its own hostname. A paid plan can add a custom domain on top of that hostname, which is the name you give to customers and to your own code.
Start with one container
Open the app, create a container, and point a hostname at it. The rest is the Google Tag Manager setup you already know, aimed at your domain.