Adobe Target

Hi, welcome. You can create a separate collection to sort out the different types of content, so you could have a Collection that holds products, and another that contains articles, and then you apply whichever one you need to a specific Recommendation. 

Make sure you have a good plan on how to separate them, it could be a flag passed in as an entity.parameter, or be based on the URL or some other piece of that is distinctly different between the two collections. 

ok thanks!

Hi arehmeyer for #1 this sounds like Experience Fragments. You can create them in AEM and shared them out to Target then pull them in via the Visual Experience Composer. 

Here are AEM XF to Target links

Adobe Experience Manager 6.4 reimagines the personalization workflow between AEM and Target. Experiences created within AEM can now be delivered directly to Adobe Target as HTML Offers.

https://experienceleague.adobe.com/docs/experience-manager-learn/sites/personalization/experience-fr...

Integrating AEM with Target

https://experienceleague.adobe.com/docs/experience-manager-65/administering/integration/target.html

https://medium.com/adobetech/experience-fragments-and-adobe-target-d8d74381b9b2

Exporting Fragments to Target

https://experienceleague.adobe.com/docs/experience-manager-65/administering/integration/experience-f...

https://experienceleague.adobe.com/docs/experience-manager-learn/sites/experience-fragments/experien...

Hi arenmeyer, can you clarify #2 a little? Are you talking about Target offer code or is this a reporting question?

reporting please.

Ex: Our HP has 3 components we're testing. Could you please share the tagging methods that work best so we're able to track at the componment level.

Hi arehmeyer

Assuming you're using Abode Analytics, you can build a script to send along the component name inside the Target Offer. 

Here is an example of tracking a user who clicks on a Recommendation component. 

var recsClick = function(entityData) {
  if (typeof s !== 'undefined') {
    s.linkTrackVars = 'events,eVar3';
    s.linkTrackEvents = 'event7';
    s.events = 'event7';
 
    if (typeof entityData !== 'undefined') {
      s.eVar3 = entityData;
    }
 
    s.tl(this,'o','Target Recs Click');
  }
};
 
var targetRecEntities = document.querySelectorAll('[data-targetRecEntity]');
 
if (targetRecEntities) {
  targetRecEntities.forEach(function(link) {
    link.addEventListener('click', function(e) {
      recsClick(link.dataset.targetrecentity);
    });
  });
}
 

Hi @arehmeyer, if you don't have access to Analytics, you can try using Target Click tracking and Event tracking to get how a particular element performs.

1) Click Tracking: Tracks Clicks on any element as a success metric:

https://experienceleague.adobe.com/docs/target/using/activities/success-metrics/click-tracking.html?...

2) Event Tracking: This functions fires a request to report user actions (clicks and conversion):

https://experienceleague.adobe.com/docs/target-dev/developer/server-side/core-principles/event-track...

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

Yes, you have John, Justin and Bill standing by. You may want to refresh the page. 

@neerspinner thank you so much for this feedback! Indeed we are piloting this new interface for the Community Q&A Coffee Breaks and are ironing out the process - taking notes and making plans! Stay tuned for updates  and please feel free to DM me with any additional feedback on this interface! 

Not related, but I have one of their die-cast cement trucks and one of their baseball hats. 

haha! cool!

@ambikaTewari_ATCI   - At this moment this is currently not possible.

Recs is definitely something that requires a fair amount of planning in the implementation process. I would suggest starting with a list of placements that you want to use, and make a list of what types of things you need to know to do what you want to accomplish as far as the business rules/logic. That list will often help you plan the type of data you need to collect to support that type of logic. (Showing only Gluten Free products would require indicating in the data which products are Gluten Free). 

Also take the template design you want to use and deconstruct that, so you know what pieces are required to make it dynamic to your requirements. You may need more than the basic "name, thumbnail, and URL" in order to do things like indicating sale prices, closeouts, etc. 

As far as the placements on the site, product detail pages tend to have the most impact, and then the shopping cart flow, and then the home page. 

I'd also recommend investigating User Based Recs and Cart Based Recs, which leverage our AI capabilities. They work as a "multi-input" recommendation so we're basing it on multiple items instead of a single item. They allow you to do very personalized recommendations in any part of the site based on the user's behavior. 

great feedback - thank you so much!

Thanks for the question. There is an option at the Activity level to Download Recommendations data. This allows you to validate that the entities you are seeing are the correct entities based on collected behavioral data and your Criteria settings. This download does not contain event counts. This information is generally available within analytics. From our combines perspective, this is not currently on the product roadmap.

Hello,

For o/p are you referring to on-page or something else?

Best practices for clicked element selection is to make sure you are using IDs on the specific element you want to track (example: <div id="myId">.  Target looks at the first ID it sees on the page. 

If the only ID is a near parent of your element, you should be good, but if the only html ID is far, you might have content at runtime that changes the html structure.  If this is happening, your tracking won't work. 

So best practice is to have an html ID on that specific element and you will avoid those potential issues.  An even better solution, if you have Adobe Analytics, is to leverage the a4t feature (Analytics for Target).

If you don't have access to a4t, you can change/force the "clicked an element" value.  For this, go in goals and settings, hit "edit" right to "clicked an element".  On the next page, hover over the "Selected Elements" option and hit the little pen icon.  There you will have the possibility to enter a more specific css string (example: if your element don't have an ID but have a unique class, you can change the field's value and only input your ".myClass" value there.

Here you go. 

Hi @arehmeyer, thanks so much for joining us this morning for today's coffee break chat with the experts! In addition to the excellent resource that @jmosbaugh shared, please also find these webinars: 

1. Zero to Hero: Starting and Scaling a Personalization Program

2.  

   City National Bank Tool Kit: How to Achieve the Top 1% in Digital Optimization

Hope these are helpful!

Warmly,

Amelia

Hi @ambikaTewari_ATCI There is an option to Export Order Details to CSV in the Reporting section of your Activity.

Note that this option is not available for Recommendations activity type. However, it is available in AB and XT activities where you can use Recommendations as an offer.