Expand your list distribution and sell data on other people's ListKey sites.
Data Share Owner to Owner
Who it's for
With Data Share Owner to Owner, ListKey Owners can easily share and expand their data distribution via the ListKey Owners Network of sites.
What to consider
When you join the ListKey network and enable a file(s) that you compile, manage or own, you gain access to the entire Alvion ListKey owner network.
With this network, you can create new partnership opportunities to distribute your data with other ListKey owners and vice versa. Because your data and the other ListKey site owners have already enabled your data with ListKey, you can create relationships similar to "licensing" without either side having the expense and labor of cutting, processing and maintaining files and their updates.
Assess your needs
Data Share Sponsorship
Who it's for
With Sponsorship, a ListKey Owner using the Storefront functionality can share-by privately labeling or co-branding its site-the data and the functionality with a company who currently does not have a ListKey system.
What to consider
This product is designed for companies who already have a license for data from the ListKey Owner but would rather store and access the data via the Internet in an ecommerce environment for themselves and their own customers.
This product is also designed for ListKey Owners who wish to co-brand and privately brand their site to customers who currently do not license data from them.
For ListKey owners, you can save internal resources in cutting files to licensees. Since your file is already accessible via the web, you can license it through your ListKey site. And you can package and re-sell Web site and ecommerce capabilities for data distribution with your data licenses, giving potential licenses more of an incentive to license your data.
Customers who wish to partner with a ListKey owner get a "child" version of the original ListKey "parent" site.
The child site has the Storefront functionality for the user interface but also includes-on the back end-the professional interface-for the child site's internal users who may want to run more complex queries.
A child site can be a "co-brand" of the site, and the ecommerce functionality-the actual financial transaction-stays on the parent site and the parent site is responsible for the customer support and the ecommerce transaction. Or a child site can be its own private label site where it has the ecommerce financial transaction and all of the customer support responsibilities.
Assess your needs