FYI: Further Gating Trigger Verbose Debug Reports

[Akash Nadan]

Hi everyone,

We are planning to further gate trigger verbose debug reports starting in M120.

Currently trigger verbose debug reports are only gated by the presence of the ar_debug cookie (3PC) at trigger registration time. This change further gates trigger verbose debug reports by requiring the presence of the ar_debug cookie at source registration time as well. Therefore, in order to receive trigger verbose debug reports, the ar_debug cookie needs to be present at both source and trigger registration times.

Note: you will still be able to receive the “trigger-no-matching-source” verbose report with only the presence of the ar_debug cookie at trigger registration time. 

Please reach out if you have any questions.

Thanks,

Akash Nadan