Skip to main content

Conversions API Destinations and Distribution Information

You can distribute CAPI event feed views to Conversions API program destination accounts to attribute transactions/events to online advertising on those platforms. See the sections below to learn which CAPI programs are available as destinations in Connect and the required credentials for each.

Available Destinations for Conversions API Programs

The following table lists all available CAPI destination accounts that can receive CAPI event feed views. In most cases, each CAPI program would have separate destinations for online and offline events. Make sure to find the correct destination by referring to the 'Integration Tile Name' column.

Note

For online event feeds, you only need to distribute feeds to destinations when you want to deliver brand- or SKU-specific views to platforms, such as in a retail use case. Without filtering applied (via view creation), online event data is sent directly to enabled platforms through the Online Conversions API integration in Console.

To learn more, see "Online Conversions API Connectors".

Platform

Event type

Integration Tile Name

Account Info Needed

Requires OAuth in Connect

Amazon

Offline

Amazon CAPI V2 - Offline - NA Non Product Array

  • Amazon Ads account ID

Yes

Amazon CAPI V2 - Offline - EU Non Product Array

  • Amazon Ads account ID

Yes

Amazon CAPI V2 - Offline - APAC Non Product Array

  • Amazon Ads account ID

Yes

Google Campaign Manager 360

Offline

Campaign Manager 360 Conversions API LR1 Product Array

No

Campaign Manager 360 Conversions API LR1 Product Array (Lmt Ad Trk)

No

Campaign Manager 360 Conversions API LR1 Non Product Array

No

OpenAI

Offline

OpenAI Conversions API PII Passthrough

  • Pixel ID

  • Conversions key

No

The Trade Desk

Offline

TTD Conversions API Brand Direct LR1 Product Array

  • TTD advertiser ID

  • Tracking tag ID

No

TTD Conversions API Brand Direct LR1 Non Product Array

  • TTD advertiser ID

  • Tracking tag ID

No

TTD Conversions API 3rd Party Provider LR1 Product Array

  • TTD advertiser ID

  • TTD encryption key (also known as TTD secret key)

  • Provider ID

No

TTD Conversions API 3rd Party Provider LR1 Non Product Array

  • TTD advertiser ID

  • TTD encryption key (also known as TTD secret key)

  • Provider ID

No

Online

TTD Conversions API - Online - Brand Direct Event Feed

  • TTD advertiser ID

  • Tracking tag ID

No

Meta

Offline

Meta Conversions API Offline Non Product Array Passthrough US

  • Access token

No

Meta Conversions API Offline Product Array

  • Access token

No

Meta Conversions API Offline Product Array EU

  • Access token

No

Meta Conversions API Offline Non Product Array US

  • Access token

No

Meta Conversions API Offline Non Product Array UK

  • Access token

No

Online

Meta Conversions API Online LR1

  • Access token

  • Meta ad account ID

No

Netflix

Offline

Netflix Offline Conversions API

  • Netflix ad account ID

No

TikTok

Offline

TikTok - Events API - Offline - EU

  • TikTok ad account ID

Yes

TikTok - Events API - Offline - US

  • TikTok ad account ID

Yes

Online

TikTok - Events API - Online Event Feed

  • TikTok ad account ID

  • Authentication token

No

Pinterest

Offline

Pinterest Events API - Offline Non Product Array

  • Pinterest advertiser ID

No

Pinterest Events API - Offline Product Array

  • Pinterest advertiser ID

No

Online

Pinterest - Conversions API - Online Event Feed

  • Pinterest advertiser ID

  • Authentication token

No

Reddit

Offline

Reddit Offline Conversions API

  • Pixel ID

  • Conversions token

No

Snapchat

Offline

Snap - Offline Conversions API Product Array

  • Snap Pixel ID

No

Snap - Offline Conversions API Non Product Array

  • Snap Pixel ID

No

Online

Snap - Conversions API - Online Event Feed

  • Snap Pixel ID

  • Authentication token

No

Yahoo

Offline

Yahoo - Conversions API - Offline Product Array

  • Yahoo Pixel ID

No

Yahoo - Conversions API - Offline Non Product Array

  • Yahoo Pixel ID

No

Online

Yahoo - Conversions API - Online Event Feed

  • Yahoo Pixel ID

  • Authentication token

No

Activating a Conversion API Program Destination Account

To activate a Conversions API destination account, follow the general instructions in "Activate a New Destination Account”, performing these additional steps:

  1. Remove the end date to leave the end date open-ended.

  2. Under Destination-Specific Settings, enter the required account IDs.

    Note

    For retailers activating online CAPI destinations, enter the same platform credentials provided in Console for your Online CAPI integration. See "Create an Online Conversions API Integration" for more information.

  3. If your destination requires an OAuth authentication, select an existing one from the OAuth Connection dropdown list and click Validate OAuth Connection.

  4. To create a new OAuth connection and validate that connection:

    1. From the OAuth Connection dropdown list, select Create New OAuth Connection.

    2. From the new window that opens with the platform's sign-in or login screen, enter your credentials and then click Sign in.

  5. Click Validate OAuth Connection.

  6. In the Destination Account Name field, pick a unique and memorable name for this account. We'll suggest one for you but you can use any name you wish as long as it is less than 50 characters in length.

Once created, the destination account displays on the Destination Accounts page with the status 'Ready' and 'CAPI' as its supported data type.

CAPI_DAs.png

