New and Improved MCC Services

Google Confidential and Proprietary

New & Improved MCC ServicesManaging thousands of accounts the automated way!


Agenda

1. Motivation○ The need for a new service

2. Introducing new API service methods○ What do they do?

3. The lifecycle of a managed account○ Using the new functionality○ Common use-case code samples

4. Mind your budgets○ Possible account level budget implications

5. Q & A


Motivation


● Until now, developers have not been able to manipulate account structures programmatically.

● The manual intervention required to link, unlink or reorganize accounts within an MCC can prevent the full automation of some business processes.

○ For example, onboarding a customer account.

Motivation


Common use-cases

● Reorganising accounts according to business needs

● API / platform efficiency improvements: Maintaining an "inactive accounts" MCC

● Taking control of (onboarding) an existing client account

● Day-to-day management of complex MCC structures

● Relinquishing control of an account no longer managed by a platform


Introducing new API service methods


MutateLink actions: MCC

Account 1

Account 0

Account 2

Account 3

ManagedCustomerService: Three new methods

ManagedCustomerService.mutateLink:

Performs various actions required to add or remove accounts to / from an MCC


MutateLink actions:

Account 1

Account 0

Account 2

● Extend an invitation

Invite extended to Account 1


Account 3


MCC





MutateLink actions:

Account 1

Account 0

Account 2


Account 3

● Rescind an invitation

Rescind invitation to Account 3

MCC





MutateLink actions:

Account 1

Account 0

Account 2


Account 3

● Rescind an invitation● Accept an invitation (client account

only action)

Account 1 accepts invite

MCC





MutateLink actions:

Account 1

Account 0

Account 2


Account 3


only action)Account 2

rejects invite

MCC

● Reject an invitation (client account only action)





MutateLink actions:

Account 1

Account 0

Account 2


Account 3


only action)MCC terminates Account 1 link

MCC


● Terminate the link between an MCC and client account





MutateLink actions:

Account 1

Account 0

Account 2


Account 3


only action)

Account 0 terminates link

MCC


● Terminate the link between an MCC and client account





ManagedCustomerService.getPendingInvitations:

Retrieves pending invitations.

● Can be invoked by either the manager (MCC) or the client.

● Once an invitation has been accepted, declined or rescinded, it will no longer be in a pending state.

● Pending invitations are available via the ManagedCustomerService.getPendingInvitations method.

● Accepted links will be available via the ManagedCustomerService.get method.

● Declined, Rescinded and Terminated links will not be available through the ManagedCustomerService at all.



ManagedCustomerService.mutateManager:

Enables you to move accounts between MCCs within your account structure

● Move a client account to or from any MCC within your structure

● Both MCCs (to and from) must be managed by the effective user

● MCCs cannot currently be moved using this method

● To move an MCC: Terminate its link to the parent MCC and establish a new link using the mutateLink method.



MCC 0

Account 2

MCC 1 MCC 2

Account 0



Account 1

● Account 1 is moved from 'MCC 1' to 'MCC 2'● This action can only be completed by 'MCC 0'


MCC 0

Account 2

MCC 1 MCC 2

Account 0



Account 1

MCCs can be nested upto 5 levels deep


The lifecycle of a managed account


Java code sample

1. MCC extends a link invitation to a client account.

2. [Optional] Retrieve the invitation.

3. The client account accepts the invitation.

4. [Optional] The client is moved to another MCC within the structure.

5. The MCC terminates its link to the client account.


Java code sample

MCC extends a link invitation to a client account

// Get the ManagedCustomerService (for top level MCC).ManagedCustomerServiceInterface managedCustomerService =

adWordsServices.get(mccSession,ManagedCustomerServiceInterface.class);

// Create a 'pending' link between sub MCC 0 and client account.ManagedCustomerLink inviteLink = new ManagedCustomerLink();inviteLink.setClientCustomerId(CLIENT_ACCOUNT_CID);inviteLink.setLinkStatus(LinkStatus.PENDING);inviteLink.setManagerCustomerId(SUB_MCC0_CID);

sub MCC 0 sub MCC 1

Client Account

Top MCC


Java code sample

MCC extends a link invitation to a client account(continued)

// Send invitation to client account.LinkOperation inviteLinkOp = new LinkOperation();inviteLinkOp.setOperand(inviteLink);inviteLinkOp.setOperator(Operator.ADD);managedCustomerService.mutateLink(

new LinkOperation[]{inviteLinkOp});

sub MCC 0 sub MCC 1

Client Account

Top MCC


Java code sample

MCC extends a link invitation to a client account:MutateLinkResponse

<ns2:mutateLinkResponsexmlns="https://adwords.google.com/api/adwords/cm/v201302" xmlns:ns2="https://adwords.google.com/api/adwords/mcm/v201302"> <ns2:rval> <ns2:links> <ns2:managerCustomerId>SUB_MCC0_CID</ns2:managerCustomerId> <ns2:clientCustomerId>CLIENT_ACCOUNT_CID</ns2:clientCustomerId> <ns2:linkStatus>PENDING</ns2:linkStatus> </ns2:links> </ns2:rval></ns2:mutateLinkResponse>

sub MCC 0 sub MCC 1

Client Account

Top MCC


Java code sample

Retrieve the invitation

// Set session customer ID to sub MCC 0. mccSession.setClientCustomerId("SUB_MCC0_CID");

// Retrieve all pending invites.// This can also be performed by the client account.PendingInvitationSelector selector =

new PendingInvitationSelector();

PendingInvitation[] invitations =managedCustomerService.getPendingInvitations(selector);


Java code sample

Retrieve the invitation:getPendingInvitationsResponse

<ns2:getPendingInvitationsResponse xmlns="https://adwords.google.com/api/adwords/cm/v201302" xmlns:ns2="https://adwords.google.com/api/adwords/mcm/v201302"> <ns2:rval> <ns2:manager> <ns2:name>SUB MCC 0</ns2:name> <ns2:login>[email protected]</ns2:login> <ns2:companyName>Google Inc</ns2:companyName> <ns2:customerId>SUB_MCC_0_CID</ns2:customerId> <ns2:canManageClients>true</ns2:canManageClients> <ns2:testAccount>false</ns2:testAccount> </ns2:manager> ....

Java code sample

Retrieve the invitation:getPendingInvitationsResponse


Java code sample

Retrieve the invitation:getPendingInvitationsResponse (continued)

....

<ns2:client> <ns2:name>Client Account</ns2:name> <ns2:login>[email protected]</ns2:login> <ns2:companyName>Google Inc</ns2:companyName> <ns2:customerId>CLIENT_ACCOUNT_CID</ns2:customerId> <ns2:canManageClients>false</ns2:canManageClients> <ns2:testAccount>false</ns2:testAccount> </ns2:client> <ns2:creationDate>20130313 113459 Europe/London</ns2:creationDate> <ns2:expirationDate>20130412 123459 Europe/London</ns2:expirationDate> </ns2:rval></ns2:getPendingInvitationsResponse>


// Get the ManagedCustomerService (for client account).managedCustomerService =

adWordsServices.get(clientAccountSession,ManagedCustomerServiceInterface.class);

// Create an 'active' link between sub MCC 0 and client account.ManagedCustomerLink activeLink = new ManagedCustomerLink();activeLink.setClientCustomerId(CLIENT_ACCOUNT_CID);

// Set LinkStatus.REFUSED to decline the invite.activeLink.setLinkStatus(LinkStatus.ACTIVE);activeLink.setManagerCustomerId(SUB_MCC0_CID);

Java code sample

The client account accepts the invitation

sub MCC 0 sub MCC 1

Client Account

Top MCC


Java code sample

The client account accepts the invitation(continued)

// Accept the invitation.LinkOperation acceptInviteLinkOp = new LinkOperation();acceptInviteLinkOp.setOperand(activeLink);acceptInviteLinkOp.setOperator(Operator.SET);managedCustomerService.mutateLink(

new LinkOperation[]{acceptInviteLinkOp});

sub MCC 0 sub MCC 1

Client Account

Top MCC


// The top MCC is the only MCC in this structure that manages// both sub MCCs.mccSession.setClientCustomerId("TOP_MCC_CID");

managedCustomerService = adWordsServices.get(mccSession,ManagedCustomerServiceInterface.class);

// The MoveAccountLink.ManagedCustomerLink moveAccountLink = new ManagedCustomerLink();moveAccountLink.setClientCustomerId(CLIENT_ACCOUNT_CID);moveAccountLink.setLinkStatus(LinkStatus.ACTIVE);moveAccountLink.setManagerCustomerId(SUB_MCC1_CID);

Java code sample

The client is moved to sub MCC 1

sub MCC 0 sub MCC 1

Client Account

Top MCC


Java code sample

The client is moved to sub MCC 1 (continued)

MoveOperation moveAccountOp = new MoveOperation();moveAccountOp.setOldManagerCustomerId(SUB_MCC0_CID);moveAccountOp.setOperator(Operator.SET);moveAccountOp.setOperand(moveAccountLink);managedCustomerService.mutateManager(

new MoveOperation[]{moveAccountOp});

sub MCC 0 sub MCC 1

Client Account

Top MCC


Java code sample

The client is moved to sub MCC 1:mutateManagerResponse

<ns2:mutateManagerResponse xmlns="https://adwords.google.com/api/adwords/cm/v201302" xmlns:ns2="https://adwords.google.com/api/adwords/mcm/v201302"> <ns2:rval> <ns2:links> <ns2:managerCustomerId>SUB_MCC1_CID</ns2:managerCustomerId> <ns2:clientCustomerId>CLIENT_ACCOUNT_CID</ns2:clientCustomerId>

<ns2:linkStatus>ACTIVE</ns2:linkStatus></ns2:links>

</ns2:rval></ns2:mutateManagerResponse>

sub MCC 0 sub MCC 1

Client Account

Top MCC


// Link can be terminated by either the client or the manager.

ManagedCustomerLink linkToTerminate = new ManagedCustomerLink();linkToTerminate.setClientCustomerId(CLIENT_ACCOUNT_CID);linkToTerminate.setLinkStatus(LinkStatus.INACTIVE);linkToTerminate.setManagerCustomerId(SUB_MCC1_CID);

Java code sample

The MCC terminates its link to the client account

sub MCC 0 sub MCC 1

Client Account

Top MCC


Mind your budgets


MCC 0

MCC 1 MCC 2

Account Level Budgets

'Managed Defined Order' (MDO) users beware: Breaking the link between an account and the MDO on which its account budget relies, will end the budget

Account 1

MDO

Budget

Budget linked to MDO

MDO - Budget link broken

Active BudgetBudget Ended

New and Improved MCC Services

Documents

Transcript of New and Improved MCC Services