Audit Trail (Vote on this Idea, not it's dupes) | Community
Skip to main content
February 4, 2011
Delivered

Audit Trail (Vote on this Idea, not it's dupes)

  • February 4, 2011
  • 52 replies
  • 28184 views

I think it would be good to have time stamp or properties info for each element on Marketo.

For example, for each Smart List or List under Lead Database, it should have info about who created the list, when created, last updated, last updated by etc.

This will give very good transparency for multiple users.

This will definitely help!

Sarat

52 replies

September 28, 2015
  • Time stamps/Audit Trail: Created by, Last Modified by, Modified date/time, etc.  For ALL assets and programs: Smart Campaigns, Lists, LPs, templates, (Design Studio, etc.)
  • Change log: Snapshot for each days' worth of data and add to the data warehouse that that we could access.  If something was deleted, the Admins need to know what, by whom and when.
  • Restoring to a previous state after an accidental change
Prinu_George
Level 3
October 29, 2015
  • Some of our VVIP leads were not receiving emails and when i looked into their activity log, they were manually unsubscribed. As an helpless admin, i was't able to provide who did that edit (nor a marketo engineer)
  • When bad data creeped into the database via wrongly set up form and the audit from marketo n/w engineer proved someone edited the form later, this feature will help me use time productively instead of wasting a lot trying to find a root cause.

    I hope this idea gets implemented soon.
November 4, 2015

Hi Everyone!

I'm a UX Designer at Marketo and I'm working on a couple designs for the Audit Trail project! I'd love your feedback and input on some of these designs. Please let me know if you're interested and we can set up some time to chat.

Thanks!

Sindhu

November 4, 2015

Hello Sindhu,

I am so excited about this badly needed feature. I would love to chat with you about it. If you will send me a meeting request, I’m available all of next week.

Catherine

Grégoire_Miche2
Level 10
January 25, 2016

Amongst other, import audit trail is needed.

-Greg

January 25, 2016

Hi Gregoire,

To clarify, do you want to know when an import happens and who did it? If that's the case, we will be including that in the audit trail!

Grégoire_Miche2
Level 10
January 25, 2016

Hi Christina Fuentealba,

Yes, this is exactly this. Thx for letting us know. Any ETA ?

Your feedback (and that of your colleagues) on all the other points in this post Just do it! Marketo so-called minor missing features  would be welcome.

-Greg

March 9, 2016

Hello,

Good news! We've made significant progress on Audit Trail and it will be done this year, tentatively planned for our Q3 2016 release. Here's the break down:

  • All customers will get it for free! We will add a new permission in admin so you can decide which roles will have access to it.
  • Audit trail will be split into three components:
    • Asset Audit Trail - will track the create, edit and delete actions that users do on all assets, programs, campaigns and lists inside of Design Studio and Marketing Activities. We'll include date/timestamp, username, action and what they did.
    • Admin Settings Audit Trail - will track the actions done inside of the admin section of Marketo. Think of this as auditing admins. We'll include date/timestamp, username, action and what they did. For example, who created/deleted a user, who changed the login password requirements etc.
    • User Login History - will be exactly what it sounds like, a login history of each user in a subscription. This will include details such as date/timestamp, username, IP address, failed login attempt and more.
  • Each of the above will be presented in a nice UI (thanks Sindhu Amugothu​) that will expose data for the last 30 days at a time. Why 30 days? There is a LOT of data! We want to give you access to a subset of information in the UI so you can easily scan for and search for specific pieces of data in a quick manner.
  • If you need anything beyond 30 days, you can get it via a csv export up to a max of 180 days.

Audit trail will not include versioning and rollback...sorry, I know some of you want this. The goal for this project is to expose the activities happening within your subscription including who did what and when. Ideally, this information can help you determine what changed so you can either change it back or go directly to the person who made the change.

I invite you to post comments to this thread or to me directly. Thanks everyone for your patience, I'm excited to be leading this project and getting it off the ground. I'll continue to provide updates as we make further progress.

~ Christina

Grégoire_Miche2
Level 10
March 9, 2016

Hi Christina Fuentealba,

This is great news indeed. Thx a lot for keeping us posted.

Let me know if you are looking for Beta testers.

-Greg

Marcia_Kerber
Level 3
June 7, 2016

Oh my gosh - I can't wait for this!   Yay!!

Marcia Kerber
July 27, 2016

Looking forward to it

September 6, 2016

Just wanted to provide a quick update. Audit trail will be live in our Q3 release. I think everyone will be very happy with it. We will be publishing to our docs site a complete list of what is being audited and what is not. There are some items which we'll add to audit trail in our Q4 release (those details will be provided later.) There will not be a beta so once the release is out, everyone will get it. I'll update more as I get closer to the date. Thanks!

Edward_Masson
Level 10
September 6, 2016

Can't wait!!!

September 12, 2016

I'm so excited about this. Just had a flow deleted from a master template and have no idea who did this or when (other than within the last 7 days)

September 26, 2016

Hi everyone!

Please have a look at a blog post I wrote about Audit Trail for additional details as well as the product documentation (links below). The biggest thing I want everyone to understand is that Audit Trail is an evolving feature! This is the starting point and we're auditing a LOT of great info and will continue to add auditing capabilities across more areas of the product. Also important to note, is that because this is a new capability, the auditing of data/activity began on Sept 14, 2016. This means that you will only be able to view history from that point forward. Please let me know if you have any questions and thanks for all of your contributions.

Docs to review:

Thanks,

Christina

September 26, 2016

Already using this feature Thank you!