> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/how-to-guides/product-finders/create-activations.md).

# Create Activations

In this article, you will find information on how to place your Product Finder on your website to allow your users to interact with it.

Once your Product Finder is ready, you need to decide how users will open it on your site.

Go to your Product Finder and open the **Activations** tab.

<figure><img src="https://1240120646-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M6BXLJuZMkdXQg6osAC%2Fuploads%2Fgit-blob-4df9470c1a29aa3bfb2b75bbe80d634659238076%2Fnew-activations-1.png?alt=media" alt=""><figcaption></figcaption></figure>

## Activations Tab

The Activations tab lists every activation of this finder. **URL Parameter** and **Javascript Snippet** are always listed. Every other activation is one you create.

Open the menu on an activation's row to **Edit**, **Enable** or **Disable**, **Duplicate**, or **Remove** it.

### Quick pick (which activation should I use?)

* Use **JavaScript Snippet** when you want a button or banner to open the Finder on the same page.
* Use **URL Parameter** when you want a shareable link (email, ads, QR, etc).
* Use **Ribbon Activation** when you want a persistent entry point across targeted pages.
* Use **Inline Rendering** when you want a dedicated Finder page embedded in your layout.
* Use **Homepage Banner**, **PLP Product Tile**, **PLP Filter Banner**, **PLP Static Banner**, **Notification**, or **Product Search Overlay** to promote the Finder in those places on your site.

