How to Access SeaText Configuration in Magento
SeaText configuration is managed in the SeaText dashboard (Main AI Hub), not inside Magento admin. Magento only hosts the JavaScript snippet. Install the snippet via Content > Design > Configuration > HTML Head, then...
SeaText does not add a configuration menu inside Magento. The Magento admin is only used to paste the SeaText JavaScript snippet into the HTML Head > Scripts and Style Sheets field. All AI activation, variant editing, translation settings, and agent parameters are controlled from the SeaText Main AI Hub after you log in at seatext.com.
Open the SeaText Main AI Hub to manage every SeaText setting for your Magento store — activation, variants, and agent parameters all live there.
Install the SeaText snippet in Magento (prerequisite)
- Log in to your Magento admin panel.
- Navigate to Content > Design > Configuration.
- Select your main store view and click Edit.
- Expand the HTML Head section.
- Paste the SeaText JavaScript snippet into the Scripts and Style Sheets field.
- Click Save Configuration and flush Magento cache if prompted.
The snippet is a small piece of JavaScript. It loads on every page of your storefront. It does not change any Magento file or database row. It only tells the visitor's browser to contact SeaText.
Why configuration lives in the SeaText dashboard, not Magento
Magento is a server-rendered PHP application. Its admin panel stores settings in the core_config_data table. SeaText is a client-side AI layer. It rewrites text in the browser after the page loads. Because of that, SeaText settings cannot live in Magento's database.
Three reasons explain the split:
- Architecture. SeaText runs in the visitor's browser. It needs a central cloud brain to coordinate variants, languages, and experiments across many visitors. That brain is the Main AI Hub.
- Client-side rewriting. SeaText swaps headlines, CTAs, and product copy after the HTML arrives. Magento never sees the change. So there is nothing for Magento to store.
- Security and multi-tenant model. Each SeaText account is tied to one primary domain. Configuration is scoped per account. This keeps one store's experiments from leaking into another store's traffic.
Magento only acts as the delivery vehicle for the snippet. The snippet is the bridge between your storefront and the SeaText cloud.
Access SeaText configuration in the Main AI Hub
- Open seatext.com and log in with your SeaText account credentials.
- From the dashboard, click Main AI Hub (sometimes labeled AI Hub).
- Choose the website you connected (it appears next to the SeaText logo once the snippet is active).
- Click Configuration to adjust AI parameters, activate agents, or edit variants.
If you do not see your website name next to the logo after 10 minutes, contact SeaText support — the snippet may not be firing correctly.
How the Main AI Hub Configuration screen is organized
The Configuration screen is grouped by agent. Each agent has its own panel with on/off switches and parameter fields. Common panels include:
- CRO Optimizer. Controls A/B and multivariate tests on landing pages.
- Google Ads Agent. Maps ad keywords to page variants.
- Translation Agent. Picks target languages and tone.
- Bot Refund Agent. Sets bot-detection sensitivity.
- Visitor Source Agent. Defines UTM and referrer rules.
Each panel has three zones: a master toggle, parameter inputs, and a save button. Changes apply to new visitors within minutes. Returning visitors see the new variant on their next page load.
What each agent parameter does in practice
Agent parameters are the knobs you turn inside each panel. They change behavior without code edits.
- Keyword rules. Match ad keywords to specific headlines or offers. Useful for Google Ads campaigns with many keyword groups.
- Target languages. Pick which of the 125 supported languages the Translation Agent should serve.
- UTM-based personalization. Show different CTAs to visitors from email, Meta, or partner sites.
- Bot-detection sensitivity. Adjust how strict the Bot Refund Agent is. Higher sensitivity catches more bots but may flag edge cases.
- Variant approval. Review and approve the first round of automatic translations and copy variants before they go live.
These controls live entirely in the SeaText cloud dashboard. Magento never stores them.
How configuration changes affect your Magento storefront
When you save a change in the Main AI Hub, SeaText updates its cloud config. The next time a visitor loads a Magento page, the snippet pulls the new config and applies it. There is no rebuild, no deploy, and no cache flush on the Magento side.
Propagation is fast for most changes:
- Agent toggles. Live within 1–2 minutes.
- Parameter edits. Live within 1–2 minutes.
- New variants. Live after the next visitor session (about 40 seconds on page).
- Language additions. Live after the Translation Agent reprocesses the page.
Magento's own cache layers (block HTML, full page cache, Varnish) do not interfere. SeaText runs after the cached HTML reaches the browser. A CDN also does not block SeaText, because the snippet is part of the HTML payload.
Magento-specific configuration considerations
Magento has its own caching and multi-store features. A few points to keep in mind:
- Full Page Cache. SeaText works with FPC enabled. The snippet is part of the cached HTML, so it loads on every cache hit.
- Varnish. Same as FPC. SeaText runs client-side, so Varnish does not strip the snippet.
- CDN. The snippet is inline JavaScript. Most CDNs pass it through unchanged.
- Headless Magento / PWA Studio. SeaText still works. Paste the snippet into the head of your PWA shell or inject it via a tag manager.
- Multi-store setups. Each store view needs its own snippet from a separate SeaText account. One account equals one primary domain.
- Staging vs production. Use separate SeaText accounts for staging and production. SeaText blocks localhost and dynamic tunnel domains for security.
- Role-based access. Inside the SeaText account, you can invite teammates with different roles (admin, editor, viewer). This keeps Magento developer access separate from marketing edits.
Verify the integration is working
- Visit your Magento storefront several times and stay on a page for at least 40 seconds — this activates the AI and links it to your account.
- Wait five minutes, then refresh the SeaText Main AI Hub. Your store name should appear next to the SeaText logo.
- Open the browser dev tools console on your site; you should see SeaText network requests confirming the snippet loads.
If the store name does not appear after 10 minutes, re-check the snippet placement in Content > Design > Configuration > HTML Head and ensure Magento cache is cleared.
Common mistakes and troubleshooting
| Mistake | Result | Fix |
|---|---|---|
| Pasting snippet in wrong field (e.g., Footer Scripts) | AI never loads | Use HTML Head > Scripts and Style Sheets only |
| Forgetting to flush Magento cache after save | Old HTML served, snippet missing | Run bin/magento cache:flush or use admin Cache Management |
| Using localhost or dynamic dev domain | SeaText blocks activation for security | Use a real, public domain; create separate SeaText accounts per domain |
| Expecting a Magento-side settings page | Wasted time searching admin | All settings are in SeaText Main AI Hub |
Limitations and scope
- One SeaText account = one primary domain. Multiple domains (staging, production, regional) require separate accounts.
- Development URLs such as
localhostor dynamic tunnel domains are restricted and will not activate. - Magento 1 is not supported; instructions apply to Magento 2 (Adobe Commerce) only.
- SeaText does not modify Magento database content — it rewrites text client-side via JavaScript after page load.
FAQ
- Where do I find the JavaScript snippet?
- In your SeaText account under the installation section for Magento. Copy the code labeled
SEATEXTCODEINTEGRATION. - Can I configure SeaText per store view in a multi-store setup?
- Yes. Paste a different snippet (from a separate SeaText account) into each store view's HTML Head field.
- Do I need developer access to change AI settings later?
- No. All ongoing configuration — activating agents, editing variants, adding languages — happens in the SeaText dashboard without touching Magento code.
- How long before I see AI-generated variants?
- After the snippet is live and you have visited the site (40+ seconds), SeaText generates the first variant batch within minutes. Check Variants Edit in the dashboard.
- What if I uninstall the snippet?
- SeaText stops executing on your site. Your dashboard data and variants are preserved; re-adding the snippet restores functionality.
- Is there a Magento module or extension to install?
- No. SeaText uses a universal JavaScript snippet; no Magento module, composer package, or extension is required.
- How do I change my primary domain?
- Create a new SeaText account for the new domain. SeaText accounts are locked to one primary URL for security. Migrate your settings manually or contact support for help.
- How do I rotate or replace the snippet?
- Copy the new snippet from your SeaText account. Paste it into the same HTML Head > Scripts and Style Sheets field, replacing the old code. Save and flush cache.
- Does SeaText work with Magento staging environments?
- Only if staging uses a real public domain. Localhost and dynamic tunnel URLs are blocked. Use a separate SeaText account for staging.
- Will Varnish or a CDN block SeaText?
- No. SeaText runs in the browser after the HTML loads. Varnish and CDNs serve the snippet as part of the page; they do not interfere with rewriting.
- Does SeaText work with headless Magento or PWA Studio?
- Yes. Inject the snippet into the head of your PWA shell or via a tag manager. SeaText runs client-side, so the rendering layer does not matter.
- Can I give my marketing team access without sharing Magento admin?
- Yes. Invite teammates to your SeaText account with roles like admin, editor, or viewer. They can change AI settings without Magento access.
- Does SeaText write to the Magento database?
- No. SeaText rewrites text in the browser only. Your Magento catalog, CMS, and config data stay untouched.
- What happens to my variants if I cancel my SeaText account?
- Dashboard data and variants are preserved for a grace period. Reactivating the account restores access. After the grace period, data is deleted.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Learn more
Visit the website for more information.