Skip to content
Picaro.AI Picaro.AI Prompt Library

Account Profile

The Account Profile is where you register the “goals and assumptions” the AI agent references when it proposes and analyzes for a given account. The metrics you set here (total sales target, ad spend, TACOS, and so on) become the basis for home-chat proposals, scheduled-task proposals, and report commentary.

The key point: this is where you communicate intent — it is not where you enforce a hard ceiling on ad spend. How to put a firm cap on total ad spend is covered later in The profile’s metrics are not enforced.

Settings

Section titled “Settings”

Target month / Keep monthly

Section titled “Target month / Keep monthly”

Choose the month the metrics apply to. Tick “Keep monthly (carry over to next month unless changed)” to roll the same metrics into the following month. This supports both per-month target changes and a fixed, repeating setup.

Conditions to start operating

Section titled “Conditions to start operating”

Once you set even one account KPI, the agent is ready to start proposing. You don’t need to fill in every metric — just the ones that matter for this account.

Where this metric is used

Section titled “Where this metric is used”

Three checkboxes control where the metrics are referenced:

  • Home-chat proposals
  • Scheduled-task proposals
  • Report commentary

Unchecking one means the metric is not referenced as context in that place. So you can, for example, have daily proposals consider your targets while leaving them out of reports.

Fill from last month’s actuals

Section titled “Fill from last month’s actuals”

One button seeds each metric with last month’s actuals as the starting value. This saves you entering everything from scratch and lets you fine-tune targets from real numbers.

Metrics and priority

Section titled “Metrics and priority”

The metrics you can register are:

  • Total sales target (¥)
  • Ad spend (¥)
  • TACOS (%)
  • TACOS incl. DSP (%)
  • Ad sales target (¥)
  • CPA ceiling (¥)
  • LTV target (¥)
  • ACoS (%)

The number to the left of each metric is its priority (1 is highest). Reorder with the arrows on the left or by dragging the handle on the right, and the agent references the metrics in that order.

Memo

Section titled “Memo”

A note field for operators that is not used as context. It doesn’t feed the agent’s judgment, but it is kept in the change history — handy as a reminder of “why we set this target.”

Saving and deleting

Section titled “Saving and deleting”
  • Edits auto-save. No explicit save action is needed.
  • Use “Delete KPI” to remove the registered set of metrics.
  • KPI targets are saved only via the Picaro connection. Whether you set them in the dashboard or over the MCP connection (chat), they are referenced automatically by every tool as the same KPI targets. To register the same targets from chat, see Set targets for sales, ad spend, and ACoS.

Metrics / History tabs

Section titled “Metrics / History tabs”

The “Metrics / History” tabs at the top of the screen let you review past setting changes — when, and which metric, was changed.

The profile’s metrics are not enforced

Section titled “The profile’s metrics are not enforced”

The metrics you enter in the Account Profile are targets (intent) that the agent references when it proposes and analyzes. They are reference information only — not a limit that guarantees “this value is never exceeded.”

  • The profile’s “Ad spend (¥)” is a target the agent aims for. Entering an amount here does not create any mechanism that forces total ad spend to stay under it (and strict numeric consistency between metrics is not assumed).
  • If there is a policy or condition you want the agent to respect, register it in the profile and also state it explicitly in each request (prompt). The agent reads both the profile and your request when it proposes. Intents like “stay under this limit” or “adjust only within this range” take effect through this way of specifying them in the prompt.
  • For any change to budgets, bids, and the like, the agent first presents a proposal. You review it and it is applied only after you approve (nothing actually changes until you approve).

When you want a firm ceiling on total ad spend

Section titled “When you want a firm ceiling on total ad spend”

To put a firm (hard) ceiling on total ad spend, set it not in Picaro but in Amazon’s advertising console (Ad Console), by setting a portfolio budget cap. When the cap is reached Amazon automatically stops delivery, so that is what acts as the firm brake on the total.

  • Amazon-side setup (the firm ceiling): create a portfolio in Ad Console and set its budget cap (the monthly portfolio budget)
  • Picaro-side monitoring (optional): register the same amount via Adjust budgets, Prompt 2 “Register a monthly budget cap,” to track consumption from Picaro too — but this is for monitoring, not for stopping spend
Section titled “Related”