Connect email providers & grow your list

Overview

Allspice allows publishers to automatically add users to their newsletter when those users explicitly opt in while using Allspice on your site.

When a visitor creates an Allspice account - or logs into an existing Allspice account - they will see an option to join your newsletter. If they agree, Allspice securely sends their information to your connected email marketing provider(s).

You can connect multiple providers at once. For example:

• Mailchimp + Kit simultaneously
• MailerLite + Mailchimp
• Several providers at once (for example Mailchimp + MailerLite + Kit + Flodesk)

If a user consents, Allspice will attempt to subscribe them to every enabled provider linked to the domain.

There are two separate flows on this page. Newsletter signups (described above) go to the destination you pick in Domain Settings. Membership events - someone joining, starting a trial, a failed payment, or a membership ending - go to their own destinations, which you map separately in the Memberships area. The two never share a destination, so a reader who cancels is never added to your newsletter list as a side effect.

Where to Configure This

1. Open the Publisher Portal
2. Navigate to Domain Settings
3. Scroll to Link Email Providers
4. Click + Add Provider

You will then:

1. Select the provider
2. Enter required credentials
3. Choose the list / audience / group / tag / segment
4. Save

Your credentials are stored securely and encrypted.

User Experience

Users may be prompted to join your newsletter when:

• Creating an Allspice account on your site
• Logging into an Allspice account on your site
• Returning to your site with an existing Allspice account

If they agree:

• ✔ They are subscribed to your configured email list(s)
• ✔ Only the domains they consent to are subscribed
• ✔ Consent is recorded and timestamped

If they do not agree:

• ✖ No subscription occurs
• ✖ No provider is contacted

Provider Setup Instructions

Mailchimp

Where to get API Key

1. Log into Mailchimp
2. Profile → Extras → API Keys
3. Click Create Key
4. Copy the key

You will also need your Server Prefix (example: us18, us19)

This appears at the end of the API key:

In Allspice:

• Enter the full API key
• Enter the server prefix
• Select your Audience

How subscriptions work

Users are added to the selected Audience. You may later segment them using Mailchimp tags or automations.

MailerLite

Where to get API Token

1. Log into MailerLite
2. Integrations → API
3. Click Generate New Token
4. Copy the token

In Allspice:

• Paste the token
• Select the Group to subscribe users into

How subscriptions work

Users are added to the selected Group. Groups are the correct MailerLite concept for subscriber entry - campaigns are not direct subscription targets.

Kit (formerly ConvertKit)

Where to get API Key

1. Account Settings
2. Developer
3. Add New V4 Key
4. Copy the value

In Allspice:

• Paste the key
• Select a Tag

How subscriptions work

Users are subscribed to the chosen Tag. You can then build automations inside Kit triggered by that tag.

Flodesk

Where to get API Key

1. Log into Flodesk
2. Go to My Account → Integrations → API keys
3. Click Create API key
4. Give the key a clear name
5. Copy the API key

Make sure to copy the key when it is created. You may not be able to view the full key again later.

In Allspice:

• Enter your API key
• Select the Segment to subscribe users into

How subscriptions work

Users are added to the selected Segment.

Segments are the correct Flodesk destination for new subscribers. You can then build Flodesk workflows or automations that trigger when someone is added to that segment.

Managing Providers

Inside the Publisher Portal you can:

Enable / Disable

Temporarily stop subscriptions without deleting configuration.

Edit

Update credentials or change the destination list, audience, group, tag, or segment.

Multiple Providers

If multiple providers are enabled:

• Allspice attempts all subscriptions
• Failure of one provider does not block others

Membership Events

If you run a site membership, Allspice can tell your email platform when a reader's membership changes, so your automations can react to it.

The four events

Where to configure this

1. Open the Publisher Portal
2. Go to Memberships → Marketing
3. Under Email integration, find the domain and provider you want
4. For each event, add one or more destinations
5. Save mapping

The connection itself - your API key, and which provider is linked to which domain - still lives in Domain Settings. Only the event mapping is set in Memberships. An event with no destination sends nothing.

Tags and status: why both

Each event adds a tag, and tags accumulate. That is what makes automations fire: a "membership ended" tag can trigger your win-back sequence.

But tags alone cannot tell you who is a member right now. Someone who joined in March and cancelled in June carries both tags forever. So Allspice also writes a custom field, allspice_membership_status, which is overwritten each time and always holds the current state:

• active - a paying member
• trialing - in a free trial
• payment_failed - renewal declined, access at risk
• canceled - no longer a member

Segment on the field when you want current members. Trigger on the tag when you want to react to the moment something changed.

Consent

A paid membership purchase is treated as marketing consent, recorded with a source of membership_purchase and a timestamp. This is deliberately distinct from the newsletter opt-in, so the two remain separable in your records.

Membership events also update the contact if they already exist in your platform. A member who was already on your newsletter still gets their membership tag and status field - otherwise a long-time subscriber who joins would never be marked as a member.

What does not fire these events

Membership events are for memberships only. Meal plans and other one-time or premium product purchases do not emit them, and those buyers are never tagged as members.

Data Sent to Providers

Newsletter signups. Only the minimal data required for subscription:

• Email address
• First name (if available)
• Last name (if available)

Membership events. The same contact details, plus:

• The tag for the event that occurred
• The allspice_membership_status field

No payment details, card numbers, or Stripe identifiers are ever sent to your email provider.

Consent is recorded by Allspice but not transmitted unless the provider supports it.

Security

• Credentials stored encrypted
• Never exposed to client browsers
• Sent server-to-server only
• Only triggered after explicit consent

Troubleshooting

Subscribers not appearing?

• Confirm provider is enabled
• Confirm destination selected
• Confirm valid API key
• Confirm automations not filtering the user

Changed lists recently?

Re-open provider settings and re-select the destination.

Need another provider?

We are continuously expanding integrations. Contact Allspice support to request:

• ActiveCampaign
• Klaviyo
• Beehiiv
• Others