Cashback Offer Integration

There are two key components involved in serving relevant offers to the user, offer serving and determination.

Offer Serving

All of the offers that are shown by the keyboard are requested from an ad server, where the keyboard makes an OpenRTB bid request to the ad server containing user information and matched keywords that occur in the user context.

Depending on the deployment use case your Tappa representative might either recommend that you run offers using the Tappa ad server or if you have your own ad server then the SDK can be configured to send requests there. The ad request made by the keyboard is OpenRTB 2.5 compliant.

Offer Determination

The keyboard determines offer relevance by comparing typed text to a configuration dataset that is dynamically loaded by the keyboard.

The configuration dataset is a mapping of "typed text" to "keyword". When the keyboard detects a match to the typed text fragment then an offer request is made. The offer request is a fully populated OpenRTB request also containing the matched keyword and the fragment of text that was matched. This permits an arbitrary level of sophistication at the server, where it can then learn per user about frequently matched terms and interests.

The keyword dataset is configured as a JSON array and is updated to the keyboard using the delta update mechanism similar to other configuration feeding, at the schedule set in the existing keyboard configuration. Child campaigns e.g locale specific configuration is fully supported.

The offer data is updated using an API to post a new version, your Tappa representative can advise on the credentials and correct endpoint to use for your account.