Performance agency campaign onboarding
Capture campaign context, goals, control rules and approval responsibilities in one project brief.
- Industry
- Agencies
- Team
- Client services, Marketing
- Use case
- Client onboarding, Client portals
- Tags
- Engagement planning Approval workflow
- Includes
- 1 app
Template preview
Included items
-
Onboarding Client app
App · Primary app configured for the performance-agency profile
Overview
What this template supports
The Onboarding Client app guides the client through four steps: campaign context, performance goals, control rules and the approval process. It supports draft progress, project attachments, submission and a response when the delivery team requests clarification.
- Four-step campaign brief
- Draft progress and final review
- Project reference attachments
- Clarification and resubmission workflow
How to use this template
-
Define the project workflow
Choose the client inputs, delivery responsibilities and decisions this project needs.
-
Configure the audience
Confirm the Client and Admin responsibilities, project context and visible information.
-
Review access and content
Check project permissions, named owners and configured content before using the app with a client.
Frequently asked questions
Who is this configuration for?
Performance-agency clients and account teams working together on campaign delivery.
Which information does the brief collect?
Campaign context, performance goals, control rules and the approval process, with fields configured for the performance-agency profile.
Can the client save before submitting?
The Client app provides draft saving and progress through the brief steps.
Can supporting files be included?
The onboarding brief has a project attachment field and shows the allowed formats, file count and size limits. Stored attachments offer downloads.
What happens when an answer is unclear?
The Admin workspace can request clarification; the Client brief displays the request and a path to update and resubmit.
Who reviews the submitted brief?
The configured delivery team reviews the project brief. Existing project access and roles determine who can take the approval action.