Continue reading Stack3d

Stack3d Rewards rules loosened and redemption process streamlined significantly

Stack3d Rewards Live Update

We recently made our all-new, fan-supporting, and rewarding Stack3d Rewards program live over at stack3d.com/rewards. It is a system that lets loyal fans sign up via email, log in on multiple devices, and earn a points for visiting our newsfeed and staying informed on all of the latest in the supplement, functional food, and beverage industries. Each day you return and check out the updates posted on Stack3d, you’ll get a point, and those points accumulate over time.

Where the rewards part of Stack3d Rewards comes in is you can eventually redeem those hard-earned points for prizes, supplements prizes, of course. We said we would make a few tweaks as the program was put to use after going live on the first of the month, and here we are doing precisely that. One of the strictest rules we had since the start was that reward points would reset if you didn’t visit the website every day, so if you returned after skipping a day, you’d be back to zero.

We have decided to roll back the reset rule, and basically, every time you visit the website and catch up on all of the action in the industry, you’ll get a point, whether that’s every day or every second day; it’ll be a point a day you stop by. We’ve also made it much more efficient to redeem your points rather than wait until the end of the month and email all of the participants; once you’ve got 30 points or more, a redemption form will appear on stack3d.com/rewards to submit.

Basically, with the new form method, you can redeem your Stack3d Rewards points whenever you want. All of this is intended to make the program easier to use and more enjoyable, especially the loosening of the points earned. We did hit the first-round limit we set hours after opening the program, so it isn’t currently accepting anymore. However, we are going to be adding more spaces as the weeks and months go by, so keep an eye out on social media for news in that department.

In this post: