Mountain Stone.

The Google System.

The Playbook / System 07 · Channel

The architecture that treats Google as the demand-capture engine.

System
07/10
Class
Channel
Governs
Demand capture
Swept
On rhythm
The Playbook
Paying twice

Google captures demand. It doesn’t need to create it.

Some of that demand comes from work the brand has already done. Some of it already exists in the market. Someone searching for a product or solution is already telling us what they want.

Google’s job is to catch that intent and make sure it lands somewhere useful.

THE COST OF CONFUSING CAPTURE WITH CREATION

Because Google sits close to the decision, it can look like the source of demand rather than the place it surfaced.

That matters when the business decides where the next dollar belongs. A channel that captures demand efficiently can be extremely valuable without being the reason that demand existed.

Capture is valuable. It just needs to be understood for the job it is doing.

The principle

Capture, do not create.

Google’s job is to be ready when someone starts looking. That intent may have been created by the brand or may already exist in the market. The account has to understand what the search is telling us and meet the customer there.

The system

Five campaigns. Each for a different kind of intent.

01
Brand Search.They already know the brand. Make sure they find it when they come looking.
02
Non-Brand Search.They know what they want, but may not know who to buy it from. Meet the search with a reason to choose this brand.
03
Performance Max.Product intent gets picked up across Google’s inventory, with the feed doing much of the work.
04
Demand Gen.The exception. Google can also reach people earlier, before the intent is fully formed. Usually run on exploratory budgets.
05
Remarketing.They’ve already shown interest. The next message should reflect what they already know, not start the conversation over.
Where the Google System comes from

The search tells us how ready the customer is. The Spine helps us decide what they need to hear when we meet them there.

Financial Architecture tells us what that demand is worth, so the account can capture it without paying more than the economics support.

In operation

The search tells us
what the customer is ready for.

Someone searching the brand by name is in a different place from someone searching the category for the first time. Google gives us that signal before they ever reach the site.

The intent routeFrom search to page
01
The search
What they search tells us what they are already looking for.
02
The route
We meet them at the level of readiness that search reveals.
03
The next step
The page continues the conversation from there instead of starting it over.
THE CUSTOMER SURFACE · READINESS

A broad search may need more context. A specific product search can move much closer to the decision.

The experience starts from what the customer already knows.

THE TEAM SURFACE · SIGNAL

Search also shows demand moving through the market. Branded search can tell us whether interest created elsewhere is turning into people actively looking for the brand.

Google captures intent and shows us how that intent is changing.

The test

Three questions.

Start with how the account handles intent.

01Is Brand Search separated from Non-Brand so each can do its own job?
02When someone searches the category instead of the brand, do they land somewhere that matches what they’re actually looking for?
03Can the team tell which parts of Google are capturing existing demand and which are bringing new customers into the brand?

If those answers aren’t clear, different kinds of intent are probably being treated the same way.

When Google catches

Brand Search protects demand already attached to the brand. Non-Brand meets people who are already in the market and gives them a reason to choose it.

The better the account understands the search, the better it can meet the customer at their readiness.

The Google System
The brands that compound meet people at the level of intent they arrive with.