Overview
Set up one Growth Engine job with a clear goal, usable context and a review owner. Start in Copilot so you can inspect proposed work before expanding automation.
This guide covers one job, not a complete rollout across every channel. For the product's workflow and trade-offs, read the Growth Engine overview.
Before you begin
Confirm Growth Engine access for the intended store.
Have access to the relevant connected accounts and the permissions needed for the chosen work.
Prepare approved assets, brand guidance, offer terms and any strategy documents the job needs.
Identify who will review proposals and the timezone for scheduled work.
Use the Growth Engine jobs reference to choose a work area and the modes and guardrails reference to understand permissions.
Warning: Do not assume that a newly enabled job is review-only. Check campaign modes, shared action permissions and limits before enabling work.
Steps
Describe the overall marketing goal. Include the desired outcome, target, timeframe, budget boundaries, priorities and exclusions in the goal or master instruction.
Describe each relevant channel's role. Include different expectations for prospecting and retargeting, or branded and non-branded search, where they matter.
Check the saved measurement definition. Match the metric calculation, target, dates, channel coverage and attribution settings to the intended goal. Where available, use How your goal is measured.
Add the job's business context. Include current brand guidance, approved assets, the marketing calendar and relevant product or inventory constraints.
Verify access to linked context. Ask the CMO a specific question about a linked document's contents. A saved link alone does not establish that its contents are readable.
Open Jobs.
Choose one job. For example, select Launch and test new ads when approved creative is ready for testing.
Tailor the job instructions. Replace generic thresholds and examples with your intended workflow and success criteria.
Select the intended connected accounts. Check the account identity and any publishing configuration required by the chosen work.
Choose the campaign or resource scope. Include only the work you intend this job to manage.
Set the selected campaign scope to Copilot. This creates a review point for supported proposed changes.
Review the action permissions. Keep the intended changes review-required and account for settings shared with other jobs. If the available controls cannot express the intended boundary, stop before enabling the job.
Configure the applicable guardrails. Use the limits appropriate to the chosen work rather than relying on restrictions written only in a prompt.
Assign the job owner. Use the person responsible for reviewing the work.
Configure the schedule. Check the intended cadence, run time and timezone in the job schedule or Agenda.
Save the configuration. Check the saved values before enabling the job.
Enable the job. Do this only after its saved scope and permissions match your intent.
Inspect the first actual run. Confirm which job ran, what ticket appeared and who received the review request. Do not assume enabling several jobs runs all of them immediately.
Verify the result
You should be able to identify the saved goal, job owner, schedule, managed scope and actions that require review. The first run should have a traceable outcome, such as proposed work or a reported blocker; setup alone does not guarantee an immediate recommendation.
Use Review proposed work in Growth Engine before approving the first change.
If the job does not produce the expected work
Use Growth Engine work is missing, stale or not completing to check missing runs, review routing and action results.