Using connected data

Bring data from your existing tools into Nuxie's investigations.

You can ask Nuxie questions about the data in your connected services and use the answers to improve your app. Investigate a drop in onboarding completion, look into a customer’s subscription, or compare store purchases with the results of an Experience.

Connect the service once under Connectors, then use it in your Tasks. Nuxie retrieves the information available through the connector and explains what it finds.

Query a source

Name the service and the provider project or customer you want to investigate. For an analytics question, include the metric and time period; for a customer question, include the ID used by that provider. The connected account’s permissions determine which records Nuxie can reach.

Compare a Mixpanel funnel

Nuxie can find a project’s saved funnels by name and query them for a date range. You can name the funnel in your request or ask Nuxie to list the available funnels first.

For example, compare two periods for the same onboarding funnel. Replace the sample project ID, funnel name, and dates with your own:

This keeps the comparison on the same funnel. If the drop is concentrated at plan selection, you can continue the Task by asking Nuxie to inspect that screen and prepare a change to it.

Investigate a subscription

For a customer-specific question, give Nuxie the ID used by your billing provider. For example, replace user-456 with the customer’s RevenueCat ID:

The provider’s subscription information can explain an expiration, cancellation, or other lifecycle change. Use it alongside the customer’s Nuxie Feature access when investigating why a capability is locked.

Customer records

You can see information supplied by connected services on a Customer profile. In Overview, the Connector Sources section shows the available fields and the provider each came from.

These records sit alongside the properties and events sent by your app. For example, the billing provider can show the customer’s current subscription, while app events show when they opened checkout. Together, they help explain what happened and what access the customer should have now.

Compare sources

Connected data can add context to an Experience’s results. An onboarding completion rate tells you how many people reached its goal; app analytics can help show what those people did afterward.

Each source measures its own activity. A store total may include renewals, while an Experience counts conversions against a particular goal and time window. Ask Nuxie to account for those differences in the comparison:

See Analytics and revenue for the metrics available within Nuxie.

Continue the Task

Once you understand the result, you can ask Nuxie to act on it in the same Task. That might mean revising an onboarding screen, preparing a new offer, or setting up an Experiment to compare two approaches.

Nuxie presents work that needs your approval through the Proposal review process. A request to investigate data doesn’t also approve a live change to the connected service.

If the question is useful every week, turn it into an Automation. Include the source and question in its instructions so each run examines the right data. See Connecting accounts to add or manage the source.