> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wavecx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Add Trigger Point

> Each trigger point can have multiple triggers. These triggers are evaluated to determine when the trigger point should be activated.

The triggers act in a logical OR, meaning if any of the triggers are satisfied, the trigger point will be activated.

![Screenshot 2026 11 18 At 9 52 00 AM](https://mintcdn.com/wave-cx-73936e8c/KxjR84ryoJU4d_aI/images/Screenshot-2026-11-18-at-9.52.00-AM.png?fit=max\&auto=format\&n=KxjR84ryoJU4d_aI\&q=85\&s=d115dda9672bfe0cbf218fd991c60cc3)

> [!TIP]
>
> To get started, select **+ Add Trigger Point** from the right panel of options on the Content Targeting page.

***

## Add Trigger Point

A **trigger point** is a place or moment in your app where content can appear. Once you create one, you can attach content to it, such as Featurettes.

On the **Content Targeting** page, click **+ Add Trigger Point** on the right. Give it a name and set the Trigger.

##### Give it a name

Give the trigger point a clear name that describes where or when it fires, such as “Dashboard” or “Payments”. This is the name you’ll see on the **Content Targeting** page.

##### Triggers

A trigger is the rule that activates the trigger point. You can add more than one trigger, and the trigger point activates as soon as **any one** of them is met.

***

## Trigger types

<table>
  <colgroup>
    <col width="110" />

    <col width="84" />

    <col width="256" />

    <col width="265" />
  </colgroup>

  <thead>
    <tr>
      <th>Type</th>
      <th>Works on</th>
      <th>Activates when…</th>
      <th>What you’ll need</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>**Route Match**</td>
      <td>Web only</td>
      <td>A user opens a specific page in your app</td>
      <td>The page’s route, which is its web address without the domain, written as a regular expression. Example: `/dashboard`</td>
    </tr>

    <tr>
      <td>**DOM Click**</td>
      <td>Web only</td>
      <td>A user clicks a specific element on the page</td>
      <td>The element’s DOM selector, such as a button’s ID or class</td>
    </tr>

    <tr>
      <td>**Dynamic Button**</td>
      <td>Web only</td>
      <td>A user clicks a WaveCX button added to your page. The button only appears when there’s content for that user at this trigger point</td>
      <td>The DOM selector where the button should go, plus the button’s text and colors</td>
    </tr>

    <tr>
      <td>**Screen View**</td>
      <td>Mobile only</td>
      <td>A user opens a specific screen in your mobile app</td>
      <td>The screen name. It must exactly match the name your mobile development team assigned</td>
    </tr>

    <tr>
      <td>**Custom Event**</td>
      <td>Web and mobile</td>
      <td>Your app sends a specific custom event</td>
      <td>The event code. It must exactly match the one defined in your app</td>
    </tr>
  </tbody>
</table>

> [!TIP]
>
> Your development team can give you DOM selectors, screen names and event codes.

***

## Saving

Click **Save** to create the trigger point. It then appears on the Content Targeting page, ready for you to add content. Click the **X** to close without saving.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.