ÃÛ¶¹ÊÓƵ

Benefit

Description

Single sign-on

Analytics users can sign in to the Experience Cloud and all solutions using their ÃÛ¶¹ÊÓƵ ID or Enterprise ID. This sign-in enables access to integrated solutions and core services in the Experience Cloud.

After the migration, users who attempt to sign in via legacy logins ( my.omniture.com and sc.omniture.com) are redirected to experiencecloud.adobe.com.

Manage user identity and permissions

Analytics administrators can manage users and permissions exclusively in the .

Manage products and core services

• Invite new users
• Create product profiles
• Grant users permission to specific products and services
• Gain access to cross-solution core services available in the ÃÛ¶¹ÊÓƵ Experience Cloud

Question / Task

Answer

I am an Analytics administrator and received a pre-migration email. What do I do first?

Verify that you have an ÃÛ¶¹ÊÓƵ ID and can access the .

If not, contact . (You should first contact your system or product administrator who can invite you to the proper organization.)

AEM integrations with Analytics

AEM users with an integration to Analytics will need to change their configuration to use the Analytics shared secret instead of the password.

You should do this before the migration is enabled. Once the migration is disabled, the originally configured password will no longer be valid.

To obtain the shared secret in Analytics

The shared secret can be obtained from Analytics ( Analytics > User Management) and is different for each user.

To update your AEM configuration with the shared secret

See .

Update Report Builder

Important: Update your installation of Report Builder to the latest version.

When does the migration begin?

ÃÛ¶¹ÊÓƵ will notify Analytics administrators via email with instructions about when the migration will begin.

Migrations to the ÃÛ¶¹ÊÓƵ Admin Console will occur in waves. On the day of migration, ÃÛ¶¹ÊÓƵ notifies Analytics administrators and grants them access to the migration tool. After a login company meets the criteria defined for each migration wave, ÃÛ¶¹ÊÓƵ will:

• Set the start and end dates for the company's migration.
• Send an email notification to the company's current Analytics administrators, approximately 30 days before their migration.
• Display an in-product notification informing administrators of the start date of the migration.

On the day of the migration, your former permission groups are automatically copied to the ÃÛ¶¹ÊÓƵ Admin Console. You will no longer be able to invite new users or create new groups in Analytics Admin Tools.

After the migration:

• Administrators will use the ÃÛ¶¹ÊÓƵ Admin Console to manage their Analytics users and permissions. (You will no longer use the user management interface in Analytics > Admin > User Management.)
• Users will access Analytics using their ÃÛ¶¹ÊÓƵ or Enterprise ID through the Experience Cloud instead of my.omniture.com.

What will happen on the start date of the migration?

At 10:00 a.m. UTC on the start date of the migration:

• Your existing permission groups in Analytics will be replicated automatically in the ÃÛ¶¹ÊÓƵ Admin Console as Product Profiles, including their description and granular permissions across report suites, metrics, dimensions, Analytics, and Report Suite Tools.
• If any of your current Analytics users were created in the ÃÛ¶¹ÊÓƵ Admin Console (meaning they have a linked ÃÛ¶¹ÊÓƵ/Enterprise ID), they will be added to the appropriate Product Profiles in the ÃÛ¶¹ÊÓƵ Admin Console.
• The User Management section under the Admin tab in Analytics will be set to read-only. You will no longer be able to create new users or permission groups here and will need to perform both these functions in the ÃÛ¶¹ÊÓƵ Admin Console. See Unsupported Analytics features in the ÃÛ¶¹ÊÓƵ Admin Console for more information.
• As an administrator, you will be granted access to the User ID Migration tool. Additionally, an in-product notification appears that includes the end date of the migration (typically 60 days in the future) in addition to links to help content and FAQs.
• You will be granted access to a Permissions tab in the ÃÛ¶¹ÊÓƵ Admin Console that allows you to create Product Profiles with all the granular options you are familiar with in Analytics.

How do I migrate user IDs?

Click Migrate User IDs on the Admin page, under User Management. Use the tool to add users to product profiles in the ÃÛ¶¹ÊÓƵ Admin Console (replicated from permission groups in Analytics). You can migrate user IDs at your own pace.

Administration privileges are required. Once the migration is complete, it cannot be reversed.

On the end date of the migration, my.omniture.com access will be disabled for users within their login company. Users (including those that are yet to be migrated) will be redirected to login via the new Experience Cloud URL ( experiencecloud.adobe.com)

Note: ÃÛ¶¹ÊÓƵ recommends taking the opportunity to perform an audit of your users and groups before migrating. Delete old and unused accounts, or accounts that should no longer have access to the product (such as employees no longer with the organization).

Related topic: Migrate Analytics user accounts for Enterprise and Federated IDs.

Will the migration affect my Analytics implementation or how data is collected?

No.

The migration tool exists to help you transition user IDs and permissions from Analytics User Management to the .

How long does the migration process take?

