Bug 238310

Created attachment 455606 [details] trend of delayed reports It's expected attribution reports send after the 24-48 reporting delay window if Safari is closed. During testing it was discovered many reports were not delivered until roughly one month later. The graph below shows a trend of a trigger data value (gray line) over time after the value was removed from trigger logic on 1/25. It is a concern so many reports deliver after 48 hours. Has this behavior been reported from other PCM API users or internally during dev/testing? - Is there a test/debug solution that can be built into PCM to track at a finer grain level to help debug? Current debug solutions automatically send reports which isn't helpful to test reporting delay. - Event level reports that are received much later than 48 hours may not be useful for certain reporting use cases. Could reports older than a threshold outside the 48 hour window be dropped if desired, either by default or via a config set on the source event?