LiveRamp

LiveRamp is the leading independent identity resolution and data collaboration platform, providing the RampID as a privacy-safe, persistent identifier used across the open web and connected TV.

⚠️

This integration is currently in alpha. Configuration and behaviour may change.

Prerequisites

Complete these steps in LiveRamp before configuring Signal.

Engage with LiveRamp

LiveRamp is enterprise-only. Contact LiveRamp for access if you do not already have an account.

Provision your LiveRamp environment

Once your account is provisioned you’ll receive:

A Customer ID identifying your LiveRamp tenant.
Credentials for the Data Onboarding workflow (typically API key + secret for the LiveRamp Data In + LiveRamp Activations APIs).
A Segment ID or Audience ID to target as the destination for your data.

Decide on hashing scheme

LiveRamp matching is deterministic on hashed PII. The supported hash schemes are:

SHA-256 (most common)
SHA-1 (legacy)
MD5 (legacy)

Signal applies SHA-256 by default after lowercasing and trimming. Confirm with your LiveRamp account team which hashing scheme is expected for your audience.

Determine your delivery destination

LiveRamp data can be delivered to multiple touchpoints. The Signal integration writes to LiveRamp’s data onboarding endpoint; from there you can route to:

LiveRamp’s Data Marketplace.
Walled-garden activations (TTD, Google, Amazon DSP, etc.).
Authenticated Traffic Solution (ATS) for first-party RampID resolution.

Configuration

Field	Type	Required	Description
`customer_id`	string	Yes	Your LiveRamp tenant ID.
`api_key`	string	Yes	LiveRamp API key.
`api_secret`	secret	Yes	LiveRamp API secret.
`segment_id`	string	Yes	Destination segment / audience ID.
`hash_scheme`	select	No	`sha256` (default), `sha1`, or `md5`.

Signal Setup

Quick Setup

Navigate to Integrations in the sidebar.
Open the Integration Library tab.
Find LiveRamp under the Identity Resolution category.
Click Install, and fill in the required fields with the credentials gathered above.
Click Install Integration.

API Setup

curl -X POST http://localhost:8084/v1/admin/integration-catalog/liveramp/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "LiveRamp",
    "variant": "default",
    "config": {
      "customer_id": "lr-12345",
      "api_key": "xxxxxxxxxxxxxxxxxxxx",
      "api_secret": "xxxxxxxxxxxxxxxxxxxx",
      "segment_id": "seg-67890",
      "hash_scheme": "sha256"
    },
    "delivery_mode": "server_side"
  }'

Event Mapping

LiveRamp is an identity / audience destination rather than an event analytics destination. Signal delivers identified records (and updates) — not page views and arbitrary behavioural events.

Datafly Event	LiveRamp Concept	Notes
`identify`	Audience record	Hashed PII added/updated in the configured segment.
`Order Completed`	Audience record + value	Order revenue can populate a value-based segment for lookalike modelling.
Other events	Dropped by default	Enable specific events in the blueprint to drive segment membership rules.

Identity

LiveRamp expects pre-hashed PII. Signal applies the configured hash scheme server-side before delivery — raw PII never leaves your environment.

Field	Source	Hashing	Notes
`email_hash`	`traits.email`	Lowercased, trimmed, then hashed	Primary input to RampID resolution.
`phone_hash`	`traits.phone`	Digits only (E.164), then hashed	Secondary input.
`firstname_lastname_zip_hash`	`traits.first_name` + `traits.last_name` + `traits.zip`	Concatenated, normalised, hashed	Offline match fallback for postal data.
`customer_id`	`user_id` from `datafly.identify()`	Plain text	Your stable customer ID — included so you can reconcile back from RampID matches.

LiveRamp data must be sent under the advertising consent category. Visitors who have not granted advertising consent are filtered out by Signal before delivery — LiveRamp never receives their records, so they cannot be targeted by RampID-based audiences.

For regulated regions (UK / EU / California / Quebec), LiveRamp also requires per-record consent flags carried in the audience file; Signal includes the visitor’s CMP consent state alongside hashed PII so LiveRamp can enforce these on its side.

Verify it’s working

After installing, trigger a test identify from a visitor with email + advertising consent.
In LiveRamp’s dashboard, navigate to Connect > Audiences and locate the configured segment. New record counts should appear within an hour (LiveRamp processes onboarding in batches).
For real-time confirmation, check Signal’s Live Events for a 200 response from the LiveRamp endpoint.

Troubleshooting

Symptom	Possible Cause	Resolution
`401 Unauthorized`	Invalid API key or secret	Re-issue credentials in LiveRamp’s admin panel and update the integration config.
`403 Segment not accessible`	Segment ID not authorised for this customer	Confirm with your LiveRamp account manager that the segment is provisioned for your Customer ID.
Low match rate	Hashing mismatch	Both sides must use the same hash scheme + normalisation. Confirm SHA-256 lowercased+trimmed is acceptable, or switch to LiveRamp’s required scheme.
Audience size not growing	Records below match threshold	LiveRamp matching requires a minimum population for some destinations. Increase volume or broaden the identifier set sent per record.
Consent-related rejections (EU)	Missing per-record consent flags	Ensure your CMP integration is publishing consent state to Signal before delivery.

Visit LiveRamp documentation for full API reference, audience onboarding details, and the Authenticated Traffic Solution (ATS) guide.