@Gokul_Agiwal Great question. We have a few customers in Beta using it.
However, it hasn't quite released yet, though it will be releasing very
soon. If you are interested in following the project, here are a few
links you might be interesting. Beta Docs (constantly changing and
Project - https://github.com/adobe/alloy
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
@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
Good news. The latest version of AppMeasurement will use sendBeacon for
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
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.