CodeLaw Booking Orchestrator
The tool Lead Pancakes uses to tell Google Ads which ad clicks became paying customers.
The problem
Google Ads counts clicks and form fills. A local service business, such as a cleaner or a landscaper, needs to know something else: which ads brought jobs that were booked and paid. Without that, the ad budget goes to the clicks that look busy, not to the ones that bring customers.
How it works
- A customer books a service on the client's own website.
- The booking is recorded in the client's customer records (CRM), together with the ad that brought the customer: the Google click ID, the campaign and the landing page.
- Google Ads learns the result: the booking goes to the client's own Google Ads account, and later the amount the customer paid for the job.
How it is built
- Infrastructure as code. Its hosting, database and secrets are declared in Terraform, so every change is code that is reviewed and versioned.
- The customer's consent choice is respected. Each booking carries the advertising consent the customer gave on the client's website; email and phone go to Google Ads only as SHA-256 hashes, and only when that consent allows it.
- Every job is counted once. One Order ID follows a job from the booking to the payment, so Google Ads never counts the same job twice.
Who uses it
Only Lead Pancakes staff use the CodeLaw Booking Orchestrator: for the agency's clients, on the clients' own Google Ads accounts linked to our manager account 182-588-6119. Clients get the results and reports; they do not get access to the tool, and it is not sold or offered to anyone else. The tool is built and run by CodeLaw, the company behind Lead Pancakes.
Privacy, terms and contact
How the tool handles personal data is described in our Privacy Policy; its use is covered by our Terms of Service. Questions: info@leadpancakes.com, or book a 15-minute call.