This PR is in relation to issue #35, but I believe it does resolve #36 as well
I found that when generating visits in the past, xGen would correctly patch timestamps on the visit and any custom page events. However, Sitecore Analytics could still kick off other page events for a specific request (ex. error or long running request) and since those are being kicked off at a later point in the execution pipeline, xGen would not be modifying them. The result would be a contact record with page events for the same visit, spanning the full duration of the 'Recency' parameter.
I added a patch to the pipeline to modify all page events timestamps
This PR is in relation to issue #35, but I believe it does resolve #36 as well
I found that when generating visits in the past, xGen would correctly patch timestamps on the visit and any custom page events. However, Sitecore Analytics could still kick off other page events for a specific request (ex. error or long running request) and since those are being kicked off at a later point in the execution pipeline, xGen would not be modifying them. The result would be a contact record with page events for the same visit, spanning the full duration of the 'Recency' parameter.
I added a patch to the pipeline to modify all page events timestamps