Target Price Tracker

Affiliate disclosure: Apify links on this page may include referral parameters. If you sign up through them, TrueFetch may receive a commission at no extra cost to you.

Target Price Tracker is a ready-to-run Apify Actor for collecting current public Target.com search results as structured US retail records, so teams can compare USD prices, deals, ratings, sellers, fulfillment signals, and source evidence without manual copying.

• Target US focus: Search the supported United States storefront with an explicit product keyword and result ceiling.
• 58 normalized fields: Keep identity, price, promotion, rating, seller, fulfillment, source, and processing context in one Dataset.
• Source-linked snapshots: Preserve query, rank, product URL, and search URL instead of returning untraceable price values.
• Automation-ready delivery: Export from Apify, schedule repeat runs, call the API, or expose the Actor to an MCP client.

Run a minimum 10-result test with a specific model before scaling. For programmatic use, open the API tab.

What does Target Price Tracker do?

Target Price Tracker searches public Target.com product results for the keyword you provide. It reads marketplace search entries, enriches them from public product pages when available, deduplicates products, normalizes fields, and stores up to your requested ceiling. The Actor is designed for current observations, not automatic historical-price storage.

Records can include title, brand, Target product ID, category, selling price, regular price, savings, promotions, badges, sponsored status, rating, review count, seller, delivery text, warranty, specifications, images, product URL, source search URL, query, rank, and processing time. The Dataset exposes 58 stable columns, while optional values remain null when Target does not provide a dependable value.

Target retail context is location-sensitive. Target's official help states that prices, promotions, styles, and availability may vary by store and online. The Actor therefore returns public source signals, not a guarantee that an item is in stock at every store, available for a particular ZIP code, or eligible for the same promotion at checkout.

Each run is a snapshot. Search order, ads, price, deal text, seller, and fulfillment signals may change. Keep processed_at, query, rank, product_url, and source_url with downstream analysis.

How do I run Target Price Tracker?

Open Target Price Tracker on Apify, complete all three inputs, and start the run. This guide uses the same scenario in every example:

{
  "keyword": "Apple AirPods Pro 2 USB-C",
  "country": "United States",
  "max_results": 10
}

The minimum accepted value for max_results is 10. It is a ceiling, not a promised row count. A run may store fewer records when Target returns fewer public matches, entries repeat, pages become unavailable, or items lack a publishable title and product URL.

Inspect the first Dataset before scheduling. Confirm that results actually correspond to Apple AirPods Pro 2 USB-C rather than cases, refurbished items, earlier connector versions, bundles, or unrelated accessories. Review seller, model, condition, price, deal, and fulfillment context before matching rows.

If you need history, schedule repeat runs and retain each Dataset. Compute changes outside the Actor using carefully reviewed product IDs or URLs. The Actor does not merge past runs or label an observation as a permanent price reduction.

What data does Target Price Tracker return?

The default Dataset defines 58 normalized fields. Optional values depend on what the public result or product page exposes.

Data group	Dataset fields
Images and content	main_image, image_urls, title, brand, badges, category, breadcrumbs, description, features
Identity and variants	product_id, sku, gtin, mpn, model, specifications, manufacturer, origin, energy_class, included, condition, release_date, variant_group, variants
Price and promotion	price, was_price, unit_price, currency, price_text, discount_pct, discount_text, promo_text, installment_text
Availability and demand	stock_status, stock_text, sales_text, buy_limit
Rating and seller	rating, review_count, seller, seller_url, seller_score
Fulfillment	shipping_text, shipping_cost, delivery_text, pickup_text, return_text, return_days, warranty_text
Retail context	platform, site, country, product_url, source_url, query, rank, sponsored
Processing context	processor, processed_at

The following is a schema illustration, not a live Target quote:

{
  "title": "Apple AirPods Pro (2nd generation) with USB-C",
  "brand": "Apple",
  "product_id": "12345678",
  "price": 189.99,
  "was_price": 249.99,
  "currency": "USD",
  "discount_text": "Save $60 (24% off)",
  "rating": 4.7,
  "review_count": 5821,
  "platform": "target",
  "country": "US",
  "query": "Apple AirPods Pro 2 USB-C",
  "rank": 1,
  "product_url": "https://www.target.com/p/-/A-12345678",
  "processed_at": "2026-07-21T12:00:00+00:00"
}

Use the output schema for exact field names. Null means a reliable public value was unavailable; it should not be converted automatically to zero, false, or “out of stock.”

What inputs can I configure?

Input	Type	Required	Accepted behavior	Example
keyword	string	Yes	A non-empty product, model, brand, category, or search phrase	Apple AirPods Pro 2 USB-C
country	string	Yes	The exact supported country value	United States
max_results	integer	Yes	A result ceiling from 10 through 10,000	10

The runtime rejects missing required values instead of adding hidden defaults. Country text is normalized case-insensitively to United States. max_results must be an integer; booleans do not qualify. Additional properties are rejected by the input schema.

Specific model queries are safest for a first run. Broad terms such as headphones are valid for assortment research but can mix brands, conditions, accessories, Target Plus sellers, and price bands.

What platforms and markets does Target Price Tracker cover?

This Actor is dedicated to Target for the United States (US) and uses Target.com search as its public source. It has no platform selector because the actor identity resolves to Target only. It does not search Target stores outside the supported country or combine Walmart and Amazon results in the same run.

Target's official current promotions guidance notes that pricing, promotions, and availability may vary by location and on Target.com. A public search snapshot should therefore be treated as evidence for that request and time, not universal store inventory.

The Actor does not accept a store ID, ZIP code, membership state, coupon code, or shopper account. Delivery and availability text is retained only when exposed by the public source context.

