How to Share Browser Console Logs with SeaText Support Effectively
Export console logs by opening Developer Tools (F12), selecting the Console tab, right-clicking and choosing "Save as" to create a timestamped log file. Include your browser version, SeaText snippet configuration, and the exact steps...
Quick answer: export and attach a complete console log
Open your browser's Developer Tools with F12 (or Cmd+Option+I on Mac), switch to the Console tab, right-click anywhere in the log area, and choose Save as… to write a .log file. Attach that file to your support ticket along with the browser name and version, the SeaText snippet you pasted into your SPA, and a short description of what you were doing when the problem appeared.
Why a clean console export matters for SeaText
SeaText runs as an asynchronous JavaScript snippet that mounts on your single-page application (React, Vue, Angular, or plain HTML). The snippet writes to localStorage, makes cross-origin requests, and rewrites page content in real time. When something behaves unexpectedly — missing translations, variant not swapping, bot-refund agent not firing — the browser console is the only place that shows load order, network failures, CORS blocks, or JavaScript exceptions. A raw screenshot misses timestamps, stack traces, and filtered messages; a saved log preserves everything.
Step-by-step: capture a useful log file
- Reproduce in a clean session. Open an incognito/private window, disable extensions that inject scripts, and navigate to the page where SeaText is installed.
- Open Developer Tools before the action. Press F12, click the Console tab, and enable Preserve log so navigation doesn't clear history.
- Filter wisely. Keep All levels selected (Errors, Warnings, Info, Verbose). SeaText's own messages are logged at info level; hiding them removes clues.
- Trigger the issue. Perform the exact steps that caused the problem: page load, language switch, variant change, ad click, etc.
- Save the log. Right-click in the console pane → Save as… → name it
seatext-console-YYYYMMDD-HHMM.log. - Gather context. Copy the User-Agent string (
navigator.userAgentin console), note the SeaText snippet version (visible in the Network tab as the script request), and paste the snippet you embedded in yourindex.htmlor SPA entry point. - Attach to ticket. Open your SeaText support channel (dashboard chat, email, or help-center form) and attach the
.logfile plus the context block.
Fill-in-the-blank context template
Copy the block below into your ticket. Replace every bracketed placeholder with your actual values.
Browser + version: [e.g., Chrome 126.0.6478.114]
Operating system: [e.g., macOS 14.5, Windows 11 23H2]
SeaText snippet source: [dashboard → Installation → Copy snippet]
Framework + version: [React 18, Vue 3, Angular 17, plain HTML]
Snippet placement: [index.html <body> / main.tsx / bootstrap.js / other]
CSP headers: [paste Content-Security-Policy header value or "none"]
Reproduction steps:
1. [step one]
2. [step two]
3. [step three]
Expected behavior: [what should happen]
Actual behavior: [what happens instead]
Attachments checklist:
☐ console.log file
☐ HAR export (if network errors)
☐ localStorage.json (run copy(JSON.stringify(localStorage,null,2)))
☐ screenshot of Network tab filtered for SeaText request
☐ snippet exactly as deployedSupport ticket template (copy-paste)
Subject: SeaText issue — [short description, e.g., "translation not applying on variant switch"]
Environment:
- Browser: [browser + version]
- OS: [operating system]
- Framework: [framework + version]
- Snippet location: [where you pasted the snippet]
- CSP: [header value or "none"]
Steps to reproduce:
1. [step one]
2. [step two]
3. [step three]
Expected: [describe expected outcome]
Actual: [describe actual outcome]
Attached:
- seatext-console-YYYYMMDD-HHMM.log
- network.har (optional)
- localStorage.json (optional)
- deployed-snippet.txt (exact snippet from your repo)
Additional notes: [anything else support should know]Annotated sample console log excerpt
The example below shows the structure SeaText support expects. Timestamps, log levels, and SeaText prefixes are preserved. Lines marked illustrative are not guaranteed to appear in every project.
[2024-07-15T14:32:10.123Z] INFO [SeaText] Snippet injected, async load started
[2024-07-15T14:32:10.456Z] INFO [SeaText] Fetching configuration from https://api.seatext.com/v1/config (illustrative URL)
[2024-07-15T14:32:10.789Z] INFO [SeaText] Configuration received, initializing agents
[2024-07-15T14:32:11.012Z] INFO [seatext-translation] Language set to 'es-ES'
[2024-07-15T14:32:11.015Z] INFO [seatext-cro-optimizer] Variant 'hero-v2' selected for campaign 'summer-sale'
[2024-07-15T14:32:11.020Z] WARN [seatext-bot-refund] Bot score 0.87 — session flagged for review
[2024-07-15T14:32:11.025Z] ERROR [seatext-translation] Failed to fetch translation bundle: TypeError: Failed to fetch
at translate.js:245:17 (illustrative filename)
at async applyTranslations (translate.js:112:5)
[2024-07-15T14:32:11.030Z] INFO [SeaText] Visitor ID stored in localStorage
[2024-07-15T14:32:11.035Z] INFO [seatext-visitor-source] Referrer detected: google.com, campaign: summer-saleDecision table for common console or network errors
| Observed symptom | Likely cause | First action | When to escalate |
|---|---|---|---|
Console shows net::ERR_BLOCKED_BY_CLIENT for SeaText request | Ad blocker or privacy extension blocking script | Disable extensions, test in incognito | If it persists with extensions off, share HAR file |
Console shows CORS policy error on SeaText fetch | Server missing Access-Control-Allow-Origin header | Check Network tab for response headers | If headers look correct, attach HAR and CSP header |
Console shows TypeError: Failed to fetch from SeaText agent | Network offline, firewall, or CSP connect-src block | Verify internet, check CSP connect-src | If CSP allows, provide HAR and localStorage dump |
| No SeaText prefixed lines appear at all | Snippet not loaded, wrong placement, or script error before init | Check Network tab for script request status 200 | If script loads but no logs, share console + snippet |
localStorage shows no visitor ID after load | Storage blocked, private mode, or script error before write | Run localStorage.getItem('visitorId') in console | If null, attach console log and CSP header |
| Translation or variant change produces no console output | Agent disabled in dashboard or scope misconfigured | Verify agent toggles in SeaText dashboard | If enabled, share log with reproduction steps |
What to include in the context block
- Browser + version (e.g., Chrome 126.0.6478.114)
- Operating system
- SeaText snippet source (dashboard → Installation → Copy snippet)
- Framework and version (React 18, Vue 3, Angular 17, etc.)
- Whether you load the snippet in
index.html<body>or via a framework-specific bootstrap file - Any Content-Security-Policy headers that might block inline scripts or
localStorage - Steps to reproduce, numbered
- Expected vs. actual behavior
Common mistakes that slow down diagnosis
| Mistake | Why it hurts | Fix |
|---|---|---|
| Sending a screenshot only | No timestamps, no stack traces, truncated lines | Always attach the .log file |
| Clearing console before saving | Loses the initial script-load sequence | Enable Preserve log before reproducing |
| Filtering to "Errors" only | SeaText logs at info/verbose level | Keep All levels visible |
| Omitting the snippet you actually use | Support can't verify async attribute, localStorage key, or version | Paste the exact snippet from your repo |
| Not mentioning CSP or ad-blockers | Blocked scripts look like SeaText failures | Share Content-Security-Policy header and extension list |
Verifying the snippet loads correctly
After you paste the SeaText snippet into your SPA entry point (per the SPA integration guide), open the Network tab, filter for the SeaText script request, and confirm:
- Status
200for the script request - Response contains the SeaText initialization code
- No CORS errors in Console
localStorageshows a visitor ID after first load
If any of these checks fail, include the Network tab HAR export (Right-click → Save all as HAR) alongside the console log.
Key facts about SeaText's client-side behavior
| Property | Detail | Source |
|---|---|---|
| Loading mode | Asynchronous script tag with async attribute | S1 |
| Storage | Writes a visitor ID to localStorage | S1 |
| Cross-origin | May request resources across domains; CSP must allow | S1 |
| SPA integration point | Insert snippet in index.html <body> or framework bootstrap | S1 |
| Verification steps | Build → serve → open DevTools Console & Network tabs | S1 |
| Agents that run client-side | CRO Optimizer, Bot Refund Agent, Translation Agent, Visitor Source Agent, etc. | S2, S4, S6 |
When the log won't help and what to do instead
- Server-side rendering errors: SeaText snippet runs in the browser; SSR logs belong in your backend.
- Network-level blocks (corporate proxy, firewall): Console shows
net::ERR_BLOCKED_BY_CLIENT; provide HAR file and IT team contact. - Third-party script conflicts: If another vendor mutates
windoworlocalStorage, isolate by disabling them one by one. - Mobile Safari / in-app browsers: Use remote debugging (Safari Web Inspector on macOS, Chrome DevTools for Android) to pull logs.
FAQ
Do I need to enable "Verbose" logging in Chrome?
Yes. SeaText's diagnostic messages are emitted at the verbose level. If the dropdown reads "Default levels", switch to "Verbose" before reproducing.
Can I just copy-paste the console text into the ticket?
You can, but copied text loses timestamps and line numbers. A saved .log file is preferred; paste only as a last resort.
What if the issue only happens in production?
Reproduce in a staging environment that mirrors production CSP headers and domain structure. If impossible, open an incognito window on production, capture the log, and note the exact URL and campaign parameters.
Does SeaText support need my localStorage dump?
Sometimes. In the console, run copy(JSON.stringify(localStorage, null, 2)) and paste the output into a localStorage.json attachment.
How do I know which SeaText agent caused the error?
Log lines prefixed with [SeaText] or seatext- indicate the agent (e.g., seatext-bot-refund, seatext-translation). Include those lines in your description.
Can I filter the log before sending to reduce size?
Keep the full log. Support greps for SeaText prefixes; removing unrelated lines may delete timing context.
What if the console is empty but SeaText still doesn't work?
Check the Network tab for failed SeaText script loads, then verify your CSP allows the script origin (check with the vendor for the exact domain).
Limitations of this guide
These steps cover browser-console export for SeaText's client-side snippet. They do not cover server-side SeaText API logs, dashboard audit logs, or mobile-app WebView debugging beyond remote-inspection basics. For those, ask support for the specific export procedure.
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.