Meta Conversions API
If you don’t have a Meta Business Suite account, you’ll need to first create one.
To create a Meta Pixel and enable the Conversions API, you’ll need to be an admin for the Meta Business Suite account. Learn how to set up a Meta Pixel.
To connect your GoFundMe Pro account to the Meta Conversions API, you’ll first need to turn on the Conversions API for your Meta Pixel, and then collect your Meta Pixel ID and Meta Conversions API access key.
Set up the Meta Conversions API
With a direct integration to the Meta Conversions API, you can create a direct (server-side) connection between conversion events on GoFundMe Pro and your Meta Business Suite, allowing you to optimize the donor journey and better target advertising.
Enable the Conversions API in Meta Business Suite
- From the Business Suite Events Manager, select the Pixel you want to associate with the Conversions API
- From the Pixel, select Settings
- Scroll to the Conversions API section
- Underneath Set up manually, select Get Started
- Select the events you want to send through the Conversions API. GoFundMe Pro supports the following events:
- Add to Cart
- Complete Registration
- Initiate Checkout, Purchase
- View Content
Note: Additional and custom event types are not supported at this time.
- Select the event parameters you want to send for the event. See the table below for which parameters GoFundMe Pro supports. You can unselect any parameters you don’t want sent to Meta
- Follow the remaining steps to implement the Conversions API for your selected Pixel
Copy your Meta Pixel ID and API access key
- From the Business Suite Events Manager, select the Pixel associated with the Conversions API
- From the Pixel, select Settings
- From the Details section, select the Pixel ID to copy it to your clipboard
- From the Conversions API section, select Generate access token. The API access key will appear
- Select the API access key to copy it to your clipboard
Connect to GoFundMe Pro
After you copy your Pixel ID and API access key, you’ll need to enter them in GoFundMe Pro.
- In GoFundMe Pro, go to Apps & Integrations > Explore
- Select Meta Conversions API
- Enter your Pixel ID and API access key into the appropriate fields
- Select Enable Meta Conversions API
Track data through Meta
Please note that the data collected through the Meta Conversions API will not appear in GoFundMe Pro - it is in the Pixel section of the Events Manager in your Meta Business Suite account.
Since the data is in your Meta Business Suite account and GoFundMe Pro does not have insight into your Business Suite account, GoFundMe Pro's Care Team will not be able to answer questions about the data. Find out more from the Meta Business Help Center.
Also, if you’re looking for additional support on how best to use Meta Pixels and the Meta Conversions API, we’d be happy to connect you with one of our agency partners: please reach out to partners@gofundme.com for recommendations.
Frequently asked questions
Do I need to have a Meta Pixel (aka Facebook Pixel) set up in order to use the Meta Conversions API?
You are not required to have a Pixel installed on your campaign pages in GoFundMe Pro. However, Meta requires a valid Pixel ID to ensure the data tracked by the Conversions API is connected to the right Meta Business Suite account. We strongly recommend that you install the Pixel you intend to use for the Conversions API on your GoFundMe Pro campaign pages as well to capture as much data about conversion events as possible. Meta also recommended this in their best practices.
Can I set up the Meta Conversions API through Google Tag Manager instead?
GoFundMe Pro does not support setting up the Meta Conversions API via Google Tag Manager, which uses a custom tag template, which isn’t available in GoFundMe Pro’s GTM container. GoFundMe Pro offers a direct integration with the Meta Conversions API that doesn’t require Google Tag Manager.
What event types does GoFundMe Pro support?
Look below to see the events you can track through the Meta Conversions API, and which parameters GoFundMe Pro supports for each event. Please note that the Event ID parameter is always sent in order to deduplicate event data. Other Event detail parameters are only sent if the data is available at the time the event occurs.
| Meta event name | Event Parameters | Customer Parameters | Description |
| Add to cart | Event Time, Event Name, Event Source URL, Action Source, Event ID, Currency, Value, Content Category, Content Name, Contents | Client IP, Client User Agent, Click ID (fbc) cookie, Browser ID (fdp) cookie | When a ticket is added to a supporter’s cart (by selecting +), or when a supporter adds an additional donation |
| Complete Registration | Event Time, Event Name, Event Source URL, Action Source, Event ID, Currency, Value, Content Category, Content Name, Contents | Client IP, Client User Agent, Click ID (fbc) cookie, Browser ID (fdp) cookie | When a fundraiser signs up successfully (P2P), or when a ticket or registration is successfully purchased (RwF) |
| Initiate Checkout | Event Time, Event Name, Event Source URL, Action Source, Event ID | Client IP, Client User Agent, Click ID (fbc) cookie, Browser ID (fdp) cookie | A supporter lands on a donation page (checkout form) |
| Purchase | Event Time, Event Name, Event Source URL, Action Source, Event ID, Content Category, Currency, Value, Content Name | Client IP, Client User Agent, Click ID (fbc) cookie, Browser ID (fdp) cookie | When a successful donation is made |
| View Content | Event Time, Event Name, Event Source URL, Action Source, Event ID, Content Name | Client IP, Client User Agent, Click ID (fbc) cookie, Browser ID (fdp) cookie | When a supporter views a page |
How soon will the Meta Conversions API collect data on my campaign pages?
Once you have successfully saved your Pixel ID and API access key in GoFundMe Pro Manager, the Meta Conversions API will collect data on conversion events as these events occur. Conversion events will be captured, sent to Meta, and be visible in the Events Manager section of your Meta Business Suite account.
Note: Events that occurred before the integration was enabled on GoFundMe Pro will not be sent to Meta.
How can I check if the Meta Conversions API is capturing data?
To learn more about testing server events, we recommend reading Meta’s Test Events Tool guide.
Where will the conversion data be stored?
Meta stores the collected information. Because of this, we cannot troubleshoot errors, missing or incomplete data in Meta, as we do not have access to your Meta account. However, if you are experiencing issues, we recommend you first double check that the correct Pixel ID and API access key were entered in GoFundMe Pro Manager.
Where can I learn more about the Meta Conversions API?
To learn more about the Meta Conversions API, we recommend viewing the Meta Business Help Center.
How is GoFundMe Pro's Meta Conversions API integration different from GoFundMe Pro's Facebook Pixel integration? Which should I use?
The Pixel helps you measure what people do in their browsers when they land on your GoFundMe Pro pages after selecting an ad. This data can help you manage and better target your advertising. GoFundMe Pro’s Meta Conversions API integration captures detailed conversion events from GoFundMe Pro’s servers and sends them to Meta’s servers. In general, the Pixel shows more information about the donor journey, whereas the Conversions API is focused on the end result. Because ad blockers or browser privacy settings may impact how much data the Pixel can collect, we recommend using both tools to help you understand and optimize the donor journey.
Note:
- The Meta Conversions API is one of a suite of tools available to understand campaign performance. It does not replace other analytics tools, such as Facebook Pixel, Google Tag Manager, etc.
- It is meant to be used in conjunction with other analytics tools as it does not offer the same breadth of event tracking as more traditional analytics tools.
- It is best to think of CAPI and other server-side solutions as a net that captures (an ever-increasing amount of) data that falls through the cracks due to browser or privacy settings