Skip to main content
NickMannion
Community Advisor
Community Advisor
Nov 12, 2026 1:06 AM UTC
Question

Destination Mapping workarounds

HI Everyone,

 

Wondering if anyone has found any workarounds for destination mapping for the following things:

 

  1. Mapping event data - I haven;t been able to map any event data in destinations since it is not on the profile snapshot. Anyone have any idea how to work around that?
  2. mapping segment membership for audiences that are not activated to the destination. I’ve seen that using segment membership for audience IDs that are not activated to the destination doesn’t populate with anything in a calculated field. Anyone know a workaround for this?

Thanks,

Nick

2 replies

arpan-garg
Community Advisor
Community Advisor
Nov 12, 2026 8:37 AM UTC

Hi ​@NickMannion  - There is no direct way of sending event data of a profile to a destination. Are the events which you would like to send outside of AEP present in a single dataset or are they scattered across multiple datasets? If they are present in single dataset what you could do is to use export datasets and then export it to some cloud storage like s3 etc. and from there on you can send it to the destination you require.

 

Thanks,

Arpan

Translate
ReenaJohn
Community Advisor
Community Advisor
Nov 12, 2026 9:44 AM UTC

​@NickMannion 

Here are some workarounds that i have seen working -

 

1. Mapping event data

Event data is not part of the profile export, so you need to get it onto the profile first, or use a different export path -

 

a. Computed attributes aggregate event data into a profile level value, such as last purchase date, purchase count in the last 30 days, or last product viewed. Once it is a profile attribute, you can map it like any other field.

 

b. You can use Query Service that lets you write SQL against the event dataset and write the result to a profile enabled dataset, then ingest it into Profile. This gives you the most flexibility, but it runs as batch, so check whether the latency works for your use case.

 

c. Dataset export destinations (like a cloud storage or AEPs Data Landing Zone) can export the event dataset directly if you need the true event level data downstream.

 

d. Event forwarding or AJO custom actions are options if you need event level data sent in real time. Event forwarding sends events server-side, and AJO custom actions send event or journey context payloads to an endpoint.

 

2. Segment membership for audiences not activated to the destination

 

The segment membership available to a destination mapping and calculated fields is generally limited to the audiences selected in that destination activation.

Audiences you have not activated there wont resolve, which is why the calculated field comes back empty.

 

Some workarounds could be these -

 

a. Building a composite audience. Audiences can reference other audiences, so create a new one with the logic you need and activate only that. This removes the need for the calculated field.

 

b. Activate the supporting audiences to the destination so they are in the membership map. The downside is that those audiences get sent downstream too, which may not be acceptable depending on the destination

 

c. Write the membership to a profile attribute. Using Query Service to read audience membership from the profile snapshot or export datasets and write it back to a profile enabled dataset, and map that attribute instead. This works but adds

latency and complexity.  

 

Warm regards 

Reena John

Translate