X

Connect X to launch X ads and read their results, with the ad accounts of the X account that connects.

Connect X

Owners and admins connect X once per workspace. The connection acts as the X account that signs in: Pluto Ads sees the ad accounts that X account has a role on in X Ads Manager. Everyone in the workspace then works through it, within their role (see Members).

  1. Open Integrations and select Connect X.
  2. Sign in to X and allow everything X asks for.
  3. X sends you back to the X page with X connected. Your ad accounts appear as soon as the first sync finishes.
  4. Turn on the ad accounts you want in Pluto Ads. Every ad account starts off, and nothing of it is read until you turn it on. Then turn on the X accounts your ads run as: they start off too.

If you cancel at X, the page says X isn't connected: connect again when you're ready. Members see Not connected and "Ask an admin to connect X." instead of the button.

What connecting brings in

  • Ad accounts the X account has a role on, with the role and X's review of the account.
  • X accounts your ads run as: each ad account's own X account, and others whose posts it can repost.
  • Payment methods of each ad account that's on, with the currency the account spends in. Pluto Ads reads them and never changes them: cards are added in X Ads Manager.

Pluto Ads uses X Ads Manager's words: a launch publishes a campaign with its ad groups and ads.

Ad accounts, X accounts and payment methods

Select Manage next to X on Integrations to open the X page.

  • Ad accounts lists each account with its currency and its switch. A row says more only when something differs: X's review of the account (In review at X, Not approved by X), the connected X account's role when it limits what Pluto Ads can do there, or what the account needs at X.
  • X accounts lists, per ad account that's on, the X accounts its ads run as, each with its username and its switch. Reposts only marks an X account whose posts the ad account can repost but not post as.
  • Payment methods lists each ad account's payment methods, with what's left of a credit line. Can't pay for ads marks one that X won't charge.

Each ad account's row has a menu with Open in X Ads Manager and Copy ad account ID.

Turn ad accounts on and off

Admins turn an ad account on or off with its switch. Members see which are on.

  • On: Pluto Ads reads the account's X accounts and payment methods and offers it for new launches. It counts toward your plan's ad accounts.
  • Off: Pluto Ads stops reading the account and no longer offers it anywhere. It no longer counts toward your plan. Turning it on again picks up from there.

New ad accounts start off. Each sync lists the ad accounts the X account has a role on, so one it gets a role on later shows up after the next sync, off, without reconnecting.

Pro turns on up to 3 ad accounts per platform across your organization's workspaces, counted apart from other platforms'. Business and Enterprise turn on as many as you need. Ad accounts that are on always stay on.

Turn X accounts on and off

Admins turn an X account on or off with its switch. Every X account starts off.

  • On: offered wherever an ad's X account is chosen.
  • Off: not offered anywhere, and an ad can't publish as it. Ads already live as it go on.

With no X account on, the page says No ad can publish until an X account is on.

Roles

X decides what the connected X account's role allows in each ad account, so it decides what Pluto Ads can do there. Roles are given in X Ads Manager.

Your roleWhat Pluto Ads can do
Account administratorEverything, including reading leads
Ad managerPublish and change campaigns, ad groups and ads
Creative managerCreate and change ads
Campaign analystRead the account and its results
Organic analystNothing in the ad account: ask for one of the roles above

Posting as the ad account's X account takes one more permission in X Ads Manager when you connect as someone else: Post on behalf.

What an ad account needs at X

The row saysWhat it meansWhat to do
Add a payment method in X AdsThe ad account has no payment method that can pay for ads, so X won't run them.Select Open X Ads Manager and add one.
Account administrator needed for leadsX shares leads only with an Account administrator of the ad account.Ask an Account administrator to connect X here, or to make you one in X Ads Manager.
In review at XX is reviewing the ad account.Wait for X's answer in X Ads Manager.
Not approved by XX didn't approve the ad account for advertising.Check the account in X Ads Manager.

Conversion events

Conversion events on the X page lists each ad account's conversion events, read from X when the page opens. An ad group with the Conversions goal optimizes for one of them, chosen in the launcher.

  • Each row shows the event's name, its type (Purchase, Add to cart, Sign up and the rest X offers), how long after a click and after a view a conversion counts, and whether X has seen it fire on your site: Not seen yet, or Last fired with when.
  • Copy install code, in a row's menu, copies the code X wrote for the event. Add it to the page where the conversion happens, such as the order confirmation page.

People who can publish also see:

  • New conversion event: a name, a type, how many days after a click (1, 7, 14 or 30) and after a view (none, 1, 7, 14 or 30) a conversion counts, and whether X may build an audience of the people who did it so your ads can reach them again. A new event counts 30 days after a click and 1 day after a view, as in X Ads Manager.
  • Edit in a row's menu changes the same things.
  • Delete in a row's menu deletes the event at X for good. Ad groups that optimize for it keep their goal at X.

