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

# Create a campaign

> Create a campaign and choose its channel, delivery timing, and audience.

## 1. Basic information and channel

![Basic campaign information and channel selection](https://mintcdn.com/notifly/dcFO7QF5JScPffiH/images/i18n/en/campaigns/campaign-basic-info-creation-v2.png?fit=max\&auto=format\&n=dcFO7QF5JScPffiH\&q=85\&s=4226eaa73f9fab35fdf8a7697679602c)

* Enter a **Campaign Name** that makes it easy to find in the campaign list.
* Use **Campaign Description (Optional)** for internal notes about the campaign.
* In **Delivery Channel**, choose a channel such as push, KakaoTalk, a popup, or SMS.
  > [!WARNING]
  >
  > * To send through KakaoTalk or email, register your sender information in **Settings** at the bottom left of the console.
  > * Incorrect sender information can cause sends to fail.
  > * See the guides for your channel: [app push](https://docs.notifly.tech/en/user-guide/channel/app-push-notification/guide.md), [web push](https://docs.notifly.tech/en/user-guide/channel/web-push-notification/guide.md), [in-app popups](https://docs.notifly.tech/en/user-guide/channel/in-app-message/guide.md), [web popups](https://docs.notifly.tech/en/user-guide/channel/web-message/guide.md), [email](https://docs.notifly.tech/en/user-guide/channel/email/guide.md), [SMS](https://docs.notifly.tech/en/user-guide/channel/text-message/notifly_guide.md), [KakaoTalk (Korean)](https://docs.notifly.tech/ko/user-guide/channel/kakaotalk/setup.md), or [webhooks](https://docs.notifly.tech/en/user-guide/channel/webhook/guide.md).

## 2. Delivery timing

Under **Delivery Timing**, choose **Scheduled Send**, **Event-Based Send**, or **API-Triggered Send**.

> [!NOTE]
>
> If you send to recipients in other countries, see [Manage campaigns across time zones and daylight saving time](https://docs.notifly.tech/en/user-guide/campaigns/timezone-and-daylight-saving.md). For recurring campaigns that use a named time zone, the local send time can shift after a daylight saving time change. **Recipient's time zone** uses each recipient's own time zone.

### 2.1. Scheduled sends

![Scheduled campaign delivery options](https://mintcdn.com/notifly/dcFO7QF5JScPffiH/images/i18n/en/campaigns/campaign-reservation.png?fit=max\&auto=format\&n=dcFO7QF5JScPffiH\&q=85\&s=adeaada503ab956ad81f1fd7d2f61208)

Choose one of the following delivery options.

1. **Immediate Delivery**
   * Click **Final Confirmation** to review the campaign. Click **Create Campaign**, then click **Create Campaign** again in the confirmation dialog to start sending immediately. Messages that have already started sending cannot be recalled.

2. **One-Time Scheduled Delivery**

   * Choose a date and time for the campaign to run.
   * You can cancel a one-time send scheduled in a single time zone only if more than five minutes remain before the scheduled send time.

3. **Daily Scheduled Delivery**
   * The campaign sends at the time you set each day from the start date through the end date.

4. **Scheduled Delivery on Specified Days**
   * Set the days and time for the campaign to send between the start and end dates. You can also set the number of weeks between sends.
     * For example, send every other week on Monday and Friday.

### 2.2. Event-based sending

Use an event-based campaign to notify a user when they trigger a specific event.

> [!TIP]
>
> 1. Use the [Client SDK](https://docs.notifly.tech/en/developer-guide/index.md) to record an event when a user takes an action in your app.
>
> 2. Use the [HTTP API](https://docs.notifly.tech/en/api-reference/getting-started.md) to send user-specific and service-wide events to Notifly, such as an event marking the end of a sale.
>
> 3. If you already use [Amplitude](https://docs.notifly.tech/en/user-guide/integrations/amplitude/amplitude-introduction.md), use the integration to forward your existing events to Notifly.

![Trigger conditions for an event-based campaign](https://mintcdn.com/notifly/dcFO7QF5JScPffiH/images/i18n/en/campaigns/campaign-event-based-timing-v5.png?fit=max\&auto=format\&n=dcFO7QF5JScPffiH\&q=85\&s=d0276823e88a8fccefa5db16fc60706f)

Set the trigger event and choose when Notifly can send the message.

* Under **Trigger Conditions**, select the event that triggers the campaign. You can enter the name of an event that has never occurred.

  * Select **Use Parameter Filter** to trigger the campaign only when the event includes a parameter value that matches your conditions.

    * For example, if `main_button_click` includes the event parameter `menu`, send only when `menu` equals `trial_click`.

    > [accordion] More event parameter filter examples
    >
    > ![Filter a purchase event by product category](https://mintcdn.com/notifly/dcFO7QF5JScPffiH/images/i18n/en/campaigns/triggering-event-filters-example-1.png?fit=max\&auto=format\&n=dcFO7QF5JScPffiH\&q=85\&s=e87d3721b4339acef1c8780b1e9cb0f7)
    >
    > * If the `purchase` event includes a `product_category` parameter, send only when the parameter equals `clothing`.
    >
    > Use **AND** and **OR** to combine conditions.
    >
    > ![Combine trigger filters with AND and OR](https://mintcdn.com/notifly/dcFO7QF5JScPffiH/images/i18n/en/campaigns/triggering-event-filters-example-2.png?fit=max\&auto=format\&n=dcFO7QF5JScPffiH\&q=85\&s=fce01a5322ffbb4e95e02412ca23bc6a)
    >
    > * In this example, the campaign sends if the user came from `blog`, visited `/product`, and had a query parameter `id` of `123`. It also sends if the user came from `banner` and landed on the home screen (`pathname` is `/`).
    >
    > The example assumes that `page_view` includes `utm_medium`, `pathname`, and `query.id`.

* Set the start and end dates in **Campaign Validity Period**. Events can trigger the campaign during this period.

* Under **Delay After Event Occurrence**, choose whether to send immediately after the trigger or wait for a set time.

  * If the send delay is at least five minutes, you can turn on **Use cancellation condition** and choose an event that cancels the pending send.

    * For example, cancel a user's pending send if the same user records `notifly__push_delivered` within 1 day, 2 hours, 3 minutes, and 4 seconds after `notifly__main_button_click`.

      > [!TIP]
      >
      > You can schedule a promotion to send one hour after a user logs in and use `purchase` as the cancellation event. If the user buys something during that hour, the promotion does not send.

* Turn on **Use frequency capping** to prevent repeated messages in a short period, for example, when the same user repeatedly triggers the event. See [Frequency capping](https://docs.notifly.tech/en/user-guide/campaigns/fatigue-management.md).

* Turn on **Use Quiet Hours** to set when the campaign cannot send.

  * To send blocked messages after quiet hours end, turn on **Allow delayed sending**.

  > [!NOTE]
  >
  > The scheduled send time can differ from the end of quiet hours after a daylight saving time change. See [Delayed delivery around daylight saving time changes](https://docs.notifly.tech/en/user-guide/campaigns/timezone-and-daylight-saving.md#how-do-quiet-hours-and-delayed-sending-work).

  > [!WARNING]
  >
  > In South Korea, sending commercial advertising by electronic means between 9:00 PM and 8:00 AM the next day requires separate prior consent from the recipient. Email is exempt from this separate nighttime consent requirement under the [enforcement decree](https://www.law.go.kr/LSW/lsInfoP.do?lsId=004797).
  >
  > * See [Article 50(3) of South Korea's Act on Promotion of Information and Communications Network Utilization and Information Protection](https://www.law.go.kr/LSW/lsLinkCommonInfo.do?chrClsCd=010202\&lsJoLnkSeq=1029563507).

### 2.3. API-based sending

You can trigger a Notifly campaign directly through the HTTP REST API. See the [Campaign Triggering API](https://docs.notifly.tech/en/api-reference/trigger-campaign.md) for the request format.

* Specify the target audience in the API request body. The console does not let you select an audience for this campaign type.

> [accordion] Example API-triggered campaign
>
> * This campaign uses the sample code in the [Campaign Triggering API reference](https://docs.notifly.tech/en/api-reference/trigger-campaign.md).
>
>   ![Message setup for an API-triggered campaign](https://mintcdn.com/notifly/dcFO7QF5JScPffiH/images/i18n/en/campaigns/api-triggered-campaign-message-example.png?fit=max\&auto=format\&n=dcFO7QF5JScPffiH\&q=85\&s=30e8654c670113c13940b6d1bf659070)
>
> - The example assumes that the user has a `name` property.

## 3. Target audience

See [Set the target audience](https://docs.notifly.tech/en/user-guide/campaigns/campaign-segments/segment.md) to choose who receives the campaign.

## 4. Message and action

See the guide for your channel to set up the message and its actions.

## 5. Analysis configuration

If you are creating an A/B test campaign, set at least one conversion event. For a standard campaign, conversion tracking is optional.

* Under **Conversion Events**, choose a user action to track as a conversion.
  * In **Tracking Period**, enter a value from 1 to 14 days. For total conversions, the period starts when the message is successfully sent or the popup is shown. For direct conversions, it starts when a click is recorded. Enter `1` for a 24-hour window.


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