What Happens If You Use the Same SeaText Account for Two Odoo Domains?
Using the same SeaText account on two Odoo domains causes data mixing, incorrect tracking, and may violate your plan terms. Each SeaText account is linked to a single primary URL, so sharing it across...
Symptoms You Might Notice
If you have pointed two Odoo domains at the same SeaText account, you will likely see problems before you notice any error message. The AI may serve the same copy to both sites, or it may stop working on one domain entirely.
Common symptoms include mixed analytics data, where visits from two domains appear in a single report and make performance numbers unreliable. You may also notice that the AI copy on one domain reflects content intended for the other, or that the tracking script fails to fire consistently on either site.
Another sign is that your conversion data in Meta or Google CAPI shows purchases attributed to the wrong domain. This makes it nearly impossible to know which site is actually driving results.
Why This Happens
SeaText ties each account to one primary URL. When you install the SeaText JavaScript snippet on an Odoo site, the script reads the current domain and matches it against the account's registered URL. If two domains share one account, the script cannot tell which domain the traffic belongs to.
Odoo lets you run multiple websites from a single instance, and each website can have its own domain. But SeaText does not support linking multiple domains to a single account. The integration was designed with a one-account, one-domain model in mind.
This is not an Odoo limitation. It is a SeaText architecture choice. The account system uses the domain as the primary key for all traffic routing, copy assignment, and conversion relay.
Likely Causes of Conflicts
The most common cause is a developer setting up a staging or development domain and reusing the production SeaText account code. They assume the script will work the same way on both domains. It does not.
A second cause is an Odoo multi-site setup where two branded domains run on the same database but share one SeaText installation snippet. The script fires on both domains, but SeaText sees the traffic as coming from one source.
A third cause is using a dynamic or temporary development domain. SeaText explicitly restricts localhost and dynamic development domains because it cannot reliably associate traffic with your account. If your Odoo dev domain changes often, the account link will break repeatedly.
How SeaText Account Linking Works
Each SeaText account is linked to a single primary URL. When you copy the JavaScript snippet from your SeaText dashboard, that code contains your account identifier tied to that specific domain.
The script runs in the visitor's browser, reads the page's domain, and sends that signal back to SeaText's servers. SeaText then matches the domain to your account and serves the appropriate AI copy, runs split tests, and relays conversions. If the domain does not match, the signal has nowhere to go.
This is why the source documentation states: "Each SEATEXT AI account is linked to a single primary URL" and "To use SEATEXT AI on several websites, create one account for each website."
Corrective Actions
If you have already shared an account across two Odoo domains, the first step is to stop. Remove the SeaText script from the secondary domain immediately to prevent further data mixing.
Next, create a separate SeaText account for the second domain. Each domain needs its own account and its own JavaScript snippet. Copy the new snippet from the second account's dashboard and paste it into the Odoo editor for that domain's website.
After installing the new snippet, verify that the script fires correctly by checking the browser console and the SeaText dashboard for both domains. Each domain should now show its own isolated traffic and conversion data.
If you were using the same account for a development domain and a production domain, move the development site to its own account or use a valid, real domain. SeaText restricts localhost and dynamic development domains for security reasons.
How to Set Up Multiple Domains Properly
Setting up SeaText on multiple Odoo domains follows a simple rule: one account per domain. Here is the process.
- Create a SeaText account for each Odoo domain you want to optimize.
- Log into each account and copy the JavaScript snippet provided in the dashboard.
- In Odoo, open the Website module for the first domain and navigate to the page editor.
- Drag the "Embed Code" module from the Dynamic Content section into your layout.
- Click the Edit button in the right panel and paste the SeaText code snippet.
- Select "Hide on Desktop" in the Visibility section if you only want the block on mobile, then click Save.
- Repeat steps 3 through 6 for each additional domain using its own account's snippet.
Each snippet is domain-specific. Pasting the wrong snippet on the wrong domain will not cause data mixing, but it also will not activate correctly because the domain will not match the account.
Limitations and Edge Cases
SeaText does not support a single account spanning multiple domains under any plan. This is not a premium-feature restriction; it applies to all accounts. The one-account, one-domain model is built into the core architecture.
Development URLs such as localhost are restricted. If your Odoo instance uses a temporary or dynamic development domain, SeaText may not be able to associate traffic reliably. You must use a valid, real domain for the integration to work.
If you run a multi-tenant Odoo setup where subdomains serve different clients, each subdomain counts as a separate domain and needs its own SeaText account. Dynamic subdomains that change per session or user will not function properly.
The source documentation does not specify pricing for multiple accounts. Check with SeaText for current pricing details on additional accounts.
Frequently Asked Questions
Can I use one SeaText account for my main Odoo domain and a staging domain?
No. Each domain needs its own SeaText account. Using one account for both will cause tracking conflicts and data mixing. Create a separate account for the staging domain and install its unique snippet there.
What if I accidentally installed the same SeaText code on two Odoo domains?
Remove the script from the secondary domain immediately. Then create a new SeaText account for that domain and install its specific snippet. Check your analytics to see if past data is mixed; you may need to exclude the affected time range from reports.
Does SeaText support subdomains on Odoo?
Each subdomain is treated as a separate domain and requires its own SeaText account. Dynamic subdomains that change frequently may not work reliably because SeaText cannot consistently associate traffic with a single account.
Why does SeaText restrict localhost and development domains?
SeaText restricts these for security reasons and because it cannot reliably associate traffic from temporary or local addresses with your account. You must use a valid, real domain for the integration to function correctly.
How do I install SeaText on a second Odoo domain?
Create a new SeaText account for the second domain, copy its JavaScript snippet, and paste it into the Odoo Website editor using the Embed Code module under Dynamic Content. Save and verify the script fires on the new domain.
Will my conversion data be accurate if I use separate accounts?
Yes. Each account tracks traffic and conversions only for its registered domain. This keeps your analytics clean and ensures that Meta and Google CAPI receive correct purchase data from the right site.
Can I manage multiple SeaText accounts from one dashboard?
The source documentation does not specify a unified dashboard for multiple accounts. Check with SeaText for details on managing accounts across domains.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.