Tronix Login

321 STRONG · Tronix

Sign in with Google

Access restricted to @321strong.com, @quietmine.com and @quietdc.com emails

or

π Search Terms
Admin Logout
Tronix/Amazon Advertising/Search Terms

Search Terms

Data as of —
…
Loading…

Feeding Crons

Loading cron status…

Data Provenance

Click a card for the full provenance detail.

Amazon Ads API v3 — spSearchTerm + sbSearchTerm reports — Two asynchronous reports, both groupBy searchTerm, timeUnit DAILY, capped at 31 days per request. Amazon REFUSES an earlier start date with a 400 naming its own floor, and the two reports answered different floors on the same day — measured 2026-09-23, spSearchTerm 2026-06-20 (95 days back) and sbSearchTerm 2026-07-25 (60 days back). The floor rolls forward daily and is always parsed from that 400, never hardcoded. A day not captured inside that window is destroyed permanently. Their columns differ: SP reports windowed attribution (purchases_30d, sales_30d), SB reports purchases / sales / unitsSold with no attribution horizon published at all. Amazon calls the SB report a preview and excludes campaigns whose isMultiAdGroupsEnabled flag is FALSE, so it is not a complete census of SB search terms.SOURCE⤢Amazon Ads API v3 — spSea…Two asynchronous reports, both groupBysearch…search-term ingest cron — two legs, one per program — Requests, polls and loads each report in <=31-day chunks, each leg with its own report sentinel, its own ingest-config knobs and its own window-coverage verdict. A run that filled one program and dropped the other is an ERROR, never a partial. IDs arrive as bare JSON numbers and are string-coerced at the ingest boundary — a JS number in a TEXT column renders as 348008469511398.0 and breaks every join silently.PIPELINE⤢search-term ingest cron —…Requests, polls and loads each report in<=31…tronix.db.ads_search_term_daily — One row per (search term, matched entity, day, SOURCE, PROGRAM). source and program are different axes and both are in the primary key: api and gui-export are two readings of one fact, SP and SB are two different charges. Joined to the structure mirror (ads_campaign_dim on the row's own program, ads_sp_ad_group, ads_entity) for names, placement, state and bids.STORE⤢tronix.db.ads_search_term…One row per (search term, matched entity,day…VIEW⤢This ViewCustomer search terms with their spend,traff…

Docs & References

Agent Brief
docs/tronix/wedges/search-terms.md
References
None.

Edit agent brief — docs/tronix/wedges/search-terms.md

Markdown. Saved to the DB (wedge_docs) live — no deploy. This is the brief handed to dispatched agents.
Saved successfully!
Something went wrong