What Are the Prerequisites for Integrating SeaText with Odoo?

Why These Prerequisites Exist

SeaText connects to your Odoo instance by injecting AI-driven content optimization scripts into your website pages. The integration requires SeaText to authenticate with your Odoo environment, verify your account status, and access your site traffic data. Each prerequisite exists because of how that connection works.

An active SeaText account proves that you have permission to use the service and provides the billing context for your integration. Administrative access to Odoo lets you modify website settings, install modules, and configure the embed code without encountering permission walls. Your Odoo API URL and database credentials are the technical keys that allow SeaText to read visitor behavior and serve personalized content variants.

If any of these three elements is missing, the integration either will not start or will produce errors that block activation. The good news is that you only need to set them up once before activation.

An Active SeaText Account

Before you can install any code on your Odoo website, you must have a SeaText account linked to the domain where you plan to deploy the integration. Each SeaText account is tied to a single primary URL. This means if you plan to use SeaText on multiple domains, you need a separate account for each one.

Creating an account is free to start. You can sign up on the SeaText homepage. Once registered, you will receive a unique JavaScript code snippet that identifies your account and routes traffic data correctly. This snippet is what you paste into your Odoo website editor during the installation steps.

If you do not have an account yet, the integration cannot proceed. The account also controls which agents are active, how conversion data is reported, and which domain permissions are granted.

Administrative Access to Your Odoo Instance

Installing and configuring the SeaText embed code requires the ability to edit your website pages in Odoo. Specifically, you need access to the Website module, the ability to drag and drop content blocks, and permission to save changes to individual pages.

In practice, this means you should be logged in as a user with administrator rights or a user who has been granted website editor permissions. Standard Odoo users who only have access to CRM, Sales, or Inventory modules will not be able to complete the installation steps without elevated permissions.

If you are setting up Odoo for the first time, make sure your user account includes access to the Website application. You can check this under Settings > Users > Access Rights in your Odoo dashboard.

Your Odoo API URL and Database Credentials

SeaText needs to know where your Odoo instance lives and how to talk to it. The API URL is the web address you use to access your Odoo dashboard, such as https://yourcompany.odoo.com or your custom domain if you host Odoo yourself.

Your database name is the identifier Odoo uses for your instance. When you log into Odoo, you typically see a database selector screen. The database name appears in the URL after the ?db= parameter, or it may be part of your subdomain. For example, if you see https://mycompany.odoo.com/web?db=mycompany, then your database name is mycompany.

You do not need to manually share these credentials with SeaText during the basic JavaScript integration. However, having them ready helps when you configure advanced features like Conversion Relay (CAPI), where SeaText needs to forward purchase data to Meta and Google platforms. In those cases, you will input specific API credentials into the SeaText dashboard.

Domain Requirements and Restrictions

SeaText accounts are tied to real, publicly accessible domains. Development URLs such as localhost, .local, .test, or IP addresses are restricted for security reasons. This restriction exists because SeaText cannot reliably associate traffic with your account when the domain is not publicly routable.

If you are building the integration in a staging environment, use a real subdomain with a valid SSL certificate. For example, use staging.yourdomain.com instead of localhost:3000. Once the integration is verified on the staging domain, you can copy the same configuration to your production domain, or create a separate SeaText account for each domain.

Dynamic development domains provided by platforms like ngrok or similar tunneling services may not function properly either, because they generate new URLs on each session and break the traffic-to-account association that SeaText relies on.

Odoo Version Compatibility

SeaText integrates through your Odoo website module using standard JavaScript embed code. This method is compatible with Odoo versions 14 through 19, which includes both the Community and Enterprise editions. The integration does not require a custom module installation in most cases.

If you are running an older version of Odoo, check whether the Website module is installed and active. Some Odoo deployments disable the website application by default. You can verify this by navigating to the Apps section in your Odoo dashboard and searching for "Website."

Readiness Checklist

Before you begin the integration, confirm each of the following items is in place:

• SeaText account created and logged in at seatext.com
• JavaScript code snippet copied from your SeaText dashboard
• Administrator access to the Odoo Website module
• Odoo API URL identified (your Odoo web address)
• Database name confirmed (visible in the Odoo login screen or URL)
• Valid production domain (no localhost or development URLs)
• SSL certificate active on your domain (HTTPS required)
• Odoo version 14 or newer with the Website module installed

Common Mistakes to Avoid

Many integration delays come from skipping the account setup step. Users sometimes try to install the SeaText code before creating an account, which means there is no account identifier in the snippet and traffic data has nowhere to go.

Another frequent issue is using localhost or a temporary tunnel URL as the target domain. SeaText will reject this during the connection verification step because it cannot match the traffic source to a valid account.

A third mistake is attempting the installation with a standard user account that lacks website editing permissions. If you cannot drag the Embed Code block into your page editor, your account permissions are the likely cause.

Key Facts

FAQ

Do I need a paid SeaText plan to integrate with Odoo?

You need an active SeaText account, but the integration steps themselves are the same for all account tiers. Some advanced features like Conversion Relay or VPN detection may require higher-tier plans.

Can I use the same SeaText account for Odoo and my other websites?

No. Each SeaText account is linked to a single primary domain. If you want to use SeaText on multiple websites, you need separate accounts for each one.

What happens if I try to use localhost for testing?

SeaText will not associate traffic with your account from a localhost URL. You will need to use a real, publicly accessible domain with HTTPS enabled.

Do I need to install a module in Odoo?

For the basic JavaScript embed, no custom Odoo module is required. You use the built-in Website module and the standard Embed Code block to place the SeaText snippet.

How long does it take to complete the prerequisites?

Creating a SeaText account takes a few minutes. Confirming your Odoo access level and identifying your database name takes another few minutes if you know your Odoo environment. The entire checklist can be completed in under 30 minutes.

What if I do not have access to the Website module in Odoo?

Contact your Odoo administrator to request website editor permissions. Without this access, you cannot complete the integration steps.

Can I integrate SeaText with a self-hosted Odoo instance?

Yes, as long as your self-hosted instance is publicly accessible via a real domain with SSL and runs Odoo version 14 or newer.