Databricks is a data and AI platform that supports analytics, data engineering, and machine learning. In this connection, Unity Catalog controls the tables shared with Amperity through OpenSharing. Amperity uses available customer data to resolve identity and prepare first-party audiences for The Trade Desk.

Databricks to The Trade Desk

Q: What is The Trade Desk?

The Trade Desk is a demand-side advertising platform used to plan and buy digital media, including display, video, connected TV, and audio. This connection supplies first-party audience segments from Amperity. The media team manages campaign settings and advertising decisions in The Trade Desk.

Q: How does Databricks connect to The Trade Desk through Amperity?

An inbound Amperity Bridge accesses tables shared from Databricks. Amperity resolves customer identity and builds the selected audience, then sends supported identifiers through The Trade Desk destination API. The sharing connection and outbound audience delivery are separate steps; the workflow is not entirely copy-free.

Q: Can I send UID2, EUID, or phone-based audiences?

Yes, with the documented prerequisites. Use uid2 when Amperity is configured as your brand’s UID2 Operator, and euid when your brand participates in EUID. Phone numbers must use E.164 format and can be sent for rows without email. Confirm applicable agreements and the configured identifier path.

Q: How quickly are audience updates available in The Trade Desk?

Allow up to 48 hours after Amperity finishes sending audience updates for them to become available in The Trade Desk. Coordinate the Databricks Bridge workflow and delivery schedule, and set membership duration at least as long as the interval between sends. Validate a sample before production.

Turn customer history in Databricks into first-party audiences for The Trade Desk through Amperity, using OpenSharing inbound, identity resolution and segment selection in Amperity, and The Trade Desk API outbound.

See The Trade Desk docs Databricks Bridge docs

How to send Databricks data to The Trade Desk

Share Databricks tables. Configure a Unity Catalog share and an open-sharing recipient for the inbound Amperity Bridge.
Build customer segments. Resolve identity and select eligible customers using history and attributes available in Amperity.
Deliver first-party audiences. Configure The Trade Desk destination, review identifier mappings, and send to a named segment.

Prepare first-party segments for The Trade Desk

Build high-value customer segments using available purchase history.

Prepare category-buyer audiences for relevant media campaigns.

Include phone-only customers in first-party segments when email is unavailable.

Prepare UID2 or EUID segments for eligible, configured accounts.

What the Databricks to The Trade Desk connection supports

Audience or field	Mapping and behavior	Documentation
Named segment	Set Segment name for the advertiser account receiving the audience.	Amperity docs; Vendor reference
Email	Map email to email for the customer audience.	Amperity docs; Vendor reference
Phone fallback	Map phone to phone when email is unavailable; use E.164 format.	Amperity docs; Vendor reference
UID2 and EUID	uid2 requires Amperity UID2 Operator configuration; euid requires EUID participation.	Amperity docs; UID2 reference
Membership duration	Default 90 days; maximum 180. Set at least the send interval; 0 removes all members.	Amperity docs; Vendor reference

Make Databricks customer history useful for media teams

Prioritize valuable customer relationships

Use transaction history shared from Databricks to define a high-value customer segment in Amperity. Send supported identifiers to The Trade Desk so the media team can consider that audience when planning its advertising.

Keep category audiences distinct

Create separate segments for customers who purchased different product categories, using history available in Amperity. Give each destination segment a clear name, then review audience availability and membership duration before the media team selects it for a campaign.

Set up the Databricks to The Trade Desk workflow

Enable OpenSharing on the Unity Catalog metastore, configure the share and recipient, and securely provide the credential file for Amperity Bridge. Verify table permissions and any Azure storage firewall requirements. Follow the Databricks Bridge setup.

Configure the advertiser ID and secret, applicable UID2 or EUID agreements, and segment name. Set membership duration to cover the send interval and validate a sample in a sandbox before production. Follow The Trade Desk destination setup.

Databricks to The Trade Desk

How to send Databricks data to The Trade Desk

Prepare first-party segments for The Trade Desk

What the Databricks to The Trade Desk connection supports

Make Databricks customer history useful for media teams

Prioritize valuable customer relationships

Keep category audiences distinct

Set up the Databricks to The Trade Desk workflow

Databricks to The Trade Desk integration FAQs

What is Databricks?

What is The Trade Desk?

How does Databricks connect to The Trade Desk through Amperity?

Can I send UID2, EUID, or phone-based audiences?

How quickly are audience updates available in The Trade Desk?

Put customer context to work in The Trade Desk