Refiner Destination

Refiner is a user qualification and lead scoring platform for B2B SaaS companies with a free trial or freemium model. Refiner helps self-service SaaS providers to identify and convert more high-revenue accounts.

This destination is maintained by Refiner. For any issues with the destination, contact their team.

NOTE: The Refiner Destination is currently in beta, which means that they are still actively developing the destination. This doc was last updated on April 24, 2019. If you are interested in joining their beta program or have any feedback to help improve the Refiner Destination and its documentation, let their team know!

Getting Started

The first step is to make sure Refiner supports the source type and connection mode you’ve chosen to implement. You can learn more about what dictates the connection modes we support here.

Web Mobile Server
📱 Device-mode
☁️ Cloud-mode
  1. From your Segment UI’s Destinations page click on “Add Destination”.
  2. Search for “Refiner” within the Destinations Catalog and confirm the Source you’d like to connect to.
  3. Enter your Refiner “API Key” into the Segment Settings. You can find this key in on the Refiner dashboard settings under Integrations > Segment.


If you’re not familiar with the Segment Specs, take a look to understand what the Page method does. An example call would look like:

Segment sends page() calls to Refiner as a pageview event.


If you’re not familiar with the Segment Specs, take a look to understand what the Identify method does. An example call would look like:

analytics.identify('userId123', {
  email: ''

Segment sends identify() calls to Refiner as an identify event.


If you haven’t had a chance to review our spec, take a look tounderstand what the Group method does. An example call would look like:"0e8c78ea9d97a7b8185e8632", {
  name: "Initech",
  industry: "Technology",
  employees: 329,
  plan: "enterprise",
  "total billed": 830

Group calls are the equivalent of providing an account object in a identifyUser call in Refiner.


If you’re not familiar with the Segment Specs, take a look to understand what the Track method does. An example call would look like:

analytics.track('Login Button Clicked')

Segment sends track() calls to Refiner as a trackEvent event. Note that Refiner doesn’t store the attributes sent alongside an event.


You can send computed traits and audiences generated through Segment Personas to this destination as a user property. To learn more about Personas, contact us for a demo.

For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property order_completed_last_30days: true, and when this user no longer satisfies we will set that value to false.

When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.


Segment lets you change these destination settings from your Segment dashboard without having to touch any code.


You can find your API in your project settings

This page was last modified: 09 Jun 2020

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