Once you've published your first experience, this guide helps you keep your Appcues account organized, your data reliable, and your content effective over time. Treat this as a reference you return to as your team and experience library grow.

Measure impact with Goals

Goals track whether your experiences drive the outcomes you care about. Attach a Goal to every experience you publish — without one, you're guessing at impact.

1. Open any experience in Appcues Studio and navigate to the Goals section in the settings page.
2. Select the event or property change that represents success. Example: for a feature adoption Tooltip, set the Goal to the event that fires when a user activates that feature.
3. Set a conversion window (the time after seeing the experience in which the action counts). Start with 7–14 days for onboarding experiences and 3–7 days for feature nudges.

Goals measure conversion rate and attribute results to users who saw the experience. See Goals overview.

Compare against a baseline

A conversion rate alone doesn't tell you whether the experience caused the behavior. Use control experiments to compare users who saw the experience against a holdback group who didn't. This gives you actual lift — the difference the experience made.

For iterating on content, use A/B testing to compare two versions of the same experience and identify which copy, design, or timing performs better.

Review analytics regularly

Check experience performance in the Analytics tab for each experience, or use the Events Explorer for a cross-experience view of engagement and event data.

Key metrics to monitor:

• Impressions/Shown — is the experience reaching the expected audience size? A sudden drop may mean a targeting condition changed or a property stopped flowing.
• Completion rate — are users finishing the experience? Drop-off on a specific step usually means the copy is unclear or the action is too complex.
• Goal conversion — is the experience driving the behavior you defined? Low conversion with high completion suggests the experience is engaging but not motivating the right next step.

Organize your team

As more people build in Appcues, clear roles and permissions prevent accidents and keep content quality consistent.

Assign roles

Open Settings > Team in Appcues Studio to manage team members and roles. Consider who needs to build vs. who needs to review or publish. Limit publishing access to people who understand your targeting strategy and naming conventions.

See Manage your team in Appcues for role-level details and best practices.

Agree on naming conventions

A naming convention keeps your experience library manageable as it grows. Without one, you end up with dozens of experiences named "Welcome flow," "new welcome," and "welcome v2 FINAL" that no one can distinguish.

Use a pattern that includes the use case, experience type, and audience:

• [Onboarding] Welcome modal — new users
• [Feature adoption] Reporting tooltip — paid plans
• [Announcement] Q1 release banner — all users

Apply the same discipline to segments. Name segments by what they describe, not when they were created: Trial users — first 14 days is findable; Segment for Q3 campaign is not.

Document your conventions

Keep a shared document (internal wiki, Notion page, or similar) that lists your team's conventions for experience names, event names, property names, and segments. Link to it when onboarding new teammates to Appcues. This prevents drift as your team changes.

Keep your data clean

Messy data leads to broken targeting, unreliable analytics, and duplicated effort. Data hygiene is an ongoing habit, not a one-time setup.

Audit properties and events

Review the Events and Properties page in Studio quarterly (or whenever you notice targeting issues).

• Hide stale properties. If a property is no longer sent by your product or hasn't had a new value in months, toggle Show in Menus off. This prevents teammates from building targeting rules on dead data.
• Check for duplicates. Look for near-identical property or event names caused by inconsistent casing or formatting (createdAt vs. created_at vs. Created At). Consolidate around one name and update your installation code to stop sending the duplicates.
• Verify values are current. Open a few user profiles in the Users section and spot-check that properties like plan and role reflect reality. If they're stale, your Appcues.identify() call may not be running on every page load. See the data hygiene section in Set up Appcues.

Keep events meaningful

As your product evolves, some events become irrelevant — features get renamed, workflows change, experiments end. Unused events clutter your menus and confuse teammates.

• Review your event list alongside your active Goals. If an event isn't used in any Goal, targeting rule, or Workflow, consider hiding it.
• Before instrumenting a new event, always check if a similar one already exists. The Events and Properties page is your source of truth.
• To request removal of properties or events from the Appcues database (not just hidden in UI), contact support@appcues.com.

Maintain your content

Published experiences need periodic review. Product UI changes, user needs shift, and stale content erodes trust.

Schedule content reviews

Set a recurring reminder (monthly or quarterly) to review your active experiences. For each one, check:

• Is the UI still accurate? If your product's navigation or layout has changed, Pins, Tooltips and Hotspots may point to the wrong elements, and screenshots in Modals may be outdated.
• Is the targeting still relevant? An onboarding Flow built for a feature that's been redesigned may confuse more than it helps. Update the content or retire the experience.
• Is the Goal still meaningful? If the success metric has changed (the event was renamed, the activation milestone shifted), update the Goal or the experience will report misleading conversion data.

Archive or unpublish stale experiences

Don't leave old experiences running if they're no longer useful. Unpublish them in Studio. Old experiences that target broadly can interfere with newer, more relevant content — especially if you have frequency and priority settings that limit how many experiences a user sees per session.

Keep a record of what you archive and why, so you can reference past decisions when planning new content.

Use staging and production environments

If your product has a staging or QA environment, use it to test experiences before publishing to production. This prevents unfinished or broken content from reaching real users.

Appcues uses the snippet's account ID to determine which experiences to load. Use the same account for both environments and limit testing to internal segments, or set up separate environments if your plan supports it. 

Contact support

If you need help with account management, data issues, or content strategy, contact support@appcues.com with:

• Your Appcues account ID
• A description of the issue or question
• Screenshots or screen recordings if applicable