| 开发者 |
rnzo
chimpmatic |
|---|---|
| 更新时间 | 2026年7月25日 21:36 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPL v3 or later |
| 版权网址: | 版权信息 |
https://signls.dev/wp-json/chimpmatic/v1/telemetry to measure setup completion, compatibility, feature use, reliability, upgrades, and long-term adoption. Administrators can turn sharing off or on repeatedly without restriction.
The bounded snapshot contains random pseudonymous site/install/device identities; the current site URL and one snapshot user agent; WordPress, PHP, database, server, theme, Contact Form 7, and ChimpMatic facts; plugin inventory (maximum 500 rows, including name/version/author/active state); 16 fixed competitor indicators; aggregate provider/auth method, destination, mapping, feature, lifecycle, submission, performance, and scrubbed failure facts; and Contact Form 7 configuration labels (maximum 100 forms, 50 detailed forms, and 30 field/mapping rows per detailed form). Totals and truncation flags identify omitted rows.
It does not send contact details, submitted values, credentials, API or license keys, OAuth secrets, cookies, authorization headers, raw provider responses, raw administrator email, commerce records, raw IP addresses, arbitrary settings, request bodies, or file contents. Server address and hostname are SHA-256 hashes; failure samples are scrubbed and limited to 50 characters.
Active installations send at most daily and quiet installations at most weekly, with one coalesced refresh after relevant changes. Delivery receipts are retained for 90 days; current typed facts are replaced by newer observations; daily aggregates and pseudonymous adoption/lifecycle identity are retained for long-term analysis. Turning sharing off clears scheduled delivery, any pending payload, and the local delivery credential immediately without sending an opt-out event.
Review the complete public field matrix, exact bounds, destination, purpose, exclusions, and retention. Also review the ChimpMatic privacy policy.
Requirements
Version 0.9.81.08 supports Mailchimp, Brevo, MailerLite, and Klaviyo. You select one provider independently for each Contact Form 7 form.
Open the ChimpMatic tab in the Contact Form 7 editor, select Mailchimp, connect with OAuth or an API key, choose an audience, and map the form's email field. You can then configure consent and single or double opt-in. Follow the Mailchimp setup guide.
Open the ChimpMatic tab, select Brevo, enter a Brevo API key, choose a list, and map the form fields to Brevo contact attributes. You can subscribe the contact directly or use a Brevo confirmation email. Follow the Brevo setup guide.
Yes. Select MailerLite in the ChimpMatic tab, connect with an API token, choose a group, and map the Contact Form 7 email field and subscriber fields. MailerLite applies the account's API double-opt-in setting. Follow the MailerLite setup guide.
Yes. Select Klaviyo in the ChimpMatic tab, connect with a private API key, choose a list, and map Contact Form 7 fields to Klaviyo profile properties. Consent behavior follows the selected Klaviyo list. Follow the Klaviyo setup guide.
Yes. Existing configurations default to Mailchimp and retain their saved audience, field mappings, API credentials, and opt-in behavior. Read more about the Contact Form 7 Mailchimp integration.
Yes. A newsletter form can send to MailerLite while a lead form sends to Brevo, for example. Every form stores its own provider, credentials, destination, mappings, and opt-in configuration.
Yes, but the control differs by provider. Mailchimp offers single or double opt-in per form. Brevo can send a confirmation email. MailerLite follows the account's API double-opt-in setting. Klaviyo follows the selected list's consent behavior. Read more about provider-specific double opt-in.
Lite maps the required email address plus up to four additional form fields. Compatible ChimpMatic Pro features can expand the mapping limit. Read more about Contact Form 7 field mapping.
Start with the provider integration guides, visit the Help Center, or contact the ChimpMatic team.