Migration of authorized Google Ads user from one Google Worspace to another

[José A. Torres]

Hi team

We have migrated from a Google Workspace (GW0 from now on)  to the Google Workspace of our parent company (GW1 from now on). Currently the domain of GW0 is already configured in the GW1 console.

We had an account on GW0 authorized by one client in their Google Ads panel to upload conversions from our application (through its client id, client secret and refresh token).

Currently, conversions continue to be uploaded normally, we understand that because the GW0 is still active (although it no longer has the domain).

A new user with same name and under GW0 old domain has been created in the GW1.

In order not to lose conversion uploads from our application to the client's Google Ads platform, we would appreciate help on how to proceed with deleting the old account and activating the new one for uploads.

If we delete the old one:
* Is the uploading of conversions lost when deleting the old account?
* Has this new account losed SSO access to the customer's Google Ads console?
* Is it necessary to ask the client to delete the old account from their Google Ads console and register the new one again with the same email address?
* Do I need to reconfigure all permissions in the client console?

Best regards and thanks in advance

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to the Google Ads API support team.

After reviewing your query, I understand that you would like to know how to proceed with deleting the old account and activating the new one for uploads. Could you please confirm if you are using the Google Ads API or UI? If you are using the Google Ads API, kindly provide us with the uncropped UI screenshot, including the customer ID, to assist you better.

You can send the details via Reply privately to the author option, or direct private reply to this email.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02rXWWs:ref"

Thanks,
 

Google Ads API Team

 

[Jose A.Torres]

Hi team 

I have sent a private message without feedback. 

Is there any problem?

Regards

José A.

The information contained in this e-mail may be confidential. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution or copying of this communication, or any of its contents, is strictly prohibited. If you have received it by mistake please let us know by e-mail immediately and delete it from your system. Many thanks.

 

La información contenida en este mensaje puede ser confidencial. Ha sido enviada para el uso exclusivo del destinatario(s) previsto. Si el lector de este mensaje no fuera el destinatario previsto, por el presente queda Ud. notificado que cualquier lectura, uso, publicación, diseminación, distribución o copiado de esta comunicación o su contenido está estrictamente prohibido. En caso de que Ud. hubiera recibido este mensaje por error le agradeceremos notificarnos por e-mail inmediatamente y eliminarlo de su sistema. Muchas gracias.

[Google Ads API Forum Advisor]

Hi José,

Thank you for reaching out to the Google Ads API support team.

With regard to your concerns, I am checking with the rest of our team and one of our colleagues will reach out to you once we have an update. Meanwhile, your patience is highly appreciated.

[Google Ads API Forum Advisor]

Hi,

Thank you for getting back to us.
 
I would like to inform you that even if GW0 is deleted entirely, the Google Ads account will remain safe and all its data will be retained. However, if GW0 is removed before GW1 is ready to take over its responsibilities.
 
Therefore, a suggested order of operations is:

1. Keep GW0 in place during the whole process.
2. Set up GW1 completely, including generating a new refresh token for GW1 (or service account credentials for GW1 if that's how you are authorizing).
3. Make a test request with GW1, using the validate_only header to ensure things are working.
4. Swap from using GW0 to GW1 for the ongoing integration process.
5. Only once step 4 is successful, take whatever steps may or may not remove GW0's access to the Google Ads account. At this point, the status of GW0 is irrelevant because GW1 is running the process.