If you’re building snapshots in HighLevel and you’re still not sure when to use Custom Values vs. Custom Fields, it’s only a matter of time before something breaks. 💥
And when it breaks, it’s not going to be fun.
I’ve seen too many smart agencies make the same mistake: they clone a beautifully built snapshot and then realize they hardcoded client-specific info all over the place. 😩
But don’t worry! I’m going to break this down in a way that actually makes sense, so your snapshots are clean, scalable, and (most importantly) don’t explode when you hand them off to a client.
What Even Is a Snapshot?
Snapshots are like cheat codes in HighLevel. They let you bundle up an entire client system workflows, forms, calendars, funnels, the whole kitchen sink—and reuse it for the next client.
Build it once. Reuse it forever. That’s how you get leverage. 💪
But if you hardcode stuff like business hours, URLs, phone numbers, or pricing directly into your emails and automations, guess what?
You’ll be stuck doing a “find & replace” nightmare every single time you onboard a new client.
So how do we avoid that? Enter: Custom Values and Custom Fields.
Custom Values vs. Custom Fields (Explained Like You’re Five)
Let’s keep it super simple:
🟨 Custom Values = Global info
Stuff that applies to the whole account—like business hours, legal disclaimers, or the company’s phone number.
🟦 Custom Fields = Personal info
Stuff tied to a specific contact—like their first name, quote amount, or birthday.
If you’re repeating the same info across multiple assets, like in emails, funnels, and texts, and that info could change in the future, use a Custom Value.
That way, when something changes, you update it once—and it updates everywhere.
Real-Life Example Because Theory Is Boring
Let’s say you’re setting up a system for a mortgage company. Here’s how I’d handle it:
✅ Use Custom Values for:
- Interest rates 📉
- Hours of operation 🕘
- Office address or contact info ☎️
- Legal disclaimers 📃
That way, when rates change (which they always do), you update the value once, and boom! Your emails, SMS, forms, and web pages all reflect the new rate automatically.
✅ Use Custom Fields for:
- The customer’s name
- Their credit score
- Their property value
- Loan amount
Because these things are specific to the person you’re talking to.
Quick Cheat Sheet: Ask Yourself These 2 Questions
Before adding any new variable, I ask:
- Is this info unique to each contact?
Use a Custom Field - Is this info shared across the whole account, but might change later?
Use a Custom Value
If it’s both? Consider if it needs to be duplicated or systematized differently. Sometimes you just need a smarter structure.
Bonus Tip: Document Everything
Seriously. Keep a shared doc or Airtable where you track all your custom values what they are, where they’re used, and any notes.
Nothing’s worse than opening up a snapshot and seeing stuff like {{custom_value_42}} and having no clue what it controls. 🙈
Final Thoughts
If you want to build scalable, clean, and reusable systems in HighLevel, getting this one distinction right will save you hours of work (and a few gray hairs).
Don’t wing it. Don’t overcomplicate it.
🛑 Custom Fields = Contact data
✅ Custom Values = Business data
Get this locked in, and your snapshots will feel like magic.
Want More Pro Tips Like This?
I share tools, templates, and frameworks that help you build smarter systems and grow your agency faster.
Head over to gohighlevele.com and see what’s new, we’re dropping helpful stuff every week.
Cool Free Thing
Before you can help businesses with your service, you need to establish trust.
The fastest way to do that? ⭐️ Testimonials.
So in the spirit of free stuff, I want to give you our Testimonial Workflow.
It’s a plug-and-play system that makes collecting, editing, and organizing testimonials super easy.
✅ No awkward follow-ups
✅ No more “uhh can you write us a review?”
✅ Just a smooth, repeatable process
👉 Grab it here and start building trust on autopilot.