AEP Debugger No Longer able to inject scripts

[MarkSt2]

So I logged into the Experience Platform Debugger (on Windows) today and found that as part of the newest update, there is no longer an option to inject the embed code to the page. Did Adobe move this feature somewhere or just remove it entirely? Sure was handy for implementation and QA. I'll be sad if it's gone for good.

[Ankit_Chaudhary]

Hi @MarkSt2 

It seems like with the new update you can't inject a new script if there is an script already available on the page, you can only replace or block an already existing script.

[dwright]

This should be fixed now in v1.6.1. If the extension doesn't update automatically, go to Manage Extension and click the Update button.

[Philippe_J]

I have the same issue, I hope it's a bug. It is so usefull for testing.

[MohitRo]

Adobe, please fix this issue.

[dwright]

 I have validated and reported this issue, but I don't have any ETA. If you have the ability to open a customer care ticket, that's always a good idea.

[dwright]

This is fixed in v1.6.1, available now in the Chrome store

[ewan_21]

In version 1.6 of the AEP debugger, I can no longer inject the script on to the page:

In previous versions I could, can you please add it back in ASAP.

[Anil_Umachigi]

@ewan_21 Yes looks like a bug, it works when you check box collect personal information consent. Not a good option but works.  

[Yuliya_Ivanchen]

Since the last update, it is no longer possible to insert custom snippets in Experience Platform Tags via the Adobe Experience Platform Debugger. Please fix this.

Thank you very much

[Anil_Umachigi]

@Yuliya_Ivanchen Agree looks like a bug, it works when you check box collect personal information consent. Not a good option but works for me with that option 

Hopefully someone at Adobe is listening! 

[Ankit_Chaudhary]

@Yuliya_Ivanchen  it seems like you can only replace an existing script now, if the website doesn't have any script then the option is not available.

@jayakrishnaaparthasarathy 

[dwright]

This is fixed in v1.6.1, available now in the Chrome store