Skip to content

Tag Telegram GA4 search events with search_source=telegram - #471

Merged
xenodus merged 1 commit into
masterfrom
cursor/telegram-ga4-search-source-1c0e
Sep 15, 2026
Merged

xenodus merged 1 commit into
masterfrom
cursor/telegram-ga4-search-source-1c0e

Conversation

@xenodus

@xenodus xenodus commented Sep 15, 2026

Copy link
Copy Markdown
Owner

Telegram /price searches already send GA4 search events via Measurement Protocol. This adds a search_source=telegram event parameter so bot traffic can be filtered in GA4 (Explorations, Data API, BigQuery) without inferring from the shared telegram-bot client ID.

GA4 setup: register a custom dimension for event parameter search_source (event scope) in GA4 Admin before it appears in standard reports.

Privacy policy: no change — no new data collection; existing aggregate search analytics now include a channel tag.

Testing

  • go test -mod=vendor ./gateway/ga4/... — pass
  • Full make test — one unrelated live gateway flake in gateway/tefuda (outbound request failed)
Open in Web Open in Cursor 

Telegram /price searches sent via Measurement Protocol now include a
search_source event parameter so bot traffic can be filtered in GA4
externally without relying on the shared telegram-bot client_id.

Co-authored-by: xenodus <xenodus@gmail.com>
@xenodus
xenodus marked this pull request as ready for review September 15, 2026 18:41
@xenodus
xenodus merged commit f534ac7 into master Sep 15, 2026
4 checks passed
@xenodus
xenodus deleted the cursor/telegram-ga4-search-source-1c0e branch September 15, 2026 18:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants