Tronix Login

321 STRONG · Tronix

Sign in with Google

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

or

π Placements
Admin Logout
Tronix/Amazon Advertising/Placements

Placements

Data as of —
…
Loading…

Feeding Crons

Loading cron status…

Data Provenance

Click a card for the full provenance detail.

Amazon Ads Reporting v3 — spCampaigns, campaignPlacement — groupBy ['campaign','campaignPlacement'], timeUnit DAILY, GZIP_JSON, account wsd. The multipliers arrive separately, on the v3 campaign list (dynamicBidding.placementBidding). The report and the config use two different placement vocabularies that share no substring convention, and no measurement maps one onto the other.SOURCE⤢Amazon Ads Reporting v3 —…groupBy ['campaign','campaignPlacement'],tim…tronix-sync-ads-placement-daily — Daily 11:25 AST (mac-mini), 31-day chunks newest-first with a rolling re-read plus backfill to Amazon’s parsed retention floor. Report READ only — the guard in the Ads API client refuses any body carrying placementBidding.PIPELINE⤢tronix-sync-ads-placement…Daily 11:25 AST (mac-mini), 31-day chunksnew…tronix.db.ads_placement_daily — PK (campaign_id, placement, date). The placement string is stored VERBATIM and shown VERBATIM. Joined to ads_campaign_dim, which holds the campaign state this page filters on and the placement_bidding_json the multipliers are read from.STORE⤢tronix.db.ads_placement_d…PK (campaign_id, placement, date). Theplacem…VIEW⤢This ViewOne row per ENABLED campaign: its fourplacem…

Docs & References

Agent Brief
docs/tronix/wedges/placements.md
References
None.

Edit agent brief — docs/tronix/wedges/placements.md

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