Event and field marketing campaigns are often added to CRM systems after an event has already taken place. For example, an attendee list may be uploaded to Salesforce several days after a conference, webinar, or dinner, or Campaign Member statuses may be updated after the event.
When this happens, the date recorded in the CRM may not represent when the actual engagement occurred. This can affect how the event receives attribution credit in RevSure.
Why an Event May Not Receive Expected Attribution
By default, RevSure can use the Campaign Member Created Date as the date of the campaign engagement or touch.
Consider the following example:
An event takes place on May 10.
A lead attends the event and becomes an MQL on May 12.
The attendee list is uploaded to Salesforce on May 15.
The Campaign Member Created Date is therefore May 15.
From the CRM record alone, the campaign touch appears to have occurred on May 15, three days after the lead became an MQL.
Because attribution evaluates the campaign interactions that occurred before a funnel stage progression, this event may not receive attribution credit for the MQL conversion, even though the event actually happened before the conversion and contributed to it.
Common Symptoms
You may notice that:
An event has fewer attributed conversions than expected.
Leads who attended an event progressed shortly afterward, but the event does not receive credit.
Event attribution in RevSure differs from expectations based on Salesforce campaign membership.
Campaign Members were created or updated after the event occurred.
In these situations, it is important to confirm which date represents the actual customer engagement.
How RevSure Can Handle Late-Uploaded Event Data
RevSure can configure the appropriate engagement date for event campaigns so that attribution reflects when the interaction actually occurred rather than when the CRM record was created.
There are two common approaches.
Option 1: Use the Campaign Start Date
For event campaigns, RevSure can use the Campaign Start Date as the engagement date instead of the Campaign Member Created Date.
For example:
Event Date / Campaign Start Date: May 10
Lead becomes MQL: May 12
Campaign Member uploaded: May 15
Using the Campaign Start Date means RevSure evaluates the event touch as occurring on May 10, correctly placing it before the MQL conversion.
This approach is typically a good fit when attendees participated in the same event on approximately the same date.
Option 2: Use an Actual Engagement Date
If your CRM captures a specific engagement date for each Campaign Member, RevSure can use that field instead.
Examples include:
Attendance Date
Registration Date
Event Participation Date
Check-in Date
Custom Campaign Member engagement date fields
This approach provides greater precision because each Campaign Member can have an individual engagement date.
It is especially useful for multi-day events, event series, webinars with multiple sessions, or campaigns where registration and attendance occur on different dates.
Which Option Should You Use?
Scenario | Recommended Approach |
|---|---|
Single-day conference, webinar, dinner, or event | Campaign Start Date |
Attendee records uploaded after the event | Campaign Start Date |
Individual attendance dates are available | Actual Engagement Date |
Multi-day event or event series | Actual Engagement Date |
Registration and attendance dates differ significantly | Actual Engagement Date |
Whenever possible, RevSure recommends using the date that most accurately represents the actual marketing interaction with the person.
Result
Once the appropriate engagement date is configured, RevSure can correctly position the event within the buyer's journey.
This helps ensure that:
Events receive appropriate credit for subsequent funnel progression.
Campaign touches appear in the correct chronological order.
Event attribution more accurately reflects the real customer journey.
Attribution results better align with how marketing and sales teams understand the event's impact.
Important Consideration
Changing the engagement date does not automatically guarantee attribution credit. The event must still satisfy the attribution model's other requirements, such as the configured lookback window, funnel stage timing, campaign eligibility, and attribution methodology.
The purpose of this configuration is to ensure that late CRM data entry does not incorrectly make a real pre-conversion event appear to have happened after the conversion.