The short answer is:
You are correct in observing that the native HubSpot-Facebook integration for optimizing ads with post-conversion events (like a lifecycle stage change to SQL or Customer) has been unreliable or non-functional for many users.
The core problem is that HubSpot’s event sending is often delayed or incorrectly formatted for Facebook’s system.
The best solution is to skip the native integration entirely and build a highly reliable, custom server-side connection.
This involves using the HubSpot API to trigger a conversion event push directly to the Facebook Conversions API whenever a significant contact property changes, ensuring the data is fast, accurately formatted, and high-quality for effective ad optimization 
The long answer is:
The frustration you and the community are expressing is extremely common and stems from the difference between two types of integrations: the low-fidelity, browser-based one and the high-fidelity, server-based one.
The issue where a browser pixel is sending events like LEAD and Lead is a classic case of client-side tracking inconsistency that breaks optimization.
The primary hurdle for using a lifecycle stage change like SQL (Sales Qualified Lead) is that it’s an offline conversion - it happens inside HubSpot, not immediately on a website.
While HubSpot’s native Ads tool *tries* to bridge this, it frequently fails.
A far superior solution is to establish a dedicated server-side pipeline.
This process begins with setting up a server-side tagging environment, such as Stape or Google Cloud Platform, managed by Google Tag Manager.
Instead of relying on the HubSpot-Facebook “direct integration” to push events, you use a HubSpot workflow to trigger an action via the HubSpot API whenever a contact’s lifecycle stage changes to your desired conversion point (e.g., SQL).
This action triggers your server-side environment.
Within that server environment, a custom script takes the contact data from HubSpot, including the crucial `fbclid` (Facebook Click ID) or other identifiers like email and phone number for effective matching, and then immediately formats it into a perfect conversion event payload.
This payload is then sent directly to the Facebook Conversions API.
This combination of HubSpot API and Facebook Conversions API is better because it is instantaneous, is not affected by ad blockers or cookie consent banners, and ensures the event label (e.g., Purchase) is perfectly consistent every time, providing Meta’s optimization algorithms with the high-quality data they need to improve your lead quality, which is the ultimate goal.
This API-to-API communication is the most robust way to attribute deep-funnel, CRM-based conversions back to your Facebook Lead Ads.
This comment was generated with the assistance of an AI tool, incorporating my expertise in conversion tracking 