Definition / Vocabulary

You will find here all the vocabulary used by Accengage : 

APK: The package of an Android application compiled with the extension .apk. It's the format used to distribute and install the application on 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: This information is reported to indicate that the device id has an invalid token. In most cases, the app has been uninstalled by the user on his device. 

Campaign: A campaign is a file in which you create one or more messages. It allows you to fetch overall statistics for messages of the same type and organize your actions in the interface.

Custom params: allows you to send data to the application at the moment the user clicks on the notification. It can be useful for analytic tools. For example, if you're using Google Analytics, you can indicate your custom parameters as follows in order to retrieve data to your GA account "key = utm_campaign" "value = campaign_name"

States: Allows you to trigger In-App messages or scheduled alarms. However, for states there are two differences:

  1. states are not transmitted to the server
  2. You can trigger messages by state values and not just by state ID (event ID).

As for events, states must be declared firstly via Accengage dashboard. Then you can select a state value for which you need to activate or deactivate triggering a message.

GCM: (Service depreciated since May 2019 in favor of FCM) Google Cloud Messaging for Android is a Google service that permits sending notifications to the Android devices.

FCM: Firebase Cloud Messaging, this is Google's new service for sending notifications under Android since May 2019.

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

Regarding Android, the deviceID remains the same because it is linked to the device and not to the application. However, starting with Android 8, the deviceID tends to change as it the case on IOS. 

IPA: The package of an iOS application compiled with the 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 server and the Accengage platform.

.p12: It's the extension of a provisioning push certificate of an application. This type of certificate is necessary for your IOS applications as well as for Safari web push. 

For IOS please specify if it is a production or development certificate. Please also note that only one certificate can be uploaded at a given time.

You will find here our .p12 certificate article. 

Random ID: It's a number attributed to each user randomly. This number is between 0 and 100 and includes decimal. This can be used as a criterion in a segment in order to divide your database for an A/B testing campaign for example.

Rich Push: it's a notification outside the application that permits 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 into the Accengage SDK as a 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 integrating them into the application. You just need to declare them in the Accengage platform to exploit them.

Test Tools: Tool, available in the help tab on our platform, which permits testing 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 that allows the messages broadcast to mobile users.

UDID: Unique identifier of an iOS device.

View: An application for iOS or Android is built on a tree structure 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 user's navigation.

.Xib: Correspond to the in-app templates which define the format on iOS.


Was this article helpful?
0 out of 0 found this helpful
Submit a request