Skip to content
Picaro.AI Picaro.AI Prompt Library

Set monthly KPI targets

Registering the target ACoS and thresholds used by each tool (bid optimization, budget adjustment, negative keyword detection, and others) in advance against the account removes the need to specify them every time. Managing favorite keywords (monitoring targets) and configuring alert thresholds also happens in this category.

When to use this category

Section titled “When to use this category”
  • “Set the April target as sales 15M JPY and ACoS 15%.”
  • “Register a TACoS cap of 12%.”
  • “Mark important keywords as favorites and monitor the gap between bid and suggested bid.”
  • “Adjust the alert threshold to 30%.”

Prompt 1: Register or update monthly KPI targets

Section titled “Prompt 1: Register or update monthly KPI targets”

🎯 Goal

Section titled “🎯 Goal”

Register monthly targets for sales, ACoS, TACoS, and ROAS against the account so that subsequent prompts can reference them automatically.

📋 When to use

Section titled “📋 When to use”
  • Setting sales and ACoS targets at the start of the month
  • Updating the ROAS target
  • Registering the TACoS cap

📝 Prompt

Section titled “📝 Prompt”
Register the KPI targets for {{TARGET_MONTH}}:
- Sales target: {{SALES_TARGET}}
- Ad spend cap: {{AD_BUDGET_CAP}}
- ACoS cap: {{TARGET_ACOS}} (either 0.15 or 15 is accepted)
- ROAS target: {{TARGET_ROAS}}
- TACoS cap: {{TARGET_TACOS}}
- Market share target: {{TARGET_MARKET_SHARE}}

Placeholders:

PlaceholderDescriptionDefault source
{{TARGET_MONTH}}Target month (e.g., May 2026)User input (required)
{{SALES_TARGET}}Monthly sales target (e.g., 15M JPY)User input
{{AD_BUDGET_CAP}}Monthly ad spend cap (e.g., 2M JPY)User input
{{TARGET_ACOS}}Target ACoS (e.g., 15% or 0.15)User input (the baseline auto-referenced by downstream prompts)
{{TARGET_ROAS}}Target ROAS (e.g., 8)User input
{{TARGET_TACOS}}Target TACoS cap (e.g., 12%)User input
{{TARGET_MARKET_SHARE}}Market share target (e.g., 5%)User input (optional)

⚙️ What the AI does

Section titled “⚙️ What the AI does”
  1. Normalize input values — Accepts ACoS / TACoS / market share in either percent or decimal form and unifies the internal representation as a decimal between 0 and 1.
    • Why normalize: “15”, “15%”, and “0.15” should be stored as the same value so that downstream prompts never reference the wrong figure.
  2. Resolve the target month — Converts expressions such as “April”, “May 2026”, or “next month” into YYYY-MM format.
    • Why normalize: Keeps the per-month reference key unique so that overwrites and reads always target the intended record.
  3. Confirm overwrite of existing targets — If KPI targets already exist for the same month, the diff is shown before the overwrite and explicit confirmation is requested.
    • Why confirm: Mid-month changes to the target shift downstream judgments such as bid optimization, so accidental overwrites must be avoided.
  4. Show the registered values and their reference paths — Returns a table listing the saved values and which prompts will reference them automatically.
    • Why show reference paths: Operators see at first registration that they no longer need to write “target ACoS X%” every time.

📊 Example output

Section titled “📊 Example output”

KPI targets registered for May 2026.

ItemRegistered valuePrompts that reference it
Sales target15M JPYMonthly budget pacing, Month-end report
Ad spend cap2M JPYAdjust budgets, Monthly budget pacing
Target ACoS15.0%Adjust bids, Add negative keywords
Target ROAS8.0Month-end report
TACoS cap12.0%Month-end report, Dashboard KPIs
Market share target5.0%Search data analysis

Subsequent prompts no longer require “target ACoS 15%” to be written out. To change a value, send something like “Update the ACoS target for May 2026 to 14%.”

🔒 Safety guards

