Calendar go-live checklist

A list of settings to check before publishing your calendar

Andreas Grosen avatar
Written by Andreas Grosen
Updated over a week ago

A calendar campaign is more complex than a regular game campaign because of the fact that it usually has different content every day.

In addition to the pre-launch analysis under the Publishing tab, you can use this checklist to keep track of all the settings you should test before going live with your calendar.

Test all days’ content

  • Check the number of doors, the dates (including year!) of each field, and the alignment of the field active areas on the calendar graphic.

  • Send the Demo URL to a colleague to test the game flow. Test in multiple browsers (Chrome, Firefox, Safari, Edge). Test on both iOS and Android phones.

  • Use the test date in the frontend (Demo URL) to preview all days. Test the entire flow for at least two days (preferably all days).

  • Using the test date in the backend (Game Settings), set a test date and open the Demo URL on a mobile phone. Update the test date in the backend and test another day.

  • Test both the winner flow (correct answer) and loser flow (incorrect answer). Make sure your #message# tag is correct, if you are using it.

Registration (backend)

  • Check the registration limit (under the Campaign tab). If you removed the limit for testing, add it back.

  • Look under the Activity tab. Is all registration and game data being collected correctly?

  • Check the integration settings (if using). Is all registration data being successfully sent to your database?

  • Delete any test registrations and any game data statistics. (Before the campaign is published, registrations from the Demo URL will automatically be deleted after 2 days.)

Registration (frontend)

  • Does your campaign remember player data based on browser cookies? Should the registration form auto-submit (be hidden) if a player returns? Check these settings on your registration addon. If you removed auto-submit for testing, re-enable it.

  • Check to make sure your Terms & Conditions link works. Also on mobile.

Prizes (regular)

  • If using automatic draw, check all prizes to ensure they are associated with the correct dates. Check the draw time.

  • Test your winner email, either with the test function or by duplicating a prize and removing the date limitation so you can win it.

  • If using the prize addon or the daily prize display under Game Settings, use the frontend or backend test date to preview the prizes on different dates.

Prizes (bulk)

  • If your prizes are date-restricted, remove the date restriction for testing and implement it again before you go live.

  • If your prizes are time-based, check that all the prizes can be won in the correct time period.

  • Win a prize. Check to make sure your prize replacement tags work on the result page and the winner email.

  • If there is a consolation prize, or if people should be able to win more than one prize, remove the restriction on winning multiple prizes.

Links, In-Game Messages, Share Settings

  • Run the pre-launch analysis and set your campaign period. If you’ve already done this, double-check the start and end dates.

  • Update your default messages (campaign not active, no active fields, registration limit) under Advanced > Messages in the backend.

  • Check to make sure your Live URL is correct (under the Publishing tab). Edit as needed under Advanced > URL Alias or by setting up a custom subdomain in Global Settings.

  • If redirecting from a pre-launch campaign, check the date and URL of the redirect.

  • Check share settings with Facebook debugger and update meta tags under Publishing.

  • If using the Social Share addon, test each link. If the game will be iframed, use the Custom URL share.

  • Test all external links and CTAs. Also on a mobile device. If the game will be iframed, make sure the link target is correct (same window or top window, depending on what you are linking to). Make sure iframe doesn’t breakout is enabled on mobile.

Search terms: test date, test, check, kalender check, tjekliste, tjek

Did this answer your question?