Based on the CMS 13 migration docs I would be careful with this setup.

CMS 13 introduces breaking changes in the Graph schema compared to CMS 12 and the documented migration path seems to create a separate CMS 13 project / Graph instance rather than reusing the CMS 12 one

no. Wojciech's right. or so I believe On 12 each type is its own flat root query, Url is a string. On 13 it's a unified schema with `_`-prefixed base types, metadata under `_metadata`, Url as an object, plus Experiences and Variations. 

Roger that, thank you

Hi Wojciech,  For anyone landing here, the post is at: https://wseweryn.dev/blog/2026-06-11-odp-real-time-audience-design/ Useful write-up. Just a quick note on the latency stats in the Feature Experimentation section. The post mentions most requests take under 10 seconds, but the linked Optimizely docs put the typical figure at under 30 seconds (with 99.999% under 90s).

Since that ~30s baseline is exactly why they advise against using RTAs for things like immediate post-purchase confirmation pages, tweaking that number actually backs up your warning even better.

Hi Piotr, thanks for catching that, you are right.

The documented baseline is that ODP usually takes less than 30 seconds to reach accurate results, with 99.999% of cases taking less than 90 seconds.

I updated my post to match the docs, thanks!