Google Optimize is no longer available.
For businesses that relied on it for A/B testing, split testing, and personalisation, this is no longer a future problem to plan for. It already happened. Google officially sunset Google Optimize and Optimize 360 on September 30, 2023, and any experiments or personalisations still running at that point ended as well.
That left a lot of teams with the same question:
What now?
If your business used Optimize, the real challenge in 2026 is not just replacing a tool. It’s choosing the right experimentation setup for where your business is today, and where you want it to be in the next 12 to 24 months.
What happened to Google Optimize?
Google announced the shutdown of Optimize as part of a broader shift in strategy. In its official guidance, Google says it is investing in third-party A/B testing integrations for Google Analytics rather than continuing Optimize itself.
That means there is no modern Google Optimize relaunch waiting in the background, and for most businesses there is no native Google replacement that handles experimentation the way Optimize once did. Google Analytics can still help interpret test results, but teams now need a separate experimentation platform to run and manage A/B tests.
Why Google Optimize mattered
Google Optimize was popular because it made experimentation more accessible.
It gave marketing teams, CRO specialists, and digital teams a relatively simple way to start testing without immediately committing to a heavyweight enterprise platform. For many businesses, it was the easiest entry point into experimentation because it offered:
- straightforward A/B testing
- a familiar connection to Google Analytics
- an approachable setup for web teams
- a lower barrier to getting started with CRO
For growing organisations, that mattered. Optimize helped teams learn by testing, not just by debating ideas in meetings.
What this means for businesses now
If you previously used Google Optimize, the question is no longer whether you need to move. It’s whether you’ve moved to the right approach.
Most organisations now need to focus on three things.
1. Decide what kind of experimentation you actually need
Not every business needs the same testing setup.
Some teams only need simple front-end A/B testing on marketing pages. Others need server-side experimentation, product experiments, rollout control, or personalisation across multiple audiences.
Those are different use cases, and they should not all be solved with the same platform.
Before comparing vendors, it helps to get clear on whether your priority is:
- marketing-site A/B testing
- CRO and landing page optimisation
- product experimentation
- feature delivery and rollout testing
- personalisation
- enterprise governance and workflow control
2. Rebuild your measurement plan
One reason Optimize worked for a lot of teams was that it sat comfortably alongside Google Analytics. That convenience is gone.
In GA4, Google’s own documentation makes clear that A/B tests are run through a third-party experiment tool, while Google Analytics is used to analyse the results.
So replacing Optimize is not just about selecting a new platform. It also means reviewing how you measure success.
That includes:
- defining clear primary and secondary metrics
- making sure event tracking is reliable
- aligning reporting between your test tool and analytics stack
- putting naming conventions in place
- improving QA before tests go live
A weak measurement setup will break confidence in your experiments no matter how good the platform is.
3. Avoid making a tool-first decision
A lot of businesses responded to the end of Optimize by immediately looking for the closest visual replacement.
That’s understandable, but it often leads to one of two problems: buying something too limited, or buying something far more complex than the team is ready to use properly.
A better question is:
What level of experimentation maturity do we want to support over the next 12 to 24 months?
That shifts the conversation from “What tool looks most like Optimize?” to “What setup will help us run better tests, learn faster, and make stronger decisions?”
What should businesses look for in a replacement?
There is no single best replacement for every team, but there are a few things almost every organisation should evaluate.
Ease of implementation
Can your team launch and maintain tests without heavy developer bottlenecks?
Experiment type support
Do you only need front-end A/B tests, or do you also need feature flags, server-side experimentation, or personalisation?
Reporting and statistical clarity
Will your team be able to understand and trust the results?
Integration with your current stack
How well does the platform fit with GA4, your tag manager, your data layer, your CRM, or your CDP?
QA and governance
Can you manage approvals, permissions, and testing workflows cleanly?
Cost versus maturity
Are you paying for enterprise depth you won’t use, or limiting yourself with a tool you’ll outgrow too quickly?
The real opportunity after Optimize
The end of Google Optimize was inconvenient, but it also forced a lot of businesses to ask better questions.
Questions like:
- Are we testing often enough?
- Are we measuring experiments properly?
- Are we learning from results, or just launching tests?
- Do we need a testing tool, or do we need a better experimentation program overall?
That’s the bigger opportunity.
The businesses that adapted best were not necessarily the ones that replaced Optimize fastest. They were the ones that used the transition to improve their experimentation strategy, measurement framework, and operating model.
Where Kraken Data can help
At Kraken Data, we help businesses move beyond “we used to use Google Optimize” toward a more sustainable experimentation approach.
That can include:
- evaluating replacement platforms
- improving CRO measurement in GA4
- planning implementation and QA
- designing a practical experimentation roadmap
- helping internal teams build a repeatable testing process
Google Optimize may be gone, but experimentation is not.
And in many cases, this shift is a chance to build something stronger than what came before.