help - Audience Data Management Platform: iNimbus Client Integration Instructions

iC Best Practice Implementation

Registration or Home Page Banner

Example below – we have used the European guidelines – EU Cookie Law to implement best practices

Sample from offercloud.com.au

Figure 1

A – Banner or overlay on home page or page of registration, key features:

  • disclosing the practice of placing a cookie
  • benefits of allowing the placement
  • set to new or 1st time visitors only – won’t display to return visits

B – Link to relevant place within the privacy policy to learn more and be more specific of what is collected with the placement

 

Changes or Additions to Privacy Policy

Following the update required to most privacy policies post the Australian Privacy Principles changing in March 2014 we have made the following additions/changes to statements in relation to the placement of cookies and the data we are collecting then making available to 1st party sponsors or advertisers

Personal Information

1. When you visit our website you are not required to provide us with personal information and from time to time you may be able to visit our website or deal with us anonymously or by pseudonym. Personal information about visitors to our website is collected only when knowingly and voluntarily submitted by you. However, we may need to collect certain information to provide you with services or to answer or forward any requests or enquiries. If you do not provide us with certain information, we may not be able to provide you with access to our services or respond to your request or enquiries.

Use of Information

2. Personal information that visitors submit and the cookie applied via our website is used as detailed below: (see below – “What is a cookie” Section 17)

(a) Sponsored Question:

When you respond in the affirmative (yes) to a particular sponsored question we will be supplying your contact details and cookie to that sponsor only, this sponsor may use this information to contact you or display relevant offers on their or 1st party websites for the duration of the cookie

(b) Generic Question:

When you respond to a generic question (no sponsor mentioned) we may make available your cookie data to 1st party advertisers who may use this data to display relevant offers on their or 1st party websites. They will not be passed any contact details from your profile

3. We may also use your personal information to create aggregate data about our website visitors, such as statistics relating to age, gender and demographics. This personal information is only used for our statistical purposes.

Collecting information on registered members

4. As part of registering with us, we collect personal information about you in order for you to take full advantage of our services. To do this it may be necessary for you to provide additional personal information when requested by sponsors and advertisers

5. This contact information is made available to our sponsors and advertisers, each time you have agreed to be contacted by responding to the appropriate question

6. Registration is completely optional. Registration may include providing us with your name, email address, address, telephone numbers details, as well as opting in to receive updates and promotional material and other information. You may access this information at any time by logging in and going to your account.

7. We may also use your personal information for the purposes of marketing our services and to send you details about promotional opportunities if you elected to receive such materials when you registered with our website. If you no longer wish to receive promotional material from us, you can opt-out by contacting us at the details on the bottom of this page or, alternatively, select the “unsubscribe” link if the promotional material is sent by email. We will then remove you from our promotions database as soon as reasonably practicable.

8. Declining all cookies – see Section 10

9. Unsubscribe from cookie tracking:

(a) If you were to view your tracking cookies available on your browser you can identify the cookies placed by iCumulus these are identified as “site = inimbus.com.au” and you can opt out from further tracking by iCumulus by clicking this link

10. Declining all cookies

You have the ability to accept or decline cookies. Most Web browsers automatically accept cookies, but you can usually modify your browser setting to decline cookies if you prefer. If you choose to decline cookies, you may not be able to sign in or use other interactive features of OfferCloud and services that depend on cookies, and some advertising preferences that are dependent on cookies may not be able to be respected. If you choose to accept cookies, you also have the ability to later delete cookies that you have accepted. If you chose to delete cookies, any settings and preferences, including advertising preferences, controlled by those cookies will be deleted and may need to be recreated.

(a) Cookies information for sponsors have a lifetime of 30-60 days from time you have last visited our website

(b) IP Addresses: Our web servers gather your IP address to assist with the management of our website and the diagnosis of problems or support issues with our services. Again, information is gathered in aggregate and anonymously only and cannot be traced to an individual user.

For a full copy of the Privacy Policy we give you our permission to use in whole or part and it is available here

11. Providing a mechanism to Unsubscribe

Section 9 of the privacy policy is repeated here:

12. Unsubscribe from cookie tracking:

(a) If you were to view your tracking cookies available on your browser you can identify the cookies placed by iCumulus these are identified as “site = inimbus.com.au” and you can opt out from further tracking by iCumulus by clicking this link

The link will remove the cookie that has been placed on the user’s browser for the specific use within the programmatic ecosystem only

 

Technical Overview:

There are a couple of technical and data issues that need to be resolved to enable the use of the 1st party cookies to be collected by clients to be made available with the Programmatic Buying eco system.

The first is the process of the placement of the cookie into your website and then the consequential configuration to ensure the data is readable by the technical platforms within the programmatic ecosystem.

iC have developed the key process to streamline the requirements for each client whilst ensuring we collect and make available the most valuable data sets for commercial maximisation.

 

Client Integration

In order for us to collect and manage your data, our cookie collection tags (known as integration tags) must be installed.

Firstly, the iC Site Audit happens and then we pass integration tags over to you.

We are aware that each site we encounter has likely been developed in a different way. Our internal auditing process counteracts this. Our tech team will inspect the key elements of each site and page and then construct a simplified tag for a once off implementation by the client.

