Black Friday
Skip to documentation content

Hotel Setup

Configure newsletter subscriptions with double opt-in

Free's Newsletter feature records email subscription requests and verifies ownership through double opt-in. It is subscription management, not a campaign builder or a promise that marketing messages will be sent automatically.

Free’s Newsletter feature records email subscription requests and verifies ownership through double opt-in. It is subscription management, not a campaign builder or a promise that marketing messages will be sent automatically.

Enable the compact form

Open Hotel Booking → Newsletter & Contact with communication-settings permission, enable new email subscription requests and save. Check readiness and place [kimorapro_hb_subscribe] on the intended published Page or supported theme surface.

The compact form contains email + Subscribe. It has no privacy checkbox, hidden consent or Privacy Policy URL requirement. Do not copy Contact’s readiness requirements into Newsletter configuration. The hotel still supplies its own appropriate privacy information through its site policies.

Verify the complete lifecycle

  1. Use a synthetic email and a mail sink in an isolated environment.
  2. Submit the form once. The neutral result means the request was accepted; it does not disclose whether the address was known or prove it is subscribed.
  3. Locate the confirmation message in the sink. Opening its link displays a landing page; GET alone does not confirm the subscription.
  4. Submit the landing page’s confirmation action and verify the subscriber becomes Subscribed.
  5. Open the unsubscribe link and explicitly submit that landing action. GET alone does not opt the address out.

The default confirmation lifetime is 48 hours. Resend has cooldown/quota checks; a resend does not reset the pending record’s original retention age. An unsubscribed address needs a fresh confirmation to subscribe again. Turning new intake off does not invalidate every already-issued confirm/unsubscribe workflow.

Separate request, confirmation and delivery

WordPress mail acceptance or a local sink capture is not Internet inbox delivery. Check the actual transport, spam handling and relevant server logs separately. Do not mark an address Subscribed by editing storage when the confirmation message is missing.

JavaScript may use the supported JSON response extension; native POST remains the fallback. A request-received response is still neutral. Prevent simultaneous submissions and avoid automatic retries after an uncertain response. Expired, invalid or wrong-purpose links must not mutate subscription state.

Manage data safely

Use the Newsletter administration screen with its dedicated permissions. Subscriber management and CSV export are separate privileges. Pending and unsubscribed records have configurable cleanup periods; Subscribed records do not expire automatically under that policy. Exported files and previously sent messages need separate handling.

See communication data and retention.

Was this article helpful?

Your feedback helps us improve the documentation.