Forward analytics

Hypertune provides two ways to forward analytics events, split exposures, and flag evaluations to your own data warehouse or analytics system:

1. Custom local logging callback

2. Custom remote logging endpoint

Option 1: Custom local logging callback

You can define a custom local logging callback with the logsHandler option when calling createSource that captures analytics events, split exposures, and flag evaluations, and forwards them to an analytics SDK in the browser, for example to Segment.

Option 2: Custom remote logging endpoint

By default, all analytics events, split exposures, and flag evaluations are sent to Hypertune Edge via the following endpoint: https://gcp.fasthorse.workers.dev/logs

You can change this endpoint with the remoteLogging.endpointUrl option when calling createSource. Point it to your own server endpoint where you can forward data to your own warehouse or analytics system, and optionally to Hypertune Edge too.

Comparison

	Custom local logging callback	Custom remote logging endpoint
Pro	Simple integration with client-side SDKs of third-party analytics providers.	Ensures you don't lose any data due to ad blockers or network restrictions in the browser.
Con	Some data may be lost due to ad blockers or network restrictions in the browser.	Server-side integration may be more complex depending on data destination.