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

1. Visitor clicks your ad and lands on your page
2. AdTarget captures the Meta click ID (fbclid)
3. They join your Telegram channel
4. 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

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

Conversion Events

AdTarget can send these events to Meta:

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

Attribution Window

AdTarget attributes conversions within a 7-day window by default:

• User clicks ad on Day 1
• User visits your page (session created)
• User joins Telegram anytime within 7 days
• Conversion attributed to original ad click

Custom attribution windows available on request.

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?

• Event type (Lead, CompleteRegistration, etc.)
• Event time
• Click ID (fbclid) for attribution
• Hashed user data (if available)

Is this GDPR compliant?

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