Overview
Review a Growth Engine proposal before approving it, then confirm what actually ran. This guide separates the decision to approve, the platform's execution result and the later business outcome.
Before you begin
Have access to the ticket and the connected platform needed to verify the result.
Know the intended goal, measurement definition and current offer or creative requirements.
Confirm that you are the appropriate reviewer for the proposed change.
Warning: Approval can cause a live change or spend. Some effects cannot be fully reversed. Never repeat an action just because a ticket's status is unclear.
Steps
Open the relevant ticket on the Board.
Read the hypothesis and evidence. Check the account, dates, metric and scope behind the recommendation.
Inspect each proposed action. Check the exact target, proposed values, assets, destination, publishing effect and budget impact.
Check the current platform state. Determine whether the proposal is still needed or the work was already completed manually.
Resolve any uncertainty in the ticket conversation. Ask for the missing evidence or a specific revision before making a decision.
Approve or reject the proposal. Approve only the work you intend to authorize. If rejecting it, explain the business reason, such as an expired offer or manual completion. Do not describe manually completed work as a failed strategy.
Inspect the result of each action. Distinguish succeeded, failed, pending and unverified work rather than treating a whole ticket as one result.
Verify consequential changes in the connected platform. Check the actual budget, status, destination or published asset, as appropriate. A created campaign is not necessarily active or delivering.
Review the applicable follow-up. Use the ticket's actual timing and observations to assess the outcome after execution.
Verify the result
You should be able to explain what you approved, which actions succeeded and which remain unresolved. A board position or approval is not proof of execution. If only some actions succeeded, reconcile them before retrying the others.
When evaluating results in Performance, compare the same dates, channels, account scope, currency, metric definition and attribution model/window. Return on ad spend (ROAS) is attributed revenue divided by ad spend, not profit. A stronger result after moving to Autopilot does not establish that the mode caused it.
Learnings stores observations for future work. It is not a guaranteed per-ticket incremental revenue or profit report, and one short-term result should not become a universal rule.
If work fails or remains unclear
Use Growth Engine work is missing, stale or not completing before retrying. For broader action errors, see My Moby action failed or didn't run.