We have this as the body of our app:
Notes:
${script}
is where the content of our React app gets rendered;${asyncTrackingScript}
is the script snippet copied from VWO UI;- if we place
${asyncTrackingScript}
in the expected place in the DOM (i.e. just before the</head>
tag), our app goes into an infinite loop of closing and reopening the widget we render (possibly due to our app setup).
Our VWOTracker
component looks like this:
This session is visible in the recorded sessions area of the VWO UI 👍
Note that:
- there is a CORS warning visible in the console which is coming from a request to one of our own internal services and should not have any impact on the behaviour of VWO;
- there is an info log in the console that seems to be coming from VWO code reporting an error;
- there are 2 requests to
GET https://dev.visualwebsiteoptimizer.com/e.gif
that fail with a414 - URI too long
error. This seems to be caused by trying to send an entire call stack as a query parameter calleds
- perhaps logging the call stack from the error logged to the console described in the previous point?
The session does not appear in the VWO UI.
We have 1 unique visitor from the Chrome session included above:
However, that visit has not been considered as a conversion, as we would expect it to given the goal settings:
It does however appear as the only result visible if we click the View recordings
button for visitors who did not convert: