Adobe Target - Personalising issue | Community
Skip to main content
SundeepKatepally
New Participant
January 6, 2021
Solved

Adobe Target - Personalising issue

  • January 6, 2021
  • 1 reply
  • 1254 views

I have installed Adobe target V2 extension with at.js version 2.2.0 in adobe launch .

I also have written rule in adobe launch and did “load target” and “fire global mbox” .

A4T configuration is done and working fine. I have also created an Experience target activity .

 

For target - using the sandbox provided by adobe.

Where as for AEM - using local instance localhost:4503 access via tunnel (ngrok) for example - https://f82bfea0d66d.ngrok.io/content/we-retail/language-masters/en/men.html

Able to successfully connect from AEM to target.

 

However when I load the page(where launch code is present) via tunnel domain name , I am not able to find any beacon in network tab when I filter it with "mbox"and also in adobe debugger I am not able to find any activity in the target tab.

 

Where as when accessed via. , localhost:4503 able to see the call on the filter with "mbox"

Please let me know whether i can access via tunnel domain name.

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

Hi @sundeepkatepally :

Is there a publicly accessible tunnel domain name URL I could look at?

Do you see any console output when you append ?mboxDebug=1 to the URL?

Are there any errors on the console?

1 reply

surebee
surebeeAccepted solution
Employee
January 15, 2021

Hi @sundeepkatepally :

Is there a publicly accessible tunnel domain name URL I could look at?

Do you see any console output when you append ?mboxDebug=1 to the URL?

Are there any errors on the console?

SundeepKatepally
New Participant
January 15, 2021
this issue is resolved when accessed by the domain name hosted in AWS , looks like there is some issue with tunnel domain name. As such i dont the tunnel name.