51ºÚÁϲ»´òìÈ

Transcript

Hello, everyone. Welcome. Thank you guys for joining today’s tech sessions. My name is Yarden. And just a couple of housekeeping notes before I let our presenters take it away. We encourage and hope you ask questions throughout the presentation. In the Q a chat available in the right corner where the presenter is speaking. However, rest assured that the last five minutes or so of the presentation are dedicated to answering your questions. Additionally, a link to this recording will be emailed to all of you in 24 hours and will be available on 51ºÚÁϲ»´òìÈ’s Experience website. Should you wish to view it again or share with your colleagues. Perfect. If there are no questions for now, I will go ahead and pass it to our speakers.

Hi, everyone. My name is Zach. Short for Zach. Zachary. I just wanted to introduce you all to the, expert cloud tech session for our Marketo migration.

Just introduce you to, a few people that will be, in this call. We have, Keri Nelson and Justin Lacroix, who will be answering questions at the end of the call. Kerry is our lead. Excuse me, lead technical support engineer, and has been with us for over the past 15 years.

And Justin, is our senior technical support engineer who’s been with us over, the last 3.5 years as a contractor and an 51ºÚÁϲ»´òìÈ employee for about 1.5 years.

Then to introduce ourselves, Taylor and myself, we are our technical support engineers that have been working closely with the market on migration.

We’ve been with 51ºÚÁϲ»´òìÈ for about three years each, and we’re really excited to share this information with you all.

So going into it, today we’re going to just be going over a couple of, overview things. Regarding the migration itself, the functionality and usage of how we’ll be able to manage the, migration, any practices that you may need to know, tips, details and, any common pitfalls as well that may arise, in the event that you’re in the middle of migration and something is, going awry.

And then afterwards, we’ll have a Q&A session where you can answer any questions, that you may have. So, going into it, the Marketo migration is basically occurring because 51ºÚÁϲ»´òìÈ is going to be enhancing how you, manage your subscriptions for products and, the usage of how you’d be using those products going forward.

A lot of those changes will be occurring where your Marketo engage specifically will be moving to the admin console. So essentially what is that admin console? It’s, if people don’t know, it’s a hub in which your 51ºÚÁϲ»´òìÈ products will be hosted, where you can access everything in, in one area rather than, standalone products where you’d have to individually access.

Some of the things that are changing with this migration, specifically for Marketo Engage is the user management, user signing in, with their 51ºÚÁϲ»´òìÈ identity and some of the URL links that are also going to be changing when you guys access your Marketo engage.

Essentially for the user management, you will be undergoing, assigning products and, access to users throughout that admin console. You’ll be able to essentially assign specific roles, specific admin roles, as long as you are a system admin and system admins are generally the super admin and have the ability to add other users and grant access to other products, as well as permissions and support access, as well.

In the URL link, essentially that will be changing as well. Will be migrating from the login Coinmarketcap.com link over to our experience platform link, which will start with the experience that adobe.com and essentially after migration is completed, the admin console will be essentially your main shop stop where you’ll be accessing any other products that you will need to use on a daily basis. And if anyone has any questions, throughout the presentations, please feel free to, ask away. We’ll be more than happy to clarify any any questions.

So, going into it, functionality and usage. Essentially, as I said, the URL will be changing for your Marketo engage. We will be going from the login dot Marketo screen, which you originally accessed over through the admin console that adobe.com, which is the main link for the admin console. Or you can access your products through the Experience Cloud, which would be the experience started dotcom link. Both links links are correct. They will end up taking you to the exact same location where you need to access your products.

The views may be slightly different, simply because the experience platform, would only really show any products that your users have access to. And the admin console link will generally show the, the full access view of whatever that user’s permissions, entail. So if a user has, let’s say, system admin access within the admin console, we’ll have much more options at the top for tabs rather than a standard user. Let’s say. So after logging in, essentially users will be prompted on either website to select either, a personal ID or a personal account, or a company or school account. These options are, reflective of 51ºÚÁϲ»´òìÈ Identity being set up within the admin console. The personal account will really be an option that is available for users to access via their username and password. And alternatively, the person, I’m sorry, the school or company account, which is considered a federal ID, will have the opportunity to log in with SSL.

