Connector name: Marketo
Table name: email_template_history (new columns), or a new email_content table
Column to add: html_body, text_body
API documentation link: https://developer.adobe.com/marketo-apis/api/asset/#tag/Emails/operation/getEmailFullContentUsingGET

Additional details:
The Marketo connector syncs email asset metadata in EMAIL_TEMPLATE_HISTORY (subject,
from_email, from_name, name, url) but no email content. No table in the connector carries the
HTML or text body of a Marketo email.

Marketo exposes this through GET /rest/asset/v1/email/{id}/fullContent.json, which returns the
serialized email content and takes a type parameter for HTML or Text.

The volume is modest, because content lives per asset rather than per send. In the instances I
work with, a few thousand email assets explain hundreds of millions of delivery activities. At
Marketo's documented limit of 100 calls per 20 seconds, a few thousand assets is roughly ten
minutes of API time, and email assets change rarely, so an incremental sync keyed on
updated_at would stay inexpensive.

Use case: we build account activity timelines from marketing email activity. Today a bulk send
shows only a campaign name, so the record is effectively unreadable — a user can see thirty
marketing touches and learn nothing from any of them. EMAIL_TEMPLATE_HISTORY.subject gives us
the subject line. The body would let us show what was actually sent, and let analysis tools
reason over the content rather than only the fact of a send.

Text content alone would still be valuable if full HTML is harder to model. A flat text column
avoids the nested section structure that /content.json returns.

Related: I have separately asked for the A/B-test exclusion on this same table to be
documented, here: https://support.fivetran.com/hc/en-us/community/posts/44282996317719-Connector-Improvement-Document-that-email-template-history-excludes-A-B-test-email-variants

Noting for completeness: this request would not cover emails belonging to an A/B-tested email
program, since Adobe documents that the Get Email endpoints exclude those. That is a Marketo
limitation and I am not asking you to work around it. Coverage would be ordinary sends only.