-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't Connect Google Data Studio to Facebook account #25
Comments
Hello @KristyAllenl Could you please remove "Native Facebook Data Connector" from your approved applications here: https://myaccount.google.com/permissions |
Thank you. I tried that and initially it still didn't work (came up with the same error message). However I was in an incognito window at the time. As soon as I instead switched to a normal window and went through the same process it then worked. The only issue I'm having it that it won't let me now connect to all of my Facebook accounts. What could the reason be for this? I'm only seeing some of them. Thanks so much, |
Hello @KristyAllen, maybe #20 is a solution for your problem of missing ad accounts? |
Hi @djozsef , Unfortunately it looks like those instructions might be out of date. When I go to the Business Manager/ Business Settings/ Ad Account, there is no field named 'Business Name' and no section that looks similar to the screenshot in the #20 thread. I googled where this might be now with no luck. If you know where this 'Business Manager' field is located within Facebook Business Manager now please let me know. Otherwise I'll still with doing my Facebook reporting separate to Data Studio for the clients I'm unable to link to within Data Studio. Many thanks, |
Hi there,
Whenever I try and connect Google Data Studio to Native Facebook Connector, once I press Authorise I see the attached.
This has been happening for a week or so, every time.
Any suggestions as to how this can be resolved?
I cleared the Cookies.
Many thanks,
Kristy
The text was updated successfully, but these errors were encountered: