Migrate conversion sources management from the Content API for Shopping

Page Summary

outlined_flag

• Merchant Center conversion sources provide insights into conversions from free listings and your website within your merchant account.

• The Merchant API enables management of these conversion sources, offering a more streamlined approach compared to the Content API.

• This migration guide details key changes in requests, methods, and resources when transitioning from the Content API to the Merchant API for conversion source management.

• Notable changes include URL and identifier structures, method functionalities, and resource attribute naming conventions.

• Refer to the provided tables for a comprehensive comparison of the Content API and the Merchant API functionalities for conversion source management.

Merchant Center conversion sources let you view conversion data from free listings , and from your website , in your Merchant Center account. The Merchant API lets you manage conversion sources for your Merchant Center account. For more information, see Manage conversion sources .

This page describes how you can migrate conversion sources management from Content API to Merchant API.

Requests

Here's a sample comparison of the Content API for Shopping to the Merchant Conversion Sources API for conversion sources requests:

	Content API	Merchant API
URL	GET https://shoppingcontent.googleapis.com/content/v2.1/ {MERCHANT_ID} /conversionSources/ {CONVERSIONSOURCE_ID}	GET https://merchantapi.googleapis.com/conversions/v1/ {NAME}
Identifiers	{MERCHANT_ID} /conversionSources/ {CONVERSIONSOURCE_ID}	{NAME}

Methods

Here is what has changed for conversion sources methods in the Conversion Sources API:

Method	URL in Content API for Shopping	URL in Merchant API	Identifiers in Content API for Shopping	Identifiers in Merchant API	Description
create	POST https://shoppingcontent.googleapis.com/content/v2.1/ {MERCHANT_ID} /conversionSources	POST https://merchantapi.googleapis.com/conversions/v1/accounts/ {PARENT} /conversionSources	{MERCHANT_ID}	{PARENT}	In Merchant API, propertyName is called property .
update	PATCH https://shoppingcontent.googleapis.com/content/v2.1/ {MERCHANT_ID} /conversionSources/ {CONVERSIONSOURCE_ID}	PATCH https://merchantapi.googleapis.com/conversions/v1/accounts/ {CONVERSIONSOURCE_NAME}	{MERCHANT_ID} /conversionSources/ {CONVERSIONSOURCE_ID}	{CONVERSIONSOURCE_NAME}	In Merchant API, destinationId is called destination .
delete	DELETE https://shoppingcontent.googleapis.com/content/v2.1/ {MERCHANT_ID} /conversionSources/ {CONVERSIONSOURCE_ID}	DELETE https://merchantapi.googleapis.com/conversions/v1/accounts/ {NAME}	{MERCHANT_ID} /conversionSources/ {CONVERSIONSOURCE_ID}	{NAME}	In Merchant API, attributionLookbackWindowInDays is called attributionLookbackWindowDays . In Merchant API, includeInReporting is called report .
undelete	POST https://shoppingcontent.googleapis.com/content/v2.1/ {MERCHANT_ID} /conversionSources/ {CONVERSIONSOURCE_ID} :undelete	POST https://merchantapi.googleapis.com/conversions/v1/accounts/ {name} :undelete	{MERCHANT_ID} /conversionSources/ {CONVERSIONSOURCE_ID}	{NAME}	URL and identifiers are different in Merchant API. The Conversion Sources API returns ConversionSource instead of Empty .
get	GET https://shoppingcontent.googleapis.com/content/v2.1/ {MERCHANT_ID} /conversionSources/ {CONVERSIONSOURCE_ID}	GET https://merchantapi.googleapis.com/conversions/v1/accounts/ {NAME}	{MERCHANT_ID} /conversionSources/ {CONVERSIONSOURCE_ID}	{NAME}	URL and identifiers are different in Merchant API.
list	GET https://shoppingcontent.googleapis.com/content/v2.1/ {MERCHANT_ID} /conversionSources	GET https://merchantapi.googleapis.com/conversions/v1/ {PARENT} /conversionSources	{MERCHANT_ID}	{PARENT}	URL and identifiers are different in Merchant API.

Resources

The following table mentions the changes in conversion sources resources in the Conversion Sources API:

Content API for Shopping	Merchant API	Description
googleAnalyticsLink: { property_id: int64, attributionSettings: object, propertyName: string }	googleAnalyticsLink: { propertyId: int64, attributionSettings: object, property: string }	In Merchant API, propertyName is called property .
merchantCenterDestination: { destinationId: string, attributionSettings: object, displayName: string, currencyCode: string }	merchantCenterDestination: { destination: string, attributionSettings: object, displayName: string, currencyCode: string }	In Merchant API, destinationId is called destination .
attributionSettings: { attributionLookbackWindowDays: int32, attributionModel: object, repeated conversionType: { name: string, includeInReporting: bool } }	attributionSettings: { attributionLookbackWindowDays: int32, attributionModel: object, repeated conversionType: { name: string, report: bool } }	In Merchant API, attributionLookbackWindowInDays is called attributionLookbackWindowDays . In Merchant API, includeInReporting is called report .