Facebook Ads Alerts Telegram Setup: Step-by-Step Guide

Facebook ads alerts via Telegram are the fastest way to know when a campaign needs attention — faster than email, more reliable than Slack push notifications, and available on any device including your phone's lock screen. Understanding facebook ads alerts telegram is essential for any media buyer looking to optimize at scale. This guide covers the complete setup from zero: creating the bot, configuring your channel structure, connecting to your ad platform, and building the alert rules that cover the scenarios that actually matter.

The entire setup takes 15-20 minutes. After that, your phone will tell you about CPA spikes, budget blowouts, and winning campaigns — before you would have discovered them manually.

For the broader strategy of which performance metrics to alert on and how to set thresholds, see our Meta ads performance alerts guide first. This article focuses on the technical setup.

---

What You Will Have After This Setup

Before getting into steps, a clear picture of the end result:

• A Telegram bot that can send messages to channels and groups on your behalf
• A channel structure with separate channels for emergencies, per-client alerts, and weekly digests
• Your ad automation platform connected to Telegram, sending alerts automatically
• Five alert rules configured and tested: spend cap breach, CPA spike, ROAS drop, creative fatigue, and daily summary

Total time: 15-20 minutes for initial setup, 30 minutes to build and test all five rules.

---

Part 1: Create Your Telegram Bot

1Step 1: Find BotFather

BotFather is Telegram's official bot for creating and managing bots. It is a verified account — look for the blue checkmark.

1. Open Telegram on any device
2. In the search bar, type @BotFather
3. Open the conversation
4. You will see BotFather's intro message

2Step 2: Create the Bot

1. Type or tap /newbot
2. BotFather asks: "Alright, a new bot. How are we going to call it?" — Enter a display name like AdRow Alerts or [Agency Name] Ads Monitor
3. BotFather asks for a username: must end in bot. Examples: adrow_alerts_bot, acme_ads_monitor_bot
4. If the username is available, BotFather sends your bot token

Your bot token looks like this:

7428391203:AAH-xYz123aBcDeFgHiJkLmNoPqRsTuVwXyz

Critical: Save this token immediately. Treat it like a password — anyone with your bot token can send messages as your bot. Store it securely (password manager or secret manager, never in plain text files or code repositories).

3Step 3: Set a Bot Profile Picture (Optional but Recommended)

1. Send /setuserpic to BotFather
2. Select your bot from the list
3. Upload an image

A recognizable avatar makes it immediately obvious when you glance at your phone that the incoming message is from your ads monitoring system.

---

Part 2: Set Up Your Channel Structure

Create Your Emergency Channel

This channel receives only critical alerts — spend cap breaches, ROAS collapses, account-level overspend. Every team member should have push notifications enabled for this channel.

1. In Telegram, tap the compose icon (pencil or new message)
2. Select New Channel
3. Name it: 🔴 [Agency Name] — Emergency Alerts
4. Make it private (invitation-only)
5. Add your team members
6. Add your bot as an administrator

Create a Per-Client Channel

For each client (or one shared channel if you have few clients):

1. Create a new channel: [Client Name] — Ad Alerts
2. Add the relevant team members (account manager, media buyer for that client)
3. Add your bot as administrator
4. Notification settings: "Mention only" is fine — these are informational, not emergency

Create a Weekly Digest Channel

Optional but useful for maintaining a high-level view without opening Ads Manager:

1. Create channel: [Agency Name] — Weekly Digest
2. Add all team members and stakeholders who want weekly summaries
3. Only one rule will post here: the Monday morning digest

---

Part 3: Get the Channel IDs

Your ad platform needs the channel ID (a number) to send messages to the right channel. Here is how to get it.

Method 1: Via Bot API (Most Reliable)

1. Open your emergency channel in Telegram
2. Send any message to the channel (so there is something for the API to return)
3. In your browser, visit this URL (replace YOUR_TOKEN with your actual bot token):

https://api.telegram.org/botYOUR_TOKEN/getUpdates

