Participant data & reporting

Agree the entry flow

Confirm which participant fields are necessary, whether sign-in is required, and what becomes public on a leaderboard or share card. The sample sign-in in a demo is not a real account and does not establish your production entry flow.

The public concepts save choices in the browser. They do not create customer accounts or submit real campaign entries.

Access, consent and retention

Before launch, document who receives and can access participant data, hosting arrangements, retention and deletion, privacy notices, and any export requirements. Agree the publisher’s and TablePredict’s responsibilities for the selected setup.

Any marketing consent must be clearly described and reviewed separately from entering the competition. Participation is not a promise that participant details can be used for any future marketing.

Do not send participant lists, passwords or API credentials through a public demo or a branding URL.

Reporting with clear definitions

Choose the measures you need: eligible entries, return visits, completed predictions, share actions or sponsor-link clicks. Agree how each measure is counted, what can actually be observed, access and reporting frequency.

Sample leaderboard rows and concept figures are not completed publisher campaign results. A page view is not an eligible entry, and a share-card download does not prove someone posted it.

Exports and participant messages

Reporting, exports and automated participant emails require agreed scope and a technical review. Define fields, recipients, purpose, delivery cadence and opt-out or consent requirements before enabling them.