Free Rotator Script guide

Admin Guide

Admin manages destinations, optional 468×60 banners, leads, reports, backups, and installed MODs. Use the Guides button in the Admin header to read every included instruction and the license as a styled web page. The Launch Path recognizes secured configuration, active destinations, 20/10 weights, banner completion or skip, preview readiness, confirmed leads, and backup reminders.

Banners

Banners are optional 468×60 image ads shown in the rotator bar. Use clear alt text and a safe destination URL. If your first campaign does not need one, click Intentionally skip banner in the Launch Path.

Preview and public paths

Use View Rotator or visit /demo/ to test the weighted destination experience. The canonical lead page is /; landing.php exists only as a permanent compatibility redirect.

Lead handoff boundary

The free core collects double-opt-in leads, records consent, supports unsubscribe/suppression, and exports confirmed leads. It intentionally contains no campaign manager, broadcasts, sequences, or scheduling. Use a delivery provider after export, or install the optional Email Campaign Manager MOD when you want those capabilities on your own server.

MOD Manager

The customer MOD Manager is part of the public release; Home Base marketplace administration is not. To use it:

  1. Create a short connection code from your account at https://freerotatorscript.com/mods/account.php.
  2. Enter it in Admin’s MOD Manager over HTTPS.
  3. Refresh the Home Base verification key and entitlements.
  4. Claim or purchase a MOD, then download, install, and activate a compatible signed version.
  5. Read the MOD’s settings and documentation before enabling it on public forms.

Current product paths include Traffic Analytics, Email Campaign Manager, Funnel Maker, and the free Pro Captcha MOD. Dependencies are enforced before installation. Deactivation keeps the free core working; uninstall should offer data retention where the MOD stores customer data.

Backups

Download a core Admin backup before changes. For a complete server backup, also preserve config.php, all of storage/, uploads/, keys/, and mods/. MOD databases commonly live under storage/mods/ and are not necessarily represented in the core JSON backup.