Mailchimp AI Connector - Governed Audiences

Email Marketing

Mailchimp

Connect your AI to Mailchimp

Marketers manage audiences, campaigns, and engagement data across a platform that returns every subscriber's email, address, phone, IP, and coordinates on every API call. AI can draft campaigns, target segments, and surface cross-system ROI, but only if access is governed to match how your marketing operation actually runs.

‍

Why it matters

Capabilities that matter most for Mailchimp

Subscriber data, redacted

Field redaction keeps addresses, phone numbers, IPs and locations away from AI tools that don't need them, even though Mailchimp returns them on every call.

Campaigns beside revenue

Join Mailchimp campaigns and audiences with ecommerce or CRM lists to see which sends actually drove orders.

Nearly 50 ready-made API endpoints

Install Mailchimp endpoints and lookups from the app store for audiences, campaigns and members, ready to use straight away.

Use cases

Example AI Use Cases for Mailchimp

scenario

New and recent donors often never reach your Mailchimp audience, so they miss updates and appeals. Adding them by hand means exporting gifts, checking each email, and taking care not to re-add anyone who unsubscribed or was cleaned.

What popdock provides

Name the Mailchimp audience, a start date and the status to give new members, and it collects recent Bloomerang donors, ignoring refunds and counting those with no email. Each is checked against the audience, and anyone already there is left alone whatever their status, so unsubscribed and cleaned contacts are never added back. You see who will be added and with what status, with a reminder that subscribed is only for people who agreed to marketing email; pending, which sends a double opt-in email, is the default. Nothing is written until you confirm.

Business outcome

---

Recent donors join your Mailchimp audience with consent respected and no unsubscribed contacts added back.

scenario

You sent an appeal through Mailchimp and want to know who gave afterwards, and whether openers and clickers gave more than everyone else. Answering that means matching each recipient to Bloomerang and checking their gifts over the following weeks.

What popdock provides

Name the Mailchimp campaign and how many days to count, and it reads the recipients, their opens and who clicked. Each address is matched to a Bloomerang constituent by email, and gifts in the window after the send are read, ignoring refunds and never double counting an email linked to two accounts. You get donors and totals split by clicked, opened but did not click, and did not open, a table of each donor's gifts, and the campaign's open and click rates for context. It only reads, and says plainly that a gift after an email is correlation, not proof.

Business outcome

---

You learn whether your Mailchimp appeals are followed by gifts, split by how recipients engaged.

scenario

Your biggest donors may have unsubscribed, been cleaned from Mailchimp, or never been added, and nobody notices until an appeal falls flat. Checking means totalling giving per donor in Bloomerang, then looking each one up in Mailchimp and reading their open rates.

What popdock provides

Set a minimum total and a start date, and it totals Bloomerang giving per donor, excluding refunds, and keeps those at or above the threshold. Each donor is looked up in Mailchimp by primary email and then by any other address on the record. Every donor is rated engaged, quiet, unreachable, not in Mailchimp or no email from audience status and open rate, and the unreachable and missing groups get a suggestion of personal outreach. It only reads, says when record limits may understate totals, and shows the top ten instead if nobody reaches the threshold.

Business outcome

---

You know which major donors your Mailchimp emails reach, and who needs a phone call instead.

scenario

Fundraisers want to see in Bloomerang which donors clicked or opened the latest Mailchimp campaign. Logging that by hand means exporting activity, matching each address and checking nobody already has the interaction, which is too slow to do for every send.

What popdock provides

Name the Mailchimp campaign and whether clicks or opens count, and it reads who engaged along with their first activity date. Each address is matched to Bloomerang by email, unmatched addresses are reported, and anyone already logged for that campaign subject is skipped. You see a table of the interactions it will create, and nothing is written until you confirm. Each becomes an outbound email interaction with a note naming the campaign and the engagement, and if Bloomerang rejects a channel or purpose it stops and asks.

Business outcome

---

Email engagement shows on donor records after each campaign, ready for fundraisers to act on.

scenario

To know whether a donor reads your newsletters you need Mailchimp, and to see their gifts you need Bloomerang. A donor with two or three addresses makes it harder, because the bounce or unsubscribe may sit on the address you did not check.

What popdock provides

Give the donor's name or email, and it finds the constituent in Bloomerang, asking if several match, and collects every address not flagged bad. Each address is checked in Mailchimp for audience membership, status, rates, opens, clicks, bounces and unsubscribes, and recent gifts are read from Bloomerang. You get a short profile, an audience table and a dated timeline merging email activity with gifts, with any unsubscribe or hard bounce at the top. It only reads, and if the donor has no email it reports their giving alone.

Business outcome

---

You see one donor's email engagement and giving on a single timeline before deciding how to reach them.

scenario

People who buy from your online store are good candidates for giving, but their details sit in the store connected to Mailchimp, not in Bloomerang. Working out who is new means comparing customer emails with constituents by hand and checking who has agreed to marketing.

What popdock provides

Optionally set a minimum amount spent, and it reads store customers from Mailchimp with their orders, spend and opt-in status, then checks each email in Bloomerang. Customers with no constituent are listed by total spent, and customers already in Bloomerang whose names differ are listed separately. Anyone who has not opted in to marketing email is pointed out. It only reads and creates no constituents, and if no customers come back it checks whether a store is connected at all.

Business outcome

---

You get a ranked list of store customers to consider for donor outreach, with marketing consent made clear.

scenario

When donors unsubscribe or their address hard bounces in Mailchimp, fundraisers in Bloomerang keep emailing them without knowing. Carrying that across by hand means matching each address and adding a note, without noting the same event twice or recording a bounce that was only temporary.

What popdock provides

Choose a start date, and it reads Mailchimp unsubscribes and hard bounces, keeping the latest event per address and ignoring soft bounces. Each address is matched to Bloomerang by email, unmatched ones are reported, and constituents already noted for that event are skipped. You see the notes it will add with the event, date and reason, and nothing is written until you confirm. It adds notes only and does not change email records or constituents.

Business outcome

---

Fundraisers know which donors email no longer reaches, straight from the donor record.

scenario

Your Mailchimp audience and your Bloomerang donor list should line up, but donors go missing from the audience, unknown subscribers pile up, and some donors unsubscribed without anyone noticing. Comparing the two by hand is a large spreadsheet exercise.

What popdock provides

Name the Mailchimp audience, and optionally a constituent status, and it reads both sides and matches on email, checking secondary addresses in Bloomerang before calling anyone unmatched. You get four tables: constituents missing from the audience, audience members with no constituent, matched donors who are unsubscribed or cleaned, and names that differ, with counts. It only reads and recommends fixes without making them. If either side returns nothing, or a read hits its limit, it says so rather than reporting everyone as missing.

Business outcome

---

You see exactly where your email audience and donor records disagree, so cleanup is targeted.

scenario

Moving Capsule CRM contacts into a Mailchimp audience by hand means checking every email first. It is easy to re-add someone who unsubscribed, or to subscribe people who never agreed to hear from you.

What popdock provides

Name the Mailchimp audience, and optionally a Capsule CRM owner. It reads people with an email from Capsule CRM and checks each against the audience. Anyone already in it, whatever their status, is skipped, so unsubscribed and cleaned contacts are never re-added. You see who will be added and who was skipped before anything happens, and each new member is added as pending so Mailchimp asks them to confirm. Matching is by email only, and a run is capped at 100 additions.

Business outcome

---

Your audience grows from your CRM without breaking consent, because every new member confirms their own subscription.

scenario

An abandoned cart from a known customer is worth a personal follow-up, but the cart sits in Mailchimp while the relationship lives in Capsule CRM. Matching carts to contacts and creating tasks by hand means the moment passes before anyone calls.

What popdock provides

Choose how many days back to look and an optional minimum cart value. It reads recent Mailchimp abandoned carts, largest first, and matches each customer to Capsule CRM by email only. Contacts that already have a task for the cart are skipped, and unmatched customers are listed rather than created. You see each planned task with its owner, cart total and checkout link before anything is created, and nothing is written until you confirm.

Business outcome

---

High-value abandoned carts get a personal follow-up from the right owner while the customer is still deciding.

scenario

When a known contact clicks a Mailchimp campaign, their Capsule CRM owner should hear about it, but the click data never reaches the CRM. Building follow-ups means exporting clicks, matching emails and writing tasks one at a time.

What popdock provides

Name the campaign and how many days until tasks are due. It finds the campaign in Mailchimp, collects the people who clicked with the links they chose, and matches each to Capsule CRM by email only. Tasks go to each contact's owner, contacts with an open task for the campaign are skipped, and people not in Capsule CRM are listed but never created. You see every planned task before anything is created, and nothing is written until you confirm.

Business outcome

---

Owners follow up with contacts who showed interest in a campaign while the click is still recent.

scenario

Your Mailchimp audience and your Capsule CRM contacts drift apart over time, and engaged subscribers end up unknown to sales. Finding them means checking each subscriber's email against the CRM, one at a time.

What popdock provides

Name the Mailchimp audience and how many members to check. It reads the subscribed members, highest rated first, and looks up each email in Capsule CRM. You get totals for matched, missing and ambiguous members, a table of missing subscribers with their rating, open rate and tags, and the emails that match more than one record. Members that could not be checked are marked as not checked rather than missing, matching is by email only, and nothing is changed.

Business outcome

---

You see which engaged subscribers sales does not know yet, ranked by how engaged they are.

scenario

Your best online customers may have no contact or open deal in Capsule CRM, so nobody is managing the relationship. Finding them means comparing Mailchimp store spend against the CRM by hand, so their spend shows up in the store and in nobody's pipeline.

What popdock provides

Set a minimum spend and how many customers to check. It reads the Mailchimp store customers who spent the most and matches each to Capsule CRM by email only. They are split into three groups: not in Capsule CRM, in Capsule CRM with no open opportunity, and with open opportunities, with combined spend shown for the first two. Money is reported in the currency given, customers with no email are counted separately, and nothing is written.

Business outcome

---

Your highest spending customers get an owner and a sales conversation instead of being left to the store.

scenario

When a contact unsubscribes from a Mailchimp campaign, their Capsule CRM owner usually has no idea and keeps reaching out as before. Copying each unsubscribe and its reason into the CRM by hand rarely gets done.

What popdock provides

Choose how many days back to look, and optionally a campaign name. It reads recent Mailchimp unsubscribes and matches each to Capsule CRM by email only, skipping contacts that already have a note for that unsubscribe. You see each note with the campaign, date and reason before anything is written, and nothing is saved until you confirm. Unmatched people are listed, and nobody is resubscribed in Mailchimp.

Business outcome

---

Owners can see who has opted out and why, before they reach out to that contact again.

scenario

To understand one contact you check Capsule CRM for their deals, tasks and history, then Mailchimp for their audiences, clicks and orders. That is two systems and a lot of scrolling, and connecting the dots is still left to you.

What popdock provides

Give an email address and how far back to look. It finds the person in Capsule CRM with their recent history, open tasks and open opportunities, then reads their Mailchimp audiences, campaign opens and clicks, and store orders. The profile ends with up to five signals, such as an open opportunity whose contact unsubscribed or a buyer with no CRM record. Matching is by email only, a missing record in either system is stated plainly, and nothing is changed.

Business outcome

---

You get one profile of a contact across sales and marketing, with the signals that need attention called out.

scenario

A campaign report shows who clicked, but not which clickers are customers, who owns them or whether they have a deal open. Answering that means looking up each email in Capsule CRM by hand, and by the time it is done the interest has cooled.

What popdock provides

