Cloud Softphone app can be integrated with various 3rd party services to allow tracking of certain in-app events for purposes like:
- analytics for running advertising campaings, conversion tracking
- monitoring user behaviors, early detection of situations with poor user experience
- usage statistics, demographics, details about audience
Event tracking has to be enabled in “Features” section of your Cloud Softphone app. It is currently only available for full white-label apps. Once the feature is enabled, you will be able to fill in the credentials for your event tracking service inside the “Whitelabel options” step.
Cloud Softphone currently supports the following event tracking systems:
- Fabric (https://fabric.io/)
- Google Firebase (https://firebase.google.com)
- AppsFlyer (https://appsflyer.com)
Cloud Softphone portal will let you fill in credentials for all supported services and will use those services for which you provide credentials. To limit the network traffic, it’s advisable to use only one event tracking service.
Cloud Softphone has to map in-app events to the events recognized by the tracking service, so the naming of the events may differ. Explanations about individual events and the mapping is given below.
This event is reported when user creates a new account and saves it This typically happens after the app is provisioned. Note that this event does no checking whether the account is valid or whether it was successfully registered.
Service Event Name Fabric Sign Up Event AppsFlyer af_complete_registration Firebase
Reported when an account successfully registers with SIP server. This usually happens shortly after the app is started or moved from background to foreground.
Service Event Name Fabric Login Event AppsFlyer af_login Firebase
Reported whenever the app is started.
Note that this event is reported only when the app is already provisioned. Starting the app into initial screen where the user can scan QR code, fill in username&password or go through registration wizard will NOT trigger this event.
Some tracking services don’t have a dedicated event to map to and simply use this event to show daily usage statistics.
Service Event Name Fabric appStart custom event AppsFlyer N/A Firebase
Reported whenever the user originates an outgoing call.
Service Event Name Fabric callOut custom event AppsFlyer callout Firebase
Reported whenever the user receives an incoming call. This event is reported for both pushed and direct incoming calls, including calls handled by CallKit on iOS. The event is reported at the time the incoming call is received, regardless of whether the user answers or whether the call is rejected by DND etc.
Service Event Name Fabric callIn custom event AppsFlyer callin Firebase
Reported when the call reaches terminal state (user hangs up, call is terminated because of no network etc.)
Service Event Name Fabric callEnd custom event AppsFlyer callend Firebase