Question for Facebook Marketing users I have seve...
# help-connector-development
e
Question for Facebook Marketing users I have several connections set up used to report on clients post performance. Today I attempted to set up a new one, however I cannot get the oauth to succeed. I tried using existing apps ids and secrets and am getting the same error. However all my pre-existing connections work. Can anyone shed any light on this? https://docs.airbyte.com/integrations/sources/facebook-marketing
m
Hi Erik, What are you seeing when going through the oauth flow? When was the last time you created a connection with Facebook Marketing?
e
Hi Mark, My latest connection was built, or at least modified a few weeks ago. I am seeing the ability to validate authentication through OAuth 2.0 in both airbyte cloud and in a locally hosted instance as well as on our server hosted instance. All operate as expected until I finalize creation of the connection, in which case it throws a 200 error. I'm getting this for existing and new Facebook developer apps. I've tested the token created through multiple means and the only one it appears to fail on is through creation of the airbyte connector. The specific error returned is "Configuration check failed "Credentials don't have enough permissions. Re-authenticate if FB oauth is used or refresh access token with all required permissions.. Full error: (#200) Ad account owner has NOT grant ads_management or ads_read permission, refer to https://developers.facebook.com/docs/marketing-api/get-started/authorization/#permissions-and-features for details." I have confirmed that I have both ads_management and ads_read permissions assigned to that token through the facebook token debugger.
So to clarify the specific point of error, the "authenticate" button under authentication succeeds, but the "set up source" button at the bottom returns a failure when testing the source.
m
Hey Erik, thanks for the detail. A couple of sanity checks: Check if
ads_read
and
ads_management
have "Advanced Access" status, not just "Standard Access". Ensure your app is still associated with a verified Business Manager account. Are your connections unique per client, or are you using one connector with multiple streams? And are you on connector version 4.1.3 or later?
e
Mark, Locally hosted Airbyte instances The "Advanced Access" is potentially the issue. I my connections are unique per client, with a separate Facebook app for each of them. They are in various stages (published vs. in development) and to my understanding the ones still in development should allow me to connect as long as I am an admin and ad admin on that account. For my companies connector specifically, I have full facebook admin privileges including ad admin and the app is in development, which should allow me (at least last i've seen) to connect. Airbyte cloud When using the Airbyte cloud instance, I am able to authenticate but still get an error when clicking "set up source". This is using the in browser authentication and not the app id and key provided from the facebook developer platform. I used my businesses account (not a clients) which I have full ownership and access for.
Copy code
Failed to save ddm Facebook Marketing due to the following error: 'The access token for this connection is invalid or corrupted. Please re-authenticate your Facebook connection in Airbyte. If re-authentication does not resolve the issue, go to facebook.com > Settings > Business Integrations, remove the Airbyte app, and then re-authenticate again.. Full error: Invalid OAuth access token - Cannot parse access token'
I have updated and tested connector version 4.2.1 on my local instance and still have not had success. There advanced access may be the culprit, but has not stopped me in the past. I was assuming Airbyte Cloud would still allow me to complete source creation if that were the case, though it throws a different error.
@Mark Grivnin just as another point of data here, I've also attempted to connect via Airbyte cloud without entering an ad account id (which doesn't appear to be required) and get an entirely different error "Config validation error: [] should be non-empty".
m
Hmm, this is interesting. Could you please DM me your workspace ID so I can try troubleshooting your cloud account?