Skip to main content
An audience is a group of people a product is for. Campaigns and UGC videos are written for one, the same way the app works: first the audience, then the ads. The flow takes three calls:
  1. Create a product. LocalAds reads it and generates its audiences automatically. They are saved as soon as they are written; there is nothing to approve.
  2. List the product’s audiences and pick one.
  3. Create a campaign or a UGC video with that audience’s id as audience_id.
Audiences are free. Listing them needs products:read; adding, editing and generating them needs products:update (products:delete to archive).

Wait for the audiences

A new product generates its audiences once its details are read, usually within a minute or two. GET /products/{product_id} shows how far along it is:
generation_status is generating while they are being written, then ready. If it reads failed, generate more.

List and pick one

Every audience listed is saved and ready. Pick any one.

Make ads for it

Pass the audience’s id as audience_id:
audience_id is required when creating a guided campaign, video concepts or a UGC video, so an audience is never skipped by accident. To make something for everyone on purpose, send "audience_id": null. See Create a campaign and Create a UGC video for the rest of each request.

Add an audience in your own words

LocalAds turns the description into a full audience and returns it with 201 Created. The description is who the audience is, in your words, 3 to 2,000 characters.

Edit an audience

Describe what should change:

Generate more audiences

Ask for a fresh set at any time. They are saved automatically, like the first ones:
This answers 202 Accepted. Poll GET /products/{product_id}/audiences until generation_status is ready.

Archive an audience

This answers 204 No Content. The audience stops appearing in lists and can no longer be passed as audience_id. Campaigns and videos already made for it are not affected.
Last modified on September 30, 2026