Name the Mailchimp campaign and how many people to cover. It collects the clickers with their click counts and links, then matches each to Capsule CRM by email only. The table shows owner, last contacted date and open opportunities, with clickers who have open deals first and people not in Capsule CRM last. Ambiguous matches are flagged, missing people are listed but not created, and nothing is changed.

Business outcome

---

Campaign clicks turn into a ranked follow-up list, starting with contacts who already have deals in progress.

scenario

Targeting a DonorPerfect group in Mailchimp, such as major donors or event attendees, means exporting the flagged donors, checking who is actually in the audience and adding them to a segment one by one. Adding someone who unsubscribed is a compliance problem.

What popdock provides

Name the DonorPerfect flag and the Mailchimp segment or tag, and it confirms the segment exists and is static, stopping if it cannot take members directly. It reads the flagged donors with an email and skips those already in the segment. Only members of the segment's audience who are subscribed or pending are added, never anyone unsubscribed or cleaned. You see the donors to add and the counts left out, nothing is written until you confirm, and DonorPerfect is not changed.

Business outcome

---

Flagged donor groups become targetable in Mailchimp without ever adding someone who opted out.

scenario

Donors entered in DonorPerfect do not appear in your Mailchimp audience until someone exports and imports them. Doing it by hand risks adding people twice or, worse, re-adding someone who unsubscribed or whose address was cleaned.

What popdock provides

Name the Mailchimp audience and optionally a minimum lifetime giving level, and it reads DonorPerfect donors with an email and keeps only those with no member record in that audience at all. Anyone present as unsubscribed or cleaned is skipped and never re-added. You confirm the list, and can remove rows, before donors are added as pending by default so they receive a double opt-in, with subscribed used only when you confirm you have consent. Each addition is read back to confirm it.

Business outcome

---

New donors reach your Mailchimp audience with consent respected, and opted-out donors stay out.

scenario

After a Mailchimp appeal goes out, the question is whether it brought in gifts, but opens and clicks are in Mailchimp and gifts are in DonorPerfect. Matching recipients to donors and checking gift dates by hand is tedious and usually skipped.

What popdock provides

Name the campaign and an attribution window, 14 days by default, and it reads the campaign report, collects everyone who opened or clicked, and matches each email to a DonorPerfect donor or address. Gifts and pledge payments within the window after the send date are totalled, with pledge totals left out. You get a headline, a table of givers and totals split between clickers and openers. It is read-only and says clearly that this is correlation within a window, not proof the email caused the gift.

Business outcome

---

You see what giving followed each Mailchimp appeal, measured honestly, to guide your next campaign.

scenario

Donors with an email address on file in DonorPerfect should be hearing from you through Mailchimp, but nobody checks until a newsletter goes out light. Comparing the donor base with the audience by hand means checking each address one at a time.

What popdock provides

Name the Mailchimp audience and optionally a minimum lifetime giving level, and it reads DonorPerfect donors with an email and checks each against the audience, matching addresses regardless of case or spacing. Donors are sorted into not in the audience, in it but unsubscribed or cleaned, and subscribed or pending. The missing donors are listed by lifetime giving, with a note when results hit the read limit. Nothing is added or changed in either system.

Business outcome

---

You know exactly which donors are not hearing from you by email, ranked by giving, before deciding who to add.

scenario

Bouncing emails in Mailchimp usually mean a wrong address in DonorPerfect, but nobody connects the two until a major donor misses an important appeal. Finding which donor holds each bad address, and where it is stored, means searching record by record.

What popdock provides

Choose a lookback period, 30 days by default, and it reads Mailchimp bounces, grouping by email with the latest date, type and number of campaigns that bounced. Each address is matched to a DonorPerfect donor or an additional address record, showing where it is held. Hard bounces and repeated soft bounces are listed, ranked by lifetime giving, and single soft bounces are left out as temporary. It is read-only, so staff decide what to correct.

Business outcome

---

Your most valuable donors with a bad email address are corrected first, before the next appeal goes out.

scenario

When a donor unsubscribes in Mailchimp, staff working in DonorPerfect have no idea and may still email them directly. Carrying each unsubscribe across means matching addresses to donors and setting a flag by hand, which falls behind quickly.

What popdock provides

Name the DonorPerfect flag and a lookback period, 30 days by default, and it confirms the flag is active, reads recent Mailchimp unsubscribes and matches each email to a donor. Donors already flagged are skipped, and an email matching several donors is held until you pick. You see the donors to flag with the unsubscribe date, campaign and reason, and nothing is written until you confirm. No one is ever resubscribed in Mailchimp.

Business outcome

---

Staff respect every Mailchimp unsubscribe in DonorPerfect too, keeping outreach compliant and donor trust intact.

scenario

A donor who clicks a link in your Mailchimp appeal is showing interest your fundraisers should know about, but that signal never reaches DonorPerfect. Logging each click as a contact by hand is tedious, and running it twice clutters the history.

What popdock provides

Name the Mailchimp campaign and an activity code, and it confirms the code is active, finds the campaign and collects each clicker's first click date and the links clicked. Each email is matched to a DonorPerfect donor, and anyone already logged with that code since the send date is skipped, so reruns are safe. You confirm the list before one new contact is logged per donor, never overwriting an existing contact record.

Business outcome

---

Fundraisers see which donors engaged with each appeal right in DonorPerfect, ready for timely follow-up.

scenario

Before calling a donor about an email appeal, you need to know whether they even receive your email. Their giving is in DonorPerfect and their subscription status, opens, clicks and bounces are in Mailchimp, so getting the full picture means two systems and several screens.

What popdock provides

Give an email address and a lookback period, 90 days by default, and it finds the donor in DonorPerfect, including through an additional address, and lists candidates if several match. It reads their giving and open pledges, then their Mailchimp audiences, status, engagement rates, recent opens, clicks, bounces and any unsubscribe. Observations call out mismatches such as an active donor who unsubscribed or an engaged subscriber who has never given. It is read-only.

Business outcome

---

You understand a donor's giving and email engagement together before reaching out, so the conversation fits.

scenario

Keeping a Mailchimp audience in step with Dynamics 365 Business Central customers means exporting emails, checking each against the audience and importing the rest. Do it carelessly and you re-add people who unsubscribed, include blocked accounts, or subscribe customers who never gave consent.

What popdock provides

Name the audience, and optionally a salesperson, and it finds Dynamics 365 Business Central customers with an email who are not blocked and not yet in the Mailchimp audience. Anyone already present is skipped whatever their status, so unsubscribed and cleaned contacts are never re-added. New members are added as pending by default, which sends Mailchimp's double opt-in, unless you state consent was given. You confirm the list first, at most 100 are added per run, and each add is checked afterwards. Nothing in Business Central is changed.

Business outcome

---

Your audience grows with real customers while unsubscribes stay respected and consent stays clean.

scenario

Abandoned cart reminders go to everyone by default, including shoppers whose accounts are blocked, overdue or already over their credit limit in Dynamics 365 Business Central. Checking each cart against the account by hand is slow, so most teams either chase every cart or none.

What popdock provides

Set a lookback period and an optional minimum cart value, and it lists open Mailchimp carts and looks each shopper up in Dynamics 365 Business Central by email. Each cart is labelled new shopper, blocked, overdue, over credit limit or good standing, with the credit test skipped when currencies differ. Carts are sorted by value, checkout links are shown only for carts worth chasing, and the rest are routed to the salesperson. Carts with no email are listed as unidentifiable. Nothing is sent or changed.

Business outcome

---

You chase the carts worth chasing and hand risky accounts to sales instead of sending them a discount.

scenario

Your most engaged Mailchimp subscribers are often warm prospects that sales has never heard of. Finding them means exporting highly rated members and checking each email against customers and contacts in Dynamics 365 Business Central, a job that rarely gets done.

What popdock provides

Name the audience and a minimum rating, and it reads subscribed Mailchimp members at or above that rating and checks each email against Dynamics 365 Business Central customers, then contacts. You get counts for each group and a lead list of members not in Business Central, sorted by rating and click rate, plus who already owns the ones that are contacts. If no one meets the rating it suggests a lower one. It reads only, and if you later ask to create contacts it confirms the list and job title first.

Business outcome

---

Sales gets a ready lead list of engaged subscribers nobody in Business Central is working yet.

scenario

Before you call or email someone, you want to know both sides of the relationship: are they subscribed, do they open campaigns, have they abandoned a cart, and do they owe money in Dynamics 365 Business Central. Getting that means logging into Mailchimp and Business Central and searching each by email.

What popdock provides

Give an email address, and it pulls Mailchimp audience memberships, status, tags, rating, recent campaign opens, store spend and open carts, then the Dynamics 365 Business Central customer or contact with balances, unpaid invoices and open orders. Emails are matched exactly, never on part of an address, and several matching customers are shown separately. A short summary flags overdue invoices, blocked accounts, abandoned carts or an unsubscribed status. Neither Mailchimp nor Business Central is edited.

Business outcome

---

You walk into any conversation knowing both the marketing engagement and the account standing behind one email.

scenario

Mailchimp reports the store revenue it attributes to a campaign, but finance trusts what Dynamics 365 Business Central actually invoiced. Comparing the two means listing the campaign's buyers, finding each as a customer and totalling their invoices in the weeks after the send.

What popdock provides

Name the campaign and a window after the send, and it reads Mailchimp's headline numbers and the orders it attributes to the campaign, then totals what Dynamics 365 Business Central invoiced each buyer in that window. You see both figures side by side, buyer by buyer, along with buyers not found in Business Central. Different currencies are never added together, and the report states that invoices in the window show correlation, not proof. Both systems are read and left as they are.

Business outcome

---

You put a finance-grade revenue figure next to a campaign, with honest caveats about attribution.

scenario

When a customer who spends heavily unsubscribes from your emails, their account manager should know. Without help, unsubscribes sit in Mailchimp while sales figures and owners sit in Dynamics 365 Business Central, and nobody connects the two until the customer has gone quiet.

What popdock provides

Set a lookback period, and it lists recent Mailchimp unsubscribes, keeping only the latest per email, then looks each one up in Dynamics 365 Business Central as a customer or contact. Customers are ranked by sales, with balance due, the campaign, the stated reason and the owning salesperson's name and email. Empty reasons stay blank rather than guessed. It never resubscribes anyone and changes nothing in either system.

Business outcome

---

Account owners hear about valuable customers who unsubscribed while there is still time to follow up personally.

scenario

Store customers synced into Mailchimp should line up with customers in Dynamics 365 Business Central, but they drift: buyers never set up, one email shared by two accounts, cities and phones that disagree. Spotting this by hand means comparing exports and ignoring endless formatting differences.

What popdock provides

Pick a start date, or use the last 90 days, and it matches Mailchimp store customers to Dynamics 365 Business Central by email. Each is classed as matched, missing or ambiguous, and matched rows are checked for city, country and phone differences, comparing countries by meaning and phones on digits so formatting is never flagged. Blocked customers are noted, missing customers are sorted by spend, and runs over 200 cover the newest and say how many were left. It reports and never edits a customer.

Business outcome

---

Customer records stay aligned between the store sync and finance, with the highest-spending gaps fixed first.

scenario

Sending a promotion to a customer who is months overdue in Dynamics 365 Business Central sends the wrong message. Keeping a Mailchimp suppression segment current means exporting overdue accounts, checking which are audience members and adding them one by one.

What popdock provides

Name the audience, a static segment and a minimum overdue amount, and it finds Dynamics 365 Business Central customers with an overdue balance and an email. It stops if the segment is missing or not static, skips anyone already in it, and lists people who are not audience members since they cannot be added. You confirm the list before anything is written, each add is checked afterwards, and nothing is changed in Business Central. It only adds, and the report reminds you that customers who have since paid are not removed.