For inspiration on where to place entry points, check [Activations: Best Practices](https://docs.crobox.com/how-to-guides/product-finders/activations-best-practices.md).

### Before you start

* The **Crobox snippet** must be installed on every page where users can open the Finder.
* The page must match the finder's [Targeting](#finder-targeting), if you set any.

## URL Parameter

Use a URL parameter when you want a direct link that opens the Finder by default.

Add the query parameter to the end of any URL on your website. When a user loads that URL, the Finder opens automatically.

#### How to get the parameter

In the Activations tab, click **URL Parameter**. A pop-up opens with the unique parameter for this Product Finder.

<figure><img src="https://1240120646-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M6BXLJuZMkdXQg6osAC%2Fuploads%2Fgit-blob-d018324628475a08f59cc3a71e04bbcf6532aa85%2Factivations-2.png?alt=media" alt=""><figcaption></figcaption></figure>

Example: **?running-shoe-finder=open**

#### Prerequisites

* The Crobox snippet is installed on the page.
* The page matches the finder's [Targeting](#finder-targeting), if you set any.

#### Suggested Use Case

* Use this when you drive traffic from outside your site.\
  Example: marketing email, paid ad, social post, QR code.

{% hint style="info" %}
Avoid URL parameters for internal navigation. Use a **JavaScript Snippet** instead to open the Finder without redirects.
{% endhint %}

## JavaScript Snippet

Use a JavaScript snippet when you want an on-page trigger (CTA, banner, link) that opens the Finder immediately.

This avoids redirects. Users can open the Finder on a PLP or PDP.

#### How to get the snippet

In the Activations tab, click **Javascript Snippet**. A pop-up opens with the unique snippet for this Product Finder.

Implement that snippet in the element that should open the Finder.

<figure><img src="https://1240120646-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M6BXLJuZMkdXQg6osAC%2Fuploads%2Fgit-blob-3b095749fd1824e47a5244c62fdaa79ca35c7d5f%2Factivations-3.png?alt=media" alt=""><figcaption></figcaption></figure>

#### Prerequisites

* The Crobox snippet is installed on the page.
* The page matches the finder's [Targeting](#finder-targeting), if you set any.

#### Suggested Use Case

* Use this for banners, buttons, and other on-page elements.\
  Example: “Find your perfect product” CTA on PLP or PDP.

## Create an activation

Every other activation is set up like a campaign, in three steps.

{% stepper %}
{% step %}

### Choose the activation type

Click **Create activation** and select a type:

* **Ribbon Activation:** A ribbon on the side of your website.
* **Inline Rendering:** A dedicated page for the Finder.
* **Homepage Banner:** A homepage section or hero banner.
* **PLP Product Tile:** A product tile on a product listing page.
* **Notification:** A notification based on visitor behavior.
* **PLP Filter Banner:** A banner for visitors using the filter menu.
* **PLP Static Banner:** A static banner on the product listing page.
* **Product Search Overlay:** An overlay that opens from your site search.
  {% endstep %}

{% step %}

### General

Name the activation in **Activation Name**. Set how it looks in the settings next to the **Preview**. The settings depend on the activation type.
{% endstep %}

{% step %}

### Targeting

Choose which visitors see the activation, with the same filters as [campaign targeting](https://docs.crobox.com/how-to-guides/dynamic-messaging/advanced-targeting-filters.md).

Under **Locations**, select the page types and the placeholder the activation shows in. To add or change placeholders, go to **Settings → Website integration → Placeholders**.
{% endstep %}

{% step %}

### Content

Add the activation's message and its translations, as in a campaign's **Content** tab. Then click **Save**.
{% endstep %}
{% endstepper %}

## Activation Ribbon

The Activation Ribbon is a persistent tab on the right side of the page. Users can open the Finder without leaving the current page.

To create one, click **Create activation** → **Ribbon Activation**. Set its look on the **General** step, and where it shows on the **Targeting** step.

#### Customization options

#### Ribbon Text

* Text Color (hex code)
* Font Size (rem or px, default is 14px)
* Font Family
* Font weight

#### Ribbon Image

You can add an icon within the tab/ribbon, which will show before the text, as shown in the screenshot below.

<figure><img src="https://1240120646-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M6BXLJuZMkdXQg6osAC%2Fuploads%2Fgit-blob-3dd0d02c6bb1aeff77a06fab123d3f714134b380%2Factivations-5.png?alt=media" alt=""><figcaption></figcaption></figure>

* Image: Upload a .svg (recommended) or .png
* Image Padding: Select how much space will be around the icon.
* Image Size: Select the size the icon will be displayed in (the value can be in px, rem, or % size of the image).

#### Ribbon Style

* Background color: Select the color of the tab (hex code).
* Border radius: How rounded the tab is (default value is 5px).
* Padding: This affects the spacing around the text and image.
* Z-index: Controls layering vs other elements on your site

#### Ribbon Animations

* Wobble after 5 seconds: Draw attention after a short delay

#### Ribbon Position:

* Height: How tall the tab is (default value is 40px)
* Top: Vertical position. Example: 20% means 20% from the top (default value is 50%).

#### Auto-hide

Auto-hide keeps the ribbon accessible without obstructing page content. It hides the ribbon while users scroll down and shows it again when they scroll up.

* **Auto-hide on scroll:** Enable or disable this behavior.
* **Hide on:** Choose **Always**, **Below breakpoint**, or **Above breakpoint**.
* **Breakpoint (px):** Set the screen width used by the **Below breakpoint** and **Above breakpoint** options.
* **Scroll threshold (px):** Set how far users must scroll before the ribbon hides or reappears.

#### Custom CSS

Add CSS snippets to customize the ribbon further. These CSS snippets only affect the ribbon.

#### Where the ribbon shows

On the **Targeting** step, choose the pages and visitors that see the ribbon. These rules only affect the ribbon. The finder's [Targeting](#finder-targeting) also applies.

## In-line Rendering / Landing Page

Use In-line Rendering when you want to embed your Product Finder directly into a dedicated page on your website. Unlike modal-based activations, in-line rendering makes the Finder part of your page layout (ideal for creating a seamless, immersive discovery experience).

#### What you need on your site

Your development team needs to prepare the target page:

* Create a dedicated page for your Product Finder (e.g., `/product-finder` or `/find-your-product`)
* Add a placement element with a unique **CSS selector** that Crobox can target
* Ensure the Crobox snippet is installed on the page

{% hint style="info" %}
Use a unique ID selector when possible (e.g., `#product-finder-placement`) rather than a class. This ensures Crobox targets exactly one element on your page.
{% endhint %}

#### Setup in Crobox

{% stepper %}
{% step %}

### Create the activation

* Navigate to your Product Finder and open the **Activations** tab.
* Click **Create activation** → **Inline Rendering**.
  {% endstep %}

{% step %}

### Configure styling

On the **General** step, set the dimensions and appearance of the Product Finder container.

* **Height:** The height of the Finder container. Use `auto` to let content determine height, or specify a fixed value (e.g., `600px`).
* **Min Height:** The minimum height the container will maintain, regardless of content. Prevents layout shifts during loading.
* **Max Width:** The maximum width of the Finder container. Use `100%` for full-width layouts or a fixed value (e.g., `1200px`) for centered designs.
* **Enable dynamic height:** On by default. The Finder container adjusts its height as users navigate through questions, which prevents unnecessary scrolling or empty space. When disabled, the container keeps its initial height throughout the experience.
* **Background color (optional):** Set a background color for the area behind the Finder. This is visible when Max Width is smaller than the viewport width, creating margins on either side. In most cases the field will be left empty.
  {% endstep %}

{% step %}

### Choose the page and placeholder

On the **Targeting** step, under **Locations**, select the Finder page and the placeholder for your placement element. To add or change placeholders, go to **Settings → Website integration → Placeholders**.

Target only the URL of the Finder page. The finder's [Targeting](#finder-targeting) also applies.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Exclude the in-line page from your ribbon targeting. If both show on the same page, they can interact and cause unexpected behavior.
{% endhint %}

## Finder Targeting

At the bottom of the Activations tab, **Targeting** sets general rules for where this finder can be shown. It uses the same filters as [campaign targeting](https://docs.crobox.com/how-to-guides/dynamic-messaging/advanced-targeting-filters.md), such as page type, market, or page URL.

Use it for rules that apply to every activation of the finder. Use an activation's own **Targeting** step for rules that apply to that activation only.

Click **Save** after changing the rules.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.crobox.com/how-to-guides/product-finders/create-activations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
