Adobe Target implementation | Community
Skip to main content
B
BrayanHo
Level 2
May 23, 2025
Question

Adobe Target implementation

  • May 23, 2025
  • 1 reply
  • 596 views

Dear Community,

I need your help resolving this error. I've followed all the steps in this documentation, but Target still isn't working.
I really appreciate your help
https://experienceleague.adobe.com/es/docs/experience-manager-learn/sites/integrations/target/load-and-fire-target#page-event


AT: [page-init] Adobe Target content delivery is disabled. Ensure that you can save cookies to your current domain, there is no "mboxDisable" cookie and there is no "mboxDisable" parameter in query string.

Rule All Pages - Library Loaded fired.

 

 

 




Please guide here.

Thanks

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

1 reply

Matthew_Ravlich_ACG
Community Advisor
Matthew_Ravlich_ACGCommunity Advisor
Community Advisor
May 24, 2025

Hi @brayanho - I cannot read your Tags rule as the image resolution was relatively low. 

“AT: [page-init] Adobe Target content delivery is disabled. Ensure that you can save cookies to your current domain, there is no ‘mboxDisable’ cookie and there is no ‘mboxDisable’ parameter in query string.”
 
…means Target isn’t able to deliver personalized content. Here are a few things to check and troubleshoot:
 
1. Check for the mboxDisable Cookie
Open your browser’s Developer Tools → Application tab → Cookies section. Look for a cookie named mboxDisable.
 
2. Inspect the URL
If the page URL includes ?mboxDisable=true, Target will be disabled for that session.
Make sure this query parameter isn’t accidentally included in your page URL.
 
3. Verify Cookie Consent and Domain Settings
If you’re using a Consent Management Platform (CMP), ensure that Adobe Target cookies (like mbox) can be set after consent is granted. Target won’t function properly if cookies are blocked or consent hasn’t been provided.
 
4. Review Launch Rule Timing
In your Adobe Launch setup, make sure the rule that loads Target is firing after any required consent logic or cookie initialization. If Target tries to load before it has permission to set cookies, it won’t function correctly.
 
Bonus Debug Tip:
In the browser console, run:
console.log('Target loaded:', typeof adobe !== 'undefined' && adobe.target);
If it returns true, Target is loaded. If not, there’s a loading issue that needs to be resolved.

 

Example:

 

I hope this helps!

Matt Ravlich | ACG Digital

B
BrayanHoAuthor
Level 2
May 26, 2025

Hello @matthew_ravlich_acg

Thank you very much for your response. I've validated all the points you mentioned, and they are correct. We don't know what could be wrong. I'm wondering what other configuration needs to be done besides the implemented rule. Below is the file with the implemented rule. I implemented this command as you indicated, and this was the result:

console.log('Target load:', typeof adobe !== 'undefined' && adobe.target);

 



I really appreciate your help.

 

Matthew_Ravlich_ACG
Community Advisor
Matthew_Ravlich_ACGCommunity Advisor
Community Advisor
May 27, 2025

Hi @brayanho : Check out this older thread that explains how to solve using a public suffix issue for setting the at.js cookie at the domain level:

 

https://experienceleaguecommunities.adobe.com/t5/adobe-target-questions/how-to-resolve-quot-adobe-target-content-delivery-is-disabled/m-p/411829

Terms & ConditionsAccessibility statement

Loading footer...