Section titled “🔒 Safety guards”
  • When KPI targets already exist for the same month, a diff table is shown and explicit confirmation is requested before overwrite (to prevent accidental overwrites).
  • ACoS / TACoS / market share values outside the 0–1 range are rejected (percent inputs are automatically divided by 100).
  • Registration, updates, and deletions are all recorded in the audit log (so that “when was what changed” is traceable later).
  • Attempts to change targets for past months (months that are already closed) trigger a warning.

🚦 Execution mode

Section titled “🚦 Execution mode”
PhaseStateConditions
Phase 1 (current)One-shotAvailable with the Picaro connection alone
Phase 2 (Q3 2026)Month-start reminder”Saved prompt” support nudges monthly KPI registration on day 1
Phase 3 (Q4 2026)Auto reminder + confirmationSummarizes the prior month’s actuals and prompts confirmation of this month’s targets
Phase 4 (2027)Auto-suggestion from historical actuals + approvalComputes target values from the last three months of actuals; finalized on approval

👉 What to do next

Section titled “👉 What to do next”
  • Adjust bids — The registered target ACoS is auto-referenced as {{TARGET_ACOS}}
  • Adjust budgets — The registered ad spend cap becomes the starting point for daily budget optimization
  • Daily operations check — The registered targets become the baseline for daily progress-gap reviews

❓ Frequently asked questions

Section titled “❓ Frequently asked questions”

Q. Should ACoS be entered as “15” or “0.15”? A. Both are stored as the same value. “15”, “15%”, or “0.15” are all treated internally as 0.15 (= 15%).

Q. Is it safe to change targets mid-month? A. Changes are allowed, but bid optimization and negative keyword detection will use the new value afterward. Be aware that judgments produced before the change will no longer line up with judgments produced after it.

Prompt 2: List, retrieve, or delete KPI targets

Section titled “Prompt 2: List, retrieve, or delete KPI targets”

🎯 Goal

Section titled “🎯 Goal”

List, retrieve, and delete registered monthly KPI targets to keep the history of past settings organized.

📋 When to use

Section titled “📋 When to use”
  • Viewing all registered targets at once
  • Checking the target values for a specific month
  • Removing past targets

📝 Prompt

Section titled “📝 Prompt”
- List: Show all registered KPI targets.
- Retrieve: Show the KPI targets for {{TARGET_MONTH}}.
- Delete: Delete the KPI targets for {{TARGET_MONTH}}.

Placeholders:

PlaceholderDescriptionDefault source
{{TARGET_MONTH}}Target month (e.g., 2026-05)User input (required for retrieve and delete; not needed for list)

⚙️ What the AI does

Section titled “⚙️ What the AI does”
  1. Identify the operation type — Determines from the prompt whether the request is list, retrieve, or delete.
    • Why identify: Reads and deletes act on the same KPI target data, so the operation must be unambiguous to prevent mistakes.
  2. Resolve the target month — For retrieve and delete, normalizes the target month to YYYY-MM format.
  3. Confirm before deletion — For delete operations, shows the registered content for the target month and asks for explicit “okay to delete” confirmation.
    • Why confirm: Deletion cannot be undone, so the risk of acting on the wrong month is minimized.
  4. Record in the audit log — On deletion, logs “when” “which month’s target” was deleted.
    • Why record: Makes “who deleted what and when” traceable later and clarifies operational responsibility.

📊 Example output

Section titled “📊 Example output”

Registered monthly KPI targets

Target monthSales targetTarget ACoSTarget ROASTACoS cap
2026-0515M JPY15.0%8.012.0%
2026-0414M JPY16.0%7.513.0%
2026-0313M JPY16.0%7.513.0%

To check a specific month, send “Show the KPI targets for 2026-05.” To delete, send “Delete the KPI targets for 2026-03” and a confirmation will appear before deletion.

🔒 Safety guards

Section titled “🔒 Safety guards”
  • Delete operations display the target month’s contents and request explicit confirmation before proceeding.
  • Deletions are also recorded in the audit log (operator, timestamp, target month).
  • Attempting to delete KPI targets for the current or a future month triggers a warning about downstream prompts (bid optimization, etc.).
  • The list view shows up to the past 12 months by default (older entries require a separate instruction).

🚦 Execution mode

