Now we have created a simple event and viewed it in a Profile – let’s get some more interesting data in the profile. This will allow you to create some segments and take action based on data in the Profile.

For this tutorial head to “Web Data Collection.”

Session Data

Session data is aligned to a particular session. Let’s add some simple session data – the referrer where the visitor has come from.

Click on the “Session Data” tab and “create new session data “. Fill in the details.

Now, go to the “Events” tab and create another event – naming as an example below.

In the Rule builder window select “Page Load” Building Block as the trigger (look under Triggers, Basic).

Now select “Referrer” under Traffic Source from the building block category Data.

 NOTE: You can always use the search box to find triggers, data or conditions.

The Referrer should be inserted in the Session Data area (not “Event data “ or Profile Attributes). Select “String” as the value type.

On every page load, the referrer will be captured and put into Session Data. However, this means that the initial referrer (for example from Google) will be overwritten when the visitor clicks to another page and the referrer will become your own website URL.

Select “Restrict per Visitor, Session or Page Load” building block from the category “Conditions”. When the building block has been added in the editor, double-click on it and select “restrict per session”.

This now means the data is only captured once per session.

The Rule should look like this:

Remember to save the event. You can also check it on your website in Dev mode as shown in Getting Started 1.

Define the event

There are different ways of creating this kind of an event. When you perform a search on you will be directed to a result page. The result page always contains a query parameter in the url (q=searchterm). In this example, we are going to use that parameter to define the search event.

Select the “trigger page load”

Select “Query Parameter” building block. Add it to the editor under “Event Data”.

Click on it and enter the Query string parameter that identifies the search term. In the mondify case it is “q”. Note you don’t need any other characters.

hit “OK”. The Search Term will now be added as an event to the profile.

In order to only trigger this event when a user has performed a search, a condition has to be added as currently, the search event will always return the value of “q” whether it is present or not. If it is not present, the event will return an empty value. Avoid this to happen by adding the building block called “Value is not empty” under the category “condition” and connect it to the query building block as below.

Profile Attribute

Profile attributes are ‘facts’ about individuals. These can change but won’t change with the same frequency as events. Good examples of Profile Attributes would be your loyalty status, name, email address or demographic information.

Click on the “Profile Attributes” tab. Create a new Attribute and call it “Browsing Method”. In this, we are going to store the value “Searcher” if the visitor uses the search box.

Go back to the search event.

Select “Static String” building block under category data. Drag it into the Profile Attributes in the editor. Double Click and enter these details:

When the event is triggered the Word, Searcher will now be added to the Profile Attribute called Browsing Method.


The “Search Behavior” event should look like this.

Test your event by performing a search on mondify with the “dev mode” on and go to your Profile and check if the intended data is visible on your profile.