Social Trading erklärt
5 stars based on
Google Tag Manager enables developers to change configuration values in their mobile applications using the Google Tag Manager interface without having to rebuild and resubmit application binaries to app marketplaces. This is useful for managing any configuration values or flags in your application that you may need to change in the future, including: Various UI settings and display strings Sizes, locations, mobiler handel binarny types mobiler handel binarny ads served in your application Game settings.
Configuration values may also be evaluated at runtime using rules, enabling dynamic configurations such as:. Google TagManager also enables the dynamic implementation of tracking tags and pixels in applications.
Developers can push important events into a data layer and decide later which tracking mobiler handel binarny or pixels should mobiler handel binarny fired. TagManager currently supports the following tags:. If you're new to Google Tag Manager, we recommend that you learn more about containers, macros, and rules Help Center before continuing this guide. This section will guide developers through a typical Tag Manager workflow: Next, add the following to your application target's linked libraries if they are not already present:.
If you would like your application to access the identifier for advertisers IDFA and tracking flag provided by that framework through the Google Tag Manager SDK macros, you'll also need to link these additional libraries:. Google Tag Manager uses a default container on the first run of your application. The default container will be used until the app is able to retrieve a fresh container over the network.
Once you've downloaded the binary file, be sure to remove the version suffix from the filename to ensure you follow the correct naming convention. Although using the binary file is recommended, if your container does not contain rules mobiler handel binarny tags, you may choose to use a simple property list or JSON file mobiler handel binarny.
The file should be located in the main bundle and should follow this naming convention: Before retrieving values from a mobiler handel binarny, your application needs to open the container. Opening a container will load it from disk if availableor will request it from the network if needed. Requests made with a non-existent key will return a default value appropriate to the type requested:. The DataLayer is a map that enables runtime information about your app, such as touch events or screen views, to become available to Tag Manager macros and tags in a container.
For example, by pushing information about screen views into the DataLayer map, you can set up tags in the Tag Manager web interface to fire conversion pixels and tracking calls in response to those screenviews without needing to hard code them into your app.
In the web interface, you can now create tags like Google Analytics tags to fire for each screen view by creating this rule: To pass the screen name to one of these tags, create a data layer macro that references the "screenName" key in the data layer. Macro values will always correspond to the current published version. Before publishing the latest version of a container, you can preview your draft container.
To preview a container, generate a preview URL in the Google Tag Manager web interface by selecting the version of the container you'd like to preview, and then selecting Preview. Hang on to this preview URL as you'll need it in later steps. Mobiler handel binarny enable container previews, you must add code to your app delegate implementation file and define the Google Tag Manager preview URL scheme in your project's property list.
When you're ready to make your draft configuration values available to your application, publish the container. Google Tag Manager for Mobile has a number of advanced configuration options that allow you to select values based on runtime conditions using rules, manually refresh the container, and get additional options for opening containers. The following sections outline several of the most common advanced configurations. The Google Tag Manager SDK provides several methods for opening containers that can give you more control over the loading process:.
Throughout the loading process, openContainerById: Unless it is acceptable for your application to use the default values, you will need to use these callbacks to know when a saved or network container has loaded. Note that you will be unable to load a saved or network container if this is the first time the app is run and there's no network connection.
If it returns mobiler handel binarny stale saved container, it will also make an asynchronous network request for a fresh one. When using kTAGOpenTypePreferNonDefaulta default container will be returned if no other container is available, or if the timeout period is exceeded. It is not recommended to use kTAGOpenTypePreferFresh in places where a longer request time may noticeably affect user experience, such as with UI flags or display strings.
You may also use TAGContainer:: Both of these convenience methods are non-blocking. Both methods have a default timeout mobiler handel binarny of 2. Containers can evaluate values at runtime using rules. Rules may be based on criteria like device language, platform, or any other macro value. For example, rules can be used to select a localized display string based on the mobiler handel binarny of the device at runtime.
This can be configured by using the following rule:. You can then create value collection macros for each language, and add this rule to each macro, inserting the appropriate language code.
When this container is published, your application mobiler handel binarny be able to display localized display strings, depending on the language of the user's device at runtime. Note that if your default container needs rules, you must use a binary container file as your default container.
Learn more about configuring rules Help Center. Default containers that need rules should use a binary container file instead of a property list file or JSON file as the mobiler handel binarny container. Binary containers offer support for determining macro values at runtime with Google Tag Manager rules, whereas property list or JSON files do not.
Binary container files may be downloaded from the Google Tag Manager web interface and should mobiler handel binarny added to your main application bundle following this naming convention: Function Call Macros are macros that are set to the return value of mobiler handel binarny specified function in your application. Function Call Macros can be used to incorporate runtime values with your Google Tag Manager rules, such as determine at runtime which price to display to a user based on the configured language and currency of a device.
Function Call Tags enable pre-registered functions to be executed whenever an event is pushed into the data layer and the tag rules evaluate to true. To set a custom container refresh period, mobiler handel binarny NSTimeras in the following example:. Enabling more verbose logging can be helpful for debugging mobiler handel binarny is possible by implementing your own Loggeras in this example:.
Mobiler handel binarny details, see our Site Policies. Last updated June 8, Guides Reference All Products. This developer guide describes how to implement Google Tag Mobiler handel binarny in a mobile application.
Introduction Google Tag Manager enables developers to change configuration values in their mobile applications using the Google Tag Manager interface without having to rebuild and resubmit application binaries to app marketplaces.
Various UI settings and display strings Sizes, locations, or types of ads served in your mobiler handel binarny Game settings Configuration values may also be evaluated at runtime using rules, enabling dynamic configurations such as: Using screen size to determine ad banner size Using language and location mobiler handel binarny configure UI elements Google TagManager also enables the dynamic implementation mobiler handel binarny tracking tags and pixels in applications.
TagManager currently supports the following tags: Getting Started Mobiler handel binarny section will guide developers through a typical Tag Manager workflow: Next, add the following to your application target's linked libraries if they are not already present: To download and add a default container binary to your application, follow these steps: Sign in to the Google Tag Manager web interface.
Select the Version of the container you'd like to download. Click the Download button to retrieve the container binary. Add the binary file to your project's root directory and to the "Supporting Files" folder in your project. Opening a Container Before retrieving values from a container, your application needs to open the container.
An empty string is returned. Pushing Values to the DataLayer The Mobiler handel binarny is a map that enables runtime information about your app, such as touch events or screen views, to become available to Tag Mobiler handel binarny macros and tags in a container.
Events mobiler handel binarny pushed to the DataLayer using push: First, add the following bolded code snippets to your app delegate file: This code must be called before the container is opened. Open the link on an emulator or physical device to preview the draft container in your app. Advanced Configuration Google Tag Manager for Mobiler handel binarny has a number of advanced configuration options that allow you to select values based on runtime conditions using rules, manually refresh the container, and get additional options for opening containers.
Each of these methods takes mobiler handel binarny enumeration mobiler handel binarny either a non-default or fresh container. Evaluating Macros at Runtime using Rules Containers can mobiler handel binarny values at runtime using rules. This can be configured by using the following rule: Adding a rule to enable a value collection macro only for devices configured to use the Spanish language. Binary Mobiler handel binarny Container Files Default containers that need mobiler handel binarny should use a binary container file instead of a property list file or JSON file as the default container.
Using Function Call Macros Function Call Macros are macros that are set to the return value of a specified function in your application. To configure a mobiler handel binarny call macro: Define the function call macro in the Google Tag Manager web interface. Arguments may optionally be configured as key-value pairs. To configure a function call tag: Define the function call tag in the Google Tag Manager web interface.
To set a custom container refresh period, use NSTimeras in the following example: Enabling more verbose logging can be helpful for debugging and is possible by implementing your own Loggeras in this example: Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 3.