Server-side experiment - Target report not working (Java SDK) and offers not sticky | Community
Skip to main content
New Participant
February 18, 2021
Question

Server-side experiment - Target report not working (Java SDK) and offers not sticky

  • February 18, 2021
  • 1 reply
  • 1565 views

Hi! We have set up an experiment on our server-side using Target Java SDK. We are returning an experience for users, however 2 things are happening:

  1. The experience isn't sticky. If a user logs out and then back in, they will be randomly assigned a new experience. We are currently using our company mboxthirdpartyId to keep this sticky, however not working as it should.
  2. We are not seeing any visitors, visits, impressions and conversions in reporting.

Is there a data point that the reporting dashboard hooks up to specifically in a request/response?

 

We're only logging empty responses, no offer, (to control log volume), but here's an example request/response...please help and thanks! If there's anything here that might tell you that this data will not be sent to Adobe Target, please let me know and thanks!  

 

CLIENT_ID: 000726153 IP_ADDRESS: 71.233.1.76 LOGGER_NAME: com.fmr.pwi.hades.api.common.service.AdobeTargetService LOG_LEVEL: WARN LOG_SESSION_ID: 602ea62b0ad213cf200010b7000eaa33 LOG_TRACKING_ID: REQ602eac9fd7d6c430859c264d592faa33 MESSAGE: Invalid Adobe Target response. Ensure the request and experiment are configured correctly. Request: TargetDeliveryRequest{sessionId='602ea62b0ad213cf200010b7000eaa33', locationHint='null', visitor=com.adobe.experiencecloud.ecid.visitor.Visitor@239ac86f, decisioningMethod=null, deliveryRequest=class DeliveryRequest { requestId: null impressionId: null id: class VisitorId { tntId: null thirdPartyId: (some unique id) marketingCloudVisitorId: null customerIds: [] } environmentId: null property: null trace: null context: class Context { channel: web mobilePlatform: null application: null screen: null window: null browser: class Browser { host: retiretxn.fidelity.com language: null webGLRenderer: null } address: class Address { url: https://retiretxn.fidelity.com/mybenefits/wellness/app/learn referringUrl: null } geo: null timeOffsetInMinutes: 330.0 userAgent: Fidelity/WI/LearnHub beacon: false } experienceCloud: class ExperienceCloud { audienceManager: null analytics: class AnalyticsRequest { supplementalDataId: 14DFDE42C4C38B32-29E83A95E4DBE708 logging: server_side trackingServer: null trackingServerSecure: null } } execute: class ExecuteRequest { pageLoad: null mboxes: [class MboxRequest { class RequestDetails { address: class Address { url: https://retiretxn.fidelity.com/mybenefits/wellness/app/learn referringUrl: null } parameters: {} profileParameters: {} order: null product: null } index: 0 name: learn-hub-mbox }] } prefetch: null notifications: [] qaMode: null }} Response: TargetDeliveryResponse{request=TargetDeliveryRequest{sessionId='602ea62b0ad213cf200010b7000eaa33', locationHint='null', visitor=com.adobe.experiencecloud.ecid.visitor.Visitor@239ac86f, decisioningMethod=null, deliveryRequest=class DeliveryRequest { requestId: null impressionId: null id: class VisitorId { tntId: null thirdPartyId: (some unique id) marketingCloudVisitorId: null customerIds: [] } environmentId: null property: null trace: null context: class Context { channel: web mobilePlatform: null application: null screen: null window: null browser: class Browser { host: retiretxn.fidelity.com language: null webGLRenderer: null } address: class Address { url: https://retiretxn.fidelity.com/mybenefits/wellness/app/learn referringUrl: null } geo: null timeOffsetInMinutes: 330.0 userAgent: Fidelity/WI/LearnHub beacon: false } experienceCloud: class ExperienceCloud { audienceManager: null analytics: class AnalyticsRequest { supplementalDataId: 14DFDE42C4C38B32-29E83A95E4DBE708 logging: server_side trackingServer: null trackingServerSecure: null } } execute: class ExecuteRequest { pageLoad: null mboxes: [class MboxRequest { class RequestDetails { address: class Address { url: https://retiretxn.fidelity.com/mybenefits/wellness/app/learn referringUrl: null } parameters: {} profileParameters: {} order: null product: null } index: 0 name: learn-hub-mbox }] } prefetch: null notifications: [] qaMode: null }}, response=class DeliveryResponse { status: 200 requestId: beaa26f8-f6ef-4cd9-ab34-29a1170df575 id: class VisitorId { tntId: 602ea62b0ad213cf200010b7000eaa33.34_0 thirdPartyId: (some unique id) marketingCloudVisitorId: null customerIds: [] } client: fidelitywi edgeHost: mboxedge34.tt.omtrdc.net execute: class ExecuteResponse { pageLoad: null mboxes: [class MboxResponse { index: 0 name: learn-hub-mbox options: [] metrics: [] analytics: null trace: {} }] } prefetch: null }, status=ResponseStatus{status=200, message='', globalMbox='null', remoteMboxes=null, remoteViews=null}} PART_ID: 3563 PART_MID: (some unique id) PART_WID: 518392 REALM: /mybenefits REQUEST_METHOD: GET THREAD_ID: tomcat-http--6 TIMESTAMP: 2021-02-18T13:06:23.689-05:00 URI: /wellness/api/help-hub USER_ID: 3563 USER_ROLE: SELF }

 

 

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

1 reply

yaboytomcAuthor
New Participant
February 25, 2021
Reacing out again, if anyone with server-side implementation experience might be able to help with the above request. Thanks!
New Participant
November 3, 2021

Just curious if you had any luck with this.  I'm also trying to figure out Analytics Reporting and sticky experience.  Not much about it (at least example-wise) in the documentation.  

Amelia_Waliany
Employee
August 24, 2023

Thanks for your question here yaboytomc, and thanks @rjbu  for your weighing in! I know this question is a few years old but in case anyone wants to try to take a stab at it to close it out with deeper insights, please do 😊 Cheers!

CC our brilliant Advisors:  , and 

and our inspiring Mentors: @abhilashsape@Gokul_Agiwal@Rajneesh_Gautam_@PratheepArunRaj, and @Sneha-Parmar