You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have been seeing unexpected data from the US banner test. The number of closes and CTA clicks both exceed the number of expands. This should be impossible, since the component does not allow closes or CTA clicks until the component is expanded.
Snapshot of the data part way through the test, provided by Anthony from D&I
The text was updated successfully, but these errors were encountered:
I looked into this with Jake from commercial. We discovered that the expand event is not being sent to Ophan when the component is expanded. This is most likely because the click is captured on a div element and ophan discounts these elements from tracking. We still have some clicks on the expands from the table, which is unexpected. This may have occurred due to certain browsers behaving differently or through dev testing.
I changed the expand element from a div to a button, so that ophan can track the clicks. However, I notice that the request is not always sent to ophan, which is unexpected.
Screen.Recording.2024-12-02.at.16.13.15.mov
Ophan does have a submitComponentEvent function, which may be able to track the clicks instead
We have been seeing unexpected data from the US banner test. The number of closes and CTA clicks both exceed the number of expands. This should be impossible, since the component does not allow closes or CTA clicks until the component is expanded.
Snapshot of the data part way through the test, provided by Anthony from D&I
The text was updated successfully, but these errors were encountered: