Mattering Automations Clicky integration
Connect Clicky web analytics to Mattering Automations: visitor and action totals, engagement, top pages, referrers, searches, audience breakdowns, goals, segmentation, the session log and uptime as read-only workflow steps, authorized with a Site ID and a read sitekey.
The Mattering Automations Clicky integration puts Clicky's reporting on your automation canvas: visitor and action totals, bounce rate and time on site, top pages, entry and exit pages, referrers and traffic sources, searches and keywords, locations and organizations, browsers, devices and screen resolutions, downloads, events and video, goals and campaigns, visitor segmentation, the session-level visitor and action log, uptime checks and alerts. Eighteen nodes, every one of them a read. Nothing in this integration writes to Clicky, and there is no destructive node in it.
The credential is two values you copy out of Clicky: a numeric Site ID and a sitekey. Clicky sends both as URL query parameters rather than as headers, which shapes how this integration handles them and is explained below. The sitekey to copy is the ordinary read key; Clicky's admin sitekey lives on the same site preferences page, is the key its manual tracking documentation says allows you to write data to Clicky, and pasting it is the single most common reason Test Connection fails on a first attempt.
Two things are worth reading before you build a report on this, because both are quiet rather than loud. First, API access is not plan-gated at Clicky, which lists it among the basics every plan gets, but what a plan returns is: a free account is limited to the last 30 days of history and 100 results per request, and Clicky enforces that by truncating rather than by erroring. Second, a multi-day request returns one undated aggregate unless you turn Daily on, so anything you intend to chart or store as a time series needs that switch. Both are covered in full below, and this guide ends with the complete node reference.
Before you start
- A Clicky account with a site already tracking. Clicky's stats API reports on data its tracking code has collected, so a site that has not been installed yet returns empty reports rather than an error.
- The Site ID and sitekey for the site you want to report on, from that site's preferences page in Clicky. Take the ordinary sitekey, not the admin sitekey. The two halves must come from the same site: a Clicky sitekey belongs to exactly one site and is meaningless against another site's id.
- A decision about which site this credential is for. One credential covers one Clicky site, so reporting on a second site means a second stored credential rather than a site field on a node.
- An understanding of what your Clicky plan returns. API access itself is not plan-gated, and Clicky lists it among the basics that every plan gets. What is gated is the data: Clicky's API documentation states that free accounts are limited to the last 30 days of history and 100 results per request, and that the maximum date range is 366 days for Pro users and 31 days for everyone else. Its pricing page adds that free plans keep 30 days of history while paid plans keep it indefinitely, except for individual visitors and actions, which are guaranteed for six months. All of it is enforced by truncation, so a workflow that exceeds a limit looks healthy and quietly returns less than it asked for.
- Goals configured in Clicky, if you intend to use Clicky: Goals and Campaigns for conversions. Goals and revenue are premium Clicky features that the free plan does not include, so there is nothing for the goals report to return without them.
- Uptime monitoring enabled on the site, if you intend to use Clicky: Uptime Checks. Clicky lists uptime monitoring as available on Pro Plus accounts and higher, so a free plan and a base Pro plan both come back with nothing to report.
- An awareness that Clicky: Visitor and Action Log returns personal data, including IP addresses, hostnames and session identifiers, so its output should be routed deliberately rather than forwarded into a public channel or a chat window.
- A Mattering workspace with access to the Automations app.
Copy your Site ID and sitekey from Clicky
Clicky authenticates every API request with a pair of values rather than with a token: the numeric id of the site you are asking about, and a key belonging to that site. There is no OAuth flow, no header form and no signature, so the whole setup is two fields and a paste. The decision that carries weight is which key you copy, because Clicky shows two of them side by side and only one of them belongs here.
Connect Clicky to Mattering
Verify it works
Open any automation canvas and check the palette: a Clicky section should list all 18 nodes. Drop Clicky: Visitor Totals on the canvas and run a test step without changing anything. It is the integration's natural probe, because it is the same call Test Connection makes and it answers the only question worth asking first: is real data coming back for the site you think you connected. Every node runs against the single site the credential belongs to, so if the numbers look like somebody else's site, the credential is the place to look rather than the node.
Now turn Daily on and run it again over a few days. The point of this step is the shape of the result rather than the numbers: with Daily off, a multi-day request returns one undated aggregate for the whole range, and with it on you get a row per day carrying a real date. That is the switch that decides whether a result can be charted or stored as a time series, and it is the most common reason a working node produces an unusable table. While you are here, look at both halves of the output: data.reports is Clicky's own response verbatim, and data.rows is the flat view this integration derives, where each row carries its own type and date as real columns. Bind charts, databases and Analytics datasets to data.rows.
Finally, run Clicky: Top Pages as it comes. This confirms the ranked reports work and shows you what a top N looks like: rows ordered by value descending and cut off at the row limit, with the page title, the count, the share of the total and the URL. Everything in this verify path is read-only, as is every node in this integration, so it is safe to re-run whenever you want to check the connection. If Clicky: Top Pages returns rows and Clicky: Goals and Campaigns returns nothing, that is a plan boundary rather than a fault, and the troubleshooting section below explains it.
Node reference
18 nodes, generated from the connector itself so this reference always matches what ships.
Read and query nodes 18
Clicky: Action Totals
clicky_get_actions
How much happened: total actions, page views, file downloads, outbound link clicks and javascript click events. These are the numbers you CAN add up. Every type this node offers is an event count rather than a deduplicated or averaged figure, so a fortnight really is the sum of its fourteen days, and a dashboard may roll daily partitions into weeks and months freely. The averages that look like they belong here (actions-average, time-average, bounce-rate) are deliberately on the Clicky: Engagement and Time Totals node instead, because they are rates and must never be summed. Output shape: data.reports is Clicky's own response verbatim, one entry per requested type, each holding dates and then items. data.rows is a flat view DERIVED by this connector, where every item carries its own type and date as real columns, because Clicky puts both on the row's parents rather than in the row. Bind charts and datasets to data.rows. Plan caps, from Clicky's own docs: a FREE account can only reach the last 30 days of history and returns at most 100 results per request, so a longer window or a bigger limit quietly returns less than you asked for. The date range itself is capped at 366 days on Pro and 31 days on every other plan.
Clicky: Engagement and Time Totals
clicky_get_engagement
How engaged people were: bounce rate, average actions per visitor, average and total time on site (in seconds and in Clicky's pretty form), plus the two engagement breakdowns that bucket visitors by how many actions they performed and how long they stayed. Read the numbers, do not add them. Every figure here except time-total is an AVERAGE, a PERCENTAGE or a formatted string, and none of those may be summed across days or averaged unweighted; Clicky returns no visitor count beside them to weight by, so the only correct move is to re-ask Clicky for the period you actually want. time-total is additive on its own but shares this node with the rates, so this connector declares nothing aggregatable here at all. Output shape: data.reports is Clicky's own response verbatim, one entry per requested type, each holding dates and then items. data.rows is a flat view DERIVED by this connector, where every item carries its own type and date as real columns, because Clicky puts both on the row's parents rather than in the row. Bind charts and datasets to data.rows. Plan caps, from Clicky's own docs: a FREE account can only reach the last 30 days of history and returns at most 100 results per request, so a longer window or a bigger limit quietly returns less than you asked for. The date range itself is capped at 366 days on Pro and 31 days on every other plan.
Clicky: Entry and Exit Pages
clicky_get_entry_exit_pages
Where visits start and where they end: landing pages (pages-entrance) and the last page someone saw before leaving (pages-exit). Requesting both in one call is the usual pattern, since the interesting answer is usually the difference between them. Rows come back ordered by value descending and cut off at limit, so a result is a TOP N rather than the whole picture: raise limit or page through before treating it as complete, and never add two periods' top lists together, because the top 20 of January plus the top 20 of February is not the top 20 of both. Output shape: data.reports is Clicky's own response verbatim, one entry per requested type, each holding dates and then items. data.rows is a flat view DERIVED by this connector, where every item carries its own type and date as real columns, because Clicky puts both on the row's parents rather than in the row. Bind charts and datasets to data.rows. Plan caps, from Clicky's own docs: a FREE account can only reach the last 30 days of history and returns at most 100 results per request, so a longer window or a bigger limit quietly returns less than you asked for. The date range itself is capped at 366 days on Pro and 31 days on every other plan.
Clicky: Get Alert
clicky_get_alert
Fetch the detail behind one Clicky alert. Clicky delivers alerts by email; each email carries an alert ID, and this node turns that ID back into structured data so an automation can act on it rather than parse an email. This is the only mode of the stats endpoint that takes no report type and no date: it wants the alert ID alone. Output shape: data.reports is Clicky's own response verbatim, one entry per requested type, each holding dates and then items. data.rows is a flat view DERIVED by this connector, where every item carries its own type and date as real columns, because Clicky puts both on the row's parents rather than in the row. Bind charts and datasets to data.rows.
Clicky: Goals and Campaigns
clicky_get_goals
Everything you configured Clicky to watch: goal completions (which also carry incompleted, conversion, revenue and cost alongside the usual value), campaign performance, split-test results, and the custom data your own tracking code logged against sessions. Goals are a Pro feature on Clicky, so a free or basic account gets an empty goals report rather than an error. Revenue figures are additive across days; conversion rate is not, and this connector declares neither, so treat any rate you see as read-only. Rows come back ordered by value descending and cut off at limit, so a result is a TOP N rather than the whole picture: raise limit or page through before treating it as complete, and never add two periods' top lists together, because the top 20 of January plus the top 20 of February is not the top 20 of both. Output shape: data.reports is Clicky's own response verbatim, one entry per requested type, each holding dates and then items. data.rows is a flat view DERIVED by this connector, where every item carries its own type and date as real columns, because Clicky puts both on the row's parents rather than in the row. Bind charts and datasets to data.rows. Plan caps, from Clicky's own docs: a FREE account can only reach the last 30 days of history and returns at most 100 results per request, so a longer window or a bigger limit quietly returns less than you asked for. The date range itself is capped at 366 days on Pro and 31 days on every other plan.
Clicky: Operating Systems and Devices
clicky_get_platforms
What your visitors ran: operating systems, and the hardware report which names the mobile and tablet devices Clicky could identify. Desktop traffic largely does not appear in the hardware report, so read the two together rather than treating hardware as a device split of all traffic. Rows come back ordered by value descending and cut off at limit, so a result is a TOP N rather than the whole picture: raise limit or page through before treating it as complete, and never add two periods' top lists together, because the top 20 of January plus the top 20 of February is not the top 20 of both. Output shape: data.reports is Clicky's own response verbatim, one entry per requested type, each holding dates and then items. data.rows is a flat view DERIVED by this connector, where every item carries its own type and date as real columns, because Clicky puts both on the row's parents rather than in the row. Bind charts and datasets to data.rows. Plan caps, from Clicky's own docs: a FREE account can only reach the last 30 days of history and returns at most 100 results per request, so a longer window or a bigger limit quietly returns less than you asked for. The date range itself is capped at 366 days on Pro and 31 days on every other plan.
Clicky: Outbound Links and Downloads
clicky_get_links_and_downloads
What visitors clicked, took and watched: outbound links they followed off the site, files they downloaded, javascript events you are tracking, and video plays. All four are counted as actions, so their totals reconcile with the action tallies rather than with visitor counts. Turn Video Meta on to get extra video measurements such as average watch time alongside the play count. Rows come back ordered by value descending and cut off at limit, so a result is a TOP N rather than the whole picture: raise limit or page through before treating it as complete, and never add two periods' top lists together, because the top 20 of January plus the top 20 of February is not the top 20 of both. Output shape: data.reports is Clicky's own response verbatim, one entry per requested type, each holding dates and then items. data.rows is a flat view DERIVED by this connector, where every item carries its own type and date as real columns, because Clicky puts both on the row's parents rather than in the row. Bind charts and datasets to data.rows. Plan caps, from Clicky's own docs: a FREE account can only reach the last 30 days of history and returns at most 100 results per request, so a longer window or a bigger limit quietly returns less than you asked for. The date range itself is capped at 366 days on Pro and 31 days on every other plan.
Clicky: Referrers and Traffic Sources
clicky_get_referrers
Where your traffic came from. traffic-sources is the high-level split (direct, search, links, campaigns), links is every incoming referrer as a full URL, links-domains rolls those up by domain, and the two chronological variants list referrers newest first (links-recent) or only the ones seen for the very first time (links-unique), which is the one to watch for new coverage. Rows come back ordered by value descending and cut off at limit, so a result is a TOP N rather than the whole picture: raise limit or page through before treating it as complete, and never add two periods' top lists together, because the top 20 of January plus the top 20 of February is not the top 20 of both. Output shape: data.reports is Clicky's own response verbatim, one entry per requested type, each holding dates and then items. data.rows is a flat view DERIVED by this connector, where every item carries its own type and date as real columns, because Clicky puts both on the row's parents rather than in the row. Bind charts and datasets to data.rows. Plan caps, from Clicky's own docs: a FREE account can only reach the last 30 days of history and returns at most 100 results per request, so a longer window or a bigger limit quietly returns less than you asked for. The date range itself is capped at 366 days on Pro and 31 days on every other plan.
Clicky: Run Any Report Type
clicky_run_report
Run any Clicky report by naming its type, for the reports the typed nodes above do not cover the way you need. The full vocabulary, which is Clicky's entire reporting surface, is these 57 values. Popular items: custom, pages, pages-entrance, pages-exit, downloads, events, video, site-domains, links, links-domains, links-outbound, searches, searches-keywords, searches-engines, searches-rankings, searches-local, goals, split-tests, campaigns, countries, cities, regions, languages, web-browsers, operating-systems, screen-resolutions, hardware, hostnames, organizations, engagement-actions, engagement-times, segmentation, visitors-most-active, traffic-sources. Chronological items: visitors-list, actions-list, searches-recent, searches-unique, links-recent, links-unique, uptime, uptime-list. Tallies: visitors, visitors-online, visitors-unique, visitors-new, actions, actions-pageviews, actions-downloads, actions-outbounds, actions-clicks, actions-average, time-average, time-average-pretty, time-total, time-total-pretty, bounce-rate. Prefer a typed node when one fits: they carry the right defaults and the right aggregation rules, and this node deliberately declares NO measures, because what may be summed depends entirely on which type you chose. Rows come back ordered by value descending and cut off at limit, so a result is a TOP N rather than the whole picture: raise limit or page through before treating it as complete, and never add two periods' top lists together, because the top 20 of January plus the top 20 of February is not the top 20 of both. Output shape: data.reports is Clicky's own response verbatim, one entry per requested type, each holding dates and then items. data.rows is a flat view DERIVED by this connector, where every item carries its own type and date as real columns, because Clicky puts both on the row's parents rather than in the row. Bind charts and datasets to data.rows. Plan caps, from Clicky's own docs: a FREE account can only reach the last 30 days of history and returns at most 100 results per request, so a longer window or a bigger limit quietly returns less than you asked for. The date range itself is capped at 366 days on Pro and 31 days on every other plan.
Clicky: Screen Resolutions
clicky_get_screen_sizes
Screen resolutions your visitors browsed at, ranked by visits. The practical use is deciding which breakpoints a redesign has to hold up at, so pair it with Clicky: Operating Systems and Devices rather than reading it alone. Rows come back ordered by value descending and cut off at limit, so a result is a TOP N rather than the whole picture: raise limit or page through before treating it as complete, and never add two periods' top lists together, because the top 20 of January plus the top 20 of February is not the top 20 of both. Output shape: data.reports is Clicky's own response verbatim, one entry per requested type, each holding dates and then items. data.rows is a flat view DERIVED by this connector, where every item carries its own type and date as real columns, because Clicky puts both on the row's parents rather than in the row. Bind charts and datasets to data.rows. Plan caps, from Clicky's own docs: a FREE account can only reach the last 30 days of history and returns at most 100 results per request, so a longer window or a bigger limit quietly returns less than you asked for. The date range itself is capped at 366 days on Pro and 31 days on every other plan.
Clicky: Searches and Keywords
clicky_get_searches
Everything Clicky knows about search: full search queries (searches), the same queries split into individual keywords (searches-keywords), which engines sent the traffic (searches-engines), your Google rankings ordered best to worst (searches-rankings), local-search terms (searches-local), and the chronological views of queries seen most recently (searches-recent) or for the first time ever (searches-unique). Expect a large share of modern search traffic to arrive with no query attached at all, because the engines withhold it; that is a limit of web analytics rather than of this node. Rows come back ordered by value descending and cut off at limit, so a result is a TOP N rather than the whole picture: raise limit or page through before treating it as complete, and never add two periods' top lists together, because the top 20 of January plus the top 20 of February is not the top 20 of both. Output shape: data.reports is Clicky's own response verbatim, one entry per requested type, each holding dates and then items. data.rows is a flat view DERIVED by this connector, where every item carries its own type and date as real columns, because Clicky puts both on the row's parents rather than in the row. Bind charts and datasets to data.rows. Plan caps, from Clicky's own docs: a FREE account can only reach the last 30 days of history and returns at most 100 results per request, so a longer window or a bigger limit quietly returns less than you asked for. The date range itself is capped at 366 days on Pro and 31 days on every other plan.
Clicky: Top Pages
clicky_get_pages
Your most-viewed content for a period, one row per URL with its page views, its share of the total, its title and a link into the Clicky dashboard. Also serves site-domains, which splits the same traffic by which domain name it arrived on when several domains report into one site ID. Use Item to pull a single page's number, or Filter to narrow to a section such as /blog. Rows come back ordered by value descending and cut off at limit, so a result is a TOP N rather than the whole picture: raise limit or page through before treating it as complete, and never add two periods' top lists together, because the top 20 of January plus the top 20 of February is not the top 20 of both. Output shape: data.reports is Clicky's own response verbatim, one entry per requested type, each holding dates and then items. data.rows is a flat view DERIVED by this connector, where every item carries its own type and date as real columns, because Clicky puts both on the row's parents rather than in the row. Bind charts and datasets to data.rows. Plan caps, from Clicky's own docs: a FREE account can only reach the last 30 days of history and returns at most 100 results per request, so a longer window or a bigger limit quietly returns less than you asked for. The date range itself is capped at 366 days on Pro and 31 days on every other plan.
Clicky: Uptime Checks
clicky_get_uptime
Clicky's uptime monitoring, if it is enabled on the site: uptime is the overview of checks and uptime-list is the event log of individual outages and recoveries. Uptime monitoring is a paid Clicky feature, so an account without it gets an empty report rather than an error, which is worth handling in a workflow that alerts on the result. Output shape: data.reports is Clicky's own response verbatim, one entry per requested type, each holding dates and then items. data.rows is a flat view DERIVED by this connector, where every item carries its own type and date as real columns, because Clicky puts both on the row's parents rather than in the row. Bind charts and datasets to data.rows. Plan caps, from Clicky's own docs: a FREE account can only reach the last 30 days of history and returns at most 100 results per request, so a longer window or a bigger limit quietly returns less than you asked for. The date range itself is capped at 366 days on Pro and 31 days on every other plan.
Clicky: Visitor Locations and Organizations
clicky_get_visitor_origins
Who your visitors are and where they connect from: countries, cities and regions, the languages their browsers ask for, and the network side of the same question, hostnames and organizations (which is how you spot a specific company reading your site). Organization and hostname data is derived from the visitor's IP and is missing or wrong for a large share of consumer and mobile traffic, so treat it as a lead rather than a fact. Rows come back ordered by value descending and cut off at limit, so a result is a TOP N rather than the whole picture: raise limit or page through before treating it as complete, and never add two periods' top lists together, because the top 20 of January plus the top 20 of February is not the top 20 of both. Output shape: data.reports is Clicky's own response verbatim, one entry per requested type, each holding dates and then items. data.rows is a flat view DERIVED by this connector, where every item carries its own type and date as real columns, because Clicky puts both on the row's parents rather than in the row. Bind charts and datasets to data.rows. Plan caps, from Clicky's own docs: a FREE account can only reach the last 30 days of history and returns at most 100 results per request, so a longer window or a bigger limit quietly returns less than you asked for. The date range itself is capped at 366 days on Pro and 31 days on every other plan.
Clicky: Visitor Segmentation
clicky_get_segmentation
Ask one report about one slice of your audience: top searches for visitors from Germany, top pages for people who arrived on a campaign, entry pages for returning visitors only. Segments names WHICH reports you want back and the filter fields below define WHO is in the segment; both halves are required for a useful answer, because an empty segment is just the ordinary report. Clicky caps segmentation at a 31-day range and 1000 items on every plan, which is tighter than the ordinary reports and is not a free-tier limit you can pay past. Output shape: data.reports is Clicky's own response verbatim, one entry per requested type, each holding dates and then items. data.rows is a flat view DERIVED by this connector, where every item carries its own type and date as real columns, because Clicky puts both on the row's parents rather than in the row. Bind charts and datasets to data.rows. Plan caps, from Clicky's own docs: a FREE account can only reach the last 30 days of history and returns at most 100 results per request, so a longer window or a bigger limit quietly returns less than you asked for. The date range itself is capped at 366 days on Pro and 31 days on every other plan.
Clicky: Visitor Totals
clicky_get_visitors
How many people visited: total visitors, unique visitors, first-time visitors, and how many are on the site right now. Turn Daily on to get one row per day for a traffic chart. Aggregation warning, and it is the one that produces wrong dashboards: NONE of these numbers may be added across days. Unique and new visitors are deduplicated over whatever range you asked for, so thirty daily uniques is not the monthly unique count, and visitors-online is a live gauge that ignores the date range entirely. Ask Clicky for the longer period instead of summing shorter ones. Output shape: data.reports is Clicky's own response verbatim, one entry per requested type, each holding dates and then items. data.rows is a flat view DERIVED by this connector, where every item carries its own type and date as real columns, because Clicky puts both on the row's parents rather than in the row. Bind charts and datasets to data.rows. Plan caps, from Clicky's own docs: a FREE account can only reach the last 30 days of history and returns at most 100 results per request, so a longer window or a bigger limit quietly returns less than you asked for. The date range itself is capped at 366 days on Pro and 31 days on every other plan.
Clicky: Visitor and Action Log
clicky_get_visitor_sessions
Session-level detail rather than totals: visitors-list is one row per visit with time on site, referrer, browser, operating system, geolocation and any custom data; actions-list is one row per page view, download, outbound click or event; visitors-most-active ranks the people who came back most often. This is the node behind a real-time alert workflow, usually with Time Offset set to the last few minutes rather than a date. It is also the node that returns PERSONAL DATA (IP addresses, hostnames, session identifiers), so route its output deliberately. Clicky caps these lists at a 31-day range and 1000 items on every plan, and at 100 on a free account. Output shape: data.reports is Clicky's own response verbatim, one entry per requested type, each holding dates and then items. data.rows is a flat view DERIVED by this connector, where every item carries its own type and date as real columns, because Clicky puts both on the row's parents rather than in the row. Bind charts and datasets to data.rows.
Clicky: Web Browsers
clicky_get_browsers
Which browsers your visitors used, ranked by visits, with each browser's share of the total. Use Item with an exact browser name to track one browser over time, which is the usual reason to automate this report rather than read it in the dashboard. Rows come back ordered by value descending and cut off at limit, so a result is a TOP N rather than the whole picture: raise limit or page through before treating it as complete, and never add two periods' top lists together, because the top 20 of January plus the top 20 of February is not the top 20 of both. Output shape: data.reports is Clicky's own response verbatim, one entry per requested type, each holding dates and then items. data.rows is a flat view DERIVED by this connector, where every item carries its own type and date as real columns, because Clicky puts both on the row's parents rather than in the row. Bind charts and datasets to data.rows. Plan caps, from Clicky's own docs: a FREE account can only reach the last 30 days of history and returns at most 100 results per request, so a longer window or a bigger limit quietly returns less than you asked for. The date range itself is capped at 366 days on Pro and 31 days on every other plan.
Using the integration
One endpoint, eighteen questions
Clicky is not a resource API and the palette reflects that honestly. Its entire reporting surface is one address whose meaning is chosen by a type parameter, and Clicky documents 57 values for it. Rather than ship 57 near-identical nodes or one node with a free-text box, each node here owns a report family and offers only the type values that belong to it, as a validated list with sensible defaults. So Clicky: Searches and Keywords carries the seven search reports, Clicky: Visitor Locations and Organizations carries countries, cities, regions, languages, hostnames and organizations, and Clicky: Web Browsers carries one. Ask a node for a type it does not own and it fails before the request goes out, with a message naming the values it accepts, instead of returning an empty report you would then have to diagnose. The mapping is a partition rather than a selection: every one of the 57 documented values belongs to exactly one node, so nothing is unreachable, and Clicky: Run Any Report Type accepts all of them when a report is grouped differently from the way you need it. Prefer a typed node where one fits, because it carries the right defaults and the right aggregation rules for that family.
Dates, and the Daily switch that decides everything downstream
Clicky takes one date parameter that can carry a relative token, a fixed day, a month, a year or a range. That is hostile to a scheduled workflow, so the nodes expose three fields instead and fold them into one request. Leave Start Date and End Date blank and the relative Date token is used, which is what a recurring report usually wants: last-7-days, last-month, yesterday, this-week and the X-days-ago family all work. Fill both Start Date and End Date as YYYY-MM-DD and they win, and the token above is ignored, which is what makes a scheduled backfill writing into those two fields safe from a leftover token. Then there is Daily, which matters more than its size suggests: with it off, a multi-day request returns a single undated aggregate for the whole range, and with it on you get one row per day with a real date on it. Turn it on for anything you intend to chart, store or compare over time. Hourly exists on the two tally nodes and the catch-all, implies a daily breakdown, and is meant for a single day rather than a month.
What may be added up, and what must never be
This is the part that produces wrong dashboards, so each node carries the rule for its own family. Everything Clicky: Action Totals returns is an event count, so a fortnight really is the sum of its fourteen days and rolling daily rows into weeks and months is correct. Clicky: Visitor Totals is the opposite and it is grouped that way on purpose: unique and new visitors deduplicate over whatever range you asked for, so thirty daily uniques is not the month's unique visitors, and the count of people on the site right now is a live gauge that ignores the date range entirely. Ask Clicky for the longer period rather than adding shorter ones together. Clicky: Engagement and Time Totals declares nothing summable at all: bounce rate and average time are rates, an unweighted mean of daily rates is also wrong, and Clicky returns no visitor count beside them to weight by, so the only correct move is to re-ask Clicky for the period you want. That is also why the averages that look like they belong with actions live here instead. And every ranked report is a top N rather than the whole picture, because the row limit decides which rows exist and not merely how many are displayed, so January's top 20 plus February's top 20 is not the top 20 of both.
The output shape, and why there are two views of it
Clicky answers with a nested structure: one block per requested report type, each holding a list of dates, each holding a list of items. That puts both of the things a consumer needs on the row's ancestors rather than in the row. The item carries a generic value; which metric that value is lives on the block, and which day it belongs to lives on the date. So a chart bound to the items alone cannot tell a page view from a bounce rate or Monday from Tuesday. Every node therefore returns two things. data.reports is Clicky's response verbatim, with nothing renamed and nothing dropped, which is the wire truth and the thing to read when you want exactly what Clicky said. data.rows is a flat view this integration derives, where every item carries its own type and date as real columns, capped at 5000 rows with data.row_count and data.truncated beside it. Bind charts, Mattering databases and Analytics datasets to data.rows. On the catch-all node, the Null Values option keeps empty fields in the response, which is worth turning on when you are loading results into a table that wants a stable set of columns rather than ragged rows.
Plan boundaries, and how they show up
Start with the good news, because it is easy to assume the opposite: API access is not a premium feature at Clicky. Its pricing page lists API access among the basics that every plan gets, the free one included. What a plan changes is the data, and Clicky enforces those limits by returning less rather than by refusing, which makes them worth knowing in advance rather than discovering. From Clicky's own API documentation: free accounts are limited to the last 30 days of history and 100 results per request, and the maximum date range is 366 days for Pro users and 31 days for everyone else. From its pricing page: free plans are limited to 30 days of history, paid plans have indefinite history, and individual visitors and actions are guaranteed for six months because of the space they take, which is the retention limit that matters most to Clicky: Visitor and Action Log. Clicky also documents a separate set of restrictions on the visitors-list, actions-list and segmentation reports: a maximum date range of 31 days and a maximum of 1000 items per request, with the page parameter fetching further batches of 1000. So a free account cannot backfill a quarter, cannot pull more than 100 rows in one request, and cannot answer a top 500 question in one go, and a workflow that asks anyway succeeds and returns less. Separately, two report families are gated by feature rather than by cap. Goals and revenue are premium features the free plan does not include, and uptime monitoring is listed as available on Pro Plus accounts and higher, so base Pro does not have it either. Without them, Clicky: Goals and Campaigns and Clicky: Uptime Checks have nothing to return, so a workflow that alerts on the result should treat an empty report as its own case rather than as a quiet zero. None of this is visible to Test Connection, because a free credential is a perfectly valid credential.
Concurrency, row limits and paging
Clicky's API documentation states a maximum of one simultaneous request per IP address per site ID, and says the restriction can be removed with a custom plan. That is a concurrency rule rather than a per-minute quota, and it has one concrete consequence for canvas design: a workflow that fans several Clicky nodes out in parallel will collide with itself, so chain them in sequence instead. On row counts, the Limit field takes 1 to 1000 with a vendor default of 50, and Page walks past it a page at a time. Clicky also accepts the literal word all, which reaches 5000 rows, and because Limit is a numeric field that value cannot be typed into it; send limit=all through Extra Params on the nodes that offer it, or page through instead. Extra Params is the general escape hatch for documented Clicky parameters that ship after a node, merged last so it overrides the fields above it, with the four values the connector controls refused so a workflow cannot smuggle a different credential through it. One of those four is the output format: Clicky's own default is XML, and this integration always requests JSON, because nothing downstream of a node would know what to do with the alternative.
One credential, one site, and no pickers
A Clicky sitekey is minted for exactly one site, so the site lives on the credential rather than on a node, and reporting on a second site means storing a second credential. That is also how the Clicky dashboard frames it. It follows that this integration has no site picker, and it is worth saying why rather than leaving a gap: the one Clicky endpoint that could list your sites, the account API, authenticates with your account username and password rather than with a sitekey, and Clicky states it stops working once Sign in with Google is enabled on the account. Putting an account password into a read-only reporting credential to populate a field that lives on the credential anyway is a bad trade, so it is recorded rather than built. Three other fields are free text for the same kind of reason. Alert ID on Clicky: Get Alert comes from the alert itself, which Clicky delivers by email, SMS or in-browser rather than to an endpoint: the alert links to a URL ending in the id, and Clicky documents nothing that lists alerts. Session ID on Clicky: Visitor and Action Log comes from a previous run of that same node, which is a workflow edge rather than something to type. And the Goal filter on Clicky: Visitor Segmentation takes a goal name read off the goals report, because there is no list-goals endpoint on this credential. The report type fields are deliberately not pickers either: those are closed vocabularies fixed in Clicky's own routing, enumerated in each field's description and validated before the call.
Segmentation and the session log
Two nodes answer questions the ranked reports cannot. Clicky: Visitor Segmentation takes a WHO and a WHAT: the segment fields define who is in the slice, by country, city, language, browser, operating system, resolution, traffic source, search, referring domain, landing page, exit page, any page viewed, campaign, goal completed, your own custom data, or new against returning visitors, and the segments field names which reports you want back for that slice. Both halves are needed, because an empty segment is just the ordinary report. Clicky documents tighter restrictions on segmentation than on the ordinary reports, a maximum date range of 31 days and a maximum of 1000 items per request, so keep the question inside a month and page for the rest. Clicky: Visitor and Action Log is the session-level view: one row per visit with time on site, referrer, browser, operating system, geolocation and custom data, or one row per action, or a ranking of the people who came back most often. Its Time Offset field returns only the last N seconds of activity, up to a day, which is what turns it into a real-time poller. Two cautions: it returns personal data including IP addresses and session identifiers, so route it deliberately, and the IP Address and UID filters override every other filter on the node, which makes the rest inert when either is set.
On the automation canvas
Clicky nodes chain with every other node in Mattering. A weekly schedule can run Clicky: Visitor Totals and Clicky: Top Pages, hand the flat rows to an AI step for the narrative, and file the result as a Mattering Productivity task so somebody can comment on it. A five-minute schedule can poll Clicky: Visitor and Action Log with a short Time Offset and notify a channel when a named company or a target page appears. A daily run can write Clicky: Referrers and Traffic Sources into a Mattering database, using the links-unique report so you are watching for referrers seen for the first time rather than re-reading a leaderboard. Because every node here reads and none writes, Clicky is one of the safer connectors to hand to a scheduled job or an agent; what deserves care is disclosure rather than damage, since the session log carries personal data. Note that Clicky's API documents no webhooks or HTTP callbacks, so this integration has no trigger nodes: Clicky workflows are scheduled or invoked, never pushed. Clicky's own alerts are delivered out of band instead, by email, by SMS, or as sound and desktop alerts while you are on its site. That is why Clicky: Get Alert exists at all: the alert carries an id, and the node turns that id into structured data an automation can act on rather than something to parse out of a message.
From AI assistants over MCP
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and Matter, the assistant built into the platform, can read Clicky through the same surface. Clicky publishes no MCP server of its own: its help documentation covers the stats, account and white label APIs and does not mention MCP or the Model Context Protocol anywhere. There is a community project, clicky-mcp by Colin Toh on GitHub, which is independent of the vendor and holds the same site id and sitekey in a local environment file. The argument for running Clicky here rather than in a local assistant config is not that a chat window is the wrong place to ask a question, it is what happens when the chat window is closed. The same nodes are canvas steps, so the report an assistant helps you assemble then runs every Monday with nobody present, chains with every other connector in one workflow, holds the credential once in a shared workspace rather than in each person's machine, and carries the per-family aggregation rules so a scheduled job does not quietly sum figures that must not be summed. A practical note for agent use: point an assistant at the typed nodes rather than at Clicky: Run Any Report Type where one fits, because the typed node's validation turns a bad guess into a corrective error message instead of an empty result the assistant will interpret as no traffic.
Troubleshooting
Test Connection fails and says Clicky rejected the credential
A node succeeds but the report is empty
A report never returns more than 30 days or more than 100 rows
A multi-day result has no dates on it, or a chart cannot find a date column
A node returns an error about an unknown report type
Several Clicky nodes running at once fail or hang
Numbers do not match the Clicky dashboard when days are added together
The row limit will not accept the value all
The connector is reporting on the wrong site
A search report returns far fewer queries than expected
An organization or hostname report looks wrong
Related
The Clicky MCP
What connecting Clicky unlocks for AI agents and automations, with common uses and FAQs.
More guides
All Automations documentation
Every integration guide, plus how connectors, credentials, and workflows fit together.
Clicky is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.