Overview

This integration connects Everflow with Meta Business Manager to provide seamless, real-time conversion tracking that goes beyond Meta's standard capabilities. By using Meta's Conversions API (CAPI), you can push conversion data directly from Everflow to Meta without placing pixels on websites, improving tracking accuracy and campaign optimization.

The setup process has been streamlined with the latest Meta SDK, making implementation straightforward for networks managing internal campaigns and affiliates running Meta ads. Remember that direct linking is required per Meta's policies—using redirect links could put your Meta account at risk.

Key Benefits

Real-Time Data Synchronization

• Instant conversion data transmission to Meta Business Manager
• Improved tracking accuracy and reliability
• Better optimization capabilities for campaigns

Simplified Implementation

• No direct website pixel placement required
• Streamlined setup process with latest Meta SDK
• No Meta Developer Settings app creation needed
• Access Token generation through simplified process

Who Is This For?

This integration is specifically designed for:

Primary Users

• Network operators managing internal Meta campaigns
• Affiliates running Meta advertising campaigns
• Performance marketers requiring precise attribution data

Secondary Users

• Marketing teams needing consolidated reporting
• Campaign managers seeking optimization insights
• Technical teams implementing tracking solutions

Prerequisites

A Step-By-Step Guide

Troubleshooting

Viewing API response from Meta (Facebook)

You will then be able to see the response from Meta (Facebook) as to why there was an error:

Required fbclid is missing from click parameters:

Meta will only receive a successful response if a fbclid is included in the click details. This can be viewed under the click details > Parameters of the click that was made:

If an affiliate is using direct linking, the fbclid will automatically be passed when a user clicks on the Meta Ad. If they are using direct linking, and there is no fbclid, then the click did not originate from Meta traffic.

If the partner is using a redirect tracking link, they will need to ensure &fbclid={fbclid} is appended to their Partner Tracking Link used in the Ad Placement.

FAQ

Troubleshooting Checklist

If conversions aren't reaching Meta, work through this checklist before reaching out for help. Have your Transaction ID, Partner ID, and the Partner Postback (pixel) ready.

For more detail on Meta's error responses, see Meta's error-handling documentation.

Using a Macro in the Event Source URL

The Event Source URL field supports macros, so you can build the URL dynamically. This is useful when a single offer routes traffic across multiple converting domains — for example, listicle offers. For this macro to resolve, the advertiser must pass the converting domain value in their postback to Everflow.

Here is how this process works step-by-step:

Creating or Updating a Meta Pixel via the API

In addition to configuring pixels in the interface, networks can create or update a Meta pixel programmatically using the Everflow API. Send a POST request to the /v1/networks/pixels endpoint with your X-Eflow-API-Key header.

# POST to create or update a Meta (Facebook) pixel
curl --request POST \
  --url https://api.eflow.team/v1/networks/pixels \
  --header 'content-type: application/json' \
  --header 'X-Eflow-API-Key: <INSERT API KEY>' \
  --data '{
    "network_affiliate_id": 12345,
    "pixel_type": "conversion",
    "pixel_level": "global",
    "pixel_status": "active",
    "facebook_pixel": {
      "custom_data": [
        { "field": "currency", "value": "usd" },
        { "field": "value", "value": "100" }
      ],
      "user_data": [
        { "field": "fbc", "value": "<insert FBC variable>" }
      ],
      "network_affiliate_integration_facebook_business_id": <Meta Integration ID>,
      "pixel_id": "<Pixel ID>",
      "event_name": "<Event>",
      "event_id": "<Event ID>",
      "event_source_url": "<Event Source URL>",
      "action_source": <Action Source>
    },
    "delivery_method": "facebook"
  }'