Replies

Avatar

Avatar

ramih79012734

Employee

Avatar

ramih79012734

Employee

ramih79012734
Employee

22-07-2020


@rajneesh_gautam wrote:

@Jon_Tehero  - thanks for this initiative. Quick question on Adobe Target Console  - any plans to add Priority on the Activities list page so that we can sort activities and find ones that are higher than a particular one (will help in troubleshooting immensely).


Currently we have a collisions tab https://docs.adobe.com/content/help/en/target/using/experiences/vec/activity-collisions.html

 

The list shows the status and priority of each potential collision, along with other information. You can use the status and priority to help you determine the likelihood of a collision occurring.

Avatar

Avatar

Jon_Tehero

Employee

Avatar

Jon_Tehero

Employee

Jon_Tehero
Employee

22-07-2020


@Amelia_Waliany wrote:

Hi @Jon_Tehero, thank you for you time today! This question was posted by Target Community member @FGHPhilJ :

Morning Community, looking for advice. We are just at the point we are starting to launch recommendations and I was looking to find a document which says the pros and cons for using Analytics over an MBox.


Hello@FGHPhilJ , we have some good guidance on our "Feeds" article. We typically encourage sending data directly to Target via a target request or our "save entities" API for the fastest results. 

Avatar

Avatar

Jon_Tehero

Employee

Avatar

Jon_Tehero

Employee

Jon_Tehero
Employee

22-07-2020


@rajneesh_gautam wrote:

@Jon_Tehero  - in order to democratise the use of Adobe Target among non-technical marketers, I'd recommend if the Experience Templates can be made part of the console itself so that marketers do not have to copy it and make changes to the code. Competitor tools like Insider are using this approach and some of our users find it much easier. 


Hi @rajneesh_gautam, thank you for sharing the feedback. We don't have any immediate plans to do this but it is really helpful to hear how you and your team are using the experience templates. I will make sure to take this feedback back to our team.

 

 

Avatar

Avatar

ramih79012734

Employee

Avatar

ramih79012734

Employee

ramih79012734
Employee

22-07-2020

Hi @Jon_Tehero, this question was posted in the community by @LordOfTheRings:

 

As a part of recommendations, we want to show the recommended items to a loggedIn user on the basis of his purchase history and not on the basis of purchase history of all users.

For example, If a user John has redeemed few offers on the website then I would like to show John similar offers on the website. The recommended offers must be 'similar' to the offers John has redeemed in past. The Recommended offers must not include the redeemed history of other users.

How do we maintain the user profile in the recommendations ?

Avatar

Avatar

tony_papousek-e

Avatar

tony_papousek-e

tony_papousek-e

22-07-2020

Hi @Jon_Tehero Thanks for hosting. Couple technical questions about the future of at.js:
1. Are there any plans of distributing the library over npm (similar to the@adobe/target-nodejs-sdk package). Ideally, I'd love something with built-in type interfaces that can be imported like any other module. Given the org-specific settings, maybe something like an Adobe-hosted registry can help with that (i.e. npm install https://npm.adobe.com/target/client_code/at.js_2.3.1.tgz). Alternatively, hosting a generic package on npm and requiring a config object on startup could simplify the process.
2. Are there plans to "promisify" all the methods? I know getOffers() and applyOffers() support it to some degree, but I'd love to have a library where `await methodName()` can be used throughout. For example: `let offer = await adobe.target.getOffer(params); await adobe.target.applyOffer(offer)`

Avatar

Avatar

Jon_Tehero

Employee

Avatar

Jon_Tehero

Employee

Jon_Tehero
Employee

22-07-2020


@ramih79012734 wrote:

Hi @jtehero, this question was posted in the community by @LordOfTheRings:

 

As a part of recommendations, we want to show the recommended items to a loggedIn user on the basis of his purchase history and not on the basis of purchase history of all users.

For example, If a user John has redeemed few offers on the website then I would like to show John similar offers on the website. The recommended offers must be 'similar' to the offers John has redeemed in past. The Recommended offers must not include the redeemed history of other users.

