Pixel and Conversions API, once
MGP installs server-side tracking at the platform level. Every merchant on your stack inherits it. Nobody pastes a script into a website.
Meta ads
Campaigns are built against the merchant's live catalogue and their own customer list, the two things a platform has and an agency usually does not.
Meta Business Partner
What a merchant actually orders
Written the way it appears in the catalogue, in outcomes a shopkeeper recognises, not in the vocabulary of a media plan.
- Always-on lead capture
- Catalogue ads that follow stock levels
- Store traffic campaigns with a radius the merchant sets
- Retargeting from the POS customer list
- Festive burst with a fixed spend cap
What Cocomo Media delivers on this one
Catalogue feed from your data
Products, prices and availability sync from the POS on a schedule, so ads stop when stock does.
Creative from the studio
Each campaign ships with a set built by Cocomo's in-house team: statics, reels and copy in the merchant's language.
Spend caps you control
Per-merchant and per-platform ceilings, enforced by MGP before the spend reaches Meta. No surprise invoices landing on your support desk.
From order to result
Connect once
One platform-level Business Manager relationship covers your whole merchant base.
Merchant sets budget
Inside your product, with the floor and ceiling you configured.
Cocomo builds and runs
Audiences, creative sets, and weekly optimisation by a certified team.
Spend reconciles
Daily spend rows come back over the API, ready for your billing run.
MetaBusiness Partner, verified agency status since the badge existed
What platforms ask about meta ads
The merchant's, always. MGP requests partner access so it can be revoked in one click and nothing is stranded if a merchant leaves your platform.
Either the merchant's own card on Meta, or through your platform as a line item. MGP reports daily spend either way.
Yes. Rejections are worked by the Cocomo team, and the merchant sees a plain-language status rather than a Meta error code.