There’s another SocialSpark release today (it must be Tuesday)! Here’s what’s coming your way this afternoon:
New This Week
- Instant notification of qualified Opportunities. Bloggers who meet segmentation requirements for any new Opportunity will receive an email about the Opp letting them know that they are qualified as soon as it launches. This does not guarantee the blogger a slot in the Opportunity. Users can disable these emails by unchecking the ‘System Alerts and Feature Updates’ setting in their message center email preferences.
- Notification of CPC Opps with empty budgets. CPC Opportunities that have run out of money are handled more gracefully now. Bloggers will see that the opp has ended and will no longer be able to get the code for banners and links. They will still be able to see a summary of how they performed while the campaign was running, and if the advertiser refills the budget they will be able to continue getting conversion payments.
- Advertiser view of CPC Participants’ top referrers. Advertisers can now see the top 10 referrers for each participant in their CPC program. They’ll be able to use this information to ban users who try to abuse the system from their Opportunity.
Top referrers displayed under participant info
Fixed This Week
- Updated: When bloggers tried to add a blog, SocialSpark would crash if it could not communicate with the IZEARanks server. This is working again, so if you experienced this issue please try again!
- There was a bug with Auto Payout that was causing posts that were rejected because the site was unreachable to look the same as posts that cannot be paid out for some other reason, making it difficult for our Customer Love folks to give accurate answers as to why a post was not paid out. This has been fixed.
- In IE7, we fixed a bug that prevented users from leaving feedback on Opportunities.
- Cleaned up some of the affiliates code that was causing crashes when the databases were out of sync with one another.
- Special characters in Opportunities occasionally caused a crash on Opp approval; this is no longer an issue.
