Skip to content

Rename Sync docs to Edge Cookie External Sync #788

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
aram356 merged 1 commit into from
Jun 19, 2026
+12 −9
Merged

Rename Sync docs to Edge Cookie External Sync #788

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion docs/.vitepress/config.mts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,7 +118,10 @@ export default withMermaid(
text: 'Proxy Signing',
link: '/guide/proxy-signing',
},
{ text: 'Collective Sync', link: '/guide/collective-sync' },
{
text: 'Edge Cookie External Sync',
link: '/guide/collective-sync',
},
],
},
{
Expand Down
16 changes: 8 additions & 8 deletions docs/guide/collective-sync.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Collective Sync Architecture
# Edge Cookie External Sync Architecture

Trusted Server supports cross-publisher data sharing through a **Collective Sync** model. Publishers who share the same EC secret key can synchronize user data across their properties, enabling privacy-preserving audience insights without third-party cookies.
Trusted Server supports ID syncing. Publishers who have engaged in an agreement with identity partners can use our sync endpoints found below.

## Overview

Expand Down Expand Up @@ -31,11 +31,11 @@ sequenceDiagram

## Architecture Principles

| Component | Role | Characteristics |
| ---------------- | --------------- | ------------------------------------------------------ |
| **KV Store** | Hot cache | Fast reads (~1ms), edge-local, eventually consistent |
| **Object Store** | Source of truth | Durable, supports range queries, sync endpoint |
| **Secret Key** | Shared salt | Distributed out-of-band, enables collective membership |
| Component | Role | Characteristics |
| ---------------- | --------------- | --------------------------------------------------------- |
| **KV Store** | Hot cache | Fast reads (~1ms), edge-local, eventually consistent |
| **Object Store** | Source of truth | Durable, supports range queries, sync endpoint |
| **Secret Key** | Shared salt | Distributed out-of-band, enables a data sharing agreement |

## Configuration

Expand Down Expand Up @@ -105,7 +105,7 @@ The Object Store maintains a richer record with full history:

### Initial Sync

When a new publisher joins the collective, they perform a full sync:
When a new publisher has a new agreement, they perform a full sync:

```http
GET /sync?type=full
Expand Down
Loading