I’m working on a Marketing Cloud Next email response flow with three email buttons: Interested, Not Interested, and Unsure.
I’m using Wait Until Event → Email Link Click and then a Decision element to identify which button was clicked and update the Lead’s Email_Response__c field accordingly.
The issue is that the click event gives me $Event.ssot__LinkURL__c, but the URL is Salesforce’s rewritten tracking URL. I checked the corresponding Email Engagement DMO record in Data Explorer using the Engagement ID, but LinkName is blank, so I can’t reliably determine which of the three buttons was clicked.
I need to know the Salesforce-supported way in Marketing Cloud Next to identify the specific email link/button clicked from the Email Link Click event, and which field/resource I should use in the Flow Decision.
#MarketingCloudNext
Hii
Khushal,
The reason LinkName is coming back blank is the root cause here — it's expected behavior, not a bug, when links aren't given an explicit identifier at authoring time.
Why $Event.ssot__LinkURL__c isn't reliable
That field returns Salesforce's rewritten/tracked redirect URL, not your original destination URL, so matching on it directly in a Decision element is fragile.
Recommended fix: set a unique alias on each button
- In your email in the Marketing Cloud Next content builder, open each of the three buttons (Interested / Not Interested / Unsure).
- In the button/link properties, set a distinct Link Name (alias) for each — e.g. Interested, NotInterested, Unsure.
- Send a fresh test and re-check the Email Engagement DMO record in Data Explorer — LinkName should now be populated instead of blank.
- In your flow, keep your Wait Until Event → Email Link Click element as is, then in the Decision element branch on the Link Name resource (ssot__LinkName__c) instead of the URL field. This gives you a clean, exact match for each of the three outcomes.
Alternative, if you can't set an alias
(e.g. dynamic/personalized links)
Use the
"Resolve URL" Event Global Resource available on the flow canvas. Configure your Email Link Click event to trigger on "every link" rather than one specific link, then branch your Decision element on the resolved URL instead of $Event.ssot__LinkURL__c. This works even without a LinkName, as long as each button points to a distinct destination URL.Since your three buttons are static, setting the alias is the cleaner, more maintainable option — it's purpose-built for exactly this scenario and avoids any URL-parsing logic in your flow.