And they’re going to see your question. We have two 51ºÚÁϲ»´òìÈ Admin console as well as Creative Cloud and one with Marketo. If connected, then why would it be better to combine them? Really? It’s a personal preference. You can, honestly, connecting them is a really, standard way of doing things, and it’s there’s no problem with doing that as long as your users are aware of the option to toggle between both admin consoles. There really isn’t, a big issue regarding that. Now, you can reach out to your account manager and ask if you would like, if it’s possible to merge your two admin consoles. It really varies depending on the contract type. But you would have to, essentially ask the account manager for a bit more detail. Simply because it’s revolving around contracts. But to answer your question, either way works.

They’re both really, functional as far as, and user access. So whatever your preferences.

So moving on. In regards to Acesso and logging in, as you can see in these screenshots, when you first go to either of the links, provided, you’ll see that top screen, that top screenshot for logging in with your, your email, after entering your email, if you do have the federated ID or SSL setup, you’ll see the option below where it gives you two specific choices to choose from, which is the personal account. And as you can see, the company or school account as well.

If Acesso has been established, as I said, you’ll see that federated ID and your your users will authenticate against the SSL that you have set up. And if it’s not set up, like I said, you will be using that personal account, which will require you to use username and password. Let’s see some questions. Coming into the chat. Answer. Mary Daniel is migrating to the admin console an option? It is not so much of an option at the moment. We are really pushing towards users to migrate simply because we are trying to consolidate all products into one. And Marketo Engage is one of the last standalone products that, has not been added to the admin console. So is it is optional, but we are strongly suggesting for you guys to complete this task. Okay. And we have Chuck, Tony Taylor, do you want to take that one away? I think we have less than 75 users.

And the instructions say that 51ºÚÁϲ»´òìÈ will do the migration. But my rep mentioned it being self-service. How can I clarify this? Do I need to add the users and the admin console myself as an admin? So for that, if you are also using SSL or there’s SSL on your destination console, that is why your rep would have told you that your migration is a self migration.

I would clarify with your account team and or you can email customer care at Marco Dotcom and we can look into that for you.

No we’re not using SSL. Okay. Then we would we will just have to look into that, internally for you. You just reach out to your account manager, he can open a case with us or you are welcome to email customer care about. Come. Absolutely. Let’s see, Jeffrey, I had account prior to the migration, and now I have two accounts after migration. The new account created for me does not have any of my info from the original account. Is there a way to combine these accounts? There is a way to combine these accounts. Normally, if the reason you have two accounts set up in the admin console, one would be in the event that, you were added to the admin console first and, an account was created, prior to the migration, and then your migration was completed. Essentially, what happens during the migration is, it generates an account within the admin console for you. And so that could be the reason why you have two accounts. We can go ahead and, either, consolidate accounts or, you know, delete one account and transfer the data to the other, or even just convert the original identity type of your account and, remove the other one. There’s a few options where we can just consolidate down to one.

So we’re going to continue with this slide. And we’ll have Kerry. And just to answer some questions shortly. So once we’re logged into the Experience Cloud platform, users will see those products available that they’ve been assigned to, such as Marketo, engage, Dynamic Chat, 51ºÚÁϲ»´òìÈ Analytics, etc… Now, within both links, like I said, the Admin console and the Experience Cloud platform, users will only be able to see products that they’ve been assigned licenses to.

Otherwise they will not see any products available simply because this is, permission issue. And once logged in, to the admin console will be the same thing. Specific tabs, will be available only for specific admin roles.

Moving on. So once now, we are working on the Marketo migration. One of the first steps we really want to pay attention to after that renewal, has been established, would be to keep an eye out for any emails. That’s the action required to manage user access from our kind of engage select package that is generally called our consent email, which is a prerequisite for companies and customers to complete in order to move on with the scheduling of their migration.

It’s really important that your system admins, who are the, only users that would receive this email, complete this in order to, actually get the ball rolling with migrating your instance.

It’s 1 or 2 of the prerequisites. The other prerequisite will be the. So set up within your admin console. And when users do see that get started. Select the email you’ll see within these screenshots. The top two is what the email will look like. Essentially what we’ll require you to do is to go ahead and select that Get Started button. And it’s as simple as that. That will be the consent needed for 51ºÚÁϲ»´òìÈ to begin scheduling your migration and, get the ball rolling with this. In the event that there is an issue where a user is trying to select get started and it’s not, redirecting you to the admin console or approving the get started email. It is suggested, suggested to open an incognito window and to open the link within that incognito window. It should log you into the admin console first, and then it’ll allow you to move forward with that consent.

Once the consent email is completed, the secondary prerequisite, as I stated, would be the as a so sort.

