Using customer data to grow a plugin business
-
Hey Gang,
Just wanted to drop in with a post I thought some might find useful.
When someone buys and uses a plugin, useful information is created across the store, licensing system, email platform, and the plugin itself.
Connecting that information makes marketing & servicing much more useful. Instead of sending the same emails to everyone, developers can create:
- Marketing emails: Send product announcements, educational content, updates, and offers to the appropriate customers.
- Growth flows: Automate cart recovery, post-purchase follow-ups, review requests, customer rewards, upgrade campaigns, and re-engagement emails.
- Segmentation: Group customers by products owned, purchase history, license status, activation activity, installed version, or engagement.
- Personalization: Adjust email content and offers based on what each customer owns and how they interact with the product.
- Cross-selling: Recommend compatible expansions, sound packs, or related plugins while excluding customers who already own them.
- Customer retention: Identify inactive customers and send relevant education, updates, or incentives to bring them back.
- Product updates: Notify only the customers affected by a release, compatibility change, or important fix.
- Analytics: Connect campaigns to purchases, activations, product use, reviews, and repeat sales instead of measuring email clicks alone.
This is especially useful for smaller plugin companies because these tasks can run automatically instead of requiring someone to manually manage lists and customer records.
It is not about collecting every possible piece of information. It is about making the information you already have useful. Purchase, license, activation, and product data can help make emails & servicing more relevant and show what is actually helping the business grow.
This is one of the larger ideas behind SoundSync. We are connecting the store, customer accounts, licensing, plugin activity, marketing emails, growth flows, and analytics so developers can manage the customer journey from one connected system.
-
@soundsync What kind of product usage data does Soundsync collect from the end user?
-
@dannytaurus SoundSync can currently receive information related to the product’s operation and the customer journey, including:
- When the plugin is opened or connects to SoundSync
- Activation, validation, restoration, and deactivation activity
- The installed plugin version
- The product and license associated with the activation
- A hashed installation/device identifier for managing activations
- Interactions with SoundSync-provided areas such as activation, account, store, support, and update interfaces
- Timestamps showing recent validation or connection activity
This can be combined with information already created elsewhere in SoundSync, such as purchases, products owned, downloads, customer accounts, support activity, email engagement, and marketing consent.
That makes practical things possible. For example, a developer could notify customers using an outdated version, help somebody who purchased but never activated, exclude existing owners from a promotion, or create a re-engagement flow based on meaningful customer activity, cart recovery, etc, etc.
SoundSync does not inspect or collect the customer’s audio, MIDI, presets, parameter changes, DAW projects, filenames, or what they are creating. We are interested in product lifecycle events that help with licensing, updates, support, and relevant communication, not the customer’s creative activity.
We also try to keep the principle fairly simple, collect the minimum information needed for the feature, be clear about how it is used, and give developers the controls they need to handle consent and privacy properly.
Some of this varies by integration. For example, the HISE package can report plugin-open and SoundSync interface events, while licensing integrations naturally generate activation and validation events whenever they communicate with SoundSync.