If your team is moving on from Appcues, this guide walks through how to fully remove the Appcues installation from your web and mobile applications. Follow every section that applies to your setup to ensure no Appcues code, data, or side effects remain in your product.

Before you start

• Cancel your subscription. Go to Settings > Subscription and follow the cancellation steps, or email support@appcues.com. Removing the code without cancelling does not stop billing. This is especially important for mobile apps — cancelling your subscription churns your account, which blocks Appcues from processing any data. Since mobile SDK changes only take effect in the app version where the change was made, users on older versions of your app may continue sending data to Appcues until they update. Cancelling ensures that lingering traffic from older versions is ignored.
• Unpublish all live experiences. Go to your Appcues dashboard and unpublish any live Experiences. This prevents brief flickers or errors during the removal process if there's a gap between removing some code and all code.

Uninstall Appcues from your web app

Step 1: Remove the Appcues SDK script

How you remove the SDK depends on how it was originally installed.

Installed via JavaScript snippet

Find and delete the Appcues embed script from your application's HTML. It looks like this:

<script src="https://fast.appcues.com/ACCOUNT_ID.js"></script>

This is typically in your main layout template, index.html, or a shared header partial.

Installed via NPM

1. Remove the package:

npm uninstall @appcues/sdk

2. Delete any import or require statements referencing the Appcues SDK in your codebase. Search for @appcues/sdk or appcues across your project files.

Installed via Segment

1. In your Segment workspace, go to Connections > Destinations.
2. Find the Appcues destination and click it.
3. Click Disable Destination, then confirm.
4. Optionally, delete the destination entirely to keep your workspace clean.

Installed via Google Tag Manager

1. Open your GTM container.
2. Go to Tags and find the Appcues tag.
3. Delete the tag.
4. Publish the container to push the change live.

Step 2: Remove all Appcues JavaScript calls

Search your codebase for any references to the Appcues or appcues global object and remove them. Common calls to look for:

• Appcues.identify()
• Appcues.group()
• Appcues.track()
• Appcues.page()
• Appcues.show()
• Appcues.on()
• Appcues.off()
• Appcues.reset()
• Appcues.anonymous()

A quick way to find them all:

grep -rn "Appcues\." --include="*.js" --include="*.ts" --include="*.jsx" --include="*.tsx" .

Remove every match. If any of these calls run after the SDK is removed, they will throw ReferenceError or TypeError exceptions in your users' browsers.

Confirm the web uninstall worked

• Deploy your changes to production.
• Open your application in a browser and check the browser console (right-click > Inspect > Console). Confirm there are no errors referencing Appcues or requests to appcues.com.
• Open the Network tab in DevTools, reload the page, and filter for appcues. No requests should appear.

Uninstall Appcues from mobile apps

If you installed Appcues in an iOS, Android, React Native, Flutter, or Ionic app, follow these steps in addition to (or instead of) the web steps above.

Important: Mobile SDK changes only apply to the app version where the removal is made. Users running older versions of your app will still have the Appcues SDK installed and may continue to identify users and send data to Appcues. Unless you have a way to force users to update (such as a mandatory update gate), you cannot fully stop data collection on older versions through code removal alone. This is why cancelling your subscription before uninstalling is critical — it churns your account and blocks Appcues from processing any data, including traffic from older app versions still in the wild.

Step 1: Remove the Appcues Mobile SDK

iOS (Swift Package Manager)

1. In Xcode, go to your project settings and select Package Dependencies.
2. Find appcues-ios-sdk and click the Remove (minus) button.

iOS (CocoaPods)

1. Open your Podfile and remove the AppcuesKit pod.
2. Run pod install to update your workspace.

Android (Gradle)

1. Open your app-level build.gradle (or build.gradle.kts) and remove the Appcues dependency. It looks like this:

implementation 'com.appcues:appcues:<version>'

2. Sync your project.

React Native

npm uninstall @appcues/react-native

Then remove any native linking artifacts by running npx pod-install (iOS) and syncing Gradle (Android).

Flutter

