Skip to main content

ACC create manual

What this task is​

The platform creates this task when automatic creation of an ads account (ACC) did not complete. An ACC is normally created via the Google Ads API, but when the root MCC hits its account limits — or the API or the account pool fails — the account has to be created manually. The operator's job is to manually ensure the ACC exists and is correctly linked so it appears in the right hierarchy.

When it appears: automatic creation of an ACC via API or the account pool failed — for example, because of account limits on the root MCC.

Creating an MCC or Sub-MCC is a separate task, see MCC create manual.

Step 1. Open the task​

  1. Go to the Operator tasks page.
  2. Find the task in the table and click Execute task at the end of its row.
  3. A modal opens with a configuration form, task details, and an inline instruction. Keep it open — you'll need these values, and you can cross-check the steps inside the modal at any time.

Review the data in the form and pick one of two scenarios.

Scenario A — Direct selection. If the form's dropdown contains available free accounts from the pool, pick the required root (parent) MCC and the account, then confirm the task.

Scenario B — Create from scratch. If the dropdown is empty and there are no available accounts, create the account on the Google Ads side: in the parent manager account, go to Accounts → Sub-account settings (or Performance) and click + → Create account.

After creating the account, return to the modal, open the Account ID tab, and fill in:

  • Root MCC — pick the root manager account from the list;
  • Google Customer ID (Account ID) — enter the 10-digit ID of the ads account you created in Google Ads.

📖 Google Ads Help: Create a Google Ads account from a manager account

Step 3. Verify sync and close​

Don't close the task too early. Close it only after the account appears in the correct hierarchy.

  1. After the setup is done, a background tree-sync operation runs automatically for the account tree and all its elements.
  2. You can track the operation status on the Operations page.
  3. After a successful sync, the structure appears on the Actual tree page: the added account shows up with all child elements and becomes available for selection in operator tasks.
  4. Make sure the account shows under the expected parent, return to the task modal, and complete it with a success result.
  5. If the account can't be created or linked, complete the task with a failure result and a short reason.

Tasks that may appear additionally​

This applies only to a task closed with a success result. If the task is closed as failure or cancelled, no further checks are triggered.

New operator tasks appear only if one of the automatic checks couldn't complete on its own. These are fallback tasks, not a mandatory step:

  • Ads node rename manual — if the system couldn't rename the ad node in Google Ads automatically. Rename it manually and close the task after verifying the name.
  • Ads access grants sync manual — if the system couldn't verify or apply access grants. Open access in Google Ads, check users and invitations, then close the task.
  • Transfer step manual — only for the pool-transfer creation scenario, if one of the transfer steps is blocked. Manually assist the specific transfer step.