Introduction

Datafly Signal Documentation

Welcome to the Datafly Signal documentation. Signal is a server-side tag management platform that replaces client-side vendor tags with a single lightweight JavaScript collector, sending events to your own server endpoint for server-to-server delivery to vendor APIs.

Why Signal?

  • First-party data collection — all data flows through your own subdomain
  • No third-party JavaScript — improved page performance, no ad blocker interference
  • Server-side delivery — better data quality, consent enforcement, PII handling
  • Single deployment per customer — complete data isolation

Quick Links

Quick StartDatafly.js SDKIngestion APIIntegrationsIdentityManagement API

Architecture Overview

Browser → Datafly.js (under 8KB) → Customer's subdomain endpoint
  → Ingestion Gateway → Kafka (raw-events)
  → Event Processor (Org Layer → Pipeline Engine)
  → Kafka (delivery-{integration_id})
  → Delivery Workers → Vendor APIs (server-to-server)

Components

ComponentDescription
Datafly.jsLightweight client-side collector (under 8KB gzipped)
Ingestion GatewayHTTP endpoint receiving events from all sources
Event ProcessorTwo-layer processing: Org Data Layer → Pipeline Engine
Delivery WorkersPer-vendor formatters with retry and rate limiting
Identity HubCross-domain identity resolution
Management APIREST + WebSocket API for configuration and real-time debugging
Management UIAdmin dashboard for source, integration, and pipeline management

Supported Integrations

Signal supports server-to-server delivery to these vendors:

VendorAPIStatus
Google Analytics 4Measurement ProtocolGA
Meta / FacebookConversions APIGA
Google AdsEnhanced ConversionsGA
TikTokEvents APIGA
PinterestConversions APIGA
SnapchatConversions APIGA
LinkedInConversions APIGA
The Trade DeskReal-Time ConversionsGA
Custom WebhookConfigurableGA
BigQueryStreaming InsertGA
SnowflakeSnowpipePlanned
Amazon S3PUTPlanned
RedshiftCOPYPlanned
Overview