Guide · 8 min read
Cross-App Promotion Strategy: Find Partners and Drive Installs Without Ad Spend
Cross-app promotion is the highest-intent, lowest-cost user acquisition channel most indie developers have never tried. Instead of paying an ad network to find users similar to your best customers, you go directly to the app those users already have on their phone — and trade placements with its developer. No CPMs, no minimum budgets, no media buyer. When audience fit is right, cross-app deals deliver installs that activate and retain at rates paid social rarely matches.
Cross-app promotion is a direct audience trade, not an ad buy
Cross-app promotion delivers users who have already proven they download apps in your category — because you're reaching them inside another app they actively use. The mechanism is a direct deal between two non-competing developers: App A shows a recommendation for App B inside its own UI or to its email list, and App B does the same in return. No money changes hands in the basic form. Only audience access is exchanged.
This is structurally different from everything in standard paid UA. In a paid campaign, you describe your ideal user and pay a network to guess who matches. In a cross-app deal, your partner already has a verified relationship with users who fit your profile — because they downloaded a complementary app for the same underlying reason they would download yours.
The same model drove early growth for apps like Calm (promoted inside meditation-adjacent productivity tools before it became a brand name) and is used systematically by large game studios to move users across their own app portfolios. The indie version requires no portfolio — just one willing partner and a basic agreement. For context on where cross-app promotion sits relative to other channels, the user acquisition channels guide for 2026 benchmarks its cost per install against paid search, social, and ASO-driven organic.
3 partner qualification criteria — all 3 must pass before outreach
A cross-app partner must pass three tests before you send the first email: audience overlap, size parity, and no substitution risk. A partnership that fails any one of these delivers noise, not installs.
Audience overlap (ICP match): Your users and their users must share the same core profile — same demographics, same problem, same behavior pattern. A habit-tracking app and a sleep app share a self-improvement user archetype. A habit-tracking app and a photo editor do not, even if both are "productivity adjacent." The test: would your average user realistically install the partner app in the same week they installed yours? If yes, the profiles overlap.
Size parity: An app with 500 monthly active users cannot propose a fair trade with an app that has 500,000. The smaller app is asking for charity, not proposing a deal. Target partners within one order of magnitude of your active user base. At early scale that means other indie apps with 500–5,000 MAU. No substitution risk: The partner app must not do what your app does. Promoting a to-do app inside another to-do app increases churn on both sides. Promoting a to-do app inside a time-blocking calendar is complementary — different tools, same workflow. Review their feature list, not just their App Store description, before reaching out.
Where to find your first partner beyond who you already follow online
App Store category adjacency is the fastest path to a qualified partner list — look at which apps your users also have installed, which is observable from the "You Might Also Like" and "Customers Also Bought" rows on your App Store listing. These apps are pre-qualified by behavior: users have voluntarily paired them with yours. Start your outreach list there before going anywhere else.
Community-sourced leads are the next tier. IndieHackers, r/iOSProgramming, r/androiddev, and the indie dev community on Twitter/X are where small-team developers talk openly about their metrics and user feedback. Developers who share download counts, revenue, and retention data publicly are far more likely to entertain a direct partnership than developers who don't — they've already demonstrated a willingness to be transparent about their numbers.
The direct cold email is underused and underrated. A two-paragraph message that (a) names their app correctly, (b) states your active user count honestly, and (c) proposes a specific starting format — a mutual email mention in the next newsletter, for example — converts better than most developers expect, because almost nobody sends it. Keep the ask small and time-bounded. "One mention in our next email, we do the same, and we compare notes in 30 days" is a much easier yes than "let's explore a formal partnership."
4 placement formats ranked by install conversion rate
In-app placement inside an active screen converts 3–8× better than an email mention — because the user is already in an engaged state, not scanning an inbox. The format choice matters as much as the partner quality.
In-app recommendation card: The highest-converting format. A card in the settings screen, post-session summary, or a dedicated "apps we recommend" section puts the promotion in front of users who are actively using a product they trust. This is where you want to be. Email mention: Lower volume, high trust. A partner's newsletter list is their most engaged audience. A genuine editorial mention ("we use X to do Y, and our users tell us they do too") converts better than a banner placement, though it fires once per send rather than continuously. Push notification shoutout: High reach, real churn risk. Push notifications for partner apps can feel intrusive. Use this format only if both parties have opted-in bases and the message is framed as a personal recommendation, not an advertisement — and even then, treat it as a one-time play.
Onboarding integration: The highest-effort but potentially highest-value format. If your onboarding flow has a "complete your toolkit" or "you might also want" step, a well-placed partner mention lands when user motivation is at its peak. This requires code changes from both parties, so it only makes sense after a shorter-format test has already confirmed the partnership converts. When building any promotional creative — cards, email banners, or onboarding assets — the screenshot size requirements reference covers the precise dimensions needed for each device class so your visual assets export cleanly.
Structuring the deal: the 30-day trial format that works without a lawyer
The simplest and most durable structure is a time-bounded equal-placement swap: both parties run the same format for 30 days, then share install numbers before deciding whether to extend. No payment, no contract, no irreversibility — if one partner gets 400 installs and the other gets 40, the deal rebalances (different placement prominence, or one party adds an email mention to compensate).
On attribution: referral links outperform UTM parameters for App Store partnerships. A deep-linked referral URL gives you install attribution across app and web; UTM parameters work for web landing pages but lose attribution on App Store redirects, where the handoff strips query strings. Both AppsFlyer and Branch generate partner-specific install links that survive App Store redirects — use one, and make sure both parties agree on who tracks what before the campaign starts. If you're comparing measurement options, the ASO tools guide covers the free-tier attribution options that work for indie budgets.
Keep the initial ask small on purpose. A 30-day email mention with shared results is a low-stakes way to validate that your audiences actually convert across the deal before either party invests in deeper integration. Most partnerships die not from bad fit but from over-commitment on the first deal — one party builds an in-app section before the email test has shown any signal.
Day-7 retention, not install count, is the metric that determines whether to continue
Day-7 retention is a better partnership health metric than install count — a deal that drives 200 installs with 40% Day-7 retention beats one that drives 500 installs with 5% Day-7 retention every time. Volume without retention just means you sent a lot of users to churn.
Users who discover your app via a genuine recommendation from a trusted developer often activate and retain at a higher rate than cold ad installs. They arrive with a pre-formed expectation set by the partner's framing, which means less work for your onboarding flow to do. Track activation events (not just opens) for partner-sourced installs specifically — if they hit your core action faster than average, that's a strong signal the audience fit is real, and the partnership is worth deepening. The App Store Connect analytics guide covers the retention metrics available natively before you invest in a third-party MMP.
Ongoing deals should be revisited quarterly. Seasonal relevance shifts — a productivity partnership that converts well in January may underperform in July. A partner who launched as a complementary tool may have since shipped features that make your apps substitutes. Build a quarterly review checkpoint into the deal structure from day one, and treat it as a standing check on both audience fit and competitive overlap.
When cross-app promotion fails: the 3 patterns that waste everyone's time
Audience mismatch is the most common failure mode. A meditation app promoted inside a gaming app gets curiosity installs from users who downloaded a game app because they wanted to play a game — not sleep better. The installs arrive; the Day-7 retention doesn't. Audience mismatch is almost always visible in the Day-1 data: if open rate on Day 1 is normal but Day-3 drops sharply, the users arrived without the problem your app solves.
Poor placement context is the second failure pattern. A promotion shown in the app's friction state — a loading screen, an error state, a mid-task interruption — carries the emotional residue of the friction, not the recommendation. Placement in a success state (post-session summary, completion screen, achievement moment) carries positive association and converts measurably better. Always negotiate which screen the promotion appears on, not just whether it appears in the app.
Competitive drift is the long-term risk that most developers don't anticipate. A partner who launched as a complementary tool can expand their feature set over time into territory that makes your apps substitutes. Review partner app release notes every quarter for ongoing deals — a feature update that adds something your app does is a reason to pause the deal before your promotion actively sends users to a competitor. For a deeper framework on how App Store presence and listing quality affects where users go after they discover you via any channel, the custom product pages and organic search guide covers how to convert discovery traffic once it arrives.
The deal that costs nothing to try and compounds over time
Cross-app promotion is the only user acquisition channel where the cost of entry is a two-paragraph email and the willingness to share your MAU honestly. The first deal is slow — finding the right partner takes longer than the campaign itself. The second deal is faster. By the third, you have a repeatable playbook and a short list of partners who've already proven they send retained users.
The promotional assets you build for these deals — in-app cards, email banners, recommendation screenshots — are the same assets you need for any channel. Design them in the AppsTemple editor, where you can preview across device frames and export to the exact dimensions each format requires. Cross-link your screenshot templates with any in-app card designs so the visual system stays consistent across every surface where users encounter your app.
Create your promotional assets in the editor →
Frequently asked questions
what is cross-app promotion and how does it work
Cross-app promotion is a direct deal between two non-competing app developers where each promotes the other's app to their own user base — through an in-app recommendation card, an email mention, or a push notification. No money changes hands in the basic version; each party trades audience access. It works best when both apps share the same type of user (a fitness app and a nutrition app, for example) but don't do the same thing, so neither app loses users to the other.
how do i find other indie developers to partner with for cross-promotion
Start with the "You Might Also Like" and "Customers Also Bought" rows on your own App Store listing — these apps are already paired with yours by user behavior, making them pre-qualified partner candidates. IndieHackers, r/iOSProgramming, and Twitter/X's indie dev community are where developers with similar-scale apps discuss their metrics publicly and are most open to direct partnership conversations. A short, specific cold email proposing a low-commitment first trial (a mutual email mention, tracked with install links) is surprisingly effective because almost nobody sends one.
how do i measure installs from a cross-app promotion deal
Use referral links with install attribution rather than UTM parameters — UTM tags are stripped during App Store redirects, so you lose tracking on the handoff. Tools like AppsFlyer, Branch, and Adjust all generate partner-specific install links that survive the App Store redirect and correctly attribute installs to your cross-promotion deal. After install, track Day-1 and Day-7 retention for partner-sourced users specifically; if they retain better than average, the audience fit is real.
what should i offer in a cross-app promotion deal if my app is smaller
If your app is smaller than the partner's, the deal needs to compensate with quality or creativity rather than volume. Options include: offering a more prominent placement (homepage vs. settings screen), adding multiple touchpoints (in-app card plus email mention) to match the partner's single high-traffic placement, or proposing a joint content collaboration (co-authored blog post, shared email campaign, or mutual social post) that extends reach beyond what either party can offer unilaterally. Be transparent about your MAU — partners who discover the size gap after the deal is signed are unlikely to extend it.
how long should a cross-app promotion deal run before reviewing results
30 days is enough for the initial trial if both parties have consistent weekly traffic. That gives you time to see install volume stabilize, collect Day-7 retention data, and compare results before committing to a longer or deeper arrangement. Avoid open-ended deals without a review checkpoint — seasonal audience shifts and partner roadmap changes can make a deal that converts well in one quarter underperform in the next. Build a 30-day and 90-day review into the agreement from the start.