## **🔍 What causes the issue?**

React hydration failures occur when the HTML generated on the server differs from the page structure React expects in the browser. The OTTO pixel can modify page elements after loading, and in some React applications this may happen while hydration is still in progress.

This can result in errors such as “hydration failed,” “text content does not match,” or “the server rendered HTML didn’t match the client.” The issue is more likely when OTTO changes content, attributes, or elements that React controls.

## **⚛️ Compatibility with Lovable and React**

Lovable projects commonly use React-based rendering. OTTO’s browser-side updates are designed to work with standard websites, but React requires its managed DOM to remain consistent during hydration. Compatibility can therefore depend on the project’s rendering mode, page structure, script timing, and the elements OTTO is configured to update.

A hydration error does not necessarily mean the pixel is permanently incompatible with React. It indicates that the pixel and the application may be modifying the same markup at an unsafe time.

## **🧪 How to diagnose the problem**

1. Open the affected page in a private browser window.
2. Check the browser console for hydration or React mismatch errors.
3. Temporarily disable the OTTO pixel and reload the page.
4. Compare the page behavior with the pixel enabled and disabled.
5. Identify whether the error occurs on every page or only pages where OTTO applies changes.
6. Record the page URL, error message, browser, and whether server-side rendering or static rendering is enabled.

## **🛡️ Recommended mitigations**

- Ensure the OTTO pixel is installed according to the current Search Atlas instructions.
- Avoid applying OTTO changes to elements that React frequently re-renders, such as dynamic components, navigation controls, or application state containers.
- Test OTTO changes on a staging or preview deployment before publishing them to production.
- For affected pages, temporarily pause the relevant OTTO changes or pixel deployment while investigating.
- Where supported by your implementation, load third-party scripts only after the application has completed hydration. Your development team should confirm the safest timing for the project.
- Do not manually edit React-generated markup in ways that could create a second mismatch.

## **🚀 Is an OTTO-side correction available?**

Our engineering team can investigate whether the reported DOM modification is contributing to the failure and whether an OTTO-side adjustment is appropriate. A correction may involve changing how a modification is applied, excluding a selector, or improving script timing. The correct solution depends on the page and the specific React error, so it cannot be confirmed without reproduction details.

When reporting the issue, include the affected URL, a console error screenshot or copied message, the time of occurrence, the OTTO project or change involved, and the result of testing with the pixel disabled. This helps the team determine whether the issue is caused by OTTO, the application’s rendering behavior, or another script.

## **💬 Get help with an investigation**

If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.