GA4 measurement for a community site
Measure the actions that help an event operator decide what to improve next.
Direct answer: Miyako de IT measures four actions in GA4: clicks that send readers to connpass, Discord-entry links, article views, and reading progress through scroll depth and completion. The purpose is to decide which page or path needs attention next.
GA4 tells us what actions happened and how often. It does not prove that reading an article caused someone to attend an event. We use the data as an operating input, not as proof of causation.
Four actions we measure
| Action | GA4 event | Operating question |
|---|---|---|
| Click to connpass | connpass_click | Which article or placement sends people to an event? |
| Discord entry path | outbound_link_click | Is a community-entry path used in context? |
| Article view | blog_view | Which articles are actually opened? |
| Reading progress | scroll_depth_75 / read_complete | Are readers reaching the end? |
Measuring event referrals
TrackedExternalLink wraps external links with GA4 measurement. With the connpass variant, a click sends connpass_click; the outbound variant sends outbound_link_click. A source label—such as hero, events_card, or footer—lets us distinguish locations that point to the same destination. Current event announcements are published on Miyako de IT’s connpass.
Measuring the Discord path
DiscordInlineCTA is the horizontal invitation card used on pages such as first-time, event, and FAQ pages. Its button sends outbound_link_click and includes a source label, helping us compare where readers choose to enter the community.
Measuring reading, with limits
BlogViewTracker sends blog_view once when an article is shown. ScrollTracker sends scroll_depth_75 at 75% of the page and read_complete at about 98%. Short pages are excluded from scroll measurement, so completion cannot be compared uniformly across every article.
How the data is used
If an article is opened but rarely read through, we review its lead and structure. If a useful event article does not send readers to the event page, we review the link’s placement and heading. We compare these operating hypotheses with our owned-media record and community statistics, while keeping the distinction between observation and causal proof clear.
Summary
Miyako de IT has operated in Kyoto for seven years and held 163 events. The measurement is only a tool; the actual gathering remains the center of the community. For current gatherings, visit Miyako de IT on connpass.
Related articles
Search Traffic to a Community Site: Bing Was Contributing Too
Search traffic to a community site does not come only from Google. When Miyako de IT measured GA4 on July 24, 2026, Bing organic search produced 68 sessions in the prior 90 days—about one tenth of Google for the same period. This report records that observation, AI referrals, and why we publish the numbers without claiming causation.
Miyako de IT Sponsor Award for YARIGAI at Impact Kyoto Hackathon 2026
Miyako de IT joined Impact Kyoto Hackathon 2026 as a sponsor and presented its Sponsor Award to team YARIGAI. In support of the project’s focus on preserving purpose and human value in the generative-AI era, the team received invitations to attend Miyako de IT events free of charge for one year.
How Search Clicks Grew About 11× in Six Months after We Turned a Member Site into a Publishing Site
A first-party operating log from six months of publishing on miyakodeit.com. Search clicks rose from 17 in January 2026 to 183 in June, while impressions grew about 35× from the first measured month. The article also records measurement and causality limitations.
Source data
The figures cited in this article are based on primary data in the Miyako de IT annual statistics report. It publishes yearly event counts, venue distribution, and event-format data.
Written by
Miyako de IT Editorial Team