list_report_targets
List performance targets configured for your org. Targets feed the wins/concerns detector in report generation: beating a target by >10% is a win candidate; missing by >10% is a concern.
Parameters#
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
ad_account_id | string? | no | null | Filter to one account; omit for all (org-wide + per-account) targets |
Returns#
json
{
"targets": [
{
"id": "ad_rtgt_abc",
"ad_account_id": "ad_acct_abc",
"campaign_external_id": null,
"metric": "roas",
"period_type": "weekly",
"target_value": 3.0,
"target_currency": null,
"valid_from": "2026-01-01",
"valid_to": null
}
],
"count": 1,
"source": "adlyse.report_targets@v1"
}| Field | Description |
|---|---|
targets[].ad_account_id | null for org-wide targets |
targets[].campaign_external_id | Set for per-campaign targets; blank for account-level |
targets[].metric | spend, conversions, cpa, roas, ctr, or impressions |
targets[].period_type | daily, weekly, monthly, or quarterly |
targets[].target_currency | Populated only for monetary metrics (spend, cpa) |
targets[].valid_to | null if the target is currently active |
Errors#
error_type | When |
|---|---|
auth_error | Missing / invalid API key |
Example#
Request: { "ad_account_id": "ad_acct_abc" }
Response: as shown above.
See also#
- Reports — authoring targets in the UI
generate_report— targets automatically drive wins/concerns in the output