There's a concern that the duplicate Popups events that @Tbayer reported in T161769: Schema:Popups sends extraneous link interaction events in control condition are being sent by the client. While there are a couple of avenues for investigation for the server-side components of the EL architecture, we should be confident that the PP codebase is behaving correctly.
We will log in Page Previews when an event that has already been logged is logged again. This will increase our confidence that the issue is not in the Page Previews code base (and let us know whether it is part of sendBeacon or EventLogging).
- If a duplicate event is logged within a page session, then:
- It is dropped;
- The PagePreviews.DuplicatePopupsEvent counter is incremented in StatsD, i.e.
mw.track( 'counter.PagePreviews.DuplicatePopupsEvent', 1 );
- We plot the counter on the Page Previews dashboard.
- Exactly when is one Popups event a duplicate of another? The data that @Tbayer provided in T161769: Schema:Popups sends extraneous link interaction events in control condition suggests that two events sharing the same interaction token (or "token") are duplicates of one another.