Engagement Capture

An engagement records what a lead did, where the signal came from and when it happened. Email opens and clicks, form submissions, content downloads and webinar activity provide different kinds of context. Marketing Operations keeps those meanings intact when connecting source systems. A webinar registration should remain distinguishable from attendance when Marketing Manager decides which activity earns a score.

The event can also identify its program or email template. Those references help the team follow a message or journey into the resulting activity. Preserve the original payload with the event so an operator can investigate a disputed lead match. When contact details are unknown, leave them blank and resolve the source identity before linking the activity to a different person.

• Accept the signal. The ingestion workflow records activity from configured form, CMS, webinar and email-service webhooks. Map each source to the supported event and source values. Retain the occurrence time provided for the activity rather than interpreting an import as the customer’s action.
• Preserve correlation. Include the program and email template when the source identifies them. A URL, form code or content title can explain the event further. Check the linked local lead against the original source identifier, particularly when display names are similar.
• Review downstream use. Scoring uses the matching event type and rule policy. An engagement-based goal can also end a member’s journey. Marketing Manager agrees which action counts, while Marketing Operations follows the event into the resulting score or exit during rehearsal.

Name the owner of each source connection and agree how its lead identifier maps to the marketing record. Decide who resolves unmatched activity and how the team checks an incorrect correlation. Keep event time and source time conventions clear when importing older activity or investigating a delayed webhook.

Rehearse repeated input and compare the records produced before opening a larger feed. Preserve the original payload for the replay decision. Agree which signal supports the scoring policy and which one satisfies a goal; the same source may provide both registration and attendance. Sales Manager should understand the distinction before asking a rep to follow up on the resulting qualification context.

Submit a rehearsal form event with a known lead identifier, occurrence time and form code. Inspect the captured engagement and original payload, then confirm that the local lead link points to the intended person. Send a content-download event with the content title and include the program only when the source identifies that relationship.

Now send webinar registration and attendance as separate activities for the same lead. Ask Marketing Manager to review the agreed attendance rule, then trace its contribution to the matching event. Repeat with an unmatched identifier and resolve it without inventing a name or email address. The operator should be able to explain both the source action and the lead correlation before the event is used in a sales conversation.

• Engagements To Review — Source activities with event time, type and lead correlation.
• Lead Score Events — Contributions linked back to the activity that triggered the rule.

Trace engagement to scoring and agree source connections.