Skip to content
ChatterfyHelp Center
HomeGeneralCRMAI ManagerTrackerPlatformsFAQUpdate log
Tracker
Dashboards
Campaigns
Sources
Sources — Traffic Sources
Facebook — Source with Meta Pixel
Google — Source with Google Ads
Telegram — Source Inside the Messenger
Custom — Universal Source
TikTok — Source with TikTok Ads
Domains
Landings
Analytics
Cohorts
Leads
Integrations
  1. Tracker
  2. Sources
  3. Facebook — Source with Meta Pixel

Facebook — Source with Meta Pixel

A Source with Provider = Facebook is needed when you drive traffic from Meta Ads (Facebook, Instagram). Tracker links your campaign events to the Facebook pixel and sends conversions back through the

Updated August 30, 20265 min
A Source with Provider = Facebook is needed when you drive traffic from Meta Ads (Facebook, Instagram). Tracker links your campaign events to the Facebook pixel and sends conversions back through the Conversions API. This is critical for ad optimization: without sending events back, Facebook does not “understand” which leads convert, and the algorithm works blindly.
When you need a Facebook Source
You run traffic through Facebook Ads Manager and want the ad algorithm to optimize for target events (FDs, registrations, any conversions). You want to see conversions in the Facebook account itself in the Custom Conversions columns. You use Lookalike audiences based on paying users — Facebook needs the signal that “this user made a deposit.” You run A/B tests of different creatives and want to see each one’s conversion rate in Facebook (not only in Tracker).
Facebook source setup
Setting up a Source with Provider = Facebook



How it works

Tracker is the server-side part of this flow. It creates and sends events to the Conversions API: ViewContent on Page View, Lead on Click, Subscribe on subscription, Contact on the first message in the bot, CompleteRegistration on registration in the affiliate program (if a postback is received), and Purchase on the first deposit. The mapping is configured in Mapping events — you can adapt it to the structure of your Custom Conversions in Facebook.

Setup steps

  1. 1

    Create a new Source

    In the campaign, on the Sources — Traffic Sources tab, click Add source. Provider = Facebook.
    
  2. 2

    Fill in the Pixel ID

    Take the Pixel ID from Facebook Events Manager → Data Sources → your pixel. It is a 15–16-digit number.
  3. 3

    Fill in the Access Token

    Generate it in Events Manager → Settings → Set up → Conversions API → Generate Access Token. It is valid for 2 months — after that you need to issue it again.
  4. 4

    Connect a Proxy (optional)

    If you want to send events through a proxy, select a connected Proxy — proxy for S2S. This reduces the risk of blocks and lets you “bind” outgoing traffic to the required geography.
  5. 5

    Configure Mapping events

    By default, the mapping is standard (see the table below). If your Custom Conversions in Facebook are named differently, adjust them here.
  6. 6

    Save and check

    After Save, Tracker will generate a Tracking link — copy it into Facebook Ads. Make a test click and check the sending in “Logs — event log” Logs — журналы событий — Sources logs.


Mapping events — standard correspondence

Mapping events block
Mapping events block

Tracker event
Facebook event
When it triggers
page view
ViewContent
Landing page opened.
click
Lead
Click on the button to go to Telegram.
subscribe
Subscribe
Joining a channel or opening a bot.
contact
Contact
First message from the lead in the bot / DMs.
registration
CompleteRegistration
Registration in the affiliate program (received via postback).
sale
Purchase
First deposit (received via postback).
Additionally, Tracker sends the following parameters to Facebook:
  • value = {cost} (deposit amount from the postback).
  • currency = {currency} (currency).
This allows Facebook to see the value of each conversion — for optimization by ROAS / value-based bidding.


Source fields

Field
What it defines
Where to get it
Name
Internal source name. Visible in Tracker filters.
FB-US-Forex
Provider
Source type. Select Facebook.
—
Pixel ID
Pixel identifier in Facebook.
Events Manager → Data Sources → your pixel
Pixel Access Token
Server token for Conversions API. Valid for 2 months.
Events Manager → Settings → Conversions API → Generate Access Token
Proxy
Optional. Proxy for outbound requests.
Section Proxy — proxy for S2S
Mapping events
Mapping of Tracker → Facebook events. Standard by default.
—


Usage examples

Standard Forex offer setup — arbitrage

