EMBEDDING THE TOOLBAR IN YOUR APPLICATION
Version 5.0

Introduction

These following guidelines (the "Guidelines") are intended to guide publishers who wish to offer their community toolbar by integrating it into the installation process of the software they provide to their users (the "Software"). Please note that the publisher may not integrate the community toolbar with the Software unless received written approval to do so by Conduit.

Integration is one of the most common practices used in order to reach a vast number of end-users. Publishers have the ability to offer their users their community toolbar the Software in one package, thus avoiding the need for two separate installations. To add your community toolbar to the Software installation package, please follow the Guidelines below. The objective of these Guidelines is to ensure a safe and secure experience for users and to follow best practices of integration. Any failure to follow these Guidelines will be considered as a violation of the terms and conditions of the Conduit Publisher Agreement. Please note that Conduit will take all necessary measures to enforce its legal policies and Guidelines as listed in the Publisher Agreement, available at: http://www.conduit.com/legal/General.aspx.

Overall

  1. The Publishers may not distribute or promote their community toolbar as part of a Software installation package without obtaining Conduit's prior written approval. Such approval must be obtained for any change or substitution of the Software that was part of an approved Software installation package.
  2. Publishers may not distribute or promote a community toolbar as part of a Software installation package unless they own the Software or are legally licensed to do so.
  3. The name of the community toolbar must represent and reflect the Publishers website's name and materials and not relate to the Software unless Conduit expressly consents otherwise.
  4. Publisher will only distribute the community toolbar as part of a Software installation package in accordance with the terms and conditions of the Publisher Agreement and these Guidelines, as may be amended by Conduit from time to time.

 

Legal Guideline

  1. One installation file: Publishers must use one installation executable file (EXE) to handle the installation of their community toolbar and the Software (the "General Installation Process").
  2. Proper disclosure and choice: Any Publisher must inform its users that they are installing the community toolbar in addition to the Software, and such Publisher must allow its users to choose whether or not to install the community toolbar as part of the General Installation Process. A "silent" or "background" installation or any other installation without the user's informed consent is not allowed under any circumstances.
  3. Activity and content: Publishers may not (1) engage in activity that violates any applicable law or regulation, or (2) use content which is related to pornography; explicit nudity; harassment of individuals or groups; or illegal, inappropriate, offensive or obscene content in connection with or relating to your community toolbar, the Software or the Software installation package.
  4. Uninstaller: As part of the integration or the package Publisher must provide an uninstaller that enables the users to uninstall the community toolbar and the Software (together or separately) without undue effort or skill, using basic and transparent uninstall methods.
  5. EULA: As part of the General Installation Process, Publisher must enable its users to review and accept the community toolbar's End User License Agreement (EULA) prior to installing the toolbar, via a link to the EULA or a scrollable text box that contains it. The most recent version of the EULA can be found here: http://conduit.ourtoolbar.com/eula. You may not modify the EULA or circumvent the acceptance of the EULA by the users as part of the General Installation Process.
  6. Privacy Policy: As part of the General Installation Process, Publisher must enable its users to review and read the community toolbar's Privacy Policy, via a link to it. The most recent version of the Privacy Policy can be found here: http://conduit.ourtoolbar.com/privacy/. Publishers may not modify the Privacy Policy or circumvent the review of the Privacy Policy by the users as part of the General Installation Process.
  7. Endorsement: If a Publisher opts to offer its community toolbar as part of the Software installation package, such Publisher must also offer its users the option of downloading and installing the community toolbar as a stand-alone application using a permanent banner ad or textual link placed on its website(s). Offering the toolbar as a stand-alone application is required in order to demonstrate that it is not a third-party component.
  8. Updated toolbar version: As part of the installation process, Publisher must offer the latest version of its community toolbar as made available via the Conduit platform. On a monthly basis Publisher must ensure that it is offering to users the latest version of its community toolbar.
  9. Toolbar web search: Publishers must allow users to have the option NOT (1) to set the toolbar search as the default search in their browser, and NOT (2) to set the toolbar search as their browser's default home page.
  10. Compliance: Before starting to distribute Publishers community toolbar as a part of its Software installation package, Publisher will contact Conduit's Compliance department (email: legal@conduit.com) to receive written approval that its community toolbar is properly integrated and eligible for distribution.

 

