Supported Technologies and Frameworks
Submit Article Requests
Do you have a suggestion for an article you would like to see created?
Feel free to submit this form and add your suggestions to our document board.
- Installation & Developers
- Web Experiences
- Mobile Experiences
- Account Management
- Best Practices
- System Status
Table of Contents
How we handle the technology you may use in your application.
We are aware that every product is architected uniquely and our goal is to support all common technologies. However, check out the items below to help ensure a successful implementation of Appcues.
If you would like to discuss your framework, feel free to contact us.
What frameworks can you build Experiences in?
|Support Frameworks||Including||Exceptions & Notes|
Single Page Applications
Native iOS & Android
|*Not supported in Native apps at this time|
|iFrames||iFrames built by your team within your own product||3rd party iFrames need the Appcues snippet installed within the iFrame to display Experiences within them|
Additional Details about Supported Frameworks
Mobile web and mobile apps
Appcues supports mobile web. Experiences are built to be responsive and will adjust as elements on your page move based on the browser size.
Note: Reducing the width of a browser on a desktop will not classify it as a mobile browser. Mobile devices are identified based on whether the browser used is a mobile browser, such is the case for all handheld mobile devices, such as mobile phones, tablets, etc.
Appcues supports native mobile apps built for iOS, Android, and cross-platform frameworks like React Native, Flutter, and Ionic.
Single-page apps (SPAs) and front-end frameworks
Appcues requires an initial page load to identify users and then polls regularly to check whether a flow should show based on changing criteria (page URL or user activity). Alternatively, you can choose to send page change updates to Appcues. This option is can be set during the installation.
There is no separate implementation work required for single-page applications.
Multiple products and environments
You can use Appcues with different products or with different environments (with different domains).
To do so, simply install Appcues using your same unique code snippet across all these products and environments. You can then specify which Experience should show on which product/environment by configuring the settings within the Page Targeting section.
Any account-level styling and configurations for your Appcues account will apply across all these domains. This includes the admins on your account being able to access Experiences.
Please note that installing Appcues in multiple products comes with additional costs.
Dynamic URLs and multiple subdomains
Appcues supports dynamic URLs and multiple subdomains (e.g. for your different customers) for your application.
You can use wildcard or regex matching to configure any step to a specific URL. You can also substitute any part of the URL with the specific user data, by using variables. This is akin to using merge tags to replace a part of a string with the specific content for that user.
You can use a similar approach to handle personalized subdomains. If you change your subdomains by customer name, then we encourage you to send this part of the URL as a company attribute.
Appcues allows you to build Experiences across any iFrames you might have in your application.
To guarantee ideal performance, please ensure that the Appcues code snippet is implemented separately within each iFrame component. Having iFrames load content from the same subdomain as the top-level page makes the process more simple and seamless. Also, ensure that the iFrame element does not use the sandbox attribute
Other supported features
To show Experiences to users who are not logged in to your product - and therefore not identified - you need to identify these users by using the Appcues.anonymous() call.
Strict security standards
Appcues takes security very seriously and we seek to continually improve our systems with the most cutting-edge techniques to guard against any attacks or unauthorized access.
Appcues does not collect any user-entered text or information within form fields in your application. To support Appcues in delivering its Services, Appcues engages third party cloud service providers, such as Amazon Web Services (AWS). You can learn more about key vendors which process data on our behalf by visiting our Subservice Providers page. They allow Appcues to operate in a robust, fully multi-tenant infrastructure with the same reliability, performance, and security characteristics of their parent companies. Appcues keeps a current SOC-2 report on file for all subservice providers.
All of the application data collected by Appcues is transmitted over SSL, encrypted both in transit and at rest. You can read more about our Security Practices from our website.
If your application contains a Content Security Policy (CSP) to limit which third-party code may be executed on the pages of your application, then you must whitelist our domains in order to enable Appcues to function correctly.
Multilingual support (Localization)
Appcues supports multiple languages in two different ways:
- Using our dedicated localization feature.
- By manually duplicating Experiences for different languages and targeting them based on user properties (e.g. browser language).
We are working on improving our Localization feature soon. Feel free to leave feedback if this is important to you!
Where can Experiences be shown?
Appcues supports all modern browsers, including Google Chrome, Mozilla Firefox, Apple Safari, and Microsoft Edge, for showing users product Experiences. You will access the Builder via a Chrome Extension in Google Chrome in order to build your Experiences.
Note: If you think Appcues is not rendering correctly on any specific browser, please contact support so we can take a deeper look into the underlying issue.