Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server-side experiences not tracking with A4T #7

Open
jmswindle opened this issue Oct 12, 2020 · 0 comments
Open

Server-side experiences not tracking with A4T #7

jmswindle opened this issue Oct 12, 2020 · 0 comments

Comments

@jmswindle
Copy link

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).
Target Experience Views
Total Unique Views

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

  • target-java-sdk v1.1.0
  • Spring v4.3.25.RELEASE

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
{
      "requestId": "1a6560bb-b963-44f5-8e59-802347f7f6d8",
      "context": {
        "channel": "web",
        "address": {
          "url": "https://www.containerstore.com/custom-closets"
        },
        "beacon": false
      },
      "experienceCloud": {
        "analytics": {
          "supplementalDataId": "02BC759D22D4FE7E-62749C19A3060DFA",
          "logging": "server_side",
          "trackingServer": "thecontainerstore.sc.omtrdc.net"
        }
      },
      "execute": {
        "pageLoad": {
          "parameters": {},
          "profileParameters": {}
        },
        "mboxes": []
      },
      "prefetch": {
        "views": [
          {
            "parameters": {},
            "profileParameters": {}
          }
        ],
        "mboxes": []
      },
      "notifications": []
    }
Returning User Request
{
  "requestId": "2d05b638-d461-4377-904b-247b403032de",
  "id": {
    "tntId": "749afadd-3570-4efd-9e6a-84cd2c892160.35_0",
    "marketingCloudVisitorId": "45913002719203183828537149552334816373"
  },
  "context": {
    "channel": "web",
    "address": {
      "url": "https://www.containerstore.com/custom-closets"
    },
    "beacon": false
  },
  "experienceCloud": {
    "analytics": {
      "supplementalDataId": "697825C548C84264-1FC0EB4BDBB0355A",
      "logging": "server_side",
      "trackingServer": "thecontainerstore.sc.omtrdc.net"
    }
  },
  "execute": {
    "pageLoad": {
      "parameters": {},
      "profileParameters": {}
    },
    "mboxes": []
  },
  "prefetch": {
    "views": [
      {
        "parameters": {},
        "profileParameters": {}
      }
    ],
    "mboxes": []
  },
  "notifications": []
}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant