Once a Custom Action is used in a journey, it cannot be edited and needs to be duplicated if adjustments are required.

Each Custom Action has its own unique ID which is visible in the content strings:

It is persistent across journeys so can be saved as fragments, however these will need adjusting if a new version of the Custom Action is created.

Sharing engagement data to a Destination is, at best, possible every 3 hours. Therefore, this has limited use for broadcast optimisation (on email clicks / push channel).

For the data sharing to work correctly, we need to ensure that the ID shared in the tracking events can be matched correctly. This is achieved by the recipientID shared to Phrasee in the Custom Action API call being: Journey Properties > Identity > profileId.

Adobe applies a capping limit of 30000 calls/min (5000 calls/second) to each custom action host. So if there are Jacquard Custom Actions in more than 5 live journeys then additional throttling required (stricter than current 1000/second supported rate) to prevent exceeding this cap.