AI-referred visitors convert to signups at 1.66% compared to 0.15% from traditional search — that’s 11x better (Microsoft Clarity, 2025). The reason? They arrive already understanding what they want. Your campaign visitors could do the same — if your website knew WHO just clicked. Standard UTMs tell you a visitor came from Facebook. Coded UTMs tell your AI that a cost-conscious WooCommerce store owner who’s frustrated with data loss just landed, and they’re ready to compare solutions.
That’s the difference between WHERE data and WHO data. And it changes everything about how your website responds to a click.
Your Campaign Links Are Carrying the Wrong Intelligence
Every marketer uses UTM parameters. utm_source=facebook, utm_medium=cpc, utm_campaign=spring-sale. This tells Google Analytics where the click came from. It tells you nothing about the person behind it.
73% of consumers expect companies to understand their needs and expectations (Salesforce, 2026). Yet the standard UTM format — unchanged since Google acquired Urchin in 2005 — carries zero information about visitor psychology, intent, or readiness to buy.
Think about what your Facebook campaign manager already knows: the audience segment, the interest targeting, the lookalike seed, the ad creative that resonated. All that intelligence dies the moment someone clicks through to your website. Your landing page greets a high-intent enterprise buyer the same way it greets a casual browser.
82% of consumers are willing to share data for a customized experience (DemandSage, 2026). They’re not asking you to spy on them. They’re asking you to pay attention. The data exists inside your campaign — you’re just not carrying it through the click.
You may be interested in: What Are Coded UTM Parameters?
What Is a WHO Profile?
A WHO profile is a structured psychographic and intent description encoded directly into your campaign link. Instead of telling analytics WHERE the traffic came from, it tells your AI WHO just arrived.
A WHO profile has four layers:
- Mindset: Where is this person in their journey? Problem-aware, solution-seeking, comparison-shopping, or ready-to-buy?
- Intent Signal: What triggered the click? Pain (data loss fear), aspiration (growth goals), or urgency (compliance deadline)?
- Value Tier: High-intent enterprise prospect, mid-market evaluator, or early-stage researcher?
- Product Affinity: Which product angle resonates? Simplicity, cost savings, data ownership, or technical capability?
A standard UTM says: “This visitor came from a Facebook ad.” A WHO profile says: “This visitor is a solution-seeking WooCommerce store owner motivated by data loss fear, mid-market value tier, drawn to the simplicity angle.”
The first feeds a report. The second feeds an AI that can personalize the entire landing experience in under 300 milliseconds.
The WHO Framework: Four Steps From Campaign to AI
Step 1: Define Your Segments
Before you encode anything, map your audience into WHO segments. Start with the campaigns you’re already running. Each ad set or audience already implies a WHO profile — you’ve just never written it down.
For a WooCommerce store running Facebook Ads, your segments might look like this:
- Segment A: Problem-aware store owners losing data to ad blockers (mindset: problem-aware, intent: pain, value: mid-market, affinity: data recovery)
- Segment B: Agency marketers evaluating tracking solutions for clients (mindset: comparison, intent: professional need, value: high, affinity: scalability)
- Segment C: Tech-savvy founders wanting data ownership (mindset: solution-seeking, intent: aspiration, value: high, affinity: data ownership)
Each segment gets a unique code. That code becomes part of your campaign link.
Step 2: Encode Into Coded UTMs
Standard UTM parameters use predictable names — utm_source, utm_medium, utm_campaign. Ad blockers and browser extensions target these patterns specifically. Coded UTM parameters replace predictable names with randomized strings that bypass every filter list.
A coded UTM link carrying a WHO profile looks like this:
yourstore.com/landing?ehgys=1276879&kxmtp=A2
The ehgys=1276879 encodes your standard campaign tracking (source, medium, campaign). The kxmtp=A2 encodes the WHO profile — Segment A, mindset level 2 (solution-seeking). To Chrome, Firefox, and every ad blocker extension, these are meaningless strings. To your WordPress site with inPIPE Free installed, they decode instantly into structured intelligence.
AI-driven referral traffic surged 35x between July 2024 and May 2025 (Adobe). The websites winning that traffic aren’t guessing who their visitors are. They know — because the campaign link told them.
Step 3: Decode on Landing
When a visitor clicks your coded campaign link, the decoding happens server-side before the page finishes rendering. The WHO profile pushes to the WordPress dataLayer as structured data:
dataLayer.push({
'who_segment': 'A',
'who_mindset': 'solution-seeking',
'who_intent': 'pain-data-loss',
'who_value': 'mid-market',
'who_affinity': 'data-recovery',
'campaign_source': 'facebook',
'campaign_medium': 'cpc'
});This is the Campaign Intelligence Layer — the structured bridge between your campaign click and your website’s AI personalization system. Every tag manager, every analytics tool, every AI personalization engine can consume dataLayer events. The WHO data is now available to anything connected to your site.
You may be interested in: First-Party Data for AI: Start Now, Win Later
Step 4: Feed to AI
With WHO data in the dataLayer, your AI personalization system can act immediately. The visitor hasn’t scrolled yet, and your website already knows:
- Which headline variation to show (pain-focused vs aspiration-focused)
- Which social proof to surface (case studies matching their value tier)
- Which CTA to display (free trial for evaluators, demo request for enterprise)
- Which product angle to lead with (simplicity for overwhelmed store owners, technical depth for developers)
71% of consumers want generative AI integrated into their shopping experience (Capgemini, 2025). WHO profiles give AI the context it needs to deliver that experience from the first millisecond — not after five page views and a form submission.
Why WHO Profiles Outperform Cookie-Based Personalization
Cookie-based personalization waits. It watches a visitor browse three pages, click two products, and maybe add something to cart before it has enough data to personalize. That takes minutes — and most visitors leave within seconds.
WHO profiles don’t wait. The intelligence arrives with the click. There’s no observation period, no cookie dependency, no “we need more data” delay.
There’s also no Safari ITP problem. Cookie-based personalization breaks when Safari limits cookie life to 7 days. WHO profiles travel inside the URL parameter — they survive every browser restriction because they never touch cookies at all. The visitor’s segment, intent, and value tier exist in the URL string itself, decoded server-side and pushed to the dataLayer as first-party data.
Cookie-based personalization learns who your visitor is. WHO profiles already know.
Building WHO Profiles With inPIPE Free
The Polymath Website concept — a site intelligent enough to greet every visitor with contextual awareness — sounds like it requires enterprise infrastructure. It doesn’t. inPIPE Free for WordPress handles the entire WHO workflow: define segments, generate coded campaign links, decode on landing, and push WHO data to the dataLayer automatically.
For stores running Transmute Engine™, the WHO data flows through the entire server-side pipeline. Your first-party Node.js server on your subdomain receives the decoded WHO profile alongside every event — purchases, add-to-carts, form submissions — and routes enriched data to GA4, Facebook CAPI, and BigQuery simultaneously. The campaign intelligence that started in your Facebook ad set ends up in your BigQuery data warehouse, ready for machine learning models that predict which WHO segments convert best.
The Polymath Website doesn’t need to be built from scratch. It needs a campaign link that carries the right intelligence and a WordPress plugin that knows how to read it.
The WHO profile is one layer of a much bigger shift — from catalogue to service portal: Grab the Vine.
Key Takeaways
- Standard UTMs carry WHERE data (source, medium, campaign). Coded UTMs can carry WHO data (mindset, intent, value tier, product affinity).
- AI-referred visitors convert 11x better because they arrive pre-qualified. WHO profiles replicate this advantage for every campaign.
- The WHO framework has four steps: define segments, encode into coded UTMs, decode on landing, feed to AI via the dataLayer.
- WHO profiles survive ad blockers and Safari ITP because the intelligence travels in the URL string, not in cookies.
- inPIPE Free automates the entire workflow — from coded link generation to dataLayer push — without developers or GTM.
Campaign links should carry a WHO profile — a structured set of psychographic and intent signals including visitor mindset (problem-aware, solution-seeking, comparison-shopping), value tier (high-intent enterprise, casual browser), emotional driver (fear of loss, desire for growth), and product affinity. Coded UTM parameters encode these into the link itself so your website AI can decode and act on them the instant the visitor lands.
The Polymath Website concept encodes visitor intelligence INTO the campaign link using coded UTM parameters. When you click, the landing page decodes your WHO profile from the URL — your segment, intent, and value tier — and pushes it to the dataLayer. AI systems consume this data in under 300 milliseconds, personalizing headlines, offers, and content before you scroll. The website doesn’t guess who you are. The campaign link already told it.
Standard UTMs carry WHERE data — utm_source=facebook, utm_medium=cpc. They tell analytics which channel drove the click but nothing about the person clicking. Coded UTMs carry WHO data — encoded visitor segments, intent levels, and psychographic profiles. Standard UTMs feed reports. Coded UTMs feed AI. And because coded UTMs use randomized parameter names, they survive ad blocker filter lists that strip standard utm_ parameters.
No. inPIPE Free for WordPress lets you define WHO segments in a visual interface, generate coded campaign links, and automatically decode them on landing. The decoded WHO profile pushes to your dataLayer for any AI system or tag manager to consume. No coding, no developers, no GTM configuration required.
Start building WHO profiles with inPIPE Free today. Your visitors arrive with intelligence — your website should use it.
