Integrations

The interoperability layer for connected media systems.

Ad360 coordinates execution across demand-side platforms, identity providers, data warehouses, creative delivery, analytics, and standards-based exchanges. Integration is a first-class operational surface — observable, governed, and protocol-literate at the boundary.

Talk to engineeringRead the protocol layer
RUNTIME / INTEROP BOUNDARY
Interoperability surfaces
  • OpenRTBBid surface
  • UID2Identity surface
  • VASTCTV surface
  • TCF 2.2Consent surface
  • WebhookEvent surface
  • S/01
    01

    Channels

    Execution surface federation

  • S/02
    02

    Identity

    Cross-graph identity federation

  • S/03
    03

    Data

    Warehouse and event federation

  • S/04
    04

    Protocols

    Standards-based exchange

  • S/05
    05

    Observability

    Boundary telemetry and sync state

  • S/06
    06

    Compliance

    Regulatory and residency federation

SECTION 01 · CHANNELS
Channel execution surfaces

Programmatic execution across the modern advertising stack.

Ad360 supports programmatic display, connected TV, digital out-of-home, native, retail media, and audio through standards-based integrations, bidder logic, and managed activation paths. Each channel is reached with explicit pacing, frequency, and policy controls at the request layer.

C/01
CHANNEL

Programmatic display execution

Demand-side platform integration through OpenRTB 2.5 and 2.6 bid adapters, with priority routing, pacing controllers, and policy enforcement at the request layer.

OpenRTB 2.5 · 2.6 · DSPs
C/02
CHANNEL

Connected TV (CTV) execution

Programmatic CTV inventory is reached through VAST-based video integrations, server-side ad insertion workflows where applicable, and per-impression frequency policy.

VAST · SSAI · video execution
C/03
CHANNEL

Digital out-of-home (DOOH) execution

DOOH dispatch operates through OpenRTB DOOH extensions, programmatic exchanges, and screen-aware delivery that preserves venue, geography, and dayparting context through the integration path.

OpenRTB DOOH · venue context
C/04
CHANNEL

Native advertising surfaces

Native execution dispatches through OpenRTB native 1.2 with explicit asset typing, sponsored content semantics, and publisher template alignment.

OpenRTB Native 1.2
C/05
CHANNEL

Retail media networks

Retail media execution federates with on-site retailer networks for sponsored product placements, audience activation, and closed-loop measurement against first-party retail data.

On-site · sponsored · closed-loop
C/06
CHANNEL

Programmatic audio

Audio execution covers digital audio streaming and podcast inventory through OpenRTB audio adapters, with cuepoint awareness and listener attention semantics.

OpenRTB Audio · podcast · streaming
SECTION 02 · FEDERATION
Identity and data federation

Inbound identity, data, audience, and consent — federated at the boundary.

Inbound surfaces resolve identity across deterministic and probabilistic graphs, ingest event data into operational storage, federate audience segments across activation channels, and propagate consent through the integration layer.

F/01
FEDERATION

Identity federation

Cross-device identity resolution against UID2, RampID, ID5, and internal identity graphs. Deterministic matching where available, probabilistic where appropriate, with provenance preserved.

UID2 · RampID · ID5 · deterministic + probabilistic
F/02
FEDERATION

Data warehouse federation

Event-grade ingestion into partitioned columnar storage and federation with customer-owned warehouses for workload isolation and zero-copy operational analytics. Inbound event flow lands in the platform ingestion layer.

Columnar OLAP · partitioned · zero-copy
F/03
FEDERATION

Audience graph federation

Segment activation across demand-side platforms, on-site retail networks, and creative surfaces with cross-platform segment ID propagation and lookalike expansion.

Segment ID · cross-platform · expansion
F/04
FEDERATION

Consent signaling

Consent strings propagate from publishers through the integration layer to demand and creative surfaces. TCF 2.2, GPP, and regional consent signals are honoured at the wire format.

TCF 2.2 · GPP · regional
SECTION 03 · INTEROP
Live interoperability surface

Bidirectional exchange across the operational boundary.

The integration runtime exchanges signals continuously across the operational boundary — bid streams, identity resolutions, event ingestion, and consent in; bid responses, identity acknowledgements, segment activations, and telemetry out. Each exchange is observable, governed, and standards-aware.

Interoperability surface
Interop dispatchActive
Inbound boundary
  • OpenRTB bid streamBid request · 2.6
  • Identity resolutionUID2 · graph match
  • Event ingestionWebhook · stream
  • Consent signalingTCF 2.2 · GPP
Outbound boundary
  • Bid response dispatchBid response · 2.6
  • Identity acknowledgementUID2 · graph ack
  • Segment activationSegment ID · push
  • Telemetry feedbackStream · attribution
Boundary stateSynchronized
SECTION 04 · PROTOCOLS
Protocol and API infrastructure

Standards-based exchange, with explicit operational surface.

Integration operates through documented protocols rather than bespoke connectors. OpenRTB governs programmatic exchange; identity standards govern resolution; HTTP-grade APIs and event streams govern custom integration. Schema versioning and contract enforcement are first-class.

P/01
PROTOCOL

OpenRTB protocol family

OpenRTB 2.5 and 2.6 bid surfaces, including DOOH, audio, native, and video extensions. Bid request and bid response semantics are enforced at the wire format, with explicit pacing and priority headers.

OpenRTB 2.5 · 2.6 · DOOH · audio · native
P/02
PROTOCOL

Identity standards

UID2, RampID, ID5, OpenID Connect, and federated identity providers are supported as identity exchange protocols, with provenance and consent context preserved across the resolution path.

UID2 · RampID · ID5 · OIDC
P/03
PROTOCOL

REST and GraphQL APIs

HTTP-grade REST and GraphQL APIs expose the platform's operational surface for custom integration, with versioned schemas, idempotency guarantees, and audited authentication.

REST · GraphQL · versioned schema
P/04
PROTOCOL

Event streams and webhooks

Real-time event streams and webhook delivery surfaces propagate operational events to customer systems with delivery acknowledgement, retry policy, and replay against the audit log.

Webhook · stream · replay-able
SECTION 05 · COMPLIANCE
Compliance and data residency

Regulatory federation, enforced at the integration boundary.

Compliance is a cross-system property. Regional regulation, consent signaling, and data residency are enforced as wire-format properties of the integration layer — not as application-level afterthoughts.

R/01
RESIDENCY

GDPR · EU regulation

Lawful basis, purpose limitation, storage minimization, and data subject rights are propagated across every integration boundary. Cross-system data flow respects EU regulation at the protocol layer.

Lawful basis · DSAR · minimization
R/02
RESIDENCY

CCPA and US state regimes

California Consumer Privacy Act compliance plus emerging US state regulations (Virginia VCDPA, Colorado CPA, Connecticut CTDPA) are enforced through consent-aware integration adapters.

CCPA · VCDPA · CPA · CTDPA
R/03
RESIDENCY

TCF 2.2 framework

IAB Transparency and Consent Framework 2.2 signaling is enforced at the integration wire format. Vendor consent and publisher restrictions are propagated to demand-side and creative surfaces.

IAB · vendor consent · publisher restrictions
R/04
RESIDENCY

Data residency · sovereign execution

Regional execution surfaces support data residency requirements where deployment scope requires it, including in-region identity and warehouse pinning.

Regional residency · in-region pinning

Walk through the interoperability layer.

Step through integration paths, protocol compatibility, or compliance constraints directly with engineering.

Discuss integration pathsReturn to overview