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. Sources — Traffic Sources

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

Updated August 30, 20264 min
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 which fields are required for setup and how Tracker sends events back to the ad account (S2S — server-to-server).
A single campaign can contain multiple Sources — this is useful when traffic for an offer is running from several platforms in parallel. Each Source creates a separate launch link (you copy it and paste it into your ad account), but analytics are shared across the entire campaign. In Dashboards — Summary Analyticsand Analytics — detailed tableyou can segment by source_name and see which channel delivers what.
What tasks the section solves
Connect Facebook Ads with all its specifics: Pixel ID, Access Token, and event sending via Conversions API. Connect Google Ads with Conversion ID and Conversion labels. Launch traffic directly from Telegram (via a channel invite link or a direct link to the bot). Run a test launch or a non-standard scenario (Custom). Separate sources within a single campaign to see in Dashboards / Analytics which channel performs best. Mixed attribution: a lead clicks an FB ad, then goes to a TG channel, then to DM — Tracker links the clickid across all stages.
Sources section
Sources inside a campaign



Video tutorial




What’s inside

Tracker supports 4 Provider types. Each one has a separate article with a detailed breakdown of fields and setup:
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
Google — Source with Google Ads
A Source with Provider = Google is needed when you drive traffic from Google Ads (Search, Display, YouTube Ads). Tracker links your campaign events to Google Conversions using the Conversion ID and Co
Telegram — Source Inside the Messenger
A Source with Provider = Telegram is needed when traffic comes directly from Telegram — without Facebook, Google, or another external advertising platform. This is a typical scenario for placements in
Custom — Universal Source
Source with Provider = Custom is a universal type that is not tied to a specific advertising platform. Tracker creates a working Tracking link and collects everything on its side (Page View, Click, Su
Provider
When to use
Specifics
Facebook
You run traffic from Meta (Facebook, Instagram).
Pixel ID + Access Token + Mapping events. Tracker sends events to Conversions API.
Google
Google Ads (search, display, YouTube Ads).
Conversion ID + Conversion labels. Auto redirect for the campaign route.
Telegram
Launch traffic from Telegram itself (your own channel, another channel, or a direct link to the bot).
Internal invite link, without an external advertising platform.
Custom
Tests, non-standard scenarios, or a source without a ready-made integration template.
No S2S sending. Universal, with no specific fields.


Use cases by segment

Sources work the same way for any niche. Here are a few real-world scenarios to understand how to combine them:
  • —Forex/crypto arbitrage: the main flow from Facebook (Pixel + CAPI), in parallel — a Telegram “Signals” channel with an invite link and reposts to other channels. One Tracker account sees both lead feeds under one campaign.
  • —E-commerce: Google Ads (search traffic with specific intent) + Facebook (look-alike based on existing customers). Comparing conversion in Dashboards helps you understand which channel to use as the basis for scaling.
  • —Support / SaaS: a Custom source with UTM tags for a webinar landing page + Google Ads with search keywords. Leads go to one Telegram channel, but Tracker remembers where each one came from.
  • —Info business: Facebook + Instagram (one FB Source, because there is one Pixel) + Telegram (reposts in the expert’s personal channels). A Custom source for placements with partners without an ad account.


How to add a Source

Universal sequence for any Provider:
Add source
Add source button

  • 1. In the campaign, open the Sources tab.
  • 2. Click Add source — the creation form will open.
  • 3. Fill in Name (the internal name for the team) and Provider.
  • 4. Fill in the remaining fields — they depend on the Provider (see the corresponding article).
  • 5. Save. Tracker will generate a Tracking link — this is what you will paste into the ad account.
Basic Source fields
Basic Source fields — Name + Provider



Where to start

It depends on the platform you are sending traffic from:
  • Facebook / Instagram — (Pixel ID and Access Token are required).
  • Google Ads — (Conversion ID and labels are required).
  • Telegram (your own ads inside Telegram, placements in other channels) —.
  • Test or non-standard source —.
  • Which parameters to pass in the link URL —.


FAQ

There is no limit. People often use 2–5 — for example, Facebook + Telegram, or several Facebook accounts in one campaign. Each Source is a separate link, but the analytics are shared. In Dashboards, Group By = source_name gives you a breakdown by each source.

A Telegram source is needed when traffic comes directly from Telegram — for example, a placement in someone else’s channel or a direct repost by an influencer. You do not have a Facebook pixel, but you do have a click-through to your channel. A Telegram Source creates an invite link that you can give to another channel for placement. It is often combined with FB as a “second leg”: FB drives cold traffic, while the TG source collects organic traffic.

Yes, that is exactly the point of multiple Sources. Each link goes to its own ad account (Facebook → link A, Google → link B, Telegram → invite C), and Tracker remembers which Source the click came through. In analytics, you can see which source produced which result.

Use the Custom Provider. It does not send events back (S2S), but it provides a working Tracking link and collects all events on the Tracker side. Suitable for non-standard platforms such as Yandex Direct, MyTarget, TikTok Ads (if their API is not connected via a ready-made Provider). UTM tags and parameters are passed via the query string.

A separate Source does not have a Stop status, but if you stop using the link (do not insert it in an ad account, do not receive clicks), the Source simply stops accepting traffic. Delete it if you are sure — the historical analytics for it will remain in the campaign.

For Google, the equivalent is Enhanced Conversions / Offline Conversions via Conversion ID + label. Tracker sends data back to Google according to the same principle as in FB CAPI, but through its own mechanism. Setup is described in “Google — Source with Google Ads” Google — Source with Google Ads — take the Conversion ID from Google Ads; the label is for each type of target action.


Articles in this section

Custom — Universal Source
Source with Provider = Custom is a universal type that is not tied to a specific advertising platform. Tracker creates a working Tracking link and collects everything on its side (Page View, Click, Su
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
Google — Source with Google Ads
A Source with Provider = Google is needed when you drive traffic from Google Ads (Search, Display, YouTube Ads). Tracker links your campaign events to Google Conversions using the Conversion ID and Co
Telegram — Source Inside the Messenger
A Source with Provider = Telegram is needed when traffic comes directly from Telegram — without Facebook, Google, or another external advertising platform. This is a typical scenario for placements in


Related

Campaigns — advertising campaigns
It is the Campaign that connects Domain, Landing, Source, Telegram, tracker parameters, analytics, and events within the CRM. Once launched, the Campaign Tracker begins to: create tracking links recor
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
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 — event logs
Open Tracker → Logs. In the upper part of the page, four logs are available: postback sends, source events, S2S requests, and the Tracker object change history. To search for a single chain, use the s

Was this article helpful?

NextFacebook — Source с пикселем Meta

On this page

  • Video tutorial
  • What’s inside
  • Use cases by segment
  • How to add a Source
  • Where to start
  • FAQ
  • Articles in this section
  • Related