Build audiences from an agreed quality definition

When to use it

An approved audience test needs better business-quality input starts this workflow. Use eligible first-party account or customer evidence to shape audiences, with the quality model and platform controls explicit. The intended output is an audience receipt with quality definition and actual control limitations. A useful receipt names the accountable person and the next action; it should make the commercial decision easier to inspect.

This is an original GTMhub reference design. It explains how we would run the job, with tools selected for the company's existing stack. It is not presented as completed client delivery or measured commercial performance.

Inputs and decision boundaries

Confirm permitted first-party data, quality definition, eligibility and platform settings. Keep the original source and observed date alongside each fact. Missing context stays unknown until it is resolved. Facts, interpretations and proposed actions should remain distinguishable in the handoff.

Your company brain holds the approved rules and proof; the live system holds current account state and ownership. Read both before making an operational change. Assign an exception owner before launch so an uncertain case has somewhere useful to go.

Run the job

1. Define the business event and quality cohort.
2. Exclude records that do not meet permission or commercial rules.
3. Check audience matching and the distinction between signal and targeting.
4. Test coverage and mature outcomes before expanding.

At the decision gate, ask: Is the data eligible and the platform behavior suitable for the intended test? If the answer is no: repair the cohort or use another audience approach. Only the supported path proceeds to its output. A stopped job should preserve the reason and what would let an owner resolve it.

The output to inspect

Failure and recovery

The material failure to watch is this: an audience signal is described as a hard targeting or remarketing boundary. Stop that path and preserve the underlying evidence. Repairing a field or a source is different from changing the commercial rule; record which decision was made.

If a connected system fails, keep the original request or event and expose its unresolved state. Retry only the incomplete action, with a stable event key where writes are involved. Do not let a retry create a second owner task or bypass a previous exclusion.

A signal is not a targeting boundary

+Check the actual campaign settings and eligibility. In Performance Max, an audience signal guides learning rather than restricting delivery to that audience. A quality cohort is an input to test, not proof that only those people saw the campaign. Read Google's audience-signal guidance.

+## Test before making it live

Replay a supported case, an incomplete case and the failure described above. Where the job writes a record or creates a task, replay the same event twice and inspect the result. Check that the exception owner can understand the hold reason without reconstructing every step.

Judge the result

Track eligible match coverage and qualified pipeline from a mature test cohort. Record the sample, dates and definitions before evaluating a change. Operational success shows that the job behaved as designed; commercial outcomes need their own mature evidence.

Return reviewed corrections to the company brain with the decision date and rule version. Keep the original observation available. The decision register records what changed and why, while the GTM brain guide explains how the job fits into one company system.