Enabling Postalytics

Overview

Enabling Postalytics connects your Kizen environment to Postalytics so you can send physical mail using Contact data. Once enabled, Postalytics becomes available for one-time sends and automation-based workflows within Kizen.

Before You Begin

Before configuring Postalytics, ensure you have:

• Admin-level access in Kizen to manage integrations and automations

• An active Postalytics account

• At least one Triggered Drip campaign created in the Postalytics dashboard

• Contacts in Kizen with valid mailing address data

• Only for sandbox users: Postalytics entitlement enabled (setup up by Kizen; reach out to Kizen support 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 Kizen.

1

Navigate to Platform> App Marketplace

2

Search for Postalytics, then toggle it on

3

Verify Contacts is a linked object on the Postalytics Configuration modal

Select Save when finished.

Note: At this time, Contacts are the only supported object.

4

Enter your Postalytics API key in the Update Integration Secret modal

The API key is provided by Postalytics. Check out the following Postalytics Knowledge Article on How to Retrieve your API Key. When you have located your API key, paste the Authorization Header value into the Integration Secret field, and select Save.

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.

Note: For sandbox setup, Postalytics entitlement must be enabled for your Business by Kizen support. Without it, the integration will not work.

After completing both steps:

• Postalytics actions should become available on Contact records

• Campaigns should load when sending mail

If actions do not appear, see Error Handling and Troubleshooting.

About Postalytics API Keys Storage

Postalytics API credentials are stored in Kizen 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 automations.

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 automations 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

• Automation-based sends fail and surface as failed automation runs until the issue is resolved

Each Kizen 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 to learn how to send one-time mail directly from individual Contact records.

You can also review Sending Mail from Automations with Postalytics to understand how to include Postalytics in automated workflows for scalable, rule-based mail sends.