Create a tag property In this lesson, you will create your first tag property.

A property is basically a container that you fill with extensions, rules, data elements, and libraries as you deploy tags to your site.

Prerequisites In order to complete the next few lessons, you must have permission to Develop, Approve, Publish, Manage Extensions, and Manage Environments in tags. If you are unable to complete any of these steps because the user interface options are not available to you, reach out to your Experience Cloud Administrator to request access. For more information on tag user permissions, see the documentation .

NOTE

Adobe Experience Platform Launch is being integrated into Adobe Experience Platform as a suite of data collection technologies. Several terminology changes have rolled out in the interface which you should be aware of while using this content:

Platform Launch (Client Side) is now tags

Platform Launch Server Side is now event forwarding

Edge configurations are now datastreams

Learning Objectives At the end of this lesson, you will be able to:

Log into the Data Collection user interface

Create a new tag property

Configure a tag property

Go to the Data Collection interface To get to Data Collection

Log into the Adobe Experience Cloud

Click the Solution Switcher Icon icon to open the app switcher

Select Launch/Data Collection from the menu Open the solution switcher using the icon and click Launch/Data Collection

You should now see the Tags Properties screen (if no properties have ever been created in the account, this screen might be empty):

Properties Screen

Create a Property A property is basically a container that you fill with extensions, rules, data elements, and libraries as you deploy tags to your site. A property can be any grouping of one or more domains and subdomains. You can manage and track these assets similarly. For example, suppose that you have multiple websites based on one template, and you want to track the same assets on all of them. You can apply one property to multiple domains. For more information on creating properties, see “Companies and Properties” in the product documentation.

To Create a Property

Click the New Property button:

Click New Property

Name your property (e.g. Luma Tutorial or Luma Tutorial - Daniel )

As the domain, enter enablementadobe.com since this is the domain where the Luma demo site is hosted. Although the “Domain” field is required, the tag property will work on any domain where it’s implemented. The main purpose of this field is to pre-populate menu options in the Rule builder.

Expand the Advanced Options section and check the box to Run rule components in sequence

Click the Save button

Create a new Property

Your new property should display on the Properties page. Note that if you check the box next to the property name, options to Configure or Delete the property appear above the property list. Click on the name of your property (e.g. Luma Tutorial ) to open the Overview screen. Click the name of the property to open it

Next “Add the Embed Code” >

This is according to the Adobe Analytics Developer Professional study guide, Section 11.1.1 ( https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/adobe-analytics-developer-professional-study-guide.pdf). Properties provide a way to organize tags and can also provide a way to manage multiple tags for the same account. By using properties, you can control which tags are deployed to a website and how they are deployed. Additionally, properties can be used to maintain data element mappings, which allow you to map Analytics variable values to data elements.

The data object that can be used to count the number of times a specific page is seen by online users is page views. The page view metric is used to track and measure the number of times a page has been viewed by visitors. This metric is useful for understanding how often users visit a particular page and can be used to track engagement on a website or application.

In Adobe Analytics, a Page View is defined as an instance of a page being loaded in a browser. When a user loads a web page, Adobe Analytics counts it as a page view. Page Views are used to measure the popularity of a page on a website and the amount of traffic it receives.

A datalayer is an object that contains the data that needs to be communicated to digital analytics and reporting servers. It is typically a JavaScript object that contains key-value pairs that represent the different data points that need to be sent to the reporting server. For more information, please refer to the Adobe Analytics Developer Professional study guide.

When an event is fired without a conversion variable being set, the output for that event in a report in Adobe Analytics will show "Unspecified". This happens when data is sent to Adobe Analytics from the page but the conversion variable is not set or is set to an empty value. Reference: https://www.adobe.com/content/dam/acom/en/devnet/analytics/analytics-developer-professional-study-guide.pdf

This method is recommended by Adobe Analytics Developer Professional documents, as it allows you to easily customize the metrics used in a table in Workspace. You can use a calculated metric to modify the name of an existing metric, or to derive a new metric from an existing one [1].

References: [1] https://docs.adobe.com/content/help/en/analytics/components/calculated-metrics/calculated-metrics-overview.html

The first step to add a new extension is to select an extension from the extensions catalog. To do this, from a property's overview page, open the Extensions tab and select an extension from the list. You can then mouse over an extension to configure it.