Add trusted server events
An optional advanced path for outcomes confirmed by your backend.
Measurement Protocol supplements browser measurement. It does not bypass consent, replace attribution setup or automatically deduplicate retries. These examples send a validation request only; they do not record a production conversion.
Your implementation route
Use available Wix SEO/log reports plus Search Console and Analytics. Keep an external uptime check if needed. Advanced event or AI API code requires supported backend functionality or a separate backend; the examples here are portable patterns, not Wix drop-ins.
Platform boundaries & account requirements
Use Wix's native integrations and SEO & GEO tools. Backend examples belong in a supported Wix backend module or an external service, never in a page embed.
Open Wix ↗A real backend, supported Node/Python/PHP runtime, server-only secret storage, a consented client/session identifier and a durable event/outbox table.
Follow the steps
Check only after completingConfirm that you need this layer
Use it when the backend is the authoritative source, such as payment confirmation or CRM lead qualification. Prefer a well-supported native integration when it already records the outcome accurately. Never put the API secret in page HTML, GTM web tags or a builder embed.
Create a server-only configuration
Create a Measurement Protocol API secret for the intended web stream. Store GA4_MEASUREMENT_ID and GA4_API_SECRET in the backend host's environment settings. Pass only a consented client ID and permitted event parameters from your trusted workflow.
Validate the payload first
Choose Node.js, Python or PHP below. Replace the example IDs with test values. Run it on your development backend and inspect validationMessages. The /debug endpoint does not write to reports and does not verify every credential; an empty array is not proof of production ingestion.
Integrate durable delivery
After validation, build an authenticated backend path from a trusted success event. Store a unique event ID and delivery state in a persistent outbox; prevent duplicate sends across retries and choose either browser or server ownership. For production remove validation_behavior, use /mp/collect, and verify reporting with a controlled test. Do not blindly retry ambiguous responses.
Implementation recipes
Expand · choose · copy</>Validate a server event — choose your runtimeOpen recipe
Run server-side only. Set GA4_MEASUREMENT_ID and GA4_API_SECRET in the host's secret environment settings. Example client/session values must be replaced with consented test values. No production events are sent by these samples.
// Save as validate-event.mjs. Requires Node 18+.
const id = process.env.GA4_MEASUREMENT_ID;
const secret = process.env.GA4_API_SECRET;
if (!id || !secret) throw new Error("Set server environment variables.");
const url = new URL("https://www.google-analytics.com/debug/mp/collect");
url.search = new URLSearchParams({ measurement_id: id, api_secret: secret });
const response = await fetch(url, {
method: "POST",
headers: { "Content-Type": "application/json" },
signal: AbortSignal.timeout(10000),
body: JSON.stringify({
client_id: "123456789.1234567890",
validation_behavior: "ENFORCE_RECOMMENDATIONS",
events: [{ name: "generate_lead",
params: { session_id: 1234567890, engagement_time_msec: 1,
form_id: "service_enquiry" } }]
})
});
if (!response.ok) throw new Error("Validation request failed.");
console.log(await response.json()); // Inspect validationMessages.
// Do not log the request URL: it contains your API secret.
// Empty validationMessages does not validate credentials or ingestion.Document payload validation, credential verification, consent propagation, duplicate/retry handling and one controlled production observation before calling the integration complete. HTTP 200 alone is not acceptance evidence.
Disable the worker/trigger and retain unsent outbox entries for review. Revoke a leaked API secret and replace it server-side. Keep the prior native/browser integration only if it does not double-count.
Read the primary instructions
Guidance checked October 7, 2026. “2027” describes this prototype’s visual concept, not a prediction of platform rules.