The integrated software

The integrated Software shall not be related in any way or matter to the following provisions:

  1. The Software shall not enable under any circumstances gambling or participation in any gambling related game and/or contests which are based on payment or consideration.
  2. Peer to Peer Software and file sharing: Publishers shall not integrate its community toolbar with any P2P/ file sharing Software which encourages the downloading of illegal content.
  3. The Software shall not offer any adult content.
  4. The Software shall be free from any intrusions in the form of a virus/ malware/ spyware as shall be detected by any leading security services.
  5.   The Software shall not harm the user's machine in any way.
  6. The publisher shall not integrate the toolbar with more than one application.

 

For removal of any doubt –

The Publisher shall be aware that Conduit may not allow the use of any Software which is determined, in Conduits sole discretion, to have a "poor reputation", (i.e. the Software may harm Conduits business).

Embedding IE Toolbar Setup

This section contains instructions for embedding your toolbar setup into your application install package and installing the toolbar in an Internet Explorer browser.

 

1.      Download the latest toolbar setup from your toolbar download web page, for example, http://<ToolbarName>.ourtoolbar.com/ie

2.      After downloading the executable and saving it locally please package it within your installer.

3.      In your application package, please launch the toolbar setup executable with the following shell command:  <ToolbarName>.exe  /s

 

4.      The setup can take extra parameters to control certain client-side behavior:

–Silent=

TRUE to open the toolbar's welcome page after installation, FALSE otherwise.

 

-StartPage=
TRUE to change the client's current homepage, FALSE otherwise.

 

-DefaultSearch=
TRUE to add search engine to search box and set it as default, FALSE otherwise.

 

-OpenUninstallPage=
TRUE if to open an uninstall toolbar page upon toolbar uninstallation, FALSE otherwise

-showPersonalCompDialog=
TRUE to open a welcome dialog after installation, FALSE otherwise.

-EnableAlerts=

TRUE to Enable the Notifications feature, FALSE otherwise.

 

5.      When specifying the included toolbar setup in your install package, ensure that you include the toolbar setup called <ToolbarName>.exe.

Add an Install Toolbar dialog box to your application setup wizard, with all of the required details according to Conduit policy. Such information includes a preview of the toolbar, the Privacy Policy and End User License Agreement links, etc.

The Privacy Policy link is located at: http://[ToolbarName].ourtoolbar.com/privacy/
For example: http://mybrand.ourtoolbar.com/privacy/.

The End User License Agreement link is located at: http://[ToolbarName].ourtoolbar.com/eula
For example: http://mybrand.ourtoolbar.com/eula/.

The Content Policy link is located at: http://www.conduit.com/Home/Privacy/content-policy.aspx.

 

Embedding Firefox Toolbar Setup

This section contains instructions for embedding your toolbar setup into your application install package and installing the toolbar in a FireFox browser.

1.      Download the latest toolbar setup from your toolbar download web page, for example, http://<ToolbarName>.ourtoolbar.com/xpi

2.      Unpack this XPI  (as you would unpack a zip file )

3.      We should distinguish between two types of extensions:
- Single XPI extension (see flow 1)
- Dual XPI extension (See flow 2)
To determine the type of extension at hand, check the install.rdf included in the xpi for the line: <em:type NC:parseType="Integer">32</em:type>

 

Flow 1 – if  <em:type NC:parseType="Integer">32</em:type> does not exist in install.rdf, then this is a Single XPI extension.

 

We have to identify the toolbar's Extension ID.

To do so, you can look through install.rdf for a line starting with <em:id>

 

 

The part which starts with a Left Bracket ( { ) and ends with a Right Bracket ( } ) is the extension ID. (Including the brackets themselves).

Place the unpacked files in a folder named after the extension ID you've just located, and package this folder into your installer.

 

In your application package:

1.     

 

 

2.      Once the profile we wish to install onto has been found, just copy the extension

ID folder from within your packaged application into the following folder:
%APPDATA%\Mozilla\Firefox\Profiles\<profileName>\extensions\

 

