[Enhancement] Introduce config parameter to set a static tracking / asset endpoint URL for trackingcode/container generation

[peterbo]

Summary

In many cases, the Reporting-UI is accessible through other URL(s) than the URL that the tracking code should use. For example, in an internal network (not accessing local applications via public routes), multiple URLs for different verticals, different subdomains, WAFs / Firewalls, proxies, etc.

The tracking code / TagManager code generator always uses the current URL as a "base" for creating the tracking endpoint / asset URLs. Therefore, I as a user always have to edit the Tracking code to contain the "correct" Endpoint URL (tracking / assets / TagManager configuration variable). It would be helpful to use a configuration variable like "generator_canonical_url" to assign a static URL which is always used by the generators.

[randy-innocraft]

Hi @peterbo,
Thank you for bringing this to our attention and for your valuable input.
Your suggestion seems like a valuable enhancement to our product.
We will forward this to our Product team for review and future consideration.
If you have any additional details or questions, please feel free to share them here.