On the roadmap — not in the product yet
“Can I run prompts like any other ad — by the hour, by the rule?”
Run your prompts as ads. Not as a report.
Sponsored Prompts spend from your campaigns every hour of the day. Adcquire will run them the way you’d run any ad — rules, campaign bids and budgets, capped and logged — through the Amazon Ads API, once Amazon approves the connection (US only). Hour-of-day bid schedules are planned.
14 days free · no card needed · View pricing →
- 24 × 7
- hours a week a bid schedule could cover (planned)
- Daily
- Prompts and campaign reports, up to yesterday, once connected
- You decide
- which rules run alone and which ask first
The control room
A day of prompts, run by rule.
Illustration of a modelled typical day, on a demo brand: a planned bid schedule lowers campaign bids in the small hours and raises them in the evening, a rule pauses a prompt that never sells, and every change lands in the log. Nothing here is applied today: a schedule like this would need Amazon’s hourly data, and each change still waits for a person to press Send.
Prompt ads
Illustration · Little Nest · modelled typical day
00:00Tuesday
Illustration · 5 rules · 1 bid schedule (planned)
0006121824
Bids −50% — returns under 2.5×NormalBoost +25%
- PromptNow
- Is this crib safe for a newborn?On
- Does it convert to a toddler bed?On
- Which crib is better than the Wren Classic?Bid −50% until 06:00
- Is it easy to assemble on your own?On
- Why choose Little Nest?Bid −50% until 06:00
Spend today
$0
Sales today
$0
Return today
—
Illustrative model, not a forecast or a result
Budget pacing · planned (needs hourly data)$0 of $300 · on pace
- Log
Four jobs
Everything you’d do by hand, done on time.
01
Dayparting
Planned: raise or lower campaign bids by hour of day — up in the peak, down in the lull. Prompts themselves can only be paused one by one.
02
Automations
When this happens, do that: pause what never sells, fund what does, tag what names a rival. Rules run each time new data arrives. Approve each change yourself, or let a rule approve its own; a person on your team still presses Send before anything reaches Amazon.
03
Budgets and pacing
Campaign budgets moved inside the caps you set. Planned: budget pacing, once hourly data from Amazon Marketing Stream is onboarded.
04
Guardrails
Caps on every change, approval where you want it, and a log of who changed what. Changes sent through the Amazon connection can be reversed from the log.
Dayparting
Buy the hours that buy back.
Illustration: campaign return by hour (modelled; Amazon doesn’t provide prompt-level hourly data). Switch on the schedule to see which hours get lower campaign bids and which get a boost.
Illustration: campaign return by hour (modelled; Amazon doesn’t provide prompt-level hourly data) · Little Nest
00:0006:0012:0018:0023:00
Low-return hours in the week
—
modelled hours where campaign return is under the line
Spend moved, a week
—
out of the small hours, into the evening peak — modelled
Campaign return
—
up from 3.0× in the model — same budget, better hours
Illustrative model, not a forecast or a result.
Modelled on the Little Nest demo brand. Planned: raise or lower campaign bids by hour of day. Prompts themselves can only be paused one by one. Hourly data would come from Amazon Marketing Stream, which needs separate onboarding (planned, not live).
Automations
When this happens, do that.
Illustration: five rules, two weeks, on a demo brand. Each rule checks again when new data arrives and fires when its condition is met. A change is approved automatically or by you, and a person presses Send before it reaches Amazon; the change log is written as it goes.
- Ask me firstwaiting
WhenA prompt passes 30 clicks with no orders
ThenPause it on Amazon
- Approves itselfwaiting
WhenA prompt returns 3× or more for 7 days
ThenRaise its campaign budget 15%, up to $400/day
- Automaticwaiting
WhenA new prompt names a competitor
ThenTag it and send me an alert
- Planned (needs hourly data)not available yet
WhenBudget will run out before 6pm
ThenMove spend out of the dead hours
- Approves itselfwaiting
WhenA prompt mentions a word on your watch list (e.g. “non-toxic”)
ThenPause it, then tell me why
Two weeks, day by dayDay 01 of 14
- Change log
0actions0you approved$0spend saved
Illustration on a fictional demo brand · illustrative model, not a forecast or a result
Cases
Three brands, thirty days each.
Worked examples on our demo brands, modelled from their demo data — what the schedule and the rules would change. Illustrative model, not a forecast or a result. Not customer results.
The problem
Comparison prompts kept spending between midnight and 6am — parents browsing, not buying.
What ran
- Night bids −50%, 00–06
- Evening bids +25%
- Pause after 30 clicks, no orders
In the model, night hours returned 1.8×; evenings 4.2×. The bid schedule lowered night bids and raised 7–10pm bids, with the same budget.
ACOS33% → 33%
Spend that sold nothing, a month$1,120 → $1,120
Prompt sales, a month$18,300 → $18,300
Illustrative model, not a forecast or a result · worked example on a fictional demo brand, modelled over 30 days from its demo data · not a customer result
How it connects
Built for the Amazon Ads API.
Coming, pending Amazon’s approval. Once connected, Amazon reports sync daily, covering up to the previous day; changes would go back the same way — inside the caps you set, once a person on your team presses Send. And where Amazon draws a line, we say so.
From Amazon
- Prompts report — each clicked prompt: clicks, spend, orders (daily, to yesterday)
- SP campaign report — campaigns, budgets and bids (daily)
- Hourly campaign data — Amazon Marketing Stream (planned, needs separate onboarding)
Adcquire—
Read
Decide
Check
- Read
- —
- Decide
- —
- Check
- —
Each rule, each time new data arrives
Back to Amazon
- Pause or restart a prompt
- Campaign and ad-group default bids (by hour: planned)
- Campaign budgets and placement %
- Day 1Prompt paused
- Day 2Default bid +10% on 3 campaigns
- Day 3Budget +15%
- PlannedPlanned: bids +25% 17–21h
What Amazon’s API allows — and what it doesn’t
Illustration above. Adcquire’s Amazon Ads connection is coming, pending Amazon’s approval (US only) — nothing is sent to Amazon today.
- ✓Pause and restart individual prompts — through Amazon’s prompt controls
- ✓Change campaign and ad-group default bids, campaign budgets and placement %
- ✓Planned: hourly campaign performance from Amazon Marketing Stream, which arrives with a delay
- ✕Bid on one prompt by itself — Amazon doesn’t offer prompt-level bids; a prompt spends at its campaign’s cost-per-click
- ✕Write or edit a prompt — Amazon writes them from your listing
Questions
The short answers.
- Is this live today?
- Not yet — it comes with the Amazon connection, pending Amazon’s approval (US only). Today Adcquire reads the Prompts report you upload, flags what to pause and scale, and keeps the approval queue and change log; making the changes on Amazon comes after approval.
- Can I bid on a single prompt?
- No — Amazon doesn’t offer prompt-level bids. A prompt spends at its campaign’s cost-per-click, so Adcquire would move campaign and ad-group default bids, budgets and placement %, and pause or restart individual prompts through Amazon’s prompt controls.
- Where does the hourly data come from?
- Hourly data would come from Amazon Marketing Stream, which needs separate onboarding (planned, not live). Once connected, the Prompts and campaign reports sync daily, covering up to the previous day; prompt-level figures come only from the Prompts report.
- Will anything change without me?
- No. An automatic rule approves its change for you; a person on your team still presses Send before anything reaches Amazon. Anything else waits for your approval as well. Changes sent through the Amazon connection can be reversed from the log.
- Does it work with my current tools?
- It only touches the campaigns its rules cover and logs each change. Avoid having two tools set bids on the same campaign.