Adding Integrations

Once your first pipeline is running, you’ll want to add more vendor destinations. This guide covers how to install additional integrations, understand the V2 schema-mapping builder, and customise field mappings.

Installing from the Integration Library

The Integration Library includes 120+ pre-built vendor integrations across six categories:

Category	Examples
Advertising	Meta CAPI, Google Ads, TikTok, Pinterest, Snapchat, LinkedIn, The Trade Desk
Analytics	Google Analytics 4, Adobe Analytics, Amplitude, Mixpanel, Heap
Attribution	Adjust, AppsFlyer, AWIN, Impact Radius, Kochava
CDP	Braze, HubSpot, Salesforce CDP, Iterable, Customer.io
Cloud Storage	BigQuery, Snowflake, Redshift, S3, Azure Blob, Kafka
Other	Custom Webhook, Pipeline Router

To install an integration:

Navigate to Integrations in the sidebar, then click Add Integration or switch to the Integration Library tab.
Browse by category or search for a vendor.
Click Install, choose a blueprint if available, fill in credentials, and click Install Integration.
The integration is automatically attached to your pipeline.

Understanding the V2 Schema-Mapping Builder

Every integration’s configuration is managed through the V2 schema-mapping builder. Open it by clicking on an integration from the Integrations page.

The builder has four sections:

Parameters

Connection credentials and shared configuration values. These are typically set during installation and rarely changed:

measurement_id  →  G-XXXXXXXXXX    (static)
api_secret      →  your_secret     (static)

Parameters can also be set at the pipeline level so they’re shared across integrations. Pipeline parameters override integration-level values.

Global Mappings

Fields that are sent with every event to this vendor, regardless of event type. Common examples:

Field	Source	Description
`client_id`	`context.anonymous_id`	The user’s anonymous ID
`user_id`	`user_id`	The identified user ID (when available)
`timestamp_micros`	`timestamp`	Event timestamp in the vendor’s required format
`user_properties`	Various	User traits from `identify()` calls

Event Mappings

Per-event-type field mappings. This is where most of the configuration lives. For each event type you want to send to this vendor, you define:

Source event — which Datafly event triggers this mapping (e.g. purchase, page_view, add_to_cart)
Destination event — what the vendor calls this event (e.g. GA4 expects purchase, Meta expects Purchase)
Field mappings — how each property maps from your canonical event to the vendor’s format

Example for a GA4 purchase event:

Vendor Field	Source	Mode
`params.transaction_id`	`properties.transaction_id`	direct
`params.value`	`properties.value`	direct
`params.currency`	`properties.currency`	direct
`params.items`	`properties.items`	direct (array)

Defaults

Fallback values applied when source data is missing. For example:

Default currency to "GBP" if not present in the event
Default non_personalized_ads to false

Field Mapping Modes

Each field mapping has a mode that determines how the value is resolved:

Mode	Description	Example
direct	Map directly from a source field	`properties.value` → `params.value`
static	Use a fixed value	`"GBP"` → `params.currency`
expression	Compute using an expression	`concat(properties.first_name, " ", properties.last_name)`
hash	SHA-256 hash the source value	Hash `properties.email` for Meta CAPI

Expressions support a SQL-like syntax for concatenation, conditionals, mathematical operations, and more. See Expressions for the full reference.

Adding a Second Integration (Example)

Let’s add Meta Conversions API alongside an existing GA4 integration:

From the Integration Library, search for “Meta” and click Install on Meta Conversions API (CAPI).
Select the Retail blueprint for pre-built e-commerce event mappings.
Enter your Meta credentials:
- Pixel ID — your Meta Pixel ID
- Access Token — a Conversions API access token (generated in Meta Events Manager)
Click Install Integration.

The Meta CAPI blueprint pre-maps events like purchase, add_to_cart, and page_view to Meta’s expected format, including SHA-256 hashing of PII fields (email, phone) as required by Meta’s API.

Each integration runs independently. The same event can be sent to GA4, Meta, TikTok, and any number of other vendors simultaneously, each with its own field mappings and transformations.

Customising Mappings After Install

After installing an integration (with or without a blueprint), you can fully customise the mappings:

Add new event mappings — map additional event types that aren’t in the default blueprint
Edit field mappings — change how fields are mapped, add new fields, or remove ones you don’t need
Add expressions — use computed values for fields that need transformation
Change defaults — override fallback values

All changes are saved as a new revision of the integration template, so you can review changes before they affect live traffic.

Custom Webhook Integration

For vendors not in the library, or for sending events to your own internal APIs, use the Custom Webhook integration:

Install the Webhook integration from the Other category.
Set the endpoint URL to your target API.
Configure field mappings to match whatever payload format your API expects.
Optionally set authentication headers (API key, Bearer token, etc.).

Next Steps

Going Live — Set up your production domain and launch.
Processing — Configure the Org Data Layer for consent, PII handling, and bot filtering.
Expressions — Learn the expression language for computed field mappings.
Event Specs — Industry-standard event schemas for e-commerce, travel, media, and more.

Your First Pipeline Going Live