3.      To control certain client-side behaviors (similar to using parameters for the IE installation), place a file called setup.ini within the extension ID folder you've just unpacked onto the user's computer.

 




You can fill this setup.ini file with one or more of the following parameters:
_START_PAGE_=TRUE/FALSE
_SET_DEFAULT_SEARCH_=TRUE/FALSE
_OPEN_UNINSTALL_PAGE_=TRUE/FALSE
_OPEN_WELCOME_DIALOG_=TRUE/FALSE
_OPEN_THANKYOU_PAGE_=TRUE/FALSE


Example of such a setup.ini file is given below:

 

 

Flow 2 – if <em:type NC:parseType="Integer">32</em:type> exists in install.rdf, then this is a Dual XPI extension.

 

This means there are two XPI's contained within the XPI we've just unpacked, which are the actual extensions we wish to install to the user's computer.
Unpack the two XPI's found within the XPI we've just unpacked.
Go into each of the two folders and note the following:

 

We have to identify the toolbar's Extension ID.

To do so, you can look through install.rdf for a line

starting with <em:id>

 

 

The part which starts with a Left Bracket ( { ) and ends with a Right Bracket ( } ) is the extension ID. (Including the brackets themselves).

 

Place the unpacked files in a folder named after the extension ID you've just located, and package this folder into your installer.

This is to be done for each of the two internal XPIs as described above.

 

In your application package:

1.      We would like to install the extension into the user's active Firefox profile, but you can choose whichever profile you'd like.
To find the list of all profiles the current user has read the contents of the following file:
%APPDATA%\Mozilla\Firefox\profiles.ini

2.      Once the profile we wish to install onto has been found, just copy the extension ID folder from within your packaged application into the following folder:
%APPDATA%\Mozilla\Firefox\Profiles\<profileName>\extensions\

3.      THE FOLLOWING SHOULD NOT BE DONE FOR THE EXTENSION WITH ID " engine@conduit.com"



To control certain client-side behaviors (similar to using parameters for the IE installation), place a file called setup.ini within the extension ID folder you've just unpacked onto the user's computer.


You can fill this setup.ini file with one or more of the following parameters:
_START_PAGE_=TRUE/FALSE
_SET_DEFAULT_SEARCH_=TRUE/FALSE
_OPEN_UNINSTALL_PAGE_=TRUE/FALSE
_OPEN_WELCOME_DIALOG_=TRUE/FALSE
_OPEN_THANKYOU_PAGE_=TRUE/FALSE

 

Example of such a setup.ini file is given below:

UI references

The following functionality and disclaimers must be part of the integration dialog screen:

    1. Checkboxes:
      1. Checkbox for approving the toolbar installation
      2. Checkbox for changing homepage settings
      3. Checking for changing the search default settings.

·The publisher may choose weather as a default the checkboxes will be checked or not unless specified otherwise in the Publisher Agreement.

    1. The user must agree to the EULA and Privacy Policy in order to complete the installation.
    2. Updated Toolbar image must be presented.
      1. The toolbar image shall not include any reference to the search engine which is provided with the toolbar.
    3. The name + the logo of the toolbar.

Enabling the Toolbar to Execute the Application

To enable the Conduit toolbar to execute your application:

1.      Add to the registry a key with your application alias, for example myApp.exe.

* Add the following key to the registry, to add an application alias for a specific user: HKEY_CURRENT_USER\Software\Conduit\AppPaths\
myApp.exe

* Add the following key in the Registry Editor, to add an application alias for all users: HKEY_LOCAL_MACHINE\Software\Conduit\AppPaths\
myApp.exe

NoteOn Windows Vista it is strongly recommended that you add the
                   key to HKEY_LOCAL_MACHINE
 

     

2.      Add a string value to the new key as follows:

*      Name = AppPath.

*      Value = The full path to your application on the end users machine.
For example, C:\Program Files\myApp\myApp.exe

Figure 3 Registry Editor Displaying the Application Path Key

Launching Your Application from the Toolbar

To add an application button or menu application item to your Conduit toolbar:

