📝 The Squeeze Page And What Gets Injected

The squeeze page is the funnel's front door. What the visitor sees is the shipped page file, or a bundled template if you chose one, with a series of injections layered on top.

What happens on every squeeze page load:

1. The plugin confirms the funnel exists, is enabled and is unlocked by your licence.
2. It records a page view in the aggregate statistics table.
3. It records a detailed view row with the visitor IP and user agent, unless the request looks like a bot or you have chosen to exclude logged in administrators.
4. It loads the page HTML, from the template if the funnel has a template override, otherwise from index.html.
5. It runs the injections below and sends the result with no cache headers.

The injections, in order:

• Placeholder URLs in the shipped page are rewritten to your real funnel URL
• The cover image is repointed at the uploads folder so it resolves regardless of trailing slashes
• The opt-in form for the funnel's autoresponder is injected in place of the default form
• Your custom headline replaces the first h1, and your background colour or background image is added as inline CSS
• Open Graph and Twitter Card tags are added, using the funnel's share image at 1200 by 630 when that file exists
• The exit intent script and the urgency timer bar are added, unless they are switched off
• The progress bar is inserted just above the opt-in form
• Legal page links are rewritten to the funnel's virtual URLs
• The PDF link is rewritten to the plugin's pdf.php handler
• Your Google Analytics tag and any custom tracking codes are added, in the head or the body as you chose

The opt-in form itself:

For API connected providers the plugin builds its own AJAX form. It posts the email, the optional first name and a security nonce to WordPress, subscribes the visitor server side, and redirects to the download page. The form includes a hidden honeypot field. If a bot fills it in, the submission is quietly accepted and discarded, so your list stays clean without a CAPTCHA.

For the direct post providers, meaning AWeber Legacy, GetResponse Campaign Token, Sendiio and a pasted custom HTML form, the visitor's browser posts straight to the provider and returns to your download page.

What happens when the provider call fails?

The lead is still written to your local database, marked as not subscribed, and the failure is written to the debug log. The visitor still reaches their download. A provider outage costs you the sync, not the lead and not the visitor experience.