Useful plugin for setting up a pre-launch site.
| Author: | Raft Co (profile at wordpress.org) |
| WordPress version required: | 4.0 |
| WordPress version tested: | 4.0.1 |
| Plugin version: | 1.0.1 |
| Added to WordPress repository: | 21-12-2014 |
| Last updated: | 21-12-2014
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
|
| Rating, %: | 86 |
| Rated by: | 3 |
| Plugin URI: | http://wordpress.org/extend/plugins/wp-prelau... |
| Total downloads: | 405 |
 Click to start download |
|
Based on Harry's Prelaunchr and discussed in greater detail on Tim Ferriss' blog Prelaunchr for WordPress helps you quickly start a pre-launch campaign for new companies, products and services.
Campaigns are conducive to social sharing and rewards / prize groups can be set based on the number of people each person refers. The groups, amounts, and rewards are completely up to you to set.
Manually add a shortcode [prelaunchr] to any page or post to insert the prelaunchr email sign up form.
At the end of the campaign export your results to csv for importing into your desired marketing/sales platform such as MailChimp, Campaign Monitor or Salesforce.
Features
- Referral tracking
- Set and manage referral rewards / prizes
- View submissions within the WP dashboard
- Export submission to CSV
- Anti Spam honeypot field
- Akismet Integration
- Developer Friendly
- Theme integration - with templates that can be overridden
Contributing and reporting bugs
You can contribute code to this plugin via GitHub: https://github.com/raftco/wp-prelaunchr
Contributions like translations/localizations are extremely grateful.
Support
Use the WordPress.org forums for community support (note we do not personally monitor these forums).
We cannot offer support directly for free but if you'd like paid support or to provide a donation we can work something out.
If you spot a bug or want to contribute some code, you can of course log it on Github instead where we can act upon it more efficiently.
If you want help with a customisation, please hire a developer!