You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Jebbit Source

Source Info

The Jebbit Source is an Event Cloud 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 integration is partner owned. Please reach out to the partner's support for any issues.

Jebbit helps build and design fun, engaging quizzes and customer experiences with speed and control, all while capturing customer preferences as zero-party data.

This is an Event Cloud Source which can not only export data into your Segment warehouse, but they can also federate the exported data into your other enabled Segment Destinations.

This source is maintained by Jebbit. For any issues with the source, contact their Support team.

Getting Started

From the Segment UI's Sources catalog page click Add Source.
Search for "Jebbit" in the Sources Catalog, select click Jebbit, and click Add Source.
On the next screen, give the Source a nickname and configure any other settings.

The name identifies this source within your workspace, and typically reflects the name of the application. The name can be anything, but should be something that reflects the source itself and distinguishes amongst your environments (for example, Jebbit_Prod, Jebbit_Staging, Jebbit_Dev).
Click Add Source to save your settings.
Send an email to Jebbit's Support team after gathering the required credentials to start the integration process.

Events

The table below lists events that Jebbit sends to Segment. These events appear as tables in your warehouse, and as regular events in other Destinations.

Event Name	Description
Survey Completed	Experience was completed

Event properties

The table below list the properties included in the events listed above.

Property Name	Description
`email`	The email address provided by the user.
`client_user_id`	Optional. An ID the Client passes in the Jebbit Experience URL that Jebbit can then pass back with the data for that user.
`experience_date`	Timestamp representing the date the user engaged with the Jebbit Experience (UTC).Default is YYYY-MM-DD HH:MM:SS
`campaign_name`	Client generated name of the campaign
`opt_in`	User opt-in if Client chooses to use the opt_in feature in their Jebbit Experience.
`outcome`	The outcome tied to the user session. Outcomes offer a way to collect a data point based on multiple questions/input. For more information on outcomes, please contact your Account Manager.
`url_param`	Any URL parameters attached to the Jebbit Experience URL.
favorite_color* (example)	Client defined attribute mapped to the experience.
age_group* (example)	Client defined attribute mapped to the experience.

How Jebbit sends data to Segment

Jebbit sends user data to Segment by triggering an identify call for each user completing an experience to be created, for example:

1{
2  "context": {
3    "externalIds": [
4      {
5        "collection": "users",
6        "encoding": "none",
7        "id": "",
8        "type": "emailSha256Hash"
9      }
10    ]
11  },
12  "timestamp": "", //EXPERIENCE_DATE
13  "traits": {
14    "email": "", //USER EMAIL ADDRESS
15    "emailSha256Hash": "",
16    "attribute_1": "" //ALL MAPPED ATTRIBUTES
17  },
18  "type": "identify",
19  "userId": ""
20  }

In order to record actions that a user has completed, Jebbit triggers a Track Call for each user to completes an experience.

1{
2  "context": {
3    "externalIds": [
4      {
5        "collection": "users",
6        "encoding": "none",
7        "id": "",
8        "type": "emailSha256Hash"
9      }
10    ]
11  },
12  "event": "Survey Completed",
13  "timestamp": "", //EXPERIENCE_DATE
14  "properties": {
15    "questions":{
16    "attribute_1": "" //ALL MAPPED ATTRIBUTES
17    },
18    "surveyId": "", //CAMPAIGN ID
19    "surveySessionId": "", //SESSION ID
20    "surveyTitle": "", //CAMPAIGN NAME
21    "trafficSource": "" //SOURCE 
22  },
23  "type": "track",
24  "userId": ""
25}

Now that the Source is configured, you can connect it with Destinations.

Log into your downstream tools and check to see that your events appear 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 there are any issues with how the events are arriving to Segment, contact the Jebbit support team.