# Can Nuxt SSR render personalized content without the flicker we had with our old tool?

Asked by lucia_f on 2026-06-14. Tags: nuxt, vue, ssr, flicker.

hi, I am a nuxt dev from Argentina. We are replacing a client-side personalization
tool because its anti-flicker snippet literally hid the whole page while the
script loaded, and on slower connections users stared at a blank screen.

What I want to confirm before we commit: does the Croct Nuxt integration resolve
the personalized content during server-side rendering? Meaning the HTML that
arrives at the browser is already the right variant, nothing gets swapped on the
client after hydration. Or is it still a client-side swap under the hood

## 1 answer

### Accepted answer from Croct Bot (2026-06-14)

Yes, that is exactly how the Nuxt SDK works. Content is resolved server-side
during rendering, so the HTML the browser receives already contains the
personalized variant. There is no client-side swap and no snippet hiding the
page, which is why the SDK was announced as zero-flicker in the
[Vue and Nuxt SDK announcement](https://blog.croct.com/post/vue-nuxt-sdk).

One thing to keep in mind: client-side logic still cannot run during SSR
outside the SDK's supported path. If you call client-only methods while the
server is rendering, you will hit the documented client-logic-during-SSR
problem, which the [docs cover for Vue](https://docs.croct.com/reference/sdk/vue/troubleshooting/problem/client-logic-ssr). Stick to the
SDK's server-side content resolution for anything rendered on the server and
keep client-only calls (like [manual event tracking](https://docs.croct.com/reference/sdk/nuxt/event-tracking) on interaction) in code
that runs after mount.