Compliance evidence
"Show me every email you sent me and everything you did with my data." With Timeline, the answer is one page — every send, open, click, and edit on the contact's record, in order. Not a week of log archaeology across systems.
Timeline · Campaigns addon
One chronological activity feed per contact — every campaign delivered, every open and click, every bounce and unsubscribe, every field edit with before-and-after values. Time-stamped, ordered, and one scroll deep. Stop reconstructing what happened. Scroll to it.
What lands in the timeline
Mumara Campaigns captures twelve event types across four families and assembles them into one unbroken, chronological record per contact. No tracking scripts to wire up — install the addon, switch on Timeline Events, and the story starts writing itself.
Every field edit with before and after values — status, email, country, any custom field. Contact adds, merges between lists, and splits. Watch the shape of a record evolve over time.
Every broadcast, trigger email, and drip that reached this contact — with the campaign name and timestamp, linked straight to its statistics. The complete answer to "what did we send them?"
Opens with the subject line that earned them. Clicks with the exact link that was clicked. Unsubscribes with the campaign that caused them. The signals that show what this contact actually cares about.
Bounce events and feedback-loop spam complaints, each tied to the broadcast and campaign that triggered them. The reputation-critical events you can't afford to lose track of.
Anatomy of an event
Every row in the timeline arrives with its full context. Field updates show the old and new value side by side — status, email, country, any custom field. Sends name the campaign and link straight to its statistics. Opens carry the subject line; clicks carry the exact link clicked. Bounces and complaints point back at the broadcast that caused them. It's not a log — it's a story you can follow.
Edit events list each modified field with its From and To value. "What was their plan tier before they churned?" takes five seconds, not a data pull.
Events link to the contact list, the broadcast, and the campaign statistics they came from. The trail is navigable, not just readable.
On any contact list, click a contact and a slide-in panel shows their subscription status, custom fields, and full timeline — without leaving the page.
Record events in real time or push them through the queue — one setting in General Settings, tuned to your sending volume.
One timeline, three jobs
The same chronological record answers three very different questions — which is why teams that install Timeline for one job end up leaning on it for all three.
"Show me every email you sent me and everything you did with my data." With Timeline, the answer is one page — every send, open, click, and edit on the contact's record, in order. Not a week of log archaeology across systems.
"I never got the email." Open their timeline: was it sent, did it bounce, did they unsubscribe, did a field change tell a different story? One page answers before the ticket escalates.
Read your best subscribers' timelines and patterns jump out that no dashboard shows — the drip where engagement dies, the field change that precedes a purchase. Qualitative gold.
Why aggregates aren't enough
Aggregate reporting tells you what happened to everyone. The moment the question names one person — one contact, one complaint, one regulator — aggregates go silent. Timeline is built for the specific question.
Your dashboard says unsubscribes ticked up yesterday. Anna's timeline says she unsubscribed at 14:23, right after Welcome Series #3 landed. Now you know which campaign lost her — and can fix it.
The segment needs plan_tier = Pro. The timeline shows the field flipped from Pro to Trial three days ago — right there in the edit history. No aggregate view will ever expose that.
A subject access request means accounting for every event on one person's record. Without a per-contact timeline, that's days of hand-querying logs across systems. With it, the whole record is on one page.
Every deliverability mystery means opening three tools to investigate one contact. Timeline collapses it to one page — and the saved minutes compound across thousands of tickets.
“The Timeline addon paid for itself the first week. We went from 30-minute deliverability investigations to 30-second timeline checks. Compliance reviews that used to take a week now take an hour.”
Verified review
Mumara customer
Common questions
Twelve event types across four families. Profile & list changes — contact added, field edits with before/after values, merges between lists, splits. Send events — broadcasts, trigger emails, and drips. Engagement — opens (with the subject line), clicks (with the exact link clicked), unsubscribes. Bounces & complaints — bounce events and feedback-loop spam complaints. All captured automatically and assembled chronologically.
Timeline starts recording the moment the addon is installed and Timeline Events are switched on in settings. From then on, every event stays with the contact — there's no rolling window that silently drops old history. Activity from before the addon was installed isn't back-filled.
Two places. Every contact has a dedicated Timeline page with their full chronological history, and every contact list gets a slide-in panel — click a contact to see their subscription status, custom fields, and timeline without leaving the list.
Yes. Drip sends show the drip name and its drip group. Trigger emails appear as send events linked to their campaign. And engagement on any of them — opens, clicks, unsubscribes — lands on the timeline just like broadcast engagement.
No. Events are captured through Mumara's hook system, off the sending path — and you choose the processing mode in General Settings: real-time or queued background processing. Send throughput is unchanged either way.
Reporting & Analytics answers "how did this campaign perform across all contacts." Timeline answers "what happened to THIS contact across all campaigns." One is per-campaign aggregated by metric; the other is per-contact ordered by time. Different axis, different question, complementary value.
No. Unsubscribe processing is core Mumara Campaigns — unsubscribed contacts are flagged automatically and excluded from future sends. Timeline adds the when and the where: the exact moment a contact unsubscribed and the campaign that triggered it.
Yes. On Self-Hosted you install the addon from the Addons page in a couple of clicks; on Mumara Machine plans it's included with the standard addon bundle. The feature behaves identically in both deployment modes.
Related
The data model the Timeline observes — lists, contacts, profile fields. Every change lands on the timeline.
Read moreCore suppression and unsubscribe handling. Timeline shows the unsubscribe, bounce, and complaint events behind a contact's status.
Read moreAggregate-level reporting. Timeline is the per-contact complement — same events, different axis.
Read moreTrigger emails sent to a contact show up on their timeline — with the campaign they belong to and the timestamp.
Read moreMumara Campaigns · Timeline addon
Timeline is included with every Mumara Machine plan and available as an addon for Self-Hosted Campaigns. Try it on a real account — the free trial includes all addons.