> For the complete documentation index, see [llms.txt](https://developer.kizen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.kizen.com/docs/integrations-and-plugins/integrations/postalytics/enabling-postalytics.md).

# Enabling Postalytics

{% hint style="success" %}
**Audience:** Admins, Developers, <code class="expression">space.vars.automation</code> Builders, Support & Operation teams, and Solution Architects

**Purpose:** Explains how to enable the Postalytics integration in <code class="expression">space.vars.Kizen\_company\_name</code> so you can connect your account and begin using Postalytics features within the platform.
{% endhint %}

## Overview

{% hint style="warning" %}
**Caution:** This setup reflects <code class="expression">space.vars.Kizen\_company\_name</code>'s default configuration. Your administrator may have customized your layout, so columns or navigation may appear differently. Trial accounts may have limited features.
{% endhint %}

Enabling Postalytics connects your <code class="expression">space.vars.Kizen\_company\_name</code> environment to Postalytics so you can send physical mail using <code class="expression">space.vars.contact</code> data. Once enabled, Postalytics becomes available for one-time sends and <code class="expression">space.vars.automation</code>-based <code class="expression">space.vars.workflows</code> within <code class="expression">space.vars.Kizen\_company\_name</code>.

***

## **Before You Begin** <a href="#prerequisites" id="prerequisites"></a>

Before configuring Postalytics, ensure you have:

* Admin-level access in <code class="expression">space.vars.Kizen\_company\_name</code> to manage integrations and <code class="expression">space.vars.automations</code>
* An active Postalytics account
* At least one Triggered Drip campaign created in the Postalytics dashboard
* Contacts in <code class="expression">space.vars.Kizen\_company\_name</code> with valid mailing address data
* **Only for sandbox users**: Postalytics entitlement enabled (setup up by <code class="expression">space.vars.Kizen\_company\_name</code>; reach out to [Kizen support](https://support.kizen.com/support/tickets/new) to do this)

The Postalytics integration currently works only with drip campaigns. Bulk mail campaigns (which are one-off mail blasts) are not currently supported for integrations with <code class="expression">space.vars.Kizen\_company\_name</code>.

***

{% stepper %}
{% step %}

#### Navigate to **Platform** > **App Marketplace**

<div data-with-frame="true"><figure><img src="/files/fQQUseLLB8e9HIWPuYtL" alt="" width="320"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

#### Search for **Postalytics**, then toggle it on

<div data-with-frame="true"><figure><img src="/files/ZzqkhC5ubVTOSbEE2s73" alt="" width="320"><figcaption></figcaption></figure></div>

The **Postalytics Configuration** modal appears.
{% endstep %}

{% step %}

#### Verify Contacts is a linked Object

Select **SAVE** when finished.

<div data-with-frame="true"><figure><img src="/files/QqpO29LBM9IYvgd6DAK9" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}
**Note:** At this time, <code class="expression">space.vars.contacts</code> are the only supported <code class="expression">space.vars.object</code>.
{% endhint %}

The **Update Integration Secret** modal appears.
{% endstep %}

{% step %}

#### Enter your Postalytics API key

The API key is provided by Postalytics. Check out the following Postalytics topic on [How to Retrieve your API Key](https://support.postalytics.com/support/solutions/articles/70000625187-where-can-i-find-my-authentication-api-key-). When you have located your API key, paste the Authorization Header value into the I**ntegration Secret** field, and select **SAVE**.&#x20;

{% hint style="info" %}
**Note:** When copying the header value, you only need to copy the key that appears after `Basic`. The full header value does not need to be copied.
{% endhint %}

<div data-with-frame="true"><figure><img src="/files/WN2ozPdWfdU602dI8lh4" alt="" width="320"><figcaption></figcaption></figure></div>

{% hint style="info" %}
**Note:** For sandbox setup, Postalytics entitlement must be enabled for your Business by <code class="expression">space.vars.Kizen\_company\_name</code> support. Without it, the integration will not work.
{% endhint %}
{% endstep %}
{% endstepper %}

After completing both steps:

* Postalytics actions should become available on <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code>
* Campaigns should load when sending mail

If actions do not appear, see [Error Handling and Troubleshooting](/docs/integrations-and-plugins/integrations/postalytics/postalytics-troubleshooting-and-error-handling.md).

***

## **About Postalytics API Keys Storage** <a href="#integration-secrets" id="integration-secrets"></a>

Postalytics API credentials are stored in <code class="expression">space.vars.Kizen\_company\_name</code> as an Integration Secret. Integration secrets are a secure mechanism for managing sensitive credentials, such as API keys, that are required for integrations to function. Storing the Postalytics API key as an integration secret ensures the key is protected and centrally managed at the Business level, rather than exposed to individual users or embedded in <code class="expression">space.vars.automations</code>.

When a Postalytics API key is saved as an integration secret:

* The key is encrypted, not displayed in plain text in the UI, and is referenced securely by integrations and <code class="expression">space.vars.automations</code> when needed.
* The secret is scoped to the Business, not to an individual user
* Only users with appropriate administrative permissions can view or update it
* All manual and automated sends use the same stored key

If the API key is updated or revoked:

* New sends immediately begin using the updated key once it is saved
* Manual sends fail with an authentication error if the key is invalid
* <code class="expression">space.vars.automation</code>-based sends fail and surface as failed <code class="expression">space.vars.automation</code> runs until the issue is resolved

Each <code class="expression">space.vars.Kizen\_company\_name</code> Business supports a single Postalytics account connection at a time. If you need to switch Postalytics accounts, update the API key stored in the integration secret.

***

## What's Next

Next, continue to [Sending Mail from a Contact Record with Postalytics](/docs/integrations-and-plugins/integrations/postalytics/sending-mail-from-a-contact-record-with-postalytics.md) to learn how to send one-time mail directly from individual <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code>.

You can also review [Sending Mail from Agentic Workflows with Postalytics](/docs/integrations-and-plugins/integrations/postalytics/sending-mail-from-automations-with-postalytics.md) to understand how to include Postalytics in automated <code class="expression">space.vars.workflows</code> for scalable, rule-based mail sends.

<details>

<summary>Related Topics</summary>

* [Postalytics](/docs/integrations-and-plugins/integrations/postalytics.md)
* [Sending Mail from a Contact Record with Postalytics](/docs/integrations-and-plugins/integrations/postalytics/sending-mail-from-a-contact-record-with-postalytics.md)
* [Sending Mail from Agentic Workflows with Postalytics](/docs/integrations-and-plugins/integrations/postalytics/sending-mail-from-automations-with-postalytics.md)

</details>


---

# 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://developer.kizen.com/docs/integrations-and-plugins/integrations/postalytics/enabling-postalytics.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.