I am trying to solve a mystery. We are using DTM and trying to pull in the Target PCID into Adobe Analytics via a data element. We never had issues in the past but are now noticing that we aren't getting the PCID set in the mbox cookie? The weird thing is on our Bank network, Everyone that tested got the same results:
Chrome Browser Normal mode on VPN - mbox cookie without PCID but contains session id
Chrome Browser Incognito mode on VPN - mbox cookie with PCID
Chrome Browser Normal mode at Home - mbox cookie with PCID
Chrome Browser Incognito mode at Home - mbox cookie with PCID
I went through and disabled all the extensions in Chrome, in Normal mode and checked all different settings I could think of ("Do not Track" etc.) but couldn't find any settings that might cause this issue? I have no idea what to look at next. On my home laptop it works in both modes of Chrome as designed. Any ideas? Adobe support hasn't been any help since they can't duplicate from their side!
Third party cookies are a little tricky to view in Chrome. They don't usually appear in the dev tools where you are looking. The most reliable way I've found to view them in Chrome is to Settings->Advanced Options->Content Settings->All cookies and site data... and then use the filter to locate the cookies. In your case the third party cookies will be set on the bankofthewest.tt.omtrdc.net domain--the domain where the mbox calls are sent. There are two cookies mboxPC and mboxSession.
By the way, thanks for signing off as MJ in your last note. I just realized we go way back! Hope all is well at the new gig.
I thought that was you! :0) Good to hear from you. So you were correct. Once I deleted the 3rd party Adobe cookie I got the PCID in the mbox cookie again. So my question is, if a user deletes their 1st party cookies there is no way to read the PCID on the client any longer?
If you delete ALL of your cookies you will get a PCId in your 1st party mbox cookie which should be readable using mboxFactoryDefault.getPCId().getId(). This is why you saw the PCId when you were in incognito mode. Incognito mode starts with a clean slate effectively clearing 1st and 3rd party cookies.
My guess is when you were experiencing this "Chrome Browser Normal mode on VPN - mbox cookie without PCID but contains session id" you were probably just clearing your 1st party cookies and not your 3rd party cookies. If you did that the 1st party cookie would not reset with the PCId.
I think this is more of a QA process issue. You should be able to read the PCId just fine for normal visitors as it would be odd behavior for normal visitors to remove only 1st party cookies. Does that make sense?
Thanks for the response, I checked and I do see the mboxPC in the request Headers (see image) but still not in the mbox cookie? So what does this mean? How do I read the PCID into Adobe Analytics then? That is why I was reading the "mbox" cookie previously to get the PCID. We are using DTM.and the Marketing Cloud ID Service if that matters or impacts anything at all?
When you use a 1st and 3rd party cookie implementation the mboxPC value will be set in a third party cookie on the bankofthewest.tt.omtrdc.net domain. Thus, there is no reason to set it in the 1st party cookie.
Take a look at the mbox request headers and confirm you see an mboxPC value being sent with the cookies to the bankofthewest.tt.omtrdc.net domain, e.g.