Campaign operations on Asana
An assessment of Asana against the group's ad operations requirements: fit, plan, integrations and the points to confirm before a quote.
01Captured use case
A media agency group runs paid media campaigns for brand clients across search, social, display and video, in several markets. Each campaign passes through five teams and six systems.
The group wants one platform for campaign operations: structured briefs, standard workflows, auditable approvals and live status for clients, leaders and finance.
- Brief-to-kickoff cycle time
- Hours spent compiling status
- Approval disputes
- Over- and under-allocated staff
- Scale
- 1,000+ users in five teams, across several markets
- Teams
- Client service, planning, buying, trafficking, creative studio
- Client reports
- Daily pacing and weekly campaign reports, built from media platforms and signed off before release
- Leadership
- Weekly status across clients and markets; read only
- Finance
- Delivered-versus-booked status per campaign for client billing and month-end close
- Systems
- Slack and Teams for collaboration; HubSpot and Salesforce for clients and deals; ADvendio for orders; Mediaocean for plans, buys and billing
- Policy
- Group single sign-on, automatic provisioning, SIEM logging, data held in a set region
- Out of scope
- Pacing and performance data, which stay in media platforms; process design and build plan
Brief
Client service captures objectives, budget, channels, markets and dates.
PainBriefs arrive incomplete. Planners chase details.
Plan
Planners build the media plan and staff the campaign. The client approves.
PainEach campaign type starts from scratch. Staffing relies on instinct.
Buy and traffic
Buyers book media in Mediaocean. Traffickers set up placements and creative.
PainHandoffs between teams are manual.
Review
Creative and client teams review assets before launch.
PainFeedback sits in email and chat. Sign-offs leave no trail.
Report and close
Pacing and campaign reports go to the client. Finance bills delivered media and closes the month.
PainNo cross-campaign view. Status is compiled by hand.
Can Asana run this, on which plan, and what does it take to connect the six tools around it?
02Client summary
Yes, on the Enterprise plan.12 of 14 requirements met. Video proofing is partial; UK data location is open.
Enterprise with the Compliance Management add-on.Advanced lacks capacity planning, single sign-on and SCIM. The add-on exports the audit log.
Four tools through Asana apps; two need API builds.Slack, Teams, HubSpot and Salesforce connect natively. Mediaocean and ADvendio have no Asana app.
Five client questions; two may add an add-on.Data residency if a set region is required (Q2). Timesheets and Budgets if a gate needs several approvers (Q3).
03Requirement fit
Lowest plan is the first Asana plan that documents the capability.Met documented on that planPartial documented with a limitOpen needs a client answer
| ID | Requirement | Asana capability | Lowest plan | Status | Source |
|---|---|---|---|---|---|
| Intake and delivery | |||||
| R01 | Structured brief for every campaign | Forms | Starter | Met | 1 |
| R02 | Brief routed by campaign type, channel or market | Forms branching | Advanced | Met | 1, 2 |
| R03 | Repeatable framework per campaign type | Project templates | Starter | Met | 1 |
| R04 | Standard lifecycle stages with business logic | Workflow builder | Starter | Met | 3 |
| R05 | Automatic handoffs between planning, buying and trafficking | Rules | Starter | Met | 1, 3 |
| Review and approval | |||||
| R06 | Timestamped, auditable sign-off at each gate | Approvals | Advanced | Met | 4 |
| R07 | Creative review and markup in the platform | Proofing | Advanced | Partial | 4 |
| Visibility and resourcing | |||||
| R08 | Status of every campaign in one view | Portfolios | Advanced | Met | 1 |
| R09 | Roll-up status for leaders and finance, without manual work | Portfolio dashboards | Advanced | Met | 5 |
| R10 | Resource visibility before work is committed | Capacity planning, placeholders | Enterprise | Met | 6 |
| Security and admin | |||||
| R11 | Sign-in through the group identity provider | SAML single sign-on | Enterprise | Met | 7 |
| R12 | Joiners and leavers provisioned automatically | SCIM provisioning | Enterprise | Met | 8 |
| R13 | Full activity log exported to the group SIEM | Audit Log API | Enterprise + add-on | Met | 9 |
| R14 | Data held in a region set by group policy | Data residency | Enterprise + add-on | Open | 10 |
NoteSources differ on R02. The help centre lists forms branching from Starter; the pricing page lists it under Advanced. The stricter source is used. The plan is unaffected.
- Forms branching
- Up to five levels of branches.2
- Single sign-on
- Okta, Microsoft Entra, OneLogin, Google Workspace and others. Session timeout from 1 hour to 30 days.7
- Provisioning
- Joiners and leavers synced from Okta, Microsoft Entra ID, OneLogin or Google Workspace.8
- Audit log
- Splunk and Panther integrations listed. Events kept 90 days; longer retention sits in the SIEM.9
04Release check
Three releases read: the September 2026 notes,17 the Fall 2026 release18 and the Spring 2026 release.19 Two findings change this scope.
Several approvers on one item
Listed under the Timesheets and Budgets add-on, sold with Starter, Advanced and Enterprise. Added as Q3.17, 1
@Asana in Slack
Available on all plans from September 2026. Slack plan note updated.17
No other finding changes this scope.
05Plan and price tier
Data residency: if the client requires it
Advanced falls short
Capacity planning, SAML single sign-on and SCIM provisioning all start on Enterprise. The group requires all three, so no lower plan qualifies.6, 7, 8
One add-on closes the gap
Enterprise has no Audit Log API. Compliance Management adds it; Enterprise+ includes it. The add-on is the smaller step when data location is not required.9, 1
Data location sets the route
Data residency is an Enterprise add-on or part of Enterprise+. The client's answer to Q2 picks the route below.10
Seat mix lowers the cost
Leaders and finance users who only read take view-only licences. Each build runs on its own service account, apart from named users. Both are Enterprise features.1
| If the client answers Q2 with | Quote |
|---|---|
| No set region | Enterprise + Compliance Management |
| United States, Germany, Japan or Australia | Enterprise + Compliance Management + data residency, priced against Enterprise+. Take the lower. |
| United Kingdom only | No listed region meets it. Raise with Asana before quoting. |
List prices in US dollars, billed annually. Add Timesheets and Budgets only if Q3 confirms several approvers per gate.1
06Integrations
| Tool | What the connection does | Plan note | Source |
|---|---|---|---|
| Slack | Tasks from messages; project, portfolio and goal updates in channels | @Asana on all plans | 11, 17 |
| Microsoft Teams | Tasks from chats and meetings; link previews; project updates in channels | Needs a paid Teams plan | 12 |
| HubSpot | Deal and campaign widgets on tasks; rules act on deal changes | Plan not stated | 13 |
| Salesforce | Salesforce events create or update tasks; opportunity changes trigger rules | Advanced and above | 14 |
| ADvendio | No Asana app listed. Orders and line items sync through a build | Records to confirm, Q5 | 15, 16 |
| Mediaocean | No Asana app listed. Plans, buy milestones and billing status sync through a build, giving finance its close view | Access to confirm, Q4 | 15, 16 |
Asana API limit: 1,500 requests a minute on paid domains; 50 concurrent reads and 15 concurrent writes.16
07Open questions
Is video creative reviewed in Asana or in a separate proofing tool?Asana proofing covers PDF, PNG, JPG, GIF and BMP files; video is not listed.4
No plan change. A separate tool may be needed for video.Does group policy require client data to be stored in the UK?Asana's listed residency regions are the United States, Germany, Japan and Australia.10
Picks the route in section 05.Does any approval gate need more than one approver on the same item?Several approvers on one item sit under the Timesheets and Budgets add-on.17
A yes adds Timesheets and Budgets.Does the client hold Mediaocean API access, and which records should sync?Candidate records: media plans, buy milestones and billing status for the finance close.
Sizes the Mediaocean build.Which ADvendio orders or line items should create Asana work?If they already sit in Salesforce, test the Salesforce + Asana app before commissioning a build.
May replace a build with the Salesforce app.Close the open questions
Five client answers complete the specification.
Request the Asana quote
Send the route chosen in section 05 with the quote inputs.
Size the two builds
Mediaocean and ADvendio, against the API limit, before a go-live date is set.
08Sources
- Pricing and plan comparisonasana.com
- How to use forms branchinghelp.asana.com
- Workflow builderhelp.asana.com
- Giving feedback and approvalshelp.asana.com
- Portfolio dashboardshelp.asana.com
- Capacity planninghelp.asana.com
- Authentication and access managementhelp.asana.com
- Provisioning users with SCIMhelp.asana.com
- Audit Suite API and integrationshelp.asana.com
- Data residency for Asanahelp.asana.com
- Slack + Asanaasana.com/apps
- Microsoft Teams and Asanahelp.asana.com
- HubSpot + Asanaasana.com/apps
- Salesforce + Asanaasana.com/apps
- Asana app directoryasana.com/apps
- API rate limitsdevelopers.asana.com
- Release notes, September 2026forum.asana.com
- Fall 2026 releaseasana.com
- Spring 2026 releaseasana.com
Asana sources only, all read on 17 October 2026. Example output; client details anonymised.
Produced by the Accelyte scoping agent from one guided interview. On paid plans it carries your brand. Run your own on Asana, free: accelyte.ai/asana-scoping-agent-form
AI-assisted solution design adds the process model, architecture and build plan.
