> For the complete documentation index, see [llms.txt](https://userguide.zappost.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://userguide.zappost.com/zap-post-web-app/zap-post-user-guide/getting-started.md).

# Getting Started

This guide will show you how to sign up, create a campaign and send your first pieces of direct mail. \
By time you finish this guide you will have a ZAP\~POST account with Live Campaign that has mail sent that you know how to do effective campaign analysis on. \
\
There are 3 main steps to any direct mail campaign within ZAP\~POST. If you're unfamiliar with any terms below don't worry we'll explain as we go along:<br>

1. **Campaigns**. This is where you tell us what you want to send. What paper stock, what artwork will go in the mail. You'll use our ZAP Designer to create your dynamic artwork so each recipients mailing is unique to them.&#x20;
2. **Submissions.**  This is where you tell us who you want to send the mail to. This can be done via one of our integrations on a recurring schedule, via an API integration or manually via file upload.&#x20;
3. **Campaign and Recipient Analysis**. This is where you can determine which of your campaigns are most effective based on our R.O.A.S reporting. You can also see which mail was rejected, undeliverable, who has scanned any QR codes or other key metrics. <br>

### **Step 1 - Create an account**

In order to get started using ZAP\~POST you'll need to go through the [sign up process](/zap-post-web-app/zap-post-user-guide/zap-app/sign-up.md) to create your account.&#x20;

After creating your account you'll be taken to the ZAP dashboard from where you can get Zapping.&#x20;

### **Step 2 - Create your first campaign**&#x20;

The easiest way to create a new campaign is to use the new campaign button on the dashboard.&#x20;

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

There is also an option to create a new campaign on the campaigns page

<figure><img src="/files/0oRikFWCfjsX3RDweCVx" alt=""><figcaption></figcaption></figure>

From here you should follow the Campaign Wizard steps or use the [campaign creation guide ](/zap-post-web-app/zap-post-user-guide/zap-app/using-the-zapp/campaigns.md#creating-a-campaign)

### Step 3 - Designing your ZAPs

Now that we know what data we're expecting for our campaign and we know what paper we're planning to use we can start to design our campaign artwork. \
\
For ZAPPOST Campaigns your artwork will be managed in the ZAP Designer. This tool allows you to add text, images (Static and dynamic) and QR codes. \
You can use your own custom artwork, fonts and other assets within our tool. \
\
To get to the designer you can select designer from the top nav, or if you're on the campaign you wish to edit artwork for you can access that from the edit designs button or by clicking the edit icon on each page.

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

Any of these options will take you to the designer where you can edit your artwork.&#x20;

#### Using the ZAP Designer

You can view our full breakdown of the designer functionality in the [designer documentation](/zap-post-web-app/zap-post-user-guide/zap-app/using-the-zapp/design.md)\
\
We also have a helpful [article on our academy too](https://zappost.com/academy/lessons/how-to-design-your-zap-video/)

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

Once you're happy with your design, you're ready to proof it. \
Proofing will show you some example documents using default ZAP POST data or using your own custom data set that you're uploaded for testing. \
\
The proof will allow you to check **text accuracy, colour matching, layout and placement** before publishing your designs and running any large volume sends. <br>

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

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

From there you can refine as necessary or publish your artwork if you're happy to begin sending mail.&#x20;

### Step 4 - Creating your first ZAP Submission

A ZAP submission is just a collection of recipients to whom you wish to send mail. In order for us to know who to send mail to, you create a submission against an Active Campaign. \
This allows us to combine your data, with your artwork to create the dynamic ZAPs that will go into the mail. \
There are 3 primary ways to submit data to ZAP POST.&#x20;

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

#### CSV File Submission

The simplest way to submit data to ZAP\~POST is to download the campaign csv file and populate it with your required recipient data. This can then simply be uploaded to the app. \
This process is documented in our [CSV submission process documentation](/zap-post-web-app/zap-post-user-guide/zap-app/using-the-zapp/sending-zaps.md#uploading-data)

#### API Submission&#x20;

For developer submissions, or self managed integrations users can submit their data via API. \
The following documentation on [API Consumers](/zap-post-web-app/zap-post-user-guide/zap-app/using-the-zapp/settings/api-consumers.md) and [API Submissions](/zap-api/api-endpoints/submissions.md) will be useful.&#x20;

#### ZAP Integrations

There are numerous integrations available in ZAP\~POST as you can see below each are covered extensively in our [integration documentation](/zap-integrations/zap-post-integrations.md).&#x20;

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

Regardless of your preferred submission method you will end up with a new Submission created in ZAP POST which will be ready for us to process.&#x20;

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

From there, we'll complete some internal processes to validate your data and confirm your recipient address details are correct. \
Once those processes are run you'll be put into the send date pool associated with your send and they will be mailed.&#x20;

### Step 5 - Analysis&#x20;

For each submission there are various key events that will occur. ZAP POST has several tools to enable users to gain key insights into their direct mail campaigns.&#x20;

#### Submission Monitoring&#x20;

Recipients in a submission can have several key events that you may wish to keep monitor. &#x20;

* Record rejected (Recipient moved, deceased, address details incorrect).&#x20;
* QR Code Scanned
* Mail Returned&#x20;
* Mail sent Successfully
* Submissions with dynamic image issues (If your campaign uses dynamic images)<br>

<figure><img src="/files/3wwf5HbYLuuqBUlRL7f3" alt=""><figcaption></figcaption></figure>

The following events are also logged to all enabled integrations with events functionality: <br>

* Submission Created
* Mail Rejected
* Mail Sent
* QR Scanned
* Mail Returned

#### Return on Ad Spend&#x20;

Users with integrations enabled that allow us to pull order information can also benefit from ROAS reporting. \
User can see overal, Campaign or Submission level ROAS reports&#x20;

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

You should now be comfortable with the basic steps of sending mail with ZAP\~POST. \
If you want any more details you can view the whole [app documentation](/zap-post-web-app/zap-post-user-guide/zap-app/using-the-zapp.md) or you can use our AI powered search functionality to ask any questions you have.&#x20;


---

# 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://userguide.zappost.com/zap-post-web-app/zap-post-user-guide/getting-started.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.