Adobe Target Standard vs Premium, Explained Feature by Feature

Adobe Target Standard covers A/B testing (including Auto-Allocate), multivariate testing, rules-based Experience Targeting, geo-targeting and server-side optimization through APIs. Adobe Target Premium includes all of that and adds Auto-Target, Automated Personalization, Recommendations and enterprise user permissions. So the real question isn't which edition is better. It's whether you have the traffic, catalog and team structure to use what Premium adds.

This guide sets out what each edition includes, based on Adobe's own product description and Experience League documentation. It explains each Premium feature with an example and the traffic Adobe says the AI features need. Then it covers how to decide, a sensible upgrade path and the cost drivers to model. If you're new to the platform, start with what Adobe Target is and how it works.

What does Adobe Target Standard include?

Target Standard is a full tool for testing and rules-based targeting, not a cut-down trial. In plain terms, a Standard team can run:

• A/B Test. Split traffic between two or more experiences and compare them over a planned test period.
• Auto-Allocate. An A/B test that sends more traffic to the leading experience while the test runs. It's part of Standard, even though people often file it under "AI".
• Multivariate Test (MVT). Test combinations of offers across several page elements to learn which element moves conversion most.
• Experience Targeting (XT). Show set content to a chosen audience, such as returning visitors. Geo-targeting adds location rules.
• Server-side and API delivery. Get decisions from your own servers or apps, as well as the browser.

You build most of this in the Visual Experience Composer (VEC), a point-and-click editor. There's also a Form-Based Experience Composer. Standard can be scoped for web, mobile web, mobile apps, email and server-side experiences such as kiosks.

What does Adobe Target Premium add?

Premium adds four things on top of Standard: Auto-Target, Automated Personalization, Recommendations and enterprise user permissions. Experience League puts a Premium badge on each Premium feature, so it's easy to check.

Auto-Target

Auto-Target is an option inside the A/B test workflow. You design several complete experiences. A machine-learning model then picks the one each visitor is most likely to convert on. It bases that on the visitor's profile and on how similar visitors behaved.

For example, a retailer might build four homepage versions, each led by a different product category. Auto-Target then learns which version suits which kind of visitor. Adobe says the models use a Random Forest algorithm and rebuild every 24 hours. At least 10% of traffic stays in a control group so you can measure lift.

Automated Personalization

Automated Personalization (AP) works with single offers, not whole experiences. You add a few offers to a few spots on the page. AP then learns which mix to show each visitor.

Three hero images and three headlines give nine combinations. AP decides which pair each visitor sees. Adobe warns that this adds up fast, so AP needs the most traffic of any activity type. It suggests Auto-Target for lower-traffic pages or for changes to page layout.

Recommendations

Recommendations shows products or content based on what visitors do. Its rules, which Adobe calls criteria, include "People who bought this also bought that" and "Recently viewed items". Adobe's examples include hiking shoes for someone who bought a backpack, or similar videos on a media site.

Premium also lets you drop a recommendation into A/B, Auto-Allocate, Auto-Target and XT activities as an offer. So you can test where a recommendations tray sits, or whether it beats hand-picked content. The older Recommendations Classic is no longer sold to new customers.

Enterprise user permissions

Enterprise user permissions split Target into workspaces and properties. The Adobe Admin Console calls workspaces product profiles. Each one holds its own users, activities, audiences and offers, much like a report suite in Adobe Analytics.

Picture a group with three brands. Each brand team gets its own workspace. An editor on one brand then can't launch tests on another brand's site. Standard still has roles (Observer, Editor, Approver and Publisher), but everyone shares one default workspace.

One catch from Adobe's docs: Recommendations items such as the catalog, criteria and designs sit outside the permissions model. Plan for that if several brands share Recommendations.

Adobe Target Standard vs Premium feature comparison

Here is the side-by-side view. "Yes" means Adobe's product description or Experience League lists the feature for that edition.

Both editions share the same usage limits in Adobe's product description, such as 500 experiences per activity. Premium adds one more. Recommendations, Auto-Target and AP activities together are capped at 10 on a single request.

Which Target features are the same in both editions?

Some useful features don't depend on the edition at all. A few need a second Adobe product instead.

• Analytics for Target (A4T). A4T makes Adobe Analytics the reporting source for an activity. You need both products. It works with A/B, Auto-Allocate, Auto-Target, XT, MVT and Recommendations, but not AP. Our page on connecting Adobe Analytics and Adobe Target covers the setup.
• On-device decisioning. It's open to all Target customers on the server-side SDKs or at.js 2.5.0 and later. It only supports A/B and XT activities, so Premium's AI features always need a live call to Adobe.
• AEM Experience Fragments. These need Adobe Experience Manager (AEM). They work in A/B, Auto-Allocate, Auto-Target, AP and XT, but not in MVT or Recommendations.
• APIs. Target has Admin, Profile, Delivery and Reporting APIs. The Recommendations API is a type of Admin API, so it only matters once you have Recommendations.

