Getting Started

Learn through 101 guides and easy solutions.

Things I Hate Thinking About: Pardot Folder Structure & Naming Conventions

Things I Hate Thinking About: Pardot Folder Structure & Naming Conventions

min. reading

Left to my own devices, I’m the kind of person who saves everything to her Desktop and has at least 5 Word docs titled “Notes Latest V2a” at any given point in time.

I’ve learned the hard way that this is NOT a good plan if you’re managing assets in a Pardot org.  (Kicking this can down the road means lots and lots of technical debt in your future! No bueno.)

It is SO worth it to take the time to build a coherent folder structure and standard file names.  Even if it’s boring and adds a few seconds to your process.  Your future self and team members will thank you for it.

General foldering best practices in Pardot

Pardot folders operate the same basic way they do on the hard drive of your computer.  A definition from Pardot:

Folders are a top-down organizational feature that house campaigns, emails, and other marketing modules together. Folders let you segment and nest marketing elements in a way that makes sense for your team.

Every piece of marketing content created must be placed in a folder.  And there’s a big catchall one called “Uncategorized” that is basically the Pardot equivalent of my messy desktop.

Side note: most people will find this to be fairly self-explanatory and intuitive, but it’s a little bit of a re-frame from what former Marketo users are used to. Marketo is very folder-centric and uses these to create programs and relate assets to each other.  That’s not really what Pardot’s trying to do – their version of folders are mostly just an organizational tool.

Options for Pardot folder structures

Folders are basically a blank canvas for organizing to your heart’s desire.  The only real limits are that you can have max 10,000 items in a folder, and up to 16 levels of subfolders.

But come on – do you really need deeper nesting than:

 Folder A >  Folder B >  Folder C >  Folder D >  Folder E >  Folder F >  Folder G >  Folder H >  Folder I >  Folder J >  Folder K >  Folder L >  Folder M >  Folder N >  Folder O >  Folder P

Common organizational structures I’ve seen include:

Heads Up: folders & scoring categories

A critically important thing to note is that folders are the basis for Scoring Categories.  Quick refresher: Scoring Categories allow you to break down the overall prospects scoring into subcategories – so that you could have separate scores for each of your product lines, or different business units, etc.

If you’re planning on using Scoring Categories at some point down the road, build your folders around the categories you will likely use (like product or business unit).  Worry about the points system later – and this will save you from a massive reshuffle when you’re ready to revisit that.

Naming conventions in Pardot

If you’ve already been using Pardot for a while, a great place to start with this is looking at how your team is naming files on their own.  If it’s good/useful – boom, document it.  If it’s a mess, then work the team to come up with a naming protocol.

Detailed file names are vital for searchability.  You will have some users that navigate to assets using the folder structure every time, and others that will type a few keywords in the search bar to filter down to what they’re looking for.  Standardized naming sets both groups up for success.

Data points you may want to work into your names could be:

  • Name/title
  • Campaign type (i.e. tradeshow, webinar, advertising)
  • Company division / business unit
  • Industry / vertical
  • Date
  • Region
  • Language
  • Audience (i.e. Client, Late Stage Prospects, etc.)

So for example, if you decided you wanted to set your naming convention to be:

Company Division – Name/Title Campaign Type – Audience – Date

This would translate into something like:

Employee Benefits – Complying with the ACA Webinar – Clients – July 2016

General tips & gotchas

Use dividers

Use some kind of dividing character so that your name doesn’t become one big string. I’m partial to – or |. Underscores are also a common divider – but personally I think they are harder to read.

Avoid over-reliance on tags

Tags are NOT a substitute for proper foldering and naming conventions. You have very limited reporting and search capabilities with tags.  They’re useful in a pinch, but I repeat, DO NOT make them the center of your organizational structure.

Consider whether date is really relevant

If you’re creating a template (an email, for example) that is going to be used in multiple initiatives over time, I’d suggest skipping the date as part of your name – it gets confusing.  You’ll always have the system created and last modified dates to refer to.

The briefer, the better

Try to keep names as short as you can, and put the most important/descriptive parts toward the front. Asset names can go up to 255 characters, max. But you’ll only see about the first 42 characters when you’re referencing in automation rules and completion actions, and about 20 characters when referencing in Engagement Studio.

Don’t set it and forget it

You’re not done when you decide on a plan and roll it out. Oh no.

Appoint someone Keep-It-Organized Cop or Organizational Officer, or whatever you want to call it – and check at least monthly to be sure things are being classified correctly to avoid a big pile up to sort out later.

Over to you: what do you think?

How is your process working?  What tactics have you tried in an effort to stay organized?  Any horror stories?

Let us know if the comments!

Subscribe to The Spot

This field is for validation purposes and should be left unchanged.

Salesforce Training Courses


Top 5 Recent Posts

  • Andrea Tarrell is the CEO & Founder of Sercante, as well as a 12X certified Salesforce MVP and Marketing Champion. Andrea caught the Salesforce bug at Dreamforce 2011 and hasn’t looked back since. She’s worked for consultancies, agencies, and client-side marketing teams over her career and is passionate about making marketing and sales teams successful with their tech stacks. Andrea lives in Atlanta with her husband Buck and her daughter, Arla. When she’s not working, she’s most likely playing with her German Shepherd Murphy, starting a new hobby that she will engage in exactly one time, or making homemade gin.

Leave Your Comment

Related Articles

Bot Single Post