App Listeners
Sometimes you want to be able to interact with the platform, but are unable to connect with API or Webhooks. Thankfully, we provide ways to interact directly with events and activities on our platform. Setting up a listener will allow you to directly get a response from the system, and the sections below describe what sort of response can be expected in different scenarios.
Events which can be listened to:
Submit Campaign Form
Every campaign requires the user to submit a form with fields chosen by the designer of the campaign.
The data in the form as well as activity specific data will be sent back in the response.
The response payload of this event is as follows:- A header called
x-tbits-server-responsewhich will have the valueactivity. - The Content-Type of the response will be
application/json - A field called
activity_duration_mswhich will list the time the campaign took to complete in milliseconds when available. For campaigns that do not support time tracking this field will be blank. - A field called
activity_idwhich will list the ID associated with this activity. - A field called
fan_idwhich will list the ID associated with the fan. - A field called
fan_idwhich will list the ID associated with the fan. - A field called
entry_formwhich will be the data submitted in entry form, encoded as application/x-www-form-urlencoded. - Additional campaign specific fields may also be present in addition to those listed above.