How do we maintain the user profile in the recommendations ?


Hello, @LordOfTheRings! This can be done by basing the recommendation off of the "last purchased item"

Jon_Tehero_0-1595438610938.png

You also have a lot of flexibility to store a different item in the user's profile and base the recommendations off of that particular item. For example, you could setup something like this:

Jon_Tehero_1-1595438676999.png

So you could have several different attributes in the user's profile related to offer's redeemed. Finally you can dynamically exclude entities from being recommended again. Check out this Recommendations FAQ and search for "Can I dynamically exclude an entity?"

 

Avatar

Avatar

ramih79012734

Employee

Avatar

ramih79012734

Employee

ramih79012734
Employee

22-07-2020

Hi @Jon_Tehero, this question was posted in the community by @kishorek1264980:


I am new to target, i am trying to create a offer and as a response trying to get a offer id from the api response via Postman.

https://admin.testandtarget.omniture.com/api?password=somepassword&amp;offerName=someOfferName&amp;c... id&amp;folderId=&amp;content=<div>somecontent</div>

But when i hit the above api in postman i am get 403 legacy api access denied. May i know how to use this in postman.

Avatar

Avatar

Jon_Tehero

Employee

Avatar

Jon_Tehero

Employee

Jon_Tehero
Employee

22-07-2020


@tony_papousek-e wrote:

Hi @Jon_Tehero Thanks for hosting. Couple technical questions about the future of at.js:
1. Are there any plans of distributing the library over npm (similar to the@adobe/target-nodejs-sdk package). Ideally, I'd love something with built-in type interfaces that can be imported like any other module. Given the org-specific settings, maybe something like an Adobe-hosted registry can help with that (i.e. npm install https://npm.adobe.com/target/client_code/at.js_2.3.1.tgz). Alternatively, hosting a generic package on npm and requiring a config object on startup could simplify the process.
2. Are there plans to "promisify" all the methods? I know getOffers() and applyOffers() support it to some degree, but I'd love to have a library where `await methodName()` can be used throughout. For example: `let offer = await adobe.target.getOffer(params); await adobe.target.applyOffer(offer)`


Hi Tony, for #1, we currently have no plans to open source At.js, however, the AEP Web SDK is open sourced. This can be a consideration for the AEP Web SDK. Regarding #2, we have no plans in the roadmap as of now, but it's a great feature request. I've shared this with my colleague David Son to consider for our backlog.

Avatar

Avatar

Jon_Tehero

Employee

Avatar

Jon_Tehero

Employee

Jon_Tehero
Employee

22-07-2020


@ramih79012734 wrote:

Hi @jtehero, this question was posted in the community by @kishorek1264980:


I am new to target, i am trying to create a offer and as a response trying to get a offer id from the api response via Postman.

https://admin.testandtarget.omniture.com/api?password=somepassword&amp;offerName=someOfferName&amp;c... id&amp;folderId=&amp;content=<div>somecontent</div>

But when i hit the above api in postman i am get 403 legacy api access denied. May i know how to use this in postman.


That looks you are trying to use outdated API. Check out our current API docs at https://developers.adobetarget.com. You can use the Create Offer API and include a "dynamic token" in your offer to return information about your offer. For example, the following will return the offer id:

${campaign.recipe.id}

See more great dynamic token examples here.

Avatar

Avatar

Amelia_Waliany

Employee

Avatar

Amelia_Waliany

Employee

Amelia_Waliany
Employee

22-07-2020

HI @Jon_Tehero, great insights here! This question was posted by Target Community member @MA1985_CG :

 

Hi, My requirement is to show each experience only for 3 times. Once user seen 1st experience as per the order show 2nd experience and so on.

I understand that we can use below script for frequency but this would work based on mbox name but looking option at the experience level Any thoughts?

mbox_location1 - experiencename_1

mbox_location1 - experiencename_2

 

var frequency = user.get('frequency') || 0; if (mbox.name == 'mbox_location1') { return frequency + 1; }

 

we are recording experience name value in Adobe Analytics but as per my understanding we can't use data layer value in profile script.