Section titled “🚦 Execution mode”
PhaseStateConditions
Phase 1 (current)One-shotAvailable with the Picaro connection alone
Phase 2 (Q3 2026)Month-start reminderNotifies at month start if last month’s target was left undeleted, when relevant
Phase 3 (Q4 2026)Auto reminder + confirmationSuggests auto-archiving targets older than six months
Phase 4 (2027)Auto-suggestion from historical actuals + approvalAppends “auto-suggested values for next month” alongside the list view

👉 What to do next

Section titled “👉 What to do next”

Prompt 3: Configure alert thresholds for favorite keywords

Section titled “Prompt 3: Configure alert thresholds for favorite keywords”

🎯 Goal

Section titled “🎯 Goal”

Register the three alert thresholds and aggregation frequency for favorite keywords so that monitoring can begin.

📋 When to use

Section titled “📋 When to use”
  • Tightening bid monitoring for favorite keywords
  • Catching sudden drops in impression share quickly
  • Reverting alerts to the defaults

📝 Prompt

Section titled “📝 Prompt”
Update the alert configuration for favorite keywords:
- Bid vs. suggested bid: {{BID_VS_SUGGESTED_THRESHOLD}}
- Bid vs. actual CPC: {{BID_VS_ACTUAL_CPC_THRESHOLD}}
- Impression share drop: {{IS_DROP_THRESHOLD}}
- Aggregation frequency: {{FREQUENCY}}


Send "reset" to restore the defaults.

Placeholders:

PlaceholderDescriptionDefault source
{{BID_VS_SUGGESTED_THRESHOLD}}Gap threshold between bid and suggested bid (e.g., 30% or 0.3)User input (default 30%)
{{BID_VS_ACTUAL_CPC_THRESHOLD}}Gap threshold between bid and actual CPC (e.g., 30% or 0.3)User input (default 30%)
{{IS_DROP_THRESHOLD}}Threshold for impression share drop magnitude (e.g., 30% or 0.3)User input (default 30%)
{{FREQUENCY}}Aggregation frequency (weekly)User input (default weekly)

⚙️ What the AI does

Section titled “⚙️ What the AI does”
  1. Normalize thresholds — Accepts inputs in the 0–1 range and converts percent notation to a decimal internally.
    • Why 0–1: Thresholds are treated as ratios internally, so mixed input formats can still be stored equivalently.
  2. Hold unmentioned items at their current values — Thresholds not referenced in the prompt keep their existing values.
    • Why hold: A single-item adjustment should not force the operator to re-enter the others.
  3. Apply aggregation-frequency constraints — If monthly is specified, falls back to weekly and states this clearly in the response.
    • Why fall back: The internal alert aggregation batch only supports up to weekly; making the fallback explicit prevents misunderstanding.
  4. Initialize on reset — When the prompt contains reset, all thresholds revert to the defaults (30% / weekly).
    • Why 30% default: This value sits above average noise and, in production, keeps notification volume from becoming excessive.

📊 Example output

Section titled “📊 Example output”

Favorite keyword alert configuration updated.

ItemOld valueNew value
Bid vs. suggested bid30.0%25.0%
Bid vs. actual CPC30.0%30.0% (held)
Impression share drop30.0%20.0%
Aggregation frequencyweeklyweekly

Next aggregation: morning of Mon, 2026-05-25 To reset, send “Reset the favorite keyword alert configuration.”

🔒 Safety guards

Section titled “🔒 Safety guards”
  • Thresholds outside the 0–1 range are rejected (out-of-range inputs prompt re-entry as an error).
  • A monthly specification automatically falls back to weekly (a spec constraint; made explicit in the response).
  • On reset, the prior values are included in the response (making rollback from an accidental reset easy).
  • Configuration changes are recorded in the audit log.

🚦 Execution mode

Section titled “🚦 Execution mode”
PhaseStateConditions
Phase 1 (current)One-shotAvailable with the Picaro connection alone
Phase 2 (Q3 2026)Month-start reminderProposes threshold revisions at month start based on last month’s alert-firing frequency
Phase 3 (Q4 2026)Auto reminder + confirmationPresents auto-adjustment candidates derived from the past four weeks of firing data
Phase 4 (2027)Auto-suggestion from historical actuals + approvalComputes the optimal threshold per keyword; applied on approval

