using Adobe on our Confluence instance - cannot calculate number of pages that were edited.

Question

Dear Confluence experts.

Several years ago we have connected our Confluence instance to Adobe analytics.Adobe is configured to calculate number of pages created based on page creation URL that has createpage.action and number of pages that were edited based on page edit URL that has editpage.action

However, recently I’ve realized that when I edit the page, the URL does not have editpage.action (only if I refresh the browser then it will appear) for page creation the URL is correct on first loadsee screenshots

Does anyone have experience with this? How can we get Adobe to correctly calculate the number of Confluence pages that were Edited in our instance?

Creating a new Confluence page: (URL correctly has createpage.action)

Editing any Confluence page: (URL does not have editpage.action)

after step above or Edit page, if we refresh the browser, then the URL will have editpage.action:

any advice on how to set our Adobe Analytics to correctly collect the number of page that were edited.

(of course this calculates the number of pages that user clicked Edit without checking if user actually clicked update to push any update)

Mikhail “in Peru” · Answer

Adding the Cloud side to what Ciro and Mihai said, since the SQL route is Data Center only. In Cloud every save of a page is stored as a version with its own timestamp and author, and the REST API returns them: GET /wiki/api/v2/pages/{id}/versions gives number, createdAt and authorId for each save, newest first, paged with a cursor. I checked it on a test site just now: two edits made a minute apart came back as versions 2 and 3 with their own timestamps, version 1 being the creation.

So a monthly report of pages edited and edits made takes two steps. First narrow down the pages with CQL: type = page AND lastmodified >= "2026-10-01". Use the start of the period and no end date, because lastmodified is the date of the newest version only: a page edited on 5 October and again on 2 November has its lastmodified in November, and a between-dates query for October would miss it. Then, for each of those pages, read the versions and count the ones whose createdAt falls inside the period, skipping version 1 if you only want edits and not creations. Pages with at least one such version is your pages-edited figure; the sum is the number of edits. It costs one extra request per page, so it belongs in a small scheduled script rather than in Adobe itself.

The same thing catches out the simple CQL count from earlier in the thread: run it for October today and again in December, and October's number will be lower, because pages edited again in November drop out. If the figure goes into Adobe as a monthly data point, take it at the end of the month and store it, or use the versions route, which does not change after the fact.

Mihai_LeanZero · Answer

Your screenshots already show the URL after Edit. resumedraft.action, no reload. The create screenshot lands on resumedraft.action too, so a rule matching it can pick up creates as well.

I'd put a Click rule on the Update button in Launch instead. Much closer to real saves than editor opens. A failed publish still counts, a keyboard save skips it. Haven't tried it on your setup, so check in the Launch debugger whether new pages use the same button.

CQL lastmodified is per page whose newest change falls in the range. Five edits, one count.

Every save? With Confluence analytics on, Data Center logs page_updated events in AO_7B47A5_EVENT and the KB has SQL for both edits and distinct pages: https://support.atlassian.com/confluence/kb/how-to-retrieve-the-number-of-pages-edited-or-viewed-by-users-from-the-database/

Ciro · Answer

Hi! What you're seeing is expected: when you click Edit, Confluence loads the editor in place with JavaScript instead of loading a new page. So the editpage.action URL only reaches the browser on a full reload, and Adobe never sees it on a normal click.

Two ways around it:

* Count saves, not editor opens (more accurate): as you said, opening the editor doesn't mean anything was saved. Confluence already knows what changed, so you can ask it with CQL:

• Pages created: type = page AND created >= "2026-10-01"

• Pages edited: type = page AND lastmodified >= "2026-10-01"

Run them through /rest/api/search?cql=...&limit=1 and read totalSize, or schedule a small script that pushes the numbers into Adobe as a data source.
* If it has to stay in Adobe: in Adobe Tags (Launch), add a rule on the Core extension's History Change event so you also catch URL changes that don't reload the page. Then check in your browser's address bar what the URL looks like right after clicking Edit, and match on that.