Publish Experience Platform tags libraries to stage and production

Hey, what’s up everybody? This is Doug. In this video, I want to walk you through how to publish your property in Adobe Experience Platform tags from development through staging and over to production. So I’m here in tags and I’m in the publishing flow and we’re gonna come back to this in a minute. I just wanted to start here and kind of show the plan that we’re gonna, you know, we’ve got this build 10. I’m gonna have you pretend for a minute that this is like maybe build one and that we don’t really have anything over here to the right and I’ll show you how to move it over there. But as you’re moving it over there, there are a couple other things you’re gonna want to do. One of those things is to get our report suites set up correctly and maybe even just set up at all, right? So I’m gonna go over to this other tab over here and we are in Adobe Analytics in the admin console and report suites and I’ve got this web retail dev one here. And I’m gonna have you kind of like see, but not see that I have this stage and prod one right here as well. Cause normally I would have just had you create this development report suite. And then when we’re done with the initial setup, go in here and create these other two, right? So if we are done with the first, maybe V1 implementation, then we would go in here, add a report suite and instead of creating from a template, we click on this and say duplicate an existing report suite. Then we would scroll down and find the one, the development one we’ve used. That one is right down here, tech marketing demos, web retail dev one, right? So there’s the one right there. Now this would mean that we don’t have these other two right here yet. But now when you duplicate this one, you can just give it a new report suite ID that says, you know, stage on it. You would create the stage one here first, right? So same kind of things that you did before, TMD web retail stage one or whatever, right? I’ve done that once, I’ve gone once through here for the staging report suite. And then I did it once for the production report suite. Now everything is going to be, you know, pretty much the same, you know, a little bit different naming, a little bit different ID of course, to put stage or prod instead of dev. And then also a different title, you know, with stage production. I’m sure time zone is the same and all these kinds of different things, except for the estimated page views per day. So those will be obviously pretty small on dev and stage, but when you create your production report suite, then you’ll want to give a more realistic number here. So instead of, you know, a hundred or 1000 or something like that for testing on dev and stage, then you’ll put your, you know, real estimated page views for your production site per day, so that the hardware can be set aside for your report suite. And that’s pretty much it there. And so I’m going to cancel out of that, because once again, I already did that here. So you would end up like this. You’d end up with the dev and a stage and a production report suite. Now, once those are created, we go back into tags and we’re going to go into our extensions, into analytics and in the configuration here, where we didn’t have those two report suites for stage and production, we had, you know, just put in the dev report suite for all three. So at this point you would actually go in and now since you’ve created this, you can go in and say, you know, where’s my web retail stage one, there’s now for staging and then so for production, I go in and find the same one, but for production, select that and now we’re good to go. And now when you are doing the testing stuff in development, it’ll go into dev. When you’re doing the staging, we’re going to stage and then prod, we’ll get your production numbers and everything will be mapped up there. So we would save that to our library or working library. I’m just going to go save to library. Now, how do I actually map my site though, to those report suites? And that’s done in the environments. And so you might remember that we went in and grabbed the code for the development site right here, right on development. And we went over here and grabbed the embed codes right here for development. And you can see over here down at the end, I think it says development or something like that. Yeah, right there development. So you copied that and embedded that in all of your pages on your development server. Well, you’re going to do the same thing now for staging and production. So you’re going to take this embed code and you’re going to embed that probably dynamically on your site into all of the pages on your staging server. And you can also see down here at the end, this is staging. So you can very easily identify that embed code when you’re comparing them. And then with production, then of course, once you’re going to go to production, you would grab the production embed code. You’ll see at the end, it doesn’t say staging or development. And that’s how you know it’s actually the production code. So you just grab those. And then once again, dynamically have those embed codes embedded in the head section of all the pages of your site. So once you’ve done that, we can go back to the publishing flow and again, maybe pretend that this is, you know, build one. And once you’re happy with that initial development, then we can go, okay, we’re going to click on these dots right here, and we’re going to do maybe our last build because we needed to add to that library anything that we’ve changed. So I’m going to click on build to development. When that completes, you can mouse over that and you can see that it was successful. So now once it has been built, when you click on that again, you can decide which is the next step. Now, some of this is going to be based on how many people you have working on this, right? If it’s just you and you know, it’s going to be good. You know, you’ve done all the testing. You’re like, I don’t really need to test it on staging or you don’t, maybe you don’t have a staging environment. Maybe you just go, you know, from development straight to production. Then you have that option as well. Or maybe you have groups that need to actually approve what you’ve done, right? So there’s some different things that you can do here. We just did the build. You can submit this for approval. Once you do that, it’ll jump over here. And then anybody who has been tasked with approving that can go in, look at all the rules, look at all the data elements, take a look at everything. And then they can submit that and build it to staging. Or if there’s nobody that needs to do that first approval, you can do that directly, submit and build a staging. You can also approve it for publishing and you can even approve and publish to production. So it depends on how far you want to move it along from here. Let’s say that I want to move it along through each stage and just, you know, knowing that you can actually skip some stages here if you want to, but I’m going to submit that for approval and I’m going to go submit for approval. There it shows up in submitted again. And now those people can submit that or they can approve that, excuse me. And then when they have looked at that and approved that, they can build it to staging.

And now we can see that that has been successfully built for staging. And now if you test staging, that’ll include everything that you included there in that library. Now we can move it along. We can approve it for publishing, approve.

And now once it’s approved, it’s ready to publish. Now, the reason why it didn’t go all the way over to publish is because it might not be time yet for you to publish. You don’t have to publish it right away if you’re waiting for a certain date, but you know, once it’s approved and it’s sitting there ready to publish, then you can go ahead and click on that and you can build it and publish it to production, go.

And now you can see that that has a successful build as well. Now, the next time you need to make some changes to your site, you will create another library, right? You can go library, add library over here. I’ll click on that. You’ll come in here and you know, and you can do, you know, build 11 or whatever you want to do. And then build that to development, et cetera. And you can start over again and make additional changes. So this will be an ongoing process as you add different pieces of your implementation to your site. But I just kind of wanted to walk you through that publishing flow and you know, include those new reports suites. Hope that was helpful. Have a great day.