Skip to content

Automation · Operations and reporting

Ask on WhatsApp which Meta Ads campaigns had the best ROAS with Porter Metrics

Ask on WhatsApp which Meta Ads campaigns performed best: an AI agent queries your accounts in Porter Metrics and replies.

How do I know which Meta Ads campaigns had the best ROAS last week without opening Ads Manager?

You write to your Met "which Meta Ads campaigns had the best ROAS last week?". The Met confirms which user and company it is connected to in Porter, lists your Meta Ads accounts and warns you if any is available but not registered, because querying it registers it and Porter starts billing it. It checks the connector's guidance in Porter's knowledge base, picks the metrics from the catalog and runs the query. It replies with the campaigns ranked by ROAS, each with its spend. It does not pause or change any campaign.

What starts it

When someone asks for it

It starts when someone on the team asks the Met about campaign performance for a period. Each query runs on request; this procedure does not leave a scheduled report.

A manual task: someone on the team runs it with a button, or asks the Met for it in chat.

Who runs it

Ads analytics Met with Porter Metrics

Social team

This is not a named, seeded Met. It is an internal Met with Porter Metrics connected: its work ends when it delivers the figures your accounts returned, or when it tells you which account it could not query and why.

Run by the data analyst Met

Channels: WhatsApp

What you need connected

5 steps · 5 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

  1. 1

    Confirm the account and company

    The Met identifies which user and which company it is connected to in Porter, because the accounts it sees depend on the companies where your user has a role.

  2. 2

    Find the Meta Ads accounts

    The Met lists your Meta Ads accounts in Porter. If one shows up as available but not registered, it points it out, because the first query registers it and Porter starts billing it.

  3. 3

    Check the connector's guidance

    Before the first query, the Met searches Porter's knowledge base for the Meta Ads connector's step by step workflows, its common errors with their fix and its FAQs.

  4. 4

    Pick the metrics

    The Met checks the connector's catalog of metrics and dimensions to ask for spend and ROAS by campaign with the name Porter uses, instead of assuming a field that does not exist.

  5. 5

    Query and reply

    The Met runs the query over your accounts with last week's range and replies with the campaigns ranked by ROAS, each with its spend in the account's currency.

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

FAQ

Questions about this automation

Yes, if both accounts are in Porter: the query can cover several accounts and blend connectors.

Because it is available on the platform but not registered in Porter. The first query registers it and Porter starts billing it.

Not with this procedure. Pausing would be the catalog's execute action, which starts off; the admin decides in Connections whether to turn it on.

This procedure runs on request. A scheduled delivery would be a different automation, with its own trigger.

Keep going

Other automations built on the same tools

Want this automation running on your own data?

We will show it to you with your accounts connected, not with a canned demo.