Connect Constant Contact
In the client’s workspace, open Sources, add Constant Contact and choose the account to sync. If you don’t have access to the account, send the client a connect link where the platform supports one.
Email & SMS integration
Turn email campaign performance, contacts, and engagement into 54 governed metrics for dashboards, agent answers, and cross-channel reporting.
What you can do with Constant Contact in Maven
Maven models Constant Contact into 54 governed metrics from the semantic layer. Track Email Attributed Orders, Email Attributed Revenue, Email Bounces, Click Rate and Email Clicks, break results down by Channel, Account, Campaign type and Subject line, and report Constant Contact alongside Shopify, HubSpot CRM and Facebook Ads without rebuilding exports or metric logic for every report.
What you can measure
Maven keeps Constant Contact numbers consistent across dashboards, reports, and answers so the team is not debating which spreadsheet is right.
Orders attributed to the send by the email platform.
Revenue attributed to the send by the email platform.
Bounced emails from connected email send performance rows
Unique clicks divided by emails delivered
Email clicks including repeat clicks at send grain
Unique opens divided by emails delivered
Email opens including repeat opens at send grain
Replies received from connected email send performance rows.
Spam or abuse reports from connected email send performance rows.
Unique recipients or profiles that clicked at send grain
Unique recipients or profiles that opened at send grain
Unsubscribes from connected email send performance rows
Emails delivered by connected email platforms at send grain
Emails sent by connected email platforms at send grain
Conversions reported by Iterable
Message bounces reported by Iterable
Message clicks reported by Iterable
Message opens reported by Iterable
Messages sent by Iterable
Revenue attributed by Iterable
SMS bounces reported by Iterable
Unsubscribes reported by Iterable
Push bounces across connected messaging platforms
Push opens across connected messaging platforms
Push messages sent across connected messaging platforms
SMS messages received across connected messaging platforms
SMS messages sent across connected messaging platforms
Orders attributed to SMS sends
Revenue attributed to SMS sends
SMS message bounces across connected messaging platforms
SMS message clicks across connected messaging platforms
SMS messages delivered across connected messaging platforms
SMS unsubscribes across connected messaging platforms
Orders attributed to the send by the messaging platform. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Email and SMS platforms report attributed ecommerce orders; Iterable rows use Iterable purchases.
Revenue attributed to the send by the messaging platform. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider.
Bounced messages at send grain across email, SMS and push. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider.
Clicks including repeat clicks at send grain across email, SMS and push. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider.
Conversions reported by the messaging platform. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Definitions differ by provider: Iterable email rows carry Iterable custom conversion events, while email-platform and SMS-platform rows carry attributed orders (equal to message_attributed_orders). Filter platform = iterable for Iterable conversions.
Opens including repeat opens at send grain. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Email opens are pixel opens (inflated by privacy proxies such as Apple MPP); push opens are app opens from a notification; SMS rows carry no opens. Do not compare open counts across channels; filter channel = email for email opens.
Replies received from connected send performance rows. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Only email-platform rows populate replies.
Spam or abuse reports (complaints) from connected send performance rows. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Iterable complaints are reported as spam reports; SMS and push rows carry none.
Unique recipients or profiles that clicked at send grain. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. SMS-platform rows report no unique clicks and carry total clicks instead (unique_clicks = clicks), and Iterable rows are 0; filter channel = email for true email unique clicks.
Unique recipients or profiles that opened at send grain. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Only email-platform rows populate unique opens (Iterable, SMS and push rows are 0), so the total equals email unique opens.
Unsubscribes attributed to sends across email, SMS and push. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Counts unsubscribers, not unsubscribe events (see message_unsubscribe_event_count).
Messages delivered at send grain across email, SMS and push. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Email-platform and SMS-platform rows report native delivered counts; Iterable email, SMS and push rows derive delivered as sent minus bounces.
Inbound SMS messages received across connected messaging platforms. Only SMS rows populate this measure. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider.
Messages sent at send grain across email, SMS and push. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Filter channel = email for emails sent.
Questions you can ask
Maven’s agent answers in plain language with the right metric definitions applied automatically. These are real, verified questions it can run today.
How many emails did we send and what was the unique open count last month by platform?
Show bounces by campaign type
How much email attributed revenue did we drive by platform?
Connection and sync
You connect Constant Contact by signing in to it and approving access, so nobody shares a password. The first Constant Contact sync pulls the most recent 30 days so the workspace fills quickly. A follow-up backfill then adds older history, up to 12 months in total. After that, each scheduled sync re-reads the last 3 days, so late changes are picked up.
Email campaign performance — sends, opens, clicks, bounces, unsubscribes.
Fields: name, status, type, send date, sends, opens, clicks, bounces, unsubscribes, forwards, and 5 more
Contact records — email, name, status, list memberships, tags.
Fields: email, first name, last name, status, source, created at, updated at, lists, tags
Contact lists (audiences) — name, description, membership count.
Fields: name, description, contact count, created at, updated at
How it works
No SQL or warehouse setup. Connect the source, then build the client’s report by asking Claude or ChatGPT.
In the client’s workspace, open Sources, add Constant Contact and choose the account to sync. If you don’t have access to the account, send the client a connect link where the platform supports one.
Maven pulls the client’s Constant Contact data (1 objects) and models it into documented tables. No SQL, warehouse or pipeline setup.
Build the client’s report or deck by asking Claude or ChatGPT through the MCP, set alerts on what matters, and publish to the client’s portal once you approve it.
Works well with
FAQ
Maven exposes 54 governed Constant Contact metrics, including Email Attributed Orders, Email Attributed Revenue, Email Bounces, Click Rate, Email Clicks and Open Rate — each defined once so it means the same thing in every report.
You can break Constant Contact metrics down by Channel, Account, Campaign type, Subject line, Title, Sender, Email list and Campaign, and more.
Yes. Constant Contact sits in the same client workspace as sources like Shopify, HubSpot, Facebook Ads, Google Ads and Google Analytics 4, so one report or question can use them together.
Maven syncs email campaigns from Constant Contact.
Maven refreshes Constant Contact on a schedule after the source is connected, and shows each source’s last sync time in the client’s workspace, so you can check the data is current before a report goes out.
Yes. Maven encrypts integration credentials and tokens, scopes access to the workspace, and uses the connection only to sync the reporting data needed for governed analytics.
Set up your first client, build their report by asking Claude or ChatGPT, and publish it to their portal.
Nothing is charged unless you subscribe.