Performance Max for service businesses: the Da Life Outdoors playbook

Service businesses get told Performance Max isn't for them. "It's a product feed thing," "you need ecommerce data," "the algorithm needs hundreds of conversions to work." All three are wrong, or at least incomplete. I ran Performance Max for a Kaua'i tour operator for 6.5 months and pulled 712% ROAS — $8,658 in spend returning $56,357 in tour bookings. This article is the playbook.

The setup (in plain English)

The brand: Da Life Outdoors, an adventure tour operator on Kaua'i. Two flagship products — a waterfall rappel ($399) and a hike-and-swim ($371). Both are seasonal, weather-dependent, and require booking through a third-party reservation platform. No physical product, no shipping, no inventory feed.

The challenge: Google's Performance Max documentation assumes you have a Merchant Center feed. We didn't. We had two services with two booking pages and a calendar.

The structure that worked

I split into two separate Performance Max campaigns — one per service. Not one campaign with two asset groups. Two campaigns. This is the most important decision in the entire build.

Why: Performance Max optimizes the budget across asset groups inside a campaign based on its own logic. If your two services have different margins, different seasonality, or different audience overlap, one will starve the other. Splitting them lets you control budget and bid strategy per service.

The five decisions that drove the numbers

1. Conversion event = booking, not lead form

Most agencies set the conversion to "form submission" or "page view of the booking calendar." That's a soft signal, and Performance Max will happily over-optimize toward it. The actual booking confirmation page (with order ID in the URL) became the conversion event. Smaller volume, much cleaner signal.

2. Conversion value = average booking value, dynamic

Hard-coding $399 as the value lies to the algorithm when you have group bookings, add-ons, or upsells. We sent the actual transaction value via the booking platform's webhook into Google Ads as a dynamic conversion value. ROAS tracking became real instead of fictional.

3. Audience signals were aggressive

Performance Max audience signals are hints, not hard targeting. We used them anyway: custom segments built from people searching "things to do Kaua'i," "waterfall hike Kaua'i," competitor brand names, and tour operator categories. Plus a customer match list of past bookers (for lookalike-style expansion). Without this, Performance Max defaults to broad demographic guesses.

4. Asset group creative was specific to the service

Generic "Kaua'i adventure" headlines pulled bad CTR and worse conversion rate. Switching to product-specific copy ("Rappel a 60-foot Kaua'i waterfall") cut CPL from $89 to $54 in the first 14 days. The algorithm rewards specificity because the audience does.

5. We ran final URL expansion = OFF for the first 60 days

Final URL expansion lets Google send traffic to any page on your site that it thinks fits the query. For a service business with a single booking page per product, this scatters traffic to your blog, your About page, and your contact page — none of which convert. We turned it off until we had 100+ conversions in the campaign, then re-enabled it cautiously.

What didn't work

Two things failed early and we cut them:

• Single Performance Max campaign with multiple asset groups. The waterfall asset group consumed 78% of spend in the first week because its conversion rate was higher. The hike asset group never got enough budget to find its audience. Splitting solved it.
• Demand Gen as a complement. We tested Demand Gen alongside PMax to seed the upper funnel. Spent $1,200, got 4 bookings. Killed it. For low-frequency, high-consideration purchases like a $400 tour, search and PMax do the work; visual-discovery channels don't.

What this means for service businesses generally

The transferable lessons, in order of importance:

1. One campaign per service. Not one campaign with multiple asset groups.
2. Conversion = transaction, not form fill or page view.
3. Conversion value = dynamic, not fixed.
4. Audience signals = aggressive and specific. Broad lookalikes default to broad waste.
5. Final URL expansion off until you've got conversion volume.
6. Specificity in creative beats polish. "Rappel a 60-foot waterfall" beats "Adventure of a lifetime."

If you run a service business and you're either avoiding Performance Max or running one and watching it spend without returning, this is the framework I'd run on your account first. The full Da Life case study lives here. If you want me on your account, The Audit is $497 and we'll find out where the leak is in 30 minutes.