Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

The following operations allow you to work with User Metrics . Click an operation name to see details on how to use it.

...

Anchor
getCountries
getCountries
Get aggregate metrics about the countries referring click traffic to all of the authenticated user's Bitlinks.

The getCountries operation Returns r eturns aggregate metrics about the countries referring click traffic to all of the authenticated user's Bitlinks. .

...

Related Bitly documentation

http://dev.bitly.com/user_metrics.html#v3_user_countries

Anchor
getPopularLinks
getPopularLinks
Get the authenticated user's most-clicked Bitlinks (ordered by number of clicks) in a given time period.

The getPopularLinks operation dets g ets the authenticated user's most-clicked Bitlinks (ordered by number of clicks) in a given time period. .

Code Block
languagexml
titlegetPopularLinks
<bitly.getPopularLinks>        
     <limitForGetPopular>{$ctx:limitForGetPopular}</limitForGetPopular>
</bitly.getPopularLinks>
Properties
  • limitForGetPopular: 1..1000 (default=100).

...

Following is a sample REST/JSON request that can be handled by the getPopularLinks operation.

Code Block
languagexml
titleSample Request for getPopularLinks
{
"limitForGetPopular":"200"
}
Related Bitly documentation

http://dev.bitly.com/user_metrics.html#v3_user_countries

Anchor
getReferrers
getReferrers
Get aggregate metrics about the pages referring click traffic to all of the authenticated user's Bitlinks.

...

Code Block
languagexml
titlegetReferrers
<bitly.getReferrers>
     <limitForGetRefDomain>{$ctx:limitForGetRefDomain}</limitForGetRefDomain>            
</bitly.getReferrers>
Properties
  • limitForGetRefDomain: 1..1000 (default=100).

...

Related Bitly documentation

http://dev.bitly.com/user_metrics.html#v3_user_referring_domains

Anchor
getReferringDomains
getReferringDomains
Get metrics about the domains referring click traffic to all of the authenticated user's bitly links.

The getReferringDomains operation Returns r eturns metrics about the domains referring click traffic to all of the authenticated user's bitly links. .

Code Block
languagexml
titlegetReferringDomains
<bitly.getReferringDomains>        
     <limitForGetRefDomain>{$ctx:limitForGetRefDomain}</limitForGetRefDomain>            
</bitly.getReferringDomains>
Properties
  • limitForGetRefDomain: 1..1000 (default=100)

...

Following is a sample REST/JSON request that can be handled by the getReferringDomains operation.

Code Block
languagexml
titleSample Request for getReferringDomains
{
"limitForGetRefDomain":"200"
}
Related Bitly documentation

http://dev.bitly.com/user_metrics.html#v3_user_referring_domains 

Anchor
getShareCounts
getShareCounts
Get the number of shares by the authenticated user in a given time period.

The getShareCounts operation Returns returns the number of shares by the authenticated user in a given time period . ..

Code Block
languagexml
titlegetShareCounts
<bitly.getShareCounts/>
Related Bitly documentation

http://dev.bitly.com/user_metrics.html#v3_user_share_counts

Anchor
sampleconfiguration
sampleconfiguration
Sample configuration

Following is a sample proxy service that illustrates how to connect to Bitly with the init operation and use the getUserClicks operation. The sample request for this proxy can be found in getLinkInfo getUserClicks sample request.

Code Block
languagexml
titleSample Proxy
<proxy xmlns="http://ws.apache.org/ns/synapse"
       name="bitly"
       transports="https,http"
       statistics="disable"
       trace="disable"
       startOnLoad="true">
   <target>
       <inSequence onError="faultHandlerSeq">
         <property name="accessToken" expression="json-eval($.accessToken)"/>
         <property name="bitlyLink" expression="json-eval($.bitlyLink)" />
         <bitly.init>
            <accessToken>{$ctx:accessToken}</accessToken>
         </bitly.init>
         <bitly.getUserClicks/>        
         <respond/>
      </inSequence>
      <outSequence>
         <send/>
      </outSequence>
   </target>
   <description/>
</proxy>