Sending Requests
How often are requests triggered by the SDKs?
The SDKs sends requests either automatically or programmatically. The SDKs trigger two types of requests:
Interaction requests
iOS
The SDKs automatically trigger interaction requests (POST) as follows:
- When the app is opened for the first time as a result of the app being installed or reinstalled
- When a View Controller appears on screen
- When a link is opened from the app
Android
The SDKs automatically trigger interaction requests (POST), as follows:
- When the app is opened for the first time as a result of the app being installed
- When an Activity or Fragment appears on screen
- When a link is opened from the app
MXO processes only those interaction requests received from Interaction Points contained in the Interaction Map. This reduces the number of unnecessary interaction requests sent to MXO , automatically, by the SDK.
Interaction requests can also be triggered programmatically by the app developer. These are referenced in the SDKs integration documentation as sendInteraction method.
Properties requests
Both SDKs automatically trigger properties requests (PUT), as follows:
- To send Activity or Attribute Capture points after an interaction request completes, if necessary.
- Activity Capture points are automatically sent as the user taps a button or another tappable element.
- Attribute Capture points are automatically sent as the data appears on screen or as the user enters this data in a text field. If multiple attributes are available on the app screen at the same time, these are bundled and sent under one request.
- When an app is opened through a deep link that contains URL parameters.
- If push notifications are enabled, a push token is sent every time it is updated by the operating system.
Properties requests can also be triggered programmatically, by the app developer. These are referenced in the SDKs integration documentation as sendProperties methods.
What sizes are the request data sent to MXO ?
Interaction Requests
Typically, interaction requests are ~20kb in size.
Property Requests
Typically, properties requests are ~1kb in size.
What happens to SDK service calls if there is no network connection?
If a connection cannot be established or MXO cannot be reached, interactions are cached under a local sqlite database and properties requests are stored in the app's local memory cache.
Once a connection is re-established the SDKs automatically send cached requests one at a time.
What should I do if the actual data captured by the SDK differs from the estimated data capture?
Perform validation of your existing SDK configurations, as follows:
- Validate that installing the app as a new user works in the Play Store or App Store.
- If you have access to the old version of the app, validate that updating that version of the app works correctly.
Tip: For Android you can access previous app versions at https://apkpure.com/.
- Validate the numbers you are seeing in MXO against the number of installs/updates since the app was launched. You can find this information in the Play Store or App Store console.
If you still have concerns, after following the validation process, email us at onesupport@medallia.comNo Content found for mailto:onesupport@medallia.com or visit our self-service Support Portal to ask for further help.