Getting Started

Profiles in Profile Cloud contain two main types of data: “Event data” and “Attributes”. Event data are typically used to track user actions. On a website, you would set up Event data for tracking things like page views, logins, clicks, or similar. Let's create some event data in the profiles now for the visitors.

Create a new Event

Click on the “Events” tab inside APSIS Web Data Collection.

Click on “Create New Event Definition”

You now have a few details to fill in. We have given an example below. All fields are not mandatory so you can skip the optional parts for the tutorial.


Name: Pagename
Save to Profile: Yes

Click on “Create”.

Define the Event rules

This is a simple event that captures the page name.

There are different things we need to define for an event. Events are comprised of a few different components: Triggers, Conditions, Data and Tags.

In the left-hand side of the event editor, there is a library of components corresponding to each area of the editor. These components are called Building Blocks. Profile Cloud offers a number of pre-created Building Blocks, and you can also create your own if you need some custom functionality.

Each Building Block helps you to create the rule which defines the Event.

Select the Trigger

For this simple event select the Building Block “Page Load”. To find it click on Triggers > Basic > “Page Load” or type “page load” in the quick search bar.

Double click on “Page Load” in order to get the building block to the corresponding area in the editor.

By adding the trigger “page load” to the event, will make the event trigger once a page has completely loaded in the browser.


Define the Data

When trigger has been defined we will now need to add a data value to the profile. In this particular case, we want to pick up the page url from each page the user brows on.

Select the “Page URL” Building Block. To find it go to Data > Page > “Page URL” or just use the quick search and search for “page url”.

Add it to the editor by double-clicking on it. Double click on it again, to save the event data to the profile by ticking the “Save to profile” box. The result type should be “string”.

Click OK.

Now click the Save button on the top-right of the screen.


Test your events

Before you can test your event, you need to install a Profile Cloud functionality to allow you to see what events are triggered on the website. In below guide, you will also add 2 other functionalities that will be useful later on.


In the APSIS web data collection app, click on “setting”.

Under the tab setting, you have 4 bookmarklets as below screenshot. To test your events you only need the “dev mode” bookmarklet. For future use of Profile Cloud, you will also need to add the “onsite widget” bookmarklet and the “profile ID” bookmarklet. All four bookmarklets are described below but for this tutorial, you will only need to add 3 of them, “dev mode”, “On-site widget” and“Profile ID”

Drag and drop the “dev mode” Bookmarklet to your browser toolbar. If you don’t have the toolbar visible in your browser, enable it under your browser settings. For further help on your browser´s bookmark bar use below links:






1) Get Profile ID

You can use this Bookmark to find your Profile ID on your website when Profile Cloud is installed. This is useful for checking what data is in your Profile when implementing Profile Cloud.

2) On-site widget

This widget helps you configure Profile Cloud rules by allowing you to point-and-click select elements on your site. We'll see this in action later on.


3) Dev mode*

When you are making changes to the website using Profile Cloud this bookmarklet allows you to check them without pushing those changes to production.

When you have installed the bookmarklets. Go to and click on the “dev mode” bookmark.

When you click on “dev mode” a widget will appear on your screen at the bottom right corner. Click on it.

Now you will see all Profile Cloud events that are triggered. In this tutorial, you should have an event called “pagename”. This event is triggered on all page loads that occur on

Great. You are now collecting a simple event in all Profiles from your website. Let's see what a Profile looks like with your newly created event.

Next Step

2. Viewing a Profile

Now we have created and tested it on “dev mode”. Let's see what your Profile looks like.

On, click the “Get Profile ID” Bookmarklet. A window will appear with the Profile ID ready to be copied to your clipboard.

Profile Overview

Go to the Visualize menu and click on “Profiles Overview”

The Profiles Overview dashboard will look like this with probably less “recently active profiles” as your account will not have as many profiles yet.

Copy your Profile ID into the box and click “View Profile.”

The Profile

NOTE: This Profile View assumes the only event enabled is to capture the Page URL.

Your Profile should look something like the above. Here is some information about the different areas.

General Profile Info
Summarised information about the Profile including Events triggered over time, activity summarised by day of the week and the Pie Chart will show the share of event activity by different types of session. Location is IP based.
If the Profile fits into any segments they will be shown here.
If the Profile has any Attributes they will be shown here.
Events are grouped into Sessions. Summary information on the Session is shown here.
The stream of events is shown. As we are only collecting Page URL currently, those are shown with screenshots.

Try clicking around your website more to collect more Page URL’s. If you access your website from a different location, that will be shown on the map.

Next Step

3. Adding Profile Attributes & Session Data

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.

Profile Cloud works with lots of different marketing channels but the best place to start is with your website. This is how to generate your websites unique Profile Cloud Script.

Create a Bucket

Buckets allow you to manage data, Apps and users in your organisation. Typically you might have a different bucket for each geographic market. Or perhaps for each brand.

Make sure you have a new Bucket if you are implementing Profile Cloud (don't implement into a Sandbox bucket for example).

Click on “Bucket List” then on “Create new Bucket.”

You can then fill in the relevant details.

Create a New Section

To generate your website Script, go to “Web Data Collection” in the Collect menu.

Profile Cloud provides different code for each Section. Typically you would install one Website per Section.

Let's create a new section. Click on the box on the right and click “Create New Section”

In the dialogue box fill in the website name. The ID is automatic.
ID: mywebsitecom

Now click “Create”.

Add Website Details

Add the default URl for your website, typically the homepage. Click “Save”.

Copy the Code

You can now Copy the javascript snippet shown in the box. Remember, this script can always be downloaded from the settings area in “Web Data Collection” under the “Collect” menu.

Installing the Code

On every page of your website, place APSIS Script AFTER inclusion of jQuery library (if your website uses jQuery). We recommend placing the Script in the head section of HTML code, as it is optimal for onsite personalization cases.

Example Code (don’t use this example):

<script type="text/javascript" src="/javascripts/jquery/1.9.1/jquery-
<script type='text/javascript'><!--
(function () {
var swDc = document.createElement('script');
swDc.type = 'text/javascript';
swDc.charset = 'UTF-8';
swDc.async = true;
swDc.src = ('https:' === document.location.protocol) ?
cd3.js' : '';
var a = document.getElementsByTagName('script')[0];
a.parentNode.insertBefore(swDc, a);



APSIS JavaScript file uses the Akamai Content Delivery Network for its distribution. Akamai is recognized as the largest and fastest network in the world, operating 100,000 servers in 71 countries to ensure fast delivery in all locations. The JavaScript file is loaded asynchronously; it is perfectly invisible for the visitors of the website and does not impact the rendering of the pages.

For more information about Akamai:

Next Steps

5. Adding Profile Cloud Bookmarklets to your Browser

Now you have installed the Script on your website, you now need to install some simple Bookmarks to help you work with Profile Cloud.

Profile Cloud has a few helpful bookmarklets to make working with Profile Cloud easier. Install them now to help with the rest of the steps.

Now that you have installed the script on your website, you can find the Bookmarklets in the same place, under the Settings tab in Web Data Collection.

Drag each Bookmarklet to your browser toolbar.

1) Get Profile ID

You can use this Bookmark to find your Profile ID on your website when Profile Cloud is installed. This is useful for checking what data is in your Profile when implementing Profile Cloud.

2) On-site widget

This widget helps you configure Profile Cloud rules by allowing you to point-and-click select elements on your site. We'll see this in action later on.

3) Dev mode*

When you are making changes to the website using Profile Cloud this bookmarklet allows you to check them without pushing those changes to production.

4) Live mode*

This bookmarklet takes you out of Dev mode so you can test the current website experience.

*Profile Cloud Web Data Collect supports two modes: dev mode and live mode. Dev mode is updated immediately when you make configuration changes in the Profile Cloud admin interface, while live mode requires you to make a 'deploy' action. By toggling to dev mode (using the bookmarklet), you can test your Profile Cloud configurations before making those changes available to all your site visitors. We will show this in action in later steps.

Bookmark Bar Help

If you are having difficulty getting the bookmark bar to work in your browser try these links.




Next Step

1. Creating your first Events

 Now that you are all set up we can create some events to add to the Profiles.

Define, trigger and deploy a pop up in a few steps using the APSIS targeted pop-up. The pop up can be used on all your visitors or just a segment. There are possibilities to add dynamic content to you pop up to make most of the personalization capabilities. This article will give you a step by step guide to activate a static pop up for your audience.

“Targeted popup” is APSIS own build pop-up functionality. Enable it from the app store and activate it from the web data collection app.

  1. Add the tag “Targeted popup element” to the canvas and double click on it. Create and define your own content, design, size, position by changing the “HTML”, “CSS in frame” and “CSS of iframe”.

  2. Add a suitable trigger. Most commonly used for a pop-up is “Page load” and “Trigger after x seconds on page

  3. Add conditions and restrictions e.g. what page or section to show the pop up message on and any eventual segments. Please also be aware of the number of time to show the message. A commonly used condition is “restrict per session/visitor

  4. Example:

