Cette conversation a été verrouillée en raison de son inactivité. Veuillez créer une nouvelle publication.
Vos réussites
Niveau 1
0% pour
Niveau 2
Conseiller
/
Connectez-vous
pour obtenir des points, passer des niveaux et gagner des badges très intéressants, comme celui de la nouvelle
Se connecter à la communauté
Tout voir
Connectez-vous pour voir tous les badges
Join us on September 25th for a must-attend webinar featuring Adobe Experience Maker winner Anish Raul. Discover how leading enterprises are adopting AI into their workflows securely, responsibly, and at scale.
RÉSOLU
Adobe launch proxy doesnt work in test luma website by adobe.
Adobe launch proxy doesnt work in test luma website by adobe. I can see it is firing adobe launch abut it is not firing report suite. But when I use url redirect proxy on other sites I can see adobe report suite firing in omnibug or other debugger. What is the problem? I also used requestly app and it doesnt work either. If somebody from adobe support takes a look at this that would be great because we had spent like many days to figure this out but couldn't.
1 solution acceptée
Réponse correcte par
Hi,
I maintain the Luma website and created many tutorials using it. When properly configured, your tags/launch property should show in the "Page Embed Codes" section like this:
The "Injected Embed Codes" section should be empty.
When you first open the Debugger, you might need to reload the Luma page in order for the "Page Embed Codes" section to appear. Reload the Luma page with the Debugger open and then replace the current embed code.
@aagk123 Are you saying that the Adobe experience cloud debugger is not working on the luma test website?
If that is the case, it does work at our end without any issue, I could analytics firing without any issues
Even I am able to ingest my own launch script on Luma website without any issues
Réponse correcte par
Hi,
I maintain the Luma website and created many tutorials using it. When properly configured, your tags/launch property should show in the "Page Embed Codes" section like this:
The "Injected Embed Codes" section should be empty.
When you first open the Debugger, you might need to reload the Luma page in order for the "Page Embed Codes" section to appear. Reload the Luma page with the Debugger open and then replace the current embed code.