1.      Navigate to your Conduit account by entering the following URL in your browser: http://accounts.conduit.com/Login/.

2.      In the Community Toolbar Name and Password fields enter your login information.

The Toolbar screen appears.

Figure 4 Adding Components to your Toolbar

3.      For instructions on:

*Adding an application button to your toolbar, see Adding an Application Button on page 10.

*Adding a menu application item, see Adding a Menu Application Item on page 11.

Adding an Application Button

An application button enables you to launch your application from your toolbar.

To add an application button to your Conduit toolbar:

1.      From the Toolbar screen, click Application Button or  to add an application button to your toolbar.

The Add Application Button screen appears.

Figure 5 Add Application Button

2.      Follow the screen's instructions for selecting an icon and a caption for the application button.

3.      In the Registered Application Alias field, enter the name under which you have registered your application. This name should be the exact alias that your application setup writes to the registry.

4.      You can optionally specify parameters to be passed from the toolbar when it is launched from the application, the URL from which your application can be downloaded, and the menu application item's tooltip text.

5.      Click Save.

The application button is added to your toolbar.

Adding a Menu Application Item

You can add a menu to your toolbar containing an application button that enables you to launch your application from your toolbar.

To add a menu application item to your Conduit toolbar:

1.      In the Adding Components to your Toolbar screen (see Figure 4), click Button with Menu or Dropdown to add a drop down menu to your toolbar.

The Add Button with Menu screen appears.

Figure 6 Add Button with Menu

2.      Follow the screen's instructions for selecting or uploading an icon for the application button.

3.      Click Application button to edit the drop down menu.

The Edit Menu Item dialog box appears.

Figure 7 Edit Menu Item Dialog Box

4.      Enter the Edit Menu Item information as follows:

*      In the Caption field, enter the text that will appear on the menu application item.

*      In the Registered Name field, enter the name under which you have registered your application. This name should be the exact alias that your application setup writes to the registry.

*      You can optionally specify parameters to be passed from the toolbar when it is launched from the application, the URL from which your application can be downloaded, the menu application item's tooltip text, and the location of the icon that will appear on the menu application item.

5.      Click Save in the Edit Menu Item dialog box.

6.      Click Save in the Add Button with Menu screen (see Figure 6 ).The Menu Application Button is added to your toolbar.

[Last updated:March, 2011]

We would like to install the extension into the user's active Firefox profile, but you can choose whichever profile you'd like.
To find the list of all profiles the current user has read the contents of the following file:
%APPDATA%\Mozilla\Firefox\profiles.ini

1800s

SIGNAL LAMP INVENTED

1838

ELECTRICAL TELEGRAPH INVENTED

1911

IBM IS FOUNDED

1927

WORLD'S FIRST TV

2400 BC

EARLIEST DOCUMENTED MAIL SERVICE

1965

FIRST WIDE AREA NETWORK

1983

FIRST COMMERCIAL MOBILE PHONE SOLD

1990s

2G DIGITAL NETWORKS EMERGE

1998

FIRST DOWNLOADABLE MOBILE RINGTONE

1998

FIRST ONLINE BLOGGING COMMUNITY

2011

CONDUIT ACQUIRES WIBIYA

2.1

BILLION INTERNET USERS TODAY

2008

MOBILE WEB GOES MAINSTREAM

1895

FIRST RADIO SIGNAL

1.08

BILLION SMARTPHONES
IN USE

109

NEW CONDUIT EMPLOYEES IN 2011

1973

FIRST ANALOG MOBILE PHONE

54,000

COFFEE CAPSULES CONSUMED AT CONDUIT IN 2011

400 BC

FIRST PIGEON POST

29

BIRTHS AT CONDUIT IN 2011

1990

FIRST INTERNET BROWSER

40,041

SQ FT OF CONDUIT OFFICE SPACE
IN 2011

1997

BIRTH OF SOCIAL NETWORKING

14

CONDUIT WEDDINGS IN 2011

250

MILLION CONDUIT USERS

260,000

CONDUIT PUBLISHERS

1876

FIRST TELEPHONE

2009

1st CONDUIT PATENT REGISTERED