Personalizing website content is one of the most popular Projects in Profile Cloud. There are different ways to change content with Profile Cloud:

  1. Using APSIS Personalization App. In this case, Profile Cloud changes the content on the website through a process called DOM manipulation. It works for any website and allows you to use a WYSIWYG (what you see is what you get) tool to pick the area to change.
  2. Using a Content Management System (CMS) integration. In this case, Profile Cloud simply tells the CMS what segment a Profile is in, allowing the CMS to change the content.

This article will describe of how to change content using the first option i.e. using APSIS Personalization App.


  • APSIS Personalization app installed in your account. Click here for more info.
  • The on-site widget bookmarklet is installed on your browser. Click here for more info.
  • APSIS javascript implemented on the website. Click here for more info.

The on-site personalization is executed by an event in the web data collection app. Go to web data collection and create a new event definition.

 (Explanation of each field below the screenshot)

  1. Event selection - dropdown: Select an already existing event to trigger the personalization or create a new event for triggering the event. As a personalization event might be active only for a short period of time, it is recommended to create new event definition in order to avoid changing existing events.
  2. Name: Name of the event. It is recommended to use a descriptive name in order for all users to understand what the purpose of the event is and to keep track of all the events.
  3. ID: An ID is generated by APSIS Profile Cloud. No action is needed from the user. This ID can be used by developers to define the event on a technical level.
  4. Category: Add the event to a category or create a new category in order to keep a structure of your organization events. It is optional. It is however recommended to create a category structure for keeping track of all the events.
  5. Description: Add a description of the event. This description will appear in the event to inform the purpose of the event. It is recommended to add a description but optional. The functionality and purpose of the event and perhaps an end date if the event is running during a specific period of time.
  6. Save to profile: Decide whether this event is to be saved in APSIS Profile Cloud. In some cases, it might not be relevant to save this information to APSIS Profile Cloud. In most cases, it is valuable to save to APSIS Profile Cloud for example if it is intended to use APSIS Profile Cloud segments or other profile info for the event.


In the event editor the “personalization app” is available under a category called “Tags”

Add the element to the editor by clicking on it. Now double click on it again. By clicking on “GO” your browser will refer you to the page stated in the field. Add the url where the personalization will be taken place or click on “GO” and navigate to the intended area to personalize.


When you are on the page where the element that is going to be personalized, click on the bookmarklet “On-site widget”. Click here for more info on how to add the “on-site widget”.

The onsite widget will now appear on your screen.

When the onsite widget is visible on the page you will now be able to select an element on the page with the cursor. The element/content will show up in the onsite widget as below screenshot.

In the drop-down list, upper right corner of the onsite widget, you will now have to define how you want to change the selected element. The options depend on what type of element that is selected.


The most used options are “change image” and “HTML editor”

  1. Change image: Replace the selected image with another image by uploading the new image to profile cloud server.
    When an element has been selected, simply click on “upload file” and select the image you want to replace or add an image URL directly into the onsite widget.

  2. HTML Editor: Change content by HTML. This option is used to create more dynamic personalization as it is possible to add dynamic variables into the HTML editor and depending on the profile, point to different content. Read more on how to add dynamic content here.
    When an element on the page has been selected and the HTML editor is selected, change the HTML. Change for example the image url as in the below screenshot.

  3. WYSIWYG Editor: Change content on the site by editing the selected element.

  4. Remove Element: Remove the element completely from the page.

When the wanted changes have been done, click “Save” and go back to the event definition page. Click on “OK” on the personalization tag

At this point, the content change has been defined. A trigger has to be added. For personalization events the trigger “Page init” should always be used as this will trigger while the page is loading and not after which is necessary in order to avoid latency in the change of the content.

You can now test the content change by going to the page and click on the bookmarklet “dev mode”.

Define the segment you want to apply the personalization on by clicking on “add segment”. All created segments will be selectable from the list that appears.

Click Save and test it with the “dev mode” bookmarklet.

The last step is to deploy it on production.  Read more on how to deploy here.

Sending data to Google analytics through Profile Cloud is commonly used by Profile Cloud users. Be aware of the different versions of google analytics, the “old” version and the newer Universal Analytics. This article will describe how to use the Universal Analytics. For more info about Google Analytics click here.


  • Your Google Universal account ID UA-xxxxx.
  • An event already created with an event value that you want to send to Universal Analytics


