Hi @Rob_Miller83 Agree with @robinders871029 just to add - while passing
the data element into the Target configuration rule use the action Add
Params to Page Load Request - This action type allows parameters to be
added specifically to your page load request only. Make sure the Load
Target action must be used earlier. Hope this helps
Hi @rrrrrraul I found similar query thread in forum where it answered.
Please check the below links.
On the last point on sessionId generation - sessionId is generated and
maintained by the client only. Let me know if any further question you
Hello @fern1 Are you looking at Adobe Experience Platform debugger? In
which browser you're trying to installing? Can you also please check the
browser extension's page is not restricted in your machine. The
extension works on browser settings. Here is the URL for Chrome
Adding more steps to check if third party cookies are allowed in your
browser like below for Chrome. Chrome > settings >...
Hi @kamlesh-maddheshiya Can you please check the same action events has
been in all environment (e.g. add action "Extension = Facebook Pixel",
"Action Type = Send Page View" or "Action Type = Send Custom Event") and
the same pixel ID is getting used. There is one more way where you can
used the Facebook pixel helper debugger / extension tool to verify your
Pixel is working properly, troubleshoot common errors, and improve Pixel
Hi @DisaRas When a request is sent to the Adobe Experience Platform Edge
Network, a datastream ID is used to reference the server-side
configuration. Looking at the error it seems like an issues with
DataStream. Have you configured a DataStream correctly? Below document
helps you to configure a datastreamHope this helps.
Hi @Vijayakumar_Raju_CBE The five most recent libraries only allows by
adobe launch that have been published to your production environment for
later retrieval / re-publish. So once the library published into
production or republish any library (from recent most five), you can't
get that library back to dev or staging environment. in your case
Library A. if you think the particular rule / data element has some
issues with your de-active library then fix those issues and save into
new dev library...