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
There appears to be an issue with new users landing on the targeted page. The server-side implementation does not have an implementation for the Visitor API to get the ECID/MCID, thus causing a mismatch between Target and Analytics. Returning users with AMCV cookies already set do not appear to have an issue.
The example stats below are for a page that is mostly new users landing on it.
Expected Behaviour
A4T accurately tracks user data from server-side requests. # of views in experiences should mimic the total # of views of the given page.
Actual Behaviour
A4T is not attributing the appropriate experience for all views.
The following images were pulled from Analytics for the same time period. The page 'landing page:custom closets' is utilizing the server-side API and every user should be attributed an Experience. The total # of unique views should match between the two charts, as well as the # of submits (the conversion criteria).
Reproduce Scenario (including but not limited to)
Steps to Reproduce
Implement the target-java-sdk with analytics.
Create a Target Experience. Track the # of views of the page compared to the views of the experiences.
The only difference being our integration through Launch. Visitor state is set to a JS variable which is propagated to the Visitor Service through Launch.
There appears to be an issue with new users landing on the targeted page. The server-side implementation does not have an implementation for the Visitor API to get the ECID/MCID, thus causing a mismatch between Target and Analytics. Returning users with AMCV cookies already set do not appear to have an issue.
The example stats below are for a page that is mostly new users landing on it.
Expected Behaviour
A4T accurately tracks user data from server-side requests. # of views in experiences should mimic the total # of views of the given page.
Actual Behaviour
A4T is not attributing the appropriate experience for all views.
The following images were pulled from Analytics for the same time period. The page 'landing page:custom closets' is utilizing the server-side API and every user should be attributed an Experience. The total # of unique views should match between the two charts, as well as the # of submits (the conversion criteria).
Reproduce Scenario (including but not limited to)
Steps to Reproduce
Implement the target-java-sdk with analytics.
Create a Target Experience. Track the # of views of the page compared to the views of the experiences.
Platform and Version
Sample Code that illustrates the problem
We followed the sample provided for targetMcid.
The only difference being our integration through Launch. Visitor state is set to a JS variable which is propagated to the Visitor Service through Launch.
Logs taken while reproducing problem
New User Request
Returning User Request
The text was updated successfully, but these errors were encountered: