From click to confirmed request

Understand every step. Count what actually happened.

TrackFlow helps you distinguish landing-page activity from genuine Telegram join requests, then sends eligible server-side events to Meta for measurement and verification.

The process

Six steps. One clearer funnel.

Each stage represents a different action. A click is not a request, and a request is not an approved membership.

01

Connect your landing page

Use the tracking integration on your WordPress landing page to record visits and prepare the Telegram button journey.

Signal: page visit
02

Measure the button click

When a visitor clicks the Telegram button, TrackFlow can record that action separately. Clicking alone does not confirm a request.

Signal: button click
03

Open a join-request invite

The visitor follows a private-channel invite link configured to require approval. Unique invite links can help connect a request with its landing-page journey.

Signal: invite-link context
04

Receive Telegram confirmation

When someone submits a join request, Telegram sends a chat_join_request update to your authorized bot's webhook. TrackFlow records the real request.

Signal: verified request
05

Send the server event to Meta

Where configured, TrackFlow sends a TelegramJoinRequest event through Meta Conversions API. You can verify delivery in Meta Events Manager.

Signal: server event
06

Review requests and approvals

See request activity in your dashboard and track approved members separately where supported by your bot permissions and Telegram updates.

Signal: approved membership
At a glance

The journey, without the guesswork.

Each milestone has its own meaning and should be reported separately.

↗Page visitVisitor arrives
◎Button clickVisitor shows interest
✉Join requestTelegram confirms request
⇄Meta CAPIServer event delivered if accepted
✓ApprovalMembership tracked separately
Built around accuracy

Know the difference between activity and outcomes.

A visitor may click your Telegram button but never submit a request. Another may request access and remain unapproved. TrackFlow keeps these actions separate so you can make decisions using clearer data.

  • Understand where visitors drop off
  • Compare button clicks against actual requests
  • Review approvals independently of requests
  • Keep different channels and landing pages distinct
Event definitions
VisitLanding page loaded
Traffic
JoinButtonClickTelegram button clicked
Intent
TelegramJoinRequestTelegram webhook received
Request
Approved memberApproval confirmed where supported
Membership

Important: event delivery is not the same as ad attribution.

Meta accepting a server event confirms processing, not necessarily which ad caused the request. Reliable ad-level attribution requires connecting the original ad interaction to the Telegram request, along with appropriate event matching and deduplication. TrackFlow does not treat a processed event as proof of attribution.

See TrackFlow in action

Track requests, not just clicks.

Explore channel plans or sign in to your existing TrackFlow dashboard.

Explore pricing → Log in