Loader Multi-Domain Configuration Questions

Hi all,

When changing the setup in the custom loader configuration screens to get the script output, changing one domain setup seems to change the values for all of them, I’ve found that a block and a bit of a pain a couple times now.

For example, we have a new dev site being setup, it’s on a different platform and I wanted to use url path as an endpoint. I added domains, set this up, but it caused the production setup to change as well in the UI. Can we not change them on a granular level per domain? Is it not possible to have different configurations based on the URL or do they have to all be exactly the same?

The layout of the interface gives the impression it’s configured per domain. Does it matter what the UX says, is it used in the process somewhere or is it literally just to select options to be a snippet generator.

Is this scenario not supported and will required a totally separate container? That kind of negates the point of being able to add 20 domains going through the one container.

Hope that makes sense, any direction appreciated.

Stuart.

Hey Stuart,

In Custom loader, two options apply to all domains:

  • same origin path
  • ga4 bypass activation

Stape has plans to rework the UI/UX there to improve the custom loader experience with multi domain, but these two options will apply to all domains.

So if you use same origin path it should be the same for all domains and used for all domains.

All other options just generate the loader code for you and actually have no effect on the functionality.