Skip to main content

Meta BoBo Ads Capability to earn $$$

Feature Request

Hi Zernio team,

We are building an AI-powered advertising platform and using Zernio as our execution layer for Meta Ads via BOBO.

We would like to request support for a simplified “budget + fee split” workflow for BOBO-based ad execution.

Use case

Our system:

  1. Generates ad creative (video + copy + link)

  2. Requests a total campaign budget from the client

  3. Splits the budget internally:

    • 25% platform fee

    • 75% Meta ad spend

  4. Launches ads via Zernio using BOBO (on behalf of client)

  5. Retrieves performance data via Zernio analytics layer

Feature request

We would like Zernio to support or expose:

  • Clear BOBO execution for ad creation under client accounts

  • Ability to pass a single “total budget” input while allowing internal allocation logic at the platform level

  • Or at minimum, ensure Zernio does not constrain downstream budget handling logic when using Meta BOBO ad accounts

Why this matters

This enables a new category of AI-driven “done-for-you advertising” products where:

  • users don’t manage Meta Ads directly

  • campaigns are generated and deployed automatically

  • platforms like ours can earn from the advertising budget on the backend.

Happy to clarify or provide deeper product specs.

Thanks in advance!

Camilo@infinitecreator.com

Posted by Camilo Lopez ·
Status: Completed1 comment

Log in to comment and vote

Comments1

  • Miquel Palet López

    Team•

    Aug 26

    Nothing here is blocked on our side. Ads execute against whichever client Meta ad account you pass as adAccountId on the connected metaads account, and the budget is simply a number you send: budget.amount on POST /v1/ads/boost, or budgetAmount plus budgetType on POST /v1/ads/campaigns for campaign budget optimization. We never inspect or constrain how you derived that number, so passing 75% of a total you collected from the client works as-is, and the 25% platform fee stays entirely in your own billing layer upstream of us. Performance comes back from GET /v1/ads/insights, or POST /v1/ads/insights/reports for large asynchronous pulls.