# Your page scores 54 out of 100 for sameness against the 4 competitors you named.

Parts of your page are genuinely your own — but what you say you do and who it's for is where you and Twilio Segment start to sound the same.

- **Your page:** https://tealium.com/
- **Compared against:** Treasure AI (treasure.ai), Twilio Segment (twilio.com), mParticle (mparticle.com), Uniphore (uniphore.com)
- **Sameness Index:** 54 — Half shared
- **Ownable share:** 28% (of 37% distinctive)
- **Report:** https://grader.wynter.com/c/tealium-com-NXerSJ8

**How you compare · vs 366 SaaS sites** — 2 points less same than the average SaaS site. The average SaaS site scores 56; you scored 54. You are less same than 216 of the 366 SaaS sites. The best-differentiated site in the set is at 6.
_A single check can move several points between runs; the benchmark averages up to eight sites per category._

## 1. Sameness Index

| Category | Weight | Score | What it means |
| --- | --- | --- | --- |
| Messaging | 30% | 81 | The most expensive kind of sameness. A buyer cannot tell what job you do that the others do not. |
| Claims | 30% | 58 | Every shared claim is a line already read on another tab. Cut the ones nobody owns and spend the space on something they cannot. |
| Features | 15% | 51 | Expected in a mature category, and the least alarming of the six. Feature parity is normal; leading with it is the mistake. |
| Proof | 10% | 13 | Same kinds of proof as everyone means the proof stops working as proof. It is scored on the kind of evidence, not on which customers are named. |
| Structure | 10% | 13 | The generic SaaS template — hero, logos, three-feature grid, testimonial, CTA. Familiar is not the same as memorable. |
| Visual | 5% | 42 | Weighted lowest on purpose: buyers rarely decide on this. Worth knowing, rarely worth fixing first. |

**Half shared** — About half your claims are also on competitor pages.

## 2. Closest competitors

| Competitor | Same | Band |
| --- | --- | --- |
| Twilio Segment | 73 | Mostly the same |
| Treasure AI | 63 | Mostly the same |
| mParticle | 55 | Half shared |
| Uniphore | 26 | Mostly your own |

_Measured from your side: how much of what YOU say each competitor also says, weighted by where you put it._

## 3. Ownable share

**The share of your own page's claim space that is yours to keep.** This is not the inverse of the Sameness Index — it is measured on your claims alone, so the two do not add up to 100 and are not meant to.

28% of your page is unique, relevant and defensible — a strong share, and the thing to protect in any rewrite.

- **Distinctive message share:** 37% — prominent space spent on claims no competitor makes.
- **Ownable share:** 28% — the part of that which is also relevant to how buyers choose and hard to copy.

## 4. Where you sound like everyone else

Most of your set makes each of these and you are spending prominent space on them, ranked by how much. **These are not necessarily lines to delete** — some of what a page has to say is unavoidably shared, and claims about what kind of product you are were left out of this list for exactly that reason. The question each one raises is whether it has earned its space.

- **routes and activates data to any destination** (Hero, 100% of the set) — also on Treasure AI, Twilio Segment, mParticle, Uniphore
  - _"Tealium keeps customer data flowing where you need it, when you need it"_
- **fast, low-latency and reliable performance** (Hero, 75% of the set) — also on Treasure AI, Twilio Segment, mParticle
  - _"Every event reaches analytics, warehouses, and AI systems in under 100ms"_
  - Said your way: nobody else makes this exact claim, but everyone occupies the territory.
- **routes and activates data to any destination** (Section, 100% of the set) — also on Treasure AI, Twilio Segment, mParticle, Uniphore
  - _"Routes data to the model, channel, warehouse, or agent that needs it"_
- **routes and activates data to any destination** (Body, 100% of the set) — also on Treasure AI, Twilio Segment, mParticle, Uniphore
  - _"Real-time, triggered, or on a schedule"_
  - Said your way: nobody else makes this exact claim, but everyone occupies the territory.
- **AI and agents built into the platform** (Body, 75% of the set) — also on Treasure AI, mParticle, Uniphore
  - _"Execute transformations and consent logic with on-device models like Gemini Nano without round-tripping to a server"_
  - Said your way: nobody else makes this exact claim, but everyone occupies the territory.
- **AI and agents built into the platform** (Body, 75% of the set) — also on Treasure AI, mParticle, Uniphore
  - _"Validated, consented event streams delivered directly to AWS Bedrock, Vertex AI, OpenAI, and SageMaker without data plumbing"_
  - Said your way: nobody else makes this exact claim, but everyone occupies the territory.

## 5. Buried gold

