This document is a collection of verbose debugging reports that are supported.
Here are the debugging reports supported for attribution source registrations.
A source is rejected due to the destination limit.
Noise is applied to a source event.
A source is rejected due to the storage limit.
A source is successfully registered. Note that this is also sent when a source is rejected due to the following limits to mitigate security concerns:
- unattributed reporting origin limit
- reporting origins per source and reporting site rate limit
- destinations per source site rate limit.
A source is rejected due to the destinations per source and reporting site rate limit.
A source is rejected due to the destinations per source and reporting site per day rate limit.
System error.
A source is rejected due to exceeding the channel-capacity limit.
A source is rejected due to exceeding the max trigger-state cardinality.
A source is rejected due to the reporting origins per source and reporting site limit.
Here are the debugging reports supported for attribution trigger registrations.
A trigger is rejected due to no matching sources in storage that match <reporting origin, destination site> (see algorithm).
A trigger is rejected due to no matching filter data.
An event-level attribution is rejected due to the max attributions rate limit.
An aggregatable attribution is rejected due to the max attributions rate limit.
A trigger is rejected due to the attributed reporting origin limit.
An event-level report is not created due to deduplication.
An event-level report is not created due to no matching event triggers.
An event-level report is dropped due to the noise applied to the source.
An event-level report is dropped due to too low priority.
An event-level report is dropped as the maximum number of reports have been scheduled for the source.
An event-level report is not created due to the storage limit.
An event-level report is not created as the report window has not started.
An event-level report is not created as the report window has passed.
An aggregatable report is not created due to deduplication.
An aggregatable report is not created as no histogram contributions are created.
An aggregatable report is dropped as the maximum number of reports have been scheduled for the source.
An aggregatable report is dropped due to insufficient budget.
An aggregatable report is not created due to the storage limit.
An aggregatable report is not created as the report window has passed.
System error.
The report data is included in the request body as a JSON list of objects, and
each object has a string field type and a dictionary field body, e.g.:
[{
"type": "source-destination-limit",
"body": {
"attribution_destination": "https://destination.example",
"limit": "100",
"source_debug_key": "1234567890",
"source_event_id": "12340873456",
"source_site": "https://source.example"
}
}]The body field is identical to the event-level report body if type is
trigger-event-low-priority or trigger-event-excessive-reports,
otherwise the dictionary may include the following fields:
attribution_destination: The site on which attribution did/would occur, e.g."https://destination.example".limit: The browser's limit enforced, e.g."100".source_debug_key: The debug key in the source registration, omitted if not set.source_event_id: The source event id in the source registration.source_site: The site on which source was registered, e.g."https://source.example".trigger_debug_key: The debug key in the trigger registration, omitted if not set.
If type is source-success or source-noised, the body
dictionary may include a source_destination_limit field if the destination limit
was exceeded.
This table defines the fields in the body dictionary.