Step 1

Welcome to the Intercom Tagging Custom Journey Builder Activity by Altus Digital. This activity is used to Tag or Untag Contacts from Intercom as they flow through SFMC's Journey Builder.

  1. In this step (Step 1) you will need to search for your target Intercom Tag
  2. Start typing the name of the tag in the search area
  3. Once the search is complete, select your desired Tag Name from the list below or select the "Create New" option if the Tag cannot be found
  4. You will know when this configuration step is complete when the "Target Tag Name" section is populated

Find your Intercom Tag

Name:

Choose your Intercom Tag

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 whether the contact should be tagged or untagged when they enter this activity.

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:

Choose your Intercom Tagging Action:

Step 3

Confirm your below configuration:

  1. Target Intercom Tag Name
  2. PIN Location Definition
  3. Intercom Tagging Action