Android get advertising id

Как получить рекламный идентификатор в Android программно

Я хочу получить рекламный идентификатор для пользователей программным способом. Я использовал приведенный ниже код с сайта разработчика. Но он не работает

Как получить идентификатор рекламы пользователя программным способом? Помогите мне, пожалуйста

ОТВЕТЫ

Ответ 1

Возможно, я опаздываю, но это может помочь кому-то другому!

Ответ 2

Получить идентификатор GAID (рекламный идентификатор Google)

1. Загрузите последнюю версию SDK Google Play. 2. Импортируйте код и добавьте его в качестве проекта библиотеки.
3. Изменить AndroidManifest.xml.

4. Включите ProGuard для сжатия и обфускации кода в project.properties..

5. Добавить правила в proguard-project.txt.

6. Вызовите AdvertisingIdClient.getAdvertisingIdInfo(getApplicationContext()). getId() в рабочем потоке, чтобы получить идентификатор в String. как будто это

Ответ 3

На всякий случай кто-то заинтересован в попытке извлечь часть AdvertisingId во время Rx-ing, тогда это может быть полезно.

Ответ 4

Получить идентификатор рекламы из фонового потока:

Я добавил null для предотвращения любых сбоев. Код в Google

Ответ 5

Убедитесь, что вы добавили сервисы идентификации воспроизведения, затем вы можете получить идентификатор рекламы, выполнив такой поток:

Ответ 6

С проверкой ОС.

Назовите это в AsyncTask

Ответ 7

Вам нужно запустить свой код с помощью Async Task

Ответ 8

Вам нужно добавить gms libs, иначе вы не сможете получить идентификатор рекламы. Он может быть reset пользователем или когда вы выполняете factory reset (в factory reset время, когда идентификатор Android также reset).

Ответ 9

Вы можете вызвать приведенную ниже функцию в onCreate (Bundle saveInstanceState) действия

и в logcat-поиске UIDMY будет отображаться идентификатор: I/UIDMY: a1cf5t4e-9eb2-4342-b9dc-10cx1ad1abe1

Источник

Get Started

Integrating the Google Mobile Ads SDK into an app is the first step toward displaying ads and earning revenue. Once you’ve integrated the SDK, you can choose an ad format (such as native or rewarded video) and follow the steps to implement it.

Before you begin

To prepare your app, complete the steps in the following sections.

App prerequisites

Use Android Studio 3.2 or higher

Make sure that your app’s build file uses the following values:

• A minSdkVersion of 16 or higher
• A compileSdkVersion of 28 or higher

Set up your app in your AdMob account

Register your app as an AdMob app by completing the following steps:

Register your app with AdMob. This step creates an AdMob app with a unique AdMob App ID that is needed later in this guide.

Configure your app

In your project-level build.gradle file, include Google’s Maven repository and Maven central repository in both your buildscript and allprojects sections:

Add the dependencies for the Google Mobile Ads SDK to your module’s app-level Gradle file, normally app/build.gradle :

Add your AdMob app ID (identified in the AdMob UI) to your app’s AndroidManifest.xml file. To do so, add a tag with android:name=»com.google.android.gms.ads.APPLICATION_ID» . You can find your app ID in the AdMob UI. For android:value , insert your own AdMob app ID, surrounded by quotation marks.

In a real app, use your actual AdMob app ID, not the one listed above. If you’re just looking to experiment with the SDK in a Hello World app, you can use the sample app ID shown above.

Note also that failure to add the tag as shown above results in a crash with the message:

(Optional) Declare AD_ID permission for previous versions to work with Android S.

If your app uses the Google Mobile Ads SDK version 20.4.0 or higher, you can skip this step since the SDK automatically declares the com.google.android.gms.permission.AD_ID permission and is able to access the Advertising ID whenever it’s available.

For apps that use the Google Mobile Ads SDK version 20.3.0 or lower and are targeting Android S, you must add the com.google.android.gms.permission.AD_ID permission in the AndroidManifest.xml file in order to target Android S:

To learn more about the com.google.android.gms.permission.AD_ID permission declaration, including how to disable it, please refer to this Play Console article.

Initialize the Google Mobile Ads SDK

Before loading ads, have your app initialize the Google Mobile Ads SDK by calling MobileAds.initialize() which initializes the SDK and calls back a completion listener once initialization is complete (or after a 30-second timeout). This needs to be done only once, ideally at app launch.

