GoHighLevel: my Won opportunity stage doesn't reach Facebook. What to check

Almost always, the Won event never left your setup, or it left and Meta could not match it to a person. Check those two things in that order, and the answer is usually visible in about fifteen minutes.

Here is the story I hear most. An agency owner moves a deal to Won on Friday, opens Events Manager on Monday, and sees nothing. The first instinct is to blame Meta. The second is to rebuild the workflow. Both waste a day, because the break is normally in one boring place.

Start with the trigger. A workflow that fires on stage change only fires when the stage actually changes. If the opportunity was created straight into Won, or was imported already sitting in Won, nothing changed, so nothing fired. Open the workflow history for that contact and look for a run. No run means the trigger never saw it. Check the current documentation for how your workflow trigger treats imported or bulk-moved opportunities, because I would not guess at that.

Second, check that the stage you moved to is the stage the workflow listens for. Pipelines get cloned, stages get renamed, and a workflow pointed at a stage called Won in an old pipeline will happily do nothing forever while the new pipeline works fine on the surface.

Third, look at what was sent. If the run happened and the action shows as completed, open the event and read it. Was there a value on it? Was there an email or a phone number? Meta needs something to match on. A Won event with no email, no phone and no click ID is a receipt with no name on it. Meta accepts it or drops it, and either way it cannot be tied to an ad.

Fourth, the timing. Meta rejects events that arrive more than 7 days after they happened. If your sales cycle is slow and the workflow only runs when someone gets around to tidying the pipeline, the event can be stale by the time it is sent. Also remember that Events Manager can take a while to show new events, so look at the dataset's activity view rather than the campaign column, which lags further.

Fifth, the dataset itself. Since May 2025 the old offline event sets are gone, and events go through the Conversions API into a dataset. If your setup still points at an offline event set from a tutorial that is a couple of years old, that is your answer. Confirm the destination in your connection, and check the current documentation on Meta's side if you are unsure what it currently expects.

Here is a made-up example, clearly invented. A dental-implant agency runs Facebook lead ads into HighLevel. The Won workflow was built on a pipeline called Sales 2024, and in March the team started using a copy called Sales 2025. Nobody updated the workflow. For six months, every Won deal in the new pipeline sent nothing, and the ad account looked like it produced only leads that never closed. Meta was optimising toward cheap leads because it had never heard about a single sale. The fix took two minutes: repoint the trigger. The damage took months to reverse, because the algorithm had to relearn.

That is the honest limit of any checklist like this. You can fix the plumbing in an afternoon, but the ad platform learns slowly, so expect the improvement to show over weeks, not days, and only if you have enough Won events for it to learn from.

For reference, DataCops has a native HighLevel connection that sends lead, booked, showed, won (with value) and paid, and writes the result back onto the contact. It never sends cancelled, no-show or lost, so those will not show up in Meta from that route.

So which of the five checks did it turn out to be for you? If you tell me whether the workflow history shows a run, I can narrow it down.