Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • Belen 4:58 pm on November 19, 2025 Permalink  

    Start users exactly where they need to be 

    Suppose you’ve built a comprehensive training program with GuidedTrack. Some people need to start with the basics. Others already know the fundamentals and want to jump straight to advanced topics.

    Most platforms would drop everyone at  the same starting point, forcing advanced users to click through beginner content they don’t need. If you wanted to avoid this, you’d have to build entirely separate programs for different skill levels.

    GuidedTrack has a simpler solution: custom links that start people at different points in the same program.

    How It Works: Labels + URL Parameters

    Add a *label anywhere in your program, then share a link with that label at the end. Users clicking that link will start at that exact spot instead of the beginning.

    Here’s the format:

    https://www.guidedtrack.com/programs/programID/run#your_label_name

    Real Example: Sourdough Bread Baking Program

    Let’s say you’re teaching sourdough bread baking – that centuries-old craft that somehow became the internet’s favorite quarantine hobby and never really went away.

    You’ve built a comprehensive baking program that covers everything from creating your first starter to mastering artisan techniques. Your program looks something like this:

    Welcome to Sourdough Mastery!
    
    Let's start with the fundamentals...
    
    *label: starter_basics
    Creating and maintaining your starter…
    (the rest of your content would go here)
    
    *label: first_loaf  
    Baking your very first sourdough loaf…
    (the rest of your content would go here)
    
    *label: troubleshooting
    Why is my bread dense? Common problems solved…
    (the rest of your content would go here)
    
    *label: advanced_techniques
    Now let's get into the artisan stuff!
    (the rest of your content would go here)
    
    Professional scoring patterns...
    Multi-day cold fermentation...
    Advanced shaping techniques...
    Experimenting with ancient grains...

    The Problem You Need to Solve

    You know that some of your users already have a thriving starter bubbling away on their counter. They’ve baked dozens of loaves. They don’t need lessons on “what is a starter” or “your first basic loaf.” Making them click through all the beginner content is frustrating and wastes their time.

    But you also don’t want to maintain two separate programs – one for beginners and one for experienced bakers. Every time you update a recipe or technique, you’d have to update it in both places.

    The Solution: Different Links for Different Users

    You add the *label: advanced_techniques right before your artisan content begins.

    Now you can share two different links:

    For beginners (standard link), they start at the very beginning and learn everything from scratch:

    https://www.guidedtrack.com/programs/sourdough101/run

    For experienced bakers (link with label), they skip all the basics and land directly at the advanced techniques section:

    https://www.guidedtrack.com/programs/sourdough101/run#advanced_techniques

    What This Looks Like in Practice

    You’re running an online baking workshop. When people register, they indicate their experience level:

    • Never baked bread before: Send them the standard link. They need to create a starter, understand fermentation basics, and bake their first simple loaf.
    • Been baking for a year: Send them the #advanced_techniques link. They already know how to maintain a starter and bake a basic loaf. They want to learn professional scoring and cold fermentation.
    • Just struggling with dense loaves: Send them the #troubleshooting link. They can focus on solving that specific problem.

    One program. Multiple entry points. Everyone gets exactly what they need.

    The Marketing Benefit

    This also works great for targeted campaigns:

    • Facebook ad to cooking beginners: “Start your sourdough journey” → standard link
    • Email to past workshop attendees: “Master artisan techniques” → #advanced_techniques link
    • Partnership with baking supply stores: “Take your loaves to the next level” → #advanced_techniques link

    Each audience sees messaging that speaks to them and lands in the right place.

    Why This Matters

    • Better user experience: Advanced users don’t waste time on content they already know. Everyone starts where they should.
    • One program to maintain: Update your content once, and all entry points automatically stay current. No syncing multiple versions.
    • Flexible marketing: Send different links to different audience segments. Same program, customized entry points.

    Important Note: Labels Must Be in Your Main Program

    This only works for labels in your starting program. If you’ve linked to other programs using *program, labels inside those linked programs won’t work with this URL trick.

    The label needs to be in the main program that people are entering.

    How to Use This Feature

    1. Add *label: descriptive_name where you want an entry point
    2. Share programID/run#descriptive_name with that audience

    That’s it: They land exactly at that label.

    Bonus tip: Use clear, descriptive label names. #advanced_techniques is much better than #section4 when you’re managing multiple entry points.

    When to Use This

    This feature works great for:

    • Training programs with beginner and advanced paths
    • Educational courses where some users have prerequisites
    • Product demos tailored to different user roles
    • Research studies with different experimental conditions
    • Any program where different audiences need different starting points
     
  • Belen 8:12 am on November 4, 2025 Permalink  

    Schedule things for “next Friday” automatically 

    Imagine you’ve got a new user who just signed up on a Tuesday. You want to check in with them on Friday to see how their first week went.

    In most systems, there would be no way to do this, or, if there were, you’d have to calculate: “Today is the 15th, so Friday would be the 18th, which is 3 days from now…”

    And if they sign up on Saturday? Now you need different logic. What if it’s already Friday afternoon?

    There’s a simpler way: just tell GuidedTrack “schedule this for Friday” and let it figure out the dates.

    Schedule based on weekdays, not dates

    GuidedTrack lets you create dates based on specific weekdays:

    >> fridayThisWeek = calendar::date({"weekday" -> "Friday"})

    This finds the Friday of the current week. Simple enough. You can now use this like any other date, like for example feeding it into an email’s *when keyword to schedule an email to be delivered on Friday.

    When to use weekday-based scheduling

    This approach works great for:

    • Onboarding sequences where you want check-ins on specific days of the week
    • Weekly programs that should always start on Mondays (or any day)
    • Habit trackers that align with people’s weekly routines
    • Study schedules with sessions on specific weekdays
    • Team coordination where everyone gets reminders on the same days

    The catch: “Friday this week” might be in the past

    If someone signs up on Saturday, “Friday this week” already happened. You need to make sure you’re scheduling for an upcoming Friday:

    >> fridayThisWeek = calendar::date({"weekday" -> "Friday"})
    
    *if: fridayThisWeek < calendar::date
    	>> upcomingFriday = fridayThisWeek + 7.days
    *if: fridayThisWeek >= calendar::date
    	>> upcomingFriday = fridayThisWeek

    Now upcomingFriday is always a date in the future, no matter what day someone signs up.

    One important quirk: weeks start on Sunday

    Computer weeks start on Sunday, not Monday. This means:

    • “Sunday this week” is either today (if it’s Sunday) or already passed
    • If you want “the upcoming Sunday,” you almost always need to add 7 days when running the check on Sunday itself

    This is just how date systems work. It’s a bit quirky, but once you know it, you can plan around it.

    Getting started

    Here is the basic pattern:

    >> targetDay = calendar::date({"weekday" -> "DayName"})
    
    *if: targetDay < calendar::date
    	>> upcomingDate = targetDay + 7.days
    *if: targetDay >= calendar::date
    	>> upcomingDate = targetDay
    

    Replace "DayName" with Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, or Sunday.

    The code is simpler. The logic is clearer. And it just works.

     
  • Belen 9:11 am on September 26, 2025 Permalink  

    Guide users through text input like a pro 

    You’ve seen it happen: someone stares at an empty text box for 10 seconds, types something, deletes it, then types something completely different.

    “What format do they want?” “How detailed should this be?” “What’s a good example?”

    Empty text boxes can be intimidating. But with the right guidance, people fill them out confidently and give you exactly what you were asking for.

    GuidedTrack’s *placeholder and *tip features solve this by putting helpful instructions exactly where users need them – right at the point of input.

    Two Ways to Help Users

    *placeholder – Gentle Hints Inside the Box

    Placeholder text appears inside the text box and disappears as soon as the user starts typing. Perfect for showing format examples or quick hints:

    The user sees the example format right in the text box, but it vanishes the moment they start typing their actual number.

    *question: What's your phone number?
    	*placeholder: e.g., +1234567890
    	*save: phone_number
    

    Use *placeholder for:

    • Format examples (phone numbers, dates, email addresses)
    • Quick hints that don’t need to be remembered
    • Simple guidance that fits in one line

    *tip – Persistent Instructions Above the Box

    The *tip keyword displays helpful information below the question but above the input area, and it stays visible while users type:

    *question: What was your most recent strange dream like?
    	*tip: For instance, you might say "I dreamt I turned into a toaster."
    	*save: dream_description

    The tip stays put, so users can reference it while they’re writing their response.

    Use *tip for:

    • Complex instructions that are hard to memorize
    • Examples that users might want to reference while typing
    • Longer guidance/explanations

    Why This Improves Your Data Quality

    📐 More consistent formats: Placeholder examples show exactly how you want information formatted.

    💡 Richer detail: Tips that explain why you’re asking encourage more thoughtful responses.

    🔄 Less back-and-forth: Clear guidance upfront prevents the need to follow up for clarification.

    Getting Started

    Both features work with any *question that accepts text input:

    *question: Your question here
    	*placeholder: Format hint that disappears when typing starts
    	*tip: Persistent guidance that stays visible while typing
    	*save: variable_name

    Small Details, Big Impact

    These aren’t flashy features, but they make a real difference in how people experience your forms.

    The person filling out your survey shouldn’t have to guess what you want. A simple placeholder or tip can turn confusion into confidence, blank responses into useful data.

    Your users will appreciate the guidance, and you’ll appreciate the better responses.

     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel