Analytics

How your ads perform across the workspace: spend, purchases and ROAS for any period, straight from Meta, X and LinkedIn.

The dashboard

Open Analytics in the sidebar. Overview is the workspace dashboard. Launches lists your launches with what each spent (see Launch results).

The default dashboard shows:

  • Tiles for Amount spent, Purchases, Cost per purchase, Purchase ROAS, Link CTR and CPM, each with its change against the comparison and its trend over the period.
  • Charts of amount spent, purchases, purchase ROAS and cost per purchase over the period.
  • The Purchase funnel beside Top launches by amount spent, with each launch's share of the period's spend.
  • Top ads by purchases, with their amount spent, purchase ROAS and link CTR, and hook and hold rate for video.
  • Hook rate and Hold rate over the period, then Ad set performance.

In Ad set performance, select an ad set or a campaign to open it in its launch. One that isn't in Pluto narrows the dashboard to it instead. Ad sets are listed by amount spent, most first; select a column's header to sort by it, and again to reverse the order.

Analytics for Brevanne over the last 30 days compared with the previous period: amount spent, purchases, cost per purchase, purchase ROAS, link CTR and CPM, with amount spent and purchases over time.
Analytics shows spend and results across every launch, with the previous period for comparison.

Hover a rounded value for the exact one, and a card's title for what the metric means. Every number comes from Meta, X or LinkedIn: we import it and add it up, and never estimate a number they haven't reported.

Analytics needs a connected ad platform. Until you connect one, the page says Connect an ad platform. See Meta.

Choose the period

The toolbar sets what the numbers cover. The dashboard opens on Last 30 days, compared with the previous period.

The Analytics toolbar: Last 30 days, Compare: Previous period, the attribution menu set to Ad set attribution setting (as in Ads Manager), and Filter.
Pick the date range and what to compare with.
  • Period: Today, Yesterday, Last 7 days, Last 14 days, Last 28 days, Last 30 days, Last 90 days, Last week, Last month, Last quarter, Last year, Month to date, Quarter to date, Year to date, Black Friday, Cyber Monday, or a custom range.
  • Comparison: No comparison, Previous period (the same number of days right before), Previous year or Custom.
  • Attribution setting: which purchases Meta credits to an ad: Ad set attribution setting (as in Ads Manager) (Meta's default: each ad set's own setting, the numbers Ads Manager shows), 7-day click, 1-day click, 28-day click or 1-day view. The first time anyone picks a setting, its numbers take a few minutes to import. Meta no longer reports 7-day and 28-day view, so they aren't offered.

With a comparison, larger cards show the change by the value, for example +$25.05 (+5.01%), and number cards show the percentage alone. Rates such as Link CTR show only the relative change. When either period has no value, no change shows. Hover the change to see what it's taken between: the previous period's value, so the value minus it is the change, and the change in full where the card shows only the percentage (a rate's in percentage points).

Each day follows the ad account's own time zone, so Today means today where the account runs. While a day in the period isn't over there yet, trend lines end at the last full day and continue as a dashed line, So far: a day that has just begun shows what it has so far instead of a drop. Totals include it.

A change never sets part of a day against a whole one. While today isn't over, the change compares the days that are over with as many days of the comparison period. Its tooltip shows both periods' values over those days, so they add up to the change, and says which days are left out. Today compared with yesterday shows So far instead of a change until the day ends. Pluto Ads keeps numbers by day, not by hour, so it can't set today so far against the same hours of yesterday.

Filter

Select the filter icon to narrow the numbers by Ad account, Campaign, Ad set or Launch, or by a segment of the audience: Age, Gender, Country, Region, Placement, Platform (Facebook, Instagram, Audience Network, Messenger, Threads), Device, Hour of day or Ad format. Filters show as chips under the toolbar: remove one with its close button, or all of them with Clear.

Segment filters combine the way Meta splits its numbers: age and gender together, or one of the others on its own. Country with age, for example, isn't something Meta reports, so the second one asks you to remove the first. While a segment filter is on, the numbers use the ad set attribution setting (as in Ads Manager), and reach, frequency and unique clicks are blank: they count people, and Meta doesn't report them per segment. A comparison is made only when the segment numbers cover the comparison period too.

Breakdowns

Split any table or card by a segment to see where your money goes and what it brings back:

  • Age, Gender, or both together
  • Country and Region
  • Placement (platform and position, such as Instagram Stories or Facebook Feed) or Platform alone
  • Device the ad was seen on, and the Device type (mobile app, mobile web or desktop)
  • Hour of the day, in the ad account's time zone, for dayparting, and Time of day (viewer's time zone)
  • DMA region, the US market areas, and Platform & device together
  • Device people acted on and Where people acted, after seeing the ad, and the other ways Ads Manager splits actions: Post reaction type, Video sound, Video view type and Carousel card
  • Action type: every action Meta counts, including your custom conversions
  • The parts of a flexible or dynamic creative ad: Primary text, Headline, Image, Video, Call to action, Website URL and Ad format
  • Product, for catalog ads