All current Analytics administrators will receive a pre-migration notification email four weeks prior to the migration. (The actual start date will appear in the Analytics interface.)

When the migration begins, administrators will have 60 days to complete the process.

Can I expedite my migration?

Yes. However, ÃÛ¶¹ÊÓƵ recommends that you use the time before the migration begins to:

• Verify that you are an Analytics product administrator in the ÃÛ¶¹ÊÓƵ Admin Console.
• Communicate to your user base that their login experience will change when the migration begins.
• Audit your current users and permissions and perform clean-up activities.

To expedite your migration, contact your ÃÛ¶¹ÊÓƵ Account Team at and submit a request for an earlier start date.

I am an Analytics administrator without access to the ÃÛ¶¹ÊÓƵ Admin Console. Who can help me gain access to the ÃÛ¶¹ÊÓƵ Admin Console?

Any system or product administrator that has access to your organization's ÃÛ¶¹ÊÓƵ Admin Console can give you access. If you are not sure who within your organization has administrator privileges in the console, contact .

Can I postpone the migration start date?

Yes. Contact .

See below for a description of the changes to your current Analytics User and Permissions management on the start date.

Now that my company is migrating to the ÃÛ¶¹ÊÓƵ Admin Console, where do I create new users and permission groups before the start date of the migration?

Before your migration start date, you can create users in the ÃÛ¶¹ÊÓƵ Admin Console or in Analytics > User Management.

After migration begins, you can create users and permission groups only in the ÃÛ¶¹ÊÓƵ Admin Console.

see the Migration section below for more details on what happens on the start date of the migration.

When can I implement single sign-on using Federated IDs?

A tool will be available soon in the ÃÛ¶¹ÊÓƵ Admin Console that enables you to change ID types from ÃÛ¶¹ÊÓƵ IDs to Federated IDs. During the migration, you cannot migrate users as Federated IDs.

Question

Answer

How are permission groups replicated to the ÃÛ¶¹ÊÓƵ Admin Console? What about my users?

A migrated Analytics group is a called a Product Profile in the ÃÛ¶¹ÊÓƵ Admin Console. Permission settings for the original group are retained in the migration. However, the users assigned to the group are not migrated. When a user belonging to that group is migrated using the migration tool, that user is assigned to that product profile.

For example, a West Coast Operations permission group that entitled its members to Report Builder and Analysis Workspace (with certain report suites, metrics, dimensions) will become a West Coast Operations product profile.

Can I delegate the migration effort to another administrator?

Once your migration begins, any administrator that accesses your Analytics instance via the Experience Cloud can use the migration tool to begin (or continue) migrating users.

Can I update permission group membership for un-migrated users?

Yes. You can change the group membership of un-migrated users from within the Analytics User Management section.

Awaiting clarification from Ashok about where that's done.

Can I create users and permission groups in Analytics after my migration begins, and then use the migration tool to move them to the ÃÛ¶¹ÊÓƵ Admin Console?

No. Once migration begins, all new users and permission groups (called Product Profiles in the ÃÛ¶¹ÊÓƵ Admin Console) must be created in the ÃÛ¶¹ÊÓƵ Admin Console.

Would users I migrate using the migration tool be assigned the same permissions they had in Analytics?

Yes. Users migrated using the tool will be accorded the permissions they currently have in Analytics. Furthermore, they will retain access to their Analytics assets (like segments, projects, calculated metrics, and so on) when they access Analytics via the Experience Cloud.

Do users I migrate to the ÃÛ¶¹ÊÓƵ Admin Console continue to have access to Analytics using my.omniture.com?

Yes. Migrated users will continue to be able to access Analytics using their existing user name and password via my.omniture.com until the end date of the migration, unless you disable their legacy login access via the migration tool.

Two or more of my users have the same email ID in their Analytics record. What happens if I migrate them?

Because user accounts in the ÃÛ¶¹ÊÓƵ Admin Console require unique email IDs, you will run into a "Duplicate Email ID" error when you try migrating more than one of these users. You can update the email IDs of un-migrated users under the User Management (legacy) section before you retry the migration.

What do I do after migrating my users?

Disable their legacy login access to my.omniture.com. You will not be able to turn off legacy login unless they have been migrated.

Can I track the migration process?

The migration tool includes a dashboard that displays how many of your users have been successfully migrated, and how many of them have their legacy login disabled.

Ideally, you will have successfully migrated your login company to the ÃÛ¶¹ÊÓƵ Admin Console when a 100% of your users have completed migration and have had their legacy logins disabled.

I need to perform user and permission management during the migration. Which tool can I use to perform this task?

After the migration begins, you will use the ÃÛ¶¹ÊÓƵ Admin Console to create and manage new users and product profiles.

What do my users experience when I migrate them using the tool?

They will receive a welcome email addressed to the email ID in their Analytics user record, notifying them about their new way to access Analytics via the Experience Cloud. If they do not have an existing ÃÛ¶¹ÊÓƵ ID, they will be prompted to create one, after which they can access the solution using their ÃÛ¶¹ÊÓƵ ID.

