Web SDK Target Issue | Community
Skip to main content
Level 2
August 10, 2023
Solved

Web SDK Target Issue

  • August 10, 2023
  • 1 reply
  • 904 views

On the evening of Thursday, August 3, we deployed an updated Launch library that migrated our website from using the legacy Visitor ID, at.js and AppMeasurement libraries to the new Web SDK.

 

The Analytics data in general looks good. 

 

However, we are seeing a significant reduction in the reporting of the Activities and Experiences assigned in Target.  We see this both in Target reporting and in A4T.  It isn’t that no users are being reported as assigned to a test, just that the total number is a fraction of what we had seen in the days leading up to the update.

 

This problem is keeping us from being able to report on site usage and we need to get to a solution quickly.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by alexbishop

Are you still seeing this issue? If so, can you provide some more details on your implementation? If you haven't already, I'd recommend using Assurance to validate whether or not the stitching is happening at the Edge, as that will help to narrow down the root cause. Whilst the documentation largely refers to Mobile App, you can also use it to troubleshoot Web SDK implementations, by using the URL from the Copy Link option, as opposed to QR Code Scan

1 reply

alexbishop
Adobe Employee
alexbishopAdobe EmployeeAccepted solution
Adobe Employee
October 30, 2023

Are you still seeing this issue? If so, can you provide some more details on your implementation? If you haven't already, I'd recommend using Assurance to validate whether or not the stitching is happening at the Edge, as that will help to narrow down the root cause. Whilst the documentation largely refers to Mobile App, you can also use it to troubleshoot Web SDK implementations, by using the URL from the Copy Link option, as opposed to QR Code Scan