Shopify Markets - Different Top Level Domains

Shopify Server-Side Tagging
1

I’ve read in a thread from last year that different Tagging-Server URLs are not supported by the Shopify App. Any change on this? Have a client with different TLDs for the different Markets:

E.g.:

If it still isn’t supported - any idea how to solve this outside of the Stape App?

2

Hello @Robin_Heerich adding such functionality is in our backlog.

You can handle this outside of Stape App by injecting scripts directly into theme and/or custom pixels. You want a condition checking for location.hostname to server the relevant snippet/subdomain

3

Thanks, I’ll look into it. Give it an upvote in the Backlog for me :wink:

Any way to get notified if you implement this?

4

@Robin_Heerich best way would to be to subscribe to our Linkedin: Stape | LinkedIn

5

Hey Dan, i have the same problem right now as Robin with a client.

I plan on manually inject custom loader / cookiekeeper on domain number 2. But what about datalayer and datalayer in checkout. Guess I also have to do that manually then?

6

@jeppe_Nielsen Unless you actively land people on checkout pages, it doesn’t make a difference which domains loads the container in the sandbox (meaning .de or .at etc).

So what the app provides for the custom pixel should be sufficient, so long as inside your setup you route the traffic correctly. Therefore you’d only need to handle pre-checkout.

If you above makes you feel dirty :smiley: though, then sure, you can unpack the script the app provides and add additional loader and conditions to that.

7

Right, thank you! so handling pre-checkout, i do need to manually deploy datalayer there then?

Yes, my setup is Lookup tables for hostnames inside GTM

8

so handling pre-checkout, i do need to manually deploy datalayer there then?

no, the app does it for you. just disable the GTM snippet part, don’t do anything with dataLayer tab. Pre-checkout all events will be properly pushed to your DL regardless of how you load the container

9

Alright, thank you! ill give it a shot

10

hey again Dan! :smiley: sorry but i am really confused right now :smiley: not sure we are talking about teh same thing.

Ok, so ill try to break it down 100%

Our domains (websites) are called. (shopify)

.se
.de

they are identical expect for the language.

  1. We are using Stape multi domains

  2. We have 2 sub domains for each website.

  3. Problem is Stape GTM app can only handle 1 which i have setup for subdomain .de

So my questions are.

  1. How do i handle datalayer both pre and inside checkout on subdomain that I dont use the Stape App for.

  2. Same question as 1, just for custom loader / cookiekeeper.

Do i need to inject it all manually then? Datalayer as well etc? Really hope you can help with this :slight_smile:

Thank you!

11

  1. You don’t ‘handle’ it. Just let the app do it’s work. Make sure in Data Layer tab of the app you have checkboxes on.

  2. You disable GTM embed from the app and add the loader snippet directly to theme.

bottom line: pre-checkout, you need to handle the loader and you DON’T need to handle dataLayer.

  1. For checkout and furher:
  • grab the script our app provides
  • get the donwloaded part (there’s a link in the script with the id)
  • put that into the custom pixel explicitly
  • within that script add logic for choosing the subdomain (line 2) to be put into the loader
  1. Enjoy
12

Hey Dan, thank you so much - that made a lot more sense :smiley:

13

Hi @Dan I have some doubts about it.

So I have to take “custom loader” code (for custom website and not for Shopify) from Stape and put it into a web pixel with logic for each subdomain and than keep enabled DataLayer in Stape GTM Shopify App copying the same code and pasting it into a web pixel right (disabling GTM embed code)?

And in theme code nothing (also GTM original code?) right?

In Webhook tab (Stape GTM App) what we gonna do? Which custom subdomain (with path) we’ll use?

Thank you

14

@Ste

You want:

  1. Hostname-based logic for container download pre-checkout - you do that by injecting script into theme directly, wrapping it into a condition(s) that fir your needs

  2. Pre-checkout dataLayer - no changes needed here. Just let the app work

  3. Hostname-based logic for container download post-checkout (so in sandbox), I described above how to do that.

  4. DataLayer post-checkout. This is part of the item 3, cause post-checkout dataLayer is controlled by that script

Bottom line: your action plan is what I described above for @jeppe_Nielsen

P.S. If you do use webhooks - the endpoint doesn’t matter, can be either one of your domains, for webhooks domain match (first party) is irrelevant.