Meta keeps numbers per segment for 13 months, so breakdowns reach back 13 months while the totals reach back 37. For a single campaign, ad set or ad, segment numbers cover the last two weeks. Segment numbers update once a day, a little behind the totals; recent days are read again as Meta restates them. The breakdown says through which day its numbers are read in full, so today's segment numbers arrive the next day.

Meta doesn't split purchases and other website or app conversions by Region, DMA region, the viewer's time zone, Product or the breakdowns of actions (Device people acted on, Where people acted, Post reaction type, Video sound, Video view type, Carousel card). Those breakdowns leave purchases, their value, carts, checkouts and landing page views out, and say so; they are never shown as 0. The totals over the whole account have them. Breakdowns of actions and by action type split the actions only, so spend and impressions are blank there. Hourly numbers carry no video metrics, and creative part breakdowns carry spend, impressions, clicks and actions only.

Breakdowns by the device an ad was seen on (alone or with its platform), and by the viewer's time zone, need Meta to turn them on for the ad account in Ads Manager. Until it does, that breakdown is blank for that ad account and everything else still shows.

When Pluto starts reading a newer kind of field (action types, video plays, watch time, rankings), it reads every ad account's older days again with it, newest first. Until it's done, the toolbar says from which day those numbers are complete, and a period reaching further back shows them for the days already read.

Metrics

We add up Meta's counts over the ads and days in view, then compute each ratio from those sums, the way Ads Manager does. Ratios are never averaged.

MetricHow it's calculated
FrequencyImpressions / Reach
CPMAmount spent / Impressions * 1,000
Link CTRLink clicks / Impressions
Cost per link clickAmount spent / Link clicks
Cost per landing page viewAmount spent / Landing page views
Cost per purchaseAmount spent / Purchases
Purchase ROASPurchase value / Amount spent
Conversion ratePurchases / Link clicks
Average order valuePurchase value / Purchases
Hook rate3-second video plays / Impressions
Hold rateThruPlays / 3-second video plays
Average watch timeTotal time watched / Video plays
Cost per ThruPlayAmount spent / ThruPlays
Cost per outbound clickAmount spent / Outbound clicks
Cost per add to cartAmount spent / Adds to cart
Cost per checkout initiatedAmount spent / Checkouts initiated
Cost per registrationAmount spent / Registrations completed
Cost per app installAmount spent / App installs
Unique link CTRUnique link clicks / Reach
Cost per unique link clickAmount spent / Unique link clicks

Amount spent, impressions, reach, link clicks, landing page views, purchases, purchase value and ThruPlays are as Meta reports them. Purchases follow the attribution setting you chose. Link CTR and cost per link click count link clicks only, while Meta's CTR and CPC count all clicks.

