Ads learn which requests became paid jobs

DoneTracking where customers come from

Every time a job moves a step in the CRM, ObserviX is told. So the ad platforms can learn which clicks became paying customers, not just form fills.

What we did

Each step of a job is reported to ObserviX the moment it changes: new request, contacted, qualified, booked, completed or lost.
The job's value goes with it, so ObserviX knows how much each customer paid.
ObserviX joins that to the visit the customer came from — which ad, which search. Google Ads now learns from this: a request counts as $50, a paid job as its real amount, a lost job as $0 (see "Ads stage 1").
When the manager moves a job in GoHighLevel, the same step reaches ObserviX through our CRM (see the GoHighLevel report).

 Ad click ──▶ site visit ──▶ request ──▶ CRM job
                                            │ every step:
                                            │ new · contacted · qualified
                                            │ booked · completed ($) · lost
                                            ▼
                                        ObserviX
                                 joins the job to the ad click
                                            │
                                            ▼
                           Google Ads / Facebook learn:
                       "this click became a $319 paid install"

What the ads learn	Before	Now
Someone filled the form	yes	yes
That request was booked	no	yes
That job was completed, and for how much	no	yes

Why it matters

Ads that only learn about form fills find more people who fill forms. Ads that learn about paid installs find more people who pay.