Expand my Community achievements bar.

Announcing the launch of new sub-community for Campaign Web UI to cater specifically to the needs of Campaign Web UI users!
SOLVED

AAM segment creation based on MCID failing

Avatar

Level 7

We can create and update segments based on Declared Id fine. We did find an issue (feature?) where a delivery adds a foreign key (@broadLog-id) to the target schema that you have to remove to get Declared Id segment update working. Once you remove that, the Declared Id segment updates fine.

However, we want to also create an identical AAM segment based on MCID for testing, but AC keeps throwing the error:

1637765_pastedImage_3.png

1637767_pastedImage_6.png

There is nothing in any documentation showing how to get MCID segments updating and the datasource just shows the same targeting dimension as the Declared Id segments (Recipient). The only difference in the datasources is the reconciliation key which is [trackingLog/@sourceId] for MCID.

Any ideas how we target for MCID segments?

1 Accepted Solution

Avatar

Correct answer by
Level 7

Ok I found the solution. For some reason, this works individually or if you fork the input into each activity instead of running them in series.

It would be great to know why this works and the other doesn't but i suspect it's "working as designed"

1638593_pastedImage_0.png

View solution in original post

1 Reply

Avatar

Correct answer by
Level 7

Ok I found the solution. For some reason, this works individually or if you fork the input into each activity instead of running them in series.

It would be great to know why this works and the other doesn't but i suspect it's "working as designed"

1638593_pastedImage_0.png