Get access to a client's Google Ads account

Confirm the individual Google Ads customer account, identified by its customer ID. Ask the client to identify the account they actually use for the work in scope, rather than choosing from a familiar-looking name. Also agree whether the immediate objective is assessment, configuration or ongoing delivery. These details determine which permission is reasonable and what your team will check afterward. If the client is unsure which asset belongs to the project, resolve that ownership or account-selection question before they approve access to an unrelated account.

The request needs a client administrator who can see the intended Google Ads customer account. Send the instructions to that person or ask the client to involve them. A staff member who can read a dashboard may still lack permission to invite an agency. Repeating the same request with the same insufficient role will not fix that distinction. The authorized person should review the requested asset, recipient and permission before proceeding, and retain their own independent access after the agency is added.

Read only fits a review of campaign performance; Standard allows campaign work; Admin should be reserved for work that requires managing users or account links. Start by naming the actions the agency must carry out, then match the role to those actions. If the team only needs to inspect Google Ads, explain why a viewing role may be sufficient. If a later task requires more authority, make that a deliberate scope decision with the client. Avoid requesting the broadest available role simply to prevent a possible future question; the current engagement should explain the permission being requested.

Agency Pilot sends a user invitation automatically after the client selects the account. The agency still accepts that invitation in Google Ads. Linking an MCC is a separate arrangement. Read the status in the context of that workflow. An invitation, a client confirmation and usable Google Ads access are related milestones, but they do not always happen at the same moment. Assign responsibility for the next step before marking delivery as ready. This prevents an agency teammate from arriving at a scheduled task and discovering that a required acceptance or platform action is still outstanding.

Use the Google login of each agency team member who needs direct account access. Verify it before creating or sending the onboarding request, especially when the agency works through more than one account. Ask the actual recipient to confirm the identity they will sign in with. A forwarded email or a similar display name is not reliable proof that the correct account has been added. For a staffing change, arrange the replacement person’s appropriate access and remove obsolete assignments through the relevant platform process.

After the platform action, sign in with the invited agency login, select the expected customer ID and confirm the campaign list belongs to the client before making any edits. Record who performed that check and whether any required work remains blocked. Prefer a harmless viewing check over an unnecessary live edit. If a teammate cannot reach the asset, compare the actual recipient and role with the original request before asking the client to start again. Completion should mean the right person can reach the intended asset with the agreed capability, rather than only that a message or notification was received.

Google Ads spend, clicks, impressions and conversions feed the client dashboard and Mission Control. A campaign reporting connection does not prove that every team member accepted their user invitation. Keep the client’s reporting expectation explicit in the service brief. If a metric is needed for a report, identify its source, date range and definition before promising that it will appear. A successful access step establishes only the capabilities described for this particular integration. It should not be used as evidence that another platform, a separate dataset or an unrelated source of business results has also been connected.

If the account is missing, check the client login and its account access first. If an invitation is missing, check the recipient address and pending invitations before resending. Start with account identity and authority because those determine what the client can share. Write down the exact stage where the flow stopped rather than repeatedly recreating the same request. If Google Ads shows an account-specific restriction, the appropriate platform administrator may need to resolve it first. Avoid broadening permissions or switching to another asset just to make a completion indicator appear; verify the intended account instead.

No. This flow invites the agency Google login as a direct user. An MCC relationship is a separate link request and approval in Google Ads. If the agency operates through an MCC, document both arrangements and verify the manager relationship separately. At offboarding, review both direct user access and manager access so that removing one does not leave the other overlooked.

The reporting authorization and the agency user invitation serve different purposes. Agency Pilot may receive campaign data while the individual invitation is still awaiting acceptance. Check the recipient and invitation state for the teammate who cannot enter Google Ads. Reconnecting reporting is unlikely to solve an unaccepted user invitation and could create extra work for the client.

The role supports campaign and budget work, but the client’s spending approval remains a separate business decision. Before taking over campaigns, record the agreed budget, approval contact and conditions for changing it. This is especially useful when the client has several accounts or agencies. A permission grant establishes what the platform allows, not the amount the client has authorized the agency to spend.

Treat them as an attribution setup decision after account identity and reporting are verified. A recorded sale and an advertising-platform conversion need a defined relationship; they are not interchangeable just because both appear in reporting. The product supports sending sold jobs through its attribution settings. Agree which sales will be recorded and check the setup before expecting those events to inform advertising decisions.

Confirm the customer ID, active campaign names, current budgets and the meaning of the conversions the client uses to judge success. Note which campaigns are intentionally paused and any launch commitments already made. Preserve enough context to explain subsequent changes. This gives the agency a defensible starting point without interpreting a newly accepted invitation as a request to immediately rebuild the account.

Remove direct users in Google Ads Access and security, address any separate manager-account link, and end the Agency Pilot reporting connection as separate handover actions. Agree a handover point before removing access that is still needed to finish approved work. Confirm the business retains the people and permissions it needs after the agency leaves. Keep permission removal separate from decisions about delivered work or historical reporting data; those are different questions. Record which Google Ads assignments were removed and which, if any, remain for an explicitly agreed support period, with a clear owner for the final review.

Open the agreed campaign set and document the existing budgets, conversion actions and search-term context before proposing changes. If measurement work is required, coordinate GA4 or Tag Manager access with the person responsible for that implementation. Confirm separately whether sold-job uploads are part of the engagement. The first useful outcome is a review tied to the correct customer account, with a clear explanation of which configuration or campaign decision needs client approval next.