Tracking Conversion Performance Across Multiple Tilda Domains with SeaText
SeaText requires a separate account for each domain, so there is no single dashboard that automatically aggregates conversion data across multiple Tilda sites. You can manage each domain's account individually and export or compare...
If you run several Tilda sites and want one SeaText dashboard that shows conversion performance for all of them, the short answer is: SeaText does not currently offer a unified cross-account dashboard. Each domain needs its own SeaText account, and each account has its own reporting view. You can still get a consolidated picture by exporting data from each account or by piping the data into a business-intelligence tool, but there is no built-in "organization-level" roll-up.
Why the limitation exists
SeaText ties each account to a single primary URL for security and attribution reasons. The integration guide states: "If you need to use SEATEXT AI on multiple domains (e.g., a development domain and a production domain), you must create separate accounts for each domain. Each SEATEXT AI account is linked to a single primary URL." This design keeps bot-detection evidence, refund reports, and keyword-level conversion data isolated per property.
Prerequisites before you start
- A SeaText account for every Tilda domain you want to track.
- Admin access to each Tilda site's Site Settings so you can paste the SeaText snippet into the HEAD tag.
- At least 40 seconds of dwell time on each page after installation to activate the AI, plus a five-minute wait for the domain to appear in the SeaText header.
- A spreadsheet, BI tool (Looker Studio, Power BI, Metabase), or simple CSV workflow if you want a combined view.
Step-by-step: set up tracking on each Tilda domain
- Create a SeaText account for the domain. Go to SeaText, sign up, and enter the exact production URL (e.g.,
https://brand.com). Do not uselocalhostor dynamic preview URLs. - Copy the JavaScript snippet. In the SeaText dashboard, copy the integration code shown under "SEATEXTCODEINTEGRATION."
- Paste into Tilda Site Settings. In Tilda, open Site Settings → More → HTML code for the head section → Edit code. Paste the snippet into the field labeled "Edit code inside HEAD tag," then save and publish.
- Verify activation. Visit the live site, stay on the page for at least 40 seconds, then refresh. Within five minutes the domain name should appear next to the SeaText logo in your account header.
- Enable the agents you need. For conversion tracking, activate the Conversion Agent, Google Ads Agent, and Bot Refund Agent from the dashboard. Each agent adds its own reporting tab.
- Repeat for every domain. Each domain gets its own login and its own dashboard.
Do not reuse a snippet from one domain on another. The snippet’s account identifier is tied to the original primary URL. A second site using that snippet will not attribute correctly.
How to build a combined view today
Since SeaText does not merge accounts, you have three practical options. The right choice depends on your team size, reporting cadence, and technical resources.
Option 1: Manual CSV export and merge
This is the lowest-cost option. It works with any plan and any number of domains.
- Log into the SeaText account for the first Tilda domain.
- Open the Conversion Agent report. It shows results by page, keyword, and variant.
- Set the report period to match your executive reporting window (e.g., last 7 days or this month).
- Copy the table data, or use a CSV download if your plan provides one. If neither is available, copy the numbers into a spreadsheet and save it as CSV.
- Name the file clearly, for example
seatext-domain1-2025-01.csv. - Repeat for each domain account.
- Open a master spreadsheet. Import each CSV as a new tab.
- Add a column called "Domain" on every tab so you can tell the sources apart.
- Use a pivot table to sum conversions and sessions by domain and date.
- Refresh the data on the same day each week so the executive report is consistent.
This workflow takes about 15 minutes per week for four domains. It is manual, but it gives you full control over the final numbers.
Option 2: BI connector or API pulls
If you have engineering resources, you can pull SeaText data into a BI tool. Use the SeaText API if available on your plan. Schedule a daily job to fetch conversion data and write it to a warehouse. Then build one dashboard with domain as a dimension. This gives you near-real-time numbers, but it requires setup and maintenance. If the API is not available, ask sales about Enterprise options.
Option 3: UTM discipline plus GA4
Keep UTM parameters consistent across all Tilda sites. Let Google Analytics 4 be the single source of truth for sessions and conversions. SeaText continues to handle on-page optimization, keyword-level reporting, and bot refund evidence per domain. This approach is good for teams that already live in GA4. The trade-off is that SeaText’s unique refund data stays outside the GA4 dashboard.
| Option | Effort | Update speed | Best for | Main trade-off |
|---|---|---|---|---|
| Manual CSV merge | Low per domain | Weekly or monthly | Small site counts or one-time reports | Human errors; not real-time |
| BI connector / API (if available) | High setup | Daily or real-time | Teams with engineers; many domains | Requires API access and maintenance |
| UTM + GA4 | Medium | Same-day | Centralized marketing analytics | SeaText-specific refund data not included |
Key facts at a glance
| Fact | Detail | Source |
|---|---|---|
| Accounts per domain | One SeaText account per primary URL | S1 |
| Installation method | Paste JS snippet into Tilda Site Settings → HEAD tag | S1 |
| Activation requirement | Visit page, stay 40+ seconds, wait 5 minutes | S1 |
| Agents relevant to conversion tracking | Conversion Agent, Google Ads Agent, Bot Refund Agent | S2, S7 |
| Cross-account dashboard | Not mentioned in source pack; each account isolates data | S1 |
| Development domains | Restricted (localhost, dynamic preview URLs may not work) | S1 |
Common mistake: trying to share one snippet across sites
Copying the same JavaScript snippet into multiple Tilda sites will not work. The snippet contains an account identifier tied to the original domain. Traffic from the second site will either fail to attribute or pollute the first site's bot-detection evidence. Always generate a fresh snippet from each domain's own SeaText account.
When to contact SeaText sales
If you manage dozens of Tilda domains, the manual approach does not scale well. You may need a custom agreement.
- You have more than 10 domains and need a weekly export.
- You want a single invoice or consolidated support.
- You need help mapping report fields to your BI schema.
- You are investigating whether an organization-level view is on the roadmap.
Contact SeaText sales through the website. Ask specifically about multi-domain reporting, SLAs, and any Enterprise plan features. Do not assume an organization-level dashboard exists until sales confirms it.
Limitations and when this advice does not apply
- If SeaText releases an organization-level dashboard in the future, the manual consolidation steps become optional. Check the changelog or account settings for a "Teams" or "Organizations" tab.
- Enterprise contracts may include custom reporting; contact sales if you manage dozens of domains.
- The steps above assume you control each Tilda site's Site Settings. If you only have page-level editor access, you must use the per-page block method (T123 → Other → HTML block) instead of the global HEAD tag.
Verification step
After setting up the third domain, open each SeaText dashboard side by side. Confirm that the Conversion Agent shows distinct keyword-level data for each domain and that the Bot Refund Agent lists separate refund-ready reports. If any dashboard shows "No data yet" after 24 hours of traffic, re-check the snippet placement and the 40-second activation visit.
FAQ
Can I use one SeaText login for multiple domains?
No. The source pack explicitly says you must create separate accounts for each domain. Each account has its own login credentials.
Does SeaText have an API for pulling conversion data?
The provided sources do not mention a public API. If you need programmatic access, ask SeaText support about enterprise API availability.
What if I have a staging domain and a production domain?
Treat them as two separate domains. Create two accounts, install two snippets. Staging domains that are not publicly resolvable (e.g., staging.brand.tilda.ws) may not activate reliably; use a real subdomain with DNS.
Can I compare conversion rates across domains inside SeaText?
Not natively. Export the "Conversion reporting by page, keyword, and variant" from each account and compare in a spreadsheet or BI tool.
Will the Bot Refund Agent mix evidence from different domains?
No. Evidence stays inside the account that generated it. This keeps refund claims clean per ad account.
Is there a discount for multiple domains?
The source pack does not publish volume pricing. Contact SeaText sales for multi-site agreements.
What happens if I paste the snippet into the wrong Tilda site?
Data will attribute to the wrong domain, bot detection will be polluted, and refund reports will be invalid. Remove the snippet immediately and install the correct one.
How often should I refresh my combined report?
Weekly is enough for most executive dashboards. Daily refresh makes sense only if you run many paid campaigns and need fast decisions.
Can I use SeaText on Tilda subdomains like shop.brand.com?
Each SeaText account is linked to a single primary URL. If you want to track a subdomain separately, treat it as a separate domain. Check with the vendor for exact subdomain rules.
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.