Why?
mailchimp does not allow to import so called role addresses via the webinterface.
so info@, support@, office@ and the like can’t be imported but need to be inserted manually. (see What role addresses does MailChimp block)
HOW?
this script allows to import subscriptions even though some or all emails are role addresses using the mailchimp API MCAPI.
type chimpimport --help for usage information:
chimpimport imports datasets given in csv file FILENAME into mailchimp's subscriber list.
first row contains headers, EMAIL (note capital letters) column is required
example csv content:
"Some Value";"EMAIL";"Some other value";
"ACME Corp.";"john@acme.com";"Sales representative";
Options:
-h, --help show this help message and exit
-u, --updateExisting if given, existing subscribers will be updated
-k APIKEY, --apikey=APIKEY
your mailchimp api key. to obtain one:
http://kb.mailchimp.com/article/where-can-i-find-my-api-key``
Status
Successfully used for 1500 subscribers.
Supports custom fields (just add headers for them to the import csv)
Supports multiple subscriber list. If you have multiple lists, the script will prompt the list to import data into.
Changelog
1.2 (2012-10-08)
existing subscribers get updated when importing with -u flag
login() api method has been disabled (see shutdown info) so we change the help text on how to obtain an api key
rename README.txt to .rst for nice display on github
1.1 (2011-11-12)
added support for multiple lists (prompt user which one to choose)
1.0 (2011-09-20)
Initial release
Metadata
Release files for wm.chimpimport 1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| wm.chimpimport-1.2.zip | 8.8 kB | Without provenance | Details for wm.chimpimport-1.2.zip |
Release files / wm.chimpimport-1.2.zip
| Download URL | wm.chimpimport-1.2.zip |
|---|---|
| Size | 8.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a79bd8610fe422c865d83dcc3826b3031b7eb6bc985b733a949e6f655c85958d
|
|
BLAKE2b-256 checksum How to use checksums |
8871674f51a2a8b8b2a044fc05a00b6e1efc1a3eebf00bf943df1c952322e46b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for wm.chimpimport 1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.