Denha NexusPlatform · Meta

Meta Ads for agencies: form leads into the CRM, deals back into the account

ADS Beast connects Facebook and Instagram ad accounts over OAuth, reads spend and results every 15 minutes, and picks up lead form entries the moment they are submitted. Deals from the CRM go back to the account as server conversions, and the placements that waste money are off by default in new campaigns.

14 days on any plan, no card needed to start. After the click: a three-field form and the workspace.

What gets connected

Connection
OAuth: the ad account, the pages that host lead forms, and the catalogue if you need it
What is read
Campaigns, ad sets, ads, spend and results: 90 days first, then every 15 minutes
What is applied
Campaign or ad set status and budget - after confirmation in the approval queue
Campaign types
8 in the launch registry: lead forms, site leads, sales, catalogue, traffic, reach, engagement, apps
Leads
Facebook and Instagram lead forms reach the CRM with the form fields and the click identifier
Safe by default
Audience Network, right column, Marketplace and Instant Articles are off in new lead campaigns

Permissions are granted on the Meta side and revoked there too. The system sees only the ad accounts where the connecting account holds a role.

01What it looks like

A Meta account in ADS Beast: leads, conversions, placements

Screen recording: connecting a Facebook and Instagram account, a lead form entry arriving in the CRM with its bot score, a deal sent to the Conversions API, and the approval queue.

A screen recording of the product in the ADS Beast demo workspace. The clients and campaigns on screen exist for the demonstration; no real advertiser stands behind them.
02What it does

What the system does with a Meta account

01

Form leads reach the CRM, not an inbox a day later

The moment a form on Facebook or Instagram is submitted, the lead is in the CRM with its fields, its campaign and its click identifier. Each one is scored for bot signals: depending on the total it passes, gets flagged for review, or is blocked.

  • A lead in the CRM with form fields, campaign and ad
  • A bot score: from 40 points it is flagged, from 70 it is blocked
  • A check that the lead reached the client CRM, when it is passed on
02

Deals return to the account as server conversions

When a manager marks a lead as qualified or as a sale in the CRM, the system sends the event to the Conversions API every 30 minutes. Delivery then learns from real deals instead of everyone who pressed Submit.

  • Conversions API events built from CRM deal stages
  • Pixel diagnostics: is it installed, which events it sends, what is missing
  • Event match quality, visible before it starts to slip
03

The placements that drain budget are off before you start

Audience Network, the desktop right column, Marketplace and Instant Articles are where accidental clicks and unanswerable leads come from. In new lead campaigns they are off. You can switch them on, and the decision goes into the log together with the name of whoever made it.

  • A safe placement set in every new ad set
  • A guard every 1 hour that notices when placements are switched back on
  • The reason a placement is blocked, in words rather than a code
04

Spend, reconciliation and audit alongside every other platform

Spend in one currency over the same date window as Google, TikTok, LinkedIn and Microsoft. Our figures are checked against the account. The audit runs every 24 hours and looks at structure, the learning phase, creative fatigue and audiences.

  • Meta spend on the same line as the client's other platforms
  • Audit findings with the campaign, the reason and the amount of data
  • Creative fatigue: which ads stopped working, checked every 12 hours
03How it works

From connecting the account to the first lead in the CRM

Connecting takes as long as signing in to Facebook takes. After that the system works on its own, and a person confirms only what moves money.

  1. 01

    Connect the account and pages

    An administrator goes through OAuth and grants access to the ad account and to the pages that host the lead forms.

  2. 02

    Wait for the history

    Spend and results for 90 days, then a refresh every 15 minutes.

  3. 03

    Take the leads

    Every lead form entry reaches the CRM with its bot score and its form fields.

  4. 04

    Confirm changes

    Pausing, budgets, placements - all through the approval queue, with a read-back from the account once applied.

04How it fits together

Where the data comes from and what you get out of it.

Ad accounts hand over their statistics through your own OAuth apps. The system puts them into one picture, agents look for what to change, and only what you approve gets changed.

Platforms
  • Google AdsOAuth
  • MetaOAuth
  • TikTokOAuth
  • LinkedInOAuth
  • Microsoft AdvertisingOAuth
  • Windsor.aiAPI key
ADS Beast
Combines and checks
  • sync every 15 minutes
  • conversion to USD at the day rate
  • reconciliation with the native account
  • 90 days of history
What you get
  1. One spend summaryEvery account in one currency and one date window.
  2. Tasks from agentsWhat to change, where and why, linked to the row in the account.
  3. A person decidesBudgets, bids and statuses change only after approval.

Early access

See your own ad accounts the way the diagram shows them.

We are opening access to agencies in turn. Leave a work email and we will write when your turn comes, then help you connect the first account.

We use the email only to reply about access. Privacy policy

05Figures from the code
15 min
between metric refreshes
8
campaign types in the launch registry
30 min
between CRM conversion uploads
1 h
between placement guard checks
06What it does not do

What the system will not do with your Meta

  • It will not change budgets or statuses without a person confirming.
  • It will not create ad accounts, pass advertiser verification or attach cards - the account owner does that on the Meta side.
  • It will not switch on Audience Network or other risky placements quietly: switching them on is an explicit decision, and it is logged.
  • It will not treat a bot score as the truth: the lead is flagged, and a manager decides what to do with it.
07Questions and answers

Questions and answers

Which permissions are requested when connecting?

Reading and managing ads, access to business assets, and reading leads from the lead forms and the pages that host them. The product catalogue is a separate step and only if commerce campaigns need it.

How quickly does a form lead reach the CRM?

At the moment the form is submitted: Meta sends the event, the system picks up the form fields and files the lead in the CRM with a bot score. On top of that, an hourly sweep checks that no lead went missing.

What are server conversions and why are they here?

They are events the system sends to the Conversions API from CRM deal stages: qualified lead, sale. Delivery then optimises towards people who actually buy rather than people who merely submitted a form.

Why is Audience Network off by default?

Because in lead campaigns that is where most accidental clicks and unanswered leads come from. You can switch it on in the campaign settings, and the decision is logged with the name of whoever made it.

Does the system see accounts I have no role in?

No. The connection sees exactly the accounts where the signed-in user holds a role on the Meta side. That is a platform limit, and the system does not work around it.

Connect a Meta account and get your first lead in the CRM instead of the inbox

The first 14 days are free on any plan and you do not need a card to start. Lead forms, server conversions and placement protection switch on the moment you connect.

14 days on any plan, no card needed to start. After the click: a three-field form and the workspace.