Extension configuration
-
Ensure you are in Extensions within your mobile app property.
-
Select Catalog.
-
Use the
-
Search for
Identity
. -
Select the Identity extension.
-
Select Install.
This extension does not require any further configuration.
-
-
Use the
This extension does not require any further configuration.
-
Use the
-
Select Pending. In this tutorial, you manage consent further in the application. Learn more about the Consent extension in the documentation.
-
Select Save to Library.
-
-
Use the
-
In Datastreams select the Datastream that you created in the previous step for each of the environments, for example Luma Mobile App.
-
If not already populated, specify the Edge Network domain within Domain Configuration. The Edge Network domain is the name of your organization, followed by
data.adobedc.net
, for exampletechmarketingdemos.data.adobedc.net
. -
From the Save to Library menu, select Save to Library and Build.
-
Your library is built for the new extensions and configurations. A successful build is indicated by a ● in the Initial Build button.
Generate SDK install instructions
-
Select Environments from the left rail.
-
Select the Development install icon
-
In the Mobile Install Instructions dialog, select the iOS tab.
-
You can copy
The install instructions provide you a good starting point for implementation. You can find additional information here.
INFO
For the remainder of this tutorial, you will not use the CocoaPods instructions but instead use a native Swift Package Manager (SPM) based setup. -
Select the Swift tab below Add Initialization Code. This block of code shows how to import the required SDKs and register the extensions at launch. This is covered in more detail in Install SDKs.
-
Copy
Mobile tags architecture
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 JavaScript 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. That flexibility allows you to modify settings (like Adobe Analytics report suite id) or even change your app’s behavior (using data elements and rules, as you will see in later lessons) without having to change code in your app and resubmit the app store.
Next: Install SDKs