Step 1

Welcome to the Boombet Bet Return Integration Custom Journey Builder Activity by Altus Digital. This activity is used to apply Bet Returns to a Contact as they flow through SFMC's Journey Builder.

  1. In this step (Step 1) you will need to search for your target Bet Return Token
  2. The easiest parameters to use in "Field" are name & id and in "Operation" are like and equals. (the other search parameters work but may have unexpected results with an incompatible "Search Input" - seek support if you are having issues)
  3. Once the search is complete, select your desired Bet Return Token from the list below
  4. You will know when this configuration step is complete when the "Target Bet Return Token ID/Name" are both populated

Find your Bet Return Token

Step 2

  1. Firstly, input the location of the contacts Boombet PIN. You can use the Journey Data Tool below to find the location definition of the PIN if it exists in your Journey DE. Otherwise, you will need to use Contact Data (more information on this can be found in the Contact Data Info section)
  2. Finally, choose the number of Bet Return Tokens you wish to allocation the contact.

NOTE: Data Binding Expressions (values surrounded by {{ and }}) are case-sensitive

Journey Data is a snapshot of a contact's data from the Entry Event's DE at the time of entry into the Journey. This data never changes and persists with a contact for the duration of a contact's existence through a journey.

To use Journey Data choose the field that you want to use in the DE Insert

Use the below in your field value:

{{Event.xxx."xxx"}}

NOTE: Data Binding Expressions (values surrounded by {{ and }}) are case-sensitive

Contact Data is point-in-time data related to a particular Contact. This data is configured within Contact Builder's Data Designer feature.

Eg: A DE named Master_DE is linked in an Attribute Group called "Master Attribute Group". In this DE, the desired field for DE Insert into another Data Extension is named FavoriteColor.

To use Contact Data your field value for DE Insert should be configured as such:

{{Contact.Attribute.Master_DE.FavoriteColor}}

If multiple paths exist to the DE within Data Designer, the shortest path will be chosen. If multiple shortest paths exist, the SFMC will arbitrarily choose one. A contact must exist in all linked data extensions in order for the attribute to be successfully retrieved. To simplify this process, only use data extensions linked directly to ContactKey. If no contact key can be found, the activity will update the field value with an empty string.

Confirm your below configuration:

1
2
3
4
5
6
7
8
9
10

Step 3

Confirm your below configuration:

  1. Target Bet Return Token ID
  2. Target Bet Return Token Name
  3. PIN Location Definition
  4. Allocations per User