In order for you to successfully pass data across, a script will have to be embedded into your site. The script will capture all event driven actions by a user on your site. For us to collect all of the data, the tag must be live on each page, but this isn’t as difficult as it sounds.
If the script is placed after the body tags on the opening website, it should load across all pages:

This script must be embedded immediately after the opening body tags.

<script type=”text/javascript”>
iNimbusLayer=[];
(function(d, t) {
try {
var g=d.createElement(t), s=d.getElementsByTagName(t)[0];
g.type=”text/javascript”;
g.defer=true;
g.async=true;
g.src=’https://trk.inimbus.com.au/tagmanager/current/?pubid={PUB ID HERE}&siteid={SITE ID HERE}’;
s.parentNode.insertBefore(g,s);
} catch(e) {
console.log(err);
}
})(document,’script’);
</script>

The above script will load the tracking javascript as well as be the base for every consecutive action being tracked.

Instead of having to manipulate scripts within your page, everything can be managed with minimal editing to your underlying code.

What is loaded?

On page load, the tracking script is initialised.

If you think the tag is not loading on a page, view the HTML code and check to see if the iNimbus tag is present.

 

Making the Data More Relevant

In the case of profiling data being available, we have created a profile tag which will pass initial profile information in order to better segment the data.

If your website has any pages where profile data is being collected, such as:

 

Then follow the instructions below:

In order for you to successfully track demographic information, a script will have to be embedded into your site. This script is known as a profile tag, which will gather any demographic information of the user on your site. Depending on what profile information is available on the website, the profile tag can collect any demographic information such as age and postcode to a consumer’s gender. On a page with profile data being collected:

1) The integration tag must still be placed after the body tags close
2) The profile tag must be placed immediately after the integration tag

This is an example body tag:

<script src=”https://trk.inimbus.com.au/?pubid={PUB ID HERE}&siteid={SITE ID HERE}&dt=1&postcode=2000&age=20&gender=M”></script>

Your body tag will be identical, except it will have your “pubid” and “siteid” placed in it.

Once this has been placed, we will be able to collect information to further enhance our targeting capabilities.

This should only be put on pages where profile data is being collected.

 

Tracking Actions

In order to track actions, we will perform a site audit to identify element ids that will be used to categorise information and configure click listeners.
The benefits of this is that there is no need to make any additional updates to your website. This will be handled by the embedded tag.

Real World Example
www.offercloud.com.au

In order to identify if a user has a pet, an element id is determined from the page and a click listener is configured to listen for a click event.

 

Figure 2

In Figure 1, if the user clicks on the element id ‘HasPet’, categorical information about the user is passed through

<script src=”https://trk.inimbus.com.au/current/?siteid=1&pubid={PUB ID HERE}&lvl0=1416802696&lvl1=1416807845&lvl2=1416808149&dt=1416802696″></script>

The click listener will pass the above information across without the need to embed any additional scripts within the page.

What information is required from you for tracking events?

No information is required. On site audit, we will supply you with what information will be collected and under what categories.

 

Reserved Variables

Please do not use the following variables in your custom fields as they are reserved for internal use.

  • Action_name
  • resolution
  • Type
  • Siteid
  • Pubid

 

Collection of Inferred Segments

Clear click data are Inferred Segments. Inferred segments basically classify what the site is all about and to what group of people it is directed to for example if iCumulus receives a site which is purely based on Travel the Inferred Segment – “Interest in Travel” will be dropped. This tag will be tracking all the web-pages linked to the Travel site.

The process of Inferred Segment Tag setup:

  1. Client places Integration Tags given by iCumulus on their website.
  2. Site audit is done by iCumulus Digital Operator.
  3. Based on Site Audit, Inferred Segment tag is sent to be setup on Client websites.

iCumulus is currently using inferred Segments shown below :

  • Grocery Buyers
  • Interest in Travel
  • Mums with kids
  • Entertainment
  • home buyers – 1st home 7 refinancing
  • C-suite
  • Older travellers
  • Likely Betting – gambling
  • Youth lifestyle (music/ movies)
  • Healthcare and beauty
  • Education – under and post grad
  • Expat’s

iCumulus is currently using the below Experian Mosaic Segments :

A. Exclusive Environs: Families in prestigious and affluent addresses
B. Knowledgeable Success: Well educated family/couple in suburban areas
C. Independence and Careers: Apartment-dwelling young and maturing professionals/students
D. Affluent Acreage: Affluent retirees and older couples in coastal and regional locations
E. Distanced Existence: Families from farming and mining communities in regional areas
F. New Homes and Hopes: Young families, have recently moved to new homes in growing suburbs
G. Middle Australia: Mixed families living on the outskirts of metro areas
H. International Infusion: Multicultural households with extended families in inner city areas
I. Books and Boots: Young professionals living in low cost inner city apartments
J. Provincial Living: singles and broken family households in cheap regions
K. Traditionally Grey: Elderly singles and couples in small units and retirement homes
L. Regional Endeavours: Ageing Australian citizens living in low density areas of provincial towns
M. Remotely Blue: Blue collar workers with low incomes living in cheap regional housing

 

Technical Contact:

iCumulus
Head of Technical Innovations
Terunesh Rao
Terunesh@icumulus.com.au
Ph: 02 8262 8079