Define an event with a data value to send to Universal Analytics. In below example, a building block with the data value “product name” has been defined.

This event will fetch the product name on each product view and store it to Profile Cloud. Profile Cloud does not consider the value you want to send to google analytics.

This procedure is applicable to any value you want to send. Make sure to create an event that corresponds to what you want to send. There are some limitations of what Google universal accepts as values. For instance, email addresses will not be accepted by Google.

To send this value:

Add a Google Universal tag to the canvas. The tag to be used depends on what report you intend to send it to. For more information on the Universal Analytics, variables can be found in Google Help Center.


Drag or double-click on the Universal element, in this example “Custom dimension or Metrics”

Connect the intended data value, in this example “Product Name” to the Universal element.

Double click on the element to open the form where you can edit the settings.

  • Account ID: Add you Universal account ID. (UA-XXXXXX)
  • Type: Select whether you want to send this as a “Dimension or Metric”. Read about the differences in Google help center.
  • Index: Define what index you want to set it to
  • Value: The intended data value to send – The options will be depended on what data values that are connected to the element. In this example “Product Name

Click OK and save the event.  Whenever this event is triggered the value will be sent to your Google Universal account. Test it in dev mode and verify in your Analytics account. Keep in mind that some reports in Google Analytics visualize the data with a delay. When ready go to the deploy-tab under web data collection and deploy.

A popular app to send triggered email is Mandrill. Install the Mandrill app and open a Mandrill account.


Before you start defining when and to whom to send the triggered email to there are a few settings needed.

  • Settings 

Mandrill setting is only done once per bucket. If it’s already set you don’t need to follow the setting-instruction. Jump directly to “Create new item”.

Go to the mandrill app under tab “settings” and add the mandrill login key. This key can be found in your Mandrill account under “Settings – API Keys”.

     *The 2 other fields (“API version” and “API URL”) should be left as they are.

  • Create new item

When the setting has been done, go to the tab “Rules” and click on “Create new item”.

There are three below options.

  • Starter: It’s the option to define what action (event) to trigger the email.
  • Advanced starter: is the same as “starter” but with an advanced option to allow you writing your own HTML DOM for cases such as sending a list of products dynamically which might be difficult to do directly in Mandrill. This option is often used for a product list in abandon cart emails.
  • Stopper: as Mandrill is sending transactional emails based on triggered events, there are occasions you would want to delay the email after your user´s action has taken place. The delay may be a couple of days after your user has visited and left your website. The delay might be a couple of hours after a user has abandoned the shopping cart and not coming back and completed the purchase. In those occasions, it is important to define an action (event) to stop the email. In many cases, a purchase is such an action you would want to stop a retargeting email to be sent. A stopper is optional to use. Each stopper rule can only be assigned to one starter rule.


Get started with Mandrill - Starter

Define what action (event) to trigger the email.

Select the trigger-event by open the list of events under “Subscribe to event of type”. This option defines what event the email should be triggered on. The event list shows all available events that are stored in profile cloud. If you cannot find your event, check if “save to profile” is enabled.

  1. Mandrill template ID
    For each template that is created in your Mandrill account, a unique ID is created. This ID is called “Template Slug” and is created and visible in the template settings (in your Mandrill account). Add the template slug here to activate the right template.
  2. Send timeout
    Add the eventual delay (in seconds) of sending an email. The time starts ticking from the moment the event has triggered. In below screenshot, the mail will be sent 5 hours after the event has triggered if a “stopper” has not been sent before that.

Set the information to be sent to Mandrill

When the trigger-event has been selected, the data that should be used by Mandrill is to be defined. The only optional data that has to be sent to Mandrill is an email address. On the left-hand side, all elements are data from P.C. This column of elements is different depending on the event that has been selected. The trigger-event might contain data. If it does, the data from the event can be utilized here. Other data available are attributes and session data stored in P.C.


On the right-hand side is the placeholder for data to be used in Mandrill. Connect the data elements from P.C. to the correspondent element in Mandrill.

Create new data elements for mandrill to receive by click in “Add new var

Give the element a descriptive name and click “OK

Connect the data from the event in P.C. to the newly created placeholder.

It is also possible to connect data from attributes and session data.

Note: If attributes are to be used, make sure that the event that triggers the rule is defined in a way that the stored data is always available when the event is triggered.

Save the rule.

To use dynamic values sent by P.C. in Mandrill, use this format in the HTML editor *|variable name|*.  Read more about how to set up the email template in Mandrill here

Below is an example of how to use the P.C. dynamic values in Mandrill