Unique, relevant, and sitting in body copy. The cheapest wins here — you already have the differentiation and the page hides it.

- **Streams consented data directly to AI/LLM services** (Body, 0% of the set)
  - _"Validated, consented event streams delivered directly to AWS Bedrock, Vertex AI, OpenAI, and SageMaker without data plumbing"_
- **Move PII/PHI server-side to meet compliance regimes** (Body, 0% of the set)
  - _"Move PHI, PII, and vendor-specific logic server-side to meet HIPAA, SOC 2, and ISO 27001 requirements"_
- **Native integrations with consent management platforms** (Body, 0% of the set)
  - _"Native CMP integrations for OneTrust, Didomi, and Usercentrics"_
- **Server-side delivery to ad platform conversion APIs** (Body, 0% of the set)
  - _"Deliver first-party events directly to Meta CAPI, Google Enhanced Conversions, TikTok Events API, LinkedIn, and Pinterest without pixel decay"_

## 6. Claim inventory

| Claim | Type | Placement | Common | Sayability | Relevant | Ownership |
| --- | --- | --- | --- | --- | --- | --- |
| Platform turns customer data into action | category | Hero | 75% | anyone | yes | Commodity |
| Gets customer data where it's needed | outcome | Hero | 25% | anyone | yes | Contested |
| Sub-100ms event delivery to destinations | quality | Hero | 0% | some | yes | Unique and owned |
| AI-ready data is complete, current, compliant | quality | Hero | 25% | anyone | yes | Contested |
| Hundreds or thousands of prebuilt integrations | proof | Hero | 25% | some | yes | Contested |
| Large enterprise customer base | proof | Hero | 25% | some | yes | Contested |
| Massive daily event volume processed | proof | Hero | 25% | some | yes | Contested |
| No custom ETL to build or maintain | quality | Hero | 25% | some | yes | Contested |
| Schema validated before delivery | capability | Hero | 25% | some | yes | Contested |
| Consent enforced at point of collection | capability | Hero | 0% | some | yes | Unique and owned |
| Data is consented, enriched, identity-resolved | capability | Hero | 0% | some | yes | Unique and owned |
| Captures events from web, mobile, server, IoT | capability | Hero | 25% | some | yes | Contested |
| Named a leader by industry analysts | proof | Hero | 25% | some | yes | Contested |
| Routes data to any downstream destination | capability | Section | 25% | anyone | yes | Contested |
| Marketers ship changes without engineering or code releases | outcome | Section | 25% | some | yes | Contested |
| Enriches data with contextual attributes | capability | Section | 0% | anyone | no | Unique for now |
| Fix data collection once, upstream of AI | outcome | Section | 0% | anyone | yes | Unique for now |
| Manage all tags from one console | capability | Section | 0% | some | yes | Unique and owned |
| Resolves identity in real time | capability | Section | 0% | some | yes | Unique and owned |
| Standardize naming and schema at the source | capability | Section | 0% | some | yes | Unique and owned |
| Holds HIPAA, SOC 2, ISO certifications | proof | Section | 25% | some | yes | Contested |
| One mobile SDK feeds all vendor SDKs | capability | Section | 25% | some | yes | Contested |
| Delivery in real time, triggered, or scheduled | capability | Body | 0% | anyone | no | Unique for now |
| On-device AI models run transformations locally | capability | Body | 0% | some | no | Unique and owned |
| Streams consented data directly to AI/LLM services | capability | Body | 0% | some | yes | Unique and owned |
| Move PII/PHI server-side to meet compliance regimes | capability | Body | 0% | some | yes | Unique and owned |
| Native integrations with consent management platforms | capability | Body | 0% | some | yes | Unique and owned |
| On-device storage and retries survive bad networks | capability | Body | 0% | some | no | Unique and owned |
| Server-side delivery to ad platform conversion APIs | capability | Body | 0% | some | yes | Unique and owned |

## What we compared

- **Tealium** (your page) — https://tealium.com/
- **Treasure AI** — https://www.treasure.ai/
- **Twilio Segment** — https://www.twilio.com/en-us/segment
- **mParticle** — https://www.mparticle.com/
- **Uniphore** — https://www.uniphore.com/actioniq/

## What this does and does not tell you

An AI read each page and wrote down the claims it makes, then grouped the claims that say the same thing. **No score in this report was written by a model** — every number is computed from those groupings in our own code, with the weights shown above.

## The only way to know if it matters

This report can tell you where your messaging overlaps. It cannot tell you whether a buyer would care, or which of your reasons to buy actually land. Put the page in front of real B2B buyers in your target market and ask them.

[Test it with real buyers](https://wynter.com)