You will find here all the vocabulary used by Accengage : 

APK : The package of an Android application compiled has for extension .apk. It's the format used to distribute and install the application on the Android devices.

APNS : Apple Push Notification Service is the heart of the notifications broadcast on iOS. Managed by Apple, this service is in charge of the message distribution on the different registered devices.

Bounce : An user who has uninstall the application

Campaign : It regroup many messages of a different nature. It permit to gather the messages in the statistic platform.

Custom params : All additional parametters in a notification.

Constitute by a key and a value.

States : It's the possibility to target a criteria more precisely in the views. For instance, in the view "Research" I want to target the state "Research Pizza". If the research is different of the defined state, my message will not be displayed.

GCM : Google Cloud Messaging for Android is a Google service which permit to send notifications to the Android devices.

Device ID : Identifier For Vendor : Single identifiers per application and per device on iOS. This identifier change for each uninstall/ reinstall of an application.

IPA : The package of an iOS application compiled has for extension .ipa. It's the format used to distribute and install the application on the iOS devices.

Landing Page : Rebound format of a notification. Usually, it takes the format of an interstitial full page.

Partner ID and Private Key : Credentials which permit to link the application to the SDK - it's the link between servor and the Accengage platform.

.p12 : It's the extension of a provisioning push certificate of an application. There are 2 different types of .p12 : development and production.

Random ID : It's a number attributed to each user randomly. This number is between 0 and 100 and includes decimal.

Rich Push : it's a notification outside of the application which permit to extend the message inside the application : webview or navigator.

SDK : Software Development Kit : gather many helping tools proposed to the developers. In Accengage case, the SDK includes all features linked to the commercial proposition (tracking, push ...).

Template : Each format is integrated in the Accengage SDK as templates format. These templates (xib on iOS, xml in the Android "layout" repertory) are customizable by developers. It is also possible to add new templates after integrate them in the application. You just need to declare them in the Accengage platform to exploit them.

Test Tools : Tool which permit to test different types of tracking (openings, tokens, events, custom params ...)

Token : It's an identifier which stock data numbers for the notifications. For instance, equivalent to the e-mail, he is the key which allow the messages broadcast to the mobile users.

UDID : Unique identifier of an iOS device.

View : An application iOS or Android is build on an arborescence base. Each "page" is called "view". On Accengage, it is imperative to declare beforehand the views in the application and add them in the tool in order to target the display of the in-app formats or trigger the scheduled alarms according to the users navigation.

Volume :

  • The segment volume represents the number of devices find in the platform.
  • The sending history volume tracks the number of devices which possesses a token.
  • The receiver volume registers the number of devices which have an opt-in token.
  • The successful volume is calculate by subtracting the number of bounce to the number of receiver. The rate symbols the users which have really received the push.

Wiki : The Wiki is a guide or an help to the developers in the SDK integration.

.Xib : Correspond to the in-app templates which defines the format.