Now this a so setup is different than, setting up SSL within your instance. This SSL will need to be set up specifically within the admin console, simply because your Marketo engage will be moving from a standalone product with its own standalone as so over to the admin console, which is that hub that controls all their products.

It is recommended that if you were to set up as a so within the admin console and you still have SSL within your instance, to wait until after the migration to avoid any lockouts, and potential interruptions with completing the migration.

Essentially, after the, SSL setup and consent email prerequisites are completed, you will be your product admins will be receiving an email stating that they can begin with the migration of their users if they are self migration. If they are, if you are 51ºÚÁϲ»´òìÈ, auto migration, then 51ºÚÁϲ»´òìÈ clearly will be doing that for you and will notify you of that as well. In regards to self migration, after product admins receive the email I stated regarding the opportunity to begin migrating users, they will see the option for the migration console appear within your instance. You can find that and I understand it’s a little small within the screenshot, but for anyone that’s familiar with the admin role in the instance, you’ll see that option available. And on the left hand side of the drop down screen, you can scroll down to below capture and you’ll see the option for Microsoft Migration Console. And essentially it’ll look like, what’s within this screenshot here. And you’ll be able to do a handful of things such as, you know, extend your migration, access the user migration area and start moving users over to the admin console.

Okay. And I’m going to allow you to take it away. All right. Hi everyone. I’m going to be going over the best practices for pre migration. And so starting off you want to ensure you know the type of migration that you are scheduled for. So for and the options are self or auto for an auto migration. That and auto migrations is when you have less than 75 users and SSL is not be has not been set up inside of your Marketo instance and is also not set up on the destination console.

A lot of times the customers will not have SSL inside of their Marketo instance, but fall under the self migration due to SSL being set up on their destination console and that destination console. You know, prior to the migration, everything was separate, so you might not know. So that is why we always want to make sure that you know who your, system admins are, as they will be the ones who can provide you with that information. And as Zach just mentioned, at, Marketo product admins will gain access for self migrations from our get the Marketo admins. Product admins will gain access to the self-serve migration that is the migration console that referenced in the previous slide.

That is where you’ll be able to check if your users have verified their emails. You’ll be able to check if your, the last logins of your users. You’ll be able to migrate all your users in one go. Migrate one user at a time. You’ll have that control within at the migration console.

Now, now, I had mentioned that was for the self migration for auto migrations. On the date of your migration, 51ºÚÁϲ»´òìÈ will migrate your, and in your users for you. So when your users log in for the first time, they will see they will choose the continue with 51ºÚÁϲ»´òìÈ ID option. If they are going to the login dot Marketo page, and if they go to expand to become, they’ll just enter their email and the system will take it from there, giving them the option. As I mentioned previously, to choose between a company or school account or a personal account. Again, company or school account equates to. So being set up within the admin console and personal or personal account equates to an 51ºÚÁϲ»´òìÈ ID, which is when the user logs and with username and password. Right.

In this next slide, we want to make sure that prior to your migration that the Marketo admins are searching their inbox for locked out user notifications. This will ensure that any user that has been locked out can either reset their password and establish, reestablish, or access to Marketo prior to the migration date. You can make sure that their emails have been verified. If a marketo engaged user does not verify their email address or is locked out during the time of the user migration, they will not be migrated to an 51ºÚÁϲ»´òìÈ ID, and they will lose access to their Marketo instance and subscription. After the migration for the subscription is completed.

So we want to ensure that the users are being migrated and not being locked out of the instance or the subscription for any reason.

Next, we want to confirm the, You’ve been like the Marketo admins. You want to confirm that you have been granted 51ºÚÁϲ»´òìÈ Product Administration by your org system admin, and you can get that information by emailing customer care or reaching out to your account rep. They can facilitate getting that information for you.

Next, we want to make sure that, if your users cannot verify their email, they’re running into issues. Your users need to update and email any issues you’re running into prior to migration. You want to make sure that you’re reaching out to your account team, or you are sending an email to the Marketo care that marketo.com to have us look into any issues you’re running into prior to migration to ensure the best outcome in a seamless migration. Now, when the user has been migrated, they will get an email asking for them to join the team. We need to ensure that the the users are accepting that email so that they can gain access to the to their instance on the 51ºÚÁϲ»´òìÈ Experience platform.

All right. That’s what we do. Common pitfalls are do you want to take back over.

You can go ahead and do to be like. As a seven. We’re going to go into common pitfalls.