Beyond these, Pluto Ads reads:

  • Video: plays, plays at 25, 50, 75, 95 and 100% of the video, ThruPlays and average watch time.
  • Engagement: post engagement, reactions, comments, shares, saves and Page likes.
  • Conversions: registrations, content views, searches, payment info added, contacts, subscriptions, app installs and messaging conversations started, alongside purchases, adds to cart, checkouts and leads.
  • Any other action Meta counts, including your custom conversions: pick it by name under Actions in the metrics library, as a count, a value or a cost per action.
  • Unique clicks and unique link clicks, which count people like reach does. They show for any period.
  • Meta's quality, engagement rate and conversion rate rankings for each ad, from the last day in the period that has one: above average, average, or below average among the bottom 35%, 20% or 10% of ads.

Reach, frequency and the unique counts come from Meta for exactly the period you chose. For a period that isn't one of the presets, Pluto Ads asks Meta for it when you open it, which can take a few seconds the first time.

Top launches by amount spent can end with Not from a launch: spend no Pluto launch accounts for, such as campaigns made in Ads Manager. An ad that stayed in Meta inside a launch's campaign or ad set, such as a dynamic creative ad, counts toward that launch. While Keep in sync is still bringing your campaigns into Pluto, that line reads Not imported yet with how many campaigns are in so far.

Currencies

Amounts stay in each ad account's currency. We never convert or add up different currencies. When the accounts in view bill in more than one, a Currency menu appears: pick a currency, or All currencies (counts only) for counts such as impressions and purchases across every account.

How current the numbers are

The numbers on the page update by themselves as new ones arrive, without reloading and without changing your filters. There's nothing to refresh.

Meta refreshes its numbers about every 15 minutes. While an ad account has a campaign running, Pluto Ads asks Meta for its recent days every 15 minutes, and every 5 minutes while someone has Analytics open, always within Meta's rate limits. Other ad accounts update every hour. A workspace where no ad account has delivered for 28 days updates once a day.

LinkedIn's recent days update every 15 minutes for an ad account that has had impressions in the last 7 days, and every hour for the others.

A card without numbers says why: Loading or Importing while numbers are on their way, No data yet before anything is imported, No data for this period when Meta reported nothing for the period, or Couldn't load right now when the numbers couldn't be read.

When Meta refuses the numbers of an ad account that's delivering, or one hasn't imported yet, one quiet line in the toolbar says so (1 ad account not imported). It lists those ad accounts, and Open ad accounts opens the Meta page when an import failed. Disabled, closed and paused ad accounts aren't mentioned.

Now and then Meta can't produce an ad account's numbers for a day, even when asked for in smaller parts. Every other day still imports, the day keeps the numbers it already had, and a quiet line in the toolbar says Couldn't read some days from Meta, with the ad accounts and days in view. Those days are read again the next day; once Meta answers, the line goes away.

Recent days aren't final: a purchase a week after a click is credited back to the day of the click. Each import re-reads today and the 3 days before it, and once a day the last 28, so recent purchases and ROAS can rise a little. Meta stops changing its numbers after 28 days.

When you connect Meta, the last 90 days import first. Older days follow in the background, back to the 37 months Meta keeps. Until they arrive, cards for an older period say Importing.

LinkedIn

