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 the Refiner Support team.

Getting Started

1. From the Segment web app, click Catalog.
2. Search for “Refiner” in the Catalog, select it, and choose which of your sources to connect the destination 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.

Page

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:

analytics.page()

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

Identify

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: 'john.doe@example.com'
});

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

Group

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:

analytics.group("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.

Track

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.

Engage

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.