Recommendations that show their own hit rate

Two things. The first is that every rule keeps a public record of its own outcomes: how often it fired, how often you acted on it, how often the follow-up concluded, and how often the result was a win. That record orders the feed, so a rule that keeps being wrong sinks. The second is that the four silos share one queue and one verdict definition, so a tracking fix and a paid move are comparable rather than living in separate tools with separate notions of success. Most engines can tell you what they recommend. Very few can tell you how often they have been right.

Four silos. GEO covers AI visibility work: crawl access, extractability, citation gaps, sentiment. SEO covers keyword and content opportunities. Paid covers spend allocation, saturation and creative. Instrumentation covers tracking defects, and it is fed directly by the Trust Center audits and investigations, which is the join most stacks do not have: the tool that finds your broken tag is usually not the tool that queues the fix.

A strategy is one active, time-bounded plan per property: an objective of leads, revenue or brand, a target metric with a value, a budget, priority channels, and the personas and competitors you already defined elsewhere. The weekly synthesis paces against it instead of narrating metrics in isolation. The target metric comes from a fixed list of six because the pacing has to be able to compute progress period-to-date from data that exists. Free text would let you set a goal that silently never gets scored. Paid revenue is named that way for the same reason: the only revenue figure the pacing can read is the paid platform summary, so a goal set against total revenue would be judged on the paid slice of it.

No. Every recommendation needs a human to plan it, and the three actions are Plan, Done and Dismiss. The feed proposes the move; nothing changes in an ad account without you. That is a deliberate line, not a missing feature: an engine that publishes its own hit rate is an engine that admits it is sometimes wrong, and something that is sometimes wrong should not have your card.

Optimize and above. It sits at the same tier as the AI engine probes because Beacon reads probe output, and gating a consumer above its producer means it runs with nothing to read. Measure gives you the measurement layer: first-party tracking, deduplicated attribution, AI visibility and SEO keyword intelligence. Optimize is where the system starts telling you what to do about it.