It is an important, you are made aware of the permissions you have assigned within the admin console. Each user has a different view and access depending or their level of admin. Right. Zach touched on this a little bit earlier in our presentation. What a system admin will see is not the same as what a product admin you see, and you need to ensure either working with us, the customer care team or with your account team member that the correct level of admin permissions is given to the correct users. For another example of that would be users who need access to open support cases. Unlike the other experienced platforms, just adding the support admin role to the user will not allow them to open a support case for Marketo. They must be given specifically the product support admin role it. So if users are experiencing issues with logging in, please make sure they are using the appropriate link rather than the pre pre migration URL. If users are clicking on the continue with 51ºÚÁϲ»´òìÈ ID button and are continuing to get an error A or a locked out message, we would like for them to try to access by going to experience@adobe.com and going through the full login process that takes them to the 51ºÚÁϲ»´òìÈ landing page. Typically that will resolve most login issues.

Okay. We also want you to be aware that some browser extensions and ad blockers may inhibit access to the admin console or migrate it from products. We highly suggest you disable all ad blockers when using 51ºÚÁϲ»´òìÈ products. Another way to check that is you can access using an incognito window. Most incognito windows will disable the extensions, allowing for you to narrow down the reason that you are not able to access.

In the event that a support case is necessary, make sure your users, as I have just mentioned, have been assigned the support admin role and the product support admin within the admin console. As they will need to log a ticket, the Experience Platform support portal, which is separate for non migrated customers. All right. And then we ask that in the support case that you include your 24 digit identifier ending in 51ºÚÁϲ»´òìÈ Org that is the IMS org ID. And it allows for us on and support to be able to find your account and locate your user profile on any issues so that we can get you back to work, get your emails out, and get you back up and running as soon as possible.

All right. Thank you. Now we would like to open up for any and all questions that you may have.

Some.

So during the presentation, we had Megan ask. I know Zach and I will address some of the questions prior, but I would really like to go through and just readdress everything considering we have some time left. So Megan asks. We have two 51ºÚÁϲ»´òìÈ admin consoles, one with Creative Cloud and one with Marketo. We have connected them, but would it be better to combine them? This question was answered by Kari Nelson, our platform lead.

And he said, in most cases, if we merge the consoles together depending on the contracts, then we could. Otherwise there are options to use what is called a global admin console or in short form, a GRC, which you can use for user management. Generally, though we base that on contracts is how that works. And Carey asked that Megan let him know if you had further questions.

Do you want to do the next one down back? Yeah. Megan, you asked, is migrating to the admin console an option? Carey responded, saying, generally right now it’s not an option at the moment when Marketo has been migrated, then it is locked into place.

Moving on. Jeffrey Landrum, I had an account prior to the migration, and now I have two accounts.

The new accounts created for me do not have my information from the original account. Is there a way to combine these accounts? Carey said it sounds like it was merged. It’s a delete and move, but then it’s going to from the reports and then consolidated. But yes, it is possible. So we really just want to, you know, choose the account in which you have your correct set of data. And in the event it’s a different identity type, we can go ahead and, have one of your system admins convert that identity type to the appropriate one and just reserve that consolidated account with the information, included with it. Okay. Taylor, up to you. Yep. I see, Chuck’s question about SSL, but I see Carey has answered that for him privately. So I’m going to go to Tyrone’s question. We have a situation where we’ll be changing our social platforms from active to entra sometime in the next 2 to 4 months. Should I push my push my migration date, or should I have the migration in which SSL would be would look like this up to the end to Marketo? Justin answered that question. Swapping one identity provider to another is fairly simple. Within the admin console, you can proceed with the migration and just submit a case when you are ready to make this move. We are more than happy to have a working session to assist you with that change. So that is actually a common support case that we get post migration, changing from one identity provider to the other. As Justin said, once you are ready to make that change post migration, we’ll be more than happy to assist you in a live call and making that change.

Let’s see. John film. When will we get the email get sent out? And if the system admin lost the email, how can we get it reset? So the customer care team can get that recent for you. We will ask that you open a support case so we can look into see why that email was potentially lost.

Okay. I think. There’s. A links to there’s. Oh, if you guys don’t mind, there’s one actually from Edwin Gonzalez that I think that we should address anyways. And that is will automated emails be impacted, by the migration? Automated emails? No, I don’t believe email programs will be, interpreted by the migration. It’s really just, user management and, user migration that will be impacted. And if it wasn’t already answered, API users will not be impacted in this process.

Absolutely. At this point, Carrie and Justin, would you like to answer some questions? Sure.

