How to migrate multiple websites into Batch Omnichannel projects?

Pre-requisite: Unique Custom User IDs

• First, ensure that the same Custom User ID is used across the websites you plan to group. If not, the ID will need to be changed in the JavaScript tag (see step 3).

Managing web environments (Batch dashboard)

• Choose between these 2 options to define the target environment: 1. Keep an existing web environment Advantage: You can continue addressing a large portion of your opt-in base without interruption if the selected website contains most of the users. 2. or Create a new environment (Recommended) Advantage: Greater flexibility for migrating campaigns. • You can recreate campaigns as drafts on the new environment and switch over at the right time, instead of having to update all live campaigns. • This allows better handling of languages, regions, and translations. • This option is also preferable if a change of Custom User ID is required (e.g., when your web and app environments do not share the same Custom User ID).

Option 1 steps:

• Select the website environment that you want to use as the target environment (e.g., domain.fr).

• Add the secondary domains (e.g., domain.de, domain.it...) under Settings > Push settings > Allowed origins:

Option 2 steps:

• Create the target environment by adding a new website to your Batch dashboard (from the left bar, "Add a new app or website).

• Declare one of your domains (e.g., domain.fr) as the primary domain on this new environment:

• Add the secondary domains (e.g., domain.de, domain.it...) under Settings > Push settings > Allowed origins:

JavaScript tag implementation

Update the Batch JavaScript tag on all your websites:

• If your Custom User ID differs between the websites of the project: Update the method to set the Custom User ID with the necessary variable.

• Replace the SDK API Key, Auth Key, and VAPID public key. These keys can be found under Settings > General and Settings > Push settings of the target environment.

• Modify the scope of the Batch Service Worker (e.g., turn it to /js/) on each domain.

• Unregister the Service Worker from the previous scope by adapting the script below to each domain (only required for secondary domains if option 1 was chosen).

async function replaceBatchRegistrations() {
  if (!("serviceWorker" in navigator)) {
    return;
  }

  // List registered service workers
  const currentServiceWorkerRegistrations = await navigator.serviceWorker.getRegistrations();
  await currentServiceWorkerRegistrations.forEach( async (registration) => {
    if (registration.scope === 'https://www.domain.fr/') { //REPLACE WITH OLD SCOPE
      // Found old service worker -> Removing
      console.debug("Found old service worker -> Removing")
      await registration.unregister()
    } else if (registration.scope === 'https://www.domain.fr/js/') { //REPLACE WITH NEW SCOPE
      if (!("pushManager" in registration)) {
        return;
      }
   
    }
  })
}
await replaceBatchRegistrations()

Managing orchestrations

• Duplicate your existing Web Push automations as drafts in the new environment.

• [Optional] Send campaigns from the old environments, encouraging users to revisit the site - this helps accelerate the migration of your user base.

• Once a sufficient volume of users has migrated to the target environment:

  • Deactivate the automations on the old environment.

  • Activate the automations on the target environment.