Skip to content
Open Screeb

Connect RudderStack as a source or destination

Use your RudderStack events and traits to target Screeb surveys, and send survey displays and answers back to RudderStack.

Integration4 min read, updated Oct 15, 2026

Screeb connects to RudderStack in both directions. As a source, RudderStack forwards your users’ events and traits to Screeb, so you can target surveys on them. As a destination, Screeb sends an event to RudderStack each time a survey is displayed or answered, so your other tools get the feedback.

  • Both integrations are part of your plan. If a card shows Upgrade to install, your plan does not include it.
  • You are an Admin of the Screeb workspace: only Admins install and remove integrations.
  • You can add sources and destinations in your RudderStack workspace.
  • If your organization runs on a dedicated Screeb platform, the source page shows “Contact us to connect this integration to your workspace.”: contact us and we connect it for you.
  1. Open Integrations and, on the RudderStack source card, click Install. The integration is created and its page shows a Webhook URL and a Header.
  2. In RudderStack, add a Webhook destination and connect it to the source that collects your users’ events.
  3. In its settings, paste the Screeb webhook URL, keep the POST method, and add a header: key Authorization, value the Bearer ... text of the Screeb page. Use Copy to copy each value.
  4. Back in Screeb, turn on Would you like to ignore events from anonymous users? if you only want events that carry a userId, and click Save.
The RudderStack Source page in Screeb, with the webhook URL, the POST method, the Authorization header and the anonymous switch
The RudderStack form to create a Webhook destination, with the Webhook URL, URL Method and Headers fields

Reset next to the token creates a new one: the old token stops working at once, so update the header in RudderStack right away. When the workspace setting Ignore anonymous users is on, the anonymous switch is locked on.

Keep the same identity in RudderStack and Screeb

Section titled “Keep the same identity in RudderStack and Screeb”

Screeb finds the respondent of each RudderStack event from its userId, or from its anonymousId when the visitor is not logged in. To keep one profile per person, identify users with the same id in RudderStack and Screeb, and give Screeb the RudderStack anonymous id: see User identity across tools.

Send Screeb data to RudderStack (destination)

Section titled “Send Screeb data to RudderStack (destination)”
  1. In RudderStack, add a Webhook source. Its settings show a webhook URL ending in ?writeKey=....
  2. In Screeb, open the RudderStack destination page.
  3. In Webhook URL, paste the URL without its ?writeKey=... part, for example https://<your-dataplane-url>/v1/webhook.
  4. In Write key, paste the value that follows writeKey=. Screeb adds it to the URL itself.
  5. Click Install.
The settings of a RudderStack Webhook source, with its webhook URL ending in writeKey
The RudderStack Destination page in Screeb, with the Webhook URL and Write key fields

From RudderStack to Screeb, as soon as RudderStack delivers each event:

  • identify: the traits become user properties.
  • track: the event and its properties, listed in User events, ready for targeting.
  • screen: a screen view.
  • group: the user joins or leaves the group, with its traits.
  • Traits sent in the context of any event update the user too.
  • page and alias calls are ignored.

New users from RudderStack count in your plan’s monthly tracked users, like users of the SDK.

From Screeb to RudderStack, for every survey of the workspace (not messages), as track calls:

  • Survey seen when a survey is displayed.
  • Survey question answered at each answer, with every answer of the response so far.

The userId is the id Screeb shows for the respondent: the first of its linked ids that is not a UUID (usually the user id you identified), else its first linked id, else its Screeb id. An anonymous respondent known from a RudderStack anonymousId is therefore sent with that anonymousId as its userId, and only a respondent without linked ids is sent with its Screeb id. The anonymousId is always empty. Properties include the survey, the channel, the response (id, time, language, tags, completion), the respondent’s name, email and groups, the questions and answers, the respondent’s properties at response time, and hidden_field_* and context_* properties.

No RudderStack events in Screeb. Check that the Webhook destination is enabled, connected to the right source, and sends the Authorization header with the current token. If an anonymous setting is on, only events with a userId arrive.

No Screeb events in RudderStack. Check that the URL in Screeb has no ?writeKey= part, and that the write key is the one of the Webhook source.

Open the integration page and click More at the top right, then Delete, and confirm with Delete integration. Its configuration is deleted. Also remove the Webhook destination or source in RudderStack, which would otherwise keep failing.