A few months ago we announced Amperity Bridge for outbound sharing. This let you share Amperity data with Databricks without replication using Delta Sharing.

We are pleased to announce that sharing from Databricks is now generally available to all customers! In combination with outbound sharing, Amperity now offers a full Lakehouse CDP integration experience with Databricks via Bridge.

Advantages of Amperity Bridge:

Read more about our Lakehouse CDP and Amperity Bridge announcement here and learn how to start using Amperity Bridge in docs.

We are constantly updating our offline conversion APIs (CAPI) to make it easier for you to send offline events to destinations that support them. These CAPIs help you accurately understand the in-store revenue your digital ads drove by connecting offline transaction data to ad platforms in real time.

Here is our current list of offline conversion APIs:

Read more in our documentation here.

The product team is excited to announce an updated user experience for new Core Tables in the Customer 360 tab that makes it easier to delve into SQL queries and provides more flexibility to create core tables with custom SQL.

First, . Now you can easily access Core Tables directly along with your existing Profile and Databases information. This new view makes it easier to review data and delve into SQL queries right within the Customer 360 tab, making it easier to inspect and validate SQL code to identify and resolve performance issues.

Second, from the , you can create your own Custom core tables with custom SQL that references any upstream tables, such as source domain tables, custom domain tables, stitch outputs, or existing core tables. This makes it easier to reuse tables across multiple databases if you have multiple brands or operate in multiple regions.

To learn more, check out the article about core tables in the Amperity Docs.

We’re thrilled to announce the launch of the new Amperity API! This marks a significant milestone in our commitment to enhancing the connectivity and flexibility of our platform. With the introduction of our public-facing API, developers and businesses can now seamlessly integrate their systems with Amperity, unlocking new possibilities for data management and customer insights.

Our initial API release includes three endpoints:

By integrating Amperity to other tools and platforms through the Open API, you can now:

This is just the beginning. We are actively developing additional endpoints and functionalities to expand the capabilities of the Amperity API. Our goal is to provide a comprehensive suite of tools that empower you to make the most of your data.

Visit our API documentation to learn more about how you can start integrating today. Our team is here to support you every step of the way, ensuring you can maximize the benefits of our platform.

We are excited to announce , a new feature that lets users share data with a Data Lakehouse without replication, allowing Amperity's AI-powered components to enhance lakehouse data. It uses each lakehouse’s open, industry-standard data formats so that data in either the Data Lakehouse or Amperity can be accessed directly. This optimizes costs and prevents unnecessary network calls and processing.

Advantages of Amperity Bridge:

These updates turn Amperity into what we’re calling a — a CDP plugged directly into a Data Lakehouse to take advantage of its open format, so users can easily share customer data among tools and platforms without having to copy data or build and manage connections.

Read more about our Lakehouse CDP and Amperity Bridge announcement here and learn how to start using Amperity Bridge in docs.

In the coming months, we will introduce more enhancements to Amperity Bridge, including sharing data from Databricks to Amperity, which is now in beta [Please reach out to your Account Manager if you're interested in joining]. We will also be introducing data sharing with Snowflake soon.

We're excited to announce revenue trees within segments! You can now view and quickly understand different revenue aspects for all segments within Amperity at a glance.

To view go to the Segments Tab and select any segment. You will see a revenue tree on the Summary tab.

We recently introduced the ability for campaigns to send audience lists as a single file. Our team is constantly looking for ways to improve your experience across the stack, and this update makes managing audiences in downstream systems much easier.

Each separate audience file sent to certain downstream apps requires its own separate list and workflow to be built. For campaigns with multiple sub-audiences, this generated multiple lists and additional work. Now a single file can be sent with all sub-audiences.

This functionality can be enabled in the "Edit Data Template" modal under the new "Campaign Settings" section. Once the data template is configured with the new setting, any campaigns that use it will aggregate any audience lists going to that destination before orchestrating it out.

Now users can filter by destination and status on the campaigns tab! In addition to the existing name and cadence filters, the additional filters provide an easier view of campaigns by destination and status and help users find the correct campaign quickly.

Couriers for PGP-encrypted files were recently updated to use the updated courier experience. You can select PGP-encrypted files, sample them, and we’ll even infer their file fields. Simply set up a filesystem courier like Azure Blob, S3, or SFTP, select your encrypted file, and add your PGP credentials.

We recently introduced a new UI for configuring Merged Customers via a template. There is now a new build mode within the Database Table editing experience called "Visual Template" in addition to the existing “Passthrough” (no configuration) and “Custom” (manual SQL logic or imported SQL logic via table template) options.

Currently, the only template is “Merged_Customers." Upon selecting “Merged_Customers,” you will be able to use the new UI to complete all required configurations. This is a no-code way to configure the following settings for Merged Customers:

This form saves implementers time and makes the C360 experience more accessible to all users.