Ad Hoc Distribution (iOS Only)
An internal production version of the application, which is distributed to up to 1000 pre-registered devices.
A unique, user-specific identifier, set by the application owner (for example, the user's email or an internal system ID number). The app owner and Appoxee both use the same alias to identify the user. Aliases are also used to identify all devices owned by the same user (an iPhone, an iPad etc.). In addition, aliases are used to create segments of application users, based on user-specific properties (as opposed to application-specific properties). Note the difference between aliases and tags: Aliases are user-specific, and each user can only have one alias (shared by all the user's devices). Tags are app-specific and you can assign multiple tags to the same device.
Appoxee collects and stores data about your application and the messages you send. You can analyze these data using different out-of-the-box graphs. To access Appoxee Analytics, log into your account and select the Analytics tab. You can choose between Application stats and Message stats. An example graph that provides application analytics is the Daily Usage graph, which shows the number of unique application opens per-day, over a specified time-frame. An example graph that provides message analytics is the Message Totals graph, which provides the following statistics:
- Push Sent - the total number of notifications sent from Appoxee to the app users.
- Rich Sent - the total number of Rich Messages sent from Appoxee to the app users.
- Rich Received - the total number of Rich Messages that were received by the in-app Inboxes on devices running the app.
- Rich Opened - the total number of Rich Messages that were opened on devices running the given app within the given time-frame.
App Store Distribution (iOS Only)
An external production version of the application, which is available to the general public and can be downloaded from the App Store.
Apple Push Notification System Service (APNS, IOS Only)
An Apple service that uses Push technology to forward notifications (such as custom text alerts, badges and sounds). The Appoxee server uses APNS to deliver notifications to iOS devices running an app with the Appoxee SDK.
A unique number that the Appoxee server assigns to each app when it is created on the Appoxee website. To find the App ID, go to your Appoxee account, select the Apps tab and then select the Application Name. When the Application Information page is displayed, check the page URL: The App ID is shown at the end of the page's URL.
Badge (iOS Only)
The number shown on the iOS icon (for example, to indicate the number of unread messages). A badge, like Sound and Alert, is an element common to all notifications.
Segmentation based on user behaviour. For example: "Last Activation", "Number of products purchased", "Registration" and "Number of activations".
- Last Activation - The last time the user activated the application (in days).
- Number of products purchased - The number of products a user purchased through the app (in-app purchases).
- Registration - The first time the user activated the app.
- Number of activations - The number of times a specific user opened the application.
A push message that is sent to all opted-in push users at once, across all platforms supported by your app. For example, broadcasts are commonly used to send "Breaking News" notifications, promotions etc.
Cloud to Device Messaging (C2DM)
Google’s pervious mobile Push service for Android devices, deprecated as of June 26 2012 in favor of GCM.
Push Token (iOS Only. Also known as "Device Token")
The device/application identifier used by the Apple Push Notification Service (APNS). A token has a 64 hexadecimal character format. Apple issues two types of tokens: Development and Production (also known as Ad-Hoc/App Store). The token type differentiates between apps that are being developed and apps that are being distributed. Using different device tokens allows Apple to separate between the two Push service-levels required to deliver Push notifications to the devices.
Expiration date (expire_date)
An optional message property, determining whether the message has an expiration date, after which the message will not be delivered (by default, a message does NOT expire). If this property is enabled, you are required to specify the expiration date. Appoxee does not send expired messages. If a message sent by Appoxee expired before the user received it (for example, it the user's device was turned off during the relevant time frame), the push notification service (APNS for iOS devices and GCM for Android devices) makes sure the expired message is not delivered.
Optional custom fields that can be added to a notification. An extra field is defined as a Key-Value pair and is used to invoke a specific code-logic execution in the app. For example, if you want to encourage app users to go to a specific promotional Web page, you can define an extra field whose key is named "Link" and whose value is the page URL (for example, "http://www.MyCompany.com/promotion"). Please be aware that extra fields are counted as characters in the payload, so when you add these fields you have less room for the message text.
A module that improves your application's star rating in the App Store, by allowing users to rate the application and communicate directly with the application owner. The feedbacks are stored on the Appoxee server and can be viewed through the Appoxee UI (by going to the Apps tab and checking the Feedbacks column). To use the Feedback feature, you must enable it in your Appoxee account and add the Feedback code to your application's code.
Google Cloud Messaging (GCM)
Google’s current mobile application messaging service for Android devices, which replaced C2DM as of June 26 2012.
Inbox (also known as In-App Inbox)
An In-app inbox for rich messages. The inbox guarantees your ability to engage the user with rich messages (such as YouTube videos, HTML messages etc.). Note that the Inbox cannot be disabled by users (as opposed to Push Notifications, which users can disable). To use the Inbox feature, you must enable it in your Appoxee account and add the Inbox code to your application's code.
More Apps feature
A feature that enables you to cross-promote your apps from within the app itself. It shows the app user additional apps you released, allowing the user to easily install them. To use the More Apps feature, you must enable it in your Appoxee account and add the More Apps code to your application's code.
Play Store Distribution (Android Only)
The process that creates an .apk file, which you can upload to the Play Store (for either testing or production purposes).
Push enabled users
Users who enabled push notifications for the specific application in their device settings.
The total number of notifications sent from Appoxee to the app users.
The number of devices that have the application installed with the Appoxee SDK. NOTE: If the user downloaded a version of the application that does not include Appoxee, the user's device will not be counted as a registered device.
A Google identifier of the device. Google uses the same Registration ID for the Development phase and the Production phase, and does not restrict the Registration ID's size (as opposed to Apple, which has a separate token for each phase and has a 64 hexadecimal character limit).
An app-related, plain text notification (as opposed to a Rich Message). A Push Notification is pushed to the device's screen, without the need to open the relevant application. Push Notifications are used to inform the users of app-related events, such as content updates, new messages and other events that may interest them. Push notifications also allow the app to display a Badge on the app's icon (for example, the number of unread messages). Note that the user has the option to disable Push Notifications.
An app-related message whose content is rich (as opposed to a Push Notification, whose content is plain text). A Rich Message is used to engage the user with eye-catching content, such as YouTube videos, HTML messages etc. Rich Messages are sent to the in-app Inbox, so to enable such messages you must enable the Inbox feature (see Inbox). Note that users cannot disable Rich Messages (as opposed to Push Notifications, which users can choose to disable).
A unique key, generated per-app by the Appoxee server when the app is created on the Appoxee account. The SDK Key is embedded in the app along with the Secret key. The two keys allow the application to securely use the API.
A unique key, generated per-app by the Appoxee server when the app is created on the Appoxee account. The Secret Key is embedded in the app along with the SDK key. The two keys allow the application to securely use the API.
A feature that groups app users based on different parameters. You can use segments in Push notifications to target the relevant users out of all available users. Segments can include multiple parameters of different types: Application-specific (Tags and Aliases); Behavioral (such as "Last Activation" or "Number of products purchased"); Platform/Devices (such as SDK Version or App Version); and Regional Settings (Location, Language or Time Zone).
Tags are used to label users with different elements of the app's business logic. For example, if your app is intended for pet owners, you can define the different pets as tags ("Dog", "Cat", “Parrot” etc.) and then label users with different tags, depending on the pets they own. Tags are a useful way to create segments: Groups of devices that share the same parameters (in this case, the tag values). You can then send Push notifications to the relevant segments (for example, one notification for dog owners and another for cat owners).
There are two tag lists: The app's global tag list and the device's local tag list. The app's global list is defined on the Appoxee website, stored on the Appoxee server, and then downloaded to the device. Be aware that you cannot add tags locally, only through the website. For more information, see "Using the Tag API in Android" and "Using the Tag API in iOS".
Be aware of the difference between Tags and Aliases: Tags are app-specific and you can assign multiple tags to the same device ("Dog", "Cat" etc.). Aliases are user-specific, and each user can only have one alias (shared by all the user's devices).
A group of internal users who receive notifications from a campaign before these messages are sent out to all users. Test segments are created using application-specific parameters: Tags or Aliases.
Universally Unique Identifier (UUID)
A unique identifier of the device on the Appoxee server