🛰️ What Data Does the OTTO Pixel Collect?

The OTTO pixel is a lightweight tracking script you place on your website. It collects anonymised, session-level behavioural data to help OTTO understand how visitors interact with your pages. Specifically, it captures:

• Page views and URL paths — which pages are visited and in what order.
• Scroll depth — how far down a page a visitor scrolls.
• Click events — interactions with links, buttons, and navigation elements.
• Session duration — time spent on individual pages and across the full session.
• Device and browser type — general environment data (e.g. mobile vs desktop, browser family).
• Referral source — the channel or URL that brought the visitor to your site.

The OTTO pixel does not collect personally identifiable information (PII) such as names, email addresses, or payment details. No individual user profiles are created. All data is processed solely to inform OTTO's on-page SEO recommendations and to measure the impact of deployed changes on engagement signals.

📋 How to View Previously Deployed Changes in OTTO

OTTO keeps a full log of every change it has applied to your site so you can audit, review, or roll back at any time.

1. In the left sidebar, navigate to OTTO SEO, then open All Sites (SEO Automation).
2. Open the OTTO project you want to review.
3. Click the Deployment History tab near the top of the project dashboard.
4. You will see a chronological list of all deployed actions, each showing the date and time, the page or element affected, the type of change (e.g. title tag update, meta description, schema injection), and the deployment status (Active, Rolled Back, or Pending).
5. Click any entry to expand the full details, including the before and after values for that change.
6. To revert a specific change, click Roll Back next to the relevant entry and confirm the action.

Deployment history is retained indefinitely for your project so you always have a complete record of what OTTO has modified.

🌐 Will OTTO Changes Be Visible in Webflow Developer Mode?

This depends on how OTTO deploys changes to your Webflow site.

JavaScript-injected changes (default method): OTTO deploys most SEO updates — such as meta tags, structured data, and canonical tags — by injecting them via the OTTO pixel script at page load. These changes are applied to the rendered DOM and are not written back into the Webflow Designer or CMS. As a result, they will not be visible in Webflow's Designer, Editor, or developer mode panels. However, they are fully visible to search engine crawlers and in your browser's View Page Source or Inspect Element tools on the live site.

Direct CMS integration (if enabled): If you have connected OTTO to your Webflow site via the native CMS integration, certain content-level changes may be written directly to Webflow CMS fields. In this case, those specific changes will appear inside Webflow's Editor and CMS collections. Check your OTTO project settings under Integrations to confirm which deployment method is active for your Webflow site.

Key takeaway: Always verify OTTO changes by viewing your live page source rather than relying on Webflow's Designer view, unless you are using the direct CMS integration.

✅ Quick Reference Summary

• OTTO pixel collects: anonymised behavioural data only — no PII.
• Deployment history: found in OTTO SEO → All Sites (SEO Automation) → your OTTO project → Deployment History tab.
• Webflow Designer visibility: changes are not visible in Designer by default; use View Page Source on the live site to confirm.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.