Business outcome

---

Overdue accounts stay out of promotional sends, with every addition confirmed by you first.

scenario

Keeping a Mailchimp audience in step with your Dynamics GP customers means exporting emails, comparing them with the audience, and importing the gaps. Do it carelessly and you resubscribe people who opted out, or add customers without consent.

What popdock provides

Name the Mailchimp audience, and optionally a GP customer class, and it reads active Dynamics GP customers with an email and every audience member, whatever their status. Only customers not in the audience at all are proposed, so anyone who unsubscribed or was cleaned is never re-added. New members are added as pending, which sends a double opt-in email, unless you state you have consent. You confirm the list or drop rows first, it stops at the first error, and each row is reported as added or failed.

Business outcome

---

Your audience covers current customers without resubscribing anyone who opted out or skipping consent.

scenario

Before calling a customer, you might want both sides: what they owe and order in Dynamics GP, and whether they read your Mailchimp campaigns or buy in the store. That means two systems, an email to carry across, and a lot of clicking.

What popdock provides

Give a Dynamics GP customer ID, name or email, and it finds the customer in GP and reads open and past-due receivables and recent sales documents. Using the customer's email it reads their Mailchimp audience status and tags, store orders, and recent opens and clicks. The profile ends with anything worth acting on, such as a customer on hold who is still clicking campaigns. If the customer has no email it says Mailchimp could not be checked, and nothing is changed in either system.

Business outcome

---

Sales and finance see a customer's account and marketing engagement together before the next conversation.

scenario

Marketing wants to know whether a Mailchimp campaign led to sales, but orders live in Dynamics GP. Matching recipients to customers by email and checking each one's orders in the weeks after the send is too slow to do for every campaign.

What popdock provides

Name a sent Mailchimp campaign and a window in days, and it reads the recipients and who clicked. Recipients are matched to Dynamics GP customers by email, and each match's orders and invoices in the window after the send are read, ignoring quotes. You get a summary of matched customers, clickers and sales value, a table per buying customer, and clickers who have not bought with their salesperson. It states that a sale after a send is correlation, not proof, and nothing is changed.

Business outcome

---

Marketing sees which campaigns are followed by real orders, and sales gets a list of interested clickers to call.

scenario

When a customer unsubscribes or hard-bounces in Mailchimp, sales and receivables in Dynamics GP never hear about it. They keep emailing an address that bounces, or contact someone who asked not to be, because the customer record says nothing.

What popdock provides

Set a lookback window, and it reads recent Mailchimp unsubscribes with their reason and campaign, plus hard bounces, and matches them to Dynamics GP customers by email. You see each proposed note, one per customer even when there are several events, and confirm or drop rows. Notes are appended with the date and time, never replacing an existing note, and each row is reported as noted or failed. It mentions that hard bounces are not limited to the window, and it never resubscribes anyone.

Business outcome

---

Your GP customer records show who opted out or bounced, so teams stop contacting them the wrong way.

scenario

Your Dynamics GP customer list and Mailchimp audience drift apart: new customers never get added, some have unsubscribed, and some have no email at all. Spotting the gaps means exporting both, cleaning emails and comparing them in a spreadsheet.

What popdock provides

Name the Mailchimp audience, and optionally a GP customer class or salesperson, and it reads active Dynamics GP customers and every audience member. Matching is on email only, never on name, and GP email fields holding several addresses are split. You get customers missing from the audience, customers in it but not subscribed with their status and reason, customers with no email, and a count of members who match no customer. It warns when the customer read may be truncated, and nothing is changed.

Business outcome

---

You know exactly where your customer list and audience disagree before planning the next campaign.

scenario

A Mailchimp campaign creates interest, but the clicks never reach the salespeople who own those customers in Dynamics GP. Turning a click report into a follow-up list means matching emails to customers, finding each salesperson and checking whether the account is on hold.

What popdock provides

Name the Mailchimp campaign, and optionally a salesperson, and it reads everyone who clicked, with click counts, dates and links. Clickers are matched by email to active Dynamics GP customers, and each customer's salesperson is looked up. You get one section per salesperson with contact details, links clicked, balance and a flag for credit hold, an unassigned section where needed, and clickers who are not customers yet as possible prospects. It sends no email and changes nothing.

Business outcome

---

Every engaged customer reaches the right salesperson for follow-up, with prospects listed alongside.

scenario

Customers on credit hold in Dynamics GP still receive Mailchimp promotions encouraging them to order. Keeping a segment of held accounts up to date by hand means exporting holds, matching emails and adding members one by one.

What popdock provides

Name the Mailchimp audience and a static segment or tag, and it checks both exist and that members can be added. It reads active Dynamics GP customers on hold and matches them by email to audience members, skipping those already in the segment. You see the proposed additions with balances, and held customers not in the audience separately, and confirm or drop rows. Only existing members are added to the segment, each row is reported, and holds in GP are never changed.

Business outcome

---

Campaigns can exclude or target held accounts, so customers on hold are not urged to place new orders.

scenario

Customers keep being added in Dynamics SL, but the Mailchimp audience only grows when someone exports a file, removes the people already there and imports the rest. Done by hand it is easy to re-add people who unsubscribed or to subscribe customers without consent.

What popdock provides

Name the Mailchimp audience, and optionally a customer class, and it reads active Dynamics SL customers with a valid email and checks each one against the audience. Only customers with no row at all qualify, so unsubscribed and cleaned contacts are never re-added. You review the list and the status they will get, pending by default so each gets an opt-in email, and nothing is added until you confirm. Each added member is then looked up again to prove it landed.

Business outcome

---

New customers reach your Mailchimp audience with consent respected and past unsubscribes left alone.

scenario

Collections emails go out to customers who unsubscribed months ago or whose address bounced, and nobody notices because the balances live in Dynamics SL and the email status lives in Mailchimp. The money owed by customers you cannot reach by email is the part that needs a phone call.

What popdock provides

Give a minimum balance and it reads Dynamics SL customers at or above it, with aged balances and average days to pay, then takes each email into Mailchimp. It reports whether each customer is subscribed, unsubscribed, cleaned or absent, and for subscribed customers when they last opened or clicked in the past 90 days. A summary shows how much of the balance sits with engaged, silent and unreachable customers. Nothing in Mailchimp is changed.

Business outcome

---

Collections effort goes to the right channel, with unreachable balances flagged for a phone call instead of another email.

scenario

To decide whether email is worth it for a particular customer, you need their Dynamics SL account position and their Mailchimp history side by side. That means finding them in SL, copying each address, then reading audiences, opens, clicks and unsubscribes in Mailchimp.

What popdock provides

Name a Dynamics SL customer by ID or name and it finds them, asking you to choose if several match. It reads their balance, credit limit, aged debt and recent orders, then carries every email on the record into Mailchimp for audiences, status, tags, open and click rates, recent activity and any unsubscribe. No activity is reported as no activity rather than dressed up as engagement, and name differences between the systems are noted. It ends with one sentence on whether email works for this customer. Nothing in Dynamics SL or Mailchimp is changed.

Business outcome

---

You know whether email reaches a customer before you rely on it for an offer or a reminder.

scenario

After a Mailchimp campaign you can see who clicked, but not whether those people went on to place sales orders in Dynamics SL in the weeks that followed. Linking them means exporting clickers, matching emails to customers and searching sales orders for the weeks after the send.

What popdock provides

Name a sent Mailchimp campaign and a number of days, and it reads the campaign results and everyone who clicked. Clickers are matched to Dynamics SL customers by email, with name matches kept separate as unconfirmed, and the sales orders each matched customer placed in the window after the send are totalled. You get the campaign headline numbers, match counts and a table of customers with their clicks and orders. It says plainly that these are orders that followed a click, not orders caused by it. It reads from Dynamics SL and Mailchimp but writes nothing back.

Business outcome

---

You see the order value that followed a campaign, stated honestly as correlation rather than attribution.

scenario

Your Mailchimp audience is supposed to cover your active customers, but nobody knows how many are missing, unsubscribed or bounced. Finding out means exporting Dynamics SL customers and checking each email against the audience by hand, then working out which status each one has.

What popdock provides

Name the audience, and optionally a customer class and state, and it reads active Dynamics SL customers and checks each email against that Mailchimp audience. Each customer is classed as subscribed, pending, unsubscribed with the reason, cleaned or missing, and customers with no usable email are counted apart. If every customer comes back missing it checks the audience name before reporting. Results capped at 500 are flagged. No record in Dynamics SL or Mailchimp is touched.

Business outcome

---

You know exactly which active customers your audience misses or cannot reach, before planning the next send.

scenario

When a customer unsubscribes from your emails, their salesperson rarely hears about it, even if the customer has open orders or a large balance in Dynamics SL. Spotting the ones that matter means matching Mailchimp unsubscribes to customers and checking their accounts.

What popdock provides

Give a lookback period and it reads recent Mailchimp unsubscribes with the campaign and reason, then matches each to a Dynamics SL customer by email, keeping company name matches apart as unconfirmed. For each matched customer it reads the current balance and open orders. You get a table sorted by balance with salesperson and phone, and a closing note on who most warrants a call. Nobody is resubscribed and nothing is changed.

Business outcome

---

Salespeople hear when a customer with live business stops reading your emails, while there is still time to call.

scenario

To send a payment reminder only to customers who owe money, someone exports balances from Dynamics SL, matches emails to Mailchimp and tags each contact by hand. It is easy to tag someone who unsubscribed or to forget to untag customers who have since paid.

What popdock provides

Name the audience and an existing static tag, plus a minimum balance, and it reads Dynamics SL customers at or above it and finds their emails in that audience. Only subscribed contacts not already tagged go forward, and you see the list with counts of everyone skipped and why. Nothing is tagged until you confirm, then the tag is read back. It never subscribes anyone or creates the tag, and it lists tagged contacts with no balance left so you can untag them.

Business outcome

---

Payment reminders reach only subscribed customers who actually owe money, with paid-up contacts flagged for untagging.

scenario

Keeping a Mailchimp audience in step with your Sage Intacct customers means exporting emails, comparing them with the audience and importing the gaps. Do it carelessly and you re-add people who unsubscribed or were cleaned, or add people without the consent Mailchimp requires.

What popdock provides

Name the audience, and it finds active Sage Intacct customers whose email is not in that Mailchimp audience, using contact names where exactly one contact matches rather than guessing. New people are added as pending, so they get a double opt-in email, unless you choose otherwise, and choosing subscribed asks you to confirm you have consent. Anyone already in the audience, including unsubscribed or cleaned addresses, is skipped and listed. You confirm the plan before anyone is added, and each add is checked afterwards.

Business outcome

---

Your audience covers every active customer without ever re-adding someone who unsubscribed or skipping consent.

scenario

Collections reminders sent by email often go nowhere because the customer unsubscribed, the address bounced or it was never in your mailing system. Checking every overdue customer's contacts against Mailchimp by hand takes so long that teams just send and hope.

What popdock provides

Set how many days overdue to look at, and it lists Sage Intacct customers with past-due invoices, gathers every email on the customer and its contacts, and checks each one in Mailchimp. Addresses are sorted into reachable, opted out, bad address or not in Mailchimp, using audience status and recent hard bounces. The report ranks customers by overdue total and lists who needs a phone call or a new address. It is read-only and treats Mailchimp status as evidence, not a legal opinion.

Business outcome

---

Collections knows up front which email reminders will land and who needs a phone call instead.

scenario

When a store buyer known to Mailchimp needs to become a billing customer, someone retypes their details into Sage Intacct. Without checking first it is easy to create a second customer for someone already set up under a business name or a contact record.

What popdock provides

Give the buyer's email, and it reads the Mailchimp store customer, then searches Sage Intacct by contact email, company name and any customer ID you supplied. If a matching customer exists or the ID is taken, it shows it and stops rather than creating a duplicate. You review and can correct the values, with fields left blank rather than guessed, and nothing is written until you confirm. The new customer is then read back from Intacct to prove it exists.

Business outcome

---

Store buyers become billing customers in one step, without duplicate records in your ledger.

scenario

Finance sees a customer's invoices in Sage Intacct, marketing sees their engagement in Mailchimp, and nobody sees both. Before chasing a late payer or planning outreach, you end up asking two teams and matching email addresses yourself.

What popdock provides

Name the customer, and it reads their status, terms, credit limit and open invoices from Sage Intacct, then gathers every email on the account and its contacts. Each address is looked up in Mailchimp for audience status, rating, open and click rates, recent opens, clicks and bounces, campaign unsubscribes and store spend. You get one profile with a few plain observations, such as an overdue customer whose only address is unsubscribed. Nothing is changed, and if Mailchimp is unavailable you still get the Intacct half.

Business outcome

---

Finance and marketing work from the same view of a customer, so outreach and collections stop working against each other.

scenario

Store buyers show up in Mailchimp e-commerce data long before anyone sets them up in Sage Intacct, and some never get set up at all. Matching store customers to billing customers by email and company name by hand is slow, and a loose company match produces false links.

What popdock provides

Set a minimum order count, and it lists Mailchimp store customers and looks each one up in Sage Intacct by contact email first, then by company name. A company name alone never counts as a match, so customers are sorted into matched, possible match and not in Intacct. For matched customers it sets store spend next to invoiced totals and flags buyers Intacct has never invoiced. It only reads and points you to a separate step for creating any missing customers.

Business outcome

---

You see which paying store buyers are missing from your ledger, ranked by spend, without a manual matching exercise.

scenario

Marketing keeps sending promotions to customers who are well behind on their invoices, because overdue status lives in Sage Intacct and the mailing list lives in Mailchimp. Building an exclusion tag means pulling overdue accounts, finding their emails and tagging each one by hand.

What popdock provides

Name the overdue threshold, the audience and an existing static tag, and it finds Sage Intacct customers past due and collects every email on the account and its contacts. Only people already in the Mailchimp audience are tagged, so nobody is ever added to the audience itself, and anyone already tagged is skipped. You see the plan with each member's status and confirm before any tag is applied, then each one is checked to make sure it landed. It stops if the tag does not exist or is condition based.

Business outcome

---

Marketing can exclude or target overdue customers from a reliable tag, kept in step with your receivables.

scenario

After a campaign goes out, marketing can see clicks in Mailchimp but not whether those people went on to buy, because orders and invoices live in Sage Intacct. Matching clickers to customers and pulling their sales for the following weeks is a long manual job.

What popdock provides

Name a sent Mailchimp campaign and a window of days, and it collects everyone who clicked, matches their emails to Sage Intacct customers and groups several clickers from the same company. For each matched customer it lists the sales orders and invoices in the window and totals the invoiced amount, without double counting an order and the invoice it became. It reports unmatched clickers, cuts the window at today, and states plainly that this shows what followed, not that the campaign caused it. Nothing is changed.

Business outcome

---

You can show what clicking customers went on to buy after a campaign, with an honest invoiced total.

scenario

Adding someone to a Mailchimp audience by hand looks harmless, but if they unsubscribed earlier you can quietly re-subscribe them against their wishes, or create a second record for someone already there. Adding a tag at the same time means another search for the right segment.

What popdock provides

Give an email address, the audience and optionally a name and tag, and it checks Mailchimp for an existing member first. People already subscribed or pending are not added again, and anyone who unsubscribed or was cleaned is never re-added; you are told they must opt in again themselves. New contacts go in as pending, which sends a double opt-in email, unless you state they already consented. The tag must exist and be static. You confirm before anything is written, and the contact's status and tags are read back.

Business outcome

---

New contacts join your audience once, and people who opted out are never re-subscribed by mistake.

scenario

Abandoned carts are lost revenue, but knowing which ones are worth chasing means checking each shopper's history and whether they can legally be emailed. It is also easy to miss that a store's cart recovery automation was never switched on.

What popdock provides

Choose a lookback period and an optional minimum cart value, and it reads your Mailchimp stores and recent abandoned carts, totalling them per store in each store's currency. For the ten highest-value carts it checks whether the shopper is returning or new and whether they are subscribed to the store's audience. You get the reachable value against the unreachable, and the first recommendation is to switch on cart recovery for any store without it. It never suggests emailing someone not subscribed, and changes nothing.

Business outcome

---

You see how much abandoned revenue you can actually recover by email, and which stores are missing cart recovery.

scenario

A Mailchimp audience can shrink or go cold for months before anyone notices, because growth, churn, bounces and pending confirmations each sit on a different report. By the time open rates drop, the list has already lost much of its value.

What popdock provides

Name the audience and how many months to look back, and it reads the Mailchimp audience's rating, rates and last send, month-by-month growth and churn, the last 30 days of sends and bounces, unconfirmed contacts and its segments and tags, flagging empty ones. It weighs signals such as two or more months of net loss, rising cleaned addresses, no send in 90 days or hard bounces over 2 percent. You get a verdict of healthy, watch or at risk with 2 to 4 recommendations. No member addresses are listed and nothing is changed.

Business outcome

---

You know whether your audience is growing or decaying, with specific fixes, before it hurts your next send.

scenario

Classic Mailchimp automations run quietly for months, and nobody checks whether an email in the middle was left paused or never sends because of its delay. Engagement can fall off a cliff partway through a sequence without anyone seeing it.

What popdock provides

Name an automation, or review every running one, and it reads each Mailchimp automation and its emails in order, with delay, status, sends, opens and clicks. It flags paused or unsaved emails inside a running sequence, emails nobody is reaching, and open rates that more than halve from one step to the next, plus automations left paused. Recommendations name the automation and email each applies to. It notes that customer journeys and store cart automations are not covered, and changes nothing.

Business outcome

---

Broken steps and drop-off points in your automations are found and fixed instead of silently losing contacts.

scenario

Reporting on a month of email campaigns means opening each Mailchimp report, copying the numbers into a spreadsheet and working out weighted rates. Campaigns with abuse reports or high bounces can slip by when you only look at the averages.

What popdock provides

Choose a lookback period and optionally an audience, and it reads every Mailchimp campaign sent in that window and totals sends, opens, clicks, unsubscribes, abuse reports and revenue, with open and click rates weighted by emails sent. It ranks the best and worst campaigns by click rate, ignoring tiny sends, and the top earners. Campaigns with abuse reports, hard bounces over 2 percent or unsubscribes over half a percent are flagged. It will not call a trend from fewer than three campaigns, and changes nothing.

Business outcome

---

Your email results for the period are summarized and ranked, with problem campaigns flagged, ready to share.

scenario

When someone asks what you know about a contact, the answer is spread across Mailchimp audiences, tags, campaign activity, unsubscribes, store orders, carts and survey responses. Checking every screen by hand is slow, and loose searches can pull up other people's data.

What popdock provides

Give an email address, and it gathers that contact's audiences with status, tags and rating, segment memberships, recent opens, clicks and bounces, campaign unsubscribes, store orders with the campaign each is attributed to, open carts and survey responses. If they are unsubscribed or cleaned anywhere, that is shown at the top. It uses exact email matches only so no one else's data appears, says which sections had no data, and never guesses alternative spellings. Nothing is changed.

Business outcome

---

You can answer any question about one contact from a single profile, without exposing anyone else's data.

scenario

Your best store customers should be subscribed, engaged and marked as VIPs, but nobody checks. A top spender who unsubscribed, or is drifting away, is often only noticed after their orders stop.

What popdock provides

Set how many customers and a minimum order count, and it ranks Mailchimp store customers by total spent, within each currency, and checks each one's audience status, VIP flag, rating and open rate. It notes which campaigns and automations their orders are attributed to. Top customers who are missing from the audience, unsubscribed, not marked VIP or opening under 10 percent are flagged. It recommends marking VIPs or re-engaging people but does not make the change.

Business outcome

---

Your highest-value customers are recognized and kept engaged, rather than found missing after they stop buying.

scenario

When someone asks to stop receiving email, you have to find every Mailchimp audience they are in and every store record that holds marketing consent. Miss one and they keep getting mail; search loosely and you might unsubscribe someone else.

What popdock provides

Give the email address, and optionally one audience and a reason, and it finds every Mailchimp audience membership and store customer record for that exact address. You see a table of what will change, and nothing is touched until you confirm. Each membership is set to unsubscribed with the reason recorded, and store marketing consent is withdrawn, changing nothing else. It never re-subscribes anyone, never guesses at a misspelt address, and reads every record back to show the final status.

Business outcome

---

Opt-out requests are honored everywhere the address appears, with a record of each change for your files.

scenario

After a campaign goes out, the question is always whether it did better or worse than usual and why. Answering it means opening the report, finding earlier campaigns to the same audience, working out averages and digging through clicks, bounces and unsubscribes.

What popdock provides

Name a sent campaign, and optionally how many earlier ones to compare, and it reads its Mailchimp report, link clicks, hard and soft bounces and unsubscribe reasons. It averages recent campaigns to the same audience to give a baseline, and shows each metric against it with a one-line verdict. The top links and grouped unsubscribe reasons follow, with observations tied to the numbers. Abuse reports and high bounce or unsubscribe rates are called out on their own, few individual addresses are shown, and nothing is changed.

Business outcome

---

You know whether a campaign beat your usual results and what drove it, in a single read.

scenario

Starting or pausing a Mailchimp automation is a single click, but it affects every contact in the sequence. Start the wrong one and emails go to people who should not get them; pause one that was never running and nothing happens while you think it did.

What popdock provides

Say start or pause and name the automation, and it finds exactly one match in Mailchimp and checks its current state, stopping if it is already running, already paused or has never run. It lists the emails in order and explains exactly what the change will do, including when a start is the first ever. Nothing happens until you clearly confirm, then one change is made to that one automation and its new status is read back.

Business outcome

---

Automations change state only when you mean them to, with the effect on your contacts spelled out first.

scenario

Resending a campaign to people who did not open it means exporting the recipient list, filtering out opens and bounces, importing them into a tag and copying the campaign. Done by hand it takes an hour and often includes people who bounced.

What popdock provides

Name a sent campaign and an existing static tag, and it finds every recipient who did not open it, leaving out bounces. You see how many will be tagged and a sample, with a reminder that privacy features hide some opens, and confirm before anyone is tagged; very large lists need the number confirmed. It then reports the new tag size and, only after a second yes, copies the campaign as a draft. Nothing is sent and nobody's subscription status changes.

Business outcome

---

Your resend reaches the people who missed the first email, set up in minutes and never sent without you.

scenario

Getting your Pipedrive contacts into a Mailchimp audience usually means exporting people for an owner or account, cleaning the list and importing it. Along the way it is easy to re-add people who unsubscribed or skip the consent Mailchimp requires.

What popdock provides

Name a Pipedrive owner or organization, or both, and the audience, and it reads the matching Pipedrive people and checks each email in that Mailchimp audience. People already subscribed or pending are skipped, and anyone unsubscribed or cleaned is never re-added. You see the plan and confirm before anything is written, then each new person goes in as pending so Mailchimp sends a double opt-in email, unless you state they already consented. Every add is checked afterwards, and Pipedrive is only read.

Business outcome

---

Sales contacts reach your marketing audience with consent intact and no opted-out person re-added.

scenario

People who click a campaign are showing interest, but turning them into Pipedrive leads means exporting clicks, checking who is already in the CRM and entering the rest by hand. Clickers fall through the gap, or the same person gets entered twice.

What popdock provides

Name the Mailchimp campaign, and optionally an owner, and it collects the people who clicked and drops anyone already in Pipedrive. Names and companies come from the campaign recipients, and people with no name are skipped. Each person is linked to an existing organization only when exactly one matches, and organizations are never created. You confirm the plan, then each person is created and read back before a lead is added to the Leads Inbox, and nobody is created twice in one run.

Business outcome

---

Interested campaign clickers become owned Pipedrive leads the same day, without duplicates or stray organizations.

scenario

Your best Mailchimp store customers should all have an owner in Pipedrive and a recent conversation with sales. Checking means taking each email from the store, searching Pipedrive for the person and then the company, and reading their deals and last activity, so high spenders slip through when no one owns them or nobody has called in months.

What popdock provides

Set a minimum spend and how many customers to check, and it takes your top Mailchimp store customers by total spent and looks each one up in Pipedrive by email. Where the person is missing, it checks whether their company already exists as an organization. Each customer is marked covered, stale, organization only or missing, with the spend in each group and the five highest spenders needing attention listed first. Amounts in different store currencies are never added together, and nothing in either system is changed.

Business outcome

---

Sales sees which high-value buyers have no owner or no recent contact, ranked by what they spend.

scenario

When a contact unsubscribes from your Mailchimp emails, the rep working their open Pipedrive deal usually never hears about it. Finding out means exporting unsubscribes, searching each email in Pipedrive and checking for deals, and by then the rep may have sent another email the buyer asked not to get.

What popdock provides

Choose how many days to look back and it reads recent Mailchimp unsubscribes, keeps the latest per email, and matches each to a Pipedrive person. People on open deals come first, grouped by owner so each rep sees their own contacts, with the campaign and reason beside them. If you ask, it adds a note of the unsubscribe to each matched person, but it skips anyone who already has that note, shows you the list and writes only after you confirm. It never tries to resubscribe anyone.

Business outcome

---

Reps learn which of their deal contacts opted out of email, so the next touch respects that choice.

scenario

Before a call with an account, you want to know which of its people actually read your emails. That means listing the organization's contacts in Pipedrive, searching each one in Mailchimp and counting opens and clicks by hand, while a key contact on an open deal may have unsubscribed months ago without anyone noticing.

What popdock provides

Name a Pipedrive organization and it finds the account, asking you to choose if the name matches more than one, then reads its people and open deals. Each contact's email is looked up in Mailchimp for audience status, opens and clicks over your chosen window. You get a table sorted by clicks with the linked open deal, the most engaged contact, and the deal contacts who are unsubscribed, missing from Mailchimp or have no email at all. It only reads both systems.

Business outcome

---

You walk into an account conversation knowing who is engaged and which deal contacts email can no longer reach.

scenario

Getting a full picture of one contact means opening their Pipedrive record for deals, activities and notes, then switching to Mailchimp for audiences, opens, clicks and store orders. The two screens rarely get read together, so a buyer with open deals who unsubscribed last month looks like any other contact.

What popdock provides

Give an email address and it reads the Pipedrive person with their owner, open activities, recent notes and open deals, then pulls their Mailchimp audiences, recent opens and clicks, unsubscribes and store spend. If more than one Pipedrive person shares the email, it lists them and stops rather than guessing. The profile ends with a short assessment of email engagement, sales activity and one suggested next step, and an unsubscribed contact on open deals is raised first. Nothing is written to either system.

Business outcome

---

One read gives you the whole relationship, sales and email side by side, with a next step already suggested.

scenario

A campaign click is a buying signal, but turning clicks into Pipedrive follow-ups means pulling the click report, finding each person in Pipedrive, checking whether someone already has a call booked and creating activities one at a time. Miss the check and a contact gets two reps calling about the same email.

What popdock provides

Name the Mailchimp campaign, and optionally the activity type and how many days out it is due, and it collects everyone who clicked and matches them to Pipedrive people by email. Anyone who already has an open activity is skipped, and people not in Pipedrive are listed but never created. You see the plan for each person before anything is written, then one activity per person is added with the links they clicked in the note. The activities are read back so you see which exist and which failed.

Business outcome

---

Every engaged clicker gets one timely follow-up with context, and nobody already in a conversation is booked twice.

scenario

Your billing contacts in Rillet and your Mailchimp audience drift apart as customers are added. Closing the gap means comparing two exports by email, and the risk is real: re-adding someone who unsubscribed or was cleaned overrides their consent and can hurt your sender reputation.

What popdock provides

Name the Mailchimp audience and it compares every Rillet customer email with every member, dropping anyone already present in any status, including unsubscribed and cleaned. You get a table of the emails to add with their Rillet customer, and nothing is written until you confirm, with any rows you remove left out. New members are added as pending by default so Mailchimp sends its opt-in confirmation, and subscribed is used only when you say you already hold consent. Each address is read back and reported as added or failed, and Rillet is never changed.

Business outcome

---

Your audience covers your paying customers without ever re-adding someone who opted out.

scenario

A renewal campaign needs the right contacts: customers whose Rillet contracts end soon and who still subscribe in Mailchimp. Building that segment by hand means filtering contracts by end date, finding each customer's emails, checking subscription status and avoiding people already in the segment.

What popdock provides

Name the audience and static segment, and optionally how many days ahead to look, and it reads Rillet contracts ending in that window, skipping closed or canceled ones, and gathers the customers' emails. Only contacts already subscribed in Mailchimp and not yet in the segment are kept, and the rest are listed with the reason they were left out. It refuses saved, condition-based segments and never creates one. After you confirm, the contacts are added and the segment is read back. It sends nothing and adds no new audience members.

Business outcome

---

Your renewal segment holds every reachable renewing customer, and nobody who unsubscribed is pulled back in.

scenario

Collections leans on email reminders, but a reminder sent to an address that bounced or unsubscribed never lands. Checking means listing overdue invoices in Rillet, finding every contact email for each customer, then looking each one up in Mailchimp for its status and recent bounces.

What popdock provides

Optionally set a minimum amount due, and it groups overdue Rillet invoices by customer with the total owed per currency and the oldest due date. Each contact email is checked in Mailchimp for audience status and hard bounces in the last 180 days, and classed as reachable, unsubscribed or undeliverable, with addresses not in Mailchimp kept separate. Customers with no reachable email are flagged at the end. It only reports: no invoice is marked, no payment is recorded and nobody is contacted.

Business outcome

---

Collections knows up front which overdue accounts need a phone call or a new contact, not another email that will bounce.

scenario

Knowing how well a Mailchimp audience covers your customers means lining up every Rillet customer email against the audience. By hand it is slow, case and spacing differences hide matches, and people who unsubscribed or are still pending get lumped in with everyone else.

What popdock provides

Name the audience and it reads every Rillet customer email and the full membership in one pass, matching addresses regardless of case or spacing. The report shows totals, the customer emails missing from the audience, members who are unsubscribed or cleaned, and those still awaiting opt-in. If fewer members were read than the audience holds, it says the comparison is partial and how many rows it read. It reports only and never adds anyone.

Business outcome

---

You see exactly which customers your audience misses or cannot reach before you plan a campaign or an import.

scenario

A campaign report gives you opens and clicks, but not which of those people pay you or how much. Answering that means exporting campaign activity, matching emails to Rillet customers and looking up each customer's ARR, so most teams never connect engagement to revenue.

What popdock provides

Name a Mailchimp campaign and it reads the headline numbers, then everyone who opened or clicked and the links they clicked, ignoring bounces. Engaged emails are matched to Rillet customers, and each customer's latest ARR and status come from Rillet's ARR history. You get a table sorted by ARR, totals per currency with no mixing, and a count of engaged people who are not customers. A customer with no ARR history shows as none recorded rather than zero, and nothing is changed.

Business outcome

---

Marketing can show which paying accounts a campaign reached and how much recurring revenue they represent.

scenario

An unsubscribe from a paying customer can be an early sign of trouble, but Mailchimp does not know who pays you. Spotting the risky ones means matching each unsubscribe to a Rillet customer and checking their ARR and contract end date, which rarely happens before the renewal conversation.

What popdock provides

Pick a date range, the last 30 days by default, and it reads Mailchimp unsubscribes and matches each email to Rillet customers. For every matched customer it pulls the latest ARR and the nearest contract end date. The table is sorted by ARR with the campaign and reason, showing not given when no reason was left, and it totals the ARR affected per currency and names campaigns that drove more than one customer away. It is read-only and never resubscribes anyone.

Business outcome

---

Account owners hear about unhappy paying customers in time for a real conversation, ranked by the revenue at stake.

scenario

To understand one customer you need their revenue position from Rillet and their email engagement from Mailchimp, which live in different systems. Pulling ARR, contracts, credit memos, audience status and recent activity together takes several searches, and an email shared by two Rillet customers is easy to miss.

What popdock provides

Give an email address and it finds every Rillet customer that contact belongs to, then reads current ARR with the change from last month, contracts with their end dates, and credit memos in the lookback window. From Mailchimp it reads audience status, open and click rates and recent activity counts. Each customer is reported separately with no ARR added across them, and the report ends with one line of interpretation, such as high ARR with no opens in 90 days. Neither system is changed.

Business outcome

---

You see what a contact is worth and whether they still listen, in one view before any account conversation.

scenario

Renewals at risk often go quiet first: contacts stop opening email, unsubscribe or start bouncing. Spotting that means listing contracts ending soon in Rillet, finding each customer's contacts and checking every one in Mailchimp, which nobody has time to do across a whole quarter.

What popdock provides

Choose how many days ahead to look, 90 by default, and it reads open Rillet contracts ending in that window and each customer's contact emails. Every email is checked in Mailchimp for status, opens, clicks and bounces over the last 90 days. Each contract is rated engaged, silent or unreachable based on its best contact, with the count and value per rating and no totals across currencies. A failed lookup is marked unknown rather than guessed, and nothing is changed.

Business outcome

---

You see which upcoming renewals have gone quiet while there is still time to reach the customer another way.

scenario

Event and campaign lists built in Salesforce often need to reach a Mailchimp audience, but being a member of a Salesforce campaign is not permission to email. Importing by hand risks subscribing people without consent and re-adding contacts who already unsubscribed or were cleaned.

What popdock provides

Name the Salesforce campaign and the Mailchimp audience, and it reads the campaign members, drops anyone without an email and splits each name into first and last. Every address is checked against the audience, and anyone already there in any status is skipped. You see who will be added and are told each person gets a confirmation email, and nothing happens until you say yes. Members are always added as pending, never subscribed, and the report lists who was added, who was skipped and why, and any failures.

Business outcome

---

Salesforce campaign contacts join your audience through double opt-in, with consent respected and no unsubscribes revived.

scenario

People who click a campaign deserve a lead in Salesforce, but creating them by hand means checking each email against contacts and leads first. Skip that and you create duplicates, and rush it and leads land without the last name and company Salesforce requires.

What popdock provides

Name the Mailchimp campaign, and optionally a lead source, and it gathers the unique clickers with their names and companies. Anyone already a Salesforce contact or lead with that email, or who unsubscribed from the campaign, is dropped. Rows missing a last name or company are marked and left out unless you fill them in, and nothing is created until you confirm. Each lead is created once with your lead source, and the report gives totals for every reason a clicker was skipped.

Business outcome

---

Engaged clickers become Salesforce leads the same day, without duplicate records or half-filled leads.

scenario

