What is a signal contract?

The frozen specification of which conversion events a Dynamic Ad engagement tracks, how those events deduplicate across browser and server, what counts as qualification, and how the events route into the operating record. Set at engagement start; not changed mid-cycle.

Why freeze the signal contract for a full cycle?

Because the make-good comparison only works if the comparison terms are stable. A mid-cycle signal redefinition invalidates the cycle's read against the baseline. Operators can renegotiate the contract at cycle close; not before.

Who owns the signal contract?

The Infra layer ships it at engagement start. Two operators countersign before the operation runs the first variant. The Analytics layer reads against it at every cycle close. Changes require a new contract for the next cycle, logged in the operating record.

Signal Contract

The frozen specification of which conversion events are tracked, how they are deduplicated across browser and server, and what counts as a qualified outcome.

Common questions

What is a signal contract?: The frozen specification of which conversion events a Dynamic Ad engagement tracks, how those events deduplicate across browser and server, what counts as qualification, and how the events route into the operating record. Set at engagement start; not changed mid-cycle.
Why freeze the signal contract for a full cycle?: Because the make-good comparison only works if the comparison terms are stable. A mid-cycle signal redefinition invalidates the cycle's read against the baseline. Operators can renegotiate the contract at cycle close; not before.
Who owns the signal contract?: The Infra layer ships it at engagement start. Two operators countersign before the operation runs the first variant. The Analytics layer reads against it at every cycle close. Changes require a new contract for the next cycle, logged in the operating record.

Every paid-growth operation runs on signal. Most operations run on whatever signal the platforms send by default. The Dynamic Ad operating system runs on a signal contract: a written specification of every event the operation reads, how it gets to the operation, and what it means.

The contract specifies: the conversion events (lead, qualified-lead, customer, retained-customer, churned), the source of each (browser Pixel, server CAPI, CRM webhook, offline upload), the dedup key (event_id, hashed email, gclid), the qualification rules (corporate domain, spend tier, role title), and the routing into the operating record. The Infra layer ships the contract at engagement start.

The contract is frozen for the duration of a cycle. Mid-cycle signal redefinitions invalidate the cycle's read against the make-good baseline; the comparison only works if the comparison terms are stable. Operators can renegotiate the contract at cycle-close; not before.

Example

An engagement starts. The Infra layer ships a signal contract: 'Lead' = audit-form submission with corporate domain + spend tier ≥ 5k-15k; deduplicated across Meta CAPI (event_id) and GA4 (audit_submitted) by hashed email. 'Qualified-lead' = audit form submission + 30-minute call held. 'Customer' = engagement letter signed. Every conversion event in the operating record routes against this contract; changes require a new contract for the next cycle.

Always on · Algorithm-led · Human-approved

Walk this operation against your account.

Thirty focused minutes with one of the founders. We map Signal Contract against your stack and tell you which entry point fits your stage.

Book a 30-minute call →Or write us