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 - audience queries

Avatar

Avatar
Validate 1
Level 3
sabahatu1546489
Level 3

Likes

13 likes

Total Posts

30 posts

Correct Reply

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

Avatar
Validate 1
Level 3
sabahatu1546489
Level 3

Likes

13 likes

Total Posts

30 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile
sabahatu1546489
Level 3

26-09-2017

Hi there,

I was wondering if someone can assist me with the following queries with regards to Adobe Target.

Assuming the client only have access to Adobe Target and not DTM and has at.js implementation:

1-       If we were to audience off of a DOM element, how would we do that i.e activate the activity if the div with specific exists activate the experiement?

2-       After changing some settings at at.js, would that require updating the tag again in the head section? e.g adding code to Library header/footer screenshotbelow:1310566_pastedImage_0.png

3-       Why don’t see more Available Tokens/parameters name in the Profile script section. In the documentation example here (https://marketing.adobe.com/resources/help/en_US/target/target/c_script_profile_attributes.html) 

1310567_pastedImage_1.png

How would I know what model and subcat is? Is that something I need to find from backend/database?

Secondly in order to test the above code I reckon we cannot do that in browser console right? How would we do that in order to make sure this code is returning the right thing?

4 - do you have more learning resources/tutorials with regards to At.js functions here

https://marketing.adobe.com/resources/help/en_US/target/ov2/c_target-ats-functions.html    

cheers,

View Entire Topic

Avatar

Avatar
Boost 50
Employee
ryanr701
Employee

Likes

188 likes

Total Posts

193 posts

Correct Reply

77 solutions
Top badges earned
Boost 50
Boost 5
Boost 3
Boost 25
Boost 100
View profile

Avatar
Boost 50
Employee
ryanr701
Employee

Likes

188 likes

Total Posts

193 posts

Correct Reply

77 solutions
Top badges earned
Boost 50
Boost 5
Boost 3
Boost 25
Boost 100
View profile
ryanr701
Employee

06-10-2017

Hi Saba,

So I've done this 2 ways.

  1. Use the console, but update all the tokens so they are referring to the browser tokens. Not great as you have to change some of the code.
  2. Activate my profile and then see what value I get after the profile is run. You can view this with the mboxTrace debugging tool (with the authorization token). Here is a help page which outlines how to get the authorization token and how to use the mboxTrace.
    1. Troubleshooting Content Delivery
    2. Note that for at.js implementations mboxTrace will be part of the mbox request response. If you view the network request in Chrome's debugger wit the preview mode you can easily see the different parts of the trace. For profile scripts you'll find them under profile > after execution > profileAttributes.

10-6-2017 7-28-11 AM.png