Campaign Management
Campaign managers are responsible for various ad operations, including managing ad accounts, campaigns, and users. In addition, it provides tools for monitoring ad performance, setting campaign parameters, and exporting performance reports.
Campaign Managers
Moloco Commerce Media provides three options for campaign management. We recommend customers pick one option that best suits their business needs. If you plan to use multiple campaign managers please review Multi-Campaign Manager usage (Dual Access) for limitations and best practices.
- Option A: Moloco’s Standalone Campaign Manager
- Option B: Moloco’s Widgetized Campaign Manager
- Option C: Build your own Campaign Manager with Moloco’s APIs
User Roles & Permissions
Please see the User Roles & Permissions page as well as API and SSO Credential Management for more information on how to manage user roles, permissions, and API keys within the campaign managers.
Campaign States
Each campaign created in the Campaign Manager has a state that indicates its current situation and helps identify unexpected problems. For the full list of campaign states please see the Campaign states page.
Multi-Campaign Manager usage (Dual Access)
Standalone and Widgetized Campaign Managers
If you choose to use both the standalone campaign manager and the widgetized campaign manager we recommend the following best practices.
Concurrent access limitations
The Platform owner and Ad account agency roles must use the Standalone campaign manager; the widgetized campaign manager does not support platform management.
The Ad account owner role may concurrently access and manage their campaigns with both the Standalone and Widgetized campaign manager.
The Ad account user roles may use both the Standalone and Widgetized campaign managers following the requirements listed below.
Standalone and Widgetized dual access requirements
- The external user ID should be unique and immutable
- The user should be mapped to one ad account ID
- Users must have only one role for each ad account ID
- The mapping of external user id to an email address should be immutable
- User email addresses should be unique and pre-existing before account creation
Password Reset
Users created in the Campaign Manager through SSO can use the 'Forgot password' function when accessing the Standalone type.
Build your own Campaign Manager and Standalone or Widgetized
Using the Build your own Campaign Manager method in combination with the Standalone or Widgetized campaign manager presents several challenges and limitations that require consideration.
Full Implementation of Build your own Campaign Manager
Attempting to incorporate the majority of MCM functions, such as but not limited to, user role management, spending controls, wallet functions, and reporting, presents significant simultaneous campaign manager usage limitations and is not recommended.
Migration
- Using the Build your own method requires customers to maintain data concerning access rights for specific features and audit user activity, including access and authorization. MCM does not support a migration path from Build-your-own to the standalone or widgetized campaign managers.
Partial Usage of Build your own Campaign Manager
Customers using a subset of Campaign Manager functions through the Management API, excluding features like user management, spending controls, wallet functions, and history may use the standalone or Widgetized along with the Build your own Campaign manager with the following limitations:
Dual Access
When a user who is only present in the Build your own campaign manager attempts to connect to the Standalone or Widgetized campaign manager, there are two potential outcomes:
- Standalone: The platform owner sends an invitation to the user for an existing Ad account. The user receives an invitation email from the MCM Campaign Manager, enabling them to set up a password.
- Widgetized (SSO): When a user attempts access, the platform sends the user's User role and ID information to MCM, where a corresponding user profile is created. This eliminates the need for users to sign in separately for the MCM Campaign Manager.
Questions?Please see our FAQ for answers to common campaign management questions.
Updated 19 days ago