GraphJSON Destination

GraphJSON provides self-serve analytics to better help you understand your business.

This destination is maintained by GraphJSON. For any issues with the destination, contact the GraphJSON Support team.

Getting Started

1. From the Destinations catalog page in the Segment App, click Add Destination.
2. Search for “GraphJSON” in the Destinations Catalog, and select the “GraphJSON” destination.
3. Choose which Source should send data to the “GraphJSON” destination.
4. Go to the https://graphjson.com/dashboard/integrations/segment, find and copy the “API key”.
5. Enter the “API Key” in the “GraphJSON” destination settings in Segment.
6. Go to https://graphjson.com/dashboard/integrations/segment and finish the setup on the GraphJSON side.

Supported methods

GraphJSON supports the following methods, as specified in the Segment Spec.

Page

Send Page calls to GraphJSON. For example:

analytics.page()

Segment sends Page calls to GraphJSON as a pageview.

Screen

Send Screen calls to GraphJSON. For example:

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

Segment sends Screen calls to GraphJSON as a screenview.

Identify

Send Identify calls to GraphJSON. For example:

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

Segment sends Identify calls to GraphJSON as an identify event.

Track

Send Track calls to GraphJSON. For example:

analytics.track('Login Button Clicked')

Segment sends Track calls to GraphJSON as a track 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.