Qualified traffic window
Growth uses the latest two complete monthly estimates and only a returned growth-qualified row.
Traffic gateThis workflow returns 3–5 verified stores with rising estimated traffic.
Build a verified watchlist from qualified increases in modeled traffic estimates, observable advertising activity and active Facebook or Instagram ads in the selected market.
Example run · 13 Oct 2026 · ~2 min
Each prompt updates with your category and country
Lock Shopify, category and country before discovery.
View promptHide promptValidate this Shopify rising-traffic scope: category ecommerce_and_retail, country context US. Country means returned store-country/main-visitor-country context, never country-specific traffic. Require Shopify and the latest qualified complete monthly traffic window. Do not call tools. Return only scope and evidence boundaries. Stop after Step 1.
Compare stores moving with ads against stores where ad growth appears ahead.
View promptHide promptCost guard: before each paid Spytrend call, run the free `estimate_cost` with the same tool and arguments, estimate the cost and stay within the user's stated budget; if the user has not stated a budget, tell them the estimate before the first paid call. If pricing consent is required, show the returned terms and stop until the customer explicitly agrees; never accept on the customer's behalf. If a required call does not fit the stated budget, make no paid call and return `Budget limit prevents required research`; omit an optional call that does not fit and disclose reduced coverage. When opening ads with `get_ad`, skip multilang ads (`is_multilang`) and never call `get_media` after `get_ad`. Retry once only when `retryable=true`, after `retry_after_seconds`. Read `params.ignored` after every search; an ignored required filter never counts as applied. Cost notices are not part of the final customer report. Run correlated_growth and ad_growth_ahead discovery sequentially with exact category, country, Shopify, exclude_infrastructure=true and limit=5 per route. Preserve signal meanings, normalize domains, deduplicate and preserve route order. Return only route outcomes and candidates. Stop after Step 2.
Confirm each merchant, traffic window, active ad GEO and first-party route.
View promptHide promptCost guard: before each paid Spytrend call, run the free `estimate_cost` with the same tool and arguments, estimate the cost and stay within the user's stated budget; if the user has not stated a budget, tell them the estimate before the first paid call. If pricing consent is required, show the returned terms and stop until the customer explicitly agrees; never accept on the customer's behalf. If a required call does not fit the stated budget, make no paid call and return `Budget limit prevents required research`; omit an optional call that does not fit and disclose reduced coverage. When opening ads with `get_ad`, skip multilang ads (`is_multilang`) and never call `get_media` after `get_ad`. Retry once only when `retryable=true`, after `retry_after_seconds`. Read `params.ignored` after every search; an ignored required filter never counts as applied. Cost notices are not part of the final customer report. Use the returned discovery rows directly as compact evidence. Normalize and deduplicate exact registrable domains; never call get_shop or repeat search_shops(q=domain) for a returned discovery domain. Confirm direct fit, country context, latest complete-month global estimate and growth signal. In retained order, verify up to five candidates: run one exact-domain Meta search per candidate for the selected country with active status and `limit=1`, then open at most one representative ad per candidate. Require detailed active status, selected-country delivery, matching offer and exact first-party destination. Stop verifying when five candidates are checked or the next search plus detail does not fit the stated budget. Return only qualified/unresolved/excluded counts and Complete/Partial. Stop after Step 3.
Turn verified evidence into readable store profiles and inspection priorities.
View promptHide promptUsing retained evidence only, write a table-free watchlist under 300 words with 3–5 qualified stores (fewer only when fewer qualify). Show offer, latest complete-month global estimated visits/period, qualified change, signal group, verified active Meta evidence and one Why inspect it. Add What stands out, Inspect first and Evidence & limits. Name the category and country in plain words, never as slugs or codes. Hide service name, tools, calls, raw IDs, timing, tokens, retries and run summaries. Do not rerun research. End exactly: `Traffic figures are third-party estimates and Meta activity is observable evidence. Their relationship is correlational and does not prove conversions, revenue, ROAS or profitability.` Stop after Step 4.
Cost guard: before each paid Spytrend call, run the free `estimate_cost` with the same tool and arguments, estimate the cost and stay within the user's stated budget; if the user has not stated a budget, tell them the estimate before the first paid call. If pricing consent is required, show the returned terms and stop until the customer explicitly agrees; never accept on the customer's behalf. If a required call does not fit the stated budget, make no paid call and return `Budget limit prevents required research`; omit an optional call that does not fit and disclose reduced coverage. When opening ads with `get_ad`, skip multilang ads (`is_multilang`) and never call `get_media` after `get_ad`. Retry once only when `retryable=true`, after `retry_after_seconds`. Read `params.ignored` after every search; an ignored required filter never counts as applied. Cost notices are not part of the final customer report. Use the connected Spytrend MCP to find Shopify stores in **ecommerce_and_retail** with returned country context **US**, a qualified increase in estimated traffic and independently verified active Meta advertising. Execute every research stage in this prompt in one turn. Apart from mandatory pre-call cost notices, do not emit intermediate responses and do not stop after scope validation. Stop early only for invalid input or unavailable required evidence. Return only the final customer report. 1. Validate the supported Shopify category and country. Country is returned store-country or main-visitor-country context only; it is not country-specific traffic, headquarters, shipping or customers. Traffic must use the latest qualified complete monthly window. 2. Run the `correlated_growth` and `ad_growth_ahead` store-discovery routes sequentially with exact category, country, platform Shopify, `exclude_infrastructure=true` and `limit=5` each. Preserve the distinct signal meanings. Normalize domains, deduplicate by registrable domain and preserve returned route order. 3. Use the returned discovery rows directly as compact evidence. Normalize and deduplicate exact registrable domains. Never call `get_shop` or repeat `search_shops(q=domain)` for a returned discovery domain. Confirm Shopify identity, direct category fit, returned country context, latest complete-month global traffic estimate, traffic quality and returned growth signal. 4. Verify up to five compact-qualified candidates in retained order. For each, run one exact-domain Meta search sequentially for the selected country with active status and `limit=1`, then open at most one representative ad. Require detailed active status, country delivery, matching offer and exact first-party destination. A store qualifies only when both the traffic signal and active-ad gate pass. Aim for 3–5 qualified stores; end verification after five candidates or when the next search plus detail does not fit the stated budget, and disclose reduced coverage. 5. Traffic estimates and ad counts alone do not qualify a store. Do not infer country-specific traffic or causation. Required discovery/verification failure makes the run Partial; completed zero is Complete. Retry only on explicit `retry_after_seconds` guidance. Write a table-free report of no more than 300 words. Show 3–5 qualified stores (fewer only when fewer qualify). Include offer, latest complete-month global estimated visits and period, qualified percentage change, returned signal group, verified active Meta evidence and one reason to inspect. Add `What stands out`, `Inspect first`, `Evidence & limits`, and useful unresolved relationships only when material. Label merchant destinations `Website` or `Landing page`. Use `Evidence` only when MCP explicitly identifies a stable first-party research resource link. A merchant destination, image CDN, preview or media URL is never `Evidence`. Name the category and country in plain words, never as slugs or codes. Hide service name, internal labels, routes, tools, calls, raw IDs, UTC timing, elapsed time, tokens, retries, pagination and run summaries. End exactly: `Traffic figures are third-party estimates and Meta activity is observable evidence. Their relationship is correlational and does not prove conversions, revenue, ROAS or profitability.` Only after `Show supporting record`, use retained responses for non-sensitive route and verification details without rerunning research.
A live run on 13 Oct 2026 used Ecommerce and Retail with United States as the main visitor country. Five Shopify stores were checked in route order; four passed the traffic, category, country and active-ad checks.
| Shopify store | Traffic and Meta signal | Verified ad evidence |
|---|---|---|
| 01Velvet CaviarPhone cases and accessories | 2,096,446 estimated September visits, up 32.21%. Ads and traffic moved together; profile-wide launches rose from 233 in July to 483 in September. | Verified · US · activeMirror camera lens protector for iPhone velvetcaviar.com |
| 02MagBakMagSafe phone cases | 1,162,357 estimated September visits, up 34.18%. Ads and traffic moved together; profile-wide launches rose from 722 to 2,268. | Verified · US · activePre-order case for the next iPhone magbak.com |
| 03AlpakaBags and everyday carry | 1,116,066 estimated September visits, up 18.21%. Ads and traffic moved together; profile-wide launches rose from 478 to 1,668. | Verified · US · activeMetro Crossbody bag alpakagear.com |
| 04Party CityParty supplies | 929,211 estimated September visits, up 12.94%. Ads and traffic moved together on a small ad base: 11 launches in July, 34 in August, 21 in September. | Verified · US · activeBirthday party kits for 8–16 guests partycity.com |
All four verified stores came from the group where monthly traffic estimates and profile-wide newly observed ads rose together from July to September.
Five more stores were returned where advertising rose faster than traffic; they stayed unchecked because the five-store verification limit was reached first.
Every displayed store has a separately opened active US Meta ad leading to its own product or collection page.
Published by Spytrend from a dated, bounded run.
Growth uses the latest two complete monthly estimates and only a returned growth-qualified row.
Traffic gateThe profile must confirm Shopify, a merchant surface, category fit and a qualified traffic history.
Store gateA detailed active Meta ad must confirm the country, category, offer and first-party destination.
Ad gateThe workflow verifies no more than five stores and returns fewer rather than weakening a gate.
Coverage ruleModeled monthly traffic, qualified growth, store profile context, observable Meta activity and one verified selected-market ad.
Store normalization, cautious comparisons between the two signal groups and inspection priorities.
Causation, live visits, complete inventory, targeting, conversions, revenue, ROAS, profitability and complete market coverage.
A traffic-growth filter alone can surface technical pages, incomplete histories or stores whose advertising is aimed elsewhere. This workflow combines qualified modeled traffic growth with observable Meta activity, then checks the merchant and an active ad separately.
The result is a research watchlist for ecommerce discovery. It helps identify stores worth inspecting without describing them as successful, profitable, high-converting or caused to grow by advertising.
Spytrend data this workflow usesIt uses qualified complete-month modeled traffic history and observable Meta activity signals, then verifies the merchant and current ad separately.
No. Shop discovery confirms observed traffic from that country. A separate active-ad check confirms Meta delivery.
No. Traffic estimates and advertising activity are research signals and do not prove causation, sales or profitability.
A promising store remains there when its final country, category, status or landing-route relationship cannot be confirmed.
Connect Spytrend MCP, copy prompt 1 and continue through the four steps.