Audit Logs

Audit Logs is the Network Admin history of what changed in OffZio, who signed in, and how postback traffic moved in and out of the network. Use it for accountability and for troubleshooting — not as a performance report.

The page subtitle states: Campaign and publisher changes, sign-in history, and postback traffic. Network admin only.

What Audit Logs are for

Network Admins use Audit Logs to:

1. See who created or changed a campaign, targeting, goals, or publisher access.
2. Confirm when a teammate or admin signed in.
3. Check whether OffZio received a conversion postback (inbound).
4. Check the log of postbacks OffZio sends to partners (outbound).

Note: Audit Logs record activity. They do not approve conversions, generate invoices, or replace the Conversion report. Use them to answer “who did this?” and “did the postback arrive?”

Who can open Audit Logs

Only a Network Admin can open Audit Logs. Publishers and advertisers do not see this screen.

Confirm your role on the sidebar profile card if you are unsure. It should show a name and role such as OffZio Admin · Network Admin.

Note: Treat this page as sensitive. It shows teammate sign-ins and operational changes. Do not share screenshots of IPs or click identifiers outside your network staff.

How to open Audit Logs

1. Sign in as a Network Admin.
2. In the left sidebar, click Audit Logs.

The page opens on the Changes tab unless you select another tab.

Which tab to use

1. Changes — Campaign and publisher edits: who changed what, and when.
2. Sign-in log — Who accessed the network and when.
3. Inbound postbacks — Postbacks OffZio received (advertiser or tracker calling the network postback URL).
4. Outbound postbacks — Postbacks OffZio sent onward (for example, to a publisher).

Tip: Missing conversions usually start on Inbound postbacks (did OffZio receive the fire?). Publisher “I did not get a postback” questions usually start on Outbound postbacks.

Search and filters

On Changes and Sign-in log, the toolbar includes:

1. Search — Placeholder: Search message, campaign, publisher.. Use this to find text in the message, campaign, or publisher fields.
2. All campaigns — Limit Changes (and related rows) to one campaign when you are investigating a single offer.
3. All publishers — Limit to one publisher when the change or context is affiliate-specific.
4. All actions — On the Changes tab, narrow to one action type (for example, only status changes).

Note: This article does not document export, delete, or edit controls. Use the tabs, search, and filters you see in the product to find a row. Audit history is for review, not for rewriting the past.

Changes tab

Changes is the activity history for campaign and publisher updates. Each row is one recorded action.

Columns:

1. Time — When the action was recorded.
2. Action — The type of change. Examples include Campaign status changed, Campaign targeting updated, Goal updated, and Campaign created.
3. Details — A more specific description. Some rows include View changes.
4. Campaign — The offer that was affected, when the action is campaign-related.
5. Publisher — The affiliate involved, when the action is publisher-specific. A dash (—) means the row is not tied to one publisher.
6. By — Who performed the action (for example, OffZio Admin or a teammate).

Example detail lines you may see (illustrative only):

1. Campaign published (status active)
2. Campaign targeting rules updated
3. Campaign publisher access updated
4. Campaign tracking settings updated
5. Campaign default goal updated

Click View changes when it appears. That is how you inspect what actually changed, not only the short action label.

Tip: If a campaign suddenly stopped converting, filter Changes to that campaign and look for targeting, tracking, goal, status, or publisher-access updates around the same time.

Sign-in log tab

Sign-in log uses the same general columns as Changes, but each row is a login.

1. Action — Typically User Logged In.
2. Details — Typically logged in.
3. Campaign and Publisher — Usually a dash (—), because a sign-in is not tied to one campaign or affiliate
4. By — The user who signed in (for example, OffZio Admin or a teammate).

Use this tab to see who accessed the network and when. It is useful after a shared computer session, a password concern, or a change you cannot attribute from the Changes tab alone.

Inbound postbacks tab

Inbound postbacks is the log of conversion or postback traffic received by OffZio — the advertiser or tracker calling the network postback URL.

Columns:

1. Time — When OffZio received the postback.
2. Status — For example, success.
3. Click — The click identifier on the incoming request.
4. IP — Source IP of the postback.
5. Response — HTTP code OffZio returned (for example, 201).
6. Error — Error text, or a dash (—) when there is none.

Use this tab when conversions are missing or delayed. First ask: did a postback arrive, and did it succeed? Then open the Conversion Report to see whether that click became an approved (or pending) conversion.

Note: A successful inbound postback means OffZio accepted the fire. It does not by itself mean the conversion is approved, unpaid, or ready to invoice. Check status on the Conversion report.

Outbound postbacks tab

Outbound postbacks is the log of postbacks OffZio sends onward — for example, to a publisher’s tracker.

Use this tab when a publisher says they did not receive a conversion fire, or when you are checking that OffZio attempted to send a postback after a conversion was recorded.

Note: This article does not list outbound columns. Open the Outbound postbacks tab in the product for the fields shown there. Do not assume they match the inbound list.

Common tasks

Find who published a campaign

1. Open Audit Logs.
2. Stay on the Changes tab.
3. Set the campaign filter to that offer, or search for the campaign name.
4. Look for actions such as Campaign status changed or details such as Campaign published (status active).
5. Read By and Time.
6. Click View changes if you need the exact before-and-after.

Check a teammate login

1. Open Audit Logs.
2. Select Sign-in log.
3. Search for the teammate’s name, or scan the By column.
4. Confirm the Time of each User Logged In row.

Verify a conversion postback arrived

1. Open Audit Logs.
2. Select Inbound postbacks.
3. Find the row by Time and Click.
4. Confirm Status (for example, success), Response (for example, 201), and whether Error is empty.
5. If the inbound fire succeeded but the conversion is still missing, open the Conversion Report and search that click or transaction id.
6. If a publisher did not see the event on their side, also check Outbound postbacks.

Best practices

1. Use Changes for “who edited this offer?” and Sign-in log for “who was in the account?”
2. Use View changes whenever the Details text is not specific enough.
3. When conversions are missing, check Inbound postbacks before you assume tracking is broken in the campaign form.
4. When a publisher’s postback is missing, check Outbound postbacks and that publisher’s postback setup — not only the inbound log.
5. A dash in Campaign or Publisher means the event is not scoped to one partner. That is expected on sign-ins.
6. Keep Audit Logs in mind: create and edit actions are recorded for compliance.