SDK and event security

A fast SDK layer for reliable experiments and secure event delivery.

Testvoy SDK is designed to run experiments on customer sites, preserve event context and keep the measurement pipeline more resilient.

Web SDKMobileServerGTM
Browser SDK docs Mobile SDK status
Product layerSDK and event security
Module control
Primary signalReliable experiment infrastructure with Browser SDK, CDN delivery, signed context and retry behavior.

This module connects setup, reporting and decision output inside the Testvoy workflow.

DeliveryVersioned CDN and Browser SDK flow
SecurityPrivate app tokens never go on customer sites
ReliabilitySigned context and retry behavior
01BuildAsync script
02ValidateGTM path
03DecideProject identifier
SDK and event pipeline

A dashboard is only as trustworthy as the technical layer running on the customer site.

Testvoy SDK is designed to load experiments quickly, reduce flicker risk, send event data with the right context and keep the measurement pipeline more resilient. Technical teams get a more predictable install path while growth teams read experiment results through a cleaner data pipeline.

Versioned CDNPredictable loading

SDK paths and versioning help keep installs more controlled.

LightweightPerformance focus

The browser SDK is designed to run experiment flows without unnecessary weight.

Signed contextEvent integrity

Events can be validated against the right project and experiment context.

Retry queueResilient delivery

Queue and retry behavior helps reduce event loss during network fluctuation.

Product capabilities

The core job Testvoy solves with this module.

This section shows what the module helps teams do, which risks it reduces and which decision it makes easier to defend.

Back to product hub
01

Web and GTM first

Browser SDK and GTM paths help teams start web experiments with a controlled install.

  • Async script
  • GTM path
  • Project identifier
02

Mobile and server paths

Mobile and server paths are positioned to preserve experiment and event context across platforms.

  • Mobile SDK staged
  • Server-side beta path
  • Platform separation
Where teams use it

Built for the experiment and optimization workflows teams run every week.

01

Next.js and modern SPA sites

Focus on route-aware scope and experiment application behavior in modern frontends.

02

Fast GTM start

Growth teams can position Browser SDK installation through a GTM path.

03

Secure event ingest

Signed context and abuse guard language help protect report integrity.

Decision path

The role this module plays in the experiment program.

01

Web and GTM first

Browser SDK and GTM paths help teams start web experiments with a controlled install.

02

Async script

GTM path

03

Mobile and server paths

Mobile and server paths are positioned to preserve experiment and event context across platforms.

04

Delivery

Versioned CDN and Browser SDK flow

How it works

Clearer setup, cleaner signals, faster decisions.

Testvoy positions this module to help teams move from experiment idea to report with the same data, context and decision language.

SDK performance is a trust signal for conversion products

If an experimentation tool slows down the customer site, the test itself becomes a conversion risk. Testvoy positions speed, loading control and anti-flicker behavior as product fundamentals.

  • Browser SDK is designed to stay lightweight
  • Anti-flicker behavior is designed to reduce visual flicker risk
  • Versioned CDN delivery keeps installs more predictable

Event security is where report trust begins

Events with the wrong project, wrong experiment or fake context can pollute reporting. Signed event context helps preserve the right ingest context.

  • Project and experiment context can be validated
  • Public endpoint abuse risks can be limited
  • Bot filtering and SRM checks strengthen reporting quality

Privacy-aware measurement should be product behavior, not a slogan

Experimentation should not require moving unnecessary sensitive data. Testvoy's measurement posture focuses on preserving experiment accuracy without carrying private tokens, card data or unnecessary customer data.

  • Authenticated API calls are separated from the public surface
  • DNT/GPC and opt-out signals can be respected in the product posture
  • Technical setup remains under /docs/web-sdk and /docs/mobile-sdk
FAQ

Fast answers before the decision.

What does the SDK do on a customer site?

It helps apply experiment variants, send events and preserve measurement context in the browser layer.

Is anti-flicker guaranteed?

Instead of absolute guarantees, the SDK is described as designed to reduce flicker risk.

Where are technical installation details?

Browser SDK and mobile SDK installation details live under /docs/web-sdk and /docs/mobile-sdk.

Reliable experiment infrastructure with Browser SDK, CDN delivery, signed context and retry behavior.

Private app tokens never go on customer sites

Browser SDK docs Back to product hub