1. Open pubspec.yaml and remove the appcues_flutter dependency.
2. Run flutter pub get.

Ionic (Capacitor)

npm uninstall @appcues/capacitor
npx cap sync

Step 2: Remove all Appcues mobile SDK calls

Search your mobile codebase for any references to the Appcues SDK and remove them. Common calls to look for across frameworks:

• Appcues.identify()
• Appcues.group()
• Appcues.track()
• Appcues.screen()
• Appcues.show()
• Appcues.reset()
• Appcues.anonymous()

Also remove:

• Deep link / URL scheme configuration added for Appcues debugging and previewing. Check your Info.plist (iOS) or AndroidManifest.xml (Android) for URL schemes containing appcues- or your Appcues App ID.
• AppcuesFrameView / Appcues Embed views placed in your layouts or SwiftUI views.
• Appcues initialization code, typically called in your AppDelegate, Application class, or root component. Look for Appcues(config:) or Appcues.Builder().

Step 3: Remove Appcues via Segment (mobile)

If you installed the Appcues mobile SDK through Segment's device-mode plugin:

1. Remove the Appcues device-mode destination plugin from your Segment mobile configuration.
2. In your Segment workspace, go to Connections > Destinations, find the Appcues mobile destination, and disable or delete it.

Confirm the mobile uninstall worked

1. Build and run your app on a device or simulator.
2. Check the device logs (Xcode Console or Android Logcat) for any errors referencing Appcues. None should appear.
3. Monitor network traffic using a proxy tool like Charles or the Xcode network inspector. No requests to api.appcues.com or fast.appcues.com should appear.

Remove the Chrome Extension

The Appcues Builder Chrome Extension is only used by your team, not your end users, but it should be cleaned up.

1. Open Chrome and go to chrome://extensions/.
2. Find Appcues Builder and click Remove.

Have every teammate who had the extension installed do the same.

Clean up Content Security Policy (if applicable)

If your team added Appcues domains to your Content Security Policy (CSP), remove them. Domains to look for in your CSP headers or meta tags:

• fast.appcues.com
• *.appcues.com
• *.appcues.net
• my.appcues.com

Leaving unused domains in your CSP is not harmful, but cleaning them up is good security hygiene.

Remove Identity Verification (if configured)

If you set up Identity Verification, your backend is generating an HMAC signature for each user and passing it to the Appcues SDK. Remove:

• The server-side code that generates the HMAC signature for Appcues.
• Any environment variables storing your Appcues Identity Verification secret key.

Request a GDPR data deletion

Removing the Appcues SDK stops new data from being collected, but it does not delete the end-user data Appcues has already stored. If you need to fully scrub all user data from Appcues systems — whether for GDPR, CCPA/CPRA compliance, or your own data retention policies — you have two options.

Option 1: Use the GDPR Deletion API

If you have a list of User IDs to delete, you can submit them directly through the GDPR Deletion API.

1. Prepare a CSV file containing the User IDs you want scrubbed.
2. Submit the file via the API using your Appcues API key:

curl https://api.appcues.com/v1/gdpr/delete \
  -u YOUR_API_KEY: \
  -F 'data=@users.csv'

3. Appcues will process the deletions within 30 days.

Option 2: Contact support

If you want to request a full account-level data scrub — removing all end-user data associated with your Appcues account — email support@appcues.com with the subject line "GDPR account data deletion request" and include your Appcues Account ID. Appcues cannot accept deletion requests directly from your end users since identity verification is required, so all requests must come from an authorized account administrator.

If you see lingering Appcues requests

• Cached assets. Hard-refresh the page (Ctrl+Shift+R / Cmd+Shift+R) or clear the browser cache. If your application uses a service worker, you may need to unregister it and refresh.
• Missed code path. A conditional branch or lazy-loaded module may still contain Appcues calls. Re-run the grep search from Step 2 and check dynamically loaded files.
• Third-party integration. If another tool (like Segment) is still sending data to Appcues, disable the Appcues destination in that tool's settings.

Still have questions?

Contact us at support@appcues.com.