Learn how to configure a tag property in the Data Collection interface.
Tags in Adobe Experience Platform are the next generation of tag management capabilities from Adobe. Tags give customers a simple way to deploy and manage all of the analytics, marketing, and advertising tags necessary to power relevant customer experiences. Learn more about tags in the product documentation.
In order to complete the lesson, you must have permission to create a tag property. It’s also helpful to have a baseline understanding of tags.
Platform Launch (Client Side) is now tags
In this lesson, you will:
Create a new mobile tag property:
In the Data Collection interface, select Tags in the left navigation
Select New Property
.
For the Name, enter Mobile SDK Course
.
For the Platform, select Mobile.
Select Save.
Default consent settings for the edge-based mobile sdk implementations such as the one you are doing in this tutorial come from the Consent extension and not the Privacy setting in the tag property configuration. You will add and configure the Consent extension later in this lesson. For more info, see the documentation.
Open the new property
Create a library:
Go to Publishing Flow in the left navigation.
Select Add Library.
For the Name, enter Initial Build
.
For the Environment, select Development.
Select Add All Changed Resources.
Select Save and Build to Development.
Finally, set it as your Working Library.
Select Extensions.
The Mobile Core and Profile extensions should be pre-installed.
Select Catalog.
Use the Search feature to find an install the following extensions. Neither of these extensions require any configuration:
Install the Consent extension.
For the purposes of this tutorial select Pending. Learn more about the Consent extension in the documentation.
Install the Adobe Experience Platform Edge Network extension.
In the Edge Configuration dropdown, select the datastream you created in the previous step.
Select Save to Library and Build.
Select Environments.
Select the Development install icon.
Select iOS.
Select Swift.
The install instructions provide you a good starting point for implementation.
You can find additional information here.
The install instructions should be considered a starting point and not definitive documentation. The latest SDK versions and code samples can be found in the official documentation.
If you are familiar with the web version of tags, formerly Launch, it’s important to understand the differences on mobile.
On the web, a tag property is rendered into JavaScript which is then (usually) hosted in the cloud. That JS file is referenced directly in the website.
In a mobile tag property, rules and configurations are rendered into JSON files which are hosted in the cloud. The JSON files are downloaded and read by the Mobile Core extension in the mobile app. Extensions are separate SDKs that work together. If you add an extension to your tag property, you must also update the app. If you change an extension setting or create a rule, those changes are reflected in the app once you publish the updated tag library.
Next: Install SDKs
Thank you for investing your time in learning about Adobe Experience Platform Mobile SDK. If you have questions, want to share general feedback, or have suggestions on future content, please share them on this Experience League Community discussion post