Skip to content
Integrations · Meta Ads

Meta, read beside Google, without pretending the two add up.

Plireo reads Meta advertising accounts with a permission that cannot change anything, keeps the figures as history, and analyses them at channel level next to Google Ads Search. It prepares no change on Meta today.

What is read

Three levels, kept as a daily and monthly series.

The permission asked from Meta is read-only: with it, Plireo could not change a campaign even by mistake.

  1. 01CampaignObjective, daily budget, spend and results by day and by month.In progress
  2. 02Ad setFigures by day, with the attribution setting the results were counted under.In progress
  3. 03AdFigures by month, with breakdowns by placement, device and market.In progress
Two platforms, two ways of counting

Why a Meta conversion and a Google conversion are not the same unit.

Neither figure is wrong. They answer different questions, under rules each platform documents. A cross-channel view is only useful if it says where the comparison stops.

Google AdsMeta AdsWhat Plireo does
What is countedConversion actions the advertiser defines in the accountEvents the advertiser defines and the result the campaign optimises forKeeps each platform's result under its own name. Two definitions are not presented as one
Attribution windowSet per conversion action. By default 30 days after a click and 1 day after an impression; a click window can go from 1 to 90 days depending on the sourceSet per ad set, as click-through, view-through and engaged-view windows. The lengths allowed depend on the optimisation goal and the objectiveRecords the setting beside the figures, and says when a platform does not return it exactly
The day a conversion falls onThe main conversion columns are counted at the time of the click, not of the conversion; separate columns report by conversion timeAs Meta reports each day, in the ad account's own time zoneDoes not re-date either. Reads recent days again at each synchronisation, because late results change them
DeduplicationAttributes within its own clicks and impressionsAttributes within its own clicks and viewsShows the channels side by side. It publishes no deduplicated total, because it has none: a customer reached by both may be counted by both

Statements about each platform come from its documentation, linked at the foot of the page and read on 12 October 2026. Defaults can be changed by the advertiser: check the settings of your own accounts.

What you can do with it

Channel-level analysis, with the same rules as for Search.

In progress

Budget review

How spend and results moved, month over month, for the channel.

In progress

Creative performance

Which ads carry the results, from the monthly figures per ad.

In progress

Recommendations to decide on

At channel level, agreed, deferred, rejected or challenged, with your reason kept.

What is not built

No change is prepared on Meta, and that is a matter of permission as much as of code.

Preparing, approving and applying changes on Meta campaigns is part of what the first version of Plireo aims for.

It also depends on Meta. An application that manages advertising for other businesses needs a wider permission than the one Plireo holds, which Meta grants after reviewing the application and verifying the business behind it. That review is one of the next steps.

A Meta connection also expires. Plireo shows the date on the connection and asks you to reconnect before it lapses, instead of failing silently.

Where this stands today

  • Meta AdsCampaign data, analysed at channel levelIn progress
  • Recommendations and decisionsChannel-level recommendations, each agreed, deferred, rejected or challengedIn progress
  • Ask PlireoQuestions on a campaign, answered with evidence and stated uncertaintyIn progress
  • Prepared changesExact changes, validated by Google without being appliedIn progress
  • Cross-platform memoryOne memory across every connected platformPlanned

Every capability and its status →

Early access

Be among the first to use Plireo.

Plireo is in pre-launch. Request early access to be told when it opens, or apply to take part in private testing. Access opens gradually, so a request does not mean immediate access.

Paid plans open once the Google Ads, Meta, GA4 and GTM integrations are operationally validated.

Request early access