Know which ad brought each paid booking.
When a client pays for a booking or a deposit online, MIQAS credits it to the ad that brought them, sets it against your spend on Meta, TikTok and Snapchat, and keeps a record of the clients who come back. It follows bookings that end in an online payment or a purchase event on your site, so every number starts from money that actually arrived.
The bookings are paid, and the cost per job is still worked out by hand
A cleaning company runs Snapchat and Meta, and clients book and pay a deposit on its website.
Each platform reports its own conversions, the payment provider lists the deposits that actually cleared, and the two lists never quite line up.
So at the end of the month somebody divides the spend by the bookings that paid, by hand, and that figure becomes the cost per job everyone argues about.
The clients who book a second and a third time are known to the owner and the team that serves them, and to no report.
Budget follows whichever platform tells the better story, and the clients who return are never traced back to the ad that first found them.
From the ad to the client who books again
A booking paid online, followed in 7 steps, in the order a service business sees them.
The ad is clicked
The MIQAS pixel on your site keeps the click ID.
The booking page
Visits and top pages come from the pixel.
The booking is paid
A deposit or a full payment confirmed online, or a purchase event your site sends, counts as an order.
Credited to the ad
The booking goes to the last ad click before it; a direct visit does not take the credit.
Sent back to the platforms
The purchase goes to Meta from your server, and to TikTok and Snapchat once you switch sending on.
The client record
On the Pro plan, each client shows their bookings, total spent and last booking.
The client books again
The record shows who is new, who has come back, and who has been quiet for 45 days.
A record for every client who books
A pipeline built for chasing enquiries misses what matters to a business whose clients pay online and return. The record that helps is the client: what they booked, what they spent, which ad first brought them, and whether they are coming back. MIQAS builds it from the paid bookings, so nobody has to type it in.
- A client record created from every paid booking and sign-up, without anyone typing it
- The platform and campaign that first brought the client
- Bookings, total spent and the date of the last booking
- Whether the client is new, repeat, a VIP after 4 bookings, slipping away after 45 days or lost after 120
- Notes, a status and an owner on each client
- A consent log for each client
- Available on the Pro plan, switched on by the workspace owner
Spend and paid bookings in one view
Per-campaign results combine what each ad platform reports with the bookings your site recorded for that campaign, so the spend and the money that came in sit on the same row.
Meta
Spend, clicks, orders, revenue and ROAS for every campaign, with the top creatives.
TikTok
The same view, with the columns TikTok reports.
Snapchat
The same view, from the Growth plan.
Your booking site
The MIQAS pixel works on any site, or connect your store if you sell packages through Salla, Zid, Shopify or WooCommerce.
Paid bookings go back to the platforms from your server
Each paid booking is sent from your server to Meta, and to TikTok and Snapchat once you switch sending on, with identifiers hashed before they leave MIQAS. The platforms then receive stronger first-party signals, built from payments that really happened rather than from page views. What each platform does with them is its own decision.
- Meta
Purchases
- TikTok
Purchases
- Snapchat
Purchases
- Meta
- Always on.
- TikTok
- Once sending is switched on.
- Snapchat
- Once sending is switched on, from the Growth plan.
Who looks at what
Owner
- Spend, booking revenue credited to ads and blended ROAS on the ROI tab
- Average cost per sale, which here is the cost of each paid booking
Marketing manager
- Ad Campaigns by platform: spend, clicks, orders, revenue and ROAS
- The top creatives on each platform
Bookings manager
- Sessions, paid bookings, average booking value and refunds
- Peak hours and top cities
Finance
- Refunds set against revenue
- What discounts and comped bookings cost
The numbers behind a paid booking
- Paid bookings
- Bookings that ended in an online payment, from your site, a store connection or a purchase event.
- Booking revenue
- What clients paid, after discounts and refunds.
- Average booking value
- Booking revenue divided by paid bookings.
- Revenue per campaign
- What the ad platform reports for the campaign, with the paid bookings your site recorded under that campaign added where the platform shows none.
- ROAS per campaign and blended
- Revenue divided by spend, for each campaign and across every platform you run.
- Average cost per sale
- Ad spend divided by paid bookings: your cost per job, without the spreadsheet.
- Refunds
- Shown against revenue, so a cancelled booking does not flatter the month.
- Peak hours and top cities
- When and where your paid bookings come from.
- Bookings and total spent per client
- In the client record, on the Pro plan.
How the month looks before and with MIQAS
Before
- Each platform and the payment provider report different numbers.
- Cost per job is worked out by hand once a month.
- Nobody can say which campaign a deposit came from.
- Repeat clients are known to the owner and to no report.
With MIQAS
- Spend and paid bookings side by side, in your currency.
- Cost per paid booking on the ROI tab whenever you open it.
- Each paid booking credited to the last ad click before it.
- A record of every client and whether they are coming back, on the Pro plan.
Whether your campaigns are run in-house or by an agency, MIQAS gives your business its own view of what happens between advertising spend and the bookings that are actually paid.
How service businesses use it
Cost per job without the spreadsheet
- The problem
- Spend is divided by paid bookings at the end of the month, by hand.
- What MIQAS does
- Connect your ad accounts and let MIQAS set their spend against the bookings that were paid.
- What becomes visible
- Average cost per sale and ROAS per campaign, whenever you look.
The deposit page
- The problem
- Deposits are paid online, and each platform's conversion count overlaps with the others.
- What MIQAS does
- Send the deposit as a purchase event, and MIQAS credits it to the last ad click.
- What becomes visible
- Deposits by campaign, in your currency.
Packages sold through a store
- The problem
- Packages are sold through an online store, and the ad that sold each one is unclear.
- What MIQAS does
- Connect Salla, Zid, Shopify or WooCommerce with the pixel on the store; orders arrive and are matched to the ad click before them.
- What becomes visible
- Revenue and ROAS for each campaign.
The client who books again
- The problem
- Repeat clients are known only to the owner.
- What MIQAS does
- Switch on the client record on the Pro plan, and it builds itself from bookings: count, total spent and last booking.
- What becomes visible
- Who is coming back, who has become a VIP and who is slipping away.
The Monday look
- The problem
- Management asks how last week's bookings went.
- What MIQAS does
- Switch on the weekly summary email in Settings and it goes out on its own, plus a PDF report from the Growth plan.
- What becomes visible
- Spend, paid bookings and revenue in one place.
What connects to your bookings
MIQAS pixel
Keeps the click ID, and records a purchase when your booking page sends the purchase event.
Salla
For packages sold through a Salla store: orders by webhook or API.
Zid
Installed from the Zid App Market.
Shopify
Orders by webhook.
WooCommerce
Orders by webhook, for WordPress sites.
Webhook and API
Send paid bookings from your own system, on the Pro plan.
Meta
Ads and spend; purchases sent back.
TikTok
Ads and spend; purchases sent back once switched on.
Snapchat
Ads and spend from the Growth plan; purchases sent back once switched on.
CSV and manual entry
Bring in past bookings or a one-off sale.
Questions from service business owners
Which bookings does MIQAS follow?
Bookings that end in an online payment or a purchase event on your site, deposits included. Each one counts as an order, so it appears in Website, Ad Campaigns and ROI like any sale. A booking agreed by phone and paid in cash is outside what MIQAS sees on its own; you can add it by hand or by CSV, and it arrives without an ad attached.
Does MIQAS replace my booking software?
No. MIQAS does not take bookings, send reminders or keep a calendar. It measures which ads brought the bookings that were paid, alongside whatever tool takes the booking today.
How does MIQAS decide which ad gets the credit?
It gives each paid booking to the last ad click before it, identified by the click ID, with UTM tags and then the referrer as fallbacks. A direct visit never takes the credit away from an ad click that came before it.
Do enquiries and quote requests show up too?
Not as a pipeline today. MIQAS follows a booking once it is paid. An enquiry or quote form on your site can be sent to the ad platforms as a lead event, but it does not become a lead you move through stages inside MIQAS.
What does the client record show?
On the Pro plan, each client shows their bookings, total spent and last booking, the ad that first brought them, and whether they are new, repeat, a VIP, slipping away or lost. It builds itself from paid bookings and sign-ups once the workspace owner switches it on.
Which ad platforms are covered?
Meta and TikTok on every plan, and Snapchat from the Growth plan. For each campaign you see spend, clicks, paid bookings, revenue and ROAS side by side.
See which ads brought your paid bookings.
Tell us how your clients book and pay, and we will show you how MIQAS credits each booking to the ad behind it.