The email numbers sit in Mailchimp while the members, responses and pipeline sit in Salesforce, so judging one campaign means two reports and a spreadsheet. It is also hard to tell how many Salesforce members were ever sent the email at all.

What popdock provides

Give a campaign name and it reads the Mailchimp report for sends, opens, clicks, unsubscribes, bounces and revenue, and the Salesforce campaign for members, responses, opportunities, won value and cost. It checks up to 200 Salesforce member emails against the Mailchimp recipients to count who was sent the email and who opened it. You get a side by side table with a few plain observations, and the exact names matched on each side so you can confirm they are the same campaign. E-commerce and opportunity revenue are kept apart, and nothing is changed.

Business outcome

---

You judge a campaign on email and pipeline results together, and spot members who were never sent the email.

scenario

Clicks from a campaign are wasted if the people behind them never reach Salesforce. Finding them means pulling the click list and searching each address in contacts and then leads, one at a time, before anyone can decide who deserves a follow-up.

What popdock provides

Name the Mailchimp campaign, and optionally how many people to return, and it collects the unique clickers with their names and companies. Each email is checked against Salesforce contacts, then leads, ignoring case and stray spaces. You get a table of the unmatched clickers with their click count and last click date, plus totals for contacts matched, leads matched and unmatched. It is read-only, so you decide who becomes a lead.

Business outcome

---

You get a short, ready list of interested people Salesforce does not know about yet.

scenario

Your biggest store buyers in Mailchimp may be invisible to the sales team in Salesforce, or sitting there only as a lead. Checking means searching each email in contacts and leads, then opening the account for its owner and any open opportunities.

What popdock provides

Set a minimum spend and a number of customers, and it takes the top Mailchimp e-commerce customers and looks each up in Salesforce by email, contact first and then lead. For contacts it reads the account, its owner and open opportunities. High spenders with no Salesforce record, and those who are only a lead, are called out separately. It matches on email only, never on a company name that merely looks similar, shows spend in the store's currency and changes nothing.

Business outcome

---

Sales knows which big buyers have no account owner or open pipeline, so no high spender goes unmanaged.

scenario

When someone unsubscribes or hard bounces in Mailchimp, their Salesforce record usually stays as it was, still sitting in active campaigns. Finding them means pulling two Mailchimp reports and searching each address in Salesforce contacts, leads and campaign members.

What popdock provides

Choose a lookback, 30 days by default, and it reads Mailchimp unsubscribes and hard bounces with the campaign and the reason or bounce type. Each email is matched to a Salesforce contact or lead with its owner, and the Salesforce campaigns that still include the person are listed. Results come in two tables, and someone who did both appears in both. It reports the records and does not change them.

Business outcome

---

You can clean up Salesforce records and campaign lists for people email no longer reaches, with the evidence in hand.

scenario

Reps working a contact in Salesforce rarely see that the person clicked last week's campaign. Logging clicks by hand means matching each clicker to a contact or lead and writing a task, and running it twice fills activity history with duplicates.

What popdock provides

Name the Mailchimp campaign and it groups the clicks by person with the links clicked and the last click date. Each email is matched to one Salesforce contact or lead, and anyone with no match, several matches or a task already logged for that campaign is skipped. You review the planned tasks and confirm before anything is written, then one completed task per person is added with the links and click count. The report lists what was created and why others were skipped.

Business outcome

---

Campaign clicks appear in Salesforce activity history once per person, so reps see the interest when they open the record.

scenario

Answering what you know about one person means opening Salesforce for their contact or lead, campaigns, tasks and opportunities, then Mailchimp for audiences, opens and unsubscribes. The two rarely agree, and someone unsubscribed in Mailchimp can still be an active campaign member in Salesforce.

What popdock provides

Give an email address and it finds the Salesforce contact or lead, listing every match with its owner if there is more than one, and the person's Mailchimp audiences with status, rating and tags. It adds email activity over your lookback period with campaign titles, plus the person's Salesforce campaigns, open tasks and open opportunities. A closing line says whether the two systems agree. It matches on email only, never on a name, and reads without changing anything.

Business outcome

---

You get one dependable picture of a person, with any conflict between email consent and Salesforce activity called out.

scenario

Shopify customers who agree to marketing at checkout do not always reach your Mailchimp audience. Fixing it by hand means comparing new customers with the audience one by one, and adding back someone who unsubscribed or was cleaned breaks their consent.

What popdock provides

Name the Mailchimp audience, and optionally a start date, and it reads recent Shopify customers who accept marketing and have an email. Each is checked against the audience, and anyone already a member in any status, or found in Mailchimp's unsubscribe history, is left alone and listed separately. You see the people to add and the status they will get, pending by default for double opt-in, and nothing is written until you confirm. Each added member is read back, and a run capped at 250 customers says so.

Business outcome

---

Customers who agreed to marketing reach your audience, while anyone who withdrew consent stays out.

scenario

Targeting your best Shopify customers in Mailchimp means finding everyone above a spend threshold, checking each is a subscribed member and adding them to a segment without doubling anyone up. A condition-based segment cannot take manual members at all, which often only shows up after the work is done.

What popdock provides

Give a minimum lifetime spend, the audience and a static segment, and it confirms the segment is static before doing anything else. It reads Shopify customers above the spend and keeps only those subscribed in the audience and not already in the segment, counting each skip reason. After you confirm the list, it adds the members and reads the segment again to show the new member count beside the old one. Nobody is added to the audience itself, and Shopify is not changed.

Business outcome

---

Your top spenders are ready to target in one segment, built from subscribed contacts only.

scenario

Mailchimp credits revenue to a campaign when an order is placed, and that figure rarely reflects cancellations or refunds made later in Shopify. Checking means finding each attributed order in Shopify by customer and amount, which is slow because the two systems share no order number.

What popdock provides

Name the campaign or automation and it reads the orders Mailchimp attributes to it, asking you to choose if several names match. Each order is found in Shopify by customer email, total and date, and ambiguous matches are noted. It checks cancellations and refunds, then totals attributed, confirmed, canceled, refunded and not found revenue per currency, with one sentence on how far the Mailchimp figure overstates kept revenue. If many orders are missing, it warns that Mailchimp may be connected to a different store. Neither Mailchimp nor Shopify is changed.

Business outcome

---

You report campaign revenue that survives refunds and cancellations, not the optimistic number Mailchimp shows.

scenario

A campaign can send hundreds of shoppers to a product that is about to run out. Checking means pulling the campaign's clicked links, working out which product each one points to, and opening every variant in Shopify to read its stock and whether it can still be ordered at zero.

What popdock provides

Name the Mailchimp campaign, and optionally a low stock threshold, and it reads the product page links and their clicks, merging links that point to the same product. Each product is found in Shopify, and every variant's quantity, SKU and stock policy is read. Variants are marked out of stock, low or ok, with a note where the policy allows overselling or turns buyers away. Collection and other links are counted but not looked up, and nothing is changed in either system.

Business outcome

---

You catch stock problems on promoted products before shoppers hit a sold out page or you oversell.

scenario

Mailchimp tracks abandoned carts, but it cannot tell you which shoppers came back and bought in Shopify later. Without that, you chase people who already ordered and cannot say whether your cart recovery emails work. Matching carts to orders by hand, one email at a time, is too slow to do every week.

What popdock provides

Set a start date, and optionally a minimum cart value, and it reads Mailchimp abandoned carts and looks for a later, uncancelled Shopify order from the same email. Carts are classed as recovered, not recovered, or unknown when there is no email, with counts, value per currency and the recovery rate. Unrecovered carts are sorted by value as the ones worth chasing, and recovered carts that ordered much less are noted. It sends nothing to shoppers and changes nothing.

Business outcome

---

You know your real recovery rate and which open carts are still worth following up.

scenario

When a customer writes in, their buying history lives in Shopify and their email history lives in Mailchimp. Piecing together orders, open shipments, subscriptions and recent unsubscribes takes several screens, and nobody notices when the two systems disagree on marketing consent.

What popdock provides

Give an email address and it reads the Shopify customer with recent orders, total spent and the shipment status of anything not yet fulfilled. From Mailchimp it reads each audience status, recent opens and clicks, unsubscribes with reasons, and any open cart with its checkout link. A consent check flags a mismatch, such as accepting marketing in Shopify while unsubscribed in Mailchimp. It matches on email only and changes nothing.

Business outcome

---

You answer a customer with the whole story in front of you, and consent conflicts surface before they become complaints.

scenario

Shopify's accepts marketing flag and a customer's Mailchimp status should agree, but they drift as people check out, unsubscribe and get cleaned. Spotting the gaps means comparing each customer's flag with their audience status by hand, and emailing someone without consent is a compliance problem.

What popdock provides

Name the audience, and optionally a start date, and it reads up to 250 Shopify customers and looks each one up in the audience by email. Every customer is classed as agree, missing from the audience, consent withdrawn in Mailchimp, subscribed without Shopify consent, or pending. Each mismatch class gets its own table sorted by spend, and duplicate members for one email are reported as a data problem rather than settled by picking one. It is read-only, so you decide how to fix each gap.

Business outcome

---

Every consent mismatch between store and email shows up in one report, before it turns into a complaint.

scenario

An unsubscribe count says little until you know who left. Working out which unsubscribes are valuable Shopify buyers, why they left and which campaign pushed them away means matching each email to a customer and reading their spend.

What popdock provides

Set a start date, and optionally a minimum spend, and it reads Mailchimp unsubscribes and looks each person up in Shopify by email. Paying customers are ranked by total spent with the campaign they left and their reason, reasons are grouped and counted, and campaigns are ranked by how many paying customers they lost. Customers whose Shopify marketing consent is still on are listed for you to fix in Shopify admin. It never resubscribes anyone and changes nothing.

Business outcome

---

You learn which campaigns cost you valuable buyers and why, and where store consent needs tidying.

scenario

New paying WooCommerce customers do not always make it into your Mailchimp audience. Adding them by hand means checking each email against the audience first, and a careless import can resubscribe someone who unsubscribed or was cleaned.

What popdock provides

Name the audience, and optionally how many days back to look and the status to use, and it reads recent paying WooCommerce customers and checks each email against the audience. Anyone already a member in any status is skipped and counted. You see the list to add and are told that pending sends a confirmation email, and if you choose subscribed it asks you to confirm the customers gave consent at checkout, falling back to pending if you do not. Nothing is written until you say yes, and failures are reported with their error.

Business outcome

---

Recent buyers join your audience with consent handled properly and no unsubscribed contact brought back.

scenario

Product blocks and recommendations in Mailchimp depend on its store catalog matching WooCommerce. Finding products that never synced, sit under another id or still carry an old title means comparing two catalogs line by line, and the problems only show when a campaign displays the wrong product or none at all.

What popdock provides

Optionally filter by product name, and it reads the published WooCommerce catalog and finds each product in the connected Mailchimp store, first by id and then by title. Products are classed as missing, title mismatch, id mismatch or in sync, with titles compared exactly. For title mismatches it shows the exact changes and, only after you confirm, updates the Mailchimp title and reads it back. Missing products and id mismatches are reported as a store sync issue rather than forced, and WooCommerce is never changed.

Business outcome

---

Your Mailchimp catalog matches the store, so campaigns show the right products under the right names.

scenario

The revenue Mailchimp credits to a campaign includes orders that were later canceled, failed or refunded in WooCommerce. Finding the real number means locating each attributed order in the store by customer, amount and date, then subtracting refunds.

What popdock provides

Give a campaign id or title, and optionally the attribution window, and it reads the Mailchimp report and the orders attributed to the campaign. Each order is matched in WooCommerce by customer email, total and currency within the window after sending, and classed as confirmed, lost or unmatched. Refunds on confirmed orders are subtracted, and the headline compares Mailchimp revenue with net WooCommerce revenue as an amount and a percentage. Currencies are never converted, and nothing is written to either system.

