When an offer activity runs, fulfillment occurs in accordance with the offer activity’s specified channels.
Where an individual qualifies to be contacted by more than one channel, contact is made via the first applicable channel for which he or she qualifies. Channel applicability is determined by the channel’s filter. The filter is defined as a selection rule; if a record is targeted by a selection rule associated as a channel filter, that channel is deemed to be applicable for the record.
Results of the execution of an offer activity are written to the permanent offer history and offer history meta tables (the actual table names are defined by audiences’ audience definitions).
In addition, fulfillment activities take place in accordance with the channels’ delivery method. Each delivery method is documented separately.
Following execution of an offer activity, a results bubble is displayed to the top right of the offer activity icon. It shows a rounded summary of the number of records in the results set. Results are shown to a single decimal place, e.g.:
1,203,492 = 1.2M
75,854 = 75.9K
Full results are available in the Results Window.
Contacts made through a particular channel may be further restricted if the channel used has been associated with a filter. In this case, fulfillment will only take place in respect of those records that are targeted by the filter’s selection rule.
You can invoke Stop or Pause at an executing email, push notification, SMS, data onboarding or CRM offer. Having done so, you can Play the activity again. Any records previously targeted by the offer will not be targeted upon resumption of execution.
When the number of records targeted by an offer activity (or export activity configured to use a data extract channel) exceeds its channel's Targeted warning threshold, the activity enters a Paused state. This applies in both Test and Production mode. Log messages are written to advise as to why this occurred. If required, Channel Targeted Threshold Exceeded email alerts are sent. You can click Play at the activity to resume its execution. Note that a threshold check is applied per individual fulfilment occurrence - e.g. one specific email send within a recurring trigger.
If the offer's channel's Fail if no merge files property is checked, the workflow will fail when zero records are targeted, with the message 'No mail merge has been generated; sending will be terminated' being shown in the log.
If the channel is configured to call an external service post-execution, that service is invoked immediately upon channel execution. If an invalid service address was supplied at channel configuration, execution continues without failing.
If a channel is configured to call a Redpoint Data Management job post-execution, not that the job will be called when executed in both Test and Production mode.
Following production execution of an offer activity when offer approval is enabled, if you view the Completed offer’s configuration panel and drill through to the offer’s template, the version displayed is always the latest – even if a prior version was used at interaction execution.
Note – if executing an offer against a Google BigQuery data warehouse, and having applied offer metadata overrides at the interaction, the potential exists for lengthy delays to occur.