Skip to main content
Version: Isle Royale (2.5.0)

Display Methods

The display method controls how terms are presented to users and what actions they must perform to agree to the terms. This setting is configured through the displayMethod option when setting up display options.

Overview​

ToughClicks offers four distinct display methods, each designed for different use cases and user experience requirements. The display method you choose affects:

  • How documents are presented to users
  • What interaction is required for acceptance
  • The level of granularity in tracking user agreements

Available Display Methods​

Scroll​

The scroll display method shows the full terms of each document in a discrete scrollable container, with a checkbox for each document. The checkbox remains disabled until the user scrolls to the bottom of the terms, ensuring users have the opportunity to review the complete content before accepting.

When to use:

  • You want to ensure users have scrolled through the entire document
  • You need to display lengthy terms and conditions
  • You want to provide the full text inline without requiring external navigation

User experience:

  • Each document appears in its own scrollable container
  • Checkboxes are disabled until scrolling reaches the bottom
  • Helper text indicates "Scroll to the bottom of the document to accept"
  • Each document requires individual acceptance

Example:

const options = {
containerId: 'tc-container',
displayMethod: 'Scroll',
signerIdSelector: 'email-input'
};

tc.setDisplayOptions(options);

Individual​

The individual display method shows a checkbox for each document in your packet. Users must check all boxes to create the acceptance, with each checkbox click representing a discrete agreement to that specific document's terms.

When to use:

  • You need granular tracking of individual document acceptances
  • Different documents may require separate consent
  • You want users to explicitly acknowledge each document

User experience:

  • One checkbox per document
  • Each checkbox must be checked individually
  • Documents are referenced by title with links to view full terms
  • Clear indication of which documents require acceptance

Example:

const options = {
containerId: 'tc-container',
displayMethod: 'Individual',
signerIdSelector: 'email-input'
};

tc.setDisplayOptions(options);

Group​

The group display method shows a single checkbox for the entire packet. Users check one box to signal their agreement to all documents at the same time, streamlining the acceptance process for multiple related documents.

When to use:

  • Multiple documents should be accepted together
  • You want to minimize user friction in the acceptance process
  • Documents are closely related and typically accepted as a set

User experience:

  • Single checkbox for all documents in the packet
  • One click accepts all terms simultaneously
  • Document titles listed together
  • Simplified, streamlined acceptance flow

Example:

const options = {
containerId: 'tc-container',
displayMethod: 'Group',
signerIdSelector: 'email-input'
};

tc.setDisplayOptions(options);

Button Assent​

The button assent display method shows a conspicuous notice and no checkbox. The visitor agrees by clicking a button you already have on the page — your Complete Booking, Place Order, or Sign Up control — and the notice names that button so the click is an unambiguous act of agreement.

This is the pattern sometimes called sign-in wrap or modified clickwrap. It is not browsewrap, where terms sit behind a link with no action tied to them; browsewrap is routinely held unenforceable.

When to use:

  • Every extra click measurably costs you completed transactions, such as at checkout
  • You already have a prominent submit button the visitor must press to proceed
  • You can place the notice directly beside that button

When not to use:

  • The agreement is high-stakes enough that you want the record a checkbox produces
  • You cannot control where the notice sits on the page
  • Regulation or your own counsel requires an affirmative, separate act of acceptance

User experience:

  • A single line of notice text with the document names as links
  • No checkbox, no helper text, nothing else to click
  • The packet becomes valid as soon as it renders and a signer identifier is set, so your submit button is never disabled waiting for a tick

Required option: assentActionLabel must match your button's label exactly. Without it the SDK reports a validation error rather than rendering a sentence with no verb.

Example:

const options = {
containerId: 'tc-container',
displayMethod: 'buttonAssent',
assentActionLabel: 'Complete Booking',
assentActionSelector: '#checkout-submit', // optional, strongly recommended
signerIdSelector: 'email-input'
};

tc.setDisplayOptions(options);

Renders as:

By clicking Complete Booking you agree to our Booking & Cancellation Agreement.

optional: true is rejected in this mode. With no checkbox there is nothing for a visitor to leave unticked, so an optional packet would silently become required.

Placement is your responsibility​

The enforceability of button assent rests on the notice being conspicuous and immediately adjacent to the action. The SDK renders the notice into the container you name; it cannot know where on the page that container sits, and it cannot enforce good placement. That part is yours.

To keep the record as strong as it can be:

  • Put the notice directly above or beside the submit button, with nothing between them
  • Keep it visible at the point of submission, not above the fold or in a scrolled-away region
  • Do not hide it behind a disclosure, accordion, or tooltip
  • Do not shrink it below your page's body text size or reduce its contrast
  • Keep assentActionLabel matching the button label exactly, including capitalization

What gets recorded​

Because the record cannot rest on a checkbox, the SDK captures more at acceptance time and stores it on the agreement. This is what an acceptance certificate needs in order to be worth as much as a clickwrap certificate:

CapturedWhy it matters
The notice text, read verbatim from the pageWhat the visitor actually saw, which can differ from the template when using dynamic contracts
The button label as renderedShows which control was pressed
When the notice first appeared, and when acceptance was submittedMakes the interval between notice and click provable
Whether the notice was on screen, and for how longTurns "the notice was in the page" into "the notice was on the visitor's screen"
The notice's size and position, and the button's, when assentActionSelector is setEvidences conspicuousness and proximity
Whether the visitor opened a document to read itWorth a great deal in a dispute

Supplying assentActionSelector is optional but strongly recommended: without it the certificate can show that the notice was on screen, but not how close it was to the button the visitor pressed.

Choosing the Right Display Method​

Consider these factors when selecting a display method:

FactorScrollIndividualGroupButton Assent
User frictionHighestMediumLowLowest
Ensures content reviewYesNoNoNo
Granular trackingYesYesNoNo
Best for mobileMediumGoodBestBest
Legal clarityHighestHighMediumDepends on placement
Requires a visitor clickYesYesYesNo separate click

Code vs Management Portal​

You can set the display method in two ways:

  1. In code (recommended for production): Set the displayMethod in your display options
  2. In the Management Portal: Configure the default display method for a packet

Important: Any settings configured in your code will take precedence over settings in the Management Portal. This ensures there are no unintended consequences from configuration changes in the web app.

Combining with Other Options​

The display method works seamlessly with other display options:

const options = {
containerId: 'tc-container',
displayMethod: 'Scroll',
signerIdSelector: 'email-input',
shouldOpenModal: true, // Open terms in modal
manualAcceptance: false // Automatic acceptance
};

tc.setDisplayOptions(options);

Next Steps​