1. I've enabled the test date for the 1st of December, but I still can’t open/scratch any of my fields?
Have you looked into the date settings for all of your fields? Maybe they aren’t set to the correct year or date, which is why your test date doesn’t enable the possibility of opening/scratching any of them. You can find and modify these here:
2. I would like to run and test the game for a specific date or period. Is that possible? Or do I have to wait for the actual date or period to test it?
That is possible indeed! You can enable a test date either through the backend or within the builder. You can find it here:
We have more information about the test date function in the following article: here.
3. Is it possible to redirect to another game outside of the calendar when opening/scratching a field?
Yes! You can redirect to another Playable game by using the "go to campaign" action in the calendar field settings.
4. I’ve seen another calendar with falling snow throughout the entire campaign. Can I add that as well? And is it possible only to have it on my winner page?
Of course! This is done through our particle generator. You can find it under “Misc.” within our integrations:
If you only want it to show on your winner page, you should just choose this from the dropdown:
We have more information on our particle generator in the following article: article.
5. Is there a way to showcase the prizes for each date in my calendar? To keep the audience motivated to return each day?
Yes! This can be done through our prize-addon. It’s up to your where and how you want to display it. We recommend doing it through a popover. Here is an example of how it’s done:
You can add an extra popover, find the addon under “add new block” and edit the settings for how the prizes should appear:
We have more information in the following article with an overview of settings for the prizes: here.
6. Do you have any recommendations for the assets needed in order to set up the calendar? I see a possibility of different ways to set up the calendar doors.
For sure we do! You can see recommendations for each possibility within our design guide article right here.
7. Is it possible to show the entire calendar on mobile? Right now I can only see one door.
Absolutely! Check out our article on how to create a multi-door calendar on mobile here.
If you like the one-door view and would like the same for desktop, this is also possible. We have a guide for this in the following article here.
8. Which template should I go for with my calendar?
This depends on your thoughts behind it. Do you want a calendar for all 24 days in December? +24 days in another month or only the dates for advent? In need of inspiration? We’ve got you covered with examples of both 24 doors and 4 doors right here.
9. I want to go live with my calendar, but I'm not sure if I'm missing anything. Will you help me go through it?
We’ve got you covered. We already have a checklist which you can run through in order to ensure that your calendar is ready to publish. Please note that it is your own responsibility that the calendar flow is as intended. We recommend that you test it thoroughly before publishing.
You can find the checklist right here.
10. Each and every day I redirect to a new game from my calendar, but the participants would have to fill out two registration forms. The first one on the calendar and the second one on the game for the specific day. Is there any way to avoid this and still receive data?
There is indeed! You can set up the autosubmit function for the second reg. Form (on the game that is redirected to) to ensure that participants don’t have to fill out the same details over and over again. You can also set this for the first reg. Form (on the calendar), so they only have to fill it out once, as their browser cookies save their previously typed information. We have an article for that right here.
Please note that from game to game, the registration forms should be 100% identical to one another. This is to ensure that the browser cookies can identify the fields and insert previously stated information.