Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Adobe Target integration with AEM 6.1 using Tealium as tag manager

Avatar

Avatar
Validate 1
Level 1
shilpa_satwase
Level 1

Likes

0 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
shilpa_satwase
Level 1

Likes

0 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile
shilpa_satwase
Level 1

06-07-2017

Hi everyone,

I am working on Adobe Target integration with AEM /CQ .

I am successfully able to target pages from AEM Local instance.

But I am unable to target pages from AEM AWS server.

I am working on targeting based on the type of browser.

Using server pages, I can see personalized content only in Internet Explorer.But not in any other Browser.

In IE, on the page from aws ,when i inspect element->console , I am able to see mboxCreate variable.But in any other browser,it says, mboxCreate is not defined.

Can you please help me with this?

Regards,

Shilpa

[Here is the list of all Adobe forums... https://forums.adobe.com/welcome]

[Moved from Comments forum to specific Program forum... Mod]

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 10
Level 10
ParitMittal
Level 10

Likes

90 likes

Total Posts

817 posts

Correct Reply

349 solutions
Top badges earned
Validate 10
Validate 1
Boost 50
Boost 5
Boost 3
View profile

Avatar
Validate 10
Level 10
ParitMittal
Level 10

Likes

90 likes

Total Posts

817 posts

Correct Reply

349 solutions
Top badges earned
Validate 10
Validate 1
Boost 50
Boost 5
Boost 3
View profile
ParitMittal
Level 10

06-07-2017

HI Shilpa,

It seems that mbox.js is itself not able to load completely on the page . Can you please use mboxDebug to troubleshoot the mbox to make sure the mbox is firing and the cookie (mbox cookie) is being set ?. Please see link for more information on debugging :

Troubleshooting Content Delivery

I suspect that since your are using cloud-based instances (Amazon AWS)  to test Adobe Target.The issue may be because of the Cookie domain setting.  The at.js and mbox.js JavaScript libraries use cookies to track users to ensure that Target always presents a consistent experience. If theTarget JavaScript libraries can't save cookies, Target requests are disabled.  please see the link for more information :Using Cloud-Based Instances with Target

Regards

Parit

Answers (2)

Answers (2)

Avatar

Avatar
Validate 250
Employee
Amelia_Waliany
Employee

Likes

190 likes

Total Posts

449 posts

Correct Reply

73 solutions
Top badges earned
Validate 250
Validate 100
Validate 50
Validate 25
Validate 10
View profile

Avatar
Validate 250
Employee
Amelia_Waliany
Employee

Likes

190 likes

Total Posts

449 posts

Correct Reply

73 solutions
Top badges earned
Validate 250
Validate 100
Validate 50
Validate 25
Validate 10
View profile
Amelia_Waliany
Employee

16-10-2017

Hi Shilpa,

Thanks for your question! Check out our Adobe Target Product Documentation for How to Implement at.js. Feel free to reach out if you have any other questions moving forward!

Warmly,

Amelia

Avatar

Avatar
Validate 1
Level 1
shilpa_satwase
Level 1

Likes

0 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
shilpa_satwase
Level 1

Likes

0 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile
shilpa_satwase
Level 1

21-07-2017

Thanks a lot for your response Parit!

I've tried to add at.js in home page template of my code. But at.js throws errors like "Uncaught ReferenceError: mboxFactoryDefault is not defined"

Is there a specific procedure to include at.js in our code , such that mbox will be available on pages?

Thanks in advance,

-Shilpa