Flex event explainer doesn't describe how attribution-success debug reports are affected about attribution-reporting-api

[evazkj]

Similarly, for flex events, if value bucketing is enabled, what will the "trigger_data" field in the report become? ( I guess it will be set to null?)

[apasel422]

Similarly, for flex events, if value bucketing is enabled, what will the "trigger_data" field in the report become? ( I guess it will be set to null?)

The trigger_data field in the report will always correspond to whatever trigger_data was used to match against the source, regardless of whether custom summary buckets are being used.

[evazkj]

Is it possible that for a certain report with value bucketing, multiple triggers contribute to it, but they have different trigger data?
for example, a trigger_spec with trigger_data: [0, 1], then triggers with data = 0 or 1 will both contributing to a report, right?

[apasel422]

Is it possible that for a certain report with value bucketing, multiple triggers contribute to it, but they have different trigger data?

No, the Flexible Event summarization is always performed per trigger_data.

[evazkj]

I see. Thanks for the clarification.

[evazkj]

One other question, not related to OP, according to https://github.com/WICG/attribution-reporting-api/blob/main/ts/src/flexible-event/main.ts#L96 , num_buckets has to be same as num_reporting_window, I didn't see an explanation for it.

[apasel422]

One other question, not related to OP, according to https://github.com/WICG/attribution-reporting-api/blob/main/ts/src/flexible-event/main.ts#L96 , num_buckets has to be same as num_reporting_window, I didn't see an explanation for it.

That may just be a command-line-invocation requirement. I suggest trying out a sample registration using the header validator to test your exact configuration is supported.

[apasel422]

Closing in favor of a new issue since the conversion got a bit sidetracked here.