> For the complete documentation index, see [llms.txt](https://documentation.crossengage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.crossengage.io/data-and-engagement-platform/messages/integrations/channels/onsite-display/trbo/obtain-response-data.md).

# Obtain Response Data

## Receiving response data

To ensure that you receive Trbo response data, please reach out to your Trbo Customer Success manager and provide them with your CrossEngage "Web tracking and response data API key".

<figure><img src="/files/GLDptxroC87J9sSCfCsK" alt=""><figcaption></figcaption></figure>

This key will be used to send events to CrossEngage endpoints which will be stored on customer profiles. You can find this key under **Settings → System setup.**

## Understanding response data

When using Trbo, CrossEngage receives & stores 3 different types of events:

* Sent, when a user was successfully sent to a Trbo campaign's audience (in segmentation trbo.segment.transfer.sent).
* Viewed, when a user views an onsite display campaign element belonging to a Trbo campaign to which audience he was transferred to from CrossEngage (in segmentation trbo.segment.transfer.viewed).
* Clicked, when a user clicks on an onsite display element belonging to a Trbo campaign to which audience he was transferred to from CrossEngage (in segmentation trbo.segment.transfer.clicked).

These events are received in realtime via API from Trbo and allow you to react and base further cross channel campaigns upon them through CrossEngage realtime campaigns.

If you require using additional metadata from these Trbo events in segmentation, please contact your dedicated CrossEngage Customer Success Manager or send an email to <support@crossengage.io> to ensure that the "Event Properties" are activated for usage. In your request, please include the required types of properties (e.g. STRING, FLOAT) and their names so that our team can quickly build these for you.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.crossengage.io/data-and-engagement-platform/messages/integrations/channels/onsite-display/trbo/obtain-response-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.