Distributing Conversion API Event Feeds

You can distribute event feeds as tables or as views. When you distribute a table, LiveRamp automatically generates a view for that table to distribute.

Grant your brand partners in LiveRamp access to your filtered conversion event feed views so they can distribute the views on their own, or create child views from them.

  • On the Tables and Views page, click the More Options (more-options-icon.png) menu of an event feed view or table and select "Distribute Event-Feeds".

  • On the Tables and Views page, check the box of the asset that appears to the left side of the row, click More and select "Distribute Event-Feeds".

  • Right after creating a CAPI event feed view, click Distribute Event Feed Views on the pop-up that displays.

  • On the asset’s details page, which can be accessed by double clicking on the asset’s row, click Action and select "Distribute Event-Feeds".

Procedure. To distribute a conversion event feed:

  1. On the Tables and Views page, click the More Options menu (more-options-icon.png) of an event feed asset and select "Distribute Event Feeds".

    CAPIRMN_MoreOptions__DistributeEvent.png

  2. (Optional) Click Previous and select any additional views you want to distribute.

    Click Next.

  3. From the Select Destinations step, check one or more boxes for the CAPI destination accounts you want to distribute the views to.

  4. Click Validate. LiveRamp checks whether your file is missing any fields required by the selected destination platform.

    Click_validate.png

  5. If a row's validation status displays “Incompatible”, hover over the status to see the missing requirement.

    Screenshot_2026-09-07_at_15_24_37.png

    Warning

    If your file is missing a field, you must reupload the file, making sure the required field is included.

  6. When all selected platforms show a validation status of “Compatible”, click Distribute Event-Feeds.

Your partner receives an email notifying them that your organization has shared the view. In your partner's account, the event feed view's Ownership column displays Partner Data (second-party-data-icon-01.png ) with your organization listed as the owner.

Additional Information for Google Campaign Manager 360 CAPI Destination Account

Activating a Google Campaign Manager 360 CAPI destination account requires you to provide a new, or existing Floodlight activity ID. You must also provide LiveRamp’s access profile ID by granting LiveRamp users access in your Campaign Manager 360. 

See the sections below for complete instructions.

Create Floodlight Activities

To create a Floodlight activity in Campaign Manager 360:

  1. From the navigation menu, select All advertisers and click on the desired advertiser name.

  2. Create a new Floodlight activity group:

    1. From the navigation menu, select Floodlight and then select Activity groups.

      GCM_Conversions-Floodlight_Activities-Activity_Groups_menu_selection.png

    2. Click New.

    3. Fill out the required fields.

    4. Click Save.

  3. Create a new Floodlight activity:

    1. From the navigation menu, select Floodlight and then select Activities.

      GCM_Conversions-Floodlight_Activities-Activites_menu_selection.png

    2. Click New.

    3. Fill out the required fields and then click Save.

      GCM_Conversions-Floodlight_Activities-Activites_fields.png

      Note

      To match transactions to impressions or clicks, make sure the Counting method of your Floodlight activity is set to "Counter activities".

Follow the same process (apart from selecting the advertiser name) to create additional Floodlight activities.

Note

Typically, a maximum of five Floodlight activities can be used with the LiveRamp integration. Contact LiveRamp to create additional audiences if you use more than one Floodlight activity. Talk to your LiveRamp representative if more than five Floodlight activities are needed for your situation.

Grant LiveRamp User Access in Campaign Manager

This step will grant LiveRamp access to insert offline conversion data into your Campaign Manager 360 account. The permission given will only allow LiveRamp to insert offline conversions via the API.

Tip

Save the ID: Once you’ve created a new user profile for LiveRamp, record the LiveRamp Access Profile ID so you can send it to us in a later step.

To grant access in Campaign Manager 360:

  1. Create a new user role:

    1. From the navigation menu in Campaign Manager 360, select Admin and then select User roles.

      GCM_Conversions-Grant_Access_User_roles_menu_selection.png

    2. From the User Roles page, click New.

      GCM_Conversions-Grant_Access_User_roles_New_button.png

    3. In the “User role name” field, enter “Offline API Access”.

      GCM_Conversions-Grant_Access_User_roles_name.png

    4. In the “Source user role” field, select “Advertiser/Reporting Login”.

      GCM_Conversions-Grant_Access_Source_User_role.png

    5. In the Reporting section, uncheck all check boxes and check the check boxes for “Insert offline conversions” and "Update offline conversions".

      Google_DV360_UserRole_reporting.png

    6. Click Save.

      GCM_Conversions-Grant_Access_User_roles_Save_button.png

  2. Create a new user profile:

    1. From the navigation menu, select Admin and then select User profiles.

    2. From the User Profiles page, click New.

    3. Enter the following information:

      • Email: googleauth@liveramp.com

      • Profile name: LiveRampAPIAccess

        Note

        Google might add a number at the end of this name– this is okay.

      • User role: Offline API Access

    4. Click Save.

CAPI Feed Monetization on DV360 via Google for Commerce Media Networks Integration

Retailers who are data sellers can monetize their offline transaction data to select brands on DV360 through LiveRamp’s Google Data Marketplace integration for Commerce Media Networks. To allow Google to associate your CAPI feed with the relevant pricing metadata, you must create a shell (dummy) segment and distribute it to the “Google - Commerce Media” destination tile.

For more information, see “Distribute Data Marketplace Data to Google”.

In this section: