Choosing CPID For Notifications
Stay organized with collections
Save and categorize content based on your preferences.
When sending a plan status notification to the user, the following factors must
be considered:
- Has the CPID of the user been registered with GTAF? Until a CPID has been
registered with GTAF, GTAF is unaware of the CPID and hence cannot send
notifications pushed for the CPID.
- Has the user granted consent for the DPA to share plan status information
with GTAF?
As outlined in the Register CPID
section, GTAF only registers CPIDs on behalf of clients whose terms permit them
to do so. This means that the CPID has been registered in accordance with the
consent requirements of Mobile Data Plan module in Google Play Services.
When the DPA gets a trigger from the backend notifying it of a change in the
plan status of the user, it can use one of the following approaches to look up
the CPID to use for sending the notification:
- Use latest registered CPID for the user.
- Use latest registered CPID for the user if the user granted consent.
- Use latest generated CPID.
Registered CPID
The DPA looks up the latest registered CPID and uses that for sending a
notification. If the DPA chooses this method, then it MUST implement the
Register CPID API and store the
latest registered CPID for each user. Please note that GTAF will only register
CPIDs that comply with the terms of service of Mobile Data Plan module in Google
Play Services.
Registered CPID of Consented Users
The DPA looks up the latest registered CPID and sends a notification only if the
user has granted consent. If the DPA chooses this method, then it MUST implement
Register CPID and
Consent APIs and store the latest
registered CPID and the consent status for each user.
Latest Generated CPID
The DPA can store the latest generated CPID for each user and use that for
sending a notification to the user. This is the least desirable method because
this would involve sending notifications for all users who may or may not have
agreed to the client terms and using CPIDs that may not have made it to GTAF.
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.
Last updated 2023-10-03 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2023-10-03 UTC."],[[["\u003cp\u003eGTAF requires user CPID registration and consent for plan status notifications.\u003c/p\u003e\n"],["\u003cp\u003eDPAs can use the latest registered CPID, the registered CPID of consented users, or the latest generated CPID to send notifications.\u003c/p\u003e\n"],["\u003cp\u003eUsing the latest generated CPID is least desirable due to potential consent and registration issues.\u003c/p\u003e\n"],["\u003cp\u003eDPAs using registered CPIDs must implement the Register CPID API, and optionally the Consent API for consented users only.\u003c/p\u003e\n"],["\u003cp\u003eGTAF only registers CPIDs complying with Google Play Services Mobile Data Plan module terms.\u003c/p\u003e\n"]]],["To send plan status notifications, the DPA must consider if the user's CPID is registered with GTAF and if the user consented to share plan status. The DPA can use the latest registered CPID, but this requires implementing the CPID registration API. Alternatively, they can use the registered CPID only for users who granted consent, requiring both CPID registration and consent APIs. A less desirable method is using the latest generated CPID.\n"],null,[]]