I ran into a scenario that I hadn’t seen in some time, where two simultaneous events are pushed into the event driven data layer (EDDL), but Adobe Launch was populating both Custom Link events ‘ variables with only the data from the second event.
Looking into the instrumentation, we can see that the system is using the Adobe Consulting – Adobe Client Data Layer extension to trigger the event and to populate the data element.
Having seen this type of issue in the past, immediately we look at how and when the data element is defined. We see that the configuration is using the Adobe Client Data Layer extension:
This is another example of why I don’t like to use third party extensions, there’s always a chance that they aren’t exactly what you need. When I saw this format for the data element, I decided to rewrite it using the native Custom Code data element:
What we do here is make sure that when the rule is triggered, using this format we can guarantee that the data element will use the values from the relative event. While the extension might intend to do this, it falls a little short.
if(event.message?.linkDetails?.linkName) {
return event.message.linkDetails.linkName
}It’s easy to want shortcuts, but there’s always a catch, and while you can root through the extension code…sometimes it’s worth it to just create your own solution.
