CM360 is not connecting to the locker

[Globant]

Hello, could you help me understand why the data from Campaign Manager 360 is not connecting to my locker? I have tried from several profiles, but it only says that there is a system error and does not allow me to see what the error is or connect the data source.

[Lobo-Google]

Hi @Globant, thanks for your post!

Have you been able to connect to the same CM360 profile successfully from Looker Studio before? Are you able to log in to CM360 and successfully access the account and profiles there? If so, you may be encountering a product bug. You can let our team know by filing a form using the instructions on this help center page: https://support.google.com/looker-studio/answer/13606940  

I've also found a CM360 Access issues troubleshooting guide, I hope that this might be helpful with some ideas to try: https://support.google.com/campaignmanager/answer/2828615 

Here are the CM360 connection instructions, as well (just in case!) https://support.google.com/looker-studio/answer/7245540?hl=en#how-to-connect&zippy=%2Cin-this-articl... 

[courtneypiel]

I am also encountering this issue. Confirming that I have successfully connected CM360 to Looker hundreds of times in the past and I have all the necessary access via CM360 that is needed to connect. Not only am I unable to connect to CM360 when building a new report, but it is causing errors in my existing reports and I am unable to reconnect the source given the error message. 

[Prakhar7296]

Yeah that's sure,CM360 is very important then to use yt analytics and thus it makes the ease use of API(Application programming interface).

[Keifay]

I am also experiencing this issue. I have successfully connect looker to cm360 many times before so i am confident there is an issue with looker.

[hollywy]

I'm having the same issue - which has been ongoing for over a week now. Is there a recommended fix???

[Frankidigi]

I am also experiencing this issue. I have successfully connected looker to cm360 many times before so I am confident there is an issue with Looker.

[Frankidigi]

@Lobo-Google  Can you help with this please ? thanks in advance

[Frankidigi]

This is still not fixed, I tried different accounts but I can't connect to Campaign manager

I reported it, see below and thanks for your help in fixing this issue promptly

[Lobo-Google]

It looks like this may be part of a larger connectivity issue, and is being looked into!

[teoz]

I have the exact same issue, it's been going on for at least a week. Do we know when this will be solved?

[garywong]

I am experiencing the same issue, would be great to have a solution. Thanks.

[guestuser10]

Is there any information, how long it will take to solve this issue? Or is there a possibility for a workaround to use CM?

[Lobo-Google]

Would anyone be able to provide the precise time of day and details of the failed interaction with CM? Our team is advising that they need this in order to look further into the issue.

[courtneypiel]

Failed interaction has been ongoing for weeks. Here is a screenshot of what I am seeing with one of my existing reports. All of the charts tied to CM (which used to work a few weeks ago) now display errors. When I try to reconnect the existing CM source, it gives me the attached error message. If there is a support email address, I would be happy to share the report with the google support team if they need it to investigate.

It is also happening when I try to build new reports from scratch. I get the same error message "looker studio has encountered a system error" when I try to connect CM as a source for any/all reports. 

[Lobo-Google]

Thank you SO much, @courtneypiel 

[Lobo-Google]

Everyone, thank you so very much for your patience! You can track resolution progress on this public issue: https://issuetracker.google.com/issues/365565139

[hollywy]

Is this an internal link?

[Lobo-Google]

No, it should be visible publicly! 

[hollywy]

It requires an SSO login. None of our credentials are working, so I assumed it's internal.

[Lobo-Google]

Apologies! I posted the incorrect link (it's my first time sharing a bug with users in the Community forum) - the correct link is https://issuetracker.google.com/issues/365565139 and I've updated my initial response. 

Thank you for bearing with me!

[JenS]

This issue is now resolved. Thank you for your patience!