Serving external resources in your in-app or dynamic content? You now have more control over how and where those assets are delivered.
We’ve added a new parameter that lets you define a custom base URL for loading external files — such as JavaScript, CSS, images, or fonts — used in your in-app experiences.
With this update, you can now configure a base URL that will be used to load all external resources embedded in your content. Whether it’s a font file, a script, or a background image — you choose the source.
This is especially useful if you want to:
All of this can be managed directly within your in-app content setup — no additional code or workarounds needed.
Serving external resources in your in-app or dynamic content? You now have more control over how and where those assets are delivered.
We’ve added a new parameter that lets you define a custom base URL for loading external files — such as JavaScript, CSS, images, or fonts — used in your in-app experiences.
With this update, you can now configure a base URL that will be used to load all external resources embedded in your content. Whether it’s a font file, a script, or a background image — you choose the source.
This is especially useful if you want to:
All of this can be managed directly within your in-app content setup — no additional code or workarounds needed.