get_event_volume to read weekly delivery counts for distinct logical conversion events. It reports Plainrouter’s retained delivery evidence, not Meta’s learning status. This read makes no provider request and changes no ads.
Before you begin
Connect an MCP client with a Read or Write Workspace key authorized for Signals reporting. Events, destination delivery records and eligible frozen touch context must already exist. Provider figures remain limited by authorized account scope. The published server card defines the inputs. Use signal quality when you need delivery reasons instead of weekly counts.How do I read weekly event volume?
Callget_event_volume with these arguments:
ad_set_id, last and a 90-day lookback. level also supports platform and campaign_id; model supports first or last; lookback supports 7, 30, 60 or 90 days.
Each event is assigned once to the selected qualifying pre-conversion touch. This is an integer count, not fractional journey credit. At campaign/ad-set level, the selected touch must carry that dimension; a later site touch without it does not replace it.
What do the weekly rows count?
Readrange_used, effective_window and rows. Weeks start Monday in UTC, using event occurrence time. Rows keep conversion_kind, channel value and platform separate: a trial start and a subscription are different optimization events.
One logical event can have accepted, pending and failed deliveries across destinations or attempts. Those columns can sum above
recorded; do not treat them as a partition. Skipped or undelivered events can remain recorded without appearing in a delivery-status count.
Assigned platform rows count that platform’s authorized destinations. Unknown-attribution rows count authorized destinations without claiming a platform assignment. Kinds without a retained frozen journey remain unknown.
Does the benchmark prove that an ad set has left learning?
No.benchmark.value is a configurable planning reference, default 50. It is explicitly unverified live and applies only to complete, attributed ad-set weeks for each conversion kind. weeks_at_or_above_benchmark is repeated context for that group; do not sum it across weekly rows.
This report cannot establish Meta’s learning status, optimization configuration or future performance. Inspect Meta separately for its current delivery state. A missing row is not proof that Meta received no events.
Troubleshoot
For trials followed to first payment, use trial-to-paid cohorts. For fractional credit and costs, use conversion journeys.