AppFigures is an app analytics and intelligence platform for mobile app developers and publishers. The AppFigures REST API at https://api.appfigures.com/v2/ exposes sales and download data, in-app purchase and subscription revenue, ad spend, App Store Optimization (ASO) keyword performance, rank trends, paid and organic search ad data, ratings and reviews, and reference data such as supported stores, countries, and currencies — enabling integrations to pull mobile-app performance data into warehouses, BI tools, or downstream analytics flows.
Power end-to-end data operations for your AppFigures API with Nexla. Our bi-directional AppFigures connector is purpose-built for AppFigures, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to AppFigures or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your AppFigures workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
The Nexla AppFigures connector authenticates using a 3-legged OAuth 2.0 flow. You will need an AppFigures account with a registered API client to obtain the Client ID and Client Secret required by the credential overlay. All API requests are sent over HTTPS to https://api.appfigures.com/v2/.
Navigate to the API Clients page at appfigures.com/developers/keys. This page is the central place to register and manage OAuth 2.0 clients tied to your account.
Click Create a new API Client (or New Client) to open the client registration form.
Provide the requested details for the new client:
Name: Enter a descriptive name for the client (for example, Nexla Integration). This name is shown on the AppFigures consent screen during authorization.
Description: Optionally enter a short description of how the client will be used.
Redirect URI: Set this to the Nexla OAuth callback URL displayed in the Nexla credential overlay. The redirect URI registered with AppFigures must exactly match the URI Nexla uses during the authorization flow.
Select the permissions (scopes) that the client requires. Scopes follow the {resource}:{access} format (for example, public:read, private:read, account:read). The Nexla connector default scope set is public:read,private:read,account:read, which grants read access to public app data, your own private app data, and account-level metadata. For complete information about AppFigures scopes, see the AppFigures scopes reference.
Select only the scopes that are required for the data your flows will read. Account administrators can revoke a client's authorization at any time from appfigures.com/account/clients.
Submit the form to create the client. AppFigures issues a Client Key (also referred to as client_id) and a Client Secret (also referred to as client_secret). Copy both values immediately and store them in a secure secret manager — the Client Secret is shown only at creation time and cannot be retrieved later.
Important
The Client Secret grants access to AppFigures data on behalf of any user who has authorized your client. Treat it like a password — never commit it to source control, and rotate it immediately if you suspect it has been exposed.
AppFigures uses a 3-legged OAuth 2.0 authorization-code flow. After you supply the client credentials, Nexla redirects you to AppFigures to sign in and approve the requested scopes, then exchanges the returned authorization code for an access token and refresh token, which are stored on the credential.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Confirm that the Authorization URL field is set to https://api.appfigures.com/v2/oauth2/authorize. This is the default value and should not be changed unless AppFigures has issued updated guidance.
Enter the Client Key issued by AppFigures for your registered API client in the Client ID field. This identifier is shown on the AppFigures API Clients page after the client is created.
Confirm that the Access Scope field is set to the scopes you selected when registering the API client. The default is public:read,private:read,account:read. Scopes are comma-separated and must match (or be a subset of) the scopes enabled on the client. For complete information, see the AppFigures scopes reference.
Confirm that the Token URL field is set to https://api.appfigures.com/v2/oauth2/access_token. This is the default value and should not be changed unless AppFigures has issued updated guidance.
Enter the Client Secret issued by AppFigures for your registered API client in the Client Secret field. This value is shown only once at client creation time and is treated as a secret.
Click Authorize to launch the AppFigures consent screen. Sign in to the AppFigures account that will be connected, and approve the requested scopes for your client. AppFigures redirects back to Nexla with an authorization code, and Nexla automatically exchanges the code for an access token and refresh token at the Token URL. The resulting tokens are stored on the credential and will be refreshed automatically by Nexla as needed.
Authorized clients can be reviewed and revoked at any time at appfigures.com/account/clients. Revoking the authorization in AppFigures will invalidate the stored tokens in Nexla, and the credential will need to be re-authorized.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the AppFigures connector tile, then select the credential that will be used to connect to the AppFigures instance, and click Next; or, create a new AppFigures credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common AppFigures endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
Get Paid Keywords for an App
This endpoint returns the paid Apple Search Ads keywords associated with a specific app. Use it to track which keywords competitors (or your own apps) are bidding on across storefronts.
Enter the AppFigures product ID of the app in the Product ID field. This field is required. Product IDs can be obtained from the List My Products or Search Products endpoints.
Optionally, enter a comma-separated list of two-letter country codes (for example, US,GB,DE) in the Countries field to limit results to specific storefronts. Use the List All Supported Countries endpoint for the full list of supported codes.
Optionally, enter the start date for the keyword data range (in YYYY-MM-DD format) in the Start Date field.
This endpoint returns the list of apps currently bidding on a specific search keyword. Use it for competitive analysis — for example, to see which apps are paying to rank for a high-value query in a given storefront.
Enter the search keyword to investigate in the Keyword Term field.
Enter the two-letter country code (for example, US) in the Country field to scope the search to a single storefront.
Optionally, enter an AppFigures product ID in the Product ID field to restrict results to a single app.
Enter the storefront to search in the Storefront field — typically ios or android.
This endpoint returns App Store Optimization (ASO) keyword performance statistics for one or more apps over a date range. Use it to monitor how your apps rank for tracked keywords and track changes over time.
Enter a comma-separated list of AppFigures product IDs in the Product IDs field. Product IDs can be obtained from the List My Products endpoint.
Optionally, enter a comma-separated list of country codes in the Countries field to filter results.
Enter the start and end dates of the reporting period (in YYYY-MM-DD format) in the Start Date and End Date fields.
Optionally, restrict results to a specific platform by entering iphone, ipad, or android in the Device Type field.
Enter the desired time bucket size in the Time Granularity field — daily, weekly, or monthly.
This endpoint returns keyword ranking trends for apps over a specified date range, with grouping and filtering options. Use it to monitor how an app's rank for tracked keywords changes over time.
Enter the dimension to group results by in the Group By field — common values include country, product, and keyword.
Enter a comma-separated list of AppFigures product IDs in the Product IDs field.
Optionally, enter a comma-separated list of country codes in the Countries field.
Enter the start and end dates (in YYYY-MM-DD format) in the Start Date and End Date fields.
Optionally, enter the device type (iphone, ipad, or android) in the Device Type field.
Set the Normalize field to true to normalize ranking data for cross-keyword comparison, or leave blank for raw rank values.
Enter the time bucket size in the Time Granularity field — daily, weekly, or monthly.
Results are paginated automatically. For complete details on rank trends and ASO endpoints, see the AppFigures ASO API documentation.
Get Download and Revenue Estimates
This endpoint returns estimated download and revenue figures for apps over a date range. Use it to benchmark performance against competitor apps for which you do not own the underlying store accounts.
Enter the start and end dates (in YYYY-MM-DD format) in the Start Date and End Date fields.
Enter the dimension to group results by in the Group By field — common values include country, product, and date.
Enter a comma-separated list of AppFigures product IDs in the Product IDs field.
Optionally, enter a comma-separated list of country codes in the Countries field.
Enter the desired response format in the Response Format field — typically json.
This endpoint returns payment and financial data for your connected apps over a date range. Use it to reconcile actual payouts from app stores against expected revenue, or to feed accounting systems with store-paid amounts.
Enter the start and end dates (in YYYY-MM-DD format) in the Start Date and End Date fields.
Enter the dimension to group results by in the Group By field — common values include country, product, and date.
Enter a comma-separated list of AppFigures product IDs in the Product IDs field.
Optionally, enter a comma-separated list of country codes in the Countries field.
Enter the desired response format in the Response Format field — typically json.
Get Ratings Totals
This endpoint returns aggregated user ratings totals for apps over a date range. Use it to track average star rating, total review counts, and rating distribution trends across stores and countries.
Enter the dimension to group results by in the Group By field — common values include country, product, and date.
Enter the start and end dates (in YYYY-MM-DD format) in the Start Date and End Date fields.
Enter the time bucket size in the Time Granularity field — daily, weekly, or monthly.
Enter a comma-separated list of AppFigures product IDs in the Product IDs field.
Optionally, enter a comma-separated list of country codes in the Countries field.
Enter the desired response format in the Response Format field — typically json.
Get Ad Spend Totals
This endpoint returns aggregated advertising spend data across connected ad networks for your apps over a date range. Use it to evaluate the cost side of user-acquisition campaigns alongside revenue and downloads.
Enter the dimension to group results by in the Group By field — common values include country, product, network, and date.
Enter the start and end dates (in YYYY-MM-DD format) in the Start Date and End Date fields.
Enter a comma-separated list of AppFigures product IDs in the Product IDs field.
Optionally, enter a comma-separated list of country codes in the Countries field.
Optionally, enter a comma-separated list of ad networks in the Ad Networks field to limit the report to specific networks (for example, apple_search_ads,meta,google).
Enter the desired response format in the Response Format field — typically json.
Get Subscriptions Totals
This endpoint returns aggregated subscription revenue and event data for your apps over a date range, with optional inclusion of one-time in-app purchases. Use it to monitor MRR/ARR, churn, and trial conversions across stores.
Enter the start and end dates (in YYYY-MM-DD format) in the Start Date and End Date fields.
Enter the dimension to group results by in the Group By field — common values include country, product, and date.
Enter a comma-separated list of AppFigures product IDs in the Product IDs field.
Set the Include In-App Purchases field to true to include one-time IAPs alongside subscription events, or leave blank for subscription data only.
Optionally, enter a comma-separated list of country codes in the Countries field.
Enter the time bucket size in the Time Granularity field — daily, weekly, or monthly.
Enter the desired response format in the Response Format field — typically json.
Get Usage Report Totals
This endpoint returns aggregated usage and session data for apps across ad networks over a date range. Use it to combine impression, click, install, and session counts in a single report for cross-network attribution.
Enter the start and end dates (in YYYY-MM-DD format) in the Start Date and End Date fields.
Enter the dimension to group results by in the Group By field — common values include country, product, network, and date.
Enter a comma-separated list of AppFigures product IDs in the Product IDs field.
Optionally, enter a comma-separated list of country codes in the Countries field.
Optionally, enter a comma-separated list of ad networks in the Ad Networks field.
Enter the desired response format in the Response Format field — typically json.
Get Revenue Totals
This endpoint returns aggregated revenue data across all sources (sales, in-app purchases, subscriptions, and ads) for apps over a date range. Use it as a single source of truth for top-line app revenue across stores and countries.
Enter the start and end dates (in YYYY-MM-DD format) in the Start Date and End Date fields.
Enter the dimension to group results by in the Group By field — common values include country, product, and date.
Enter a comma-separated list of AppFigures product IDs in the Product IDs field.
Optionally, enter a comma-separated list of country codes in the Countries field.
Enter the desired response format in the Response Format field — typically json.
Get Ratings
This endpoint returns raw individual rating events for apps over a date range. Use it when you need the per-rating granularity that the Get Ratings Totals endpoint aggregates away — for example, to feed a sentiment dashboard or downstream review-management system.
Enter the start and end dates (in YYYY-MM-DD format) in the Start Date and End Date fields.
Enter the dimension to group results by in the Group By field, when needed.
Enter a comma-separated list of AppFigures product IDs in the Product IDs field.
Optionally, enter a comma-separated list of country codes in the Countries field.
Enter the desired response format in the Response Format field — typically json.
List External Accounts
This endpoint returns the list of external store and ad-network accounts connected to your AppFigures account. Use it to audit which connections are active or to drive downstream provisioning of new flows.
No additional configuration is required beyond selecting this endpoint template. The endpoint automatically returns all external accounts visible to the authorizing AppFigures user.
This endpoint returns a paginated list of users in your AppFigures account. Use it for user-administration workflows — for example, syncing AppFigures users into an identity directory or building an internal access-review report.
No additional configuration is required beyond selecting this endpoint template. Results are paginated automatically by Nexla.
This endpoint returns sales and download data aggregated by configurable dimensions with extensive filtering options. Use it as the primary feed for app-store sales analytics — daily revenue, downloads by product or country, paid versus free dataset breakdowns, and device-type splits.
Enter the start and end dates (in YYYY-MM-DD format) in the Start Date and End Date fields.
Enter the dimension to group results by in the Group By field — common values include country, product, and date.
Enter the time bucket size in the Time Granularity field — daily, weekly, or monthly.
Enter a comma-separated list of AppFigures product IDs in the Product IDs field.
Optionally, enter a comma-separated list of country codes in the Countries field.
Optionally, restrict the report to a specific dataset (for example, app, iap, or book) by entering the dataset name in the Dataset field.
Optionally, enter a comma-separated list of devices (iphone, ipad, android) in the Devices field.
Set the Include In-App Purchases field to true to include IAPs alongside outright app sales.
Enter the desired response format in the Response Format field — typically json.
List Supported Store Categories
This endpoint returns the list of app-store categories supported by AppFigures. Use it as a reference lookup to join category IDs to human-readable names in downstream warehouses.
No additional configuration is required beyond selecting this endpoint template.
List All Supported Countries
This endpoint returns the full list of countries supported by AppFigures for reporting and filtering. Use it as a reference lookup to validate country codes used elsewhere in your flows.
No additional configuration is required beyond selecting this endpoint template.
List Countries Supported by Apple
This endpoint returns the list of countries supported by the Apple App Store. Use it as a reference lookup specific to Apple App Store distribution and reporting.
No additional configuration is required beyond selecting this endpoint template.
List Supported Languages for Review Translation
This endpoint returns the list of languages that AppFigures can translate app reviews from. Use it as a reference lookup when configuring review-translation downstream pipelines.
No additional configuration is required beyond selecting this endpoint template.
List Supported Currencies
This endpoint returns the list of currencies supported by the AppFigures API. Use it to validate currency codes in sales and revenue reports or to join currency metadata downstream.
No additional configuration is required beyond selecting this endpoint template.
List Supported Stores
This endpoint returns the list of app stores supported by AppFigures (for example, Apple App Store, Google Play, Amazon Appstore). Use it as a reference lookup when joining store IDs to store names in downstream models.
No additional configuration is required beyond selecting this endpoint template.
List Supported SDKs
This endpoint returns the list of SDKs that AppFigures can detect inside apps. Use it as a reference lookup to enrich SDK-detection outputs with vendor metadata.
No additional configuration is required beyond selecting this endpoint template.
Get Reviews
This endpoint returns app reviews with extensive filtering, search, and translation options. Use it to feed review analytics, sentiment scoring, or response workflows downstream.
Enter a comma-separated list of AppFigures product IDs in the Product IDs field.
Optionally, enter a comma-separated list of country codes in the Countries field.
Optionally, enter a free-text query in the Search Query field to filter reviews by content.
Optionally, enter a comma-separated list of star ratings (for example, 1,2) in the Stars field to filter by rating.
Enter the start and end dates (in YYYY-MM-DD format) in the Start Date and End Date fields to scope the review date range.
Optionally, enter a comma-separated list of language codes (for example, en,es) in the Languages field to filter by review language.
Optionally, enter a target language code in the Translate To field to have AppFigures translate review bodies into the chosen language.
Enter the sort order in the Sort field — for example, date or stars.
Results are paginated automatically by Nexla. Review translation may consume additional AppFigures API credits — see the AppFigures API credit usage reference.
Get Ads Totals
This endpoint returns aggregated paid advertising totals (impressions, clicks, installs, revenue) for your apps over a date range. Use it to evaluate paid acquisition effectiveness alongside organic data.
Enter the dimension to group results by in the Group By field — common values include country, product, network, and date.
Enter the start and end dates (in YYYY-MM-DD format) in the Start Date and End Date fields.
Enter a comma-separated list of AppFigures product IDs in the Product IDs field.
Optionally, enter a comma-separated list of country codes in the Countries field.
Optionally, enter a comma-separated list of ad networks in the Ad Networks field.
Enter the desired response format in the Response Format field — typically json.
Generate Ranks Report
This endpoint generates a chart-rank report for your apps across categories and storefronts over a date range. Use it to monitor category-leaderboard positioning and detect rank-movement events.
Enter a comma-separated list of AppFigures product IDs in the Product IDs field.
Optionally, enter a comma-separated list of country codes in the Countries field.
Enter the start and end dates (in YYYY-MM-DD format) in the Start Date and End Date fields.
Optionally, restrict results to a category by entering the category ID in the Category field. Category IDs can be obtained from the List Supported Store Categories endpoint.
Optionally, restrict results to specific subcategories by entering subcategory IDs in the Subcategory field.
Enter the chart type to retrieve in the Chart Type field — typically free, paid, or grossing.
Enter the time bucket size in the Granularity field — daily, weekly, or monthly.
Enter the dimension to group results by in the Group By field.
Rank reports can be data-intensive and may consume additional API credits when run over wide date ranges or many categories. For credit costs, see the AppFigures API credit usage reference.
Search Products
This endpoint searches across all public app products available in AppFigures by name, vendor, or other attributes. Use it to look up competitor or partner app product IDs to feed into other report endpoints.
Enter the search query term in the Search Term field.
Optionally, filter by app store with the Store field — typically apple, google_play, or amazon_appstore.
Optionally, filter by app type with the Type field — for example, ios, android, mac, or book.
Optionally, enter a vendor or developer name in the Vendor field to scope the search.
Results are paginated automatically. Use the returned id field as the product ID for other AppFigures endpoints.
List My Products
This endpoint returns the list of products (apps, IAPs, books) connected to your AppFigures account. Use it to discover the product IDs of your own apps to drive other report endpoints.
Optionally, set the Include Inactive field to true to include products that are no longer active in your account.
Optionally, set the Hide Section field to filter out a specific section (for example, archived apps) from the results.
Results are paginated automatically. The returned id field is the product ID required by most of the reporting endpoints above.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
AppFigures data sources can also be manually configured to ingest data from any valid AppFigures API endpoint under https://api.appfigures.com/v2/, including endpoints not covered by the pre-built templates — for example, the public Partner API endpoints or newly released report dimensions — as well as sources that chain multiple API calls or use custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
AppFigures only accepts requests over HTTPS — confirm that the API URL begins with https:// (for example, https://api.appfigures.com/v2/reports/sales?start_date=2026-01-01&end_date=2026-01-31&group_by=product). Nearly all AppFigures source endpoints use the GET method, and the OAuth 2.0 Authorization: Bearer header is added automatically based on the credential — no additional request headers are typically needed.
AppFigures expects dates in the sortable YYYY-MM-DD format. When using date/time macros such as {now} and {now-1} to enable incremental ingestion of reporting endpoints that require start_date and end_date parameters, set the Date Format for Date/Time Macro value to YYYY-MM-DD.
Response shapes vary by endpoint: list/search endpoints (for example, Search Products, Get Reviews) return an object with a results array — set the path to data to $.results[*]; most reporting endpoints (for example, Get Sales Report, Get Subscriptions Totals) return an object keyed by group dimension (date, country, or product) — use $.* to flatten it into records; and reference-data endpoints (for example, List Supported Currencies) return a top-level array — use $[*]. List endpoints frequently return pagination metadata (pages, total) alongside the results array, which can be preserved into each record by entering its path (for example, $.pages) in the Path to Metadata in Response field.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new AppFigures data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the AppFigures destination, and select the Send to Destination option from the menu. Select the AppFigures connector from the list of available destination connectors, then select the credential that will be used to connect to the AppFigures account, and click Next; or, create a new AppFigures credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common AppFigures endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Create External Account
This endpoint creates a new external account connection in AppFigures — for example, an iTunes Connect, Google Play, or ad-network account that AppFigures will pull data from. Use it to programmatically onboard new store and ad-network connections from upstream systems.
Each record in the upstream Nexset must include the fields AppFigures requires to register an external account — typically a store or network identifier, the credentials needed to authenticate to that store/network (for example, a username and password, an API key, or an issuer/key pair), and any optional metadata such as a label.
The full record is sent as the JSON body of the POST /external_accounts call. Use the Nexla transform layer to shape upstream attributes into the field names expected by AppFigures.
External-account credentials are sensitive. Ensure upstream Nexsets are sourced from a secure secret manager and that the destination is restricted to authorized users. For full details, see the AppFigures External Accounts reference.
Update External Account
This endpoint updates an existing external account in AppFigures — for example, to rotate credentials or change a label. Use it as part of a credential-rotation workflow that keeps AppFigures connections current.
Enter the AppFigures external account ID in the Id field. This identifies which account to update and can be obtained from the List External Accounts source endpoint or from an upstream Nexla flow.
The body of each PUT call is the upstream record (as JSON). Include only the fields that should be changed — omitted fields are left untouched.
Updating credentials on an external account may temporarily interrupt data collection for the associated store or network. For complete details, see the AppFigures External Accounts reference.
Update User Status
This endpoint updates the active status of a specific user in your AppFigures account. Use it to drive deprovisioning or reactivation from an identity directory — for example, deactivating an AppFigures user when their account is offboarded in your IdP.
Enter the AppFigures user ID in the Id field. User IDs can be obtained from the List Users source endpoint.
The body of each PUT call is the upstream record carrying the new status fields (for example, an active boolean or a role assignment) expected by AppFigures.
This endpoint updates properties on a specific AppFigures product — for example, toggling active status, visibility, or display metadata. Use it to keep product configuration in AppFigures in sync with a downstream system of record.
Enter the AppFigures product ID in the Product ID field. Product IDs can be obtained from the List My Products or Search Products source endpoints.
The body of each PUT call is the upstream record (as JSON). Include only the fields that should be changed.
AppFigures destinations can also be manually configured to send data to any valid AppFigures API endpoint under https://api.appfigures.com/v2/ — for example, account-level write endpoints or newly released API operations. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
AppFigures write endpoints use POST to create resources (for example, POST /external_accounts), PUT to update resources (for example, PUT /products/{id}, PUT /users/{id}), and DELETE to remove them. The API expects application/json for all write endpoints, so JSON is the appropriate Content Format for every AppFigures destination, and requests are only accepted over HTTPS. For update operations, include the resource ID at the end of the URL — Nexla macros can substitute the ID from each upstream record (for example, https://api.appfigures.com/v2/products/{id}).
The write endpoints covered by the templates above operate on a single resource per request and do not natively support batched create/update calls, so record batching is best left disabled for AppFigures destinations. Enabling the response webhook is particularly useful for Create External Account (to capture the new account ID) and for any update operation where you need to confirm success and capture the updated resource state.
Important
Test payloads sent to write endpoints (such as Create External Account, Update External Account, Update User Status, or Update a Product) will make real changes in your AppFigures account. Use a test or non-production AppFigures account before sending test data against a production account.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to AppFigures, open the destination resource menu, and select Activate.
The Nexset data will not be sent to AppFigures until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
