Meta Integration

AdTarget sends conversion events to Meta when users join your Telegram channel. This helps Meta’s algorithm optimize your ad delivery for real conversions.

Pixel Setup - Add your Meta Pixel to AdTarget
CAPI Events - Configure Conversions API events

How It Works

Visitor clicks your ad and lands on your page
AdTarget captures the Meta click ID (fbclid)
They join your Telegram channel
AdTarget sends a conversion event to Meta via CAPI

This creates a closed feedback loop: Meta learns which ad clicks lead to Telegram joins.

Why Use CAPI?

Browser tracking is unreliable. Ad blockers, iOS privacy, and browser restrictions break traditional pixel tracking.

CAPI is server-side. AdTarget sends conversion data directly to Meta’s servers, bypassing browser limitations.

Better optimization. More accurate conversion data means Meta’s algorithm can find better audiences for your ads.

What You’ll Need

A Meta Business account
A Meta Pixel ID
A Conversions API access token (System User token)

Quick Setup

Set up your Meta Pixel in AdTarget
Configure CAPI events to send

Conversion Events

AdTarget can send these events to Meta:

Event	When Sent	Description
Lead	User joins channel	Primary conversion event
Purchase	User joins channel	Revenue-focused campaigns (includes value and currency)
CompleteRegistration	User joins channel	Alternative conversion type
Subscribe	User joins channel	Subscription-focused campaigns
Custom	User joins channel	Custom event name for specific campaign needs

You choose which event type to send based on your campaign objectives.

Attribution Window

Tracked invite links expire after 7 days. If a user joins using the tracked link within that window, the conversion is attributed. If they join after the link expires or via other means, the join appears as organic.

FAQ

Does AdTarget replace my existing Meta Pixel?

No. Keep your existing pixel for website events. AdTarget adds Telegram conversion events that your pixel can’t track.

What data does AdTarget send to Meta?

AdTarget sends these parameters via CAPI:

event_name — The configured event type (Lead, Purchase, etc.)
event_time — Timestamp of the join
action_source — Always “website”
event_source_url — Your landing page URL
fbc — Facebook Click cookie (contains the fbclid from the ad click)
fbp — Facebook Browser ID cookie
external_id — Telegram user ID (SHA-256 hashed)
client_ip_address — Visitor’s IP address
client_user_agent — Visitor’s browser user agent
value, currency, content_name — If configured per channel

Is this GDPR compliant?

Yes. AdTarget follows Meta’s data processing guidelines. No personal data is stored beyond what’s needed for attribution.