Scope
This guide covers daily operation for AI Studio: Landing Builder. Availability depends on your tenant package, role and configured providers.
Purpose
Create landing-page systems from grounded briefs.
Generate, edit, preview and review page versions.
Before you start
Correct tenant and project selected
Required source or provider is available
An accountable owner is identified
Test data can be separated from live activity
Procedure
- State the operating objective and the record, audience, campaign or project in scope.
- Generate, edit, preview and review page versions.
- Inspect the current status and supporting context before changing anything.
- Account for system behaviour: Queue build tasks and reuse approved modules.
- Resolve failures, missing data or approval requirements before continuing.
- Close the loop: Review page status, engagement and conversion context.
Verify the result
Review page status, engagement and conversion context. Confirm that the intended record, state, run or report is visible to another authorised operator and that its next owner is clear.
Completion checkpoint
The capability is in the intended state, evidence is current, exceptions are owned and the next action can be understood without a separate status message.
Controls and limitations
Require brand, content and publish approval. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.