Skip to content
ChatterfyHelp Center
HomeGeneralCRMAI ManagerTrackerPlatformsFAQUpdate log
Tracker
Dashboards
Campaigns
S2S Postbacks — Sending Events from a Campaign
Campaigns — advertising campaigns
How to create a campaign
Information — Basic Campaign Identification
General — user journey
Auto Actions — auto actions based on postbacks
Parameters — link parameters
Filters — traffic filters
Test — checking a campaign before launch
Invite + DM — Hybrid Scenario
Sources
Domains
Landings
Analytics
Cohorts
Leads
Integrations
  1. Tracker
  2. Campaigns
  3. Test — checking a campaign before launch

Test — checking a campaign before launch

The Test tab is a built-in simulation of a real user journey through a campaign link. It opens the landing page on your behalf, takes you through the entire path all the way to Telegram, and records e

Updated August 30, 20264 min
The Test tab is a built-in simulation of a real user journey through a campaign link. It opens the landing page on your behalf, takes you through the entire path all the way to Telegram, and records every event along the way. This is the main tool for checking a campaign before sending traffic.
When you must run Test
Before every new traffic launch, always. After any changes to the campaign (if you changed the landing page, domain, Source, or filters). After recreating the bot / DM bot. If leads suddenly stop coming in, Test will show which step in the chain is breaking. Before presenting the campaign to a client or manager, make sure everything works.
Test section
Test section




How it works

  • Tracker creates a clickid and records a Page View.
  • Filters are applied (if the IP is not allowed, there will be a redirect).
  • The landing page opens — either your Default or Custom one.
  • When the transition button is clicked, a Click event is recorded and the user goes to Telegram.
  • If Channel: request to join → acceptance → DM bot sends a private message.
  • If Bot: the bot opens → Start is pressed → Flow starts.
  • All events (Page View, Click, Subscribe, Contact) are logged in and in .
Test is completely transparent — it is not an “emulator”, but a real path. You simply go through it yourself to find errors.

How to run Test

  1. 1

    Open the campaign

    Tracker → Campaigns → select the campaign → Edit.
    
  2. 2

    Go to the Test tab

    The last tab on the right.
    
  3. 3

    Click Open

    A new browser tab with the landing page will open. If filters block access, you will see a redirect (this is normal if your IP is not from an allowed country — use a VPN).
    
  4. 4

    Go through the user path

    Click the button to go to Telegram. If it is Channel, submit a request to join the channel (in the real Telegram under your own account). If it is Bot, press Start in the bot. Wait for the first message from the bot.
    
  5. 5

    Check the result

    Open Logs — event logs and Dashboards — Summary Analytics. The following should appear: Page View, Click, Subscribe (for Channel), Contact. If any stage is missing, the problem is at that point.
    
  6. 6

    Remove the test chat from the CRM

    After the test, your chat with the bot will appear in Статья. Delete it or set Status = Stopped so you don’t confuse the analytics. You can also leave it and mark it with the test tag.
    



What to check during Test

  • Whether the landing page opens (domain / SSL / content).
  • Whether filters work — a non-target IP triggers a redirect (use a VPN to check).
  • Whether the button to Telegram leads to the correct destination (channel Invite-link or direct bot).
  • Invite Bot accepts the request (for Channel).
  • The DM bot or Invite Bot sends the first message (the Flow starts).
  • Page View / Click / Subscribe / Contact events are recorded in Tracker.
  • The test lead card shows Tracker parameters (sub1, ad_name) — .
  • Auto Actions run (if you want to check this, send a test postback via ).



Usage examples

Before driving traffic — arbitrage

Buyer has created a new campaign with a creative and is ready to spend $500 on Facebook. Before driving traffic, they run Test. They go through the entire path and see that the DM bot is silent after Subscribe. They go to Статья — it turns out the DM bot is disabled. They enable it, run Test again, and everything works. This saved $500 in potential losses.

After changing the landing page — arbitrage

Buyer moved from the Default landing page to Custom (their own ZIP). They run Test — they land on the landing page, click the button to proceed, and the button does not work. They open Custom — your own ZIP archive — they see that they forgot to add the tracker attribute to the button in the HTML. They fix the ZIP, reupload it, and Test passes.

Filter debugging — arbitrage

Buyer added the filter Available countries = US, AU. They want to make sure the filter works. They run Test from their IP (Russia) and see a redirect to a separate URL. They run it through a VPN with a US location and land on the landing page. The filter works correctly.
What to keep in mind
A test click-through is recorded in the campaign’s overall statistics — Page View, Click, Subscribe, and Contact events go to Dashboards and Analytics. If you want clean analytics, filter test leads by the test tag or by the test click’s clickid. Test does not send postbacks from the affiliate network — to check postbacks, use a test account in the affiliate network, a registration link with a test clickid, and a postback emulator (if available). If, according to the filters, you are not in an allowed country, Test will not show the landing page, and this is a valid check.



Frequently Asked Questions

The problem is with the domain or landing page. Check: How to Set Up SSL (status Active), the domain opens directly via HTTPS in a new tab. If it is a Custom landing page, the ZIP was uploaded correctly (see Custom — your own ZIP archive).

Wait a minute — Contact may be recorded with a delay. If it does not appear: check Статья — the bot may be archived or in a Space you do not have access to. Also check that the DM bot is not in Stopped status.

Logs displays only postbacks from partner networks — Page View, Click, Subscribe, and Contact are not visible there. View these events in Dashboards — Summary Analytics and Analytics — detailed table (the counters there should increase after Test).

Yes, Test creates an invite link or a direct link to the bot depending on the Telegram — Source Inside the Messenger settings. The actual Telegram will open; from there, it works the same as for Facebook / Google.

Check that the campaign has been saved (if you have just edited it, click Save first), all required fields are filled in (if there are validation errors, Test may not open), and the browser is not blocking pop-up windows. Also check that the campaign has at least one Source — without a Source, the link cannot be created.



Related

How to create a campaign
Creating a new campaign in Tracker — a step-by-step flow through all form setup tabs. Result: a working campaign with ready-to-use links for the ad account. This guide takes you from an empty campaign
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
Dashboards — Summary Analytics
The Tracker → Dashboards section is a quick monitoring screen. Six key metrics at the top and funnel charts from click to repeat deposit at the bottom. It opens in 2 seconds and immediately answers th
Filters — traffic filters
The Filters tab is a campaign-level system for filtering out non-target traffic. A user who does not meet the conditions is redirected to a separate URL (you specify which one). Those who pass go to t

Was this article helpful?

BackFilters — фильтры трафикаNextInvite + DM — Hybrid Scenario

On this page

  • How it works
  • How to run Test
  • What to check during Test
  • Usage examples
  • Before driving traffic — arbitrage
  • After changing the landing page — arbitrage
  • Filter debugging — arbitrage
  • Frequently Asked Questions
  • Related