Overview
With Goal Based Dimensions, events fire when they occur, yet the data is not published until the end of the session so that all required data to properly evaluate the event is tabulated. Events that are configured to be evaluated at the end of the session are not published until that time. At the end of the session, the last known value for each dimension is back-populated to the event occurrences earlier in the session.
For example, the event that identifies when a user goes to the shopping cart occurs on hit 6, yet there are references to dimensional data populated by this event earlier in the session, on hits 2 and 4.
You can configure the event to properly capture the event on hit 6 and then to apply the dimensional values backward in the session.
For example, the Went to Cart
event fires on hit 6 and the Shopping
Cart
report group that fires on hits 2 and 4 include a YES
value for the
Went to Cart
dimension. The populating event is not yet fired at the time of the
recording of the report group on the earlier hits.