Hi Team,
We are trying to push experience fragments to the targeting system.
we are able to push the experience fragments to the targeting but the problem is in the offer details we are always seeing localhost:4503 in the offer details.
Not sure it is coming from where? and how to resolve it.
This is the first time we are doing it.
Any help or pointers that helps a lot.
Thanks
Solved! Go to Solution.
Views
Replies
Total Likes
Hi,
I would need bit more clarity on the problem statement.
If you are looking at the details of Experience Fragment offer within the Adobe Target, then it should come like this:-
You can go to AEM Deep link (Author Instance) to make any changes to the Experience Fragment and then publish it.
Offer Delivery URL can be changed from (Not Tested):- http://localhost:4502/system/console/configMgr/com.day.cq.commons.impl.ExternalizerImpl
-Kautuk
Views
Replies
Total Likes
Hi,
I would need bit more clarity on the problem statement.
If you are looking at the details of Experience Fragment offer within the Adobe Target, then it should come like this:-
You can go to AEM Deep link (Author Instance) to make any changes to the Experience Fragment and then publish it.
Offer Delivery URL can be changed from (Not Tested):- http://localhost:4502/system/console/configMgr/com.day.cq.commons.impl.ExternalizerImpl
-Kautuk
Views
Replies
Total Likes
Hi Kautuk,
Exactly we are seeing the same.. in offer details but why it is showing localhost:4503, it should be our server right?
or where do we need to update those configurations to show our server name instead of the localhost:4503.
Thanks
Uma
Views
Replies
Total Likes
Not tested, but that can be changed from:- http://localhost:4502/system/console/configMgr/com.day.cq.commons.impl.ExternalizerImpl
-Kautuk
Views
Replies
Total Likes
Yes, you have to update externalizer config for offers in target to have proper url instead of localhost:4503
You can change from localhost:4503 to www.example.com
Views
Replies
Total Likes
Ok, Got it. Let me try that. I believe that it is not gonna affect other things right?
I will update the results soon.
Views
Replies
Total Likes
well it may not affect but might change anything in your app which is using externalizer configs. Also consider, that's the main point of using externalizer to create public facing urls instead of localhost and all.
Views
Replies
Total Likes
Thanks Kautuk and edubey , now I am able to see actual server URL as a deeplink in the offer details.
Thanks
Uma
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies