facebook marketing access token doesn’t generate

To generate a Marketing API access token for Facebook Marketing, you need to follow these steps: 1. Navigate to [Meta for Developers](https://developers.facebook.com/apps/) and follow the steps provided in the [Facebook documentation](https://developers.facebook.com/docs/development/create-an-app/) to create a Facebook app. 2. While creating the app, when you are prompted for "What do you want your app to do?", select Other. You will also need to set the app type to Business when prompted. 3. From your App’s dashboard, [set up the Marketing API](https://developers.facebook.com/docs/marketing-apis/get-started). 4. Generate a Marketing API access token: From your App’s Dashboard, click Marketing API --> Tools. Select all the available token permissions (

ads_management

,

ads_read

,

read_insights

,

business_management

) and click Get token. Copy the generated token for later use. 5. Request a rate limit increase: Facebook [heavily throttles](https://developers.facebook.com/docs/marketing-api/overview/authorization#limits) API tokens generated from Facebook apps with the default Standard Access tier, making it infeasible to use the token for syncs with Airbyte. You'll need to request an upgrade to Advanced Access for your app on the following permissions: - Ads Management Standard Access - ads_read - Ads_management See the Facebook [documentation on Authorization](https://developers.facebook.com/docs/marketing-api/overview/authorization/#access-levels) to request Advanced Access to the relevant permissions. You can use the [Access Token Tool](https://developers.facebook.com/tools/accesstoken) at any time to view your existing access tokens, including their assigned permissions and lifecycles. If you're still having issues, it might be due to the length of the access token. In one [Github issue](https://github.com/airbytehq/airbyte/issues/40609), a user reported that their access token was shorter than expected, which caused problems. The access token they obtained consisted of 20 symbols versus the one that should emit 200 symbols. If you're using Airbyte Cloud, you might need to pass an additional parameter

auth_type

alongside the

secretId

parameter when creating a new source via the Cloud API. This isn't documented, but was mentioned in the same [Github issue](https://github.com/airbytehq/airbyte/issues/40609). If none of these solutions work, you might need to contact Facebook Support, as the issue could be on their side. Sources: - [Airbyte Documentation](https://docs.airbyte.com/integrations/sources/facebook-marketing#for-airbyte-open-source-generate-an-access-token-and-request-a-rate-limit-increase) - [Github Issue](https://github.com/airbytehq/airbyte/issues/40609)