Expand my Community achievements bar.

Applications for the 2024 Adobe Target Community Mentorship Program are open! Click to the right to learn more about participating as either an Aspirant, to professionally level up with a new Certification, or as a Mentor, to share your Adobe Target expertise and inspire through your leadership! Submit your application today.
SOLVED

adobe not defined

Avatar

Level 2

I'm trying to use adobe.target.applyOffer but am getting the error adobe is not defined. Target seems to be running correctly on the page as there is an active test running on the page. Is there a reason adobe would be undefined?

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Dear deakin96,

If you are using Adobe Target Extension (V1 or V2) in Adobe Launch, then you should not get the error.

Is it possible to share the public URL so that we can validate it? Something is missing here.

Thank You, Pratheep Arun Raj B (Arun) | NextRow Digital | Terryn Winter Analytics

View solution in original post

9 Replies

Avatar

Level 4

Hi @deakin96,

applyOffer requires the mbox parameter. If no mbox name is specified, an error occurs.

Documentation: https://experienceleague.adobe.com/docs/target-dev/developer/client-side/at-js-implementation/functi...

I hope that helps.

Avatar

Level 2

The problem is its saying adobe isn't defined so I can't get that far regardless.

Avatar

Level 4

When does the error appear? Can you share a screenshot of the error?

Avatar

Level 2

Sure, it appears everywhere I've tried to use it, for example in chrome devtools on any of our site pages: Screenshot 2023-05-16 at 1.55.15 PM.png


If I try it on the Adobe Experience League site which is running target it looks like this and returns an object:
Screenshot 2023-05-16 at 1.56.25 PM.png

Avatar

Employee

Hi @deakin96, It could be because of race conditions. Can you try to load the at.js on that page synchronously? It may be that the at.js is still loading when the adobe.target.applyOffer() function is called.

Avatar

Level 2

Thats a good idea but that wouldn't explain not being able to access the adobe object in the chrome devtools long after the page has loaded correct?

Avatar

Correct answer by
Community Advisor

Dear deakin96,

If you are using Adobe Target Extension (V1 or V2) in Adobe Launch, then you should not get the error.

Is it possible to share the public URL so that we can validate it? Something is missing here.

Thank You, Pratheep Arun Raj B (Arun) | NextRow Digital | Terryn Winter Analytics