> For the complete documentation index, see [llms.txt](https://documentation.crossengage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.crossengage.io/data-and-engagement-platform/campaign-management/campaigns/create-a-real-time-campaign.md).

# Create a Real-Time Campaign

* Go to the Campaigns Tab, and click on Create Campaign.
* Choose Realtime Campaign.

<figure><img src="/files/yEh1715nKo4tR0vFZuhQ" alt=""><figcaption></figcaption></figure>

* Give your Campaign a meaningful name. You can also add a Description, Labels or choose a Campaign Group. This will help you and your team to follow the Campaign later.

<figure><img src="/files/NDwLiS9rxInKLAcyOkJA" alt=""><figcaption></figcaption></figure>

* Select the time frame for the Campaign. For this example, this campaign will run from April 2023 onwards.

<figure><img src="/files/pbq6o60hbZmlt7Hl8smK" alt=""><figcaption></figcaption></figure>

* Choose if this campaign is Transactional. A transactional campaign always sends its messages, bypasses frequency cappings. Here we do not select this option.

{% hint style="info" %}
Transactional Campaigns are useful for messages that the customer needs, such as purchase receipts. Generally, we avoid using transactional campaigns, to avoid sending too many messages to a single user.
{% endhint %}

* Choose a Control Group for the Campaign. A Control Group is a group of customers who are excluded from the Campaign, so we can judge how the Campaign is affecting user behavior. Here, we disable the Control Group.

<figure><img src="/files/826gFL7xyM3jFN7H4GHt" alt=""><figcaption></figcaption></figure>

* Click on Save Changes.
* Go to next step: Target Group.
* In the Target Group, select or create a User Segment. This is the audience of your campaign that will be targeted.

<figure><img src="/files/XDQCLG7FoId0VaSlwsGM" alt=""><figcaption></figcaption></figure>

* Click on Save Changes.
* Define a User Journey. Here, we use the events "Added Product" and "Order Completed".
  * Add the first event E1 "Added Product" of type "needs to happen".
  * Add a wait W2 after E1 for "+6 Hours after E1".
  * Add the second event E3 "Completed Order" of type "Should not happen".

<figure><img src="/files/HK804EGVjcfWSK2RS9HI" alt=""><figcaption></figcaption></figure>

* Click again on "Save Changes".
* Go to next step: Messages.
* Create a new message for your audience. Here we use a [Template](/data-and-engagement-platform/messages/templates.md) for the message. You can also use [Handlebars ](/data-and-engagement-platform/messages/personalization.md)such as `{{journey.steps.[0].[properties.price]}}` to customize your message and Subject.

<figure><img src="/files/KYECWbeD2zLqUoUT6ekT" alt=""><figcaption></figcaption></figure>

* After configuring your message, you can click on Preview Message to see what the outgoing message will look like.
* Go to next step: Frequency Capping.
* Select the required Frequency Capping. Here, we cap messages from this Campaign at 1 per 7 days.

<figure><img src="/files/XvUzfWpJ2XzHTHaZYuXE" alt=""><figcaption></figcaption></figure>

* Go to Campaign Summary.
* You can now activate your campaign,by clicking on the Activate button from the Campaign Summary page.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.crossengage.io/data-and-engagement-platform/campaign-management/campaigns/create-a-real-time-campaign.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