Ads may be preloaded by the Google Mobile Ads SDK or mediation partner SDKs upon calling MobileAds.initialize() . If you need to obtain consent from users in the European Economic Area (EEA), set any request-specific flags (such as tagForChildDirectedTreatment or tag_for_under_age_of_consent ), or otherwise take action before loading ads, ensure you do so before initializing the Google Mobile Ads SDK.

Here’s an example of how to call the initialize() method in an Activity:

Example MainActivity (excerpt)

Kotlin

If you’re using mediation, wait until the completion handler is called before loading ads, as this will ensure that all mediation adapters are initialized.

Select an ad format

The Google Mobile Ads SDK is now imported and you’re ready to implement an ad. AdMob offers a number of different ad formats, so you can choose the one that best fits your app’s user experience.

Banner

Rectangular ads that appear at the top or bottom of the device screen. Banner ads stay on screen while users are interacting with the app, and can refresh automatically after a certain period of time. If you’re new to mobile advertising, they’re a great place to start.

Interstitial

Full-screen ads that cover the interface of an app until closed by the user. They’re best used at natural pauses in the flow of an app’s execution, such as between levels of a game or just after a task is completed.

Native

Customizable ads that match the look and feel of your app. You decide how and where they’re placed, so the layout is more consistent with your app’s design.

Rewarded

Ads that reward users for watching short videos and interacting with playable ads and surveys. Used for monetizing free-to-play apps.

Additional resources

The Google Mobile Ads repository on GitHub demonstrates how to use the different ad formats that this API offers.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Источник

Таргетинг по ID рекламодателей на мобильных устройствах

Вы можете настраивать таргетинг рекламы на основе списков клиентов. Такой список может состоять из идентификаторов рекламодателей на мобильных устройствах, то есть рекламных идентификаторов Apple или Android либо ID пользователей Facebook. В этой статье мы расскажем, как получить эти идентификаторы и как с их помощью создать пользовательские аудитории для рекламы приложений.

Прежде чем начать, ознакомьтесь со статьей Таргетинг по спискам клиентов.

Общие сведения: получение ID пользователей и настройка таргетинга на них

Обращение к приложению для получения ID

Определитесь, когда вы хотите получать ID пользователей: например, в момент запуска вашего приложения или при выполнении в нем определенного действия (покупки и т. п.).

Идентификация пользователя

Существует несколько технологий, позволяющих идентифицировать человека:

Ниже приведены примеры кода для каждой из них.

Хранение данных

После сбора вы можете сохранить ID пользователей в любой базе данных, электронной таблице Excel или файле CSV.

Экспорт данных

Передавать эти данные в Facebook Ads Manager нужно в виде файла Excel или CSV. Большинство баз данных поддерживает экспорт в один из этих форматов.

Импорт данных в Facebook Ads Manager

Обратитесь к нашему руководству по таргетингу по спискам клиентов. Импортируйте список клиентов из файла Excel или CSV.

Поддерживаемые идентификаторы рекламодателей на мобильных устройствах

Мы поддерживаем три типа идентификаторов рекламодателей на мобильных устройствах:

Рекламный идентификатор Apple (IDFA)

Рекламный ID, который Apple предоставляет в своем рекламном фреймворке в составе iOS.

Рекламный идентификатор Android

Рекламный ID, который Google предоставляет в Google Play.

ID пользователя приложения Facebook

Если люди входят в ваше приложение через Facebook, вы можете использовать для таргетинга ID пользователей внутри приложения.

Источник

Mobile Tutorial Series – What is a Google advertising ID or GAID?

The Google advertising ID is a device identifier for advertisers that allows them to anonymously track user ad activity on Android devices. It has often also been called the Android advertising ID, but Google advertising ID (short form: GAID) is more commonly used.

You can think of the GAID or Android advertising ID as somewhat analogous to a third-party cookie on the web.

Advertisers use third-party cookies to know what actions a user of a particular web browser is taking on their ads on various websites. The Google advertising ID does something similar: it helps advertisers know when an ad has been viewed or clicked in an app, and when an ad causes a conversion.

An app install would be a common tracked conversion using the Google Advertising ID.

The Android advertising ID is a hot topic right now because in iOS 14, Apple has made the IDFA — the iOS version of Google’s advertising identifier — opt-in on a per-app basis, which many web marketers think will reduce the visibility of advertising effectiveness.

