Tip: Getting Started with the iPerceptions Universal Code

by Phil A.

Once you have obtained the iPerceptions Universal Code for your account, it is recommended that it be tested in a staging environment, or on test pages not linked to your website’s navigation, before publishing it to your website.

This article provides a list of some things to keep in mind when implementing and testing the Universal Code for your account.

 

Implementing the Universal Code

1. The iPerceptions Universal Code can be implemented using a Content Management System (CMS) or Tag Management Solution (TMS), or it can also be programmed directly in your website’s code

2. The Universal Code should be implemented on all pages of your website (e.g. in the global footer).

  • If you would like to limit where your visitors can qualify for a survey invitation or comment card feedback button, you can program triggers for these projects to block these items from being shown on specific sections of your website. 

3. The Universal Code should be placed above the closing </body> tag, but not within iFrame tags.

  • Placing the Universal Code inside an iFrame tag will prevent survey invitations or comment card feedback buttons from being shown. 

4. Avoid programming custom triggers in your code (or your CMS / TMS) to call the iPerceptions Universal Code.

  • Triggers can be programmed in the iPerceptions Active Research Platform to show survey invitations or comment card feedback buttons only to those who meet certain behavioral conditions.
  • Programming triggers in your CMS / TMS, or in your website’s code, may conflict with the triggers you programmed for your project in the Active Research Platform, and prevent the iPerceptions Universal Code from functioning properly for your projects.

5. The domains on which the iPerceptions Universal Code will be implemented must be specified on the “Universal Code” page in the Active Research Platform. 

 Locking_Universal_Code_to_Specific_Domains_2.png

  • These fields provide an additional security measure which locks the Universal Code for your account to the domains you specify.  As such, survey invitations and comment card feedback buttons can only be served on the domains specified in these fields. 
  • Note that “http / https” does not need to be entered in these fields, though "www" should be entered if needed.  
  • Starting with the iPerceptions Premium plan, you can also now associate all subdomains for a given domain by entering * before the domain.  For example, to associate all subdomains ending in "example.com", enter *.example.com in the field provided.
  • These fields can be modified at any time.  As such, if launching a new project, ensure that the domain on which it will be launched is already specified in this list.
  • If the iPerceptions Universal Code has been implemented in your staging environment, or has been placed on test pages not linked to your website’s navigation, ensure that the domain for these items is included in this list. 

 

Project Settings and Invitation Triggers

The following items can all be performed in the “Research Design” section of the Active Research Platform, on the “Invitation Trigger” page.  After performing any changes on this page, click “Save” for them to be applied in real-time to the iPerceptions Universal Code:

Getting_Started_with_Universal_Code_Invitation_Trigger_Page.png

 

  

6. Invitation rates must be set in the triggers for your surveys.

 Getting_Started_with_Universal_Code_Invitation_Rates.png

  • Invitation rates can be set to specify the proportion of visitors who will qualify for a survey invitation if they meet the conditions for this trigger, depending on their device type.
  • For new triggers, a default invitation rate of 50% is set for Desktop, and 0% invitation rates are set for Mobile and Tablet. 
  • When testing the Universal Code, it is recommended that invitation rates be set to 100%, and then set to your desired level before publishing your research to your website.

 

7. Triggers must be activated in order for them to be used to qualify visitors for survey invitations or comment card feedback buttons. 

Getting_Started_with_Universal_Code_Trigger_Activation.png

  • A default trigger is created for each of the language versions of your projects, based on “Browser Language”.  You can activate or deactivate collection for a certain language by using the toggle provided for its triggers. 

 

8. Cookies are used to prevent your visitors from receiving multiple survey invitations within a certain time period.

Getting_Started_with_Universal_Code_Cookies.png 

  • One cookie (“days for this survey”) prevents visitors from receiving another invitation for the same survey (default 30 days).
  • If more than one survey has been activated on your website, one cookie (“days for other surveys”) prevents visitors from receiving the invitation for a survey if they recently received the invitation for another survey (default 1 day). 
  • When testing the iPerceptions Universal Code, make sure to clear your cookies, or open a new Private Browsing or Incognito Mode session (depending on your browser), before every attempt to receive the invitation for one of your surveys.

 

Project Publishing and Activation

 

9. In order for questions to be shown on the live version of a project, they must be activated in the “Research Design” section of the Active Research Platform, on the “Research Setup” page:

 

Getting_Started_with_Universal_Code_Activate_Questions.png

 

 

10. Projects must be published at least once in the Active Research Platform.

  • A project can be published by using the Publish button provided on the "Project Info", "Research Setup", "Translations" and "Look and Feel" pages in the “Research Design” section of the Active Research Platform.

 

  • A project which has yet to be published at least once will show “Last published on: --“ on the Publish bar, as shown in the image above. 
  • The first time that a project is published, the project is automatically activated in the “My Projects” section of the Active Research Platform (see #11).

 

11. Projects must be activated (set to “Online”) in the “Overview” section of the Active Research Platform.

  • When a project is activated, each of the triggers that have been activated for it will be used to qualify website visitors for survey invitations or comment card feedback buttons (see #6 to #8), and all questions that have been activated and published will be shown to respondents when they complete the survey or comment card (see #9 and #10).

 

___________________

UPDATED: December 3 2015

This article was updated to reflect our new platform navigation being released on December 4 2015.  Check out this article to learn more about this update.  

________________

UPDATED: July 16 2015

Additional content added for Step 5, with regards to associating domains to your Universal Code. 

  • An update has been released which asks that the domains entered for your Universal Code must match exactly, and should included "www" if needed.  
  • Starting with the iPerceptions Premium plan, you can now associate all subdomains for a given domain by entering * before the domain.  For example, to associate all subdomains ending in "example.com", enter *.example.com in the field provided. 

_______________________

UPDATED: JUNE 16 2015

The following changes have been made to the content provided in this article: 

  • Reordered the content to emphasize that triggers should be programmed for your project before you choose to activate your project.
  • Emphasize that publishing a project for the first time in the Active Research Platform will automatically activate it.   
  • Mention that collection for a project's language packs when using the Universal Code is controlled by activating / deactivating the trigger(s) for these languages on the "Invitation Trigger" page.  If the project still uses the legacy iPerceptions code, collection for a project's language packs can be controlled by using the "Active" box provided these languages on the "My Projects" page.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk