Documentation
How can we help?
Setup guides, platform how-tos and answers to common questions. The same guides are on the app's Help page.
No matches. Try another word, or ask us.
Guides
Setup guides
Step-by-step instructions, the same as on the app's Help page. Most take a few minutes.
Set up a server container with Stape
Checkout events are sent to your server-side GTM. Any host works; we recommend Stape. You can start on Stape's free plan and upgrade as you grow.
- In Google Tag Manager, create a Server container. Choose “Manually provision tagging server” and copy the Container Config.
- Create a Stape account. The free plan works for setup and small stores. It has a monthly request limit, and when that is used up the container stops accepting data until the next month, so upgrade before your traffic reaches it.
- Add a container, paste the Container Config and choose the server location closest to your customers.
- When Stape shows your container URL (for example https://abcdefgh.stape.io), copy it.
- In dataMonitorio → Settings → Google Tag Manager, paste it into “Server container address”, click Check connection, then Save. During setup, the Server container step does this for you.
- Next, connect your own subdomain to the container for first-party tracking (see the next guide).
Use your own subdomain for first-party tracking
A subdomain of your store (for example sgtm.yourstore.com) keeps tracking first-party and harder to block. It works on Stape's free plan too.
- Pick a short, neutral subdomain of the domain your customers see, for example data.yourstore.com. Avoid words like gtm, analytics, tracking or ads.
- In Stape, open your container → Domains → Add, enter the subdomain and choose to add the DNS records yourself. Stape shows the record to create.
- Add that record where your domain's DNS is managed. In Shopify: Settings → Domains → your domain → DNS settings → Add custom record. In Cloudflare, set the record to DNS only.
- Back in Stape, click Verify and wait until the domain shows as ready. This usually takes a few hours and can take up to 72.
- In your GTM server container: Admin → Container Settings → add https://your-subdomain as a server container URL.
- In dataMonitorio → Settings, change “Server container address” (and Advanced → “Load GTM from your own domain”, if you use it) to the new address, click Check connection, then Save.
- Tag setup then shows “Your tags need updating”: click Update tags, import both files with Merge → Overwrite, then Publish.
- Full walkthrough, including other DNS providers and troubleshooting: Run your server container on your own subdomain.
Turn on tracking in your theme
The tracking embed creates your storefront dataLayer and loads GTM.
- In Shopify, go to Online Store → Themes → Customize on your live theme.
- Open App embeds (the puzzle icon) and switch on Tracking dataLayer (listed under dataMonitorio).
- Click Save. The app's Home shows “Storefront: Active” within a minute. It can switch off when you publish a new theme: Home tells you if it does.
Respect your shoppers' consent
Connect your cookie banner so tags only run with permission.
- In dataMonitorio → Settings → Cookie banner, choose your cookie banner. During setup, the Cookie banner step finds it for you.
- Turn on Google Consent Mode. Microsoft Consent Mode (Settings → Advanced) is only needed for a Microsoft UET tag you run yourself (for example from Microsoft's sales channel app): dataMonitorio's own Microsoft setup already follows your banner.
- Save. If you already added your tags, Tag setup shows “Your tags need updating”: update them so every ad tag waits for consent.
- With Google Consent Mode on, Google Ads only accepts server-side conversions for events marked as key events in GA4. Checkout and purchase are marked for you. For storefront conversions you track in Google Ads (for example add_to_cart, sign_up or generate_lead), open GA4 → Admin → Key events → New key event, and type each event name exactly.
- Check it in GTM Preview: before you accept marketing cookies, the ad platforms' server tags don't fire; after you accept, they do. Google Ads reads consent only from Google Consent Mode, so keep it on.
Add your ready-made tags to Tag Manager
One web and one server container file, built for your platforms. Growth and Pro plans. Guided setup walks you through it; these are the same steps.
- Connect your cookie banner first, so your tags include consent settings.
- In guided setup's Platform IDs step (or Tag setup → Update tags), fill in each platform's IDs and access tokens. Each field shows where to find it.
- Click Generate, then Download web container and Download server container.
- In Google Tag Manager, open your web container → Admin → Import container. Choose the web file and your workspace, then Merge. The first time, choose Rename conflicting tags, triggers and variables. When you're updating, choose Overwrite conflicting tags, triggers and variables. Confirm.
- Do the same in your server container with the server file. Google's default “GA4” client can stay: our “dM - GA4” client runs first and handles GA4 requests.
- Check both in Preview, then Submit → Publish each container. Back in dataMonitorio, tick the three boxes to confirm.
- Later changes (a platform, an ID, your cookie banner, post-purchase tracking): Home and Tag setup show “Your tags need updating”. Click Update tags and repeat the import with Overwrite.
Test your tracking with a test order
Place one test order and see, event by event, that every platform you set up got it. Growth and Pro plans.
- Add your tags to Tag Manager and publish both containers first.
- Open Test in the app and choose a test: Quick (about 3 minutes: open your store, a product, add to cart, checkout, order) or Full (about 10 minutes: every event your store sends).
- Choose how to pay for the test order: Cash on Delivery or another manual payment method, Bogus Gateway on a dev store, or a free order (we create a one-time code, apply it for you and delete it after the test).
- Click Open my store and start test. Your store opens in a new tab. Keep the Test tab open: its table fills in as you do each step.
- Password-protected store? Enter the password first, then click Open my store again: the password page drops the test link.
- Full test: if your store has no newsletter, search or customer accounts, or you can't do a step now, click “Skip this step”.
- Pro with post-purchase tracking on (Full test): after the order, add a product to it (accept your upsell offer, or in Shopify open the order → Edit → add a product → Update order), then cancel the test order (More actions → Cancel order). The test checks that the upsell and the refund reach your platforms. Untick “Send invoice to customer” and “Send a notification to the customer” so no emails go out.
- When every row is green: “All tests passed — your tracking is set up”. Cancel the test order afterwards. Home shows the result. If your tags still have test event codes, the result reminds you to remove them before you go live.
- Just published? Tag Manager can take up to 5 minutes to switch to the new version, and a server container (on Stape, for example) up to 10. Wait a moment before you start, or repeat a step that shows a problem.
- Something red? Each problem says what happened and how to fix it. Fix it and click Test again, or send us a screenshot: the test ID and the details for support are on the page. Your last 10 tests are listed under Past tests.
Test problems and what they mean
Each problem a test finds has a code. Support uses it to see the cause at once.
- STORE_NO_EVENTS: nothing arrived from your store. Open it with the test button, check the app embed is on, and enter the store password first if there is one.
- STORE_EVENT_MISSING: you did a step but your store didn't send its event. Your theme may work differently: send us the details.
- GTM_NOT_LOADED: Google Tag Manager didn't start. Check the GTM container ID in Settings and accept the cookie banner.
- CONSENT_BLOCKED: cookies weren't accepted in this browser, so ad platforms held back. Click Accept on your banner and repeat the step.
- CONTAINER_NOT_PUBLISHED: your store runs other containers than the ones you downloaded. Import and Publish both (Tag setup shows how).
- CONTAINER_OUTDATED: your store runs tags from before your last update. Import and Publish the newest files.
- WEB_TAG_FAILED / WEB_TAG_NOT_RUN: a platform's browser tag failed or didn't run. Check its ID in Tag setup → Update tags, then import and publish again.
- SERVER_UNREACHABLE: events didn't reach your server container. Check the server container address in Settings and turn off ad blockers.
- SERVER_TAG_REJECTED: the platform answered with an error, usually a wrong or expired token or ID. The card says where to make a new one.
- SERVER_TAG_TIMEOUT: the platform didn't answer in time. Test again; if it repeats, send us the details.
- SERVER_TAG_ERROR / SERVER_TAG_NOT_RUN: the platform's server tag stopped or didn't run. Check it's published and that consent allowed it.
- CHECKOUT_PIXEL_MISSING: checkout events didn't arrive. Reconnect checkout tracking in Settings.
- CHECKOUT_TO_SERVER_MISSING: checkout sent events but your server container didn't get them. Check the GA4 measurement ID and server container address, and that the server container is published.
- ORDER_TO_SERVER_MISSING: dataMonitorio sent the upsell or refund from your test order but your server container didn't get it. Check the server container address and that your newest server container is published.
Test your tracking in GTM Preview
For experts: see every event and tag in Google Tag Manager.
- Storefront: in Google Tag Manager, click Preview on your web container and enter your store's URL. Browse, add to cart, and watch the events appear.
- Checkout: open Preview on your server container in the same Chrome window, then place a test order. Checkout events and the purchase appear there.
- GA4: turn on Debug mode in dataMonitorio → Settings → Advanced, then open GA4 → Admin → DebugView. Turn Debug mode off when you finish.
- Ad platforms: use each platform's test tool, for example Meta Events Manager → Test events, with the test event code from Tag setup.
Track post-purchase upsells, refunds and renewals
Pro plan. Upsells customers accept after checkout, from any app, reach GA4 and your ad platforms. Refunds and renewals reach GA4.
- In Settings, check that your server container address and GA4 measurement ID are filled in, and that After checkout → “Post-purchase upsells and refunds” is on. Save.
- Tag setup then shows “Your tags need updating”: click Update tags, import the server file (Merge → Overwrite), then Publish. Ad platforms count upsells as purchases only after this.
- Upsells arrive as post_purchase in GA4 (not as purchase, so your purchase revenue stays the checkout amount) and as a Purchase on your ad platforms. Order IDs look like 1001-01, 1001-02: the original order's ID plus one number per upsell.
- Google Ads: in Goals → Conversions, create a separate website conversion action for upsells (set up manually, category Purchase), add its label as “Post-purchase upsell conversion label” in Tag setup → Update tags, and import again. It keeps upsells out of your Purchase count. Make it primary to count its value in bidding, or secondary for reporting only. Without the label, Google Ads gets no upsells.
- Refunds of the original items are a GA4 refund. Refunds of upsell items are post_purchase_refund, because GA4 never counted them as purchase revenue.
- Subscription renewals (beta) arrive in GA4 as subscription_purchase with IDs like 1001-sub-03 (the first order's ID and the renewal count). Ad platforms don't get them: renewals are charged automatically, not won by an ad.
- To report on them in GA4, register original_transaction_id, post_purchase_source, subscription_cycle and subscription_plan as custom dimensions (GA4 → Admin → Custom definitions).
- Test it: turn on Debug mode in Settings → Advanced, place a test order paid by card and accept an upsell. post_purchase appears in GA4 → Admin → DebugView within a few minutes. Post-purchase offers only appear for card payments.
- Upsells won't appear in your server container's Preview: they're sent by our server from the order, not by the shopper's browser, and Preview only shows browser requests. To check an ad platform, use its test tool, for example Meta Events Manager → Test events with the test event code from Tag setup. Turn Debug mode off when you finish.
- Upsell apps that create a separate order instead of adding to the original aren't counted as post-purchase yet. Orders placed with buy-now or express buttons (no cart) match shoppers less well.
Load GTM from your own domain
Fewer ad blockers stop GTM when it loads from your server container's domain.
- In dataMonitorio → Settings → Advanced, paste your server container address (ideally your own subdomain) into “Load GTM from your own domain”.
- Click Check loader. When it says “Loader serves your GTM container”, click Save.
- If the loader ever fails for a shopper, GTM loads from Google as usual.
Does it work with Shopify's new checkout?
Yes. dataMonitorio uses Shopify's own app pixel for checkout, so it works with checkout extensibility.
Which ad platforms are supported?
GA4, Google Ads, Meta, TikTok, Pinterest, Snapchat, LinkedIn, X, Reddit and Microsoft Advertising. The Free plan covers GA4 and Google Ads.
Do I need a server-side GTM container?
Yes, for checkout. Shopify's checkout doesn't allow GTM in the browser, so checkout events (including purchases) go to your server container. Any host works, and you can start on a free plan. For the best results we recommend your own subdomain on a paid plan.
Can I use a free server plan?
Yes, it works, including with your host's own address (for example abcd1234.stape.io). The trade-offs: with the host's address, cookies are treated as third-party and expire sooner in browsers like Safari, and more requests are blocked by ad blockers. Free plans also have a monthly request limit (10,000 on Stape at the time of writing); when it runs out, the container stops accepting data until the next month. You can connect your own subdomain on Stape's free plan to fix the first two, and upgrade to a paid plan before you reach the limit. Compare the options.
Will dataMonitorio slow down my store?
No noticeable effect. The storefront script is small, loads after your page content, and only the platforms you turn on are loaded.
Does dataMonitorio store my customers' data?
No. Storefront and checkout tracking data goes straight from your store to your own Google Tag Manager containers, never through our servers. Email, phone number and name are hashed (SHA-256) in the shopper's browser before they reach your ad platforms, so platforms can match conversions without receiving them in plain text. With Pro post-purchase tracking, Shopify sends us order changes (upsells, refunds, renewals); we hash the customer details, forward the event to your server container right away and keep only a delivery record without customer data for 30 days. Pro reports keep only counts, totals and, for the order check, each tracked purchase's order ID (90 days, no customer data); the Customers page reads from Shopify each time without saving a copy.
Does dataMonitorio see my access tokens?
No. Access tokens (Meta, TikTok and the others) go from your browser straight into your own Tag Manager, inside the files you download and import. They never reach our servers and are never saved. Platform IDs (pixel IDs, conversion IDs) are remembered on your browser only, so you don't type them twice; “Forget saved IDs” clears them.
What happens when a shopper declines cookies?
With a cookie banner connected, personal details and ad identifiers are removed and your ad tags wait for consent. GA4 can still count anonymous visits if you use Google Consent Mode.
Which cookie banners work?
Shopify's own cookie banner on every plan. Growth and Pro also support CookieYes, Cookiebot, OneTrust, Pandectes, Consentik and a custom consent cookie.
I already have tags in GTM. Will importing break them?
No. The first time, import with Merge → Rename: it keeps your own tags safe. When you update, import with Merge → Overwrite: every item we add starts with “dM -” and sits in a “dataMonitorio -” folder, so Overwrite replaces only dataMonitorio's own tags. Your other tags stay as they are. Review duplicates of your own (for example a second GA4 tag you set up yourself) before you publish.
When do I need to update my tags?
After you turn a platform on or off, change an ID, change your cookie banner, turn on post-purchase tracking or move to Pro. You don't have to remember: Home and Tag setup show “Your tags need updating” with the reason, and a test afterwards confirms everything arrives.
Google Ads shows a server tag as failed: “Mark … as a conversion”. What do I do?
With Google Consent Mode on, Google Ads only accepts conversions for events marked as key events in GA4. In GA4 → Admin → Key events, add the event name shown in the error. Checkout and purchase events are already marked for you.
Why don't my GA4 and Shopify numbers match exactly?
Some shoppers block tracking or decline cookies, and Shopify also counts orders from POS and drafts. A gap of a few percent is normal; Analytics (Pro) shows where events go missing.
Can I change or cancel my plan?
Yes, any time from Plan in the app. Changes are billed through Shopify. If you cancel, tracking keeps working on the Free plan with the Google platforms.
How do I contact support?
Email support@datamonitorio.com. Pro plans get priority replies.
Still stuck?
Email support@datamonitorio.com or send us a message. Pro plans get priority replies.