dataMonitorio sends checkout events, including every purchase, to a server-side Google Tag Manager container that you own. Where that container lives makes a real difference to how much data reaches your ad platforms. This guide explains our recommended setup and walks you through it.
The short version
You can start on a free hosting plan with the address your host gives you, and dataMonitorio will work. For the best results we recommend a subdomain of your store (such as sgtm.yourstore.com) on a paid plan. Any host that runs a GTM server container works; we recommend Stape because it is affordable and quick to set up.
Your three options
Here is an honest comparison, so you can pick what fits your store and budget today and upgrade later.
| Setup | Works with dataMonitorio? | What to know |
|---|---|---|
Free plan + your host's address (e.g. abcd1234.stape.io) | Yes. Good for setting up and testing. | Cookies are set from your host's domain, so browsers like Safari treat them as third-party and expire them sooner. More requests are blocked by ad blockers. The free plan's monthly limit applies (see below). |
Free plan + your own subdomain (e.g. sgtm.yourstore.com) | Yes. You get first-party tracking. | Custom subdomains are available on Stape's free plan too, so you get the first-party benefits at no cost. The monthly limit still applies, so watch your usage as you grow. |
| Paid plan + your own subdomain | Yes. This is our recommendation. | First-party tracking with room for your traffic, plus extra tools on paid plans, such as request logs and Cookie Keeper on Stape. |
Why your own subdomain matters
When you first create a server container, it gets an address on your host's domain, for example abcd1234.stape.io. dataMonitorio works with that address, but every request then goes to a domain that has nothing to do with your store. Moving the container to a subdomain of your store changes three things:
- Cookies become first-party. Your server container sets cookies from your own domain. Browsers such as Safari limit the lifetime of cookies set by scripts or by other domains, but treat these as your site's own cookies, so returning customers are recognised for longer and conversions are credited correctly.
- Fewer requests are blocked. Ad blockers and privacy tools keep lists of shared tracking domains. A request to your own subdomain is far less likely to be stopped than one to a hosting provider's domain.
- GTM can load from your domain too. With “Load GTM from your own domain” in dataMonitorio, the GTM script itself loads from your subdomain, with Google as the automatic fallback.
Free plan or paid plan?
A free plan is a perfectly good way to get started. Every page view and event from your storefront and checkout counts as a request to your server container, and free plans include a limited monthly allowance: on Stape it is 10,000 requests a month at the time of writing. That covers testing and a very small store, but a store with a few thousand visits a month can use it up.
When the allowance runs out, the container stops accepting data until the next month starts. Purchases then quietly stop reaching your ad platforms, often at your busiest time.
- Starting on the free plan? Set up your own subdomain anyway: it works on Stape's free plan and gives you first-party tracking from day one.
- Check your usage in your host's dashboard, and upgrade before you reach the limit.
- On a paid plan, choose an allowance that covers your traffic with room to spare, then check your usage after the first month and adjust.
Before you start
- A server container that is already running (see Set up your server container with Stape).
- Access to the place where your domain's DNS is managed: your Shopify admin if you bought the domain through Shopify, otherwise your domain provider or Cloudflare.
- About 15 minutes of work, plus waiting time while DNS updates.
Using a host other than Stape?
The steps are the same in principle: add the subdomain in your host's dashboard, create the DNS record it gives you, wait until it is verified, then update GTM and dataMonitorio. Follow your host's screens for steps 2 and 4.
Step 1: Choose a subdomain
Pick a short subdomain of the domain your customers see in their browser, not your myshopify.com address. If your store is yourstore.com, good choices are data.yourstore.com, sgtm.yourstore.com or m.yourstore.com.
Avoid words that blockers look for, such as gtm, analytics, tracking, ads or your host's name. The subdomain must not already be in use.
Step 2: Add the subdomain to your server container
- Open your container. In Stape, open the container you use for dataMonitorio.
- Add a domain. Find the Domains section (it may be labelled Tagging Server URLs) and add a new domain. Enter the full subdomain, for example
data.yourstore.com. - Keep the CDN off for now. You can add it later. It is not needed for first-party tracking.
- Choose how to connect. If Stape offers to connect automatically to your DNS provider, you can use that and skip to step 4. Otherwise choose to add the records yourself. Stape then shows the DNS record to create, usually a CNAME record with a name and a target value. Keep this page open.
Step 3: Add the DNS record
Create the record exactly as your host shows it. Where you do this depends on who manages your domain.
If your domain is managed by Shopify
- Open your domain settings. In your Shopify admin, go to Settings → Domains and click your main domain.
- Open the DNS settings. Choose the option to edit DNS settings for that domain.
- Add a custom record. Choose CNAME, enter the name (for example just
data) and paste the target value from your host. Save.
Don't use “Add subdomain” in Shopify
That option points the subdomain at your Shopify store. Your server container needs its own CNAME record instead.
If your domain uses Cloudflare
In Cloudflare, open your domain, go to DNS → Records and add a CNAME record with the name and target from your host. Set the proxy status to DNS only (grey cloud), otherwise verification can fail.
Other domain providers
Look for DNS settings, DNS management or Zone editor, and add a CNAME record. Many providers add your domain automatically, so enter only the first part of the name (data, not data.yourstore.com). If your provider can't create a CNAME for that name, Stape can give you A and AAAA records instead: turn the CDN off and look for the option to use A records in the domain's advanced settings.
Step 4: Verify the domain
Back in your host's dashboard, click Verify. Your host checks the DNS record and issues a security certificate for the subdomain. This usually takes a few hours and can take up to 72 hours while DNS changes spread. Stape shows the domain as ready and emails you when it is done.
To check it yourself, open https://data.yourstore.com/healthy in your browser. A working Google tagging server answers with ok.
Step 5: Update your GTM server container
In Google Tag Manager, open your server container and go to Admin → Container Settings. Add https://data.yourstore.com as a server container URL, save, and publish the container.
Step 6: Update dataMonitorio
- Server container address. In dataMonitorio, open Settings → Google Tag Manager, replace the server container address with
https://data.yourstore.com, click Check connection and save. Checkout events now go to your subdomain. - Load GTM from your own domain. If you use it, paste the same address into Settings → Advanced → Load GTM from your own domain, click Check loader and save.
- Update your tags. Your GTM containers contain the server address, so Tag setup shows Your tags need updating. Click Update tags, download both files again, and import both into Google Tag Manager with Merge → Overwrite conflicting tags, triggers and variables. Check them in Preview, then publish both.
Step 7: Check that it works
- Open Preview in your server container and browse your store. Events should arrive as usual.
- In your browser's developer tools, open the Network tab and filter by your subdomain. You should see requests going to
data.yourstore.com, not to your host's domain. - Run a test order on the app's Test page (Growth and Pro), or place a test order and confirm the purchase appears in your server container and in each ad platform's test tool.
Troubleshooting
| Problem | What to check |
|---|---|
| Verification is stuck | Check the record name (many providers add your domain automatically, so data.yourstore.com.yourstore.com is a common mistake), turn off the Cloudflare proxy, and remove any older record with the same name. Then allow more time. |
| “Check connection” fails in dataMonitorio | Wait until your host shows the domain as ready and the certificate is issued, then try again. Make sure the URL starts with https:// and has no path at the end. |
| Events stop partway through the month | Your hosting plan has probably used its monthly allowance (common on free plans). Upgrade the plan and data starts flowing again straight away. |
| Purchases appear twice in an ad platform | Another app may be sending the same events. Choose one source for each platform. |
Still stuck? Contact us with your store address and the subdomain you chose, and we'll take a look.