What Happens When a Visitor Arrives from an Unknown Source?
SeaText serves the default page variant when it cannot identify a visitor's traffic source. To customize this fallback, you can configure a catch‑all rule that applies a specific variant to any unrecognized source.
When SeaText cannot match a visitor to a known traffic source — such as Google Ads, Meta, email, referral, or organic search — it automatically serves the default variant of your page. This default is the original, unmodified version of your content unless you have set up a catch‑all rule.
How Source Detection Works
SeaText identifies where a visitor comes from by inspecting the HTTP referrer header, UTM parameters, and known ad‑platform click IDs (for example, gclid for Google Ads or fbclid for Meta). If one of these signals matches a configured source rule, the corresponding variant is applied in real time at the edge before the page renders.
When none of those signals are present or recognizable — for instance, a visitor types the URL directly, uses a privacy‑focused browser that strips referrers, or arrives from a new platform not yet in your rule set — the system treats the source as unknown.
Default Behavior: The Original Page
By default, SeaText does not rewrite or personalize the page for unknown sources. The visitor sees exactly what you published in your CMS. This ensures a safe, predictable experience and avoids showing mismatched headlines or offers.
This behavior is intentional. Personalization only triggers when there is enough confidence that a specific variant will improve relevance. Guessing on unknown traffic could hurt conversion rates by presenting the wrong message.
When to Configure a Catch‑All Rule
A catch‑all rule lets you define a single variant that applies to every visitor whose source cannot be identified. You might want this if:
- You run broad brand campaigns where even direct traffic should see a tailored headline.
- You want to test a generic high‑performing variant against the original for all unidentified visitors.
- Your analytics show a significant share of "direct" or "unknown" traffic that you suspect comes from dark social, messaging apps, or privacy tools.
To set it up, create a new source rule in the SeaText dashboard, leave the source condition empty (or select "Any / Unknown"), and assign the variant you want as the fallback. The rule will sit at the bottom of the priority stack and apply only when no other rule matches.
Priority and Rule Order
SeaText evaluates source rules in the order they appear in your configuration. Specific rules — like "Google Ads campaign X" or "Email newsletter Y" — are checked first. The catch‑all rule, if present, is evaluated last. This means known sources always get their dedicated variant; the catch‑all only fills the gaps.
You can reorder rules at any time. Moving a rule higher gives it priority over broader rules below it.
Common Scenarios That Produce Unknown Sources
| Scenario | Why It Appears Unknown | Typical Share of Traffic |
|---|---|---|
| Direct URL entry or bookmark | No referrer header sent | 10–30% |
| Privacy browsers (Brave, Safari with ITP) | Referrer and click IDs stripped | 5–20% |
| Messaging apps (WhatsApp, Slack, Teams) | Links opened in‑app often drop referrer | 2–10% |
| New or niche ad platforms | Click ID not yet recognized by SeaText | Variable |
| HTTPS → HTTP navigation | Referrer policy blocks cross‑protocol referrer | Rare |
These ranges are industry observations; your actual split depends on audience, channels, and technical setup. Check your analytics "Source/Medium" report to see how much traffic lands in "direct / (none)" or "unknown".
Limitations of the Catch‑All Approach
- One variant for many intents. A single fallback cannot match the relevance of source‑specific variants. A visitor from a product‑review blog and one from a brand‑search ad have different needs.
- No automatic learning. SeaText does not currently auto‑create rules for emerging sources. You must monitor analytics and add rules manually.
- Edge‑case conflicts. If a catch‑all rule is too broad, it may inadvertently apply to traffic you later want to target specifically. Review rule order after adding new sources.
Key Facts
| Fact | Detail | Source |
|---|---|---|
| Default behavior for unknown sources | Serves the original, unmodified page variant | S1 |
| Catch‑all rule support | Configurable in dashboard; applies when no other source rule matches | S1 |
| Source detection signals | HTTP referrer, UTM parameters, ad click IDs (gclid, fbclid, etc.) | S3, S4 |
| Rule evaluation order | Top‑down; specific rules first, catch‑all last | S1 |
| Agents that use source adaptation | Visitor Source Adaptation Agent, Google Ads Landing Page Agent | S3, S4 |
Terminology
- Variant — A version of your page with specific headline, copy, offer, or CTA changes applied by SeaText.
- Source rule — A condition that maps a traffic source (e.g., "Google Ads", "Email newsletter") to a variant.
- Catch‑all rule — A rule with no source condition (or "Any / Unknown") that acts as a fallback for unmatched traffic.
- Edge delivery — SeaText rewrites the page at the CDN edge, before it reaches the browser, so there is no flicker or layout shift.
FAQ
Can I see how much traffic is "unknown" in SeaText?
SeaText reports show variant impressions by source rule. Traffic that falls through to the default (or catch‑all) appears as "Unmatched" or "Default" in the dashboard. For a full breakdown, cross‑reference with your analytics platform's Source/Medium report.
Does the catch‑all rule affect known sources?
No. Rules are evaluated in order. A visitor matching a specific rule (e.g., "Google Ads") receives that variant and the evaluation stops. The catch‑all only applies when no prior rule matches.
What if I don't set a catch‑all rule?
Unknown‑source visitors see your original page exactly as published. No personalization, no A/B test assignment — just the baseline experience.
Can I A/B test the catch‑all variant?
Yes. You can assign an A/B test group to the catch‑all rule so unidentified visitors are split between two or more fallback variants. This lets you optimize the generic experience over time.
How quickly does a new catch‑all rule take effect?
Changes propagate to the edge within seconds. There is no cache purge required; the next request evaluates the updated rule set.
Will a catch‑all rule hurt my Quality Score or SEO?
No. SeaText operates at the edge and serves the same URL. Search crawlers typically have no referrer or click ID, so they receive the default (or catch‑all) variant. As long as that variant contains your core content and metadata, SEO is unaffected.
Next Steps
- Open your analytics and check the share of "direct / (none)" or "unknown" traffic over the last 30 days.
- If it exceeds 15–20% and you have a hypothesis for a better generic headline or offer, create a catch‑all variant in SeaText.
- Assign it to a new catch‑all source rule at the bottom of your rule list.
- Monitor variant performance in the SeaText dashboard for 2–4 weeks.
- Iterate: promote high‑performing catch‑all elements into source‑specific rules as you identify where that traffic actually originates.
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.