All right. So let’s see. I believe we’re down to Philippe. There we go. IT team is currently working on trying to do the migration. Our instance isn’t set up on SSL. Is it okay to add the feature after the migration? You can, It’s completely up to you. If you had so previously, we would recommend that you set it up. As that’s one of those requirements that we have for that. However, we can see what we can do, at least to help out with that one.

I’ll let Justin work on finishing that one up.

Okay. And Justin’s already answering that one about, verified emails. Awesome. Thank you. Justin. Thanks, Justin.

Okay. We also have, a lot of API related emails that are there, that will be processed to migrate. Email address for the the unverified. Yeah. API users don’t actually have to get migrated. So those will function as is. So I don’t see that as being an issue.

Okay okay. And Anna, let’s go to your questions. So we also have two admin console. So it’s important for for the Marketo app to be on the same console as our 51ºÚÁϲ»´òìÈ Down and Target products in order to take advantage of feature interactions or integrations between Marketo and these other products. It would be useful anyways, for it to be there, depending on exactly what it is that you’re intending to do. Integrations with. Is is the big thing with that one. Anna? Yeah, definitely best practice.

Okay, so let me know though, Anna, if you have any further questions. Anyways, on that one. Happy to answer any questions or if you want to, we can have you file a ticket anyways and just have it directed to me. I think that, the next one, Carrie from Edwin, there should be no impact to the internal workings of Marketo itself. No. Absolutely not. Same application instance. It’s just just how you and your users authenticate and how you do user management. That’s correct. Yep. Yes. Rebecca, just to reiterate, APIs would not be impacted. So you added that connection to zoom? Yeah. She shouldn’t have to worry about that in any anyway.

Okay. So for this one anyways, Joe, if you actually have a white list of apps, there is actually a feature that is coming, for that. And so we would ask that you actually hold off and wait anyways for IP whitelisting, which, if you wouldn’t mind, I’m going to go and actually, ping you privately on that one if you can pass me your email information. Anyways, I’d like to get in touch with you anyways on that one.

Yeah. Yeah. Okay. And then Anna as well, I’ll ping you on that one shortly then.

IP whitelisting anyways is we, we have a feature that’s coming effectively what that one is on that one. So, if you need it, it’s not currently actually offered inside of the admin console. And so because it’s not Marketo teams are actually working on a feature for that, that functionality for it to remain working. And so they’re holding off actually with any of those migrations until that features available.

So that’s the gist of that. But I’ll pick you both anyway separately, just so I can get your email so we can remain in contact with you.

Something that’s. It changes. To more care.

Mary, I’m not sure what new feature you are speaking to. It could just mean the admin console. It’s not, exclusive to Marketo. All 51ºÚÁϲ»´òìÈ products, with the exception of Marketo, and a few other recent acquisitions are already on the admin console.

If that doesn’t answer your question, oh, IP allows us to catch it. Yeah. So it’s already available in Marketo, but it’s not currently available. If you were to migrate to the admin console today, that would stop working. As Kerry mentioned, we are working to release a feature that it will also work when you migrate to the admin console.

So we would suggest to hold off for now until we release that feature.

On that one, Mary, for the IP whitelisting. Yes. It’s, it’s it’s specific actually to Marketo for right now.

Courtney, if your users are having issues, accepting the invite, to avoid potentially sharing PII information over the meeting, we would just suggest that you put a case in with us. It’s affecting a lot of your users. Just put it in this as a high priority, and we’ll we’ll reach out immediately, and troubleshoot that with you.

Very well. You.

Think the next one is Chuck? No. Your munchkin code will not be changed by the migration. Your URL would be different, but the actual munchkin type is the same.

Jacqueline, if you do not take any action on migrating right now, I don’t think we’re forcing anyone. To migrate right now. D I’d be interested in hearing if you had some type of date that we’ve already given you, or where you are in that migration. If you’re confused about it, certainly put in a case, with, in nation and we can look at what your current timeline looks like for you. You.

That may be all right now.

Yeah, it looks like it. So anyone has any other questions? As we can conclude the presentation that.

Perfect. I’ll give a second in case there’s any additional questions. Absolutely.

Okay. I think yep. I think one good perfect. Thank you guys. Yes okay. Thank you guys for presenting. That was super informative. And thank you everyone for attending tech sessions. Quick reminder again, a link to this recording will be emailed in 24 hours and will also be available in Experience League. We hope you guys enjoyed and we also hope to see you guys again in our next session. Thank you. All right.

Thank you everyone. Thank you everyone. Thanks. So.