Why SeaText Might Not Adapt Content for a Referral Email Even With UTM Tags Present
SeaText may skip referral-email adaptation when a higher-priority rule wins, the variant is unpublished, the edge cache serves stale HTML, or the referrer domain is blocked in settings. Diagnose in that order: check rule...
Why the UTM Tags Aren't Enough
UTM tags are the signal SeaText uses to identify a referral-email visitor. But a signal only matters if the engine is configured to act on it. When you see a referral email click land on a generic page, the most likely causes are: a rule priority conflict, an unpublished variant, a stale cached version, or a blocked referrer domain.
Think of it like a mail sorter. The envelope has the right address (UTM tags), but the sorter might be following a different instruction set (rule priority), the drawer with the right letter is locked (unpublished variant), the sorter is looking at yesterday's list (cache), or the sender's name is on a do-not-deliver list (blocked domain).
How SeaText Decides Which Content to Serve
SeaText evaluates rules in priority order. When a visitor arrives, the engine reads the UTM parameters, checks the referrer header, and then runs through your configured rules from highest to lowest priority. The first rule whose conditions match wins.
If you have a rule for utm_source=newsletter and another for utm_medium=email, and the email link carries both, the higher-priority rule takes over. If that rule points to a generic variant, your referral-specific content never appears.
This is by design. Priority lets you layer rules without conflicts. But it also means a broad rule can silently override a specific one.
Diagnostic Sequence: Check These Four Things in Order
- Rule priority — Open the Visitor Source Adaptation settings. Look for any rule that matches the same UTM parameters but sits higher in the list. If a generic rule outranks your referral rule, the generic one wins.
- Publish status — A variant can exist in draft mode. SeaText only serves published variants. Check that the referral-email variant shows a green or active status, not "draft" or "scheduled."
- Cache freshness — SeaText serves content from an edge cache for speed. If you edited the variant recently, the cache may still hold the old HTML. Force a cache purge or wait for the TTL to expire.
- Referrer domain blocklist — In settings, confirm the email provider's domain (e.g.,
mail.example.com) is not on a blocked list. A blocked referrer prevents adaptation even when UTM tags are present.
Why Rule Priority Conflicts Are the Most Common Cause
Most teams create rules incrementally. You might start with a rule for all email traffic, then add a more specific rule for referral emails. If the older, broader rule has higher priority, it captures the visitor first.
The fix is simple: reorder rules so the most specific condition sits at the top. SeaText evaluates top-down, so a rule matching utm_source=referral should outrank a rule matching utm_medium=email.
Check your rule list after every new campaign. New rules default to the bottom, which is often not where you want them.
Unpublished Variants: The Silent Killer
You can create a variant, edit the headline and CTA, and even preview it in the editor. But if you never hit "Publish," SeaText treats it as inactive. The engine will not serve unpublished content to any visitor.
This is a common workflow gap. Teams build variants during a campaign planning session, then move on to other tasks. The variant sits in draft mode indefinitely.
Always verify the publish status before launching a referral campaign. A quick check in the variant list saves you a confusing debugging session later.
Cache Serving Stale HTML
SeaText uses edge caching to deliver content with zero flicker. That speed comes with a trade-off: changes may not appear instantly.
If you updated a variant and tested immediately, you might see the old version. The cache TTL determines how long the old HTML persists. For urgent changes, use the cache purge option in the dashboard.
This is not a bug. It's the cost of fast delivery. Plan your edits before campaign launch, or purge the cache after major changes.
Blocked Referrer Domains
SeaText lets you block specific referrer domains. This is useful for filtering out spam or unwanted traffic. But if you accidentally block the domain your referral emails come from, adaptation stops.
Check the blocklist for any email service provider domains. Common ones include mailchimp.com, sendgrid.net, or your own company's mail server. Remove any that should be allowed.
This is less common than priority conflicts, but it's a quick check that eliminates a whole category of failure.
When the Advice Does Not Apply
These four causes cover most cases, but not all. If your referral email uses a redirect service (like a link shortener), the UTM tags might be stripped before the visitor reaches your site. Some email platforms also remove query parameters for privacy.
In those cases, SeaText never sees the UTM tags. The fix is to use direct links or ensure your email platform preserves query strings.
Also, if the visitor has JavaScript disabled or uses a strict ad blocker, the adaptation script may not run. SeaText relies on client-side execution for some features. Check your analytics for the session to confirm the script loaded.
Key Facts at a Glance
| Cause | How to Spot It | Fix |
|---|---|---|
| Rule priority conflict | Generic rule outranks referral rule | Reorder rules, specific first |
| Unpublished variant | Variant shows "draft" status | Click Publish |
| Stale cache | Old content appears after edit | Purge cache or wait for TTL |
| Blocked referrer domain | Domain on blocklist | Remove from blocklist |
| Stripped UTM tags | No UTM in analytics | Use direct links |
Practical Scenarios
Scenario 1: You have a rule for utm_source=newsletter and another for utm_source=referral. The newsletter rule is higher priority. A referral email link carries both utm_source=referral and utm_medium=email. The newsletter rule matches first, so the visitor sees the newsletter variant.
Scenario 2: You created a referral variant yesterday but forgot to publish. Today's campaign sends traffic. Visitors see the default page. The variant list shows "draft." One click fixes it.
Scenario 3: You edited the referral variant's CTA text. You test immediately and see the old CTA. The cache hasn't refreshed. Purge the cache and test again.
Frequently Asked Questions
Why would a rule priority conflict happen if I only have one rule?
It can't. If you have only one rule, priority is not the issue. Check publish status, cache, and referrer blocklist instead.
How long does the cache take to refresh?
It depends on your TTL setting. SeaText typically uses a short TTL, but you can purge manually for immediate updates.
Can I test without affecting real visitors?
Yes. Use a private browser window and append the UTM parameters to your URL. This simulates a referral visit without sending real traffic.
What if the UTM tags are present but the referrer header is empty?
SeaText can use either signal. If UTM tags are present, it should still adapt. If it doesn't, check the other three causes.
Does SeaText support multiple referral sources at once?
Yes. You can create separate rules for different sources. Just ensure the most specific rule has the highest priority.
What does it cost to fix these issues?
Nothing. These are configuration changes within your SeaText dashboard. No additional fees apply.
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.