Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

KMarchewaNew Participant

Support for More Specific Language TargettingNew

Description - When creating an Audience in Target, the platform allows users to target visitor's based on their browser language. Per the documentation, only a handful of languages are offered: https://experienceleague.adobe.com/docs/target/using/audiences/create-audiences/categories-audiences/browser.html?lang=en Since the platform only offers "major" language versions (English, Spanish, Italian, etc; ), it seems logical to assume that this would include language "subvariants" (i.e. English (United States). That is, if I create an Audience targetting "English" I would expect this to include visitors with a browser language of English (United States), English (United Kingdom), etc. Put another way, given that Target does not offer anything more specific, I would expect only the "primary subtag" of an IETF Language Tag to be taken into account; I would expect en, en-us, en-uk, and so on to be considered "English" for targetting purposes. However, this is not the case. An Audience that targets English language browsers does not match English (United States) or anything but "English" (with no variant). As such, this renders the language targetting nearly useless as the vast majority of users, at least in our region, will have some sort of language subvariant set in their browser (with en-us/English (United States being predominant for us).   Why is this feature important to you - The current Language targetting feature is essentially non-functional for our organization. Most visitors will have their browser language set to "English (United States)" or similar.   How would you like the feature to work - See above.   Current Behaviour - See above.

BrettBirschbach
BrettBirschbachNew Participant

Make Target UI Obsolete for Owners of AEMInvestigating

Request for Feature Enhancement (RFE) Summary: Make AEM + Target a truly seamless integration Use-case: Delivering Personalized Experiences as Standard Content Management Current/Experienced Behavior: User creates the default experience on an AEM page, creates XF in AEM, exports those XF in AEM, then swivels the chair over to the Target UI to create a Personalization Activity, selecting from the experiences exported from AEM to then deliver back to AEM.  This makes customers feel like Personalization is distinctly separate from Content Management, and that AEM and Target may "talk to each other" but are not truly an "integrated content marketing platform". Improved/Expected Behavior: Keep Target there behind the scenes, and even the UI for customers that don't have AEM.  But for customers that do have AEM, allow Activities to be fully created directly within AEM such that to a content author they don't even need to know that Target is a separate tool/technology.  I believe most, if not all of the APIs already exist to work with Target headlessly to create Activities, so let's just do those things inside AEM and not even talk about something called Target.   Having Target as a separate tool that needs to be learned is increasing the barrier of entry to personalized experiences.  Further, the more we can make personalization seem like just another "standard part" of content management, as opposed to some "special thing" you do with this other magical tool called Target, I think the more we'll see it used.

cristiano613359New Participant

Lower the risk of having an unresponsive server by restricting the page reach for the functionality “Create launches”Investigating

Request for Feature Enhancement (RFE) Summary: Lower the risk of having an unresponsive server by restricting the page reach for the functionality “Create launches” Use-case: A content author opens the Adobe Experience Manager (AEM) Launches interface (/libs/launches/content/launches) and clicks “Create”. The next step is to click to top-left button “+ Add Pages” to select a page or a folder. On the next screen, the content author selects “Included subpages”. The top-right button “Next” is clicked, the next screen is displayed and “Inherit source page live data” is clicked along with “with existing content”. The button “create” is clicked. Current/Experienced Behavior: The current behaviour is described above, with the mention the content author is allowed to select any page or node, even the top folder that might include a very large number of pages that will trigger AEM to create copies for all those pages. Due to the number of nodes, a site-wide transversal is triggered, resulting in an unresponsive AEM instance.   Improved/Expected Behavior: To prevent the situation described above we would suggest the following improved behaviour. When the content author selects a page or a node ensures he has the write permission for that page or node Restrict the number of pages or nodes to be included in the Launch by leveraging a configuration field via sling:osgiConfig. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 Service Pack 14 Customer-name/Organization name: Service Canada / Government of Canada Screenshot (if applicable):   Code package (if applicable):