👉 What to do next

Section titled “👉 What to do next”

Prompt 4: Register favorite keywords

Section titled “Prompt 4: Register favorite keywords”

🎯 Goal

Section titled “🎯 Goal”

Register the favorite keywords to monitor against the account so that they are included in bid-trend analysis and the three alert checks.

📋 When to use

Section titled “📋 When to use”
  • Adding important keywords to the monitoring set
  • Auto-selecting high-revenue keywords from candidates and adding them to favorites
  • Bulk-registering keywords given only as strings

📝 Prompt

Section titled “📝 Prompt”
(Candidate-extraction mode)
Register the top {{TOP_N}} search terms by revenue from the last {{LOOKBACK_WEEKS}} weeks as favorites.


(Bulk-registration mode)
Bulk-register the following keywords as favorites: {{KEYWORD_LIST}}

Placeholders:

PlaceholderDescriptionDefault source
{{LOOKBACK_WEEKS}}Look-back window for candidate extraction (e.g., 4)User input (default 4 weeks)
{{TOP_N}}Number of entries to extract by revenue rank (e.g., 20)User input (default 20)
{{KEYWORD_LIST}}Array of keyword strings for bulk registrationUser input (required in bulk-registration mode)

⚙️ What the AI does

Section titled “⚙️ What the AI does”
  1. Detect the mode — Determines from the prompt whether the request is candidate-extraction mode or bulk-registration mode.
    • Why detect: Favorite registration via data-driven selection and via string input have different backend handling, even though the surface action is the same.
  2. Filter in candidate-extraction mode — Sorts and filters by revenue / ACoS / CVR / CPC / impressions / substring match.
    • Why multiple metrics: Revenue alone would miss “high revenue but high ACoS” keywords, so multiple axes are provided as decision input.
  3. Resolve identifiers in bulk-registration mode — For keywords given only as strings, resolves match_type and campaign_id from actual data in the background before registering.
    • Why auto-resolve: Operators should not have to specify match_type for every keyword; string input alone should be enough to execute.
  4. Apply the upper limit — If the total would exceed 50 entries when combined with existing registrations, warns and stops the registration.
    • Why 50: This level keeps the monitoring screen readable and the alert-firing volume sustainable in production.

📊 Example output

Section titled “📊 Example output”

Favorite keyword candidates: 20 entries (top 20 by revenue)

Search termRevenue, last 4 weeksACoSCVRImpressions
amino acid shampoo184,500 JPY12.4%8.2%12,400
refill shampoo162,300 JPY14.1%7.5%10,900
… (18 more) …

Current favorites: 12 → after registration: 32 (cap 50) To proceed, reply “Execute.” To exclude items, send something like “Exclude items 3 and 7 and register the rest.”

🔒 Safety guards

Section titled “🔒 Safety guards”
  • Registrations that would push the total over 50 entries are blocked, and the operator is prompted to remove unneeded keywords.
  • Candidate-extraction mode is not applied unless “Execute” is sent explicitly (no changes until approval).
  • In bulk-registration mode, keywords whose match_type could not be resolved are reported in the response with the exclusion reason.
  • Registration and deletion are recorded in the audit log.

🚦 Execution mode

Section titled “🚦 Execution mode”
PhaseStateConditions
Phase 1 (current)One-shotAvailable with the Picaro connection alone
Phase 2 (Q3 2026)Month-start reminderPresents “major keyword candidates not yet favorited” at month start
Phase 3 (Q4 2026)Auto reminder + confirmationAuto-flags newly top-ranked revenue keywords as candidates; registered on approval
Phase 4 (2027)Auto-suggestion from historical actuals + approvalAuto-suggests favorite swap candidates as revenue composition shifts

👉 What to do next

Section titled “👉 What to do next”

Prompt quick reference

Section titled “Prompt quick reference”
GoalPrompt to use
Register or update monthly KPI targetsPrompt 1
Review or delete KPI targetsPrompt 2
Configure alert thresholds for favorite keywordsPrompt 3
Register favorite keywords or extract candidatesPrompt 4
Section titled “Related categories”