The question naturally becomes: will Google make the GAID opt-in as well?

It’s also a hot topic because, in addition to its use in measuring ad campaign effectiveness, the third-party cookie has been used to track people around the web, which has serious privacy implications. Apple has eliminated the third-party cookie from its browser, Safari, and Google will be following suit by 2022. All of which has opened questions about the future of the Google advertising ID on mobile as well.

History of the GAID, or Android advertising ID

Advertisers want to be able to connect ad views with actions.

Before mobile became the dominant means of accessing the internet, cookies served that function in desktop web browsers. Marketers could set a cookie on a website or in an ad and then measure ad effectiveness. However, cookies don’t work well in the mobile world: they work in web browsers, not mobile apps, and we tend to spend most of our time on our phones in apps, not mobile browsers.

In addition, cookies typically have short life-spans … somewhere around one to thirty days.

So the GAID or Android advertising ID took the place of cookies in mobile advertising delivered to Android devices, just as the IDFA did that on iOS devices. Marketers use it to connect app installs or purchases to specific anonymous individuals.

The good thing about GAID from a marketers’ perspective is that in contrast to cookies, Google advertising IDs are semi-permanent device identifiers because they don’t change unless users specifically take an action in their Android device settings. Because few consumers actually do take this action (fewer than 5% in the U.S.), Android advertising IDs can offer a better foundation for a persistent and anonymized consumer profile based at least in part on ad interaction data.

Privacy and GAID (and IDFA)

Privacy has become increasingly important for consumers.

Misuse of advertising identifiers and trackers have created significant problems, and legislation like GDPR and CCPA (the California Consumer Privacy Act) have limited how marketers can collect and use data. The major platforms — especially Apple — have moved to decrease the amount of data that can be collected digitally from consumers.

Interestingly, both the Android advertising ID and the IDFA were actually privacy-focused identifiers.

Each replaced a permanent device ID, the Android ID or ANDI on Android, and the Unique Device Identifier or UDID on iOS. Before Google created the advertising ID, advertisers could track activity on Android phones using that permanent and unchangeable device ID. The Android advertising ID enabled more consumer choice and privacy because people could turn it off or change its value – neither of which is possible with a permanent device ID.

Even so, there is increasing concern that advertising identifiers like GAID and IDFA can also cause significant privacy violations. That has led Apple to make IDFA opt-in and offer SKAdNetwork as a privacy-safe replacement. Google hasn’t said yet what it plans to do with the Android advertising ID, but Google already has potential replacement technologies at least partially in place such as the Google Play Install Referrer.

Using the GAID or Android Advertising ID

When consumers take actions because of ads, like clicking on a banner in an app, playing a video in an app, or installing an app, ad networks can provide the Android advertising ID with information about the consumer action that took place because of the advertising.

This is called attribution, and it attributes actions, or conversions, to stimuli, or ads.

Most media companies do pass Android advertising IDs.

Some media companies, including some large social networks, do not pass device IDs to advertisers but do allow you to target specific IDs within their properties. Singular helps advertisers by associating in-app consumer actions and marketing programs to these semi-permanent identifiers. This helps advertisers understand the effectiveness of their marketing and create powerful customer profiles to understand their audiences.

Using Android advertising IDs and app attribution tools like those offered as part of the Singular Platform, marketers can understand which ads, creative, campaigns, and media partners were responsible for the consumer conversions they want. Using these insights, they can calculate the ROI for all of their ads and tactics, and optimize their campaigns and ads to the most profit-generating tools.

The Android Advertiser ID also enables a marketer to target specific individuals that have taken actions in the past on their mobile devices or find others such as the most highly-engaged users in their apps.

• Re-engagement
  • Find people who have installed an Android app and deliver advertising that invites them to relaunch the app
  • Create an audience of lapsed users and advertise to them on their Android phones to get them to come back to the app
• Offers
  • Identify people who have abandoned items in shopping carts, and present an offer for them to come back and complete their purchases
• Look-alike audiences
  • Identify devices from users who are deeply engaged and profitable in your app, and ask an ad network or media company to find more people who look like those, and therefore would conceivably be good new users to acquire

This sort of individual targeting has become increasingly common as programmatic media and social media advertising grow in popularity for the marketing of apps. However, they may become harder to achieve, if not impossible, if advertising identifiers like GAID and IDFA get essentially deprecated in favor of more privacy-safe solutions.

Источник