Marketing email object - custom properties API

Marketing & Content Hub Email Marketing Tool
, , ,
1

I’ve created a couple of custom properties on the marketing_email object in an attempt to be able to group our emails with properties instead of a complicated email naming convention. This works well enough within the HubSpot UI, but we’ve discovered that there is no supported public API path to pull custom properties on the marketing_email object, only standard properties (confirmed by HubSpot solutions expert).

Has anyone had a similar use case and figured out a workaround? The goal is to be able to filter on custom properties within our Redshift tables that store our marketing email assets and send activities.

2

Hi @evan.mazursky Welcome to the community! A couple of possible workarounds:

  1. Campaign-based grouping: If your email groupings align with HubSpot campaigns, you might be able to use campaign associations to handle the grouping in Redshift instead.

  2. Metadata mapping table: Someone in the other thread mentioned using a custom Marketing Email report to export the email IDs and custom property values. You could potentially load that into Redshift and join it to your existing email data.

I do have two questions…

Are your custom properties used for multiple independent classifications (e.g., region, product, audience), or do they mostly represent campaign groupings?

Do you need those values synced automatically, or would a periodic export work?

3

Hi @UttamM , thank you for the reply and suggested workarounds. To answer your questions:

  1. We would like to use the properties for multi-classification purposes (region, registration status, automated vs. one-off, etc)
  2. Automatic cadence would be the goal since we are building new emails at a fairly rapid pace. We may be able to set up a weekly export if there is no automation realistically possible.
4

One option is setting up middleware, but if the API doesn’t expose the custom property values, middleware won’t solve that.

If you’re open to changing the workflow, you could maintain the classifications in an external metadata table keyed by the HubSpot email ID and sync that to Redshift. That would give you an automated pipeline without depending on the missing API fields, although you’d need a reliable way to capture the email ID and metadata.

Have you tested whether the Marketing Email index lets you export the custom properties alongside the email IDs? Feel free to DM me if you want to discuss this further