Skip to main content

Mailcoach - Setup Guide

Overview

The Mailcoach source syncs campaign, audience, engagement, unsubscribe and bounce data into Daspire-managed pipelines.

This is a Daspire-owned source connector. Customer-facing APIs use Daspire product ids. Use conn_mailcoach_sellersync_edm as the primary connector_id.

Legacy runtime ids such as source:efd2f044-dcbb-52ee-98d0-c169d9d092b9 are accepted only for old URLs or saved configurations that still contain runtime-style ids.

Prerequisites

  • A Mailcoach account.
  • A Mailcoach bearer token with read access to email lists, campaigns and campaign engagement detail.
  • The HTTPS API base URL:
    • Self-hosted Mailcoach: your Mailcoach instance API URL ending in /api.
    • Mailcoach Cloud: your hosted account API URL in the form https://[your-domain].mailcoach.app/api.

Configuration

FieldRequiredNotes
Connection MethodNoDefaults to Self-hosted. Use Mailcoach Cloud for hosted *.mailcoach.app accounts. Existing configs that do not include this optional field continue to work.
API Base URLYesEnter this value manually. Must be an approved HTTPS Mailcoach API host. Plain HTTP, localhost, private hosts, credentials in URLs, query strings, fragments and non-default HTTPS ports are rejected. For self-hosted Mailcoach, enter the customer's own instance API URL ending in /api; for Mailcoach Cloud, use https://[your-domain].mailcoach.app/api.
API TokenYesStored as Daspire secret material and never returned by product APIs.
Campaign StatusNoDefaults to sent. Other values are scheduled, draft and all.
Page SizeNoDefaults to 100 records per request.

Supported Streams

StreamDescription
email_listsMailcoach email list metadata.
campaignsCampaign records and campaign-level metrics.
campaign_clicksClick detail rows grouped by campaign.
campaign_opensOpen detail rows grouped by campaign.
campaign_unsubscribesUnsubscribe rows grouped by campaign.
campaign_bouncesBounce rows grouped by campaign.

Mailcoach exposes campaign-level EDM metrics natively. Traffic and sales attribution require UTM or internal attribution joins outside Mailcoach.

Migration And Rollback

This connector is added as a new source definition and does not migrate customer connections automatically.

Existing source ids, destination ids, pipeline ids, job ids, selected catalogs, schedules, state, billing and usage behavior are unchanged. Existing _daspire_* warehouse naming is unchanged.

Rollback removes the new Mailcoach source definition from customer setup while leaving existing customer connections and all legacy connector code untouched.