Skip to main content

Announcement: A New Conversions API Hub Experience to Simplify New CAPI Program Setup (4/9/2025)

You can now capture and send web conversions and event data to subscribed Conversions API platforms for optimization and measurement in a new streamlined experience in LiveRamp’s enhanced Conversions API Hub.

LiveRamp’s enhanced Conversions API Hub simplifies setup and configuration for web signal data feeds into one streamlined process across all online CAPI programs (e.g., Meta, TikTok, Pinterest, Snap). This will reduce initial setup time and engineering/tech burdens while accelerating speed-to-value—especially when you want to add new Online CAPI program connectors.

universal_CAPI_GRAP.png

Main Benefits of the Enhanced CAPI Hub

The simplified setup and workflow reduce initial setup time and eliminate repetitive work, making each new CAPI program you add easier to launch. Key improvements include:

  • Build payloads and configure data layer or event settings once: For each new CAPI platform, you only need to provide the account ID and authentication token from your platform partners in Console — no code updates required.

  • Better data layer detection: For ATS for Web implementation, the enhanced data layer detection feature works with any website's data layer (not just Google or Adobe).

  • Single API call for ATS API and server-side users: API users only need to call a single endpoint, which automatically translates event data to all subscribed CAPI programs. This reduces complexity and page weight, as well as simplifying maintenance.

Upgrading Your Existing CAPI Connectors

Due to the difference in framework, to upgrade any existing CAPI implementations, you must manually copy all your previous settings from the old ATS configuration and CAPI integration to a new one.

See "Upgrading Your Conversions API Integrations for Web Conversions and Events" to learn the overall steps and FAQ's.

Note

Reach out to your LiveRamp representative to help you with migrating to the enhanced Online CAPI.

You do not have to migrate to the enhanced CAPI connector if you don’t need access to any new platforms that are not already on the legacy framework.

In this section: