Managing Master and Child Events in Salesforce

One of the most frequently misunderstood features in Salesforce is how events are created and managed, particularly the relationship between master events and child events. Understanding this distinction is critical for accurate activity reporting and pipeline visibility.

This guide explains what child and master events are, why they matter, when to filter them out, and how to build effective reports that avoid double-counting activities.

When you create a meeting in Salesforce with multiple attendees, Salesforce automatically generates one master event and then creates a child event for each additional attendee. This behavior is built into the Salesforce platform and cannot be disabled.

For example, if you hold a meeting with one other internal sales rep and one external contact, Salesforce creates:

This happens automatically with no configuration required.

The child event structure ensures that each attendee has visibility into the meeting from their own record. This is particularly useful for org-wide activity summaries because it fairly attributes activities to all participants, not just the meeting organizer.

Child events are extremely useful for certain reporting scenarios:

When tracking overall team or individual rep activity levels, child events ensure fair representation. If you want to measure: How active are my reps overall? or How much activity is happening across the team?, then including child events is appropriate. Each attendee should be credited for their participation in the meeting.

A common chart groups activities by assigned rep and date, filtered to show only events over a recent time period (last 7 or 30 days). This visualization becomes more meaningful when child events are included:

With child events: You see that all 3 reps who attended a meeting are counted, reflecting actual team engagement.

Without child events: Only the organizer is counted, understating activity for supporting team members.

The double-counting issue arises when you report on a specific account or opportunity:

When you ask: How many activities has this account had? or What's the activity level on this opportunity?” the presence of child events distorts the count. Each child event appears as a separate activity, making a single meeting appear as multiple activities.

Scenario:

You have a meeting with two internal sales reps related to Account ABC. Salesforce records this as:

1 master event on Account ABC (same date)

1 child event on Account ABC (same date)

Your report shows 2 activities when there was actually only 1 meeting. This inflates activity metrics and can mislead stakeholders about engagement levels.

Salesforce stores information about whether an event is a child event in the IsChild field. Unfortunately, this field is hidden in the standard Salesforce interface and is not directly accessible in standard reports.

The recommended solution is to create a custom formula field that exposes this hidden IsChild field, then use it as a filter in your reports.

Navigate to:

Name the field something descriptive, such as:

Field Type:

In the formula editor, enter:

This formula references Salesforce's hidden IsChild field and returns a simple true/false value.

Once the custom field is created, you can now:

Scenario

You're building an account-level activity report. You want to answer: How many activities has Account ABC experienced in the last 30 days

Before Filter (With Child Events):

After Filter (Master Events Only):

Same event, same date, but the child event artificially doubles the count. After filtering, you get an accurate count of 1.
​

Include a note on your report explaining whether child events are included or excluded, and why. This prevents confusion when stakeholders review the data.

While it may be tempting to build flows that automatically delete child events, this is not recommended. Child events have legitimate reporting uses (e.g., individual rep activity tracking). Filtering is a better solution than deletion.

Activity reports are most insightful when scoped to a recent period (last 7, 14, or 30 days). This makes trends easier to spot and reduces noise from stale data.

No. Child event creation is an automatic and built-in Salesforce behavior. There is no configuration setting to disable it.

No. Child events exist only within Salesforce. They do not appear in external calendar applications. Only the master event syncs externally.

No. The IsChild field is hidden and not accessible through the standard Salesforce report builder. You must create a custom formula field to access it.

Many activity capture platforms (like WeFlow) have built-in options to report on and filter by child events. Check your app's reporting documentation for native filter options before building custom fields.
​

Child events are a fundamental part of how Salesforce manages multi-attendee meetings. They serve important purposes for rep-level activity tracking, but they can distort account and opportunity activity metrics.

By creating a simple custom formula field and filtering appropriately in your reports, you can leverage the best of both worlds: fair activity attribution at the individual level, and accurate activity counts at the account and opportunity level. The key is understanding your reporting goal and applying the correct filter.