With more than one ad platform connected, a platform menu in the toolbar switches the dashboard between them. It opens on the platform you used last, and with only LinkedIn connected it opens on LinkedIn with no menu. Each platform's numbers show on their own: Pluto never adds Meta and LinkedIn together.

  • UTC days. LinkedIn reports by UTC day, so Today on LinkedIn runs from midnight to midnight UTC. Hover the date button to see it.
  • Conversions follow their conversion rule. LinkedIn counts each conversion in the click and view windows set on its conversion rule in Campaign Manager, so there's no attribution setting to choose.
  • The last 3 days may still change. LinkedIn can restate them: conversions sent through its Conversions API can take up to 72 hours to arrive. While the period includes them, the date button's tooltip says so.
  • What LinkedIn reports, in Campaign Manager's words. Total spent, impressions, clicks, landing page clicks (clicks that open your ad's destination URL), leads, conversions, cost per conversion, total conversion value, return on ad spend (total conversion value divided by total spent) and video views. Return on ad spend shows once your ads have conversions. Landing page CTR and cost per landing page click count landing page clicks, where Campaign Manager's Average CTR and Average CPC count every chargeable click. Purchases, purchase value, landing page views, ThruPlays, hook and hold rate are Meta's, so they never show on LinkedIn.
  • Reach and frequency show when the view covers exactly one ad account, campaign or ad set.
  • How current. Today and yesterday update every 15 minutes for an ad account that has had impressions in the last 7 days, and every hour otherwise. The last 7 days are read again every day and the last 90 every week. Connecting brings in the last 365 days, which is as far back as LinkedIn's terms let Pluto keep them. Earned (viral), event length and job metrics, and dwell time, update once a day; segments every 6 hours (see below).

Until a LinkedIn ad account is connected, the LinkedIn view says No LinkedIn ad accounts, with Connect LinkedIn.

LinkedIn's dashboard, filters and launches

  • Its own cards. LinkedIn's view shows what LinkedIn reports: total spent, impressions, landing page clicks, landing page CTR, leads, cost per lead, engagement rate, follows, conversions, cost per conversion, total conversion value and return on ad spend, total spent over time, top launches, cost per landing page click, average CPM and ad sets (amount spent, leads, cost per lead and landing page CTR for each). Customize changes Meta's dashboard.
  • LinkedIn's own numbers. Under the ad sets, a number card shows each of LinkedIn's own metrics below that your ads produced in the period, compared with the one before. A metric your ads didn't produce (sends without message ads, say) gets no card.
  • Filter by LinkedIn ad account, campaign, ad set or launch.
  • Launches keeps the platform you chose. A launch with campaigns on several platforms is one row with its campaigns under it, each with its platform's icon, what it spent and its results (leads on LinkedIn). Its results page shows LinkedIn's numbers for its whole delivery, led by its campaign objective's key result as Campaign Manager reports it: leads and cost per lead for Lead generation, conversions and cost per conversion for Website conversions, landing page clicks and cost per landing page click for Website visits and Job applicants; Brand awareness and Engagement show impressions and CPM, since Pluto doesn't read their key result per ad. Each ad set shows its leads and cost per lead, and its ads' review and delivery read in LinkedIn's words: an ad LinkedIn still reviews counts as in review, not live.

LinkedIn's own metrics

Beyond amount spent, impressions, clicks, landing page clicks, leads and conversions, Pluto Ads imports every metric LinkedIn's reporting offers, in Campaign Manager's words. They show on LinkedIn only, in the totals and in each campaign's, ad set's and ad's row, and you can rank ads and build loop conditions on them.

GroupMetrics
EngagementEngagements, engagement rate, cost per engagement, reactions, likes, comments, reposts, comment likes, follows, other engagements, clicks to your Page, average dwell time
LeadsLead form opens, lead form completion rate, qualified leads, cost per qualified lead, leads with a work email and their share of leads, talent leads, appointments scheduled
ConversionsPost-click and post-view conversions, beside conversions and total conversion value
VideoVideo starts, start rate, views at 25, 50 and 75%, completions, completion rate, watch time, average watch time, full-screen plays
Document adsViews at 25, 50 and 75% of the document, completions, downloads
Carousel adsCard impressions, card clicks, card CTR
Message and conversation adsSends, opens, open rate, cost per send, cost per open, button clicks, banner clicks, link clicks in the message, headline impressions and clicks, contact info shares, interested clicks
Events and jobsRegistrations (after a click and after a view), cost per registration, event views and views over 15 seconds, 30 seconds and 2 minutes, event watch time, job applications and apply clicks (after a click and after a view), cost per job application
EarnedViral impressions, clicks, landing page clicks, engagements, reactions, comments, reposts, follows, leads, conversions, video views, video completions, registrations and job applications: what your ads earned when members shared them
AudienceAudience penetration: the share of your target audience your ads reached, for one ad account, campaign or ad set over 92 days or less

