TLDR: Cookie-based and composable CDPs are dead. They run on bad data. EdgeTag builds a first-party identity graph at the edge (not a vendor cloud), resolving anonymous visitors into cross-device profiles in real time. One 4kb SDK routes resolved identity to all channel partners (Meta, Google, TikTok, etc.) with edge-enforced consent. You own the data, you control the signal, you orchestrate growth.

‍

The era of the cookie-based CDP and the composable CDP is over.
If your identity layer depends on third-party cookies or warehouse joins, you're optimizing against garbage data — and garbage data drives garbage strategy.

‍

Cookie CDPs vs. Composable CDPs vs. Edge-Native CDP

The market is cluttered with "CDP" labels. Here's what actually separates them:

‍

‍

How the Edge ID Graph Gets Built

Every visitor that touches your site is an opportunity. Here's the progression from anonymous visitor to fully-resolved, cross-device identity — happening automatically at the edge of your network:

‍
‍

The Code: How EdgeTag Works

One lightweight SDK (4kb). One edge endpoint. Every channel partner gets resolved identity automatically. Reference: docs.edgetag.io

// 1. Init — connects browser to YOUR edge (not a vendor cloud)
edgetag("init", "https://your-store.edgetag.io");

// 2. Consent — edge-enforced, per provider. No data moves without it.
edgetag("consent", {
  all: true
  // Or granular:
  // meta: true,
  // google: true
});

// 3. User — builds YOUR ID graph on YOUR edge. Data persists.
// Captured once → enriches every event that follows.
edgetag("user", {
  email: "customer@example.com",
  phone: "+1234567890"
});

// 4. Tag — one event, edge routes to ALL channel partners
// Meta CAPI, Google, TikTok, Snapchat — all get resolved identity
edgetag("tag", "Purchase", {
  value: 129.99,
  currency: "USD",
  items: [
    {
      id: "SKU-001",
      quantity: 1
    }
  ]
});

‍

‍

What the Edge Sees vs. What a Cookie CDP Sees

‍

‍

Audience Metrics: What You See When Identity Lives at the Edge

When every browser touch builds your edge ID graph, your audience metrics transform. Known vs. anonymous, new vs. returning, cross-device counts — all resolved in real time:

‍

‍

Orchestrating Your Growth Strategy

Once your edge ID graph is resolving identity in real time, data tagging stops being a technical chore and becomes your growth strategy. You control what data is shared, when it's shared, and how channel partners optimize against it.

‍

The fastest signal caller wins. When your edge is real-time segmenting your audience and signaling to Meta, Google, TikTok, and Snapchat how to optimize against your strategy — not theirs — you're not just collecting data. You're orchestrating growth.

‍

‍

GTM Server-Side vs. EdgeTag: Direct Comparison

‍

‍

The Atom of Audience

Every browser session that touches your site — once filtered for bots and gated by consent — becomes the basic atom of audience: a Device/Browser node in your edge ID graph. This isn't a cookie. It's a persistent, first-party identity node that lives on your infrastructure.

From that atom, the system builds automatically:

‍

Stop sending garbage data to your channel partners. Build your own ID graph at the edge. Orchestrate your growth
‍

‍

‍

See EdgeTag in Action

2-minute install. No DevOps. Your ID graph, your edge, your strategy.

‍Read the Docs →