4. Look in the response for "chat":{"id": — the number after this is your channel ID

Channel IDs for public channels look like negative numbers starting with -100:

"chat": {
  "id": -1001234567890,
  "title": "Emergency Alerts",
  "type": "channel"
}

5. Copy the full ID including the minus sign: -1001234567890

Repeat this process for each channel you created, sending a test message to each before calling the API.

Method 2: Forward a Message to @userinfobot

1. Forward any message from your channel to the Telegram bot @userinfobot
2. It will reply with the channel's ID

---

Part 4: Connect Telegram to AdRow

With your bot token and channel IDs ready, connect them to your automation platform.

In AdRow:

1. Go to Settings → Integrations → Telegram
2. Click Add Telegram Destination
3. Paste your bot token in the token field
4. Enter a label (e.g., "Emergency Channel", "ACME Client Channel")
5. Enter the channel ID (with the minus sign for private channels)
6. Click Send Test Message

You will see a test notification in your Telegram channel immediately. If you do not see it within 30 seconds:

• Verify the bot is an admin in the channel
• Check that the channel ID is correct (copy it again from the API response)
• Make sure the bot token matches exactly (no extra spaces)

7. Save the destination

Repeat for each channel. You will have multiple Telegram destinations configured — each rule will specify which destination to use.

---

Part 5: Build Your First Five Alert Rules

With Telegram connected, build these five rules in order. Each takes 2-3 minutes to configure.

Alert Rule 1: Emergency Spend Cap Breach

This is the most important alert. Set it up first.

In AdRow → Automation → New Rule:

• Name: Emergency — Spend Cap Breach
• Applies to: All active ad sets
• Conditions: Spend today > [enter 3x your target CPA] AND Conversions today = 0 AND Running time > 4 hours
• Action 1: Pause ad set
• Action 2: Telegram notification → Emergency Channel
• Message template:

🔴 SPEND CAP BREACH: {{ad_set_name}}
Spend today: €{{spend_today}} | Conversions: 0
Campaign: {{campaign_name}} | Account: {{account_name}}
Paused at: {{timestamp}}
→ Open in Ads Manager: {{ads_manager_link}}

• Evaluation: Every 30 minutes
• Cooldown: 12 hours

Click Save and Test — AdRow will simulate the rule and show you a preview of the Telegram message.

---

Alert Rule 2: CPA Spike

• Name: Performance — CPA Spike
• Applies to: All active ad sets
• Conditions: CPA (last 4 hours) > [enter 2x your target CPA] AND Spend (last 4 hours) > [enter 1.5x your target CPA]
• Action: Telegram notification → Client-specific channel
• Message template:

🟡 CPA ALERT: {{ad_set_name}}
CPA (4h): €{{cpa_4h}} | Target: €{{target_cpa}}
Spend today: €{{spend_today}} | Conversions: {{conversions_today}}
Campaign: {{campaign_name}}

• Evaluation: Every 2 hours
• Cooldown: 4 hours

---

Alert Rule 3: ROAS Drop (For E-Commerce)

Skip this rule if you optimize for CPA rather than ROAS.

• Name: Emergency — ROAS Below Break-Even
• Applies to: All active campaigns with purchase optimization
• Conditions: ROAS (today) < [enter 0.8x your break-even ROAS] AND Spend today > $150 AND Running > 48 hours
• Action 1: Pause campaign
• Action 2: Telegram notification → Emergency channel
• Message template:

🔴 ROAS EMERGENCY: {{campaign_name}}
ROAS today: {{roas_today}}x | Break-even: {{breakeven_roas}}x
Spend: €{{spend_today}} | Revenue: €{{revenue_today}}
Auto-paused. Review before restarting.

• Evaluation: Every 3 hours
• Cooldown: 24 hours

---

Alert Rule 4: Creative Fatigue Warning

• Name: Creative — Fatigue Detected
• Applies to: All active ads
• Conditions: Frequency (7 days) > 3.0 AND CTR (today) < [enter 70% of your average CTR for active ads] AND Impressions (7 days) > 5,000
• Action: Telegram notification → Client channel (creative team tag)
• Message template:

🟡 CREATIVE FATIGUE: {{ad_name}}
Frequency (7d): {{frequency_7d}} | CTR today: {{ctr_today}}
Historical CTR: {{ctr_alltime}} | Impressions: {{impressions_7d}}
Ad set: {{ad_set_name}} — Time to refresh creative

• Evaluation: Every 6 hours
• Cooldown: 48 hours

---

Alert Rule 5: Daily Summary

• Name: Daily — Performance Summary
• Applies to: Account level
• Schedule: Every day at 20:00 (local time)
• Conditions: None (always fires)
• Action: Telegram notification → Digest channel
• Message template:

📊 DAILY SUMMARY — {{account_name}}
Date: {{date}}
Total spend: €{{account_spend_today}} / €{{account_budget_today}}
Conversions: {{account_conversions_today}} | CPA: €{{account_cpa_today}}
Active campaigns: {{active_campaign_count}}
Alerts fired today: {{alerts_count}}

• Evaluation: Daily at 20:00
• Cooldown: 20 hours

---

Part 6: Test Every Alert Before Going Live

Never rely on untested alerts in production. Run this test protocol before enabling all rules.

Test Protocol

Test 1: Force a spend cap trigger Temporarily lower the spend cap threshold below an ad set that is already spending (e.g., set it to $1 to guarantee it triggers). Confirm:

• Alert arrives in Telegram within 2 minutes
• Message content is correct (all variables populated)
• Ad set is paused

Restore the threshold to the correct value immediately.

Test 2: Verify channel routing Each alert should go to the correct channel. Confirm the emergency channel receives emergency rules; the client channel receives client-specific rules.

Test 3: Check cooldown behavior Trigger the same rule twice within the cooldown window. The second trigger should not send a duplicate. If it does, verify the cooldown is saved correctly.

Test 4: Test message formatting on mobile View every alert template on your phone (not just desktop). Long messages truncate differently on mobile. Confirm the most important information (entity name, metric, action taken) appears in the first two lines — above the fold on a lock screen notification.

Test 5: Verify the Ads Manager link Every alert template should include a direct link to the affected entity in Ads Manager. Tap the link in the Telegram message and confirm it opens to the correct campaign, ad set, or ad.

---

Maintaining Your Alert System

Weekly Maintenance (5 minutes)

1. Send a test notification to confirm the bot is still active in all channels
2. Review the week's alert log — did any rules fire unexpectedly?
3. Check whether any cooldowns prevented important alerts from firing

When to Update Alert Thresholds

• When your target CPA changes (client agreement change, product pricing update)
• At the start of each quarter (performance benchmarks shift)
• After major Meta algorithm updates that change delivery patterns
• When seasonal events (Q4, major sales periods) begin — CPMs rise and standard CPA thresholds may be too tight

Adding More Alert Rules

Once your five foundation rules are running reliably, add rules from our Meta ads performance alerts guide for more sophisticated monitoring. Typical next additions: account-level budget milestone alerts, weekly performance digest per client, and winner detection alerts for scaling candidates.

---

Key Takeaways

Your Facebook ads Telegram alert system is now live:

1. Bot creation takes 5 minutes via @BotFather. Save the token securely — it is your bot's authentication credential.

2. Channel structure matters. Emergency channel for critical alerts, per-client channels for operational alerts, digest channel for weekly summaries.

3. Test before trusting. Force every alert rule to trigger in a controlled test before relying on it in production.

4. Include all decision context in every message. Entity name, current metric, threshold, spend, and a direct Ads Manager link. Alerts without context require you to open Ads Manager — defeating the point.

5. Review and maintain weekly. Bots get removed from channels, tokens expire, thresholds become stale. A 5-minute weekly check keeps the system reliable.

For managing this alert system alongside your complete automation stack, see our Facebook ads automation complete guide.