Before You Begin

Ensure that you have a Bitly account.

To Add a Bitly URL Shortener 

1. Click the New Tab icon . Under the Governance Console, click All Settings within Platform Setup.
2. In the Platform Settings window, select URL Shorteners from the list of options to open the URL Shortener Settings. You can also search for it in the search bar above.
3. In the top-right corner of the URL Shortener window, click Add URL Shortener.
4. In the Create URL Shortener window, select the URL Provider as Bit.ly from the drop-down menu under Primary Details. 
5. Under Provider Settings, click Authorize.
6. In the Bit.ly Authorization window, sign in with your Bit.ly account.
7. Click Allow to grant Sprinklr the permission to access your Bit.ly account.
8. Under the Provider Settings, select the available group for bit.ly from the drop-down menu.
9. Check the URL shortener box and enter a unique name for easy identification of the bit.ly URL shortener.
10. Click Save in the bottom right corner to save your URL Shortener.

URL Shortener Migration

The Bitly API was updated to V4. Bitly no longer supports older versions of the API, and outdated connections will be phased out by September 14, 2020. For more information, see Migrating from V3 to V4 of the Bitly API.

To Re-Add the URL Shortener

1. Click the New Tab icon . Under the Governance Console, click All Settings within Platform Setup.
2. In the Platform Settings window, select URL Shorteners from the list of options to open the URL Shortener Settings. You can also search for it in the search bar above.
3. In the URL Shortener window, click Re-Add. You will be prompted with the bit.ly authentication process similar to the steps in To Add a Bit.ly URL Shortener.

   Note Since bitly.com and j.mp are being removed. Thus, when an admin re-authorize these URL shorteners, the only option available is the bit.ly URL shortener.

   

FAQs

► Is there anything Care Agents need to do here or will they see anything differently, or is this a backend configuration for the customer and/or backend API upgrade from Sprinklr? 

Agents will not see anything differently. Only the Admins have to re-add the existing shorteners once the API is upgraded.

► Will older shortened links need to be updated? While we don't really use URL shorteners in Forums content, will older URLs on Accepted/Published solutions need to be changed?  

Older links need not be updated; they will work as it is. However, once the API is upgraded, to create the newer ones, you need to re-add the shortener.