Skip to content

Connections

Connections is graph8’s data pipeline. It collects events from your website, transforms them with custom functions, and routes them to destinations — webhooks, data warehouses, JavaScript tags, and external connectors.

How It Works

Events flow through a simple pipeline:

  1. Streams collect events from your website or app (page views, form submissions, custom events)
  2. Functions transform or filter events in transit using custom JavaScript
  3. Destinations receive the processed events (webhooks, warehouse, tags, connectors)
  4. Links define which streams connect to which destinations, with routing rules

Streams

A stream is a data source — typically your website. Each stream has:

FieldWhat It Does
NameLabel for the data source (e.g., “Website”, “Mobile App”)
DomainsAllowed source domains for CORS validation
Browser keyPublic write key for the JavaScript SDK
Server keyPrivate key for server-side event tracking

When you set up graph8, a default “Website” stream is created automatically with browser and server keys.

Event Types

Streams accept standard event types:

EventWhat It Tracks
pagePage views with URL, referrer, and page metadata
trackCustom events (e.g., button clicks, signups)
identifyUser identification with traits
groupAccount/company grouping
form_submissionForm fills captured from your website

Destinations

Destinations are where events are sent after collection and transformation.

Destination Types

TypeWhat It Does
WebhookHTTP POST event payloads to any URL
TagInject JavaScript into the page for client-side integrations
WarehouseBatch events to a data warehouse for analytics
ConnectorExternal connectors for data sync

Default Destinations

When you set up Connections, graph8 creates several destinations automatically:

DestinationTypePurpose
IdentifyTagVisitor identification pixel — resolves anonymous visitors to companies
ChatTagWeb chat widget script
Form TrackerTagCaptures form submissions from any form on your site
Campaign Visitor TriggerWebhookTracks campaign link clicks and associates them with contacts
Forms SyncWebhookSends form submissions to graph8 for contact creation
TailorTagWebsite personalization engine
WarehouseWarehouseEvent storage for analytics (optional)

Custom Destinations

Add your own destinations to route events wherever you need:

  • Webhook destinations — send events to any HTTP endpoint
  • Tag destinations — inject custom JavaScript (analytics, pixels, chat widgets)
  • Connector destinations — sync data to external databases and SaaS tools

Functions

Functions are custom JavaScript that transform events in transit. Use them to:

  • Filter — drop events that don’t meet criteria
  • Enrich — add data to events before they reach a destination
  • Transform — reshape event payloads to match destination expectations
  • Route — conditionally send events to different destinations

graph8 includes built-in functions for common tasks like campaign visitor filtering and form submission processing.

Links connect streams to destinations. Each link defines:

SettingWhat It Controls
SourceWhich stream sends events
DestinationWhere events are routed
FunctionsWhich transformation functions to apply
Event filterWhich event types to forward
Host filterWhich source domains to accept

For sync-type links, you can also configure:

  • Schedule — sync frequency
  • Timezone — scheduling timezone
  • Table prefix — naming convention for destination tables

Syncs

Syncs enable bidirectional data transfer with external systems. Configure:

  • Which data streams to sync
  • Sync schedule
  • Destination table naming

Live Events

Monitor your event pipeline in real time:

  • View incoming events as they arrive
  • Inspect event payloads and metadata
  • Debug routing and transformation issues
  • Verify that destinations are receiving data

Campaign Tracking

Connections powers campaign attribution automatically. When a prospect clicks a campaign link:

  1. The URL contains a campaign hash identifying the sequence step and contact
  2. The graph8 tracking script captures the page view with the hash
  3. The Campaign Visitor Trigger destination sends the event to graph8
  4. graph8 links the visit to the correct contact and sequence step

This happens automatically — no manual setup required beyond having Connections installed on your site.

Next Steps