Most Recent Adobe AD0-E213 Exam Questions & Answers

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

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

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:

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

Next ''Add the Embed Code'' >

Within Adobe Analytics, it typically takes around 5 minutes for data to be processed and ready for reporting. This is due to the fact that data must be collected, processed, and stored before it can be made available for reporting. This process can take a few minutes depending on the amount of data being processed. However, Adobe has various optimizations in place to reduce the time it takes for data to be processed and ready for reporting.

The manager should use the Data Sources API to upload order conversions into Adwords. The Data Sources API allows users to upload and manage data from various sources, including Adwords, and to use that data to create metrics and segments in Adobe Analytics. Details can be found in the Adobe Analytics Developer Professional study guide.

This is according to the Adobe Analytics Developer Professional study guide, Section 10.2.4 (https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/adobe-analytics-developer-professional-study-guide.pdf). To make a segment available in other reports, you must edit the segment and check the box to make the segment public. Once the segment is made public, it will be available in other reports in the segment list.

After the tracking call runs, the s.useBeacon variable resets to false and must be set to true in order for the beacon to be sent on the next tracking call. This is described in the Adobe Analytics documentation (https://docs.adobetag.com/analytics/implementation/vars/usebeacon/).