You connect Adjust to Claude by adding Windsor’s native connector from inside Claude, then authorizing your Adjust account through Windsor.ai. Once that’s done, you can ask Claude directly about your installs, ad spend, and revenue numbers. No API key, no code, no CSV exports.
Adjust tracks installs, clicks, ad spend, and in-app revenue for your mobile apps, and its dashboard does that job well. What it isn’t built for is sitting next to the rest of your marketing stack. Comparing an Adjust number against your Google Ads or Meta Ads spend usually means exporting a report and rebuilding the comparison in a spreadsheet by hand. Once Windsor is connected, Claude can query your live Adjust data directly and blend it with 350+ other connected sources in the same conversation.
Connect Adjust to Claude in two steps
The whole setup takes about a minute, and there’s no code or manual export involved.
For a full walkthrough with screenshots, see Windsor’s documentation on integrating data into Claude.
Prerequisites
- A Windsor.ai account (free forever plan, no credit card required, or paid plans from $19/month)
- An Adjust account with at least one app actively sending data
- A Claude account on a plan that supports connectors
Step 1. Connect Adjust to Windsor.ai
- Create a free Windsor.ai account, or log in if you already have one
- Go to onboard.windsor.ai/app/adjust
- Select Adjust and authorize Windsor to read your account data
- Repeat the step for any additional Adjust apps you track, they’ll all appear under the same Windsor account
Step 2. Add the Windsor.ai connector in Claude
In Claude, open Customize, then Connectors, and search for “Windsor.” Select Add, sign in to your Windsor.ai account, and pick your Adjust connector from the list. That’s the whole install, one click plus a sign-in.
Confirm the connection is live before asking anything more complex:
List the data sources connected to my Windsor account. Do you see Adjust there?
Once Adjust shows up in that list, it’s ready to query in plain language, no dashboard logins or exports needed for every new question.
The metrics that matter for Adjust
| Metric | What it tells you |
|---|---|
| Installs | How many times your app was downloaded and opened for the first time, the core volume metric for measuring growth. |
| Organic Installs | How many of those installs happened without any paid click or impression, showing how much traction the app earns on its own. |
| Non-Organic Installs | How many installs are attributed to a paid click or impression, the number your media spend is actually buying. |
| Ad Spend (Attribution) | How much you spent acquiring users through paid channels, the cost side of every cost-per-install calculation. |
| Ad Revenue | How much money in-app ads generated, the key monetization number for ad-supported apps. |
| All Revenue | Total revenue from purchases and ads combined, so you can size the full commercial value your installs produce. |
| ROAS (All Revenue) | How much revenue came back for every dollar spent on ads, the headline number for judging whether a campaign is profitable. |
| Click Conversion Rate (CCR) | How efficiently ad clicks turn into installs, useful for spotting weak creative or a broken landing experience. |
| Network | Which ad network delivered a given click or install, so you can compare partners against each other on cost and quality. |
| Campaign | Which specific campaign drove installs, clicks, or revenue, letting you compare performance side by side. |
| Uninstalls | How many users deleted the app after installing it, an early warning sign of churn or a poor first experience. |
| ROAS (SKAN average) | Return on ad spend measured through Apple’s privacy-preserving SKAdNetwork, useful for judging iOS campaign profitability after ATT. |
What to ask Claude about your Adjust data: prompt ideas
Install and attribution performance
Show my total Adjust installs and organic installs by network for the last 30 days.
Break down non-organic installs by campaign and country for the current month.
Spend efficiency by campaign
Compare Ad Spend (Attribution) and ROAS (All Revenue) by campaign for the last 30 days, and flag any campaign where ROAS is falling.
Track click conversion rate by network over the last quarter and tell me where it dropped the most.
Retention and revenue cohorts
Show cohorted all revenue and uninstalls for installs from the last 30 days, grouped by campaign.
The Adjust connection through Windsor is read-only. Claude can analyze your installs, clicks, spend, and revenue, but it can’t create, pause, or edit anything inside Adjust itself.
Bonus: analyze Adjust alongside your full stack
Windsor connects 350+ sources, so Adjust doesn’t have to sit in its own silo. A few practical blends:
- Blended cost per install and ROAS across UA channels. Combine Adjust installs and Ad Spend (Attribution) with spend from Google Ads, Meta Ads, and TikTok Ads for one cross-channel install cost and ROAS figure instead of three separate dashboards.
- Installs versus real engagement. Pair Adjust installs with in-app event data from Amplitude to see which channel brings users who actually open and use the app, not just install it.
- Full revenue and LTV view. Blend Adjust’s all revenue and cohorted revenue with your e-commerce or subscription revenue data for a single source of truth on what each user acquisition channel is really worth.
Other ways to connect Adjust to Claude
Manual CSV export
You can export a report from Adjust and upload the file into a Claude conversation for a one-off analysis. It works for a quick look, but it’s a static snapshot from the moment you downloaded it. Every new question about more recent data means exporting and uploading again.
Zapier or Make
Zapier or Make can push Adjust events into another tool on a schedule. That’s workable if you already have a scenario built, but someone still has to build and maintain the automation, and it doesn’t give Claude a natural-language, queryable view of the data on its own.
Neither approach gives Claude the live, queryable connection that the native Windsor.ai connector does.
Conclusion
Connecting Adjust to Claude through Windsor.ai turns a dashboard-only, mobile attribution tool into a data source Claude can query directly, and blend with the rest of your marketing stack, in plain language. Setup takes about a minute and there’s nothing to code.
Ready to see your Adjust data in Claude? Connect Adjust to Windsor.ai and start asking questions in minutes.
FAQs
Do I need to write any code to connect Adjust to Claude?
No. The setup is entirely no-code: authorize Adjust in Windsor.ai, then add the Windsor.ai connector in Claude.
Can I connect more than one Adjust app?
Yes. You can connect multiple Adjust apps to the same Windsor.ai account, and ask Claude to compare performance across all of them in one conversation.
Can Claude change anything in my Adjust account?
No. The connection is read-only. Claude can analyze your installs, spend, and revenue data, but it can’t create, edit, or pause anything inside Adjust.
Can I combine Adjust with other marketing channels in Claude?
Yes. Windsor connects 350+ sources, so Claude can blend Adjust’s install and revenue data with platforms like Google Ads and Meta Ads for a cross-channel view instead of looking at mobile performance in isolation.
Can I connect Adjust to both Claude and ChatGPT?
Yes. Once Adjust is authorized in Windsor.ai, the same connection is available to any AI assistant with a native Windsor connector, including both Claude and ChatGPT, so you’re not locked into a single tool.
Windsor vs Coupler.io

