Refiner Source

Good to know: Event Cloud source

The Refiner Source is an event source. This means that it sends data as events, which are behaviors or occurrences tied to a user and a point in time. Data from these sources can be loaded into your Segment warehouses, and also sent to Segment streaming destinations. Learn more about cloud sources.

This source is supported in US data processing regions.

The Refiner source is only supported in workspaces configured to process data in the US region. Workspaces configured with data processing regions outside of the US cannot connect to this source. For more information, see Regional Segment.

Refiner is a customer survey tool built specifically for SaaS, eCommerce and Membership sites. Ask your users any question while they are using your product with Refiner’s beautiful and simple survey widgets - on brand and perfectly timed.

This source allows you to enrich user profiles with survey responses and use them in any tool connected to your Segment account.

This source is maintained by Refiner. For any issues with the source, contact Refiner Support.

Good to know: This page is about the Refiner Segment source, which sends data into Segment. There’s also a page about the Refiner Segment destination, which receives data from Segment!

Getting Started

  1. From your Segment UI’s Sources page click on “Add Source”.
  2. Search for “Refiner” within the Sources Catalog and click Connect to confirm.
  3. Give the Source a nickname and follow the set-up flow to “Add Source”.
  4. Copy the Write key from the Segment UI and log in to your Refiner account.
  5. In Refiner, navigate to Integrations > Segment and paste the write key to connect.

Identify Call

Refiner sends an identify call each time a user completes a new survey, and includes the collected survey responses parsed into the traits object of the call.

Each trait is prepended with refiner_ so you can easily identify them. For example, the question What is your job role? in Refiner becomes refiner_what_is_your_job_role in the identify call.

An example identify call:

  "type": "identify",
  "traits": {
    "refiner_email": "",
    "refiner_how_big_is_your_team": "10+",
    "refiner_what_is_your_job_role": "CEO",
  "userId": "your-user-id"

You can also define a custom property name for each question in Refiner’s Survey Editor.

Group Call

Refiner’s internal data structure is based on User and Account entities, where one Account can have multiple Users.

Each answer given by a user is either attributed to the User directly, or to their parent Account.

To mirror this behavior in Segment, Refiner sends a group call right after each identify call.

The group call includes all collected data which is linked to an account in Refiner, as well as the userId used in the identify call.

A group call issued by Refiner could look like this:

  "type": "group",
  "groupId": "your-account-id",
  "userId": "your-user-id"
  "traits": {
    "refiner_employee_count": "1000+",
    "refiner_industry": "acounting"

Adding Destinations

Now that your Source is set up, you can connect it with Destinations.

Log into your downstream tools and check to see that your events are appearing as expected, and that they contain all of the properties you expect. If your events and properties don’t appear, check the Event Delivery tool, and refer to the Destination docs for each tool for troubleshooting.

If you see any issues with how the events are arriving to Segment, contact the Refiner support team.

This page was last modified: 25 Apr 2022

Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
Create free account