Configuring a capture widget

When you've created a capture widget from a template or from scratch, you can edit its content, style and settings.

The content editing features are similar for most capture widgets, although there are differences for embeddable form, tracked form, and spin the wheel capture widgets.


Content

The content section will be similar for most capture widgets. To edit the content:

  1. After creating a capture widget from scratch or from a template, click Edit on the capture widget details page.
    The capture widget’s content editor page consists of numerous display components, such as Greeting and Thank you components, which contain the messages and controls to engage your visitors.
  2. Edit the Greeting or Thank you display components, each of which is made up of one or more content components:
    • Click on the content component to expand and collapse the content.
    • Click and hold the content component or its re-order icon to drag and drop them.
    • Click the trash can icon to delete the content component.
    • Click Add content to add from the available content components for the capture widget, default options include:
      • Text
      • Button
      • Form
      • Coupon
      • Image
      • Video
      • Reaction
      • Net promoter score (NPS)
      • Survey
      • Countdown.

    NOTE: The content components FormReaction, and Survey add a Thank you display component which provides feedback or coupons to the user after completing the capture widget.

    Adding and editing components (Click on the GIF to maximize it)
  3. Review the changes in the capture widget preview on the right-hand-side of the screen, which:
    • Shows changes made to the content component.
    • Allows you to switch between the preview for the greeting and thank you display components of the capture widget.

4. Edit the style to change the appearance of the capture widget.

TIP: Click the merge tag icon to add merge tags to text and links.

Example merge tag in a link

Attaching files to a button for download

To let users download files by clicking a button:

  1. Click on the Button component.
  2. Under On click, select Download file.
  3. Upload your file. Supported file types include JPEG, JPG, BMP, GIF, PNG, TIFF, TIF, PDF, CSV, DOC, DOCX, XLS, and XLSX.

TIP: This feature works with all buttons, whether they’re in a form or as standalone elements. To show a thank you message before allowing a download in a form, set the button inside the form to Go to the next step. Then, add the download button to the Thank You section.

Attaching a file to a button for download (Click on the GIF to maximize it)

NOTE: If the button is inside a form, users can only download the file after completing all required fields.


Style

Edit the style to adjust the appearance of the capture widget.

On the Edit capture page, click Style and use the various options provided to customize the appearance of the capture widget. A preview of the capture widget is provided on the right as you alter options on the left.


Settings

Configuring the capture widget enables you to specifically target where, when, and how the capture widget appears for your users.

Use the configuration components on the left hand navigation bar target the capture widget.

Widget display prioritization

Widget display prioritization is disabled by default, however, you can modify this in Settings > Channels > Capture widgets.





Once enabled, you can set the priority for each widget. This essentially queues the widget based on qualification and priority, to ensure users see the most relevant content at each interaction stage, without clutter.





If the lock icon is selected, the widget will always display when its trigger rules are met, regardless of other widgets and their priorities.

You can select another priority, with 1 representing the highest priority and 10 the lowest.

If there are other widgets with the same priority, we will show you a link allowing you to see those widgets so that you can manage the priority best.



On the Capture overview page, there will also be a column showing the priority set for each widget so that you have this information without having to open each widget individually:





NOTE: Journey widgets will always have priority over normal capture widgets (i.e. priority 10 of a Journey widget will be displayed before priority 1 of a normal capture widget).

NOTE: If two or more widgets have the same priority, we will randomly pick one of them to display first.

Learn more about Journey widgets.

Platforms and pages

In this section you can select the platforms you want to display the capture widget on, including web (desktop and mobile), and, where available, Android and iOS applications.

NOTE: Currently, only popup type capture widgets can be configured for mobile applications.

Once you’ve chosen the platforms to display the widget, you can specify the pages on which it appears. These options include:

  • Any page,
  • On any page, excluding specific pages, or
  • On specific pages only.

