A WiFi router/modem company has a mobile app that allows users to view their quota and active packages as well as make additional purchases. The app user can manage multiple devices with one mobile user ID. This is useful for Bob who manages one modem for work, one for home, and one for his wife.
Device ID | Email Address | MobUserId | Operating System | Name | *Balance |
---|---|---|---|---|---|
111 | a@a.com | 1abc | Android | Andy | 10,000 |
222 | b@b.com | 2abc | Android | Bob | 50,000 |
555 | e@e.com | 5abc | iOS | Evan | 25,000 |
Bob downloaded the mobile app on his Android phone and created an account/login for Device ID 222, his home modem. Then in the app, he added Device ID 333 for his work modem and Device ID 444 for his wife Mary’s modem. This information is sent to the Multiple Devices relational table via XML API.
Multiple devices relational table
- Mapped to the database using the MobUserId field.
- Device ID is the Unique ID.
- Balance is set up as a numeric field type
MobUserId | Device ID | Name | *Balance |
---|---|---|---|
2abc | 333 | Bob | 30,000 |
2abc | 444 | Mary | 70,000 |
Case 1
When the marketing team sends a mobile app message to all customers, they expect Bob to receive one message (not three).
Choose the mobile push database as the contact source for the mobile app message and the message is sent to only those contacts listed in the database.
Case 2
The marketing team wants to send a push message to notify customers with a balance greater than 60,000 about a special promotion. They expect the message to be sent to the phone which is used to manage the account.
Create a database query with the following criteria:
Profile criteria: balance is greater than 60,000 OR relational table criteria: balance is greater than 60,000
To perform this query, balance must be created as a numeric field type in both the database and the relational table.