This blog highlights how to implement dynamic content that leverages both profile attributes and additional non-profile data sources. By extending personalization beyond simple profile attributes, marketing teams can deliver richer, more contextual experiences that boost engagement and conversion. 

@BLM  The difference in profile counts between your two audiences could be due to slight variations in audience filter logic (such as using different message IDs or segment rules), timing/data sync delays, or profile merges (identity stitching). You need to check that both audiences use the exact sa...

Thank you for documenting your testing! So if I understand the observations correctly,  If you create an email template from scratch within a Journey and add the mirror page link fragment, the link works.If you pre-save the template to the library (using the same fragment), and later use this templ...

@Michael_Soprano  Ok, yes, you can use a Custom Action in AJO to call an external API (i.e., Target Recommendations API) during the journey flow. The response from that API can then be mapped to journey attributes and used for personalization in email templates later in the journey, BUT here are the...

@Michael_Soprano  Don't think that Target recommendations are directly embeddable in AJO email templates.Target recommendations are intended for real-time web personalization, not static or batch email. AJO email templates are rendered server-side at send time, not at open time, so dynamic JS calls ...

@ASNeelima  Each audience entry typically includes metadata such as name, creation date, and description. In many cases (especially in B2B and recent UI updates), you will see a Created by (showing the username) or Origin (made using the Segmentation Service, imported/uploaded) column apart from th...

@Selliers  The /ee in your mirror page URL is essential—it routes the request to the email engine backend to render the online version of your email. If you get a link without /ee, it will not work. It's likely due to a template, personalization, or fragment issue—most often a hardcoded string or o...

@Michael_Soprano  As such, there is no integrated native system today that works across both AJO and Target to fully arbitrate conflicts automatically. When Adobe Target and the AJO Web channel use the same web real estate for personalization, the AJO experience should take precedence—but only becau...

@montezh2001, If I understand the requirement correctly, you want to send batch emails using external data sources, such as non-profits’ lists, without persisting that data in AEP or Campaign databases. I don't think there is any way to run a “batch” without at least staging the data for delivery pr...

@Michael_Soprano  The best practice is generally to create a separate Decision Scope for each placement. This allows you to control and personalize the offers shown in each distinct web placement (e.g., homepage banner, sidebar widget, etc.) and thus track, report, and optimize each placement indep...