Build Guide

In this article, you’ll learn how to:

• Launch an in-app feature announcement
• Track views and usage of the new feature
• Create a Workflow from scratch
• Add branching logic based on behavior
• Send targeted follow-up messages
• Track adoption with a goal
• Configure finish criteria and re-enrollment

Step 1. Launch your in-app announcement

Create a Flow or Tooltip that announces your new feature in the product. Keep it simple—focus on the “why it matters” and give users a clear next step (like trying it out right away).

Make sure to create a button on your in-app announcement that tracks an event when the announcement is viewed (e.g., feature_announcement_viewed), so you can trigger follow-ups based on that interaction.

Step 2. Track feature usage

You’ll also want to track whether a user interacts with the new feature. This could be:

• Clicking a CTA in the announcement
• Opening or using the new feature itself
• Completing a related action (e.g., creating a report, submitting a new form)

Name this event something like feature_used, and make sure it's ready to be used in a Workflow condition.

Step 3. Create a new Workflow

Head to the Workflows tab in Appcues and click Create Workflow.

Give it a name like “Feature Follow-Up” or something specific to your release.

Step 4. Set start criteria

Click the Start node and configure:

• Audience: Anyone eligible to see the announcement
• Trigger: The feature_announcement_viewed event
• Trigger timing: Immediately, so follow-ups can happen shortly after the announcement

Step 5. Add a time delay

Add a Time delay node to give users time to explore the feature before you follow up.

• Suggested delay: 2–3 days

Step 6. Add branching logic

Next, add a Condition node to check if the user has tried the feature.

• If they have: No follow-up needed—or optionally, send a message highlighting the next thing to try
• If they haven’t: Send a reminder with a real-life benefit, quick how-to, or short video showing how it works

💡 Email or push works great here—especially for users who might not be in your product every day.

Step 7. Set a goal

Add a Goal to track if the user tries the feature after receiving the follow-up message. Use the feature_used event from Step 2.

This helps you see how effective the follow-up was at driving actual adoption.

Step 8. Set finish criteria

Click the Finish node to set how users exit the Workflow.

• Exit when: They reach the end of the workflow
• Timeout threshold: Try 7–10 days
• Re-enrollment: Optional—turn this on if users might re-enter based on future feature flags or releases

Step 9. Publish Workflow

Once your logic, messages, and goal are set up, hit Publish to go live.

👏 And that’s it! You’re now turning a one-time announcement into actual product adoption—with a little help from Workflows.