Signal

Overview

A Signal is a named segment used for targeting — an audience, contextual cohort, or first-party data slice. Signals are registered with Scope3 (or auto-discovered from external signals agents like LiveRamp), exposed via the v2 REST API, and deployed to DSPs/SSPs for use in media buys. The v2 signal model is conceptually identical to v1 — the same registration, discovery, access tier, and deployment semantics apply — but is now exposed via stable v2 REST endpoints under /api/storefront/signals.

Storefront-mounted: Signal management endpoints live on the storefront router (/api/storefront/signals/...) even though buyers and seat operators interact with the resulting signals on campaigns. This is because signals are owned by the agent/seat (storefront context) and surfaced to buyers via discovery and campaign attachment.

Signal sources

First-party (custom)

Audiences you upload — CRM segments, behavioral cohorts, geographic territories. No additional cost.

Agent-managed

Surfaced by external signals agents (LiveRamp, Optable, custom) using the ADCP signals protocol. Agents own the segments they create.

Third-party

External data providers (weather, behavioral, contextual). Premium signals incur additional CPM cost.

Built-in

Scope3-provided quality and viewability signals always available — no setup required.

Key fields

Field	Type	Notes
`signalId`	string	Stable signal identifier
`name`	string	Human-readable name
`description`	string	What the segment represents
`keyType`	enum	The identifier the segment is keyed on (e.g. `RAMPID`, `EMAIL_HASH`, `MAID`)
`regions`	string[]	ISO regions where the signal is available
`visibility`	enum	`PUBLIC`, `PRIVATE`, `SHARED` access scope
`isLive`	boolean	Deployed and accepting buys
`agentId`	string	Owning agent (for agent-managed signals)
`seatId`	string	Owning advertiser/seat
`seatName`	string	Display name for the owning seat
`pricing`	object	Optional CPM premium for premium signals

Lifecycle

Register first-party signals via POST /api/storefront/signals. Discover external signals via POST /api/storefront/signals/discover against signals agents.

Deploy

Deploy signals to DSPs/SSPs so they become addressable in media buys. Agent-managed signals deploy through the agent.

Activate in campaigns

Reference the signal as a target audience on a campaign (audienceConfig.targetAudienceIds) or in a brand story.

Monitor / archive

Track signal effectiveness through campaign reporting. Archive with DELETE /api/storefront/signals/:signalId.

Common operations

Register a first-party signal

curl -X POST https://api.agentic.scope3.com/api/storefront/signals \
  -H "Authorization: Bearer $SCOPE3_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "high_value_customers",
    "description": "Top 10% LTV customers — refreshed weekly",
    "keyType": "EMAIL_HASH",
    "regions": ["US", "CA"],
    "visibility": "PRIVATE"
  }'

Discover signals from an agent

curl -X POST https://api.agentic.scope3.com/api/storefront/signals/discover \
  -H "Authorization: Bearer $SCOPE3_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "agentId": "liveramp_signals_agent",
    "query": "premium auto intenders, last 30 days",
    "regions": ["US"]
  }'

The discover endpoint queries the agent’s catalog (RAG-style) and returns the most relevant segments along with metadata.

List / get / update / delete

# List with filters
curl "https://api.agentic.scope3.com/api/storefront/signals?agentId=liveramp_signals_agent&visibility=PRIVATE&isLive=true&limit=100" \
  -H "Authorization: Bearer $SCOPE3_API_KEY"

# Filter to a specific seat
curl "https://api.agentic.scope3.com/api/storefront/signals?seatId=seat_abc123" \
  -H "Authorization: Bearer $SCOPE3_API_KEY"

# Get one
curl https://api.agentic.scope3.com/api/storefront/signals/sig_abcd \
  -H "Authorization: Bearer $SCOPE3_API_KEY"

# Update
curl -X PUT https://api.agentic.scope3.com/api/storefront/signals/sig_abcd \
  -H "Authorization: Bearer $SCOPE3_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "description": "Refined definition — top 5% LTV" }'

# Archive
curl -X DELETE https://api.agentic.scope3.com/api/storefront/signals/sig_abcd \
  -H "Authorization: Bearer $SCOPE3_API_KEY"

Access tiers

Visibility	Description
`PUBLIC`	Available to all customers (e.g. Scope3 built-in signals)
`PRIVATE`	Owned by one customer/seat — invisible to others
`SHARED`	Selectively shared with named partner seats

Partner agents can list and manage signals across multiple seats they have access to. The seatId filter on list lets a partner narrow to one client at a time; seatName is returned so dashboards can show ownership without an extra lookup.

Signal RAG and optimization

When a campaign runs, Scope3’s RL optimizer uses signals as inputs alongside built-in quality and viewability data:

Collect — gather available signals on each impression opportunity (custom, third-party, agent-managed, built-in)
Retrieve — pull signals relevant to the campaign’s brief and optimization goals
Optimize — bias bidding and budget allocation toward signal combinations that perform well
Learn — feed measured outcomes back to inform future signal usage

This is the model AdCP and Scope3 refer to as Signal RAG. The platform documents which signals drove decisions so you can trace optimization choices.

Deployment

Some signals require deployment to a DSP before they’re addressable:

First-party: deployed by Scope3 to integrated DSPs after registration
Agent-managed: deployed by the agent (e.g. LiveRamp deploys RampIDs to its connected DSPs)
Built-in: always available, no deployment needed

isLive: true in the response confirms the signal is deployed and bidding is possible.

Pricing

Source	CPM premium
First-party	None
Agent-managed	Per-agent (LiveRamp, Optable, etc.)
Third-party	Per-provider; surfaced in pricing fields
Built-in	None

Premium signal cost is added on top of the publisher’s CPM at the media buy level. See the campaign budget breakdown for mediaBudget vs fees reporting.

Campaign

Reference signals as audienceConfig.targetAudienceIds

Brand

Brand identity that contextualizes signal usage

Discovery

Discovery uses signals to refine product matches

Storefronts

Browse storefronts and register credentials per inventory source

Overview

Setup

Object Guides

Workflows

Connections

Reference

Release Notes

Overview

Signal sources

First-party (custom)

Agent-managed

Third-party

Built-in

Key fields

Lifecycle

Common operations

Register a first-party signal

Discover signals from an agent

List / get / update / delete

Access tiers

Signal RAG and optimization

Deployment

Pricing

Campaign

Brand

Discovery

Storefronts

Overview

Setup

Object Guides

Workflows

Connections

Reference

Release Notes

​Overview

​Signal sources

First-party (custom)

Agent-managed

Third-party

Built-in

​Key fields

​Lifecycle

​Common operations

​Register a first-party signal

​Discover signals from an agent

​List / get / update / delete

​Access tiers

​Signal RAG and optimization

​Deployment

​Pricing

​Related concepts

Campaign

Brand

Discovery

Storefronts

Overview

Signal sources

Key fields

Lifecycle

Common operations

Register a first-party signal

Discover signals from an agent

List / get / update / delete

Access tiers

Signal RAG and optimization

Deployment

Pricing

Related concepts