Why use Target Price Tracker?

The Actor turns repeatable Target search observations into one source-linked Dataset. Retail analysts can compare current and regular prices, discounts, promotions, ratings, sellers, and search placement. Catalog teams can retain Target product IDs, brand, model, features, specifications, warranty, and image links. Monitoring workflows can keep query and rank beside each result.

Target's official Price Match Guarantee guidance warns that search-engine prices may be outdated and that Target.com prices change frequently. A fresh, timestamped run with direct source URLs is more defensible than cached snippets, while still requiring live verification for important purchase decisions.

For Apple AirPods Pro 2 USB-C, retaining model, product ID, seller, condition, and title detail helps separate the intended earbuds from cases, accessories, older connector versions, and third-party marketplace offers.

Who is Target Price Tracker for?

• US retail analysts monitoring public Target prices, deals, assortment, and search placement.
• Brands comparing how specific models appear in Target.com results.
• Procurement teams collecting source-linked product evidence before manual review.
• Catalog teams enriching internal records with public identifiers, specifications, and images.
• Data teams building scheduled snapshots, dashboards, or change-detection workflows.
• AI-agent developers retrieving structured Target search context through API or MCP.

The Actor is not a checkout tool, store-inventory guarantee, coupon validator, or automatic repricer. Verify high-value actions on Target.com for the relevant location and time.

How can I use Target Price Tracker through the API or MCP?

The Apify API tab provides token-aware examples. The public Actor ID is HbCxcsd3sQuyGr59W.

{
  "actorId": "HbCxcsd3sQuyGr59W",
  "input": {
    "keyword": "Apple AirPods Pro 2 USB-C",
    "country": "United States",
    "max_results": 10
  }
}

Use Apify schedules for repeat observations and webhooks to notify a downstream service after completion. Retrieve rows from the default Dataset and retain their source context.

For agent integrations, follow the official Apify MCP guide. Apify documents a Streamable HTTP endpoint with OAuth and Actor selection through tools=actor. Pass all three required fields explicitly.

How much does Target Price Tracker cost?

Billing consists of one Actor start event plus one result event per row stored in the default Dataset. Local pricing metadata verified on 2026-07-21 defines:

Apify tier	Actor start	Price per stored result
FREE	$0.01000	$0.00810
BRONZE	$0.01000	$0.00783
SILVER	$0.01000	$0.00756
GOLD	$0.01000	$0.00729
PLATINUM	$0.01000	$0.00729
DIAMOND	$0.01000	$0.00729

At FREE pricing, storing 10 results costs 0.01000 + (10 × 0.00810) = $0.09100. Fewer stored records incur fewer result events. Check the current pricing tab before budgeting because prices can change.

How does Target Price Tracker compare with alternatives?

Option	Best fit	Important trade-off
Target Price Tracker	Repeatable public Target.com US search snapshots with normalized source context	Current observations; no store/ZIP selector
Product Price Tracker	Compatible multi-source retail comparisons	Broader results demand careful matching
Manual Target browsing	A few location-aware checks where a person can inspect every detail	Slow to repeat and difficult to audit at scale
Cached search-engine results	Fast discovery of possible products	Prices can be stale and context is incomplete

Use this Actor for structured public Target search collection. Use live manual review when a decision depends on a specific store, ZIP code, account, fulfillment method, or checkout promotion.

What are the limits and troubleshooting steps?

Symptom or limit	Explanation and next step
Empty Dataset	Confirm country is United States; retry a recognizable model with max_results: 10.
Fewer rows than requested	The limit is a ceiling; public matches may be sparse, duplicated, removed, or incomplete.
Price differs at checkout or in store	Target states that price and promotions can vary by location and online; verify the live context.
Availability looks inconsistent	The Actor has no store/ZIP input and does not guarantee local inventory.
Similar titles have different prices	Compare product ID, model, seller, condition, bundle, and promotion.
Optional fields are null	Target did not expose a reliable value; preserve null rather than inventing data.
Rank changes across runs	Search merchandising and sponsored placement are time-dependent.
Cost is unexpected	Count stored rows and apply the start-plus-result formula.

Public sites change and can limit requests. The Actor cannot guarantee a fixed count, completeness, ranking, response time, or uninterrupted availability. Validate a minimum-size run first.

Frequently asked questions

Does the Actor create price history automatically?

No. Schedule runs and store successive Datasets externally.

Does max_results: 10 guarantee ten rows?

No. It is a ceiling, and only valid unique public records are stored.

Does availability apply to every Target store?

No. The Actor does not take a store or ZIP input, and source signals are not universal inventory guarantees.

Are README prices live retail quotes?

No. Examples document shape. Use a fresh run and verify the product page.

Can rows be matched only by title?

Not safely. Compare product ID, model, seller, condition, bundle, and URL.

How is billing counted?

One start event per run plus one result event for each stored Dataset record.

Can an AI client call this Actor?

Yes. Use the API or Apify MCP server and pass every required input.

Related TrueFetch Actors

• Product Price Tracker for compatible multi-source searches.
• Amazon Price Tracker for Amazon country storefronts.
• Walmart Price Tracker for Walmart US, Canada, and Mexico.

Support and last updated

Open an Actor issue with the input, run ID, expected behavior, and a redacted sample. You may also use the TrueFetch group or support channel.

The public Store page checked on 2026-07-21 reported 2 total users, 1 monthly active user, 0 ratings, and 0 bookmarks. These dated Store signals are not proof of current extraction quality; this revision follows local runtime and schema evidence.

Last updated: 2026-07-21.