Once your first campaign is live, a few habits keep Appcues reliable as more people build in it: clear roles, consistent names, clean data, and regular content reviews. Come back to this page whenever your team or your experience library grows.

Manage your team

Open Settings > Team to invite teammates and manage their roles.

Roles decide what each person can do. Editors create campaigns and experiences, publishers and admins can publish them, and only admins can change account settings such as Settings > Appcues AI. Limit publishing to people who understand your targeting and naming conventions.

See Manage your team in Appcues.

Agree on naming conventions

Names are how your team finds things later, and how Appcues AI tells similar items apart when you @-mention them. Agree on a pattern before your library grows:

• Campaigns and tactics: name them after the outcome and the approach, such as "Trial activation" and "Trial activation: day-3 reminder."
• Experiences: include the use case, the type, and the audience, such as "[Onboarding] Welcome modal: new users."
• Key Moments: use the words your team already says out loud, such as "First project published." You can rename a Key Moment later, but its slug is permanent.
• Segments: name them by who's in them, such as "Trial users: first 14 days," not by when they were made.

Write the conventions down where your team keeps shared docs, and link to them when someone new joins.

Keep your data clean

Messy data breaks targeting, skews dashboards, and gives Appcues AI the wrong picture of your users. Review it every quarter, or whenever targeting stops behaving as you expect.

• Look for duplicates. Check Settings > Properties and Settings > Events for near-identical names, such as createdAt and created_at. Pick one, and ask your developer to stop sending the other.
• Spot-check real users. Open a few profiles in Settings > Accounts & Users and confirm properties like plan and role are current. If they're stale, Appcues.identify() may not be running on every page load. See Set up Appcues.
• Check new events first. Before anyone instruments a new event, look for one that already covers it.
• Review your Key Moments. Confirm each one still matches how your product works. If an event was renamed or a feature changed, update the Key Moment, because every objective and dashboard built on it depends on it.
• Keep the installation plan current. Record every new property and event in your plan from Brief your developer before install.

To remove properties or events from Appcues entirely, contact support@appcues.com.

Keep live content current

Product changes can quietly break live experiences. A Tooltip loses its target, a Modal shows an old screenshot, or a campaign keeps running after its moment has passed.

• Act on recommendations. Appcues AI monitors live experiences and adds a recommendation to the Recommendations page when one starts failing, often with a fix it can apply for you. See Review and act on recommendations.
• Review on a schedule. Once a month or once a quarter, open each live campaign and check that its experiences match your current UI, that its audience still makes sense, and that its objective still measures what matters.
• Unpublish what's done. Old experiences that target broadly compete with newer ones for the same users. Check the Weight on experiences that overlap, and unpublish anything you no longer need.

Keep Appcues AI up to date

Appcues AI is only as current as what you tell it. When your product, audience, or terminology changes, an admin should update the context rules in Settings > Appcues AI. Each person can also review or clear what Appcues AI remembers about them on the same page. See Configure Appcues AI.

Test before you publish

Test new experiences where real users won't see them:

• Use a staging environment. In an experience's Settings tab, under Environment, choose Only the domains I choose and select your staging domain.
• Or target your team. Set the audience to an internal segment, or to your own user ID, and widen it after testing.

See Preview and test experiences.

Contact support

For help with your account, data, or content, contact support@appcues.com with:

• Your Appcues account ID, from Settings > Web
• A description of the issue or question
• Screenshots or a screen recording, if they help