Enterprise Editions Comparison

Enterprise 1

Enterprise 2

E2.0 with Person Model

Other than a finished email, no granular control over individual pieces of content or control over who sees what.

Using sophisticated combinations of roles and permissions, the Administrator can define user views and actions on every item available in the Content tab of the application.

Unless noted, the functionality with person model works the same as Enterprise 2.0.

Images

• All portfolio items from the Admin account are automatically visible and available in all Lock & Publish account 'global images'. 
• Images loaded at the Lock & Publish account level cannot be shared or published to other accounts.

• Users in any business unit, with the role and permissions to do so, can upload images into the Shared Portfolio making them available for other business units and users.

Templates

• All templates from the Admin account are automatically visible and available in the Lock & Publish account 'global templates'. 
• Templates loaded at the Lock & Publish account level cannot be shared or published to other accounts.

• Users in any business unit, with the role and permissions to do so, can create Templates in the Shared Templates folder making them available for other business units and users.

Stored Content

• All stored content in the Admin account is automatically visible and available in the Lock & Publish account 'global content'. 
• Content created and stored at the Lock & Publish account level cannot be shared or published to other accounts.

• Users in any business unit, with the role and permissions to do so, can create and save content in the Shared Content folder making it available in other business units and for other users.

Emails

• When created at the Admin level, emails can be published and made available to select Lock & Publish account(s).  Content areas within the email can be locked to prevent changes.
• Emails created at the Lock & Publish account level cannot be shared or published to other accounts.

• Users in any business unit, with the role and permissions to do so, can create emails in the Shared Emails folder for other business units and users.
• Content areas with the email can be locked by the creator of the email to prevent changes.

Surveys

• Can be created at the Admin or Lock & Publish level, but cannot be published to other accounts

• Not available

Dynamic Content

• Can be created at the Admin or Lock & Publish level, but cannot be published to other accounts

• Emails containing Dynamic Content can be shared.

Simple Automated Emails

• Can be created at the Admin or Lock & Publish level, but cannot be published to other accounts

• Users with the appropriate roles and permissions can create SAS emails but cannot share them.

Landing Pages

• Can be created at the Admin or Lock & Publish level, but cannot be published to other accounts

• Users with the appropriate roles and permissions can create landing pages but cannot share them.

Enterprise 1

Enterprise 2

E2.0 with Person Model

Data structures, subscriber attributes and mail history are unique to each Lock & Publish account and not shared across the enterprise.

A single All Subscribers list is stored at the Admin level and shared via filter criteria to other business units.

In the future all new Enterprise 2.0 accounts to be provisioned with the Person Model.

Attributes

• Attribute set is not shared between the Admin and Lock & Publish accounts
• Each account needs to configure its own attributes

• Admin defines the attribute set for the entire enterprise
• Only Admins can create profile and preference attributes

• Admin creates a set of common attributes
• Admin determines if each attribute can be used "locally" by BUs
• Business Units can add their own attributes to the common set

Attribute Values

• Unique to each account, i.e. a subscriber can have blue eyes in one Lock & Publish and brown in another

• Attribute values are persistent across all business units, i.e. if subscriber has blue eyes on the All Subs admin account, they will have blue eyes in every instance
• Changes made in any BU are reflected across the enterprise

• Values can vary by account
• If a BU, with permissions to "localize" a common attribute, does not populate the attribute  value, the Admin value is be used by default

Subscription & Profile Center

• Relative to the lists and attributes of the distinct Lock & Publish account
• Updates made via the subscription and profile pages are reflected only in the account that sent the originating email

• By default, the same for every BU
• Updates made via the subscription and profile pages are reflected across the enterprise

• Configurable to support multiple use cases
• If an attribute is marked "use local value" updates are made only within the corresponding BU
• If an attribute is "Common" then updates are applied to the master list

Unsubscribe

• Unique to the account the email was sent from, unsubscribe data is not shared between Lock & Publish accounts or with the Admin level

• Option to post unsub status across entire enterprise, across a BU or at suppression list level

• Configurable to support multiple use cases

Bounce History

• Unique to the account the email was sent from, bounce history is not shared between Lock & Publish accounts or with the Admin level

• Aggregated across all BUs

Subscriber Key/Unique ID

• Can be different for each Lock & Publish account

• Defined for the Enterprise and common to all BUs

• Introduction of Person ID to tie all profile, demographic, modality, subscription preferences together

Lists

• Lists are not visible or accessible between the Admin and Lock & Publish accounts
• On Your Behalf accounts can view, edit and update subscribers assigned to them

• Filtering rules can be defined by the Admin to determine which subscribers a BU has access to
• Changes made in any BU are reflected across the enterprise

• Appear as lists to the user, but are built on data extensions
• BUs can maintain their own lists and/or share elements of the master list

Data Extensions

• An Lock & Publish can access data extensions in the admin account using query activities or AMPscript

• A shared data extension is available to all BUs in its entirety

• BUs can maintain their own data extensions or share a master DE

Enterprise 1

Enterprise 2

E2.0 with Person Model

Administrators use a simplistic org chart model to create parent/child account relationships with a limited set of controls over permissions.

Administrators have unlimited, centralized control on how to structure the enterprise, account relationships, and role and user permissions.

Sub Account Creation

• 'Top down' approach with creation of Admin and Lock & Publish accounts; Lock & Publish accounts are stand alone Core accounts
• Configuration is required for each account and often requires intervention from services or support to complete
• Must navigate back to the org chart, find the Lock & Publish and user in order to impersonate an account

• No predefined hierarchy for sub accounts
• Select a BU from a dropdown list in the persistent task bar for easy impersonation

On Your Behalf Sending

• Sub account required for each sender.  Sender can have login access to update subscriber data and/or view tracking history

• Admins dynamically populate the from field in the sender profile and are not require to create a new account for each from name

Permissions

• 13 available permissions that focus on restricting user functions, such as the ability to create new emails or delete lists

• Every application element has associated permissions for viewing, updating, deleting, exporting etc
• Roles are combined sets of permissions
• Users are assigned a role(s)

Enterprise 1

Enterprise 2

E2.0 with Person Model

On Your Behalf

• On Your Behalf users have a login to view tracking results relevant to the subscribers assigned to them

• Tracking at the aggregate/job level, but not broken out by Sender Profile

Sub Account

• Account Send Summary provides visibility into Lock & Publish tracking results for defined time period

• Account Send Summary provides visibility into BU tracking results for defined time period

Enterprise 1

Enterprise 2

E2.0 with Person Model

Measures

• Work as expected within Admin or Lock & Publish account

• Work as expected.

Reply Mail Management

• Configurable for each Lock & Publish account

• Configurable for each BU

Brand Builder

• Each Lock & Publish account can create their own brand identity

• Branding can be created for Administrators and BUs, who can share a brand or have their own.