Segment Source
Receive real-time track, identify, group, page, and screen events from Segment into Vendo.
Last reviewed September 15, 2026
Source: Receive real-time events from your Segment workspace into Vendo. Vendo writes track, identify, group, page and screen calls to BigQuery. It can forward them to other Vendo destinations.
How It Works
Vendo appears as a destination in Segment’s catalog. When you enable the Vendo destination in your Segment workspace, Segment forwards all events that match your subscriptions to Vendo in real time.
Your App → Segment → Vendo Destination → Vendo BigQuery + Streaming DestinationsSupported Event Types
| Segment Type | Vendo Event | Description |
|---|---|---|
track | Event name (for example, “Order Completed”) | Custom events with properties |
identify | $identify | User traits (email, name, custom attributes) |
group | $group | Company/account traits |
page | $page:Name | Page views with URL and title |
screen | $screen:Name | Mobile screen views |
Setup
Step 1: Create a Segment Source in Vendo
- In the Vendo app, go to Sources > Add source.
- Select Segment from the source list.
- Give your source a name and click Create.
- Copy the App ID and Endpoint URL. You need these in Segment.
- After you create the source, copy the API Key from the app settings.
Step 2: Configure Vendo as a Destination in Segment
- In your Segment workspace, go to Connections > Destinations > Add Destination.
- Search for Vendo and select it.
- Choose the Segment source you want to connect.
- Enter your Vendo credentials:
- API Key: The API key from Step 1
- App ID: The app ID from Step 1 (included in the endpoint URL)
- Enable the destination.
Step 3: Configure Event Subscriptions
The Vendo destination supports five actions with default subscriptions:
| Action | Default Subscription | What It Does |
|---|---|---|
| Track Event | type = "track" | Forwards all track calls |
| Identify User | type = "identify" | Forwards all identify calls |
| Group User | type = "group" | Forwards all group calls |
| Page View | type = "page" | Forwards all page calls |
| Screen View | type = "screen" | Forwards all screen calls |
You can customize these subscriptions with Segment’s FQL (Filter Query Language) to route specific events.
Platform Details
| Setting | Value |
|---|---|
| Delivery | Real-time streaming |
| Auth Method | API Key (auto-generated) |
| Protocol | HTTPS POST to Vendo pipeline API |
| Deduplication | Segment messageId used as insert ID |
| BigQuery Write | Automatic: events stored in webhook_events table |
| Batch Support | Up to 1,000 events per request |
Data in BigQuery
Vendo writes events to the webhook_events table in your account’s BigQuery dataset:
| Column | Description |
|---|---|
insert_id | Segment messageId (deduplication key) |
event_name | Event type (for example, “Order Completed”, “$identify”) |
timestamp | Event timestamp |
distinct_id | User ID or anonymous ID |
properties | JSON: event properties, traits, or context |
raw_payload | JSON: full original Segment payload |
app_id | Vendo source app ID |
account_id | Vendo account ID |
Verify Setup
- Send a test event from your application or Segment’s Event Tester.
- Check that the Vendo source status shows Active.
- Query your BigQuery
webhook_eventstable to confirm that events arrived. - Check Logs in Vendo for recent activity.
Related
- Segment Destination: Send data FROM Vendo TO Segment