Making and changing conversion events takes an Account administrator or Ad manager role on the ad account (see Roles). The Agent and MCP clients do the same with manage_platform_conversion_event, after you approve.

Audiences

The Audiences section of the X page lists, per ad account that's on, the account's audiences as X has them now: customer lists, website visitors, app users, look-alikes, audiences another account shared, and the account's Do-not-reach list. Each row has its type and how many people X matched, or why an ad group can't target it yet: Matching while X matches a new list, Fewer than 100 matched until X has matched 100 people active on X.

People who may publish make and change the account's own lists:

  1. Select New list, choose the ad account and Customer list, and give the list a name unique in the account.
  2. Paste one person per line, or select Choose CSV file. Each person can have an email, a phone number with its country code, an @username, an X user ID and a mobile device ID; a file's first line may name its columns (Email, Phone, Username, X user ID, IDFA). Pluto Ads counts the people it will send and the rows with nothing X can match, which it leaves out. A list takes any number of people: Pluto Ads sends them to X in the sizes X takes.
  3. Select Make list. The new list is in ad groups' audience picker right away, and X serves it once it matched 100 people.

Pluto Ads hashes every email, phone number, username and ID before it reaches X (SHA-256, as X requires) and keeps none of them: only the list's ID, its name and how many people were sent.

A list's menu has Add people, Remove people (also how you honour someone's opt-out), Rename, Copy ID and Delete. Deleting a list at X is for good; ad groups that targeted it then reach everyone else their audience names. Website, app and look-alike audiences are X's to fill, so their menu only copies the ID.

The Do-not-reach list keeps its people out of every campaign of the ad account for 13 months. An ad account has one: select New list and Do-not-reach list to make it, from emails and phone numbers only.

Agents do the same with list_platform_audiences and manage_platform_audience (see Agents).

Syncing

  • We sync when you connect and every hour after that.
  • Sync now, on the X page, syncs right away. Last synced says when the last one finished.

X API usage

Reading replies, who wrote them and hiding a reply go through X's API, which X charges for. Each workspace has its own amount for the month, and X API usage on the X page shows what this month's calls cost so far against it. When most of it is used, replies are read less often, then again from next month; replying and hiding a reply still work until the month's amount is used.

Import from X

Campaigns that already run on X can become launches you manage in Pluto Ads. See Import from X for what comes in, and how.

Reconnect X

X can end access, for example when you remove Pluto Ads under Connected apps in your X settings, or when the X account hasn't been used with Pluto Ads for about six months. The X page then shows X access ended with Reconnect, and syncing waits until an admin reconnects. Reconnecting signs in again and reads your ad accounts again; turn on the ones you use.

Disconnect X

Admins open the more actions menu next to Sync now on the X page, select Disconnect, and confirm Disconnect X? with Disconnect X. What Pluto Ads read from X is deleted from the workspace at once (see What stays in Pluto Ads). Your launches and the history of changes made in Pluto Ads stay saved.

To connect another X account, disconnect first, then connect as that X account.

What stays in Pluto Ads

X's terms for its Ads API decide where what Pluto Ads reads from X may go, and for how long Pluto Ads keeps it.

It shows in the Pluto Ads app only. Until X agrees in writing that it may leave, what X reports shows to people signed in to Pluto Ads and goes nowhere else: names, statuses and settings as X has them, results, payment methods, lead forms and the answers in leads, and replies with their text. These get Pluto Ads' own records and the IDs of X's objects, and nothing X reported:

  • the Public API and connected agents: each field that holds what X reports is null, with withheld: true beside it;
  • the MCP server, the same way;
  • Agent and the AI steps of loops, because their model provider is outside Pluto Ads;
  • webhooks, exports, Slack and email.

Pluto Ads' own records travel as always: your launches and drafts, approvals, jobs and what they did, and who changed what in Pluto Ads.

It's kept for 90 days at most.

  • Results: the last 90 days.
  • Leads: 90 days after they arrive.
  • Replies: their text for 90 days. Who wrote a reply shows as X has it and isn't stored.
  • Ad accounts, X accounts, payment methods, campaigns, ad groups and ads: as long as each sync reads them again, and never longer than 90 days after the last read.

It's deleted when access ends. Disconnecting X, X ending access, or connecting the workspace as another X account deletes what Pluto Ads read from X for that workspace: at once, and its results within minutes. Your launches, and the history of changes made in Pluto Ads, stay.

Good to know

  • One X connection per workspace. Workspaces of the same organization can connect the same X account, and share its access: disconnecting one leaves the others connected, and Pluto Ads ends its access at X when the last one disconnects.
  • One X account connects to one organization. Connecting it in a second organization answers This X account is connected in another Pluto Ads organization: disconnect it there, or connect another X account.
  • If connecting fails, start again from Integrations in the same browser and finish within 15 minutes. An organization without a plan is read-only and can't connect until an owner or admin chooses one.
  • Agents and scripts can read, sync and disconnect X through the MCP server and the Public API. Connecting always takes a person allowing access at X.