Skip to main content
Dex 666
Level 2
August 24, 2026
Solved

Capping in Offer Decisioning in Mobile SDK

  • August 24, 2026
  • 4 replies
  • 71 views

I noticed that capping is not counter properly in Offer Decisioning. 

Which schema is responsible for that:
1. ajo_inbound_activity_event_dataset
2. ODE DecisionEvents
Does the event that the offer is displyed and clicked in Mobile SDK is generated automatically or manually? 

In order for the capping to work I need to include of these two datasets include in Datastreams (that is what Adobe support advised). However these two schemas has different structure then that specific for Mobile SDK?

Best answer by Pulkit_Jain_

​@Dex 666  Neither, of the two.

You need a dataset with the "Proposition Interactions" field group in its schema. ajo_inbound_activity_event_dataset is unrelated (inbound SMS/RCS only). ODE DecisionEvents only applies if using AJO Decisioning.

Mobile SDK requires you to call offer.displayed() / offer.tapped() manually. Not automatic (auto only applies to AJO Decisioning).

Also, Structure mismatch is a valid concern.

ajo_inbound_activity_event_dataset won't work — wrong schema entirely.

You just need any dataset whose schema includes the Proposition Interactions field group in your Datastream — confirm with support which one that actually is.

4 replies

Pulkit_Jain_
Adobe Employee
Pulkit_Jain_Adobe EmployeeAccepted solution
Adobe Employee
August 24, 2026

​@Dex 666  Neither, of the two.

You need a dataset with the "Proposition Interactions" field group in its schema. ajo_inbound_activity_event_dataset is unrelated (inbound SMS/RCS only). ODE DecisionEvents only applies if using AJO Decisioning.

Mobile SDK requires you to call offer.displayed() / offer.tapped() manually. Not automatic (auto only applies to AJO Decisioning).

Also, Structure mismatch is a valid concern.

ajo_inbound_activity_event_dataset won't work — wrong schema entirely.

You just need any dataset whose schema includes the Proposition Interactions field group in your Datastream — confirm with support which one that actually is.

    Dex 666Author
    Level 2
    August 24, 2026

    Thanks!

    These events proposition.display and proposition.interact are no display automatically in Mobile SDK implementation? Has to be implemented in the source code of the Mobile App?
    Adobe Journey Optimizer proposition edge events

    Pulkit_Jain_
    Adobe Employee
    Pulkit_Jain_Adobe Employee
    Adobe Employee
    August 25, 2026

    Yes — for code-based experiences / Offer Decisioning offers, since the app renders the UI not the SDK, propositionDisplay/propositionInteract are not automatic. You must explicitly call the tracking APIs (offer.displayed(), offer.tapped(), or proposition.track(...)) in your app code.

      Terms & ConditionsAccessibility statement

      Loading footer...