Shopify App Marketing Beyond the App Store Listing

Shopify app marketing usually means App Store optimisation: listing copy, category keywords, screenshots, review volume, and paid placement if the budget allows. It works, and it is demand capture. It reaches merchants who are already searching your category. Every other store in your market never sees it.

The disclosure first. We build Keaz Signals, which sells ecommerce buying signals to the people doing the selling. Software companies selling into ecommerce are our own readership, so we have an interest in the argument this post makes. Better said at the top than left in a footer.

This is written for the app developer, not for the merchant. The question is not how a store should choose its apps. It is narrower, and harder: of the merchants you could theoretically reach, which ones have a reason this week to hear from you at all.

Every Shopify store is a total addressable market, not a list. A market you can work has to be small enough to write to individually and specific enough that the message is not generic. Runs Shopify fails both tests: it is true of everyone, so it sorts nobody.

The trade runs one way. A segment defined by a platform gives you volume and no relevance. A segment defined by a change gives you relevance and much less volume. The second is the workable one, because outbound is paid for per reply rather than per contact.

Some numbers from our own panel, dated because they move. As of September 2026 we watch 4.1 million Shopify and WooCommerce stores across Europe and North America, re-scraped weekly. Roughly 41,200 carry a fresh signal in any given seven-day window. That is about one per cent, and the one per cent is the product. The 4.1 million is only the panel it comes out of.

Turning that into something you can send to is the job of the ecommerce leads database, where a change plus your fit conditions becomes a segment with a live count against it.

A change is worth acting on when it leaves unfinished work inside the store: money already committed, a decision already taken, and someone internally now accountable for making it pay. That is the condition under which a merchant answers mail they did not ask for.

Four events on our list meet it. An email or marketing tool going in, where the setup is still at defaults and the flows are unbuilt. A storefront or site change, where the rebuild is live and its gaps are visible to anyone who looks. Meta ads going live, or the active ad count climbing, which means acquisition spend is committed and under review. And a product launch, a shift in newsletter rhythm, or social growth on Instagram or TikTok.

The first of those has a page of its own: stores that just installed an email tool. It is the clearest case because the budget line is new and the work it implies has barely started.

The test for your own app is the same every time, and it is not whether the store could use you. It is whether this particular event leaves a job your app does, which the merchant has started and not finished.

The strongest trigger for an app developer is a merchant installing a tool in your category. They have named the problem, paid for an answer, and are still at the defaults. It is also where we have to be precise about what we actually see, because the obvious reading of this post is more generous than the truth.

What we detect is email and marketing tools going in. Klaviyo, Brevo and their neighbours. We do not run a general detector across every app category, and a developer working in subscriptions, reviews, shipping or upsells should not read this as a promise that we can see their competitors' installs. We cannot, and no framing changes it.

A second distinction sits underneath, and it applies even where we do have coverage. A lookup tells you what is installed now; a signal tells you what changed and when. We wrote that out in a Shopify app detector shows state, not change.

So the honest version is narrower than the pitch. If your app sits next to email and retention, the category-install trigger is open to you. If it does not, you are working from storefront changes, launches and ad activity, which are weaker proxies for your problem.

Write from the event, not from the app. You run a Shopify store is a mail merge, and it reads like one. You put a retention tool in nine days ago and the flows are still the defaults is an observation about their week. Only the second earns a reply from someone who never asked to hear from you.

Three things follow operationally. You segment on the change plus your fit conditions, such as country, platform and follower count, rather than on the platform alone. You send while the event is still recent, which is the only honest reason to pay for freshness at all. And you write one message per event, because a second message with nothing new to say is a message about you.

Our sales agent drafts the per-store copy from the signal plus your own knowledge base, and campaigns run through Instantly in your own workspace, with status and replies syncing back. Sending through your own infrastructure rather than ours is a structural choice: the domain reputation you build stays yours. That is a statement about how the plumbing is arranged, not a claim about anyone else's.

We are not going to give you Shopify App Store install counts, category market shares, or a conversion rate from listing view to install. We have not measured any of them. The figures that circulate for them are not traceable to a method we can check, and a number we cannot stand behind is worth less to you than this sentence.

We are also not going to quote a reply rate for signal-led outreach, or tell you it beats App Store optimisation by some multiple. We have not run that comparison. Anyone who quotes you a number for it is quoting their own campaign in their own category, which tells you very little about yours.

What we will state, dated: as of September 2026 we watch 4.1 million Shopify and WooCommerce stores across Europe and North America, re-scraped weekly, with roughly 41,200 carrying a fresh signal in any seven-day window. Those numbers move, which is why they carry a date every time we use them.

One more we will not make: what you may lawfully send, and to whom. We are GDPR-conscious by design and we will not claim more than that. Responsibility for what you send stays with you, and that sentence is deliberately narrow.

If your app answers a need every store has from its first day, the listing is the better investment and outbound is an expensive way to reach the same people. Demand capture wins whenever the demand already exists and is already searching. We are not a substitute for the listing and would rather not be read as one.

Four limits, plainly. We cover Shopify and WooCommerce in Europe and North America and nothing else, so if your merchants are on BigCommerce or in Brazil we are the wrong tool. We detect email and marketing tools going in, not every app category. We do not export: leads move into campaigns and stay there, which is a dealbreaker for some teams and should be. And we have no LinkedIn signals and no LinkedIn sending, with no plans to add either.

If the event rather than the audience size is what you are missing, the buying signal catalogue is the honest list of what we watch, and pricing is what it costs. Signup includes 1,000 free leads, which is enough to find out whether the events we see are the ones your app answers.

• Keaz Signals buying signal catalogue — retrieved 28 September 2026
• Our own coverage: 4.1M Shopify and WooCommerce stores watched, roughly 41,200 with a fresh signal in seven days — as of September 2026
• Weekly re-scrape cadence and the shipped signal set — own product behaviour, September 2026
• Adjacent: state vs change · timing, not finding