Test and verify the Experience Cloud Identity Service test-and-verify-the-experience-cloud-id-service
These instructions, tools, and procedures help you determine if the ID service is working properly. These tests apply to the ID service in general and for different ID service and Experience Cloud solution combinations.
Before you begin section-b1e76ad552ed4eb793b6e521a55127d4
Important information to know before you begin testing and verifying the ID Service.
Browser environments
When testing in a normal browser session, clear your browser cache before each test.
Alternatively, you can test the ID service in an anonymous or incognito browser session. In an anonymous session, you don’t need to clear your browser cookies or cache before each test.
Tools
The Adobe debugger and the Charles HTTP proxy can help you determine if the ID service has been configured to work properly with Analytics. The information in this section based on the results returned by the Adobe debugger and Charles. However, you should feel free to use whatever tool or debugger works best for you.
Testing with the Adobe Debugger section-861365abc24b498e925b3837ea81d469
Your service integration is configured properly when you see a Experience Cloud ID (MID) in the Adobe debugger response. See Cookies and the Experience Cloud Identity Service for more information about the MID.
To verify the status of the ID service with the Adobe debugger:
- Clear your browser cookies or open an anonymous browsing session.
- Load your test page that contains ID service code.
- Open the Adobe debugger.
- Check the results for a MID.
Understanding Adobe Debugger results section-bd2caa6643d54d41a476d747b41e7e25
The MID is stored in a key-value pair that uses this syntax: MID= *Experience Cloud ID*. The debugger displays this information as shown below.
Success
The ID service has been implemented properly if you see a response that looks similar to this:
mid=20265673158980419722735089753036633573
If you’re an Analytics customer, you may see an Analytics ID (AID) in addition to the MID. This happens:
- With some of your early/long-time site visitors.
- If you have a grace period enabled.
Failure
Contact customer care if the debugger:
- Does not return a MID.
- Returns an error message that indicates your partner ID has not been provisioned.
Testing with the Charles HTTP proxy section-d9e91f24984146b2b527fe059d7c9355
To verify the status of the ID service with Charles:
- Clear your browser cookies or open an anonymous browsing session.
- Start Charles.
- Load your test page that contains ID service code.
- Check for the request and response calls and data described below.
Understanding Charles results section-c10c3dc0bb9945cbaffcf6fec7082fab
Refer to this section for information about where to look, and what to look for, when you use Charles to monitor HTTP calls.
Successful ID Service requests in Charles
Your ID service code is working properly when the Visitor.getInstance function makes a JavaScript call to dpm.demdex.net. A successful request includes your Organization ID. The Organization ID is passed as a key-value pair that uses this syntax: d_orgid= *organization ID*. Look for the dpm.demdex.net and the JavaScript calls under the Structure tab. Look for your Organization ID under the Request tab.
Successful ID Service responses in Charles
Your account has been provisioned correctly for the ID service when the response from the Data Collection Servers (DCS) return a MID. The MID is returned as a key-value pair that uses this syntax: d_mid: *visitor Experience Cloud ID*. Look for the MID in the Response tab as shown below.
Failed ID Service responses in Charles
Your account has not been provisioned correctly if the MID is missing from the DCS response. An unsuccessful response returns an error code and message in the Response tab as shown below. Contact customer care if you see this error message in the DCS response.
For more information about error codes, see DCS Error Codes, Messages, and Examples.