
The **Send Web Push** node allows you to communicate with your customers through wep push notifications based on events and other conditions defined in a workflow.  

When a workflow that contains this node is launched, a web push campaign is created as a result. You can find its statistics in the **Experience Hub** and in the **Send Web Push** node itself. 

The configuration of the node requires:
- selecting or creating a template
- defining the web push lifespan

Optionally, you can:

- add UTM and URL parameters,
- add custom parameters,
- send a test message

## Requirements
---

- You must implement a tracking code into your website.
- You must configure web push notifications.
- You must have Web Push subscribers.

## Configuration
---
1. Go to **Automation Hub > Workflows > New workflow**.  
2. Select one of the profile trigger nodes, for example [Profile Event](/docs/automation/triggers/client-event-node).  
3. Click **THEN > Send Web Push**.  
4. To open the configuration form of the node, click it.  
5. Optionally, next to the node name, you can add a custom node title which will be displayed on the node.
6. If you want to assign a tag to the web push campaign you will send through the workflow, under the node title, click **Add tag**.  
7. From the dropdown list, select the [tag](/docs/assets/tags).  
    The list contains only the tags which are available in the predefined **campaigns** tag folder. 
    
   <div class="admonition admonition-tip"><div class="admonition-icon"><svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2.5"><path stroke-linecap="round" stroke-linejoin="round" d="M9.663 17h4.673M12 3v1m6.364 1.636l-.707.707M21 12h-1M4 12H3m3.343-5.657l-.707-.707m2.828 9.9a5 5 0 117.072 0l-.548.547A3.374 3.374 0 0014 18.469V19a2 2 0 11-4 0v-.531c0-.895-.356-1.754-.988-2.386l-.548-.547z" /></svg></div><div class="admonition-body"><div class="admonition-content">

   Assigning tags helps you organize your communications by categorizing campaigns across different channels. Additionally, you can control [communication limits](/docs/settings/configuration/campaign-limits) by applying restrictions to these tags.

   </div></div></div>
  

### Select or create template
---
In this part of the node configuration, you will create the content of the message.

3. In the **Content** section, click **Define**.
2. If you want to:  
    - Select a template, click **Create message**. From the list of the templates, select the one you want to use.  
        - If you make changes to the template, click **Save** and then **Use in node**.
        - If you don't make changes to the template, click **Use in node**.
    - Create a message without using an existing template, click **Create message > New template**.  
        The template will be available only in this node for preview and modifications.  
        **Result**: You are redirected to the template builder.
        1. Prepare the template according to the instructions available in ["Creating web push templates"](/docs/campaign/Webpush/creating-webpush-templates).  
        2. After finishing the template, click **Use in node**.  
3. If you want to send this text message regardless of the marketing consent, tick **Send without marketing agreement** checkbox (not recommended).
2. Confirm settings in the section by clicking **Apply**. 

### Define lifespan
---
Define the time for how long the push service will keep trying to send the notification to the browser. If the push service can’t deliver the notification within that time (for example, due to the user’s device being turned off), the notification will be discarded. The notification is only shown to customers whose browsers are running (also in the background) within this time range.


1. In the **Web push lifespan** section, click **Define**.
2. In the **Webpush lifespan (TTL)** field, enter the number.
3. From the dropdown list, select the time unit.
4. Confirm the settings by clicking **Apply**. 

### Adding UTM and URL parameters
---
In this part of the node configuration, you will define UTM and URL parameters that will be added to the links in the web push campaign launched with the start of the workflow. This part is optional.

4. In the **UTM & URL parameters** section, click **Define**.  
1. Fill in the following fields: **UTM campaign**, **UTM medium**, **UTM source**, and **UTM term**.
2. To add URL parameters, in the **URL parameters** section, click **Add parameter**. 
3. Enter values for the **Parameter** and **Value** fields.
2. Confirm by clicking **Apply**.

### Adding additional parameters
---
If you want to add custom event parameters events generated automatically for the web push channel, in the **Additional parameters** section, click **Define**. Add additional parameters according to the instructions in the ["Define additional parameters"](/docs/campaign/Webpush/creating-webpush-campaigns#adding-custom-parameters) section.

### Sending a test message
---
In this part of the node configuration, you can send a test mobile push notification **only** to the users available in [Behavioral Data Hub](/docs/crm/crm-profile), who have the `has_web_push_devices` attribute set to `true`.

1. In the **Test** section, click **Define**.
2. In the search box, you can search users who are available in **Behavioral Data Hub > Profiles**.
3. In the search results, select the users.
4. In the search box, to confirm the list of recipients of test push notification, click **Add**.  
  **Result**: The list of recipients you added is shown.  
4. When your message is ready to be sent as a test, in the upper right corner of the section, click **Send test**.

### Defining additional node settings
---
1. To impose a limit on the action, switch the **Action limit** toggle. Enter a number and from the dropdown list, select the time unit. You can define how many times this action can be executed for the whole automation process (**workflow**), or you can define how many times per second/minute/hour/day/week/month can be executed.  
2. If you want to make sure that this message is sent to a customer, even it exceeds the global limit of this type of messages for a single customer per day (more information is available [here](/docs/settings/configuration/campaign-limits)), enable the **Ignore limits** toggle. You may apply it to system messages such as a transaction confirmation, notifications about order delays, and so on.
3. If you want to exclude customers who belong to the [global control group](/docs/settings/configuration/global-control-group) from the recipients, enable the **Enable Global Control Group** option.  
    This option is only visible in workspaces where the global control group is enabled.


## Example of use
---

<figure>
<img src="/api/docs/image/54176ad07f146575310749eba44b7c2f42c1b327/docs/automation/_gfx/send-webpush-example.png" alt="Example of use" class="full">
<figcaption>Example of an automation process that uses the Send Web Push action</figcaption>
</figure>

This scenario sends a welcome web push notification to customers who subscribed to web push notifications. 

1. It starts with a **Profile Event** trigger node. In the settings of the trigger, select a web push subscription event. 
2. Add **Send Web Push** action. In the settings of the action select the template of the notification (which you need to prepare before) and set the notification lifespan (TTL).
3. When the notification is sent to a customer, the process ends. 
