Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Clicky Destination


Destination Info
  • Accepts Page, Alias, Group, Identify and Track calls.
  • Refer to it as Clicky in the Integrations object
Connection Modes
Device-modeCloud-mode
Web Web
Mobile Mobile
Server Server

Clicky(link takes you to an external page) is a web analytics tool that enables you to monitor, analyze, and react to your blog or web site's traffic in real time. Clicky supports user segmentation, so marketers can define and track customers based on unique constraints like user action, traffic source, location, or device. Additionally, it allows on-site analytics in order to track total visitors on site, pages currently viewed, and user actions like pageviews, downloads, sign ups, and session duration.

Our Clicky destination code is open-source on GitHub. You can check out the code in the @segment-integrations/analytics.js-integration-clicky(link takes you to an external page) repository.


Getting started

getting-started page anchor
  1. From the Segment web app, click Catalog.
  2. Search for "Clicky" in the Catalog, select it, and choose which of your sources to connect the destination to.
  3. In the destination settings, enter your Site ID in the settings. You can find your Site ID under the Preferences of your account.
  4. Segment automatically initializes Clicky's script with your Site ID upon loading analytics.js.

If you're not familiar with the Segment Specs, take a look to understand what the Page method does. An example call would look like this:

1
analytics.page("Home",{
2
path: "http://www.example.com/home"
3
});

When you call page, we call Clicky's log function with the current URL path and the name of the page. Clicky does not support event properties for page calls.


If you're not familiar with the Segment Specs, take a look to understand what the Identify method does. An example call would look like this:

1
analytics.identify('ze8rt1u89', {
2
name: 'Zaphod Kim',
3
gender: 'Male',
4
email: 'jane.kim@example.com',
5
phone: '1-401-826-4421',
6
address: {
7
city: 'San Francisco',
8
state: 'Ca',
9
postalCode: '94107'
10
}
11
});

When you make an Identify call with Segment, we will create a Clicky custom session and we will map the traits of your event. We set the username of the user that is being identified based on the traits.username value that's included in the event. If the username value is not provided, then we default to the email trait and if, that is not included either, we default to the name included in the traits of the event.


If you're not familiar with the Segment Specs, take a look to understand what the Track method does. An example call would look like:

1
analytics.track("My Custom Event", {
2
checkinDate: new Date(),
3
myCoolProperty: "foobar",
4
});

When you use our track method, a goal is created in Clicky. Only the event name and the revenue of the event (if it exists) will be included in the call. Clicky doesn't support any other event properties.


My visits aren't showing up in Clicky

my-visits-arent-showing-up-in-clicky page anchor

When you login to Clicky, it automatically sets a cookie on your browser to ignore your visits to your website. If you need to test something, such as a goal or campaign, you'll want to use a different web browser or switch your browser to private/incognito mode.


Segment lets you change these destination settings from the Segment app without having to touch any code.

Property nameTypeRequiredDescription
Site IDstring
required

You can find your Site ID under the Preferences tab on your Clicky account(link takes you to an external page).