Databricks is a data and AI platform for analytics, data engineering, and machine learning. Here, Unity Catalog controls the customer tables shared with Amperity through OpenSharing. Amperity uses the available records to resolve customer identity and prepare audiences for delivery to Meta Ads Manager.

Databricks to Meta

Q: What is Meta Ads Manager?

Meta Ads Manager is the tool advertisers use to configure campaigns across supported Meta placements, including Facebook and Instagram. Customer-list Custom Audiences help advertisers reach or exclude matched customers. Amperity supplies audience data; the media team manages targeting, creative, placements, budget, and campaign decisions in Meta.

Q: How do I send Databricks customer data to Facebook audiences?

Share selected Databricks tables with Amperity through an inbound Bridge, define the customer audience, and send mapped identifiers through the Meta Ads Manager destination. The outbound connector uses the Facebook Marketing API. This activation route is separate from importing Meta advertising reports into Databricks for analysis.

Q: Which customer identifiers can I send to Meta?

The documented mappings include Amperity ID to EXTERN_ID, email to EMAIL, and phone to PHONE, alongside other supported customer fields. Follow the exact requirements for the selected query or campaign path. Amperity applies documented normalization and hashing, while source quality and Meta matching still affect the resulting audience.

Q: How does Meta process audience updates?

The connector replaces audience membership with the list sent from Amperity using Replace Users. Amperity documentation allows up to 24 hours after sending completes for updates to become available. Verify the resulting audience before campaign use; configuring ad-set exclusions or changing ad targeting is a separate step.

Build Meta Custom Audiences from Databricks customer tables through Amperity, using Unity Catalog OpenSharing inbound, identity resolution and audience selection in Amperity, and the Facebook Marketing API outbound to Meta Ads Manager.

Meta Ads Manager docs Databricks Bridge docs

How to send Databricks data to Meta

Share curated Databricks tables. Configure a Unity Catalog share and open-sharing recipient for the inbound Amperity Bridge.
Choose the customer audience. Resolve identity in Amperity and use available transaction, return and customer records to define eligibility.
Update the Meta audience. Send mapped customer identifiers through the Meta Ads Manager destination, then review the audience before configuring advertising.

Prepare Meta audiences from curated Databricks tables

Build purchaser Custom Audiences using available net-purchase history.

Create service-area Custom Audiences from available customer locations.

Refresh named Custom Audiences as selection criteria change.

Prepare customer exclusion audiences for Meta ad-set configuration.

What the Databricks to Meta connection supports

Audience or field	Mapping and behavior	Documentation
Named audience	Set account ID and a unique audience name; Amperity creates the audience if absent.	Amperity docs; Vendor reference
Customer identity	Map amperity_id to EXTERN_ID; complete the required mapping for your query or campaign path.	Amperity docs; Vendor reference
Contact keys	EMAIL and PHONE are examples, not the full required mapping; follow the selected path’s field and hashing rules.	Amperity docs; Vendor reference
Membership	Replace Users replaces the existing membership with the sent customer list.	Amperity docs; Vendor reference
Source declaration	Select user-provided, partner-provided, or both as the customer file source.	Amperity docs; Vendor reference

Use curated customer records to qualify Meta audiences

Distinguish purchases from returned orders

When transaction and return records are available in Amperity, define the purchaser audience around the relationship your team wants to recognize. Send the resulting identifiers to Meta so follow-up targeting can use that selection rather than treating every recorded order as a retained purchase.

Prepare audiences for a service area

Use available customer location records to select people associated with a defined service area. Deliver a named Custom Audience to Meta, where the media team reviews the matched audience and separately configures placement, location targeting and campaign settings.

Set up the Databricks to Meta 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.

Authorize Meta through OAuth, accept its Custom Audience terms, and set account ID, audience name and customer file source. Confirm data-use permissions, the complete required mapping and a sandbox sample before production; replacement affects existing membership. Follow the Meta Ads Manager setup.

Databricks to Meta integration FAQs

What is Databricks?

What is Meta Ads Manager?

How do I send Databricks customer data to Facebook audiences?

Which customer identifiers can I send to Meta?

How does Meta process audience updates?

Put customer context to work in Meta

Explore how customer purchase and location context can inform your next Meta audience.

Get a demo