How much traffic do the Premium AI features need?

Adobe gives a rule of thumb for Auto-Target with a conversion goal. Plan for about 1,000 visits and 50 conversions per experience per day. The activity also needs at least 7,000 visits and 350 conversions in total. AP usually needs more, and Recommendations depends more on clean catalog data than on raw traffic.

Here's what that means for each feature:

• Auto-Target. By that rule, a four-experience activity needs roughly 4,000 visits and 200 conversions a day. A revenue per visit (RPV) goal needs at least 1,000 conversions per experience, because revenue varies more than conversion.
• Automated Personalization. Use the Traffic Estimator in the VEC. Adobe aims for models to be ready within half the activity's run or 14 days, whichever is shorter. Keep it to 4 to 6 locations with 4 to 6 offers each. Adobe also suggests an A/B test of the offers first.
• Recommendations. You need a catalog of items, sent by daily feed, the Entities API or page code. Product pages should pass the item ID and category. When an algorithm lacks data, backup recommendations fill slots with popular items.

For comparison, Auto-Allocate in Standard waits until each experience has 1,000 visitors and 50 conversions. Only then does it shift traffic. If your pages can't get there, the AI features will mostly serve random experiences while they wait for data.

Do you need Target Premium? How to decide

Choose Premium when you can name a use case and the data to support it. Good signs are busy pages with frequent conversions and a large catalog. So is a set of brands or teams that need separate access. If none of those apply yet, Standard will likely serve you better.

Team maturity is the one buyers skip. Machine learning boosts a program that already has a backlog, clean audiences and offers that really differ. Our Adobe Target personalization best practices cover how to build that base.

Good audience design also goes a long way in Standard. For a program built around high-intent visitor signals, see DWAO's Whirlpool high-intent personalization case study. If you're still comparing vendors, read our Adobe Target vs Optimizely comparison.

What is a sensible upgrade path from Standard to Premium?

Start on Standard and prove a steady testing rhythm. Then upgrade for one named use case that meets Adobe's traffic guidance. Upgrading for "AI" in general is how teams pay for features they never switch on.

A practical sequence looks like this:

1. Use all of Standard. Run A/B tests, Auto-Allocate and XT, and set up A4T if you have Analytics. This builds the experimentation program Premium depends on.
2. Find qualifying pages. Pull daily visits and conversions for your top pages. Mark the ones that clear Adobe's Auto-Target rule.
3. Prepare the data. Tidy profile attributes and shared audiences. If Recommendations is the goal, test that you can produce a reliable catalog feed.
4. Pilot one feature. Run Auto-Target on a qualifying page with a 50/50 control split for the clearest lift reading. Move to Adobe's 90/10 option once you trust the model.
5. Plan permissions early. Design workspaces and properties before you switch them on. Existing activities land in the Default Workspace and can be copied, not moved.

Treat this as an indicative range, not Adobe data: steps 2 to 4 often take one to two quarters. Data layer quality, catalog feed readiness and sign-off rounds move it most.

What drives the cost of Adobe Target Premium?

Adobe doesn't publish Target prices. It quotes each deal, so the useful work is knowing what moves the number.

• Edition. Premium is the larger license. DWAO's pricing guidance says the jump from Standard to Premium is where most negotiation happens.
• License metric and volume. Standard is licensed on annual page view traffic. Premium is licensed on annual page view traffic or server calls.
• Properties and channels. Adobe's pricing page lists the volume of digital properties and omnichannel delivery as factors. Channels are scoped in your sales order.
• Implementation. Catalog feeds, profile data, delivery set-up and workspace design all take effort. That's Adobe Target implementation work, priced separately from the license.
• Running the program. Someone has to build activities and read results, in-house or through Adobe Target managed services.

Our Adobe Target pricing guide goes through each driver and how to bring your own numbers to the negotiation.

Next steps: a quick checklist

Before you settle the Adobe Target Standard vs Premium question at renewal, work through these:

• List the Standard features you aren't using yet, especially Auto-Allocate, XT and A4T.
• Pull daily visits and conversions for your top 10 pages.
• Mark which pages meet Adobe's Auto-Target rule of thumb.
• Count the brands, regions and agencies that need their own workspace.
• Check whether your catalog can be sent as a clean daily feed.
• Pick one Premium use case and write down the lift that would justify it.

For an independent read on your setup first, DWAO's Adobe Target audit is a good place to start.