Frequency and capping for custom action

[akwankl]

Hi there,

We are using customAction to send signals to our 3rd party platform to send emails and SMS. I know there is the Rules - Message Frequency OOTB feature in AJO, but can that be applied to emails sent from custom Actions as well?

If not, can someone suggest a workaround that we can use this? For example, maybe I can create a subsequent action after the customAction - send email and feedback to an AJO dataset to however AJO would interpret and an email was sent out using the OOTB feature?

Thanks.

[SatheeskannaK · Accepted solution]

Hi @akwankl, You can’t use OOTB message frequency while using custom action. Couple of options,

• Consider creating a feedback loop after the action. If the third-party platform that you are calling has the option to post feedback data via a webhook endpoint, you could look to capture this feedback data as a new experience event, allowing you to record the response and then back to the individual profiles or use the response content to progress profiles through a journey further.
• Get the feedback data from 3rd party system and ingest that as a flat file using sftp/amazon s3/azure blob and capture that in the new experience event schema.
• You may have already looked at some of the guardrails around custom action.

[AnanthanJa]

Just one call out, reaction event seems to work only for Email and Push. It does not seem to work with custom actions. Hence usage of reaction activity might not work. 

The customer can use profile update activity to update the count of emails or SMS sent for the week if all custom actions are considered successful. The customer also needs to zeroise the counts at the end of the week using a scheduled query. 

Using a custom feedback loop will have additional complexity as the counts from the custom feedback event dataset need to be aggregated at a regular frequency by using scheduled queries data distiller or computed attributes. This will add some lag time where the count of deliveries can get over the scheduled counts if more journeys are running in parallel which is using the custom actions.