-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SAASINT-3425] DDSaaS: Mailchimp - README changes #19076
base: master
Are you sure you want to change the base?
[SAASINT-3425] DDSaaS: Mailchimp - README changes #19076
Conversation
1. Navigate to the `Mailchimp` integration tile in Datadog. | ||
2. Add your Mailchimp credentials. | ||
|
||
| Mailchimp parameters | Description | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we keep the table with the parameters? It's helpful!
|
||
#### Get API credentials for Mailchimp |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generate API credentials in Mailchimp
|
||
### Add your Mailchimp Credentials |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Connect your Mailchimp Account to Datadog
- Add your Marketing API Key and Server Prefix
- Click the Save to save your settings.
|
||
| Mailchimp parameters | Description | | ||
| -------------------- | ------------ | | ||
| Marketing API key | API key for your Mailchimp marketing account. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also see a Status and Messages columns on the integration tile, what do those do?
What does this PR do?
This PR makes a minor change to the Mailchimp README file.
Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.backport/<branch-name>
label to the PR and it will automatically open a backport PR once this one is merged