Use a partner integration that supports the Conversion API
Posted: Wed Jan 22, 2025 6:45 am
Advertisers who use services on the partner integration list can implement the Conversion API with just the settings on the admin screen of Facebook and the partner service.
You can check the list of partner integrations on the following page.
Partner Integrations
However, the above page cannot be viewed without access to Business Manager, so if you do not currently have the permissions, please refer to the following:
About Partner Integration for Web | Facebook Business Help Center
The number of partners listed on each page varies, but generally there are around 50 partners.
Of those, it seems that there are less than 10 partners find investor through investor database that are likely to be commonly used by Japanese advertisers (such as Shopify and Makeshop).
On the other hand, there are some services that are not on the partner integration list but are supported independently. Below are the ones I have found. If you are using these services, please contact the service provider for details.
EC Platform
BASE
LaunchCart
Use Google Tag Manager (server-side container)
Facebook has also officially announced the implementation of the conversion API using the Google Tag Manager server-side container.
Reference: Conversion API for Google Tag Manager - Marketing API
Using this allows for a lighter implementation than developing it from scratch in-house. To use it, you must first implement the server-side container of Google Tag Manager, so please refer to the following:
Server-side tagging | Google Tag Manager - Server side
Information to be sent
Once you have decided on the implementation method, the next thing to decide is what information to send to Facebook through the conversion API.
First, the required parameters for the conversion API are as follows.
*For website events. This does not apply to non-web events (such as phone calls or physical stores).
event_name: Name of the event. Specify a standard event or any event name.
event_time: The date and time the event occurred (UNIX timestamp in seconds, GMT).
action_source: where the event occurred (in this case, it's a website event, so "website")
event_source_url: The URL where the event occurred (must start with http:// or https:// and match the domain where you performed domain authentication)
user_data: Information about the user who generated the event (for website events, the "client_user_agent" field below is required)
client_user_agent: The user agent of the browser that generated the event.
You can check the list of partner integrations on the following page.
Partner Integrations
However, the above page cannot be viewed without access to Business Manager, so if you do not currently have the permissions, please refer to the following:
About Partner Integration for Web | Facebook Business Help Center
The number of partners listed on each page varies, but generally there are around 50 partners.
Of those, it seems that there are less than 10 partners find investor through investor database that are likely to be commonly used by Japanese advertisers (such as Shopify and Makeshop).
On the other hand, there are some services that are not on the partner integration list but are supported independently. Below are the ones I have found. If you are using these services, please contact the service provider for details.
EC Platform
BASE
LaunchCart
Use Google Tag Manager (server-side container)
Facebook has also officially announced the implementation of the conversion API using the Google Tag Manager server-side container.
Reference: Conversion API for Google Tag Manager - Marketing API
Using this allows for a lighter implementation than developing it from scratch in-house. To use it, you must first implement the server-side container of Google Tag Manager, so please refer to the following:
Server-side tagging | Google Tag Manager - Server side
Information to be sent
Once you have decided on the implementation method, the next thing to decide is what information to send to Facebook through the conversion API.
First, the required parameters for the conversion API are as follows.
*For website events. This does not apply to non-web events (such as phone calls or physical stores).
event_name: Name of the event. Specify a standard event or any event name.
event_time: The date and time the event occurred (UNIX timestamp in seconds, GMT).
action_source: where the event occurred (in this case, it's a website event, so "website")
event_source_url: The URL where the event occurred (must start with http:// or https:// and match the domain where you performed domain authentication)
user_data: Information about the user who generated the event (for website events, the "client_user_agent" field below is required)
client_user_agent: The user agent of the browser that generated the event.