Business outcome

---

You report what a campaign really earned after cancellations and refunds, with every lost order listed.

scenario

Abandoned carts in Mailchimp do not tell you who came back and ordered in WooCommerce, or who tried and failed at payment. Without that, follow-ups go to shoppers who already bought, and recovery cannot be credited to the right email.

What popdock provides

Choose how many days back to look, and optionally a minimum cart value, and it reads Mailchimp carts and searches WooCommerce for a later order from the same email. Carts are classed as recovered, attempted when only pending or failed orders exist, or unrecovered. Unrecovered carts are ranked by value with whether the shopper is still subscribed and whether they have bought before, and unsubscribed shoppers are never shown as reachable. Follow-ups are suggested in text only, and nothing is changed.

Business outcome

---

You know which carts came back, which are worth chasing, and which shoppers you can still email.

scenario

Winning back lapsed WooCommerce buyers means finding who has not ordered in months, checking which of them still subscribe in Mailchimp, creating a coupon and tagging the right contacts. By hand it is easy to tag people who unsubscribed or reuse a code that already exists.

What popdock provides

Name the Mailchimp tag, and optionally the inactivity period and discount, and it finds paying WooCommerce customers with no qualifying order since the cutoff, then keeps only those subscribed in the tag's audience. It proposes a coupon code, checks the code is unused, and shows the discount, a 30-day expiry, one use per customer and the contacts to tag. After you confirm, it creates one coupon and tags each contact, stopping before any tagging if the coupon fails. It never creates tags or sends the campaign.

Business outcome

---

Your win-back campaign is ready to send, with a unique code and an audience of lapsed buyers who still accept email.

scenario

Answering a shopper well means knowing what they bought in WooCommerce, what was refunded and how they respond to your Mailchimp emails. That takes several screens, guest orders are easy to miss, and the two systems often disagree on totals.

What popdock provides

Give an email address and it reads the WooCommerce customer, including guest orders, with order counts by status, net spend after refunds and the products in the three latest orders. From Mailchimp it reads audience status, tags, open and click rates, recent campaign activity, unsubscribes and the store's copy of the customer. A gaps section shows what one system knows that the other does not, with any disagreeing names or totals side by side. Records are joined on email alone, never on name, and nothing is written.

Business outcome

---

You see a shopper's buying and email history together, with any mismatch between the systems laid out plainly.

scenario

The Mailchimp for WooCommerce sync can quietly miss customers or carry stale order counts and spend. Checking means comparing each new customer's orders in WooCommerce with their record in the Mailchimp store, then looking the other way for customers only Mailchimp knows.

What popdock provides

Choose how many days back to check, and it finds the connected WooCommerce store in Mailchimp, then reads recent WooCommerce customers with their valid orders and spend. Each is classed as in sync, missing or out of sync against the Mailchimp store, and store customers WooCommerce does not know are listed as Mailchimp only. The report ends with the store's sync status, notes when many gaps point to the sync itself, and warns that customers created today may simply lag. Nothing is created or updated in either system.

Business outcome

---

You find sync gaps between store and email platform before they skew segments and revenue reporting.

scenario

When an order is refunded or canceled in WooCommerce, the Mailchimp store copy often keeps counting it, so campaign revenue looks better than it is. Fixing it means finding each full refund and cancellation, checking the order exists in Mailchimp and changing its status by hand.

What popdock provides

Choose how many days back to look, 7 by default, and it reads WooCommerce refunds and cancellations, treating an order as fully refunded only when its refunds equal its total. Each order is confirmed in the Mailchimp store by order id, never by email or amount. You see the planned changes, the partly refunded orders being left alone, and a warning that Mailchimp may send notification emails, and nothing is written until you confirm. Only the financial status is changed, and WooCommerce is never touched.

Business outcome

---

Mailchimp stops counting revenue you no longer have, and partial refunds are never marked as full ones.

scenario

Moving a HubSpot list into a Mailchimp audience usually means an export, a spreadsheet comparison and an import, and it is easy to add people who already unsubscribed or to re-subscribe someone Mailchimp cleaned.

What popdock provides

Name the HubSpot list and the Mailchimp audience, and it compares members by email to find who is missing from the audience. People opted out in HubSpot are skipped and listed with the reason, and anyone already in the audience, whatever their status, is left alone. After you confirm the list to add, each person is added as pending, so Mailchimp sends them its own opt-in confirmation. HubSpot is never changed.

Business outcome

---

HubSpot list members reach your Mailchimp audience with their consent confirmed, and nobody who left is brought back.

scenario

Your best online customers often sit only in Mailchimp's store data, so sales never sees them. Finding them means exporting customers by spend, then searching HubSpot one email at a time to see who is missing.

What popdock provides

Set a spend threshold and how many customers to check, and it reads the high-value store customers in Mailchimp and looks up each email in HubSpot. You see who is already a contact, with their lifecycle stage, and who is missing, with company, spend and order count. Only the customers you confirm are created, existing contacts are never edited, and customers who share an email across stores become one contact. Mailchimp is only read.

Business outcome

---

High-spending store customers become HubSpot contacts sales can work, with no duplicates created.

scenario

Collections teams send reminder emails without knowing whether the billing contact still reads them. An address that bounced or unsubscribed in Mailchimp means the reminder never lands, and the invoice ages while everyone waits.

What popdock provides

Set a minimum balance and a lookback period, and it takes every overdue HubSpot invoice, checks the billing contact's Mailchimp status and recent opens, and classes each one as reachable, doubtful or unreachable. Unreachable contacts come first with a recommendation to phone or write instead, and balances are totalled per class and currency. It only reads, and never adds an overdue customer to a marketing audience.

Business outcome

---

Collections know which overdue customers to email and which to phone, before more reminders go unread.

scenario

Answering what you know about one person means checking HubSpot for their contact, deals and tickets and then Mailchimp for their audiences, purchases and opens. The two systems often disagree, and nobody notices until a customer complains.

What popdock provides

Give an email address, and it builds one profile from HubSpot, owner, lifecycle stage, company, open deals, open tickets and subscriptions, and from Mailchimp, audiences and status, store spend and recent opens and clicks. A discrepancies section lists every place the two systems disagree, such as subscribed in one and unsubscribed in the other, with both values side by side. It only reads.

Business outcome

---

One view of a person across CRM and email marketing, with every conflict spelled out.

scenario

Sales cannot see which links a contact clicked in a Mailchimp campaign, because that activity never reaches HubSpot. Copying click data onto contacts by hand is tedious, so it simply does not happen.

What popdock provides

Name a Mailchimp campaign, and it collects everyone who clicked and the links they clicked, leaving out unsubscribe and preference links, then matches each email to a HubSpot contact. You see every note before it is written, with the campaign, send date and links. After you confirm, one note is added per contact, people not in HubSpot are listed, and where an email matches several contacts it asks which one. Mailchimp is only read.

Business outcome

---

Campaign interest shows up on the HubSpot contact, where sales will actually see it.

scenario

A deal closing this month whose buyer has stopped opening your emails is a risk the forecast does not show. Checking means looking up each deal's contact in Mailchimp one at a time.

What popdock provides

Set a closing window, a lookback period and optionally a pipeline, and it reads the open HubSpot deals closing soon, finds each deal contact's email and checks their Mailchimp status, opens and clicks. Each deal is rated engaged, quiet, unreachable or no contact email, with quiet and unreachable deals listed first by amount. It treats engagement as evidence, not a forecast, and changes nothing in either system.

Business outcome

---

See which closing deals have a buyer who has gone quiet, while there is time to act.

scenario

Someone who unsubscribes in Mailchimp can still look subscribed in HubSpot, and may even be on an open deal. Without a regular check, the CRM keeps emailing people who asked you to stop.

What popdock provides

Set a lookback period and optionally a campaign, and it takes the recent Mailchimp unsubscribes and checks each email in HubSpot for subscription status, owner and open deals. You get one table with the people still subscribed in HubSpot first, then those on open deals, and counts for each group, including those not in HubSpot. It never changes a subscription, so you decide what to fix.

Business outcome

---

Catch consent gaps between Mailchimp and HubSpot before an unsubscribed person is emailed again.

scenario

Campaign clicks show interest, but in Mailchimp nobody owns the follow-up. Matching clickers to HubSpot owners and open deals by hand is slow enough that most never get a call.

What popdock provides

Name a Mailchimp campaign and how many people to enrich, and it collects the clickers and their links, leaving out unsubscribe and preference links, then looks each one up in HubSpot for owner, lifecycle stage, lead status and open company deals. You get a follow-up list grouped by owner, with separate groups for clickers not in HubSpot and clickers with no owner. It only reads and creates no contacts.

Business outcome

---

Every interested clicker lands on the right owner's follow-up list.

scenario

Highly engaged email openers never reach the CRM because nobody compares the Mailchimp list with the NetSuite records. Checking each opener against customers, leads, prospects and contacts one at a time is too slow, so warm people are never followed up.

What popdock provides

Give a Mailchimp campaign and a minimum number of opens, and it reads the people who opened it that often, with their names and companies. For each email it searches NetSuite for a customer, then a lead, a prospect and a contact, stopping at the first hit. You get openers with no NetSuite record, ready for sales to add, and openers found with the record type and ID, plus counts. Blank emails are listed separately. It only recommends creating records and never creates them, and nothing in either system is changed.

Business outcome

---

Sales gets a list of engaged openers missing from NetSuite so they can be added, with no records created automatically.

scenario

Marketers copy the list of openers from a Mailchimp campaign and look each person up in NetSuite to see what they ordered. Done one at a time it is slow, so campaign results rarely get tied to revenue.

What popdock provides

Give a campaign ID, and optionally how many days after the send to look (14 by default). It reads the campaign title, send date and openers from Mailchimp, matches each opener to a NetSuite customer by email, and totals their sales orders dated within that window after the send. The report shows openers, how many are customers, how many ordered and the total order value, with a table of ordering customers. It says plainly that this shows timing and not cause, lists but does not total orders for emails matching several customers, and changes nothing in either system.

Business outcome

---

Campaign opens are linked to NetSuite orders in one report, with timing stated honestly and ambiguous matches left uncounted.

scenario

Sales and marketing compare the customer list with the email audience by hand. Customers get left off, and some are mailed after they opted out.

What popdock provides

Give an audience name and how many customers to check, and it reads NetSuite customers with their balance and first order date. Each email is looked up in the Mailchimp audience, ignoring case, and customers are grouped as subscribed, unsubscribed, cleaned or other status, and not on the audience. Customers with no email are listed separately as unmatchable. If the audience name matches nothing it lists the audiences it found. Where names differ it shows both, and it never adds or changes members or customers.

Business outcome

---

Marketing sees who is subscribed, unsubscribed or missing from the audience, with no members added or changed.

scenario

Collections and marketing both email the same customers, and neither team sees what the other has sent. A past-due account can keep receiving promotional campaigns while collections is asking for payment.

What popdock provides

Give an as-of date, and optionally how many days of email history to check (30 by default), and it totals past-due NetSuite receivables by customer and keeps the five largest. It finds each customer's email in NetSuite and reads their Mailchimp email activity, counting opens and clicks and noting the latest activity and campaign. The report has one row per customer with the past-due total, emails received and last activity, and flags customers who are heavily mailed and past due. Customers it cannot match are marked instead of dropped, and no records are changed.

Business outcome

---

Collections and marketing can see which past-due customers are still receiving campaigns, and coordinate before the messages clash.

