Introduction Of Adobe Experience Platform Tag

Adobe has a modern tool to manage tracking codes for analytics, ads, and marketing scripts on a website. Instead of writing code, you can manage everything in Tags. Tags are the next generation of tag management. Previously, tags in Adobe Experience Platform were called Adobe Experience Platform Launch. Tags connect to third-party tools through Adobe Analytics extensions. It has apps in that you can choose an extension -> install it -> set it up -> start to use. Tags are an API application that you can perform programmatically through an API, which we are performing through UI.

Benefits

• You can quickly get your values.

• Consistent data management, Centralized Collection, Send clean data.

• Use conditions to turn data into personalized user or customer experiences.

The Tags workflow

Set up groups and users

Users work in tags through their Adobe ID. User permissions are maintained in Admin Console. Tags have a rights-based user management system. The admin creates the group and adds the user to the group, then the user can get access. Using an Adobe ID, the user can manage other Adobe Products.

Log in

After user got the access to tags, they can log in to the Experience Platform UI or Data Collection UI. This login process takes you directly to the Experience Cloud login screen, and selecting either Data Collection or Experience Platform.

If you have multiple organizations with an account. You can change the organizations by selecting the organization's name at the top of the screen and choosing the organization from the drop-down.

Property

Once you log in to the UI.  Then you need to create a property. It is a container which fill with extensions, rules, data elements and libraries. The property is used to track and manage your website behavior. A property can contain multiple related websites.

Install Extension

An Extension are add-ons help Tags do more things. Is a tool created by Adobe/Adobe partner or other companies that works with Adobe Tags. It has default or pre-built extension it called “Core Extension”. The core extension collects When and Where data. If you want mobile apps extension the Adobe automatically adds the built-in extension. The most advanced feature come through you installed extensions.

Create data elements and rules

Data elements (Variables) are pointing to the information that you want to collect and share the data to difference of places such as analytics tools, Ads platforms, database and APIs.

Rules (Logic) It gives instruction to the tags what to and when. It has structure to work, Event (When) – It would be a page load Click on a “Purchase” and Video Reached 50%. Conditions (If) – It is a filter conditions. Only fire this rule if the Data for equals the conditions. Actions (What) – Extension can where you said to perform.

It can control the tag’s behavior:

• What happens?

• When it happens?

• Where it happens?

• How it happens?

Test into the Dev Environment

Libraries and Buildings

The changes aren’t directly published to the live site. Every change is inherited and saved in the library. The library stores already approved changes and previously published settings. The builds are actually a set of JS code version it created from the library. The build will publish the change to the live site.

Host

Host decides where to store and deliver the tag files with a connection between the property and the host location. The tags support two hosting methods – Akamai is a Content Delivery Network (CDN), Self- Hosting (SFTP) – Files are stored on our server.

Environment

Environment is a configured profile that determines exactly how the code is packaged and where it’s delivered. The library is created inside the environment. The changes belong to libraries. Host inside the environment to decide where the build has to be sent to Akamai or Self- Hosting. Once you have set up the environment, Adobe gives you a script like embed code. That needs to be pasted onto the website to load tags.

Publish a build to the Dev Environment

• Create the Host.

• Using the host to create the dev environment.

• To test the dev test site, deploy the embed code from your dev environment.

• Assign the library to the dev environment that you created.

• Build your library.

Production Environment

Once you've done all the changes must go to a different environment for testing and proper permissions. First, need to test the change in the Dev Environment. Create the stage environment for testing and then the production environment to move to live. This process goes through different steps and people. Developer -> Approver -> Publisher.

Conclusion

Adobe Experience Platform Tags provides a meaningful and flexible system to manage website tracking and marketing integrations. By using tags, users can collect data and connect with various tools through extensions. Control the action using rules, doing all of these without coding. Have structured components like Properties, Data elements, Rules, Library, Host and Environment. The tags organized everything properly. The platform-controlled publishing workflow ensures all the changes are in a different environment then deployed to the live site. It’s allowed to API first approach it will be suitable for both tech and non-tech users.