Snapboard Destination


Snapboard allows customers to build dashboards and internal tools without code. Snapboard pulls in your data from the apps you use (Segment, Stripe, etc) and displays them as a spreadsheet in Snapboard (which you can filter, sort, group, etc).

You can then create any tool you want by hooking up the data to the cards/components (inputs, sliders, tables, charts, forms, todos, calendars, gallery, etc).

This destination is maintained by Snapboard. For any issues with the destination, please reach out to their team.

Note:

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

Getting Started

  1. From your Segment UI’s Destinations page click on “Add Destination”.
  2. Search for “Snapboard” within the Destinations Catalog and confirm the Source you’d like to connect to.
  3. Drop in the “API Key” into your Segment Settings UI which you can find from your Snapboard dashboard.

You can obtain the API Key by logging into Snapboard, clicking on the circle icon in the top-left, and then clicking on the workspace name. Then click on the Settings menu item.

settings menu

And then select the [Workspace Name] that your would like to send your Segment events to. Ensure you select the correct workspace, because data cannot be shared between workspaces.

token

Page

If you haven’t had a chance to review our spec, please take a look to understand what the Page method does. An example call would look like:

analytics.page()

Page calls are sent to Snapboard as a pageview.

Screen

If you haven’t had a chance to review our spec, please take a look to understand what the Screen method does. An example call would look like:

[[SEGAnalytics sharedAnalytics] screen:@"Home"];

Screen calls are sent to Snapboard as a screenview.

Identify

If you haven’t had a chance to review our spec, please take a look to understand what the Identify method does. An example call would look like:

analytics.identify('userId123', {
  email: 'john.doe@example.com'
});

Identify calls are sent to Snapboard as an identify event.

Track

If you haven’t had a chance to review our spec, please take a look to understand what the Track method does. An example call would look like:

analytics.track('Login Button Clicked')

Track calls are sent to Snapboard as a track event.

Alias

If you haven’t had a chance to review our spec, please take a look to understand what the Alias method does. An example call would look like:

analytics.alias("507f191e81");

Alias calls are sent to Snapboard as a alias event.

Personas

You can send computed traits and audiences generated through Segment Personas to this destination as a user property. To learn more about Personas, reach out 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.

Settings

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

API Key

Go to Settings > [Workspace Name] > Tokens

This page was last modified: 10 Mar 2020

Get started with Segment

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