# Creating a campaign

{% hint style="warning" %}
Meta restricts 1 message per person every 24 hours to prevent spam
{% endhint %}

#### Steps

1. Go to “Home” tab
2. **Campaign** name is internal only and used for analytics
3. **Image** or **video** can be uploaded (optional)
4. In **text input**, write the intended message. Note there is 250 character limit
5. Include CTA **button** (optional)
   1. **Button title** is what the recipient will see on the button
   2. **Button URL link** is where the recipient will be directed to. Can include UTM parameters
6. **Recipients** let you segment your audience. Segments are built in a separate “Segment” tab.
7. **Preview** your message. This will ask you to approve 1send messaging your FB user account if you have not interacted with the FB page in 24 hours
8. **Send** campaign.

#### The campaign builder consists of 4 parts:

* **Campaign Name:** This is an internal name used for analytics and reference purposes later. The default is current date
* **Image/Video Upload**: 1send supports multimedia elements including image and video. It is optional to include in your campaign.
* **Text Input**: This is the message you want to send to your subscribers. It supports emojis and has a character limit of 250.
* **CTA Button**: This is an optional input that can help direct your subscribers to a URL. Clients often include UTM parameters to better track traffic sources

Once the fields are complete you can either choose to send a preview to yourself or broadcast it to your subscribers!

{% content-ref url="/pages/YKA3KHpOJ5DkylI24C4X" %}
[Sending Previews](/learn/creating-a-campaign/sending-previews.md)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://docs.1send.net/learn/creating-a-campaign.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.