A buyer sends a Forex offer from Facebook to the US. Creates a Source with Pixel ID = 123456789012345, an Access Token from Facebook, and the default Mapping (Subscribe → Subscribe, Contact → Contact, Purchase → Purchase). After a day, the Custom Conversions column appears in Facebook Ads Manager, showing Subscribes and Purchases — the ad algorithm starts optimizing for them.

Custom Mapping for specific Custom Conversions

The client has Custom Conversions configured in Facebook with the names TgChannel_Sub, TgChannel_Lead (from an old solution; changing the names would take a long time). The buyer overrides the Mapping: subscribe → TgChannel_Sub, click → TgChannel_Lead. Tracker sends events under these names, and Facebook picks them up.

With Proxy — bypassing blocks

The buyer noticed that Facebook rejects 30% of events (visible in “Logs — event log” Logs — журналы событий — Sources logs with the Error status “Invalid token” or “User-data missing”). Enables Proxy — proxy for S2S with a US IP (where the traffic is concentrated). After 2 days, the rejection rate drops to 5%, and optimization in Facebook stabilizes.
Important things to consider
The Pixel Access Token is valid for 2 months — after it expires, you need to regenerate it. Set a calendar reminder for this, or monitor Sources logs (a sudden spike in Error means the token has died). Pixel ID is required — without it, the event simply will not be sent. Mapping events can be changed “on the fly” — changes are applied instantly to new events. With Proxy, events are sent to Facebook faster and more reliably, especially at high volume. Test sending in Logs — журналы событий after every settings change — it shows the actual status of each event.


FAQ

Check Sources logs in Logs — журналы событий — if the status is OK, Facebook has accepted them. Next comes the delay — events appear in Events Manager with a 30–60 minute lag. Also check that the correct pixel is shown in Facebook Test Events and that the events were not “eaten” by the deduplicator (CAPI + browser pixel send the same event — Facebook merges them. If it looks like there are half as many events, this is normal).

The standard interval is every 60 days. Set a reminder. Also check Sources logs once a week — mass “Invalid token” Errors mean the token died ahead of schedule (for example, the Facebook account password was changed).

If you use standard Facebook events (ViewContent, Lead, Subscribe, Contact, CompleteRegistration, Purchase), leave the default. If you have Custom Conversions with different names in Facebook, override the Mapping. The main rule: the event name in Mapping must exactly match what you have in Facebook (including case).

Yes, there are no restrictions on the Tracker side. The same Pixel ID can be entered in the Source of each campaign. Facebook will see events from all campaigns in one pixel — this is convenient for overall optimization, but makes it harder to separate conversions by project. If you want isolation, use a separate pixel for each project.

Facebook requires at least one user-data parameter for matching (email, phone number, External ID). Tracker automatically passes fbc + fbp + client IP/UA, but sometimes this is not enough. Check that the pixel is installed on the landing page (it generates fbc / fbp) and that the Pixel ID in Tracker matches the pixel on the landing page. If the campaign has no landing page or the landing page belongs to someone else, events may be sent without user-data, and then Facebook will not match them.


Related

Sources — Traffic Sources
The Sources section inside campaign settings is where you connect an advertising traffic source. Each Source has a type (Provider): Facebook, Google, Telegram , or Custom . The Provider determines whi
Proxy — proxy for S2S
The Tracker → Proxy section is a directory of HTTP/HTTPS proxy servers through which Tracker sends outgoing S2S requests to advertising platforms (Facebook Conversions API, Google, etc.). Without a pr
Logs — журналы событий
Откройте Tracker → Logs. В верхней части страницы доступны четыре журнала: отправка постбэков, события источников, S2S-запросы и история изменений объектов Tracker. Для поиска одной цепочки используйт
Parameters — link parameters
Parameters is the campaign tab where link markup is configured: which parameters will be added to the campaign URL and which data will be saved with the lead after they click the link. Campaign tracki

Was this article helpful?

BackSources — источники трафикаNextGoogle — Source с Google Ads

On this page

  • How it works
  • Setup steps
  • Mapping events — standard correspondence
  • Source fields
  • Usage examples
  • Standard Forex offer setup — arbitrage
  • Custom Mapping for specific Custom Conversions
  • With Proxy — bypassing blocks
  • FAQ
  • Related