Appcues: usage limits and mobile onboarding

Forecast usage before choosing a plan

Estimate your audience and publication schedule together. A plan with room for the audience can still constrain the experiences your team intends to launch.

Appcues pricing lists Start with up to 3,000 MAUs and ten published experiences. It advertises all experience types across plans, but Appcues’s pricing page gives no numerical price. Ask for the applicable price, staff access, delivery and warning thresholds, and potential charges in writing.

Appcues subscription guidance counts anonymous identifiers toward MAUs. Scheduled and live experiences both use the published-experience allowance. Include visitors before login and planned launches in your forecast.

For example, a team with several live guides schedules another for a release. That scheduled experience consumes allowance before it goes live. Review the usage meter before scheduling a second launch, and keep spare capacity for changes.

We found no Appcues documentation on what happens to live guides above an MAU limit. Include delivery and warning thresholds in the quote. Include potential charges for the quoted plan. Record who can authorize extra capacity during a launch.

Test the identity handoff

Treat identity as part of your implementation. A person and an identifier may not be equivalent. Compare your expected traffic with the count shown during a trial.

Appcues subscription guidance includes anonymous identifiers in MAUs. Appcues does not specify exactly how an anonymous session merges with a known user for your implementation. Test that transition instead of assuming a single count.

Use synthetic users to open your product before login, identify the same person, and repeat on another device. Record each identifier and the usage meter at each step. Ask an implementation owner to explain any extra entries.

Keep this exercise alongside the quote. If your product attracts substantial anonymous traffic, the pre-login population may change the capacity you need. A forecast based only on signed-in accounts leaves that traffic out.

Control changes to live targeting

Assign an owner to audience rules before publishing. A targeting edit can affect users without a separate publication step.

Appcues segment guidance says changes to segment rules immediately affect connected experiences without republishing. Agree who may edit a shared segment and review the affected experiences before saving a change.

For a trial, create a segment for a synthetic account and publish a test experience. Change the rule, then check whether the intended account still sees the experience. Record the editor and the time of the change.

Appcues segment guidance also describes a limited historical membership window for a newly created segment. Check the cohort window before using a new segment to interpret older behavior. Preserve the segment definition with your analysis so a later edit does not obscure your original question.

Match the runtime and data timing

Check the app runtime and the timing of the data used for targeting before committing to a rollout. A supported platform name alone does not prove that your particular flow works.

Appcues framework guidance lists native iOS and Android, React Native, Flutter and Ionic using Capacitor; it excludes Cordova. It distinguishes mobile web in a browser from content inside native apps. Bring the actual runtime to the vendor conversation.

Appcues public API guidance covers historical imports, bulk event export and flow publication. Some public API requests can take minutes; Appcues recommends its HTTP API when qualifying properties are needed immediately. Test the data path that determines whether the guide should appear.

An event export can help preserve reporting evidence, but Appcues does not document portable guide definitions. Inventory experiences and targeting rules before leaving. Open a sample export and ask which fields and history will remain available after cancellation.

Run a delivery trial

Use one representative journey and a synthetic audience to expose the work behind the builder. The person responsible for identity should join the author who maintains the experience.

Record the audience before and after login, then compare it with the usage meter. Schedule a test experience and inspect the published count. Change a segment rule and record the resulting delivery.

Repeat the journey in the runtime you intend to ship. Capture the guide shown and the product action that follows it. A completed tour measures exposure; the action tells you whether the onboarding helped with the task.

Ask for a written quote covering the expected audience and experience allowance. Include installations. Include staff access and the rule for a usage spike. Use the software trial guide to keep the same evidence across candidates.

How to compare the alternatives

Choose the alternative that resolves a specific constraint in your rollout. Compare its full workflow with the experience and identity model you already rely on.

UserGuiding may fit when a stated quota boundary helps your team plan capacity. UserGuiding pricing says guides stop above quota until the quota increases or usage falls. Its identification setup also deserves a deployment test.

Userpilot may fit a team evaluating native mobile engagement with an annual add-on. Userpilot mobile guidance requires an SDK and the add-on on Growth or Enterprise; custom mobile-content roles require Enterprise. Compare those terms with your runtime and authoring team.

The Appcues alternatives comparison puts the decisions side by side. The product onboarding buying guide includes a delivery and exit worksheet for the same synthetic journey.

Common questions

What does Appcues count toward MAUs?

Appcues subscription guidance includes anonymous identifiers. Test how your anonymous-to-known transition affects the count.

Do scheduled Appcues experiences count?

Yes. Appcues subscription guidance counts scheduled and live experiences toward the published-experience allowance.

Does Appcues support our mobile app?

It depends on your runtime. Appcues framework guidance lists supported technologies and excludes Cordova; test your own implementation.

Should we choose Appcues or an alternative?

If immediate segment changes suit your workflow, evaluate Appcues. If a documented quota cutoff or Userpilot mobile add-on matters more, compare those terms. Run the same trial.

Sources and scope

We read the linked vendor documentation on October 29, 2026. We have not run these products or tested their support.

Plan entitlements and implementation behavior need confirmation for your account.