Send booked jobs from form leads back to Google Ads and Meta
Checks that your WordPress lead forms capture click IDs, sets up a click-import conversion action, validates your booked-job list and uploads it to Google Ads and the Meta Conversions API after your approval.
When to use it
When Google Ads and Meta only see form fills and you want them to optimize for the jobs you actually booked.
What you get
A checked setup with click-ID capture on your form, a Booked job conversion action, a validated job list, and offline conversions uploaded to Google Ads and the Meta Conversions API after your approval.
Does it change anything in my account?
Only with your approval. The assistant first shows a preview of every change and waits for your go-ahead.
Works with
WordPress, Google Ads, Meta Ads
Fill in before sending
[site][contact page URL][average job value][timezone offset, e.g. +03:00][currency]
Not every form lead becomes a paying job. I want Google Ads and Meta to learn from the jobs we actually booked, not just form fills.
1. On [site], list the Contact Form 7 forms and read the fields of the main lead form. Then read the live page [contact page URL] and look for hidden inputs in the HTML. Is there a hidden field capturing the gclid from the landing URL, and one capturing the fbclid (or the _fbc cookie)? If not, stop and tell me exactly which hidden fields to add and the small script that fills them from the URL, before we continue. Do not change anything on the site.
2. In Google Ads, list the conversion actions and their settings. Is there an "Import from clicks" action for booked jobs? Show its counting type, default value and click lookback window, and tell me whether enhanced conversions for leads is switched on at account level. If no suitable action exists, preview a new one: name "Booked job", type UPLOAD_CLICKS, category PURCHASE, default value [average job value]. Create it only after I approve.
3. Find my Meta ad account and the pixel to send server-side events to.
4. I will paste the booked jobs from the last 30 days: job ID, name, phone, email, gclid, fbclid (if captured), booking date and time, job value. Validate the list and flag:
- rows with no gclid (these cannot go to Google),
- clicks older than the action's lookback window or 90 days,
- rows with no email, no phone and no fbclid (Meta cannot match them),
- Meta events older than 7 days (Meta rejects most server events past that, so tell me if I need a weekly routine instead),
- duplicate job IDs.
Where an fbclid exists, build the fbc value as fb.1.<click time in milliseconds>.<fbclid>.
5. Prepare the uploads. Google: gclid, conversion datetime with timezone [timezone offset, e.g. +03:00], value, currency [currency], order_id = job ID. Meta: event_name Purchase, value, currency, email and phone (hashed by the tool), fbc where available, action_source system_generated, event_id = job ID. Run both tools in preview mode first and show me the row counts per platform plus every skipped row with the reason. For Meta, offer to send one row with a test event code before the full batch. Upload only after I confirm.
Finds page-one pages that get impressions but few clicks, compares them to your site-wide CTR, and rewrites their meta title and description around the queries that actually bring them traffic.
When to use itWhen your pages rank on page one and get impressions but few clicks, so your titles and descriptions are probably not convincing.
Matches GA4 landing-page performance against your WordPress menus, flags valuable pages missing from the navbar, dead weight and broken links, and proposes a leaner main menu.
When to use itWhen your site menu feels cluttered or outdated and you suspect it does not point visitors to the pages that actually bring conversions.
A plugin-by-plugin action list that flags outdated, duplicate and conflicting plugins and double-firing tags.
When to use itWhen your WordPress site has too many plugins, updates piling up, or you fear duplicate tags are inflating the conversions your ads optimize toward.