Testing marketing automations before launch

Before launch, compare the configured automation against a written set of expected outcomes. Check entry, routing, delays, exits and actions that reach another system. Check message delivery and connected-record changes separately.

Define a passing run

For each important case, record what should happen and what must not happen. Include an eligible contact, an excluded contact, missing data, overlapping branch rules, a change during a delay, a repeat trigger and a contact who reaches the campaign objective.

Use the campaign’s approved audience, offer and timing rules to set the expected result.

Give each controlled record an identifier and compare its observed path with the expected one.

Check entry and routing separately

A record can satisfy a branch condition without qualifying to enter the workflow. Check the start criteria first, then the branch reached after entry. In HubSpot, the enrolment criteria test checks the record’s current state but does not guarantee re-enrolment after an earlier completed run. For event triggers, it cannot simulate the event itself; it checks additional filters only.

HubSpot branches send enrolled records down paths based on conditions. Check an overlapping case and, where configured, the unmatched path against the branch criteria. Compare each observed outcome with the configured criteria. If a path has no action, review whether the campaign has an outcome for it.

Testing Workflow Entry and Routing in HubSpot

Tie evidence to the workflow version

HubSpot’s workflow and enrolment tests assess the current version of the workflow. Before relying on a result for a release decision, note which version was tested and compare it with the version intended for activation.

When investigating an unexpected action, HubSpot recommends reviewing workflow details, checking the exact version the record may have been enrolled into, and reviewing additional workflow settings. Timing settings can automatically reschedule actions, so check them when an action appears to run at an unexpected time.

Keep a concise test record of the selected record, test mode and observed outcome. This makes it easier to distinguish a verified path from one that still needs checking after a workflow change.

Check what changes during a delay

Record the contact’s initial state, change one value while it waits, then check the next action. Repeat for lost eligibility, a completed objective and a corrected field. HubSpot says records must match branch criteria before reaching the branch; check the relevant values against the configured criteria.

Treat exit controls separately and include configured unenrolment controls in the acceptance check.

Verify data is ready at branch points

Branch criteria rely on exact matches, including spelling, capitalisation, spacing and format. For example, a value of “CA” does not match criteria set to “California”; include the configured value in the expected outcome for each case.

HubSpot recommends an 80-minute delay before a branch based on analytics such as page views, to allow analytics to update. It recommends a 5-minute delay at the start when branch values may not yet be populated, and before a branch that depends on an earlier action such as a form submission or engagement with email content.

If a branch depends on several properties being known, HubSpot recommends adding those properties to the enrolment trigger. When assessing the workflow, check that the configured data dependencies and timing give the branch the values its criteria require.

Key Timing Recommendations for Branch Conditions in HubSpot

Match the test method to the question

Use the Test criteria feature to inspect which enrolment criteria a record meets, then use the Test feature to check whether it will enrol and simulate its path after enrolment. The email-editor test sends a test email to a selected verified address.

Use the email editor’s test email to review how the draft appears in a verified inbox; HubSpot notes that its test sender differs from the sender set for the actual email.

For consequential actions, use a customer-safe rehearsal; see the dedicated guidance for detailed procedures.

Test Methods vs. Testing Objectives in HubSpot

Make the launch decision

Hold activation when an excluded record could receive a message, a required path has no outcome, an exit fails to block an action or a connected result remains uncertain. After a correction, recheck the affected case and any neighbouring case the rule change could alter.

At activation, inspect the treatment of records already eligible. HubSpot offers an immediate-enrolment choice; confirm whether existing eligible records should be enrolled now, check the first eligible population and assign an owner to review initial enrolments and action history. Later workflow edits call for a new check of affected paths.

Pros and Cons of Immediate Enrolment at Launch

Confirm release access

Check that the people responsible for final verification and activation have the required HubSpot permissions. Super Admin or Workflows permissions are required to use the workflows tool; editing branches requires Edit permissions or Super Admin permissions, and publishing requires Publish permissions.

Once the required checks are complete, have a user with publish access turn on the approved version.