Alternative Outcomes

Learn how to log the appropriate user interaction for in-app offers and banners.

When logging user interactions, it's important to select the most appropriate outcome type to accurately capture user behavior. The SDK provides generic outcomes for immediate user decisions, as well as additional outcomes for more detailed interactions, such as banner interactions or ads.

If your flow has just 2 potential outcomes, we strongly recommend using simply .positive and .negative outcomes, to avoid extra complexities. However, if your flow has more than 2 potential outcomes, the following outcomes can be used for further distinction:

• .positive: A generic positive outcome, typically used when the user makes an immediate decision (e.g., responding to a full-screen prompt).

  • .positiveInteracted: User interacted with the banner and started the purchase flow, or read more about the offer.

  • .positiveConverted: User successfully completed the intended action (e.g., purchase).

  • .positiveAdTapped: User tapped an advertisement or promotional element.

• .negative: A generic negative outcome, typically used when the user makes an immediate decision (e.g. dismissing a full-screen prompt).

  • .negativeNotInteracted: User did not engage with the banner in any way.

  • .negativeDismissed: User explicitly dismissed the banner (e.g. using a close button).

To see a practical example where these alternative outcomes can be used, see (Coming Soon) Multivariate Monetization.

Logging Outcomes for Ignored Banners

Typical in-app offers force users to make a decision to either accept or dismiss the offer. However, when showing a banner, users may simply ignore the banner (not interacting with it), and continue using the app. In those cases, you may want to log the outcome of the banner at a later point in time.

If the user has not interacted with a banner, consider logging .negativeNotInteracted at a suitable later point, such as when the user closes the app or exits the screen displaying the banner. To handle this, use the context.logIfNotLoggedYet method:

func applicationDidEnterBackground(_ application: UIApplication) {
    if let context = ContextManager.recentContext(flowName: "onboarding_upsell") {
        context.logIfNotLoggedYet(.negativeNotInteracted)
    }
}

Once log or logIfNotLoggedYet is called on a context, it becomes marked as "logged," preventing subsequent duplicate logs. This ensures accurate tracking of user interactions.