Archive = hide from default view, preserve data. Delete = soft delete (may permanently remove on platform). Archive reversible; delete harder.

Archive vs delete

In Wevion's Ads Manager the destructive action is Delete — there is no separate "Archive" action, no Unarchive, no Restore, no "Show deleted" toggle, and no 30-day recovery window in the UI (verified use-reports-actions.ts). "Delete" calls each platform's delete endpoint (Meta with a delete_action); on success the row's status becomes ARCHIVED and the UI shows an "archived" confirmation. In effect, Delete behaves like archive on most platforms (stops delivery, hides from active view). Treat it as final and export/audit-log what you need beforehand.

Who is this for

Mediabuyers cleaning up Ads Manager after campaigns end. Anyone wondering "should I archive or delete this old campaign".

What "Delete" actually does

There is a single destructive action, Delete:

• It calls the platform's delete endpoint (Meta uses a delete_action).
• On success, Wevion sets the row's status to ARCHIVED and shows an "archived" confirmation.
• On most platforms this stops delivery and hides the entity from the active view — functionally like archive.
• There is no separate Archive action, no Unarchive, no Restore, and no "Show deleted"/"Show archived" toggle or 30-day recovery window in the UI.

When to use Delete

• Campaign ended its run and you want it out of the active view
• Accidental campaign creation or a clearly redundant duplicate
• Test campaign with no value
• Compliance erasure requests (full account deletion is separate — see acc-117)

Because there is no in-UI restore, export or note anything you need first (the audit log and CSV/PDF exports are your record).

How to delete

Single delete

• Use the row's action (⋮) → Delete (there is no right-click context menu)
• A delete confirmation dialog appears (it does not require typing the campaign name)
• Submit → runs async; the row's status becomes ARCHIVED when done

Bulk delete

Select multiple → toolbar Delete → confirmation dialog. See am-105 bulk actions. Deletes run per-row (grouped by account); one row can fail while others succeed.

Cascade behavior

• Delete campaign: its ad sets + ads are removed with it
• Delete ad set: its ads are removed; other ad sets in the campaign are unaffected
• Delete ad: only that ad is removed

Platform-side effects

Delete maps to each platform's own removal/archive state:

In practice, Delete stops delivery and removes the entity from the active view. In Wevion's status column the row then reads as error (ARCHIVED/DELETED/REMOVED all map to the error type — see am-113).

Recovery

There is no in-UI restore or recovery window. Once deleted, recreate the campaign (e.g. from a template or by duplicating a similar one) if you need it back. Keep exports / audit-log records as your backup.

When to use Delete: decision tree

Do you still need this entity in the active view?├─ Yes → keep it (pause it if you just want to stop spend)└─ No  → Delete (it moves to an archived/removed state; not restorable in-UI)

RBAC + audit

There is no separate Archive/Unarchive/Restore action. Delete is audit-logged.

What you'll see

After delete:

• The row leaves the active view
• Its status reads as error where surfaced (ARCHIVED/DELETED/REMOVED)
• An "archived" success toast confirms completion

Common issues

• "Deleted but still spending": the platform may not have synced; force-sync the account. Pause first if you need spend to stop immediately.
• "Some rows deleted, others failed": bulk delete runs per row/account; retry the failed ones.
• "I can't find a restore/undo": there is no in-UI restore — recreate the campaign if needed.

Best practices

Pause before delete

Pause first → verify spend stops → then delete. Prevents "deleted but still delivering" surprises during sync.

Export before deleting

Since there's no restore, export a CSV/PDF (or rely on the audit log) before deleting anything you might need later.

Reserve delete for genuine cleanup

• Test campaigns with $0 spend
• Accidental duplicates
• Compliance erasure requests

FAQ

Is there both an Archive and a Delete in Wevion?

No — there is a single destructive action, Delete. There is no separate Archive action, no Unarchive, no Restore, and no "Show deleted"/"Show archived" toggle. Delete calls the platform's delete endpoint (Meta uses a delete_action) and, on success, the row's status becomes ARCHIVED — functionally like archive on most platforms (stops delivery, hides from active view).

Can I recover a deleted campaign in Wevion?

There is no in-UI restore or recovery window. Once deleted, recreate the campaign if you need it back (e.g. from a template or by duplicating a similar one). Keep CSV/PDF exports and the audit log as your record before deleting.

Does deleting a campaign in Wevion also delete its ad sets and ads?

Yes. Deleting a campaign removes its ad sets and ads with it. Deleting an ad set removes its ads while leaving other ad sets in the campaign unaffected, and deleting a single ad affects only that ad.

Should I pause a campaign before deleting in Wevion?

Yes. Always pause first, verify that spend stops, then delete. This prevents the "deleted but still delivering" surprise where the platform hasn't yet synced the change and the campaign keeps spending.

Who can delete campaigns in Wevion?

Delete is the more restricted action — recommended at the manager role, with admin able to force it. There is no separate archive/unarchive/restore permission because those actions don't exist. Delete is recorded in the audit log.

Related articles

• Pause and resume a campaign
• Bulk actions — pause, resume, edit budget
• Read your audit log