Domain migration to eggplant.cloud
for Real Customer Insights
The domain from which we host core.js, config.js and where the beacon is sent back to is moving away from nccgroup-webperf.com to eggplant.cloud. This means that the snippet that you instrument on your website will need updating to reference the new URL.
When is this change occurring?
As of 1 September 2018, we have enabled the new domain and customers can move over at any point from then.
Will my service continue to work whilst we plan the migration into a development sprint?
For a period of time, we will be dual-running the nccgroup-webperf.com domain alongside the new eggplant.cloud domain. This dual running will continue until 23:59 on 31 October 2018. This means you can plan in to upgrade at any point up until 23:59 on 31 October.
Do I need to let you know when I’m planning on/have done the migration?
There’s no need to let us know when you’re planning on doing the migration. As we are dual running, switching to the new snippet will be seamless and doesn’t require any further input from Eggplant.
What happens if I don’t update my script?
In the short term, nothing. However, if you haven’t updated your script by 23:59 on October 31 2018, your service will stop collecting data. We will serve a 200 in response to calls so as not to impact the browsing experience of your visitors but no data will be collected.
Will I lose any data/experience any service interruption?
As we are dual running, switching to the new snippet will be seamless. We will accept beacons coming in to both URLs during the dual running period which will handle propagation of the new snippet out via CDNs/local caching occurring over a period of time.
Do I have to remove the old snippet?
Yes. Keeping both snippets on the site will result in potential duplication and corruption of data.
Do I have to update my conversion/MVT capture?
No. These details are all the same and aren’t impacted by this change.
Are there any other benefits to changing?
We will be consolidating the URLs used for the core.js and the config.js files into one single domain. Currently, these are coming from two different domains, which results in an unnecessary call and TLS negotiation. By consolidating into a single domain, we will improve the reliability of capturing data from users on slower connections and on slower devices.
Is there a cost?
No. There is no cost to you from Eggplant for this change.