Setup guide · about 5 minutes

Connect X Ads

Connect an eligible X Ads account to import campaign performance and run audits.

Before you start

  • An X account with access to the X Ads advertiser account.
  • The Campaign Medic workspace must have X Ads enabled.
  • The developer app must have X Ads API access for the advertiser account.

Connect and run an audit

  1. 1

    Check account access

    Make sure the provider account you will authorize can see the X Ads advertiser account you want to connect.

  2. 2

    Connect X Ads

    Open Connect in Campaign Medic, find X Ads and choose Connect. Sign in to the provider and approve the requested access.

  3. 3

    Choose the ad account

    Return to Campaign Medic and select the account you want the workspace to use. Only accounts returned by the provider are shown.

  4. 4

    Run your first audit

    Open Audit, choose X Ads, select the connected account and run the audit. Campaign Medic will import the available campaign and performance data.

  5. 5

    Review before applying

    Read each recommendation and its expected effect. Any supported account change requires your approval, and the app records the operation.

Campaign Medic currently supports pausing and re-enabling X campaigns after you approve the action.

Troubleshooting

  • X developer app eligibility and Ads API access are separate from completing the OAuth authorization screen.
  • Campaign Medic currently supports pausing and re-enabling X campaigns after you approve the action.
  • If authorization succeeds but no advertiser is listed, confirm Ads API access and account assignment with the X Ads administrator.
  • If Campaign Medic reports that the connection attempt expired, return to Connect and start a new attempt in the same browser.
  • If the problem continues, contact support with the platform name and the approximate time of the attempt. Do not send passwords, access tokens or app secrets.
X Ads API access requirements

Disconnect

Open Connect and choose Disconnect for X Ads. This removes the stored connection and stops future requests to the provider. Existing audit history remains subject to the retention period in the Privacy Policy.