LinkedIn Ads
Org-level connection
LinkedIn Ads is connected once at the org level by an admin. The credential is shared across all groups that have been granted access — individual team members don't need to connect their own accounts.
How to connect
Click "Connect with OAuth" below to authorize On Belay to access your LinkedIn Ads account. You'll be redirected to LinkedIn to approve the connection — no credentials to copy or paste.
Note: LinkedIn requires Standard Tier access for multi-account production use. Apply via the LinkedIn Developer Portal if you encounter ad account limits.
Ready to connect?
Go directly to the integrations page in your dashboard.
Permissions (scopes)
These are the data scopes On Belay can be granted for LinkedIn Ads. Your org admin controls which scopes are enabled per group.
| Scope | Description | Access |
|---|---|---|
r_ads | Read ads | Read only |
r_ads_reporting | Read ad reports | Read only |
rw_ads | Read/write ads | Read / Write |
r_organization_social | Read org social data | Read only |
Troubleshooting
"redirect_uri_mismatch" error during OAuth
Your OAuth app's authorized redirect URIs don't include the On Belay callback URL. Add https://app.onbelay.ai/api/oauth-callback/linkedin_ads to the allowed redirect URIs in your OAuth app settings.
"invalid_scope" error
The API or scope isn't enabled in your cloud project. For Google integrations, make sure the relevant API (e.g., Google Ads API, Search Console API) is enabled in Google Cloud Console for your project.
Connected but Claude can't access data
Check that your group has been granted access to this integration in On Belay → Groups → [your group] → Integrations. Also verify the specific scopes your group is permitted to use match what your query requires.
Still stuck? We're happy to help.
Contact support →