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 Conditional Based Activity

Avatar

Avatar
Validate 1
Level 1
johnuff
Level 1

Likes

0 likes

Total Posts

11 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
johnuff
Level 1

Likes

0 likes

Total Posts

11 posts

Correct Reply

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

18-02-2021

Wondering if its possible to show an activity based on asynchronous params, I know there is the targetPageParams but how would I trigger these params on a dynamic value that populated after Adobe Target is loaded such as an API call. Then how would I trigger the updated Param to the activity?

 

Is this at all possible?

Thanks

J

Accepted Solutions (0)

Answers (1)

Answers (1)

Avatar

Avatar
Ignite 1
Level 4
josejr19
Level 4

Likes

60 likes

Total Posts

117 posts

Correct Reply

13 solutions
Top badges earned
Ignite 1
Validate 1
Give Back 5
Give Back 3
Give Back 10
View profile

Avatar
Ignite 1
Level 4
josejr19
Level 4

Likes

60 likes

Total Posts

117 posts

Correct Reply

13 solutions
Top badges earned
Ignite 1
Validate 1
Give Back 5
Give Back 3
Give Back 10
View profile
josejr19
Level 4

18-02-2021

Out of the box there is not solid solution without some level of coding. Either route requires making another mbox call unless you hold up the first one which might impact the user experience.

 

Here are the two options I have entertained in the past:

1. Use an Adobe Launch rule to listen to a custom event or data element related to the data you are waiting from the API. Then fire another Adobe Target global mbox with the parameters including the data you need for Target to qualify the user for the experience. I have seen where the rule might actually live right in Adobe Launch that way you only call Adobe Target if needed and thus not needing to make multiple calls. Only in Launch can you fire multiple global mboxes for some reason which makes this one more appealing for those who want to minimize coding in Target experiences.

2. User the parent/child approach. This is when you create a "parent" experience which is going to be targeted to everyone essentially on the page in scope. In this experience you have an event listener or data element listener waiting for the data from the API and then you can chose again to execute your logic on the client side to decide if to call another mbox or just fire getOffer/applyOffer function with the parameters needed with the custom mbox name. With this approach you would then have form-based edited experience with the custom mbox name being targeted to users with the parameter key value pair needed to qualify.

 

Let me know if you need any more details.

 

Best of luck!

Jose