- A server container is a programmable pipe for events. You can use it for alerts, file proxying, refunds, A/B assignment, geo rules and warehouse loading.
- Each use is a small tag or client, but each adds a dependency and a privacy question.
- Start with one, document it and monitor it.
The headline use of a server container is sending conversions to ad platforms. Once the pipe exists, other uses appear. This page lists ten that are practical and a little unusual, with a caution for each. They build on server-side tagging use cases and webhook servers.
| Idea | How | Caution |
|---|---|---|
| Slack or e-mail alert for a big order | An HTTP request tag on purchase events above a value | Do not include personal data in the message. See Slack and server GTM recipes |
| Serve a third-party script from your domain | File Proxy (every Open Tracked plan) serves a pixel script, font or image from your tagging address | Respect the vendor's licence and cache rules |
| Refund and cancellation events | A webhook from the shop becomes a refund event in GA4 and an adjustment in Google Ads | Use the original order ID. See conversion adjustments |
| Server-side A/B assignment | Assign a variant in the container and set a cookie | Keep assignment stable. See server-side A/B testing |
| Geo-aware rules | Use the country from CDN headers (Visitor Location) to change tags by region | Do not use location for sensitive decisions |
| Forward events to BigQuery | A BigQuery tag with the Google Service Account power-up (Pro) | Plan costs and retention |
| Delay a webhook for deduplication | Request Delay (Business) holds requests for minutes | Keep within platform windows |
| Block abusive IPs | Block Request by IP (Business) | Review the list regularly |
| Check for bot traffic | Bot Detection header | It only catches self-identifying bots |
| Send a daily summary of events | Write counts to a store and report them | Do not over-engineer |
A cautionary pattern
Each extra use makes the container more important and more fragile. Treat it like production software: name an owner, write down what each tag does, monitor errors and keep a backup export. A container that quietly runs ten unrelated jobs is a source of outages and privacy surprises.
Ask Ari instead of digging through reports
Ari reads your tracking and ad data and answers in plain words.
Start small
Pick one idea that solves a real problem
Not the cleverest one.
Build it in a test workspace
And test with a test event.
Document it
A line in the container notes.
Monitor it
An alert or a regular check.
Connected in minutes
Add your domain, install the pixel, connect your ad platforms and watch the first events land.
A realistic example
A small agency wants to know quickly when a client's checkout breaks. It adds a tag in the client's server container that counts purchases per hour and posts an alert to the agency's chat if there are none for three hours during opening times. The tag uses a small store for the counts and a simple condition. The first alert fires on a Sunday: a payment provider change had broken the thank-you redirect. The client fixes it within the hour. The idea was not clever, and it paid for itself the first time it fired. Most good uses of a container are like this: small, specific and tied to a real failure that someone once had.
Orders from your store, back to the ad that earned them
Your store sends the order once. Open Tracked passes it on to each ad platform, cleaned and deduplicated.
Frequently asked questions
What else can I do with a server container?
Send alerts, proxy files, handle refunds, assign A/B variants, use geo rules and load data into a warehouse.
Is it safe to add many uses?
Each use adds a dependency. Document, monitor and keep it small.
Can I proxy third-party scripts?
With File Proxy, yes, respecting vendor terms.
Do these need paid plans?
Some need Pro or Business, such as BigQuery access, Request Delay and IP blocking.
Where do I start?
With one idea that solves a real problem and a test workspace.
Do I need spreadsheets to read my results?
No. Once tracking is live, the Open Tracked analytics shows spend, revenue, ROAS and profit, and you can ask Ari, the built-in AI assistant, questions about your own numbers in plain words. Ari's allowance depends on your analytics plan.
Is Open Tracked different from Open Track or Open Space Track?
No. Open Tracked is the official name of our server-side tracking platform, and the website is opentracked.io. Many people search for it as Open Track, OpenTrack or Open Space Track. All of them lead to the same product: server-side Google Tag Manager hosting, first-party analytics and a CRM pipeline.
Fix your tracking at the source
Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.
The Open Tracked team
We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?
Comments
Loading comments...
Blog · 4 min read
