Manage visitor consent
Set up the Plainrouter CMP, saved preferences, consent-tag controls and decision records.
Scan cookies and publish a declaration
Inspect website cookie and storage metadata, scan coverage and per-host freshness.
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
Connect MCP with a workspace key or OAuth and verify the intended workspace and 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.
- Read the API introduction: choose credentials and make an authenticated read.
- 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.
Resources for coding agents
Use the API resource index and API catalog to discover authentication, schemas, and documentation. The public SDK and agent repository includes agent instructions, coding-tool configuration, and official Agent Skills.Legacy Launcher
Drive connection and inventory sync, draft-file import and thelauncher.* MCP tools are retired. Use the supported creative workflow for Meta library reads and governed proposals.