Thanks for posting. This is something we are looking into and scoping out. It touches every part of our infrastructure so it isn't simple but it is something we are actively working on.

charism51522941​ It is possible to use sendBeacon for any call just set s.useBeacon=true. It will then make the next request a sendBeacon request. ExitLinks will be automatically use sendBeacon without any configuration.

@ursboller and @itaparia You shouldn't need to pay any special attention to exit links other than what you are currently doing. The limit is most browsers enforce is that you can only have 64k of stuff queued in sendBeacon (See the spec). This is usually not a problem for most exit links but can become a problem for other tracking scenarios (especially in offline mode of a PWA). With our new implementation the only effects should be exit links should unload slightly faster and the data transmiss...

Good news. The latest version of AppMeasurement will use sendBeacon for ExitLinks. Release Notes - AppMeasurement for JavaScript There are some oddities with sendBeacon that make it tricky to use more often (e.g. Size limits per session, Number of requests active at a single time and such).

Thanks for the feedback. We will continue to look at this. Browser support is such that this makes a lot of sense now.

One way you could do this is to create a segment then use that segment to filter a virtual report suites. Segment can be filtered down to certain date ranges by using the dates as part of the criteria.

Love the idea. We will keep an eye on this one.

This is now available in the admin console and we are moving to have it be on by default.

Is the idea that you can then add them as a group to a freeform table? Do tags solve this use case?