விளக்கம்
ListBridge Sync for Constant Contact and MemberPress connects MemberPress membership events to your Constant Contact account so subscribers move between contact lists based on their membership state — without exporting CSVs or running manual syncs.
This is an independent integration. “Constant Contact” is a trademark of Constant Contact, Inc. and “MemberPress” is a trademark of Caseproof, LLC. This plugin is not affiliated with, endorsed by, or sponsored by either company.
Key features
- OAuth2 Authorization Code flow
- Three event slots, each mapped to a Constant Contact list of your choice:
- New Member Signup — added when a member registers and pays for the first time.
- Membership Expired — added when a membership expires or a subscription is cancelled.
- Reactivated / Renewed — added when an expired membership is renewed or a cancelled subscription is reactivated.
- Cron at Midnight (site timezone) catches any expired members the real-time hooks may have missed — for example, if your site was offline when MemberPress fired the event.
- Admin-triggered status changes (Transactions list, Edit Transaction screen, bulk status updates) are detected and synced.
- Automatic access-token refresh before every API call — you never hit a 401.
- Translation-ready with a
.potfile in/languages.
Requirements
- WordPress 5.8 or later
- PHP 7.4 or later
- PHP OpenSSL extension (the plugin will refuse to activate without it)
- MemberPress 1.12.14 or later
- A Constant Contact developer account — create one for free at https://developer.constantcontact.com
External services
This plugin relies on the Constant Contact service to synchronise your MemberPress members with your Constant Contact account. No data is transmitted until a site administrator saves valid OAuth2 credentials on the plugin’s settings page and completes the OAuth2 connection flow.
Service used
- Constant Contact (operated by Constant Contact, Inc.)
- OAuth2 authorisation endpoint:
https://authz.constantcontact.com/oauth2/default/v1 - API endpoint:
https://api.cc.email/v3
What data is sent, and when
- During OAuth2 connect / token refresh — your Constant Contact Client ID and Client Secret are sent to the Constant Contact authorisation endpoint to obtain or refresh an access token. This happens when an administrator clicks “Connect to Constant Contact” and automatically before any API call whose access token has expired.
- When a MemberPress member signs up (
mepr-signup) — the member’s email address, first name, and last name are sent to Constant Contact so the contact can be added to the list mapped to the “New Member Signup” slot. - When a membership expires or a subscription is cancelled (
mepr-event,mepr-expire-membership,mepr-subscription-pre-cancel,mepr_txn_store,mepr-transaction-saved,mepr_txn_transition_status) — the member’s email, first name, and last name are sent so the contact can be moved to the list mapped to the “Membership Expired” slot. - When an expired membership is renewed or reactivated (
mepr-transaction-completed,mepr-event) — the member’s email, first name, and last name are sent so the contact can be moved to the list mapped to the “Reactivated / Renewed” slot. - Nightly cron at 12:05 AM in the site’s timezone — the plugin queries MemberPress for transactions that expired in the last 48 hours and, for any that have not yet been migrated, sends the same fields (email, first name, last name) so Constant Contact stays in sync if a real-time hook was missed (for example, the site was offline).
- When loading the settings page (administrators only) — the plugin requests the list of contact lists in your Constant Contact account so they can be shown in the mapping dropdowns. No member data is sent in this call. The response is cached for 30 minutes.
The plugin does not transmit any data to any other third-party service.
Terms and privacy
By connecting your site to Constant Contact you agree to Constant Contact’s policies:
- Constant Contact Terms of Service: https://www.constantcontact.com/legal/terms
- Constant Contact Privacy Notice: https://www.constantcontact.com/legal/privacy-notice
- Constant Contact Developer Portal terms: https://developer.constantcontact.com
Screenshots










Installation
- Upload the plugin folder to
/wp-content/plugins/, or install via Plugins Add New Upload Plugin. - Activate the plugin from Plugins Installed Plugins.
- Navigate to MemberPress Constant Contact in the WordPress admin.
Setup
Step 1 — Create a Constant Contact application
- Go to https://developer.constantcontact.com and sign in (or create a free developer account).
- Under My Applications, click New Application.
- Give it a name (for example “My WordPress Site”) and click Save.
- Copy the API Key (Client ID).
- Click Generate Client Secret and copy the secret — it is only shown once.
- Add a Redirect URI: copy the exact value shown on the plugin’s settings page (for example
https://yoursite.com/wp-admin/admin-post.php?action=mp_cc_oauth_callback).
Step 2 — Save credentials
- Paste the Client ID and Client Secret into the plugin’s settings page.
- Click Save Credentials.
Step 3 — Authorise access
- Click Connect to Constant Contact.
- Log in to Constant Contact and grant access.
- You will be redirected back to the settings page with a “Connected” confirmation.
Step 4 — Map contact lists
- Three dropdowns appear once you are connected.
- Pick a Constant Contact list for each event slot.
- Click Save List Mappings.
அடிக்கடி கேட்கப்படும் கேள்விகள்
-
Do I need a paid Constant Contact developer account?
-
No. The free developer tier is enough to create the application that holds your Client ID and Client Secret. A paid Constant Contact subscription is only required to actually send marketing emails to the lists you sync to.
-
Where are my credentials stored?
-
Inside the standard WordPress
optionstable, encrypted with AES-256-CBC. The encryption key is derived from your site’sAUTH_KEY, so a database leak alone is not enough to recover the credentials. -
What happens when an access token expires?
-
The plugin stores the
expires_attimestamp and refreshes the access token automatically (using the saved refresh token) before every API call. -
What if my site is offline when a membership expires?
-
A nightly cron job runs at 12:05 AM in your site’s timezone and looks back 48 hours for any expired transactions whose contact has not yet been migrated to the expired list. Members caught by the safety net are processed exactly once.
-
Can I sync Constant Contact custom fields?
-
No. Currently this functionality not available. We will add in our road map if many users will ask for that.
-
Does deleting the plugin clean up my database?
-
Yes.
uninstall.phpremoves every option and transient the plugin created when you delete it via Plugins Delete (not just deactivate). -
Which MemberPress events trigger a sync?
-
mepr-signup— new member completes signupmepr-event— generic event bus (expired, renewed, cancelled)mepr-transaction-completed— renewal transactionmepr-subscription-pre-cancel— subscription cancelledmepr-expire-membership— natural membership expirymepr_txn_store,mepr-transaction-saved,mepr_txn_transition_status— admin-triggered status changes
-
Why does the plugin require the OpenSSL extension?
-
So that we can store your Constant Contact credentials encrypted at rest with AES-256-CBC. OpenSSL ships with PHP by default; if your host has disabled it, please ask them to enable it before activating the plugin.
-
How do I enable the debug log?
-
On the settings page, open the Debug Settings card and tick Enable debug log. Logs are written to
wp-content/uploads/mp-cc-logs/mp-cc-YYYY-MM-DD.logand protected from direct web access by anindex.phpand an.htaccessfile.
Reviews
இந்த செருகுநிரலுக்கு மதிப்புரைகள் எதுவும் இல்லை.
பங்களிப்பாளர்கள் & உருவாக்குனர்கள்
“ListBridge Sync for Constant Contact and MemberPress” is open source software. The following people have contributed to this plugin.
பங்களிப்பாளர்கள்Translate “ListBridge Sync for Constant Contact and MemberPress” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.0.0 — 2026-06-05
- Initial release.
- OAuth2 Authorization Code flow with automatic token refresh.
- Three event slots: New Member Signup, Membership Expired, Reactivated / Renewed.
- cron at Midnight (site timezone).
- OpenSSL is a hard requirement.
- Translation-ready.
