Help Center

Explore our knowledge base
article

Fixed buttons: migration guide (June 2017)

In order to deploy several new features, we now have to make sure that all the engagement methods you offer to your website visitors are displayed via our targeting engine. The same goes for fixed buttons which, in some cases, were not yet displayed via our targeting engine. 

This guide does not apply to you if you do not use any fixed buttons on your website. 

If you display fixed buttons on your website, please read this guide carefully. Otherwise, you may not be able to offer any more fixed buttons to your website visitors. In order to be complete, this migration requires a minor technical operation on your website. Please make sure all persons concerned in your company read this guide. 

If you have any further questions, feel free to contact your Success Manager. 

 

 

The migration is performed in two steps.

 

Step 1: make sure the configuration of your button is complete and that you are displaying your button via the targeting engine

YOU HAVE UNTIL THE 10TH OF JULY 2017 TO MAKE SURE THIS STEP HAS BEEN ACHIEVED. After this date, we cannot guarantee that your current buttons will continue to function at all.

To know which actions you should perform during this first step, first please assess your current situation between the 4 following scenarios. The first thing you should do is go on one of the website pages where you display a fixed button. 

Right click on your fixed button and then click on "Inspect" (or its equivalent according to your web browser). At this point, please note down the names of the HTML div elements (containers in your website code).

fixedButton.gif

 

 

1st scenario: Targeting rules are associated with your fixed buttons and the HTML div elements used for your fixed buttons have the following IDs

- for a chat button

  • Online status: idzFonline or idzfonline
  • Offline status: idzFoffline or idzfoffline
  • Busy status: idzFbuzy or idzfbusy

- for a call button

  • Online status: idzCallOnline or idzfcallonline
  • Offline status: idzCallOffline or idzfcalloffline

Actions to be carried out:

In this case, the migration will be transparent. You do not have any thing to do during this first step of the migration and you can move on to Step 2.  

 

2nd scenario: you meet all the conditions from the 1st scenario but you do not use the busy status

Actions to be carried out:

Service_button_-_iAdvize.jpg

In this case, you need to log in to the iAdvize administration, go to the Engagement tab (1) and then go to "Notification" (2). 

In the list of buttons, you will find your fixed button called "Fixed chat". Please edit it. 

In the Options parameter, you must indicate the ID of the HTML div element of your busy status (3). If you do not have any, you can reuse (copy paste) the information corresponding to your offline status. When your agents are all busy, we will display the same thing visitors see when no agent is logged in to the iAdvize platform. 

 

3rd scenario: Targeting rules are associated with your fixed buttons but your div IDs differ from the ones mentioned in the first scenario

Actions to be carried out: 

Service_button_-_iAdvize.jpg

In this case, you need to log in to the iAdvize administration, go to the Engagement tab (1) and then go to Notification (2). 

In the list of buttons, you will find your fixed button called "Fixed Chat". Please edit it.

In the Options parameter, you need to indicate the ID of the HTML div element of your 3 statuses (3). Like for the 2nd scenario, if you don't currently have a busy status, you can reuse (copy paste) the information corresponding to your offline status. When your agents are all busy, we will display the same thing visitors see when no agents are logged in to the iAdvize platform. 

 

4th scenario: if targeting rules are not currently associated with your fixed buttons

Actions to be carried out:

Service_button_-_iAdvize-1.jpg

If your fixed buttons do not currently use targeting rules, log in to the iAdvize administration, go to the Engagement tab (1) then go to Notification (2) and click on the + green button to create a new fixed button (3)

Service_button_-_iAdvize-2.jpg

Now, give a name to your fixed button (1) and find it in the list of buttons to then associate it with a targeting rule, choose the channel (chat, call or video) you want to associate this button with (2) and indicate the 3 HTML div IDs corresponding to the 3 statuses of your button (3). 

We recommend you to use, by default: 

  • Online status: idzFonline
  • Offline status: idzFoffline
  • Busy status: idzFbuzy

You can finally save your brand new fixed button (4).

 

Behavioral_targeting_-_iAdvize.jpg

Then go to the Engagement tab (1), Targeting (2) and click on the + green button to create a new targeting rule (3).

Give a name to this rule (4), select the targeting criterion you want to use (5) and, in the list of actions available, choose to display a fixed button (6). Then, you can choose your button in the list and save your rule (7).

For more information about the creation of a targeting rule, you can have a look at this article

 

Step 2: delete your current fixed buttons

This step SHOULDN'T be carried out before the 10th of July, your new fixed buttons are not guaranteed to function properly before this date.   

Step 2 must be carried out no matter what your situation was in Step 1.  

 

Now that your fixed buttons are handled by our targeting engine, you need to delete callbacks (they previously enabled you to display and hide fixed buttons) from your website code. 

In your website code and on all the webpages where you display fixed buttons, please search for the following lines of code and delete them: 

iAdvizeCallbacks = {
  onTargetingRuleTriggered: function(obj){
    if (iAdvize.opOffline == 1) {
      iAdvize.$("#idzFoffline").show();
      iAdvize.$("#idzFbusy").hide();
      iAdvize.$("#idzFonline").hide();
    } else if (iAdvize.opBusy == 1){
      iAdvize.$("#idzFbusy").show();
      iAdvize.$("#idzFoffline").hide();
      iAdvize.$("#idzFonline").hide();
    } else {
      iAdvize.$('#idzFonline').show();
      iAdvize.$("#idzFbusy").hide();
      iAdvize.$('#idzFoffline').hide();
    }
  }
};

Be careful: the names of the HTML div elements (here in brackets in the code above) can vary just like we saw in Step 1. Remember that you need to adapt this example according to the name of the div elements used in your code. 

 

Once these two steps carried out, you shouldn't be using the old system of fixed buttons but rely on our targeting engine instead.  

If you have any further questions, feel free to contact your Success Manager.  

Comments