Adobe Target

When utilizing A4T, the user may only select ONE report suite to push the data to. As an example, this makes reporting by device a bit more convoluted as segments will be needed to cut the data in such a way.

Inability to create more than one Target Instance within an Org ID. For Example, if we have multiple business units or regions under one org ID, we would like to have a target instance for each business unit - North America Org ID - which includes, US, Canada, Mexico - each of these regions should have their own target instance regardless of Org ID

When utilizing A4T as a reporting source, users are unable to apply Target Goal Settings. ie. Bar from entry; allow re-entry; keep user in activity etc.  

Since A4T data collection is done server side as opposed to client side, we are unable to see the variables fire within the debugger - makes for QA-ing our impression and clicks tags impossible.

We are unable to optimize based on custom metrics. Currently Target only allows success to be calculated on out of the box metrics - not a custom metrics built in Analytics. Because of this we are unable to utilize features like auto-personalization.

A4T does not allow the grouping of granular data from an uploaded source report.

A4T does not allow segmentation at the visit level. All of the A4T dimensions only allow for hit level data.

Analytics has an option to add opt-in links as part of its opt-out functionality. (using query parameters with the opt-out service)Add an Opt-Out Link Please add this feature to the Target opt-out link service. Adding an Opt-Out Link There are many use cases for this and even more now that we are post GDPR.  Also in this post GDPR world some vendors like TrustArc are incorrectly configured to disable ALL Target testing internet wide across all target users.

With regular A/B tests, we can write custom code.  Unfortunately, a lot of our tests require custom code since we use React components.  Right now, custom code is not available to use for MVT tests, which basically means we can't ever run an MVT test.  We would love to have the ability to create custom code for MVT tests.

I wanted to email you to provide somefeedback on one confusing email that you have getting auto sentout.   I just deleted a workspace for Adobe target, and when I didso, everyone who had access to that workspace received the below email. I think the email is confusing because I did not lose access toTarget.  I lost access to the one workspace because it was justdeleted.  I have had a number of people contacting me due to thisconfusing email, so it might make sense to update the wording a bit to mentionthey lost access to that specific adobe target workspace instead of saying theylost access to target as a whole. Excerpt from the email:Travis, you no longer have access to Adobe Target.MetLife Global has removed your access to Adobe Target.This does not affect your access to other Adobe products and  services.If you think this was done in error, please contact your administrator.

There are two features which are useful in Taerget Classic, but no in Target Standard. There two features needs to be implenmented for smooth migration.1. Monitoring campaign type2. Plug-ins

After having 40 experiences disappear in an instant I would love the chance to have the ability to recall past versions. Is storage an issue? Fine, charge me for it. It will be a bargain compared to the 3 weeks of lost work.

Can you add the ability to know what segments I use all the time and keep them in a special tab? I hate having to search every time I need to apply an audience. I use like 10 segments all the time, but I gotta search every time.

In the July 25 release of Adobe Target, the custom code UX was seriously degraded and should be rolled back to it's previous UX state.Horizontal Panel view removedIn the previous version, you could display the custom code panel vertically (as we are forced to use now) or horizontally across the bottom of the page.Custom Code view - Limited editing sizeThe custom code editing panel is restricted to a very small maximum size within a normal browser window.  This severely limits the amount of code you can see while editing, which increases the amount of scrolling you have to do to view the code.  The only workarounds I've seen thus far are to expand your browser across two monitors so the % allowed for maximum width is reasonable or to copy the code and do your editing in another application.  Neither are feasible or acceptable, considering the previous version did not handicap the editor so poorly.Closing the Editing panel on save / Interface to open Custom CodeWhen you save your changes

Is it possible to update the 'Country' dropdown in Target to 'Country/Region.'?Navigate to the Audience TabClick ‘Create Audience’Click ‘Add a rule’Select ‘Geo’Open the dropdownExpected Result: Country dropdown should be changed to ‘Country/Region’

Redirect offers currently change + to %20 when the "+" character is included in a query string. There is no need to convert the "+" character.

Currently the "option.id" in the response tokens is useless and cannot be mapped to anything. Please add in "offer.id" to response tokens. We do not want to get rid of the deprecated ttMETA plugin until offer.id works properly. Note you may also want to update the product documentation. "option.id" != "offer.id".

QA appendages currently get changed if an experience within the activity (ordered before) gets deleted. It would be nice to have unique QA appendages that remain consistant even after activities are deleted within the campaign.

Often I would like to change the experience inside of a campaign due to changes made from the website CMS. It think it would be a great feature to allow timing to be set on individual experiences within the campaign. This way we will not longer need to stay up until midnight to do a hot swap with the experience code.

In order to see where a particular offer is used you need to click on it and view the details to see which activities it is used in. It would be helpful to display a number next to each offer in the list that signifies how many activities / experiences the offer is used in.Also, a filter would be EXTREMELY helpful in the offer search to be able to filter by active/inactive offers. We find that our offer library has a ton of outdated items but we do not have an easy way to clean it out because there is no easy way to tell what is being used.

A4T currently only includes Activity and Experience level information. If we want to track offer impressions with Adobe Analytics we need to use workarounds that are clunky. For example, historically a way to track impressions of offers was to include a specific URL parameter in the CTA of the offer and then scrape the page for that parameter and store in an Adobe Analytics list var. Or you could potentially use the information from the ttMETA plugin to pull info from the ttMETA object. Or you could use Response Tokens (once Offer ID is supported). However, the cleanest solution would be to include this information in the A4T data so its stitched via SDID. With all other solutions we have to defer our analytics pageview tag until all Target calls are complete or fire unnecessary analytics tags.

The current URL search for activities only searches the base URL that the Activity was setup against. It does not consider any additional pages for that activity. Additional pages and other URL based configurations should be considered in the search.

We run automated nightly regression on our website, however this uses mboxDisable to regression test the base page without Target. We would like to regression test Target activities, but we would need a comprehensive list of preview URLs to do that. We are currently building a list of these URLs manually in a spreadsheet. Now that QA URLs persist, this is feasible. However it would be nice to have an automated solution via Target APIs to pull preview URLs or a way to export in bulk in the Target UI.

In the Activity search, allow the user to search/filter activities that leverage a specific regional mbox. This is helpful for SPAs and mobile apps where the global mbox is not used frequently.

It appears to be a known functionality that when an audience refinement is added to an Activity the QA links only work if you actually qualify for the Audience Refinement. In order to view your QA experience links before publishing, you have to remove the Audience Refinement. This is agnostic of whether you have 'Match audience' turned on or off. This does not seem logical or efficient. The 'match audience' functionality should also affect the Audience Refinement or there should be some other way to view your QA links without having to remove the audience refinement.