Skip to main content
A connector is a public HTTPS endpoint that returns visitor context to Dynamite. Use it for information such as a company’s industry or an explicitly stated preference.

​
Request

Dynamite sends a request like:
Your application maps the anonymous visitor ID to its own record. Dynamite does not forward the visitor’s authenticated session automatically.

​
Response

Return a JSON object with scalar values:
Nested keys become dot paths. Use fields to allowlist the values you want to return. Traits are signed and stored in a browser-readable cookie; they are not encrypted.

​
Timing

Enrichment runs separately from the first decision. Results are cached and used by later decisions. Completing a quiz does not immediately refresh traits or rerun personalization. Keep access and discount rules in your application. Connector traits inform selection; the standard gate set has no general trait-expression evaluator.
Arrays are ignored. Strings are trimmed to 200 characters; finite numbers and booleans are retained. Up to 30 scalar keys per connector are considered. Combined traits are bounded to about 2,400 characters.
  1. The browser starts enrichment independently of the first decision when enabled and no valid value is available.
  2. The server calls enabled connectors in parallel with individual 200–4,000 ms timeouts.
  3. Failures are isolated; successful traits are bounded and signed for site/workspace/visitor with expiry.
  4. The browser stores the signed value in a first-party enrichment cookie.
  5. Later decisions return it. The server verifies the signature, bindings and expiry before using traits.
Enrichment does not block the page and completion does not automatically repaint it. The browser suppresses repeated attempts within a session and retries failures after a cooldown. A connector’s TTL and successful results govern freshness. There is no general public method to update arbitrary traits immediately after a quiz response.
Connectors require public HTTPS without credentials in the URL or nonstandard ports. Fetching resolves/pins public addresses, rejects private/link-local targets, disallows redirects and limits responses to 64 KB. Up to five connectors can be configured. Secret header values remain on the server and are not returned in public runtime settings.Test a connector with synthetic data through authenticated settings before enabling it for visitors. Ensure the intended source fields and your consent integration agree. Prefer source, freshness and match-confidence metadata when it makes interpretation clearer.