trackiq-amazon-branded-searchlisted

Splits every Amazon Sponsored Products and Sponsored Brands search term into branded, competitor, product-targeting and generic buckets, then shows where the ad money really goes — how much is spent on shoppers who already typed the brand, what generic search returns once brand is taken out, whether competitor conquesting pays — and checks the brand's purchase share on its own name before calling brand spend defence or waste. Use when the user asks about branded vs non-branded, brand vs generic spend, branded search, brand defence, conquesting, competitor keywords, true or non-branded ACOS, or whether ACOS is flattered by brand terms.
TrackIQ-HQ/trackiq-amazon-branded-search · ★ 0 · AI & Automation · score 72

Install: claude install-skill TrackIQ-HQ/trackiq-amazon-branded-search

# Branded vs. Non-Branded Search Takes the blended ACOS everyone reports and splits it into its honest parts: brand, competitor, product targeting and generic. Brand search almost always flatters the average, so the number that says whether advertising is growing the business is the generic one. Run it monthly, and before any conversation about "our ACOS is fine". ## Requires - The TrackIQ MCP, for `list_marketplaces`, `get_search_terms`, `get_targets`, `get_search_query_performance`, `get_product_performance` and `get_campaigns`. - **The brand's own terms**, from the Brand terms block in account.md — the brand name, its misspellings and its product-line names. Ask once. - **Competitor brand names**, from the same block. Optional; without them competitor search counts as generic, and the report says so. - **Without the MCP:** works from a search-term report exported from Campaign Manager for Sponsored Products and Sponsored Brands. ## First run Fill in a copy of `assets/account.example.md` saved as account.md beside the skill. Every TrackIQ skill reads the same file, so an account already set up for another TrackIQ report only needs the Brand terms block added. If the runtime has no filesystem, print the same block and ask the user to paste it into their project instructions once. ## Read first - `assets/pulls.md` — the pulls, why SP and SB are pulled separately - `assets/method.md` — the classifier, the buckets, and the brand-share test - `assets/checks.md