Before updating the Experience Cloud site URL for your branded Experience Cloud app, review the potential impacts of making the change.
General Considerations
Keep these considerations in mind when changing the Experience Cloud site URL through Mobile Publisher.
- Changing the Experience Cloud site URL requires a new submission, build, and distribution of the updated branded Experience Cloud app.
- Use the final branded App Name in a test project since the App Name gets tied to the Experience Cloud site URL (not the site).
- Submit a beta app request when you know the final Experience Cloud site URL.
- Work closely with your Experience Cloud site admins to ensure there’s no last-minute changes to the Experience Cloud site URL.
- Use CDN for content storage and distribution that’s geographically closer to your users. CDN changes the URL for the Experience Cloud site.
- Avoid making any URL changes after the Mobile Publisher for Experience Cloud app is live.
- For orgs with multiple Experience Cloud sites, changing site URLs can cause deep linking issues to other Experience Cloud sites.
- URL validation now includes both the domain and the specific Experience Cloud site path on Android and iOS. If you change your site path, update your URL Management configuration and test link behavior on both platforms to ensure links to your site and to other sites on the same domain open as expected.
Testing Considerations
Keep these considerations in mind on how changing the Experience Cloud site URL can affect testing.
- Sandbox URLs can change after a sandbox refresh, so keep this possibility in mind. If the sandbox URL changes, a new beta app submission is required with the updated sandbox URL.