Skip to content

feat: add custom tracking domain support#35

Merged
tyson-cleary-appier merged 1 commit intomasterfrom
tyson-cleary/AIRIS-7321/custom-tracking-domain
Mar 16, 2026
Merged

feat: add custom tracking domain support#35
tyson-cleary-appier merged 1 commit intomasterfrom
tyson-cleary/AIRIS-7321/custom-tracking-domain

Conversation

@tyson-cleary-appier
Copy link
Copy Markdown
Collaborator

@tyson-cleary-appier tyson-cleary-appier commented Feb 2, 2026

Summary

  • Add tracking_domain config option to allow custom tracking endpoints
  • When configured, requests are sent to https://{tracking_domain}/track/ instead of region-based endpoints
  • Falls back to existing region-based endpoints (EU/KR) if no custom domain is set

Test plan

  • Verify getEndpoint() returns custom domain URL when tracking_domain is configured
  • Verify getEndpoint() falls back to region-based endpoints when no custom domain is set
  • Verify custom domain takes priority over region setting

Add KEY_TRACKING_DOMAIN config option that allows sending tracking
requests to a custom domain instead of the default region-based
endpoints. When configured, requests are sent to
https://{tracking_domain}/track/.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@tyson-cleary-appier tyson-cleary-appier merged commit 0e4aea7 into master Mar 16, 2026
@tyson-cleary-appier tyson-cleary-appier deleted the tyson-cleary/AIRIS-7321/custom-tracking-domain branch March 16, 2026 07:42
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