When to Use Separate SeaText Accounts for Odoo Staging and Production Domains

Your Decision Trigger: Separate Accounts Are the Default

If you run Odoo on both a staging domain and a production domain, create a separate SeaText account for each. SeaText links every account to one primary URL. That means one account cannot correctly serve two domains. Using one account for both will mix test data with live data, distort your analytics, and may violate your plan terms.

So the real question is not whether to separate — it is when you can safely skip it. The answer: almost never, unless you are only testing on a temporary domain that you will delete before launch.

Readiness Checklist: Are You Ready to Separate?

Use this checklist before you set up your second SeaText account. If you can tick every box, you are ready.

• You have a real, valid production domain. SeaText restricts development URLs like localhost for security. Use a live domain for both accounts.
• You know which domain is your primary URL for each account. Each account binds to exactly one domain.
• You have a separate email or access path for each account. This keeps logins and billing clear.
• You have a plan that covers two accounts. Check your pricing tier. Some plans may not include multiple accounts.
• You can paste a different code snippet on each site. The Odoo integration uses an embed code per account. Do not reuse the same snippet.
• You have a naming convention. For example, staging-yourbrand and prod-yourbrand.

Signs You Should Wait Before Separating

Do not create a second account yet if any of these apply:

• Your staging domain is temporary. If you use a throwaway subdomain for a one-off test, you may not need a permanent account. But remember: SeaText may not work reliably on dynamic development domains.
• You are still deciding on your production domain. Wait until the final URL is locked. Creating an account for a domain you will change later wastes setup effort.
• You have not confirmed your plan allows multiple accounts. Check pricing first. If it does not, you may need to upgrade or choose which environment gets the account.
• You are not yet running real traffic on staging. If staging is only for internal QA with no visitors, you might not need SeaText there at all.

How SeaText Handles Multiple Domains

SeaText explicitly states: if you need to use it on multiple domains — for example, a development domain and a production domain — you must create separate accounts for each domain. Each account is linked to a single primary URL.

This is not a limitation you can work around with clever configuration. The code snippet you paste into Odoo is tied to your account. When you paste the same snippet on two domains, SeaText cannot reliably associate traffic with the correct account. That breaks attribution and can pollute your conversion data.

Main Options and Trade-Offs

Choose Separate Accounts If...

Choose separate accounts if you answer yes to any of these:

• You run A/B tests or CRO experiments on staging before pushing to production.
• You need to compare conversion data between environments.
• You have different team members responsible for staging versus production.
• You want to avoid any risk of test data contaminating your live analytics.

Choose One Account If...

Choose one account if:

• You only need SeaText on production.
• Your staging domain is a temporary test that you will delete.
• Your plan does not support multiple accounts and you cannot upgrade.

Practical Scenarios

Scenario 1: Ecommerce Store with Active Staging

You run a Shopify-like store on Odoo. Your staging domain is staging.yourstore.com and production is yourstore.com. You test new product copy on staging. You need separate accounts. Otherwise, your staging tests will show up in production analytics.

Scenario 2: Agency Managing Multiple Client Sites

You manage Odoo for several clients. Each client has a staging and production domain. You need a separate SeaText account for each domain — not just per client. That means two accounts per client if you want both environments covered.

Scenario 3: Pre-Launch Startup

You are still building your Odoo site. You have not launched. You only need SeaText on your staging domain for now. Create one account for staging. When you launch, create a second account for production. Do not try to reuse the staging account.

Limitations and When This Advice Does Not Apply

This guidance assumes you are using SeaText on Odoo websites. If you are not using Odoo, the same rule applies: one account per domain.

There is one exception: if you only need SeaText on one environment and you never plan to use it on the other, you do not need two accounts. But if you think you might later, create both now to avoid rework.

Also note: SeaText restricts development URLs such as localhost. Dynamic development domains may not work properly. Use a real, valid domain for each account.

Key Facts

Frequently Asked Questions

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

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

What happens if I use the same snippet on both domains?

SeaText may not reliably associate traffic with your account. Your data will be mixed and inaccurate.

Does it cost more to have two accounts?

It depends on your plan. Check the pricing page to see if multiple accounts are included or if you need to pay per account.

Can I use localhost for staging?

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

What if my staging domain changes frequently?

Dynamic development domains may not work properly. Use a stable, real domain for your staging account.

Do I need separate accounts for separate business units?

Yes. If each business unit runs on a different domain, each domain needs its own SeaText account.

How do I set up the second account?

Create a new SeaText account, copy the code snippet for that account, and paste it into the Embed Code module on your Odoo staging site. Repeat for production with a different account.