Direct URL Routing FAQ

What’s Changing?

Starting October 1st, 2024, all requests from SDKs will be sent directly to our pod endpoints rather than through Fastly, our CDN provider.

Background

mParticle stores and processes data in various geographic pods (US1, US2, EU1, AU1, etc.). Currently, all requests are sent to generic subdomains such as jssdks.mparticle.com (Web) or nativesdks.mparticle.com (iOS/Android), managed by Fastly. Fastly reroutes these requests to specific pods such as jssdks.us1.mparticle.com or nativesdks.us1.mparticle.com, which adds an extra step before reaching our servers. We aim to enhance the real-time performance of our platform by removing the extra step.

Web:

Previous Endpoint Subdomain	New Endpoint Subdomain Starting October 1st, 2024
https://jssdks.mparticle.com	https://jssdks.[pod].mparticle.com
https://identity.mparticle.com	https://identity.[pod].mparticle.com
https://jssdkcdns.mparticle.com	No change (Used to fetch the SDK/configuration)

Android/iOS (Native)

Previous Endpoint Subdomain	New Endpoint Subdomain Starting October 1st, 2024
https://nativesdks.mparticle.com	https://nativesdks.[pod].mparticle.com
https://identity.mparticle.com	https://identity.[pod].mparticle.com
https://tracking-nativesdks.mparticle.com	https://tracking-nativesdks.[pod].mparticle.com
https://tracking-identity.mparticle.com	https://tracking-identity.[pod].mparticle.com
https://config2.mparticle.com	No change (Used to fetch the SDK/configuration))

Why is mParticle making this change?

Sending data directly to the specific geographic pod will not only enhance the real-time performance of our platform, but also remove a potential failure point.

Do I need to make any changes to my setup before October 1st, 2024?

This change only impacts customers using the Android, iOS, or Web SDKs with whitelisted mParticle subdomains. Select the platform that your company uses for further directions for any changes you need to make and testing options after you make the change.