Using Ad Superpowers
Understand what changed.
Enable external platform Logging for a client and interpret its status, coverage and retention.
On this page
Two kinds of history
Ad Superpowers actions record supported actions performed through Ad Superpowers, with the authenticated user, target, result and action summary. They are separate from usage records and do not reconstruct every before/after platform value.
External platform history archives changes reported by supported platform APIs, including changes made outside Ad Superpowers. The dashboard calls this Logging. It must be enabled for a client and source, either directly or through a saved workspace default for new dashboard clients.
The platform's actor can be the person who authorized a shared connection, another platform user or a source application. It is not automatically the Ad Superpowers teammate who made a request. Keep the two records distinct when interpreting who did what.
Enable Logging for a client
You need to be an owner or admin with write permission to manage Logging. Owners/admins with read-only permission can view the archive. Members do not have archive read or management access.
If Logging does not appear for an owner or admin in your workspace, contact support to check availability.
- Select the workspace and open Clients.
- Check that the client is active and has the intended supported accounts linked in its profile.
- Open Logging for the client, or use its Logging switch. Select Google Ads and/or Meta, then save the source choice (Bronkeuze opslaan).
- Inspect the source and account statuses. An enabled switch means the choice was saved; it does not prove a successful import.
- Use Platformhistorie bekijken to open that client's external history in Activity.
A source can be enabled before a usable account is linked. It then waits for a suitable connection. A draft or inactive client must become active before collection can proceed.
Set a default for new clients
In Settings → Clients, an owner/admin with write permission can save Logging standaard aan voor nieuwe klanten. This enables the Google Ads and Meta choices for new clients created through the dashboard, including account import. It does not change existing clients.
GA4 is added separately per client. A saved default also does not guarantee an import: the client must be active, accounts must be usable, and the authorizing administrator must retain the required authority. If that authority is lost, a writable owner/admin must save the default again before it applies to new clients.
Add GA4 permission separately
Open Logging for the client and add GA4-configuratiewijzigingen. When the source asks for additional permission, use its Google authorization action. Ordinary Analytics reporting access is insufficient; change history requires the additional analytics.edit permission.
After Google returns you to the clients list, reopen Logging and inspect the account status. Receiving permission, having access to the property and completing an import are separate steps. If permission was already granted, use the source-check action shown in the panel rather than repeatedly granting access without checking the cause.
Understand source coverage
| Source | What the archive can collect | Limits to keep in mind |
|---|---|---|
| Google Ads | API-supported account change events and allowed configuration details | Initial lookback is up to 30 days; Google Ads Editor changes are not supported by this source; provider omissions and incomplete periods remain visible |
| Meta | Available ad-account activities | Event types and old/new details vary; a requested 30-day lookback is not a guarantee of a complete history |
| GA4 | API-supported changes for selected properties | Requires extra permission; account-wide history and unreviewed detail types are not included |
| TikTok | Not connected to this archive | Availability of provider exports does not mean collection is implemented here |
| LinkedIn, Search Console, Merchant Center | No verified change feed in this archive | Do not interpret an empty archive as proof that nothing changed |
| Tag Manager | No full change-event archive | Container version snapshots are not a complete timeline of changes |
Collection and retention are different. Enabling Logging now cannot create a full year of past events. The archive contains only events actually imported from the source, and reports include coverage information. Check that information even when an event list is empty.
Status and recovery
| Dashboard status | Meaning | What to do |
|---|---|---|
| Uit | Logging is off for this client | Enable the intended sources if you want collection |
| Geen gekoppelde accounts | No supported account is linked for the source | Link an account and check that the client is active |
| Import ingepland | Logging is enabled; no successful synchronization is confirmed yet | Recheck the status after the import runs |
| Bijgewerkt | The latest synchronization succeeded | Inspect the coverage for the requested period; this label does not certify complete history |
| Deels actief / Deels opgehaald | Only some sources/accounts or part of a period were retrieved | Open Logging and history to identify the missing part |
| Vertraagd | Synchronization is behind or needs retry | Inspect the source state; a delay alone does not prove missing permission |
| Actie nodig | A source needs intervention | Use the source-specific repair, authorization, account or subscription action shown |
For expired credentials, reconnect the platform in Integrations. For provider permission, check the original platform login's access. For a missing account or limit, fix the account selection or allowance. Use the panel's repair action only for states that offer it. After recovery, check for a successful synchronization and inspect coverage again.
Read or export the archive
Open Activity and choose external platform history. Filter the period, platform, client or account and inspect the available details. Owners/admins can export the archive as CSV.
CSV exports allow at most 10,000 combined change and metadata rows. Narrow the dates or accounts if that limit is exceeded.
A client filter uses the profile's current account links. Moving an account between profiles can therefore change which events appear under a client filter; it does not rewrite the original platform event.
An owner/admin can also ask the assistant:
Read the stored external change history for [client] from [start date]
to [end date], across supported platforms. Include coverage gaps and
available details. Keep these events separate from Ad Superpowers actions.
The change_history_query tool reads the saved archive. It does not fetch new events from a platform while answering. See the client and history tool reference.
Pause, retention and deletion
Use the client's Logging switch and confirm Logging pauzeren to stop collecting for that client. Existing events remain subject to retention. If the same account is also enabled for another active client, that account can continue collecting for the other client.
External events are retained for 365 days from the event time. Pausing, reconnecting or importing an older event does not restart that clock. Removing a client profile or platform connection does not erase the workspace's account archive. Deleting the workspace removes its archive.
For the kinds of data stored in event details and their exclusions, read data and privacy.
