Skip to main content

How to Use the Activity Log in Alta (Campaigns, Dashboards, Views, and LinkedIn Reps)

Track who changed what in Alta — campaign edits, dashboard updates, data-model view changes, and LinkedIn rep events — with filters and a per-change diff.

Written by Katie Supporté

The Activity Log is how you see exactly who changed what in Alta, when, and what the value was before and after. It runs across four surfaces — campaigns, dashboards, data-model views, and LinkedIn reps — so when a metric shifts, a campaign pauses, or a widget moves, you can find the edit and the editor in seconds.

Summary

Open the Activity Log on any campaign, dashboard, view, or rep to see a timeline of edits, filter by user or entity type, and click into a change to see the old value, the new value, and which fields moved.

Who this is for: Admins, managers, and power users who need an audit trail — for governance, debugging a campaign that suddenly behaves differently, or understanding why a dashboard widget moved.


How to open the Activity Log

Campaign activity

  1. Open a campaign from Campaigns.

  2. Go to the Activity tab on the campaign (URL ends in /activity).

  3. You'll land on a page titled Campaign activity with a compact timeline of edits grouped by day, then by actor.

Dashboard activity

  1. Open any dashboard in Track.

  2. From the dashboard toolbar, open the Activity Log panel.

  3. The slide-over titled Activity Log opens on the right, showing dashboard, dashboard-view, and widget changes.

View activity (data model)

  1. Open a view in the data model.

  2. Open the Activity Log from the view's side panel.

  3. You'll see view-level and field-level changes (create, update, delete) with a before/after diff.

LinkedIn rep activity

  1. Go to Settings → Integrations and open a LinkedIn rep.

  2. Open the Rep activity panel.

  3. You'll see connections, disconnections, updates, rate-limit starts and clears, and system reconnects.


What's tracked

The Activity Log records the events you'd expect to need for an audit or a debug session. The exact event labels you'll see come straight from the product:

Campaigns

  • Created the campaign

  • Updated the campaign (with a per-field change preview)

  • Launched / paused / resumed the campaign

  • Archived the campaign

  • Deleted the campaign

Dashboards

  • Created Dashboard / Updated Dashboard / Deleted Dashboard

  • Created Dashboard View / Updated Dashboard View / Deleted Dashboard View

  • Created Widget / Updated Widget / Widget Moved / Deleted Widget

Data model views

  • Created View / Updated View

  • Created Field / Updated Field / Deleted Field

LinkedIn reps

  • Connected LinkedIn account

  • Updated LinkedIn account

  • Disconnected LinkedIn account (manual)

  • LinkedIn account disconnected (system-detected)

  • LinkedIn account reconnected (system-detected)

  • LinkedIn account rate limited / rate limit cleared


Filtering the timeline

  1. Click the Filters button at the top right of any Activity Log surface.

  2. Pick a category from the left menu — the categories you'll see depend on the surface:

    • CampaignUsers

    • DashboardEntity Types (Dashboard / Dashboard View / Widget), Users, Widgets

    • ViewEntity Types (View / Field), Users, Fields

  3. Select one or more options. The chip next to the category label shows how many filters are active.

  4. Use Clear all in the popover to reset everything for the current category.

  5. Click the refresh icon next to Filters to refetch the latest events.

If your filters return nothing, you'll see "No results found — Try searching again." If there's truly no recorded activity for the entity yet, the empty state reads "No activity log."


Reading a change

Click any event in the timeline to expand it. For an Updated event you'll see a "N changes" accordion that opens to a per-field summary like:

  • name changed from "Outbound Q1" to "Outbound Q1 — Tier 1"

  • status set to active

  • excludedDomains removed ["acme.com"]

If there are more than six changes, the summary shows the first six and ends with "+ N more changes". Nested objects are inspected up to two levels deep; very long string values are truncated with an ellipsis.

If your workspace has the JSON diff option enabled, you'll also see a View JSON / View Summary toggle in the top-right of the change preview — handy when you need the exact raw payload for a support ticket.


Tips and common pitfalls

  • System-attributed events show "Alta" as the actor. Anything Alta did automatically — like detecting that a LinkedIn account got disconnected or hit a rate limit — appears with the Alta avatar instead of a user.

  • Each surface only shows its own scope. The campaign Activity tab does not show dashboard widget edits, and the dashboard Activity Log does not show campaign launches. Open the matching surface to find a missing event.

  • The dashboard log includes its widgets, but you can narrow further. Use the Widgets filter on the dashboard Activity Log to focus on a single widget — useful when one chart is the one that changed.

  • The view log includes its fields, with a similar narrowing filter. Use the Fields filter on the view Activity Log to isolate edits to one column.

  • Refresh after a recent edit. The log doesn't live-poll. If a teammate just made a change, hit the refresh icon next to Filters to pull the latest batch.

  • Identical values aren't logged. If a field was "saved" but the value did not actually change, no entry is created for it — the diff engine compares old vs. new and skips no-op writes (this also skips id, createdAt, and updatedAt).

  • Use Users + Entity Types together. The fastest way to find a specific edit on a dashboard is filter by the teammate and by Widget at the same time — both filters apply.


Related

  • How to Build, Manage, and Reuse Audience Lists in Alta

  • How to Build and Manage Flows in Alta (Workflows: Drafts, Publish, Runs)

  • How to Create and Track Goals & KPIs in Alta

]]>

Did this answer your question?