Skip to content
Browse documentation

Audit log

Find out who changed what and when in a workspace — offers, partners, conversions, billing, users, keys and settings — and export the trail.

Last updated 3 min read

On this page

Every change made in a workspace — by a person, an API key or an automation — is written to the audit log with the time, the actor, the action, the affected object and the details of the change. Passwords, tokens and other secrets are never recorded.

Open the audit log#

Settings → Audit log (/app/settings/audit-log). Admins and owners only.

  1. Pick the date range in the top bar (default: last 30 days; your time zone).
  2. Filter by User, Action and Entity, or search ("Search action, entity or exact ID…").
  3. Page through with 50, 100 or 200 rows per page.

Columns#

ColumnContent
TimeWhen it happened.
ActorThe user (name and e-mail); for API calls the API key used is shown under the name.
ActionA dotted name such as offer.update, conversion.status, invoice.paid.
EntityThe type of object: offer, affiliate, conversion, invoice, …
Entity IDIts ID — searchable exactly.
DetailsThe change as JSON: before/after values, reasons, counts.
IP (hashed)Hidden by default: a keyed hash of the actor's IP address, for correlating actions without storing the address.

Export CSV downloads the rows on screen with the full JSON details.

What is recorded#

The log covers more than 270 distinct actions. The most common groups:

AreaExample actions
Offersoffer.create, offer.update, offer.status, caps, payout rules, overrides, landing pages, creatives, terms
Partnersaffiliate.approve, affiliate.reject, affiliate.block, affiliate.payment_details, affiliate.tax_form_review, affiliate.impersonate, affiliate.impersonate_end
Offer accessapprovals, rejections, blocks and access-row changes
Advertiserscreate/update, advertiser.network (parent account), advertiser.partner_signup, postback token rotation
Conversionsconversion.status (with reason and IDs), conversion.adjust (old → new amounts), conversion.advertiser_reject, conversions.export
Billinginvoice.sent, invoice.paid, invoice.void, invoice.reopen, payout.approved, payout.paid, payout.provider_send, tax.1099_export, referral.commission_added
Reports & automationreport adjustments, custom metrics, scheduled reports, KPI alerts, scheduled changes, optimisation rules and exclusions
Settingsworkspace settings (workspace.signup_settings, workspace.terms_publish, workspace.referral_settings…), postback tokens, tracking domains (domain.advertiser_cname…)
Users & accessuser invites, role changes, removals, API keys, webhooks
Documents & termsuploads, document.sign, visibility changes

Automations write under a person's name where one is responsible: optimisation rules and scheduled changes record the user who created the rule or change.

Typical investigations#

QuestionHow
Who paused this offer?Filter Entity = offer, search the offer's ID.
Why was a conversion rejected?Search the conversion ID; conversion.status shows the reason and who set it. Also see the conversion's Change history.
Did someone change a partner's payment details?Filter Action = affiliate.payment_details.
Who viewed a partner's portal?Filter Action = affiliate.impersonate.
Who downloaded tax data?Filter Action = tax.1099_export.

Where else history is shown#

  • Offer → Notes: the offer's change timeline from the audit log.
  • Conversions → Change history and the transaction journey: status history of a conversion.
  • Partners → Partner program → Terms → Acceptance log: terms acceptances (a separate log).
  • Admin → Sign-ins: sign-in attempts (a separate log, see Login security).

Platform-level actions#

Actions that belong to no workspace — brands, single sign-on, sign-up CAPTCHA, privacy requests, platform security policy — are recorded without a workspace and do not appear on a workspace's audit log page.

Retention#

Audit entries are not deleted automatically. They are kept for the life of the workspace; see Data retention.

Related#

Something unclear or missing in this article?Tell us