Document audience and usage

This document assumes that you have an understanding of basic programming concepts and variable principles. This document is not an instructional or general guide to programming. Examples provided are specific to the most commonly requested solutions. This document provides guidance on how to add or change custom parameters. Consult your Digital expert for specific requirements on integrating.

Targeting examples

Custom parameters can define when a survey is triggered, providing your app with fine-grained control over when to target. For example, when your app exposes information related to specific types of customers (such as differentiating between regular and VIP customers), set up a custom parameter to capture this information. This custom parameter can then be used for targeting, for example surveying only VIP customers.

Medallia recommend adding custom parameters at regular stages of the flow of your app. Custom parameters are not sent to Medallia until the app calls the one of the setCustomParameter or setCustomParameters methods. Therefore there is little overhead for adding custom parameters. Similarly, if your app is already sending data to an analytics platform such as Adobe Analytics then recommended practice is to also send the same data to Digital. This makes it easy to make targeting decisions based on the same data used for analysis.

Data collection examples

A custom parameter can collect information from a app and add it to the feedback collected. For example, if a app displays the user name for a logged-in user, a custom parameter could store this information, instead of asking the user to provide that information during survey submission. This is useful when a app includes data that can provide more information about a user or add to the context and information about the customer's experience at the time of survey submission.

To illustrate, imagine an online shopping page where you invite a customer to leave feedback. Use custom parameters to understand any or all of the following items:

• Did the user place anything in the cart?

• What is the value of the cart?

• How many items are in the cart?

• Is the customer logged in?

• Is the customer a specific type of customer, such as bronze, silver, gold, or platinum?

• Is there a specific campaign ID or transaction information?

If a custom parameter is attached to a survey, the feedback item contains a new section and a new field when the feedback is received. The custom parameter does not add a field to the survey.

The following lists some examples of how custom parameters can be used in different industries:

• eCommerce/retail - Cart value, loyalty, products viewed or purchased

• Insurance - Member type, group number

• Travel hospitality - Confirmation code, loyalty ID

Custom parameter types

In Digital Mobile SDK custom parameters collect data when the app calls the setCustomParameter or setCustomParameters methods. The value passed to these methods can be a number, text, or a boolean. Unlike Digital Web, in Digital Mobile SDK there is only one type which is always Var.