Events
An event is something that happens, for example something customer does, such as making a purchase, or something a customer does not do, such as not visiting a web site in the last 90 days. Program provides predefined events, as well as custom events that can be defined in the Responsys Event Interface or from the Account page. The End event and timers are used to terminate a program flow.
To specify event settings, right-click an event on the canvas and select Properties.
For any of the starting events, you can choose how to handle program entries associated with that event stage:
- When a person is not currently in the program, the system automatically creates a new program entry for that person.
- When a person is already in a program, you can select one of the following options in the event properties dialog:
- Create a new entry in the program
The person will be in the program more than once. - Do not create a new entry in the program and leave the existing entry where it is
Ignores the new attempt to enter the program. - Do not create a new entry in the program and move the existing entry to this location.
Pulls the existing program entry from its current location in the program and starts it over at the new event location. A program can include more than one start event. This option moves the existing program entry to a new starting spot.
- Create a new entry in the program
Note: For custom events, you can match program entries based on Program Entry Data rather than RIID.
Available starting events
A program must start with one of the following starting events:
- Get an audience
- Intelligent Audience Selector
- Connect
- Customer activated
- Customer deactivated
- Custom event
- REI custom event
- Beacon entry
- Beacon exit
- Geofence entry
- Geofence exit
- Scheduled filter or view
- SMS received
- Cart abandon
- Browse abandon
- Purchase
- Catch event
Get an audience
Create enactments from a published audience result set. For more information about audiences, see Audiences--Overview.
Important: This feature is available as part of the Advanced Intelligence Package add-on that must be ordered for your account. Please contact your account manager or Oracle sales.
The Intelligent Audience Selector is a starting event that determines which contacts to bring into your program based on the behavior of current and past program members. In this way, the Intelligent Audience Selector can increase the program's engagement rates over time. This stage is for recurring programs only and not intended for one-time programs.
Intelligent Audience Selector
Important: This feature is available as part of the Advanced Intelligence Package add-on that must be ordered for your account. Please contact your account manager or Oracle sales.
Over time, the Intelligent Audience Selector helps marketers maximize on their investment by:
- Adding contacts to the program that, based on behavioral data such as Opens, Clicks, and Conversions from the program's previous and current contacts, are predicted to produce a high ROI.
- Reducing the time that marketers need to spend in frequently changing and determining the criteria for the best performing audience for a Program.
To configure the Intelligent Audience Selector stage, set up which filters it should use to determine the intelligent audience:
- Run this filter against your Profile List
Select the filter that Program will use to pull contacts into the program. Initially, Program brings the contacts in using only the filter, then, over a period of time, Program will bring in the intelligent audience in addition to the filter. - Filter for Intelligent audience (optional)
Optionally, select a filter that Program should apply after the Intelligent Audience Selector pulls in contacts automatically. - Total Maximum Audience (optional)
Limit the total number of contacts that will be intelligently selected for each recurring run of the Intelligent Audience Selector. For example, if you set this maximum to one million contacts, and then you run the program weekly, each week the Intelligent Audience Selector would be able to bring in up to one million contacts.
Additionally, you'll need to configure the frequency at which Program will pull in contacts—whether it's from the filter or an intelligent audience—and specify what should happen if Program wants to pull in a contact who is already in the program at a different stage.
Once Program has made an intelligent audience selection, double-click the Intelligent Audience Selector stage in the Analyze tab to view the Intelligent Audience performance report with the open rate, click-through rate, and conversion rate.
Connect
Detects completion of a Connect import job that was designated to raise an event. You designate which jobs raise an event in Connect, then select the job from the Listen for Connect job completion drop-down list on the Connect Event Properties dialog.
For more information, see Creating Import Jobs.
Customer activated
Detects activation (opt-in to the associated List) of a customer.
Tip: This event is available from the Interactions menu on the palette.
Customer deactivated
Tip: This event is available from the Interactions menu on the palette.
Detects when a customer opts-out or becomes undeliverable in one or more channels. For example, an email hard bounce.
To remove a unsubscribed or undeliverable customer from a program, add a Customer deactivated event to the program, connect it to an End stage, and select the rule to remove the recipient.
Custom event
In association with account-defined custom events (see Defining Custom Events with the Account Page), these events can be triggered by loads (manual or automated), form submits, or Web Services.
If your account is enabled for real-time custom events, those events will be displayed with a check mark icon in the Listen for custom event type drop-down list. If you select one, the custom event icon on the program canvas will also be flagged with the icon.
REI custom event
Important: This event is only available if REI is enabled for your account.
A signal from an external source that alerts Oracle Responsys when notable customer activity occurs and should be recorded, or alternatively when a notable activity occurs to a customer. On occurrence of an REI event, programs that are listening for the event create enactments for the REI event.
Two or more REI custom events can only be in the same program so long as they have different names.
Beacon entry
Important: This event is only available if REI is enabled for your account.
Detects when a customer enters a beacon's range. Learn more about this event.
Note: Oracle Responsys provides an open solution that will work with any Geofence and Beacon SDK / Product.
Beacon exit
Important: This event is only available if REI is enabled for your account.
Detects when a customer exits a beacon's range. Learn more about this event.
Note: Oracle Responsys provides an open solution that will work with any Geofence and Beacon SDK / Product.
Geofence entry
Important: This event is only available if REI is enabled for your account.
Detects when a customer enters the area you have indicated as a geofence. Learn more about this event.
Note: Oracle Responsys provides an open solution that will work with any Geofence and Beacon SDK / Product.
Geofence exit
Important: This event is only available if REI is enabled for your account.
Detects when a customer exits the area you have indicated as a geofence. Learn more about this event.
Note: Oracle Responsys provides an open solution that will work with any Geofence and Beacon SDK / Product.
Scheduled filter or view
Runs a filter or a saved SQL view against the associated List once or on a recurring schedule (daily, weekly or monthly) and feeds all matching customers into the program. You can set the specific time of day to run the filter or refresh the SQL view.
Note: As of 20C, Web Push filters can be used with this stage.
You can choose any SQL view associated with the same profile table as the program. The requirements for using a SQL view in a program are:
- To return an RIID value, the SQL view must have a join with the profile table (list).
- The SQL view must have the RIID as the data extraction key.
- The profile table must be the first table selected to join.
The columns selected in a SQL view are not available in data switches in the program. If you delete a supplemental table that is used in the SQL view, the program will not run.
If the SQL view associated with a program generates duplicates, the customer receives duplicate messages because Program does not support de-duping.
To create a new audience each time a group enters the event, make sure the Create a new audience check box is selected. This is used in program monitoring. If you do not select this option, a new audience overwrites any previously created audience. For more information about monitoring, see Analyzing programs.
SMS received
Important: This feature is only available if Oracle Responsys SMS is enabled for the account.
Tip: This event is available from the Interactions menu on the palette.
Detects that a customer sent an SMS message to one of the selected codes with one of the selected keywords.
For more information about Oracle Responsys SMS, see Oracle Responsys SMS Overview.
Cart abandon
Important: This feature is only available if Rapid Retargeter is enabled for the account.
Tip: This event is available from the Interactions menu on the palette.
Detects that a shopper put items in a shopping cart but did not complete the purchase.
Browse abandon
Important: This feature is only available if Rapid Retargeter is enabled for the account.
Tip: This event is available from the Interactions menu on the palette.
Detects that a customer browsed your website without progressing to the shopping cart.
Purchase
Important: This feature is only available if Rapid Retargeter is enabled for the account.
Tip: This event is available from the Interactions menu on the palette.
Detects that a customer made a purchase.
Catch event
Tip: This event is available from the Cross program events menu on the palette.
Catches any enactments passed by the specified cross program event. Cross program events are defined for an account by the Account Administrator. For more information about the catch event, see Passing enactments between programs below.
| Name | Description |
|---|
Passing enactments between programs
Use the Throw event and Catch event (available from the Cross program events menu) to pass enactments between programs. You might use these events, for example, to reuse common program paths, or to simplify a program that has too many stages.
Throw event and Catch event use the cross program events created by the Account Administrator for the account. Any program can pass (throw) enactments to a cross program event, and any program can receive (catch) the enactments from the same event.
To pass enactments to a program:
Use Throw event to pass enactments to other programs listening for the same cross program event. Note that many programs can throw and catch the same cross program event. The Throw event does not remove enactments from the original program, they may continue through the program. To specify the cross platform event to throw, double-click the Throw event on the canvas and select the event from the Select throw event list.
To receive enactments from a program:
Use Catch event as a starting event to receive enactments from other programs. Note that many programs can catch the same cross program event. To specify the cross platform event to catch, double-click Catch event on the canvas and select the event from the Select catch event list.
Ending events
You can end a program with either a Throw event or an End event.
The End event terminates a program flow. When customers progress to an End event, they exit the program. They also exit if they encounter an activity with no further connecting stages. Although End events are not required, it's important to prevent infinite loops by always including an exit condition that completes the flow of customer interactions.
The Throw event passes enactments to other programs.
Next steps
Geofence and Beacon Event Variables