Can I use APIs to migrate my users instead of using the migration tool?

No. You must use the migration tool to ensure all your existing users are migrated to the ÃÛ¶¹ÊÓƵ Admin Console.

What Analytics user-management features are not available in the ÃÛ¶¹ÊÓƵ Admin Console?

• Asset transfer
• User expiration
• User logs

These will remain available to you in Analytics user management.

See Unsupported Analytics features in the ÃÛ¶¹ÊÓƵ Admin Console for more information.

We created several configurations in the ÃÛ¶¹ÊÓƵ Admin Console and mapped them to Analytics permission groups. What will happen to those configurations when the migration begins?

Analytics permission groups are recreated in the ÃÛ¶¹ÊÓƵ Admin Console as product profiles, just like all your other groups. This means you will see two product profiles in the console that essentially have duplicate permissions. You can delete duplicate product profiles from the ÃÛ¶¹ÊÓƵ Admin Console.

What is my next step after migrating user?

Once you have migrated the user or a set of users, your next step is to disable their legacy login via my.omniture.com. You can do that by selecting these users in the migration tool and clicking on the contextual "Disable Legacy Login" option that appears at the top of the screen. Note that this option is only visible when you select a user or set of users that have all been migrated successfully to the ÃÛ¶¹ÊÓƵ Admin Console.

What happens on the migration end date?

After the migration end date (60 days from the start of the migration), all users within your login company are redirected to login via the Experience Cloud login page using their ÃÛ¶¹ÊÓƵ IDs.

I haven't been able to migrate all my users by the migration-end date. Would un-migrated users lose their access to Analytics?

Users that have not been migrated by the end date will be redirected to the Experience Cloud login page (experiencecloud.adobe.com) and will be unable to access Analytics. However, you will continue to have access to the migration tool so you can find and migrate them to restore their access.

Question / Issue

Answers

Deleting users from the ÃÛ¶¹ÊÓƵ Admin Console

In Analytics, a deleted user is set as expired, but the account continues to exist. Preserving the account enables the transferring assets, such as segments, calculated metrics, scheduled reports, projects, and so on.

Account expirations

You can manually set an account expiration date in Analytics in Admin Tools. Once the expiration date is met, the user will not be able to access Analytics, but their actual Experience Cloud user account (e.g. ÃÛ¶¹ÊÓƵ ID, Enterprise ID, Federated ID, etc.) doesn't expire. They can still log into Experience Cloud, they just won't be able to click into Analytics.

Question / Issue

Answers

Log-in As

Admins migrating to the ÃÛ¶¹ÊÓƵ Admin Console will no longer be able to use the "Log-In As" function to access non-Admin user accounts that have been migrated to the ÃÛ¶¹ÊÓƵ Admin Console. This feature is retired.

User expiration and asset transfer

The ÃÛ¶¹ÊÓƵ Admin Console does not support user expiration or asset transfer. Admins will use the Analytics Users and Assets section under Admin Tools in Analytics for both functions.

Last Access (Last Login)

Details around a users' last-login date and time will be available in the Analytics Users and Assets link and not the ÃÛ¶¹ÊÓƵ Admin Console. The last-login date in Analytics is specific to when users actually accessed Analytics from within Experience Cloud and does not reflect the date/time when they logged into the Experience Cloud.

User Management APIs

Admins migrating to the ÃÛ¶¹ÊÓƵ Admin Console should configure offered on ÃÛ¶¹ÊÓƵ Developer for programmatic access to user accounts in the ÃÛ¶¹ÊÓƵ Admin Console.

The Analytics Permission APIs will be turned off when you are enabled for the migration.

Web Service Credentials

Users' web-service credentials (and their shared secret) will not be available in the ÃÛ¶¹ÊÓƵ Admin Console and can be accessed by clicking into the specific user from the Analytics Users and Assets section.

Single Sign-On

Analytics single sign-on configurations will be removed when you have completed the migration. They will remain active during the migration. Customers that use Analytics single sign-on should upgrade to .

Analytics recommends that you migrate your users as ÃÛ¶¹ÊÓƵ IDs first to easily create the Experience Cloud accounts, and then convert those accounts to Federated single-sign users.

Downloading permission groups

Downloading of Permission Group information will no longer be supported in either the Analytics Admin Tools or the ÃÛ¶¹ÊÓƵ Admin Console. Customers should use the adobe.io user management APIs to get permission group information in bulk.

Account Creation Date

Account Creation Date information is no longer supported in either the Analytics Admin Tools or the ÃÛ¶¹ÊÓƵ Admin Console.

Bulk Email

Bulk email to users will no longer be supported in either the Analytics Admin Tools or the ÃÛ¶¹ÊÓƵ Admin Console. Customers can bulk export their users' email addresses from ÃÛ¶¹ÊÓƵ Admin Console and send an email using any email client they wish.