You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/admob/european-user-consent.md
+22-22
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,13 @@
1
1
---
2
2
title: European User Consent
3
-
description: Understand how the EU User Consent Policy can be managed within AdMob and how it effects your application.
3
+
description: Understand how the EU User Consent Policy can be managed within AdMob and how it affects your application.
4
4
---
5
5
6
6
# European User Consent
7
7
8
8
Under the Google [EU User Consent Policy](https://www.google.com/about/company/consentstaging.html), you must make
9
-
certain disclosures to your users in the European Economic Area (EEA) and obtain their consent to use cookies or
10
-
other local storage, where legally required, and to use personal data (such as AdID) to serve ads. This policy
9
+
certain disclosures to your users in the European Economic Area (EEA) and obtain their consent to use cookies or
10
+
other local storage, where legally required, and to use personal data (such as AdID) to serve ads. This policy
11
11
reflects the requirements of the EU ePrivacy Directive and the General Data Protection Regulation (GDPR).
12
12
13
13
The React Native Firebase AdMob module provides out of the box support for helping to manage your users consent
@@ -22,7 +22,7 @@ The `AdsConsent` helper & AdMob module provides out of the box support for:
22
22
23
23
## Understanding AdMob Ads
24
24
25
-
Ads served by Google can be categorized as personalized or non-personalized, both requiring consent from users in the EEA. By default,
25
+
Ads served by Google can be categorized as personalized or non-personalized, both requiring consent from users in the EEA. By default,
26
26
ad requests to Google serve personalized ads, with ad selection based on the user's previously collected data. Users outside of the EEA do not require consent.
27
27
28
28
> The `AdsConsent` helper only provides you with the tools for requesting consent, it is up to the developer to ensure the consent status is reflected throughout the app.
@@ -93,22 +93,22 @@ Now we understand the consent status of the user, we can gather their consent (i
93
93
94
94
If you are aware that users are under the age of consent in Europe, it is possible to set this using the `setTagForUnderAgeOfConsent`
95
95
method (TFUA). Once the setting is enabled, the Google-rendered consent form will fail to load. All ad requests that include
96
-
TFUA will be made ineligible for personalized advertising and remarketing. TFUA disables requests to third-party ad technology
96
+
TFUA will be made ineligible for personalized advertising and remarketing. TFUA disables requests to third-party ad technology
97
97
providers, such as ad measurement pixels and third-party ad servers.
98
-
98
+
99
99
To remove this setting, pass `false` to the method.
100
100
101
101
#### 1. Google-rendered consent form
102
102
103
-
The Google-rendered consent form is a full-screen configurable form that displays over your app content.
103
+
The Google-rendered consent form is a full-screen configurable form that displays over your app content.
104
104
You can configure the form to present the user with combinations of the following options:
105
105
106
106
- Consent to view personalized ads
107
107
- Consent to view non-personalized ads
108
108
- Use a paid version of the app instead of viewing ads
109
109
110
-
You should review the consent text carefully: what appears by default is a message that might be appropriate if you use
111
-
Google to monetize your app; but Google cannot provide legal advice on the consent text that is appropriate for you.
110
+
You should review the consent text carefully: what appears by default is a message that might be appropriate if you use
111
+
Google to monetize your app; but Google cannot provide legal advice on the consent text that is appropriate for you.
112
112
To update consent text of the Google-rendered consent form, modify the `consentform.htm`l file included in the Consent SDK as required.
113
113
114
114
> An [example of a Google-rendered](https://developers.google.com/admob/images/android_eu_consent_form.png) consent form.
The requested ad URL via the SDK will send a request with an additional parameter `&npa=1`, which will return a
235
+
The requested ad URL via the SDK will send a request with an additional parameter `&npa=1`, which will return a
236
236
non-personalized ad.
237
237
238
238
> The requestNonPersonalizedAdsOnly option can be applied to every supported ad format.
@@ -241,14 +241,14 @@ non-personalized ad.
241
241
242
242
#### "Could not parse Event FE preflight response."
243
243
244
-
This is a common error which occurrs on both Android & iOS when making a request to display a Google-rendered consent form. Unfortunatly the reasoning for this error is generic, making it hard to debug. There are a number of steps to check which are usually the cause for this error:
244
+
This is a common error which occurs on both Android & iOS when making a request to display a Google-rendered consent form. Unfortunately the reasoning for this error is generic, making it hard to debug. There are a number of steps to check which are usually the cause for this error:
245
245
246
-
- The AdMob App ID is incorrect: Ensure you have entered the correct ID into the `firebase.json` file under the React Native config, called `occurs`.
246
+
- The AdMob App ID is incorrect: Ensure you have entered the correct ID into the `firebase.json` file under the `admob_app_id` key in the `react-native` config.
247
247
- A publisher ID is incorrect: Ensure your entered publisher IDs are correct.
248
248
- The publisher ID needs to be available on the same account as your AdMob App ID.
249
249
- The user is outside of the EEA: If a user does not need to provide consent, the form request will error. Ensure you have checked the users status via `requestInfoUpdate`. If using an emulator, ensure you set a debug location via `setDebugGeography`.
250
250
- Your AdMob account is not valid:
251
-
- Your account is not disabled: This can occur if Google notices you have duplicate accounts. They will email you about this, and block you from entering the dashboard.
252
-
- You have setup valid payment information: If your account has no payment information setup, this seems to cause this error to trigger.
251
+
- Your account is disabled: This can occur if Google notices you have duplicate accounts. They will email you about this, and block you from entering the dashboard.
252
+
- You have provided invalid payment information: If your account has no payment information set up, this seems to cause this error to trigger.
253
253
254
254
If you are still struggling to present the consent form, reach out to AdMob support to investigate your account status.
Copy file name to clipboardExpand all lines: docs/admob/index.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -22,15 +22,15 @@ _We are currently investigating how to integrate with [Native Ads](https://devel
22
22
icon="attach_money"
23
23
color="#2196f3"
24
24
title="Quick Start"
25
-
to="quick-start"
25
+
to="admob/quick-start"
26
26
>
27
27
Install & start monetizing your React Native application with AdMob.
28
28
</Block>
29
-
<Block
29
+
<Block
30
30
icon="pan_tool"
31
31
color="#f44336"
32
32
title="European User Consent"
33
-
to="european-user-consent"
33
+
to="admob/european-user-consent"
34
34
>
35
35
Learn how to request consent from users within the EEA. The AdMob library comes with built in support to help you handle GDPR regulations in your application.
The AdMob package provides a JavaScript API for integrating event based adverts such as Interstitial Ads and
21
-
React component view adverts such as Banner Ads. It also provides functionality for requesting consent from those users within the EEA, specified by EU ePrivacy Directive & GDPR.
21
+
React component view adverts such as Banner Ads. It also provides functionality for requesting consent from those users within the EEA, specified by EU ePrivacy Directive & GDPR.
22
22
23
23
Import the Cloud Functions package into your project:
24
24
@@ -34,7 +34,7 @@ import { firebase } from '@react-native-firebase/admob';
34
34
35
35
### Important: Adding your AdMob App ID
36
36
37
-
The AdMob module needs hooking up to your own Google AdMob account. On [the dashboard](https://apps.admob.com/v2/home), you can add an application via the "Apps" menu item. Once created, under the "App settings" section you will find a custom "App ID". This ID is needed in order for the module to be used.
37
+
The AdMob module needs to be hooked up to your own Google AdMob account. On [the dashboard](https://apps.admob.com/v2/home), you can add an application via the "Apps" menu item. Once created, under the "App settings" section you will find a custom "App ID". This ID is needed in order for the module to be used.
@@ -56,12 +56,11 @@ Ensure you **rebuild** your application for the changes to take effect.
56
56
57
57
Out of the box, AdMob does not handle any related regulations which you may need to enforce on your application. It is up to the developer to implement and handle this on a user-by-user basis. For example, you must consent to EEA users being served both personalized and non-personalized adverts before showing them. For more information, see [Requesting Consent from European Users](https://developers.google.com/admob/android/eu-consent).
58
58
59
-
The AdMob module provides a `AdConsent` helper to help developers quickly implement consent flows within their application. See the
60
-
<Anchorversiongrouphref="/european-user-consent">European User Consent</Anchor> page.
59
+
The AdMob module provides a `AdConsent` helper to help developers quickly implement consent flows within their application. See the <Anchorversiongrouphref="/european-user-consent">European User Consent</Anchor> page.
61
60
62
61
### Example: Displaying an Interstitial
63
62
64
-
An interstitial is a full screen advert which is overlaid on-top of your currently application. They are perfect for showing periodically between game levels or after the user completes an action.
63
+
An interstitial is a full screen advert which is overlaid on-top of your currently application. They are perfect to show periodically between game levels or after the user completes an action.
65
64
66
65
#### Testing
67
66
@@ -111,11 +110,11 @@ Once created, you will be provided with a new Ad Unit ID which can be passed ove
111
110
112
111
### Configuring Ad Requests
113
112
114
-
The AdMob module provides two ways of filtering and handling ad content within your app.
113
+
The AdMob module provides two ways of filtering and handling ad content within your app.
115
114
116
115
### Global Configuration
117
116
118
-
To comply with various online acts, such as [Children's Online Privacy Protection Act (COPPA)](http://business.ftc.gov/privacy-and-security/children%27s-privacy) and [General Data Protection Regulation (GDPR)](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32016R0679), it is possible to set targetting preferences across every ad request in your aplication.
117
+
To comply with various online acts, such as [Children's Online Privacy Protection Act (COPPA)](http://business.ftc.gov/privacy-and-security/children%27s-privacy) and [General Data Protection Regulation (GDPR)](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32016R0679), it is possible to set targetting preferences across every ad request in your application.
119
118
120
119
Using the `setRequestConfiguration` method, all future ad requests will comply with the `RequestConfiguration` set:
For more information on the options available, see the `RequestConfiguration` documentation.
131
+
For more information on the options available, see the [`RequestConfiguration` documentation](https://firebase.google.com/docs/reference/android/com/google/android/gms/ads/RequestConfiguration).
The Analytics package will automatically start tracking events such as when users clear app data, dismiss notifications and more.
21
-
To view the full list of automatic events, see <Anchorversiongrouphref="/reserved-events">Reserved Events</Anchor>.
21
+
To view the full list of automatic events, see [this page](https://support.google.com/firebase/answer/6317485) of the official Firebase documentation.
22
22
23
23
The package also provides a JavaScript API to allow for logging custom events and metrics throughout your application.
24
24
@@ -52,7 +52,7 @@ async function onProductView() {
52
52
53
53
### Attaching user data
54
54
55
-
User data can be attached to analytical events via the `setUser*`methods:
55
+
User data can be attached to analytical events via the [***`setUserId`](reference/module#setUserId), [***`setUserProperties`](reference/module#setUserProperties) and [***`setUserProperty`](reference/module#setUserProperty)methods. Each Firebase project can have up to 25 uniquely named (case-sensitive) user properties.
@@ -65,9 +65,11 @@ async function onSignIn(user) {
65
65
}
66
66
```
67
67
68
+
> When you set user properties, be sure to never include personally identifiable information such as names, social security numbers, or email addresses, even in hashed form.
69
+
68
70
### Tracking screen names
69
71
70
-
Similar to Analytics on the web, it's important to understand the user journey within your application, for example
72
+
Similar to Analytics on the web, it's important to understand the user's journey within your application, for example
71
73
tracking drop off points during a e-commerce transaction flow. The Analytics package provides a method called
Copy file name to clipboardExpand all lines: docs/auth/phone-auth.md
+4-2
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,8 @@ Phone authentication allows users to sign in to Firebase using their phone as th
9
9
to the user via their phone number containing a unique code. Once the code has been authorized, the user is able to
10
10
sign in to Firebase.
11
11
12
+
Phone numbers that end users provide for authentication will be sent and stored by Google to improve our spam and abuse prevention across Google services, including but not limited to Firebase. **Developers should ensure they have appropriate end-user consent prior to using the Firebase Authentication phone number sign-in service.**
13
+
12
14
> Firebase Phone Auth is not supported in all countries. Please see their [FAQs](https://firebase.google.com/support/faq/#develop) for more information.
13
15
14
16
React Native Firebase provides two separate integration flows:
@@ -23,10 +25,10 @@ The `signInWithPhoneNumber` method handles the entire authentication flow, howev
23
25
error handling. Some Android devices may also automatically handle the incoming SMS code and authenticate the user
24
26
automatically.
25
27
26
-
**Step 1**: Trigger phone auth
27
-
28
28
> Whilst testing, make sure you have [whitelisted your device](https://firebase.google.com/docs/auth/ios/phone-auth#test-with-whitelisted-phone-numbers).
0 commit comments