Docs / Capability guide
Delivery alerts, experiments and diagnostics
Find causes of under-delivery and test changes to pacing or targeting.
All capabilities · Related guide · Agent prompt for this capability
When to use this example
When a campaign falls behind, changing a floor or budget before checking the cause can obscure the problem. Gather delivery and eligibility evidence for the affected period before proposing a change.
What the example gives you
The report exporter saves the selected period's metrics as CSV. Use that report with delivery diagnostics to investigate the shortfall; alert creation, experiments and configuration changes use the operations listed below.
Before you start
Reporting and diagnostic permissions, a bounded time interval and enough sandbox events to observe the outcome.
Run the example
Extract the archive and follow README.md for setup, commands, and expected results. Start with report_export.py. Local tests use sample data.
Python tools accept --help. To connect to your workspace, supply the deployment URLs, credentials and resource IDs required by the tool.
Connect it to your application
Inspect line-item delivery state and eligibility before changing pacing or floors. Use diagnoseDelivery with the relevant resource and time window; separate no-demand, targeting and budget causes.
Create delivery alert rules for the metrics you collect. Review triggered alerts and acknowledge or mute them as needed; configure a signed webhook receiver for notifications.
Create an experiment with explicit subjects and compare the same reporting periods. Preflight proposed configuration changes and retain a rollback plan; do not promote a change on a tiny or mismatched sample.
Check the result
A synthetic threshold breach generates the expected alert and a recovered condition stops it. Experiment reports identify the population and time window.