Dynamic Content

Dynamic content allows your backend to return tailored responses depending on the user, request parameters, or external data. With Cortado, it’s easy to build APIs that respond differently to different users—whether you're customizing landing pages, fetching user-specific assets, or building gated experiences. In this guide, you'll learn how to structure your routes for dynamic output, fetch conditional data, and manage localization, personalization, or AB testing logic—all with a clean, scalable backend.

Advanced

21 min

Mark as Completed

Step 1: Identify Dynamic Use Cases

Dynamic content can be used in many contexts. Some common examples include:

User-Specific Dashboards — Show each user their own stats or files
Localized Content — Return text or assets based on language or region
AB Testing — Serve different versions of content for experimentation
Asset Personalization — Display different images depending on user status
Smart Offers — Tailor product offers based on behavior or purchase history

Clarifying these use cases helps you build endpoints that serve meaningful and relevant content.

Step 2: Build Flexible Routes

To support dynamic logic inside routes, consider this structure:

Use URL params and query strings to pass context (/user/:id?lang=fr)
Read authentication tokens to identify the current user
Fetch external data (e.g. CMS, database, or payment platform) before forming a response
Implement fallback logic if no personalized content is found
Avoid hardcoding responses—structure them as templates with variables

These design principles ensure your APIs are reusable, clean, and easily testable.

Step 3: Common Dynamic Patterns Table

With Cortado, these dynamic patterns can be chained with middleware or custom logic, giving you full control over how content is generated and delivered in real time.

Making Output Context-Aware

Once you've built routes that can detect user data, language, or behavior, use that information to adjust the response dynamically. This might mean switching between languages, showing different content based on subscription level, or tailoring responses to location or device type. The output format should remain predictable (e.g. same JSON shape), but the data inside changes based on context. This approach improves UX and performance while still keeping your backend maintainable. Always test with multiple user types and devices to ensure fallbacks work and personalization logic is sound.

Was this helpful?

Last updated on