So I'm using this ACS commons feature (https://adobe-consulting-services.github.io/acs-aem-commons/features/marketo-form/index.html) to auto-configure the "embed" component for Marketo. This is working fine in author. I can see the marketo form in edit-mode and view-as-published.
I cannot see the marketo form when:
Any ideas on how to fix? Thanks
EDIT:
After more investigation, I found this code as part of ACS commons
<sly data-sly-use.configMgr="com.adobe.acs.commons.marketo.MarketoClientConfigurationManager" data-sly-use.marketoForm="com.adobe.acs.commons.marketo.MarketoForm">
configMgr is returning blank/null on the publisher BUT it's returning the correct values in author.
In both author and publisher, Marketo has been configured via settings => Cloud services => Marketo. Any more ideas?
Solved! Go to Solution.
Views
Replies
Total Likes
Please make sure the chnages that you have made on author along with the code and content package is deployed to publish instance. Once it is available on publish instance, you should be able to see it on publish as well followed by dispatcher.
Thanks!
Please make sure the chnages that you have made on author along with the code and content package is deployed to publish instance. Once it is available on publish instance, you should be able to see it on publish as well followed by dispatcher.
Thanks!
Views
Replies
Total Likes
After more investigation, I found this code as part of ACS commons
<sly data-sly-use.configMgr="com.adobe.acs.commons.marketo.MarketoClientConfigurationManager" data-sly-use.marketoForm="com.adobe.acs.commons.marketo.MarketoForm">
configMgr is returning blank/null on the publisher BUT it's returning the correct values in author.
In both author and publisher, Marketo has been configured via settings => Cloud services => Marketo. Any more ideas?
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Its been 3 years since there was an update on this Question, going around on Experience League Community and same reply only and no proper solution/closure. Sharing link for reference wherein they even created a custom component just to utilize AEM + Marketo integration(Noted i have shared this reply on that thread to help more other devs) > https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/2582
Sharing here our experience on this wherein we encounter same issues/findings and what led us to make this work on Publisher and hope helps future devs on this integration.
(1) Follow the instruction on below, this will help setup the Marketo on your AEM instance, once that is done you will be able to see Marketo on Author and View as Publish
https://adobe-consulting-services.github.io/acs-aem-commons/features/marketo-form/index.html
(2) Now if you are encountering the issue wherein Marketo/Embed Component is not showing in Publisher, first thing to do is ensure that the acs-aem-commons-ui.content, acs-aem-commons-ui.apps and also acs-aem-commons-content is same version and is installed both on Author and Publishers(If you have multiple Publisher) Environment
(2) Second is ensure also that the configuration you have setup on Author is replicated in Publishers, here are the paths i have on our environment and maybe different on yours but should be the same idea:
(3) So once we confirm everything is aligned on Author vs Publisher, check your consoles and logs and see if any errors, one thing we notice is this "Cannot access this method" when calling the *js call for Marketo/Embed Component
(4) This is due to Permission issue when calling the /conf/xxxxxxx/settings/cloudconfigs hence why we are getting ERR_EMPTY_RESPONSE, so for this we need to give READ access to said path /conf/xxxxxxx/settings/cloudconfigs
(5) After all above is done, you should be able to see Marketo/Embed Component, sharing here our Public Website wherein Marketo/Embed Component is showing in Publisher(Noted this is a test page only, will try to share a live Publish page moving forward for future reference).
https://www.manulifeim.com.hk/en/marketo-config-testing.html
Hope this helps!