scenario

Mailchimp reports a customer's total spend and order count, and NetSuite shows a different set of invoices for the same person. Nobody can explain the gap without pulling both sets by hand, and amounts in different currencies make it easy to compare the wrong numbers.

What popdock provides

Give a customer email, and optionally a start date, and PopdockAI reads the customer's spend, order count and orders in Mailchimp. It finds the matching NetSuite customer and reads their invoices from that date, summing the totals and counting them. A side by side comparison shows spend, number of orders and the difference, with a view on whether the gap is plausible because Mailchimp only sees store orders pushed to it. It stops if the email is missing in one system or matches several customers, says so when currencies differ and corrects nothing.

Business outcome

---

Marketing and finance can explain the gap between Mailchimp spend and NetSuite invoices for a customer in one answer.

scenario

Collections reminders go out by email, but nobody knows which customers have unsubscribed. Reminders reach people who opted out, or customers who owe money and cannot be emailed are missed entirely.

What popdock provides

Give a Mailchimp audience name and, optionally, a minimum unpaid amount, which defaults to 1. It reads the unsubscribed members of that audience with their unsubscribe date and reason, matches each email to a NetSuite customer and reads their unpaid invoices. The report has one row per customer, with open invoice count and total unpaid, largest first, plus a list of members not found in NetSuite. Ambiguous matches are listed, not guessed. Customers with no unpaid invoices are counted in a footer line, it never suggests re-subscribing anyone, and nothing is changed in either system.

Business outcome

---

Collections get a list of unsubscribed customers who still owe money, so they can use another channel.

scenario

Contacts on open deals sometimes unsubscribe in Mailchimp, and the rep emailing them from the CRM never sees it. Nobody compares the two systems, so opted-out people keep getting email and the deal suffers.

What popdock provides

Name a Nutshell owner and it lists their open leads and the people on them, then checks each person's email in Mailchimp. People who are unsubscribed, cleaned or not in Mailchimp at all are flagged. Contacts with no email are listed separately and never treated as safe, and it warns when the results may have been cut off. It only reads, nothing is changed in either system.

Business outcome

---

Reps know who not to email on their open deals, and opted-out contacts stop getting messages by mistake.

scenario

Customers who spend heavily in a Mailchimp connected store do not always exist in the CRM. Nobody notices without exporting both lists and comparing them, so valuable buyers never get an owner or a lead.

What popdock provides

Give a spend threshold and it finds the Mailchimp store customers above it, then looks for each one in Nutshell people and companies. A match on email is accepted, and a match on name alone is shown only as a possible match. It lists who is missing from the CRM. It only reads and never adds records to Nutshell.

Business outcome

---

High-spending customers who are missing from the CRM are listed, so sales can add them deliberately.

scenario

Reps check Mailchimp by hand for a contact they found in the CRM, copying email addresses between tools. They miss opt-outs and the contact's other email addresses, so they do not see the full picture of how the person engages.

What popdock provides

Name a Nutshell contact and it looks the person up in Nutshell, then builds their Mailchimp profile by email: audience subscription, campaigns received, unsubscribes and store purchases. If more than one contact matches, or none, it stops and asks. Addresses that are missing from Mailchimp are reported as such. It only reads, nothing is changed.

Business outcome

---

Reps see a contact's subscription status, email engagement and purchases in one answer before they reach out.

scenario

Deciding who on a lead to approach means checking each person in Mailchimp one at a time. Someone who has unsubscribed or whose address has bounced is easy to email by mistake, and the best-engaged person is hard to spot.

What popdock provides

Name a Nutshell lead and it reads the lead, finds the people attached and their email addresses, then checks each one in Mailchimp. It reports each person's engagement and marks anyone unsubscribed or cleaned as do-not-email. Ambiguous name matches are flagged for you to check. It only reads, nothing is changed in either system.

Business outcome

---

Reps pick the right person to approach on a lead and avoid emailing anyone who opted out.

scenario

A Mailchimp campaign shows who opened it, but not whether those people have live deals. Reps do not know which openers are already in the pipeline, so warm interest goes unfollowed.

What popdock provides

Name a Mailchimp campaign and it finds the repeat openers, then matches each to Nutshell by email, or by name and company together. For every match it shows the open leads and their owners. Ambiguous matches are flagged, and if the campaign cannot be found it stops. It only reads, and nothing is added or changed in either system.

Business outcome

---

Reps follow up with campaign openers who already have deals, while the interest is fresh.

scenario

Adding a CRM contact to a Mailchimp audience by hand risks duplicates, and it is easy to re-subscribe someone who opted out. There is no quick check of whether the person is already a member before they are added.

What popdock provides

Name a Nutshell contact and a Mailchimp audience, and it finds the person in Nutshell and checks the audience for an existing membership. You see what it will add and nothing is written until you confirm. It never re-subscribes people who unsubscribed or were cleaned, and it stops if the contact or the audience is ambiguous. Afterwards it checks that the member was added.

Business outcome

---

Contacts are added to the right audience once, and people who opted out stay opted out.

No items found.

ready, go

Tools for Mailchimp

Start with ready-made MCP tools for the Mailchimp. Each one gives your AI client a single, clearly defined job: get invoices or journal entries, pull a file, or create and update records. Add a tool to your PopdockAI MCP server, choose the fields it returns and who can use it, and it's ready in Claude, ChatGPT or Microsoft Copilot. Nothing is exposed that you haven't switched on.

Name of tool

Description

run-action

mailchimp-update-product

Updates an e-commerce product in a store connected to Mailchimp. Only the values supplied are changed.

run-action

mailchimp-update-order

Updates an e-commerce order in a store connected to Mailchimp, typically its payment or fulfilment status and shipment tracking.

run-action

mailchimp-update-customer

Updates an e-commerce customer in a store connected to Mailchimp, such as their name, company or marketing opt-in. Only the values supplied are changed.

run-action

mailchimp-update-list-member

Updates an existing contact in a Mailchimp audience: subscription status, name, email address or preferences. Only the values supplied are changed.

run-action

mailchimp-start-automation

Starts all emails in a classic Mailchimp automation, so it begins sending to contacts who meet its trigger.

run-action

mailchimp-replicate-campaign

Copies an existing Mailchimp campaign as a new draft, ready to edit and resend. Nothing is sent.

run-action

mailchimp-pause-automation

Pauses all emails in a classic Mailchimp automation. Nothing further is sent until it is started again.

get-data

mailchimp-get-survey

Returns Mailchimp surveys with their status, audience, response count and hosted URL.

Ready to unlock your data?

‍

Start building tools that turn your business systems into AI superpowers

Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

Capabilities that matter most for Mailchimp

Example AI Use Cases for Mailchimp

Add missing Bloomerang donors to a Mailchimp audienceMarketing

Bloomerang gifts after a Mailchimp campaignMarketing

Check Bloomerang major donor reach in MailchimpMarketing

Log Mailchimp campaign engagement to BloomerangMarketing

Mailchimp engagement for a Bloomerang donorSales

Mailchimp store customers missing from BloomerangSales

Note Mailchimp bounces and unsubscribes in BloomerangOperations

Reconcile a Mailchimp audience with Bloomerang constituentsData and Analytics

Add Capsule CRM contacts to a Mailchimp audienceMarketing

Create Capsule CRM tasks for Mailchimp abandoned cartsSales

Create Capsule CRM tasks for Mailchimp campaign clickersSales

Find Mailchimp subscribers missing from Capsule CRMMarketing

Find Mailchimp top buyers with no Capsule CRM opportunitySales

Log Mailchimp unsubscribes as Capsule CRM notesMarketing

Mailchimp and Capsule CRM contact profileSales

Match Mailchimp campaign clickers to Capsule CRMMarketing

Add flagged DonorPerfect donors to a Mailchimp segmentMarketing

Add missing DonorPerfect donors to a Mailchimp audienceMarketing

DonorPerfect gifts after a Mailchimp campaignMarketing

Find DonorPerfect donors missing from a Mailchimp audienceMarketing

Find DonorPerfect donors with bouncing Mailchimp emailsOperations

Flag DonorPerfect donors who unsubscribed in MailchimpMarketing

Log Mailchimp campaign clicks to DonorPerfect donorsMarketing

Mailchimp engagement for a DonorPerfect donorMarketing

Add missing Dynamics 365 Business Central customers to a Mailchimp audienceMarketing

Check Mailchimp abandoned carts against Dynamics 365 Business Central accountsMarketing

Find engaged Mailchimp subscribers missing from Dynamics 365 Business CentralSales

Mailchimp and Dynamics 365 Business Central customer profile by emailSales

Measure Dynamics 365 Business Central revenue from a Mailchimp campaignMarketing

Rank Mailchimp unsubscribes by Dynamics 365 Business Central salesSales

Reconcile Mailchimp store customers with Dynamics 365 Business CentralOperations

Tag overdue Dynamics 365 Business Central customers in a Mailchimp segmentMarketing

Add missing Dynamics GP customers to a Mailchimp audienceMarketing

Mailchimp and Dynamics GP customer profileSales

Measure Mailchimp campaign sales in Dynamics GPMarketing

Note Mailchimp unsubscribes on Dynamics GP customersMarketing

Reconcile Dynamics GP customers with a Mailchimp audienceMarketing

Route Mailchimp campaign clickers to Dynamics GP salespeopleSales

Tag Dynamics GP customers on credit hold in MailchimpMarketing

Add missing Dynamics SL customers to a Mailchimp audienceMarketing

Check Mailchimp reachability for overdue Dynamics SL customersFinance

Dynamics SL customer Mailchimp engagement profileMarketing

Mailchimp campaign clicks to Dynamics SL sales ordersMarketing

Reconcile Dynamics SL customers with a Mailchimp audienceMarketing

Review Mailchimp unsubscribes from Dynamics SL customersSales

Tag overdue Dynamics SL customers in MailchimpFinance

Add missing Intacct customers to a Mailchimp audienceMarketing

Check Mailchimp reachability for overdue Intacct customersFinance

Create an Intacct customer from a Mailchimp store customerFinance

Mailchimp and Intacct customer profile by emailFinance

Reconcile Mailchimp store customers with IntacctFinance

Tag overdue Intacct customers in MailchimpMarketing

Trace Intacct sales after a Mailchimp campaignMarketing

Add a contact to a Mailchimp audience safelyMarketing

Mailchimp abandoned cart reviewMarketing

Mailchimp audience health checkMarketing

Mailchimp automation reviewMarketing

Mailchimp campaign period reportMarketing

Mailchimp contact profileMarketing

Mailchimp top customers reviewMarketing

Process a Mailchimp unsubscribe requestMarketing

Review a Mailchimp campaign's performanceMarketing

Start or pause a Mailchimp automationMarketing

Tag Mailchimp campaign non-openers for a resendMarketing

Add Pipedrive contacts to a Mailchimp audienceMarketing

Create Pipedrive leads from Mailchimp campaign clicksSales

Mailchimp top customers in PipedriveSales

Mailchimp unsubscribes on open Pipedrive dealsSales

Pipedrive organization Mailchimp engagementSales

Pipedrive person Mailchimp engagementSales

Schedule Pipedrive follow-ups for Mailchimp campaign clickersSales

Add missing Rillet customers to a Mailchimp audienceMarketing

Add renewing Rillet customers to a Mailchimp segmentMarketing

Check overdue Rillet customers' Mailchimp email reachFinance

Find Rillet customers missing from a Mailchimp audienceMarketing

Find Rillet customers who engaged with a Mailchimp campaignMarketing

Flag Rillet ARR at risk from Mailchimp unsubscribesSales

Mailchimp and Rillet customer 360 by emailSales