Feature Overview
Custom Domain for Redirect URL is a feature in Synerise that lets users define a custom base URL for loading external resources — such as JavaScript, CSS, images, and fonts — used in in-app experiences and dynamic content. This allows assets to be served from a user's own domain or CDN instead of the default Synerise-hosted URL.
The feature is configurable directly within the in-app content setup in Synerise.
What Is Custom Domain for Redirect URL?
Custom Domain for Redirect URL is a configuration parameter in Synerise that lets users specify a custom base URL for external resources embedded in in-app and dynamic content. All external files — JavaScript, CSS, images, fonts — are loaded from the specified domain instead of the default source. This provides control over asset delivery, enabling users to serve content from their own domain or CDN.
Why Custom Domain for Redirect URL Matters
By default, external resources in in-app content are loaded from Synerise-hosted URLs. Organizations with strict security policies, performance requirements, or brand consistency standards may need to serve these assets from their own infrastructure.
Custom Domain for Redirect URL addresses this by:
- Allowing external resources to be served from a custom domain or CDN
- Enabling stricter security and performance policies for asset delivery
- Ensuring brand consistency in how content is delivered to end users
- Requiring no additional code or workarounds — configurable directly in content setup
Key Capabilities
Custom base URL configuration
Users define a base URL that is used to load all external resources embedded in in-app and dynamic content — JavaScript, CSS, images, and fonts.
Own domain and CDN support
Assets can be served from the organization's own domain or CDN, enabling control over delivery infrastructure, caching, and security.
No-code configuration
The custom domain is configured directly within the in-app content setup — no additional code or workarounds required.
How Custom Domain for Redirect URL Works
- Navigate to the in-app content setup in Synerise.
- Locate the custom base URL parameter.
- Enter the desired base URL (e.g., your own domain or CDN endpoint).
- All external resources (JavaScript, CSS, images, fonts) in in-app content will be loaded from the specified URL.
Example Use Case
A financial services company has a security policy requiring all customer-facing assets to be served from their own CDN with specific caching and access controls. Using Custom Domain for Redirect URL, the team configures their CDN endpoint as the base URL for in-app content resources. All JavaScript, CSS, and image assets are now served from the company's infrastructure — meeting security requirements without modifying any content code.
FAQ
What is Custom Domain for Redirect URL?
A configuration parameter that lets users define a custom base URL for loading external resources (JavaScript, CSS, images, fonts) in Synerise in-app and dynamic content.
What resources are affected?
All external resources embedded in in-app content: JavaScript files, CSS stylesheets, images, and fonts.
Do I need to write code?
No. The custom domain is configured directly within the in-app content setup.
Can I use my own CDN?
Yes. Any custom domain or CDN endpoint can be specified as the base URL.
Key Facts
| Attribute | Value |
|---|---|
| Feature | Custom Domain for Redirect URL |
| Product | Synerise |
| Module | In-App Communication / Dynamic Content |
| Purpose | Define a custom base URL for loading external resources in in-app content |
| Supported resources | JavaScript, CSS, images, fonts |
| Configuration | No code required — set directly in content setup |
Related Concepts
- In-app communication in Synerise
- Dynamic content delivery
- Dedicated On-Device Storage for In-App Communication
- CDN and asset management
- Security and performance policies
TL;DR
Custom Domain for Redirect URL in Synerise lets users define a custom base URL for loading external resources (JavaScript, CSS, images, fonts) in in-app and dynamic content. Assets can be served from a custom domain or CDN instead of the default Synerise-hosted URL. The feature is configured directly in the content setup — no code required — and supports stricter security, performance, and brand consistency requirements.
