Integration directory
Connect the systems that measurement and activation depend on
Audiencelab supports SDK, server-to-server, API, MMP, warehouse, and ad-network workflows. Exact capabilities vary by source and destination, so each implementation should document what is read, what is written, event ownership, privacy controls, latency, and reconciliation.
Overview
01Ad-network destinations
Use approved network endpoints to deliver web and app events or value signals. Available event types and diagnostics differ by network.
02Measurement and data sources
Keep MMP, app, server, and warehouse sources in the workflow. Audiencelab can use approved data to support creative and campaign decisions.
03Implementation paths
Choose the smallest path that meets the goal: SDK, server-to-server, REST API, approved export, or warehouse connection.
Process
- Define source and destination systems
- Document event ownership and identifiers
- Approve privacy and security controls
- Validate in a test environment
- Monitor volume, latency, and discrepancies
Limitations
What this page does not prove or guarantee.
- Integration availability and permissions can change.
- A listed platform does not imply endorsement or every possible connector.
- Data definitions must be reconciled across systems.
Questions
- Does one integration enable every capability?
- No. Capabilities depend on data availability, network APIs, account permissions, and the implementation path.
- Can Audiencelab work with a warehouse?
- Warehouse or server data can be part of a supported setup, subject to technical and security review.
- Where are implementation details?
- Use the technical documentation and confirm the intended source and destination with the Audiencelab team.