Oasis National Exclusion Database

Ensure customer eligibility from the National Player Exclusion database

Overview

This feature allows campaigns to check the Oasis national player exclusion database via a GiG integration to make sure a player is not registered to not receive messages of a certain type before a campaign is sent to them.

These checks are in addition to the usual Xtremepush subscription and segmentation checks and will run as part of the sending process at send time.

Switch on and configure

Can't see this feature?
This feature needs to be enabled on a project by project basis by Xtremepush Support. Contact us if you'd like to enable it.

Navigate to the Integrations Marketplace to enable the feature (Settings > Integrations > Marketplace). Select the Oasis National Exclusion Database card and enter the connection details before clicking Connect.

Once the integration has been set up, the feature can be used for both single-stage campaigns and multi-stage journeys. See below the different options for set-up.

Single-Stage campaigns

This feature requires using and applying a specifically configured engagement category to the campaign. To do so:

Set up the Engagement Category (from Campaigns > Engagement Categories > Add Category). Toggle on the option Use National Exclusion. When you do, an extra drop-down menu will show up to select the different categories. For details of exactly what each category is checking please refer to the GiG internal docs. You can also add this option to an already existing category.

Apply the category on a campaign: Select the engagement category from the Setup tab and the checks for National Exclusion will be done automatically at send time.

Only users with admin access can access and create Engagement categories. Once the category is created, marketers can just apply the engagement category on campaigns.

Multi-Stage campaigns

Journey campaigns also allow an Engagement Category to be selected at the campaign level. This will be checked at the point the user triggers the campaign, or the campaign is scheduled to run. If a user fails the check at this point then they will be prevented from entering the journey at all and so will be excluded from all following messages.

This check is ONLY done at the point of entering the journey, so to run a check at any other stage of the journey, there is an additional option which can be used to select a check category on each message step within the journey.

To add this to a message action, enable the toggle on the setup tab. This shows the same category selection as is found in an Engagement Category.

Time of send, recipient count and error checking

This feature will not affect the recipient's count and preview, as the API call is made during the message-sending process.

When the campaign sends, whether this is a scheduled send to a large number or individual triggers of a campaign, the users' details are sent to the exclusion API along with the information about which category the check should be done for. The service returns a yes or no result and this is used by the Xtremepush sending engine to determine whether the send is attempted.

If the response is yes the send to that recipient will continue with the rest of the usual check and send process.

If the response is no, the send will be treated as a failure and the details will be found in the notifications log, which can be accessed via Campaigns > Notifications log. To drill down on the specific failure, click on the Options menu > Details to the right of each row. This shows the Details page that shows the stats and error messages (both searchable).