Rates and costs are computed from the period's sums, never averaged. Watch times read in seconds and minutes. Average dwell time, how long more than half of an ad stayed on screen, is LinkedIn's own figure for the period, like reach: it shows for the periods Pluto Ads reads reach for (such as the last 7, 14, 28, 30 or 90 days, last week or last month) and one ad account, campaign or ad set. A metric LinkedIn didn't report is left out, never shown as 0.

LinkedIn's segments

Breakdown, under the cards, splits LinkedIn's numbers by who saw your ads and where they ran:

SegmentWhat it shows
Job titleThe job titles of the members who saw your ads
Job functionTheir job function, such as Marketing or Engineering
SeniorityTheir seniority, such as Entry or Director
IndustryTheir company's industry
Company sizeTheir company's number of employees
CompanyThe companies they work at
Country, Region and CountyWhere they are
Conversion actionEach conversion rule's conversions
PlacementWhere the ad showed, on LinkedIn or on the LinkedIn Audience Network
DeviceThe device the ad showed on
Serving locationOn LinkedIn, off LinkedIn, or unknown
Carousel cardEach card of a carousel ad

Each row carries amount spent, impressions, clicks, landing page clicks, CTR, CPC, CPM, leads, conversions and their costs, video views, and LinkedIn's own metrics where the segment has them. Reach and frequency aren't available per segment. A conversion action splits only the conversions, and a device has no conversions.

The first nine are demographic segments. LinkedIn keeps its members private, so:

  • They're for the whole period. Pluto Ads asks LinkedIn for the numbers of exactly the period you chose, for the ad account, campaign or ad set you're looking at, as Campaign Manager shows them. Adding up days or ad sets would lose values that LinkedIn leaves out of each day on its own. The chart over days still adds up days, so it can show a little less than the totals.
  • Small values are left out. A value with fewer than 3 events, or an ad too few members engaged with, isn't reported.
  • Only the top values. For each ad and day, LinkedIn keeps the 100 values with the most impressions, so long lists such as job titles or companies end there.
  • Total spent isn't adjusted for over delivery. LinkedIn reports demographic cost before its over delivery adjustment, so it can add up to more than you were billed. Loops don't check spend or costs by demographic.
  • They arrive later. Demographic numbers take 24 to 48 hours to appear, so the last 3 days may still change.
  • Older periods in whole months. LinkedIn keeps daily demographics for 6 months. A period that starts earlier has to start on the 1st of a month and end on a month's last day (or today).
  • No conversion value or ROAS, and no carousel numbers. LinkedIn doesn't report them by demographic segment.
  • Not by ad. LinkedIn reports demographics for ad sets and up, so they can be filtered by campaign or ad set but not by ad or launch.
  • A company you didn't target can appear, for example when members work at two companies, change jobs during the campaign, or when audience expansion is on.

Segments update every 6 hours while your ads deliver, and once a day otherwise. Pluto Ads keeps the last 365 days, as far back as LinkedIn's terms let us keep its reporting (demographics by day for the last 6 months, as LinkedIn keeps them): when you connect LinkedIn, the last 30 days arrive first and older ones follow over the next days, within LinkedIn's limits. A demographic period is read from LinkedIn the first time someone looks at it, and kept. Company names, job titles, industries and places are LinkedIn's own, in English; a name LinkedIn hasn't given yet shows as the value alone.

