Password Gates & Link Expiration¶
Ruby provides link protection and lifecycle controls to safeguard confidential content, manage embargoed assets, and automatically retire time-limited marketing campaigns.
Password Protection¶
Password protection intercepts visitors with an on-brand gate screen before they can access the final destination URL. This is ideal for confidential client deliverables, private product betas, or embargoed press releases.
How the Password Gate Works¶
- Gate Page Interception: When a visitor clicks a password-protected link, Ruby routes them to an on-brand passcode entry screen (
/gate/{short_code}). - Passcode Validation: The visitor enters the configured password. Passwords are securely hashed and validated.
- Stateless Clearance Session: Upon successful entry, Ruby issues a temporary clearance session cookie valid for 1 hour. The visitor is seamlessly redirected to the destination URL and can navigate back and forth without having to re-enter the password on every click.
- Brute-Force Rate Limiting: To prevent automated passcode guessing, Ruby enforces an automated rate limit of 5 failed attempts per IP address within a rolling 15-minute window. Once exceeded, further attempts are temporarily blocked.
- Crawler Privacy: When social platforms or crawlers inspect a password-protected link, Ruby serves safe preview metadata without revealing the confidential destination URL.
Setting or Removing Passwords¶
- Enabling Protection: When creating or editing a link, expand the Security & Protection section and enter your desired password.
- Removing Protection: To remove the gate, edit the link and select Remove password (or pass
remove_password: truevia the API). The link immediately reverts to open redirection.
Scheduled Link Expiration¶
For flash sales, seasonal discounts, webinars, or embargoed announcements, you can schedule an exact date and time for the link to expire.
Expiration Behavior¶
- Active State: Prior to the expiration date and time (configured in UTC), incoming traffic redirects normally to your primary destination and device targets.
- Expired State: Once the expiration timestamp is reached, incoming traffic is automatically intercepted:
- With Fallback URL: If you configured a Fallback URL (e.g.
https://example.com/offer-expiredor your homepage), visitors are redirected there with an HTTP 302 status. - Without Fallback URL: If no fallback URL is specified, Ruby displays a branded notice indicating that the link is no longer active.
- With Fallback URL: If you configured a Fallback URL (e.g.
Always Configure a Fallback URL
Setting a fallback URL ensures that late visitors never encounter a broken page or dead end, preserving brand reputation and redirecting lingering traffic to an active promotion or homepage.
Manually Pausing Links¶
If you need to halt traffic immediately without deleting the link:
- Open the link in the web application.
- Toggle the Active switch to disabled.
- Save changes.
Traffic will instantly redirect to your fallback URL or the inactive page. You can reactivate the link at any time to resume traffic flow, with all historical clickstream data and settings preserved.