Skip to content
The Workflow Library
Get the full library

Counter property: marketing emails received by a contact (engagement volume reporting)

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Marketing Hub Professional.

Contact2 stepsUpdated for HubSpot seat pricing
OutcomeEvery contact carries a running count of marketing emails sent to them, so reporting on send volume per contact does not depend on manually tallying campaign sends.
Workflow mapreporting-alerts-017
Contact was sent a marketing email leads to Increment marketing_emails_received_count by 1. Contact was sent a marketing email Increment marketing_emails_received_count by 1
Contact was sent a marketing email leads to Increment marketing_emails_received_count by 1. Contact was sent a marketing email Increment marketing_emails_received_count by 1

When to use it, when not to

Use it

  • Use it for engagement-volume reporting, list segmentation, or spotting contacts who receive far more email than the rest of the database.
  • Use it as an input to a "do not over-email" suppression list once the counter passes a threshold in a given period.
Read more on when to use itShow less

Skip it

  • Do not use it as a substitute for HubSpot's own marketing email analytics (opens, clicks per send). This counts sends only. It says nothing about engagement quality.
  • Do not use it if a rolling window is needed (for example emails in the last 30 days). This counter is lifetime, cumulative, and never resets on its own. See Variants for a reset alternative.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 2 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 2 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 1 case, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Reporting and alerts spec

Not the workflow you needed?

More in Reporting and alerts

50 specs in this section

See all 50 This category, 39 EUR
FreeSlack alert: deal marked Closed Won (revenue milestone notification)Deal4 steps Property: days since last marketing email open (engagement recency helper)Contact2 steps Stage-entry timestamp properties for pipeline velocity reportingDeal5 steps Timeline note logging on critical property change (audit visibility)Deal2 steps

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library