LinkedIn doesn't allow its demographic data (job titles, job functions, seniorities, industries, company sizes, companies and places) as input to AI. So the Agent, AI steps in loops and the MCP server don't read demographic segments; Analytics, the API and loop steps without AI do. The Agent can still read every LinkedIn metric and the conversion action, placement, device, serving location and carousel card segments.

X

With X connected, the platform menu offers X, and with only X connected Analytics opens on it. X's numbers show on their own: Pluto never adds them to another platform's.

  • The ad account's days. X reports by day in each ad account's own time zone.

  • Conversions follow their conversion event. X counts each conversion in the windows set on its conversion event in X Ads Manager, so there's no attribution setting to choose.

  • The last 4 days may still change. X's numbers are final after a day, and what you were billed can change for three days after an ad ran. While the period includes those days, the date button's tooltip says so. Pluto reads the last 3 days again every day and the last 14 every week, when X processes its last billing adjustments.

  • What X reports, in X's words. Amount spent, impressions, clicks (every click on an ad, likes included), link clicks, engagements, likes, replies, reposts, follows, app clicks, video views and views at 25, 50 and 75%, purchases and total conversions (X adds up purchases, sign-ups, site visits, downloads and custom conversions). Results, leads, ThruPlays, hook and hold rate and outbound clicks are other platforms', so they never show on X.

  • Each campaign's own metrics. Under the cards, X metrics by campaign lists every X campaign in view with its objective and the metrics X defines for it, worked out the way X does:

    • Engagements: engagement rate and cost per engagement.
    • Website traffic: CPM, click rate, cost per link click, total conversions, conversion rate and cost per conversion.
    • App installs: CPM, app click rate, cost per app click and cost per install.
    • Followers: CPM, follow rate and cost per follow.
    • Video views and Pre-roll views: CPM, video view rate and cost per view.

    X's rates are over impressions. A launch's results page shows the same row for its campaign.

  • Reach and frequency show when the view covers exactly one campaign, as X reports them for the period.

  • Everything X reports. Under the campaigns, Everything X reports lists every other number X gives for the period, in X's groups, each only when X reported it:

    • Engagement: engagements, likes, replies, reposts, follows, app clicks, card engagements, qualified impressions and carousel swipes.
    • Billing: billed engagements.
    • Video: video starts, 3-second, 6-second and 15-second views, video completions and video button clicks.
    • Media: media views and media engagements.
    • Website conversions: site visits, sign-ups, downloads, custom conversions, and purchases after a view and after an engagement.
    • App conversions, for ad accounts that track them: installs, purchases, sign-ups, re-engagements, adds to cart, checkouts started, content views, key page views, and lifetime purchases and sign-ups.
    • Reach and frequency, for one campaign.
  • Breakdown. Below it, Breakdown splits the numbers:

    • Placement: where the ads ran (on X, the X Audience Platform, Spotlight, Trends), with impressions, engagements, clicks and amount spent, for the ad account or one campaign and any period of the last 90 days.
    • Age, Gender, Device, Region, Metro area and Conversion event: one campaign's numbers as X splits them, on X or on the X Audience Platform. X prepares these when you ask, for at most the period's last 45 days; regions and metro areas are within the country you choose. Pluto reads them from X each time and never keeps them.
  • How current. Today and yesterday update every 15 minutes for an ad account that is delivering, and every hour otherwise. Connecting brings in the last 90 days.

  • A number X hasn't reported is blank, never 0. When X's reporting doesn't answer for a while, Pluto keeps the last numbers it read and asks again; it never fills a gap with a guess.

  • Kept for 90 days, inside Pluto. X's terms let Pluto keep what it reads from X for 90 days, so X's numbers go back 90 days at most, and they are deleted when you disconnect X. They show here in the app: exports, API keys, connected agents, webhooks and notifications carry no X numbers.

Until an X ad account is switched on, the X view says No X ad accounts, with Connect X.

Launch results