When you select to exclude or specify the pages to display the capture widget, an Add page link appears. Click this link to specify:

  • the exact URL (is) for the page which displays the capture widget,
  • the exact URL (is not) for the page which should not display the capture widget,
  • pages where the URL starts with a specific URL,
  • pages where the URL ends with a text string,
  • pages which contain (contains) a specific text string, or
  • pages which do not contain (does not contain) a specific text string.

IMPORTANT: If your website is a SPA (single-page application), please read about page exclusions in SPAs.

Recipients

In this section, set the rules determining who will see the capture widget.

People is used to target which people see the capture widget, based on the following options:

  • Everyone— All visitors to your web page will be shown the widget.
  • Contacts — These are visitors who are known people, such as those who have signed in to your web application or have an existing user session with it, and optionally meet the filter conditions for the capture widget to be displayed. These people are recognized as existing records in your CDP.
    Click Add condition to define a filter to further refine when the capture widget is displayed to people.
  • Anonymous users — These are visitors who are unknown, such as people who have not yet signed in to the web application or do not have an identifiable user session with it. These people may or may not (yet) exist in your Ortto account’s customer data platform (CDP).

Location is used to present the capture widget to users based on their geographical location, which includes the following options:

  • Anywhere,
  • Anywhere, excluding specific countries,
  • Specific countries only, or
  • Within proximity of city.

Trigger

In this section, set the rules determining when visitors will see the capture widget.

Show the widget is used to choose when the capture widget will be displayed, and includes the following options:

  • When page loads.
  • When an element is clicked — The link or button is embedded on the web or mobile app page specifically to open the capture widget using an ID, or class. This could be located within any element of the web or mobile app page.
    The link ID is specified as #<id>, or the class is specified as .<class> in the configuration box.
  • Based on rules — Set display conditions to determine when the widget will be shown. You can choose to have the widget show when any or all conditions are met.
    At Display conditions, you can set a custom amount of seconds spent on the page (up to 120 seconds), or choose from the available options for percentage scrolled and number of pages visited.

At Widget can show, select the frequency at which the widget is shown to a visitor.

NOTE: For the Once per session option, a user's session is considered ended when:

  • They close the web browser. Apple Mac users must also "Quit" the browser in order to clear the session cookie — simply closing the browser will not end the session.
  • Cookies are cleared.

Until one of these actions has occurred, a user's session will continue, and they will not see the widget again until after the current session has ended. If the user opens the page hosting the widget in a different browser or device, it will be counted as a separate session.

Stop showing the widget is used to configure one or more options when the widget will no longer be shown to the visitor. The options are:

  • When they convert.
  • When they dismiss it — When the user clicks the X on the widget.
  • After an expiration date — This setting is handy for widgets relating to time-sensitive information, such as promoting an event or sale.
    After the specified time, the widget will be turned off.

Attribution

Attribution shows which capture widgets are most effective at driving conversions. In this section, set the activity which will count as conversions for the widget.





Navigate to Settings - Attribution to set the touch trigger for capture widgets. By default, the touch trigger will be set to Shown, but can be changed to Engaged:



  • Shown — A touch will be counted when the capture widget is shown to a contact.
  • Engaged — A touch will only be counted when a contact engages with the capture widget. They can engage in various ways such as watching a video, clicking a button, or submitting a form within the capture widget.

Learn more about Attribution and Touch Triggers.

Page exclusions in SPAs (single-page applications)

If you are using a single-page application (SPA), you may encounter an issue where certain widgets, meant to be excluded from specific pages, remain visible when navigating to those excluded pages. If a widget appears on one page and the visitor navigates to an excluded page before dismissing the widget, it will continue to display even though it should not.

To address this, we have implemented a JavaScript command: ap3c._generalWidget.hideAllWidgets()

By calling this command when the user changes pages within the SPA, all widgets will be closed. The relevant widgets will then reload on the new page, ensuring that any page exclusions are properly applied.