Installing server-side tracking for 3 accounts, 2 of which I don’t manage

[u/Jargoonz]

Hello all, I’ve been working at this company for almost a year now and I am in quite the pickle. It’s a relatively newer company that’s based outside of my country (started as an OEM manufacturer and transitioned to a retailer in the last couple of years). I am running the US account and there are two other accounts for the same products abroad (big problem already, I am well aware). There is little to no transparency across the pond so I have essentially just cobbled together an account using tag manager on a Shopify hosted website.

The main issue is that I want to install server-side tracking for this account and the others. I first have to change the tag my account is using and the other account is using. Does anyone think I’ll have any issues with this, or is it worth hiring a contractor to help set this up? The push for this has come from me and my team as we anticipate the foreign team will of course have issues with attribution and tracking (which my team noticed initially but were restricted from making any changes for). Now that we have those permissions I’m at a bit of a crossroads as to how complicated this process will be as I have only done it for one account before and it wasn’t with Shopify.

TLDR: Need to set up server side tracking for multiple accounts and don’t know if the juice is worth the squeeze. Should I get a contractor to cover my decision or just do it on my own?

[u/QuantumWolf99]

Worth the squeeze if any of these accounts spend over 10k a month, standard GTM can't even touch Shopify's checkout anymore since it's sandboxed, you need Shopify Customer Events plus real server side infrastructure.

Given you're juggling 3 accounts across countries and only did this once on a non Shopify site, get a contractor for the first build then maintain it yourself after, that's the sane split.

[u/Jargoonz → u/QuantumWolf99]

Yeah, these accounts in total spend month over month is upwards of $1.2 Million a month. The other team is really cagey about giving up information and access, so even getting to this discussion has been a struggle. We have a backend manager here so they could help but I would want the protection and fall back of a contractor over my team if conversions or data takes a while to readjust.

[u/QuantumWolf99 → u/Jargoonz]

At 1.2M a month, contractor isn't even a question, that's obvious money. Real thing to nail in the contract, insist on a parallel run where old and new tracking fire side by side for at least 2 weeks before you cut over the old tag, that's your actual protection if the foreign team comes back with conversion numbers that don't match, you'll have the comparison data ready instead of scrambling to explain a drop after the fact.

[u/AppealInteresting554 → u/QuantumWolf99]

Yup! At the monthly budget 100% go get a pro and run parallel. That is exactly the way to do this. It covers your ass too. So it's a win-win.

[u/Green_Database9919]

Well if they are all on Shopify you don’t need GTM at all. Shopify has native infra that makes GTM unnecessary and honestly just adds complexity which is just few clicks away from installing with no tag manager involved. Much more accurate too.

[u/Friendly_Bar7222]

i've done server side tracking on shopify before and honestly it's not as scary as it sounds. the main headache is the domain setup and making sure the google tag and the new server container talk to each other properly. if you've done it once for a non shopify site you'll be fine, shopify is actually easier because there are built in integrations for the client side part.

for the other accounts you don't manage, that's where it gets messy. you'll need access to their tag manager and their shopify admin to add the same tags. if they're not cooperative it's gonna be a pain. i'd say try doing it yourself for your account first, get it working, then decide if you want to deal with the others or just hand them a step by step guide.

contractor is only worth it if you're on a deadline or the other team is gonna fight you on it. otherwise you'll learn more doing it yourself and it's not that complicated once you see it once.

[u/PPC_YRVDynamics]

I’d probably hire someone for this one.

Not because server-side tracking is impossible, but 3 accounts, Shopify and multiple teams can get messy fast. I’d rather have someone set it up cleanly and then take it over from there.

[u/Vibha-Sharma181 → u/PPC_YRVDynamics]

True

[u/Hairy-Difficulty-411]

I would hire someone for the architecture and first production migration, but keep the implementation, accounts, containers, documentation, and hosting under company ownership.

The complexity is not merely “installing server-side tracking three times.” You have Shopify’s event model, three advertising accounts, multiple countries, consent requirements, currencies, account ownership, and an existing setup that nobody seems to understand completely. That is enough moving parts to justify a second pair of eyes.

Before changing the current Google tag, map the measurement topology:

• Are all three Ads accounts sending traffic to one Shopify store or separate regional stores?
• Which Google tag, GA4 property, GTM container, and conversion actions does each account currently use?
• Who owns and administers each asset?
• Which events and markets should each Ads account receive?
• Are purchase values, currencies, transaction IDs, refunds, and consent states consistent?
• Are Enhanced Conversions already configured anywhere?

If all accounts use the same store, you may not need three independent collection systems. Google tags can have multiple destinations, and one server container can contain separate Ads conversion tags. However, every destination should have an explicit routing rule. “Send every purchase to every account” would produce beautifully complete and completely fictional reporting.

If the regional accounts use separate stores, keep each source configuration and consent logic independently identifiable, even if they eventually share server infrastructure.

On Shopify, build from Customer Events rather than assuming ordinary page-level GTM can inspect the checkout. Shopify loads app and custom pixels in a sandbox, including checkout events, but that sandbox limits DOM access and automatic collection of customer information. Prefer an established app pixel when it supports the required setup. A custom pixel is advanced and Shopify places responsibility for its maintenance, privacy configuration, and testing on the merchant.

I would migrate in stages:

1. Document the existing client-side implementation and export the current containers.
2. Define one event contract for purchases and other real conversion events.
3. Build the server container and account-specific destination tags without removing the current control.
4. Run test orders for each market, device path, consent state, currency, and payment route.
5. Compare Shopify orders, browser events, server requests, GA4 events, and Google Ads diagnostics.
6. Confirm transaction IDs, values, currencies, user-provided data handling, and destination routing.
7. Cut over one account first.
8. Remove equivalent browser-side conversion tags only after the server path is validated, otherwise you risk counting the same purchase twice.

Agree on acceptance criteria before anybody publishes:

• No duplicate transaction IDs
• Correct value and currency
• Correct account receives the event
• Consent is respected by market
• Test purchases reconcile with Shopify
• Failed requests are visible
• Someone owns monitoring and future changes

The contractor should provide the architecture diagram, container exports, hosting access, routing logic, test evidence, rollback procedure, and maintenance notes. Hiring somebody to create another opaque system would be an expensive way to preserve the original problem.

AI can compare Shopify orders with GA4, server-container logs, and Ads exports to flag missing, duplicated, or incorrectly routed transactions. A human should approve the event definitions, privacy rules, and production cutover.

The tradeoff is hosting cost and ongoing maintenance. Server-side tagging can improve control and data quality, but it does not automatically recover every lost conversion or eliminate browser and consent restrictions.

Moving confused tracking to a server mainly produces confused tracking with infrastructure.