X

X (Twitter) ads through chat: campaign management reference

Everything AdWhispr can do in your X Ads account from a chat: connect the account, create a paused campaign with its ad group, promoted post, targeting and conversion optimization, pause and resume, change budgets, rename, read performance, and what X requires before an ad can run.

Updated September 11, 2026 · 6 min read

This page covers your own X Ads account (X Ads Manager at ads.x.com). AdWhispr does not research competitors' X ads yet: X publishes no ad library outside the EU, so there is nothing to read.

Everything is created paused. A launch builds the campaign and its ad group in your X account with delivery off. It starts spending only when you resume it, and X then runs its own review before anything shows.

Before you start

X has three requirements that no launch can skip:

  1. A connected X Ads account. Say Connect my X Ads account in the chat, or open Settings, then Connected accounts, in the dashboard. You grant access on X's own screen. X asks for permission every time you connect, even if you connected before; that is how X works.
  2. A payment method on the ads account, under Payment methods at ads.x.com. X does not let AdWhispr add one. Without it, every campaign is refused, and the chat says so.
  3. X Premium or a Verified Organization. X only serves ads from a verified account: X Premium for individuals, Verified Organizations for businesses. An unverified account can connect and build campaigns, but X holds the ads until the verification is done.

If you connected X before AdWhispr's X app was approved by X (10 September 2026), reconnect it once under Settings, Connected accounts.

Connect the account

You

Connect my X Ads account.

AdWhispr

Open this link and sign in with the X account that has access to your X Ads account: adwhispr.com/api/execution/x/start. You approve on X's own screen; AdWhispr never sees your password.

After you approve, every X Ads account that login can manage appears under Connected accounts, and in the chat when you ask what is connected. X ads accounts have short letter-and-number ids (like 18ce54d4x5t), not the long numbers Meta uses.

Create a campaign

One request builds the whole thing, all paused: the campaign, its ad group (X calls it a line item), the promoted post that runs as the ad, the targeting, and, on a sales or leads goal, conversion optimization. X requires a daily budget on every campaign, so the chat asks for one if you leave it out.

You

Launch an X campaign called "Spring launch" for traffic at 30 a day. Post: "Ship ads from a chat. Try AdWhispr." link adwhispr.com, target the US, men 25 and up, keyword "marketing automation".

AdWhispr

Preview: campaign "Spring launch" on X account 18ce54d4x5t, traffic objective, daily budget 30.00, one promoted post, targeting US, male, 25+, keyword "marketing automation", created paused. Create it?

You

Yes.

AdWhispr

Created campaign "Spring launch" (PAUSED) on X with 1 promoted post in its ad group at 30.00 a day. Targeting applied: US, male, 25+, keyword. It will not spend until you resume it.

What you can set today:

  • Objective: traffic (default), sales, leads, awareness, engagement, video views, app installs or followers.
  • The promoted post, written from the chat: the text, your own image, and the landing link. Give two or more posts and they run as a creative test in one ad group, where X shifts budget to the winner. A traffic post needs a link, so the chat uses your saved website if you do not give one.
  • Targeting on the ad group, in the same request: country (for example "US"), gender, an age floor (X uses a single "over" bracket, so "25 and up"), keywords (X's signature lever), and interests or existing audiences. Look up interest and audience ids first by asking, for example, find X interests for software (see below).
  • Conversion optimization. A sales or leads goal optimizes for a conversion on your X web event tag (X's pixel) instead of just clicks. The chat picks the right tag automatically (a purchase tag for sales, a sign up tag for leads). If the account has no tag it runs optimized for website clicks and tells you.
  • Daily budget, in the account's currency (the currency of your payment method).

Find targeting and your pixel

Ask the chat to look things up before launching, so real ids go into the campaign:

You

Find X interests for software, and show me my X conversion tags.

AdWhispr

X interests matching "software": Technology / Software Development ... Web event tags on this account: Purchase (tracking), Site visits (tracking), Lead (tracking) ...

This covers locations, interests, existing audiences (for retargeting), and web event tags. Keywords need no lookup; just name them.

Pause, resume, budgets and renaming

  • Pause stops spend immediately, no confirmation. Pausing the campaign stops every ad group under it.
  • Resume goes live and starts spending; the chat warns you and waits for your confirmation. Resuming also wakes the campaign's ad groups, which X leaves paused otherwise.
  • Budget changes are previewed, then applied to the campaign. X refuses a daily budget below what the campaign has already spent today, and the chat says so.
  • Rename a campaign or ad group, on its own or together with a budget change, previewed then applied.
You

Change the Spring launch budget to 45 a day and rename it to "Spring launch v2".

AdWhispr

Preview: budget 30.00 to 45.00, name to "Spring launch v2" on this campaign. Apply it?

Performance reads

Ask how your X ads are doing and the chat reads spend, impressions, clicks, engagements, likes, replies and reposts for the last 30 days, or a date range you give. X only reports seven days at a time, so a longer range is read in seven-day pieces and added up. The same numbers live on the Ad Campaigns page in the dashboard. See reading performance and cutting wasted spend.

One honest limit: X's reporting service has been unreliable since April 2026. When it fails, the chat says so rather than showing zeros, and the campaign controls (pause, resume, budget) keep working. The numbers are always in X Ads Manager.

When X refuses

The chat shows X's own message plus one sentence on what to do. The common ones:

  • No payment method (or X rejects the card on file): add or fix it under Payment methods at ads.x.com, then run the launch again.
  • Access revoked or expired: reconnect X under Settings, Connected accounts.
  • Too many campaigns: X caps active campaigns per account, and a paused campaign still counts. Delete old ones in X Ads Manager.
  • Rate limited: wait about a minute without retrying.
  • Server error on X's side: try again in a few minutes; nothing to fix on yours.

Frequently asked questions

Do I need X Premium to run ads?

Yes, or a Verified Organization for a business. It is X's rule for every advertiser, not AdWhispr's. Campaigns can be built before you verify, but X will not serve them until you do.

Where do I add the payment method?

At ads.x.com under Payment methods. X does not allow it through the API, so AdWhispr cannot do it for you.

Why does X ask for permission again every time I connect?

X always shows its permission screen when an app asks for access, even if you approved it before. Approve it and the connection updates in place.

Can AdWhispr write the post for me?

Yes. Give the post text (and your own image and a link) in the launch request and the chat creates the campaign, the ad group and the promoted post together, all paused. Give two or more posts and they run as a creative test in one ad group. Use only images you own, never a competitor's.

What is the smallest budget I can set?

X sets no published floor for a daily budget, but the campaign cannot spend more than the card on file allows. Start with what you would spend in X Ads Manager.

Related pages