Skip to main content
Every scoring request needs an audience. It is what the persona is built from, and it conditions every score in the response. Send exactly one of audience or audience_id — not both.

Inline audiences

Define the audience in the request. Only name is required.
Inline is the right choice for one-off runs and for agents generating audiences on the fly.

Saved audiences

Reference an audience already created in your Kettio account:
A 404 means the ID does not exist or is not owned by the authenticated account.
Saved audiences are the better choice when you are comparing results over time. An inline audience that drifts between runs quietly invalidates the comparison, because scores are conditioned on the audience.

Demographics

All demographics fields are optional, and sensible defaults are applied. They shape the persona’s attitude and behavior rather than filtering anything.

Writing a description that does work

description is free text and it carries real weight — it is the part of the audience the persona reads directly.

Useful

“Women considering GLP-1 support who need credible purchase proof”Names the buying situation and the objection to overcome.

Not useful

“Our target customers”Carries no information the persona can act on.
Describe the purchase situation, not the demographic profile — the structured demographics fields already cover the profile.
Changing the audience between runs changes what is being measured. If you are comparing two sets of creative, hold the audience fixed across both.