Campaigns

The Campaigns page shows synced performance and provider delivery status. A shared toolbar at the top lets you pick the provider, the connection, the date range, and refresh provider data; the view below is specific to the selected provider. If the table is empty, connect a platform and run a refresh first.

Switch between Current and Archive without mixing counts or selections. The views are two complementary parts of Noeryx's local projection: Meta owns what it reports about an object, while Noeryx records whether the local row is still active and whether its connection is retained.

• Current holds a local active row when Meta has not marked its object lifecycle as archived and every parent is Current. For Meta, that includes active, paused, review, and other non-archived statuses.
• Archive holds every other row: an object Meta still returns as archived, a row whose absence was confirmed after a complete sync, or a row retained because its connection was archived. Archiving an object on Meta moves it to Archive on the next refresh without changing its local provenance; un-archiving can move it back when the full path is current again.

Archive keeps the same provider, connection, hierarchy-level, date, and column navigation, and daily and range performance stay attached to every archived row. It is read-only toward the advertising platform: it does not sync on open, fetch live previews, change On / Off, or delete objects on Meta. The Reason column says which kind of archive a row is in: Archived on Meta for a row Meta still returns as archived, No longer available from Meta after a complete refresh and exact absence check stopped returning it without proving deletion, Deleted on Meta after a direct confirmed delete, and Connection archived when Noeryx retained history for an archived connection.

When a refresh finds a row missing, Noeryx re-reads the top missing point of that branch on Meta; children inherit the parent's outcome rather than causing extra reads. A narrow, exact "not found" result can retain the branch as No longer available from Meta. Only an explicit deleted answer can remove the confirmed local branch and its performance data, and Noeryx keeps it when an in-flight command or approval still protects the branch. If Meta still reads the row, access is unclear, a temporary failure happens, or too many absences need checking, Noeryx stops that lifecycle update: it does not move rows to Archive or delete local history. A refresh that did not complete changes nothing at all.

Working with the table

• Switch between the Campaigns, Ad Sets, and Ads levels.
• Choose a date range preset — Noeryx stores performance day by day and filters local facts for the range. When you open Current, Noeryx may also queue a cooldown-limited refresh for that range; Archive never fetches Meta on open.
• Show or hide columns and save your own column presets. Presets are per workspace and per person, so your view doesn't change anyone else's.

Delivery status

In Current, delivery status (for example, active or paused) refreshes automatically when you open or reload a level. When the selected provider and connection support writes, each Current row exposes an On / Off control. This is an explicit operator command: Noeryx checks the current value and access again, queues the durable background operation, and then refreshes the synced result. Archive preserves the last synced status and has no live status refresh or On / Off control.

Delete selected entities

When the provider supports entity deletion, select campaigns, ad sets, or ads at the current level and choose Delete. Noeryx asks for confirmation because provider deletion cannot be undone, then queues one durable command item for each selected entity.

Agent-proposed changes remain separate. Ask an agent to create a structured provider-action draft when you want an agent to propose a change. Noeryx validates that draft, sends it to Approvals for a human decision, and only then applies it through a background task. The final result and audit receipt come from that approval lifecycle.

From Archive, Delete permanently from Noeryx removes only the selected archived local branch and its reporting facts. Noeryx first recomputes an exact impact preview and blocks confirmation if the branch changed. This action never calls Meta. It is offered only after Noeryx records the row as unavailable from Meta or deleted. A row Meta still returns as archived, or a row retained because its connection was archived, remains local history rather than a local-delete candidate.