Hi,This is very interesting question. I have a similar question.From my experience, once the organization unit (representing brand in your case) is added to the profile, the profile table becomes a brand-individual or brand-account level table. That means, the organization unit/individual is the nat...

That's correct. Since the tracking log recipient (TrackingLogRcp) is the lowest level, you query activity node has to be set at that level so you can pull attributes/columns from other higher level tables such as BroadLogRcp, Delivery, etc.Thanks.

Hi,Campaign users should not worry about "temp" tables and just focus on using the activity nodes. I believe if the customer can receive different personalized messages during the journey, there should be different delivery nodes and not trying to make one delivery do everything. It is the preferred...

Hi,You should be able to use the Tracking Log table since it is linked to the profile to identify EM engaged people. If you don't filter by a delivery, then you can identify and include/exclude people ever opened/clicked on any email.Adobe Campaign Help | Tracking messages Thanks.

I believe there is additional option (standalone or needed w/ the Genesis option), you can schedule a technical workflow to extract the required campaign data elements on daily basis from Adobe campaign mart (system tables) to SFTP site or push the files to Analytics. Keep in mind that via Genesis c...

Hi,Delivery code and segment code are two different attributes and they are populated in Adobe mart at two different levels. Delivery code is an attribute of Delivery (NMSDelivery) vs. Segment Code is an attribute of the universe targeted in a delivery and the proper location for segment code attrib...

Thank you for confirming.

I'm referencing the option to trigger/call the workflow from an external system and NOT running it through the scheduler.

Hi,Can you provide more details regarding option #1 (triggering a workflow)?

Can this be done on an operator group level? the goal here not to update the relationship table every time a new operator/user is being created/added to the system.