After implementing Marketing Cloud Connect, the customer notices tracking details from Email Studio initiated sends...

For Marketing Cloud Connect to correctly write tracking data (sends, opens, clicks, bounces) back to the corresponding Contact or Lead record in Sales Cloud, the integration relies on properly mapped profile attributes that establish how a Marketing Cloud subscriber record correlates to a specific Salesforce record ID. If these mappings are missing or misconfigured, Marketing Cloud cannot reliably resolve which Salesforce record a given Email Studio send/tracking event belongs to, so the data simply fails to synchronize back, even though the send itself completes successfully. This is the first configuration a consultant should audit when tracking sync silently fails after an otherwise successful Marketing Cloud Connect implementation. Option A, folder placement of a sendable data extension, affects where the object lives organizationally but is not a driver of whether tracking data flows back to Salesforce. Option B, standard folder placement for reports, is a Salesforce-side organizational detail unrelated to the tracking sync mechanism. Option D, including the Email Address column in a report used for sending, is relevant to Report/Campaign-based sends resolving recipients, but does not by itself explain a broad tracking sync failure specifically tied to profile attribute mapping. Reference: Marketing Cloud Connect Configuration, Profile Attribute Mapping.