Skip to main content

How to Use Embedding Options for Forms: Triggers, Layouts, and Deactivation Settings

Introduction​

Embedding Options for Forms in Stack give you enhanced control over how and when your forms appear on your website or funnel. This feature allows you to dynamically manage form behavior with advanced options for triggering and deactivating forms based on specific conditions. Remember, once you place an embed code on your site, it's static. Any updates to the form's layout, triggers, or deactivation settings require generating a new embed code and replacing the old one to reflect these changes. These options are designed to help you align your forms with your goals, such as enhancing user experience, running time-sensitive campaigns, or effectively managing lead collection.

Use Cases​

Time-Limited Campaigns​

  • Deactivate forms after a specific number of displays: Enforce urgency or exclusivity, perfect for limited-time offers or seasonal promotions.

Lead Management​

  • Deactivate forms after a specific number of displays: Similar to time-limited campaigns, this approach can also be used to create a sense of urgency or exclusivity.

Step-by-Step Guide​

Step 1: Access the Integration Settings​

  • Navigate to the Form Integration Settings. After creating a form, click on the Integrate button to proceed.

Step 2: Choose an Embed Layout Type​

Select how your form will appear on your website or funnel. The options include:

  • Sticky Sidebar: The form stays visible on the left or right of the screen as the user scrolls. It can be minimized or maximized.
  • Polite Slide-In: The form slides in from the side of the screen, subtly catching the user's attention. It can be minimized to avoid disruption.
  • Popup: The form appears in a modal window overlaying the page content, grabbing immediate attention.
  • Inline: The form is embedded directly into the page content, maintaining a seamless user experience.

Step 3: Configure Trigger Options​

Decide when the form should appear:

  • Show on Scrolling [X]%: The form appears after the user scrolls a certain percentage of the page.
  • Show After [X] Seconds: The form appears after a specified delay.
  • Always Show: The form is always visible, independent of user interaction.

Step 4: Set Activation Options​

Define when the form should become active:

  • Activate on [X] Visit: Display the form only after the user has visited the page a set number of times.
  • Always Activated: Keep the form active at all times.

Step 5: Set Deactivation Options​

Decide when the form should stop being displayed:

  • Deactivate After Showing [X] Times: Stops displaying the form after it has been shown a specific number of times.
  • Deactivate Once Lead Is Collected: The form deactivates automatically once the user submits their information.
  • Never Deactivate: The form remains active and visible indefinitely.

Step 6: Copy and Embed the Form​

  • Click Copy Embed Code to get the HTML code for embedding the form into your website.
  • Paste this code into your website’s HTML where you want the form to appear.
  • Alternatively, click Copy Form Link to get a direct URL for the form. Use this link in emails, social media, or other platforms to give users access to the form.

FAQs​

  1. How do triggers and deactivation options work together?

    Triggers determine when the form appears (e.g., after a delay or scrolling). Deactivation options control when the form stops appearing (e.g., after a specific number of displays or after a lead is collected). Both can work simultaneously to create a dynamic user experience.

  2. Do I need to update existing embed codes for the new features to work?

    Yes, to use the new embed options (e.g., triggers, deactivation), you need to update the integration by generating a new embed code from the Integrate Form section and replacing the old code on your site.

  3. Can embedded forms work dynamically if I change my options?

    Embed codes are static once they are placed on a website. This means any changes made to the form require generating and replacing the embed code with the updated version for the changes to take effect.