Select Launches at the top of Analytics. Published lists the launches that spent in the date range (the last 7 days at first), whenever they went out, and the ones published in it, with their Amount spent and Results (Meta's own results, each ad set's goal, as in Ads Manager's Results column). Published shows when each went out; for a campaign brought in from Meta, when it was created there. A launch with several campaigns is one row with its campaigns under it. A launch that hasn't started yet is marked Scheduled. A dash in Amount spent or Results means the platform reported nothing for it in the date range; point at it to see why. Drafts lists the rest with Open launch. Filter by ad account, search, and sort by Most spent, Newest first or Most ads.

A published launch with one campaign opens its results page from Most recent launches on Home, or from its notification in the Inbox. The results cover the launch's whole delivery:

Launch results for Always on, Vitamin C Serum since it was published: $93,751.74 spent, 3,879 purchases, $24.17 per purchase and a purchase ROAS of 3.58, amount spent over time, and its two ad sets.
Each published launch has its own results page.
  • Tiles for Amount spent, Purchases, Cost per purchase, Purchase ROAS, Purchase value, Impressions, Link CTR and Cost per link click.
  • Amount spent over time, and Ad sets with each ad set's results, most spent first. Select an ad set to open it in the launch, or a column's header to sort by it.
  • Whether the launch is Published or Partially published, and how many ads are in each delivery status, such as Active or Paused.

Until results arrive, the page says why, for example Not published yet or Waiting for the first results. See Publishing.

Customize the dashboard

The dashboard belongs to the workspace: everyone sees the same one. Changing it needs a role that can edit the workspace.

  1. Select Customize.
  2. Add metrics from the library in the sidebar, grouped into Delivery, Engagement, Conversions, Video and Breakdowns. Breakdowns has Amount spent by placement, Amount spent by platform, Purchases by age and gender and Purchases by country. Drag cards to move them and drag a corner to resize.
  3. Use Add section for a titled group of cards, and Reorder sections to move sections.
  4. Select Save dashboard. Nobody sees your changes until you do.
Customizing the Analytics dashboard: the metrics library on the left, the dashboard's cards, and Add section, Reorder sections, Reset to default, Cancel and Save dashboard.
Customize the dashboard with the metrics your team reads.

Reset to default brings back the default layout, and Cancel leaves everything as it was. If a teammate saves while you edit, Someone else saved this dashboard offers Keep my layout, Use their layout or Review their layout.

Change history

Every change to a campaign, ad set, ad or your ad account's spending limit is kept, whoever made it: you or a teammate in Pluto Ads, the Agent, a loop, a connected agent or API key, someone in Ads Manager, another app, or Meta itself (review, learning and delivery). Each change shows what it was before and after.

  • An ad set: open its menu in an ad set table and select Ad set history.
  • A published ad: open the ad; History is above its activity.
  • A published campaign, ad set or ad of a launch: in the launch's list of what runs in Meta, open its menu and select History. A campaign's history includes its ad sets and ads.
  • Filter by who made the change (People in Pluto, Agent and Loops, Ads Manager and other apps, Meta) and by what changed.

Changes made in Ads Manager or another app show up within minutes. The Agent reads the history before it changes a live budget, bid, status, schedule or targeting, and tells you when someone changed it in Ads Manager. A loop can start when someone changes something in Meta: see Loops.

LinkedIn's campaigns, ad sets and ads have the same History. Changes made in Campaign Manager show after the next sync, within the hour.

X's campaigns, ad groups and ads have the same History. A change made in X Ads Manager shows after the next sync as made by someone in X Ads Manager; when X shares that your connected X account made it, the history names that account. What a setting was before and after such a change is kept for 90 days, as X's terms ask, and shows only here in the app; the changes Pluto made stay for good.

Good to know

  • A number Meta hasn't reported is blank, never 0.
  • The period, comparison, attribution, filters and currency stay in the page's link, and Views saves them as a view. A fresh visit opens on the last 30 days.
  • Agents and scripts read the same numbers. See the MCP server and the Public API.