Tronix Login

321 STRONG · Tronix

Sign in with Google

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

or

π Dayparting
Admin Logout
Tronix/Amazon Advertising/Dayparting

Dayparting

Data as of —
SHADOW — writes nothing
Days the window opens
—: —–—UTC (yours): —–—window undecidable
…
Loading…

Arm dayparting

This begins writing to the live Amazon advertising account.

  • 0 ad group(s) in scope.
  • Pause at —, resume at —, —.
  • —–— in UTC.
  • Every tick from the next one onward corrects any ad group that does not match.
  • Disarming returns to shadow immediately and writes nothing further.

Feeding Crons

Loading cron status…

Data Provenance

Click a card for the full provenance detail.

The measured Scale Insights rule — OFF 23:00 to 04:00 America/Los_Angeles, every assigned ad group. Read from Scale Insights own UI and confirmed independently from our bid log: 52 of 52 observed changes were entity_type=ad_group, field=state. Timezone read from GET /v2/profiles for ads profile 4236473380793700, not inferred from the marketplace.SOURCE⤢The measured Scale Insigh…OFF 23:00 to 04:00 America/Los_Angeles,every…PIPELINE⤢dayparting reconcilerRuns frequently and corrects thedifference b…tronix.db.ads_daypart_run / _action — One row per tick including the ticks that decided nothing, so a gap is visible as a gap. Departures only in _action, with direction_risk stored per row: a failed resume is expensive, a failed pause is harmless, and the two must never be read the same way.STORE⤢tronix.db.ads_daypart_run…One row per tick including the ticks thatdec…VIEW⤢This ViewThe schedule, what the account isactually do…

Docs & References

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

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

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