Skip to main content

Overview

There are two fundamental ways to get data into Unify:
  • Sending events — Real-time signals from websites and products (page visits, user actions, identity information)
  • Syncing object records — Structured data from CRMs, warehouses, databases, APIs, and other systems (product users, subscriptions, enrichment data)
Events and records often come from different sources, but they serve the same overall purpose of connecting all of the data relevant to your go-to-market operations in one place.

Sending events

Events are the real-time behavioral signals that power intent-based workflows in Unify. They capture what visitors and users are doing on your website or in your product and link that activity to Companies and People.

Example use cases

  • You want to identify companies visiting your marketing website (IP reveal)
  • You want to track product usage to trigger sales plays (PLG motions)
  • You want to capture form fills, logins, or other user interactions
  • You want real-time or near-real-time signals to power automations

Choosing an event source

The right way to send events depends on what tools you already have deployed.

Marketing websites

For marketing websites, blogs, docs sites, and other public-facing pages, the goal is typically to capture page visits and identify visitors.

Web applications (product usage)

For SaaS products and web applications, the goal is typically to track user actions (feature usage, paywall hits, milestones) and identify logged-in users.

Backend and server-side events

Some events originate from backend systems rather than browsers—for example, a subscription renewal, a usage limit being hit, or a derived milestone like “onboarding completed.”
Server-side events complement client-side tracking—but they are typically not a replacement. Client-side events provide session context, attribution data, and browser-based identity. Server-side events cover backend-only actions and provide resilience against ad blockers.

Quick reference: event ingestion methods

Syncing records

Records are the structured, persistent data that populates objects in Unify. While events capture what’s happening right now, records represent what Unify knows—companies, people, CRM data, product users, subscriptions, and more.

Example use cases

  • You want to sync CRM data from Salesforce or HubSpot
  • You have product usage data modeled in a data warehouse (e.g., a users table in BigQuery or Snowflake)
  • You want to bring in business data like subscriptions, contracts, or usage tiers
  • You have enrichment data from a third-party tool

Choosing a sync method

Model your data as objects. Rather than adding lots of custom attributes directly to the Company or Person objects, create dedicated custom objects (e.g., Product User) and link them to Person or Company with reference attributes. This keeps your data organized and makes it easy to filter based on data source.
For a step-by-step walkthrough, see Connect a data system.

CRM data

If you use Salesforce or HubSpot, Unify has native integrations that sync CRM data automatically. This is managed through the Unify UI—no developer setup is required.

Salesforce

Connect your Salesforce instance.

HubSpot

Connect your HubSpot CRM.
When you connect a CRM, Unify creates objects (like Salesforce Account or HubSpot Contact) that are linked to the Company and Person objects. CRM data flows bidirectionally and stays in sync.

Combining data sources

Many teams use multiple data sources together. For example:
  • Website Tag on the marketing site for anonymous visitor identification
  • PostHog integration in the product for usage events
  • Hightouch to sync product user records from the data warehouse
  • Salesforce integration to keep CRM data in sync
Events and records complement each other. Events provide real-time behavioral signals. Records provide structured context. Together, they give Unify the full picture it needs to power targeted, timely go-to-market actions.

Next steps

Connect website traffic

Get started with marketing website tracking.

Connect product usage data

Track in-app user behavior and product signals.

Connect a data system

Sync structured data from warehouses and databases.

Send records via API

Push data programmatically from custom pipelines.