Running leads through IG bot to booking page. Can Ads Manager track that?
I want to run a lead generation campaign that sends people to my Instagram ManyChat bot. After answering a few qualification questions in the bot, users will be redirected to an external booking page (built in HighLevel).
I’ve already installed the Meta Pixel on that external website.
Will I be able to track the number of booked appointments in Ads Manager?”
The short answer is:
Yes, Ads Manager can track the booked appointments, but relying only on the Meta Pixel on the HighLevel booking page is risky and will likely lead to significant underreporting and poor ad optimization due to the break in the customer journey within the ManyChat bot and subsequent data loss from ad blockers and browser privacy features.
The solution is to use the Meta Conversions API (CAPI) to send the ‘booked appointment’ event directly to Meta’s servers from your HighLevel system, which provides a clean, server-side data stream that bridges the gap between the ad click, the bot qualification, and the final conversion event.
The long answer is:
The challenge in your funnel – Instagram Ad to ManyChat Bot to External HighLevel Booking Page to Appointment Booked – is the handoff of tracking data across three distinct platforms.
The Meta Pixel you’ve installed on the HighLevel page is crucial, but it only tracks what happens on that page, and its performance is compromised by client-side issues like iOS privacy changes.
The moment a user clicks the ad and enters the ManyChat bot, the Meta ad-click ID (known as the fbclid needs to be captured, stored, and then successfully transferred across the redirect to the HighLevel page.
While ManyChat is generally good at preserving this fbclid and other parameters in the link it generates for the booking page, the subsequent tracking by the Pixel is still vulnerable.
When the user books the appointment on HighLevel, the Pixel fires a Schedule or CompleteRegistration Standard Event, but the connection back to the original ad is often broken or degraded.
This results in inaccurate conversion counts in Ads Manager, making it hard to trust your Return on Ad Spend (ROAS) figures and hindering Meta’s ability to effectively optimize your campaign.
To make this funnel robust, accurate, and resilient, you need to use a server-side tracking solution, namely the Meta Conversions API (CAPI).
This is where the ManyChat API, HighLevel API, Google Tag Manager (GTM), and a server environment like Stape or Google Cloud Platform come into play.
ManyChat, being aware of the user’s conversation thread, can use its API to send a Lead event directly to CAPI when a user is qualified and clicks the link to the booking page.
This creates a strong, early signal.
The truly powerful, cheap, and permanent solution involves using the HighLevel API to capture the confirmed appointment event.
Instead of relying on the client-side Pixel on the booking page, you use a webhook or integration from HighLevel to send the confirmed appointment data, along with the captured user parameters and the fbclid, to a server-side GTM container (hosted affordably on a service like Stape or a Google Cloud Platform VM).
This server acts as a clean conduit, sanitizing the data and using the Meta Conversions API to fire a high-quality, reliable Schedule or Purchase event directly to Meta’s servers, bypassing ad blockers entirely.
This custom, API-based approach is cost-effective because the operational costs of Stape or a small cloud instance are minimal, yet it gives you enterprise-level attribution accuracy, ensuring that every booked appointment is correctly attributed to the specific Instagram ad that started the customer journey.
About The Author
