> For the complete documentation index, see [llms.txt](https://wamoca.gitbook.io/wamoca-docs-en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wamoca.gitbook.io/wamoca-docs-en/our-platform/campaigns.md).

# Campaigns

<mark style="color:purple;">**Before you continue, make sure you have:**</mark>&#x20;

* <mark style="color:purple;">**Connected your whatsapp account**</mark>
* <mark style="color:purple;">**Configured your time zone in Settings > General**</mark>

The campaigns module allows users to efficiently create and manage WhatsApp campaigns.

## List of campaigns

The list will show the campaigns created by the user with the following columns:

* **Name**: name of the campaign&#x20;
* **Template**: WhatsApp template used in the campaign&#x20;
* **Contacts**: total number of contacts&#x20;
* **Delivery Rate**: message delivery rate&#x20;
* **Read Rate**: message reading rate&#x20;
* **Status**: status of the campaign
  * <mark style="color:orange;">**Scheduled**</mark>: the campaign has not yet been implemented and has a future date for implementation
  * <mark style="color:blue;">**On going**</mark>: the campaign is running
  * <mark style="color:green;">**Finished**</mark>: the campaign has been implemented and completed
* **Scheduled date**: date to which the campaign is scheduled to take place.

<figure><img src="/files/o2sQbgdUH6FhOhpKq9cX" alt=""><figcaption><p>List of campaigns</p></figcaption></figure>

## List of campaigns

On the campaign creation screen we will find:

### Basic data

<figure><img src="/files/gCYCzi7gliRDfOQW6gwN" alt=""><figcaption><p>Basic campaign data</p></figcaption></figure>

These are the basic details of the campaign:&#x20;

* **Name** of the campaign&#x20;
* **Template**: WhatsApp message template that we must have created previously
* **Send to**: the group of contacts to send the campaign to
* **Scheduled time**: date and time at which we want to send the campaign (it can also be sent immediately if we select the ‘Skip scheduling’ checkbox).

### Message template variables

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

Depending on the design of the WhatsApp message template used, some fields will appear or others. In this case, we have used several fields to see it in more detail:&#x20;

#### Header variables&#x20;

This field refers to the header of the message. In this example, we have used an image as a header. To include it in the message, click on the ‘*Upload image*’ button and select the desired image.&#x20;

#### Body variables&#x20;

This field refers to the body of the message. In this example we have used a text with a variable called {{1}}, which we will dynamically replace with the name of the client: ‘*Hello {{1}}, we have a special discount on sunglasses at 2X1! 😎🏖️*’ To do this we will have to select the option ‘*dynamic*’ and the field ‘contact first name’:

<figure><img src="/files/1kv7J1J8BaO05p8GrY7J" alt=""><figcaption><p>Dynamic variable message body</p></figcaption></figure>

Now the text that the user will receive will be: ‘***Hi Cristian**, we have a special discount on sunglasses AL 2X1! 😎🏖️*’

**Button variables**

<figure><img src="/files/g92bDKsfKtxp93FFZMRJ" alt=""><figcaption><p>Button variables</p></figcaption></figure>

This field refers to the buttons or CTAs of the message. In the case of this template, we use four buttons:&#x20;

* **URL**: external link that is configured directly in the template
* **Phone**: phone or mobile number that is configured directly in the template
* **Copy Offer Code**: offer code that can be copied and modified from the campaign
* **Label**: custom button, whose value can be modified from the campaign. Once the user presses the button, it will send a message with that value. This type of buttons are very useful for autoresponders.

### **Campaign details**

In the details screen you can analyse the campaign in more detail by viewing the following metrics:

* **Total contacts**&#x20;
* **Messages sent**: number of messages sent
* **Delivered messages**: number of messages that have been delivered to recipients
* **Messages read**: number of messages that have been delivered and read (only works if the end-user has enabled read confirmation in their WhatsApp account)
* **Failed messages**: number of messages that have not been sent

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

You can also view a log of each message sent by clicking on the ‘More information’ button:

<figure><img src="/files/LTh9XGpirfpfmTXlQPxf" alt=""><figcaption><p>Message information</p></figcaption></figure>


---

# 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://wamoca.gitbook.io/wamoca-docs-en/our-platform/campaigns.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.