How to Avoid Common Mistakes When Connecting SeaText to Odoo

Why SeaText and Odoo Connections Fail

Connecting SeaText to Odoo fails most often because users skip steps in the official integration process. The source pack lists a clear sequence: open the Website module, drag the Embed Code block, paste the snippet, save, hide the block on desktop, and save again. If you miss any of these, the script may not load or may show visible artifacts.

Another major cause is the account-to-domain rule. The SeaText Odoo integration guide states that each account is linked to a single primary URL. If you try to reuse one account across staging, production, or development domains, the connection can behave unpredictably. This often shows up as missing data or broken personalization.

The good news is that most problems come from a few repeatable mistakes. Below are the most common ones, why they happen, and how to fix them.

Mistake #1: Using One SeaText Account for Multiple Domains

SeaText accounts are not portable across domains. The official guide says: “Each SEATEXT AI account is linked to a single primary URL.” If you have a staging site and a production site, you need a separate account for each.

Why this matters: SeaText associates traffic with your account by domain. If you use the same code on two domains, the AI cannot reliably attribute visitors. Your data becomes mixed, and sync errors appear.

How to fix it: Create a separate SeaText account for every domain you use. Copy the JavaScript snippet from each account individually. Then paste the correct snippet into the matching Odoo website.

Practical scenario: You run a development copy at dev.example.com and the live site at example.com. You must create two SeaText accounts—one for each URL. Never share a snippet between them.

Mistake #2: Pasting the Code in the Wrong Odoo Module

The integration guide says to log in to Odoo and access the “Website” module. Some users paste the code into backend settings, a custom module, or an HTML block outside the Website module. The script then never runs.

Why this matters: SeaText's embed code is designed to load on the frontend of your website. Odoo's backend pages do not process visitor behavior, so the AI stays inactive.

How to fix it: Open the Website module, navigate to the page you want to edit, and click “Edit.” Scroll through the “Blocks” panel to the “Dynamic Content” section. Drag the “Embed Code” module into the page. Then click “Edit” on that module and paste the SeaText code.

Check the exact location: the guide repeats this step to emphasize it. Do not place the snippet in a custom HTML block outside Dynamic Content.

Mistake #3: Forgetting the "Hide on Desktop" Setting

After pasting the code, the guide says to select “Hide on Desktop” in the “Visibility” section. If you skip this, the empty embed block may appear as a blank or broken element on desktop screens.

Why this matters: The block is only there to load the script. Visitors should never see it. An empty box can make your site look unprofessional and confuse users.

How to fix it: After pasting the code and clicking “Save,” go to the right panel. Find the “Visibility” section and check “Hide on Desktop.” Then click “Save” once more.

Note: The guide lists this as Step 6. It is easy to forget, but the two-step save is essential for a clean page.

Mistake #4: Not Saving After Each Step

Odoo's editor requires two saves for this integration. The first save applies the pasted code. The second save applies the visibility change. If you skip the second save, your visibility setting may not persist, and the script may still load in a visible block.

Why this matters: A missing save means your configuration is incomplete. The SeaText script may load, but the page will show an empty element.

How to fix it: Always click “Save” after pasting the code. Then adjust the visibility setting and click “Save” again. Do not combine these steps into one quick save.

Practical tip: After the second save, refresh the page in your browser to confirm the script activates.

Mistake #5: Testing on Localhost or Dynamic Development Domains

The guide says: “Development URLs, such as localhost, are restricted for security reasons. Ensure you use a valid, real domain for these cases.” Dynamic development domains may also fail because SeaText cannot reliably associate traffic with your account.

Why this matters: Localhost is not a public domain. SeaText blocks it to prevent abuse and misattribution. If you test on localhost, skip this and test on a real domain instead.

How to fix it: Use a valid, real domain for testing. If you need a staging environment, use a subdomain like staging.example.com and create a separate SeaText account for it.

Decision criteria: Always ask, “Is this a domain that real visitors can reach?” If not, create a new account for a real domain before integrating.

Mistake #6: Skipping the Page Refresh After Installation

The source pack ends with an important note: “Visit or refresh y…”—the full instruction is to visit or refresh your page after installation. This activates the AI. If you don't, the script loads but remains inert.

Why this matters: SeaText's integration is secure by design. The AI stays inactive until the page is visited or refreshed. That step is part of the official process, not an optional extra.

How to fix it: After completing both saves, refresh the page in your browser. You should see no visible block, and the script will start collecting data.

Limitations: If you refresh once and nothing changes, double-check the earlier steps. Verify the correct snippet is pasted and the hide-on-desktop setting is saved.

Key Facts About SeaText and Odoo Integration

Step-by-Step: The Correct Connection Process

1. Create a SeaText account for your production domain.
2. Copy the JavaScript code snippet from your SeaText dashboard.
3. Log in to Odoo and open the Website module.
4. Navigate to the page you want to edit and click Edit.
5. Scroll to Dynamic Content in the Blocks panel.
6. Drag the Embed Code module into the page.
7. Click Edit on the module and paste the SeaText code.
8. Click Save.
9. In the Visibility section, select "Hide on Desktop".
10. Click Save again.
11. Refresh the page to activate the AI.

FAQ: Common Questions About SeaText + Odoo

Why is my SeaText script not working in Odoo?

Most likely you skipped a save or used a development domain. Check that you placed the code in the Website module, saved twice, and refreshed the page.

Can I use one SeaText account for both staging and production sites?

No. Each SeaText account is linked to a single primary URL. Create separate accounts for each domain.

Do I need to hide the embed block on desktop?

Yes. The official guide says to select "Hide on Desktop" to prevent display issues.

What happens if I paste the code in the wrong Odoo module?

The script will not load. Move the embed code to the Website module's Dynamic Content section.

How do I avoid data duplication in Odoo?

Data duplication usually comes from using the same account on multiple domains. Use a dedicated account per domain and follow the integration steps exactly.

Can I test on localhost?

No. Development URLs like localhost are restricted for security reasons. Use a real domain.

What should I do after installing the script?

Visit or refresh the page. The AI activates only after that step.

Where can I find the official Odoo integration guide?

It is available at seatext.com/odoo-integration.