What cannot be restored

Taseli restores exactly what it can and tells you what it couldn't. The proposal card says whether a change can be restored before you approve it.

The limits

What	Why it can't come back
1. Spend and results during the change	Clicks, impressions and spend while the change was live are history
2. Items deleted since	That part of the restore is skipped and marked
3. Removed items	Google won't make a removed item active again. Taseli recreates it with a new ID and without its old history, such as its statistics
4. Later edits by people	Taseli keeps their edit and never overwrites a human change. It alerts you to the gap between the approved and actual state
5. Changes by others	Restore covers only Taseli's changes. Your team, a former agency or another tool show in the change log as external
6. Google's Auto-apply changes	Not human and not Taseli's. Taseli opens an alert with a proposal to revert, which you approve like any proposal
7. Partly applied proposals	Only the items that worked are reverted
8. After 30 days	Manual restore ends. Create a reverse proposal by hand
9. Some change types	Each item is marked exactly restorable, restorable by a compensating change, or not restorable. The card shows this before you approve
10. Platform changes	Changes Google makes are logged with what's known. Restore is offered only where supported

When something can't be restored

Open the proposal page
See which items were restored, skipped or failed.
Open the change log
At /app/[ws]/accounts/[id]/history, see who changed what since.
Create a new proposal
If you still want the old setting, propose it and approve it.

Troubleshooting

The restore failed. The proposal page lists failed items and why, for example lost access. Reconnect if needed, then restore again within the 30 days.

Learning or delivery changed after a restore. Settings can come back. How the platform's bidding reacts to two changes in a row can't be controlled. That's one reason guards wait for mature data.