It's possible to automatically trigger a piece of content after end users have finished a certain step in their personal route. There are several types of content that can be triggered:

  • Diary
  • Template treatment
  • Template training
  • Template ROM
  • Template screening
  • Topics

Where to build in a trigger

It's possible to add a trigger to a normal page as well as a review/reflection moment or a milestone.

When does the trigger go into effect?

The trigger goes into effect as soon as the end user continues past the page containing the trigger.

Note: the following content types will appear on the client's home page when they are triggered: diary, template training, template treatment, template ROM and a template screening. However, if you trigger a “topic”, this triggered topic will automatically be placed behind the module. At the end of the module the client will automatically change to this triggered topic. Are you triggering multiple topics? Then they are placed in the order in which you triggered them.

How to build the actual trigger

You can build a trigger in just a couple of steps.

First check whether you have the programmer role assigned to you by clicking on your profile, then preferences and then by checking whether ‘Programmer’ is listed under groups. If not, first contact your application manager to have this role assigned to you.

Step 1 

For now, building a trigger happens in the raw code. To get to the raw code of your topic, you have to be in the edit mode. Once in edit mode, remove all the text in your URL after the word 'json':

After removing this text, add '/edit' to the URL:

Step 2

You've now entered the raw code of your topic. If you look closely you can recognize the different elements of your topic within the code. Scroll to the page that you want to add the trigger to. You can recognize the start of a new page by the text "type": "page".

Step 3

The right place for your trigger is after the text: "type": "page" . You do this by first adding a comma after "page" (,) and then entering the following code (of course replacing the content ID with the ID that you want to trigger). The page is then closed of by the }], "title" "TITLE OF CHAPTER" already in the raw code.

To copy you can use this code:

"triggers": [
                "tool": [
                    "id":"ID OF TO BE TRIGGERED CONTENT"

Step 4

All you have to do now is click 'save and view' and your trigger has been built. Once back in the regular edit mode, a small lightening bolt shows that the trigger has been successfully added. From now on you can directly navigate back to the raw code by clicking on the lightening bolt. You no longer have to edit the URL to get there.