Measure website arrivals
Create a workspace, connect your collection domain, and verify the first real arrival.
Send purchases to Meta
Choose a browser or backend workflow, then verify delivery without duplicate purchases.
Connect an AI agent
Try MCP with synthetic data, then connect a workspace token for your Meta ad account.
Troubleshoot measurement
Diagnose missing arrivals, delivery failures, stale platform data, and reporting differences.
Choose one purchase sender
Start with an active Signal. Advertising delivery also requires a connected Meta dataset and a recorded consent decision. Select one owner for each logical purchase; enabling multiple senders for the same checkout can create duplicates.
An API receipt confirms ingestion. Inspect destination delivery to check Meta acceptance; acceptance does not establish attribution or improved advertising performance.
Set up access and development tools
- Choose the correct credential: Signals secrets for REST, SDKs, and CLI; workspace execution tokens for MCP.
- Try the API sandbox: validate synthetic requests without an account or Meta delivery.
- Choose an SDK or CLI, or open the Conversion API overview.
- Read MCP tool inputs and limits, then create a governed creative proposal.
- Review pricing and billing before moving from testing to ongoing production use.