Developer guide
Download WordPress pluginIntegrate Wefido Signals
A consistent format for measuring browser, WordPress and server-side events, with consent management and deduplication.
Web SDK
Script for custom websites
Create a source, verify its domain and use only the public Web Signal key.
<script
src="https://wefido.it/sdk/wefido-signals.js"
data-wefido-source-key="wfs_web_..."
data-wefido-endpoint="https://events.wefido.it/v1/events"
data-wefido-auto-pageview="false"
defer>
</script>WefidoSignals.setConsent({
granted: true,
version: "cmp-policy-2026-07",
recordedAt: new Date().toISOString()
})
WefidoSignals.track("lead", { form: "contact-request" })WordPress
Guided installation and CMP support
The plugin integrates with the WordPress Consent API, CookieYes, Complianz, Cookiebot, OneTrust, iubenda and Borlabs Cookie. Events are sent only when the required consent can be verified.
- Install the ZIP from Plugins > Add Plugin.
- Open Settings > Wefido Signals.
- Enter the source public key, purpose and consent version.
- Verify the domain and inspect diagnostics.
WooCommerce records paid purchases without personal data; Contact Form 7 records submitted enquiries.
Event contract
Available events
page_viewview_contentsearchcontactleadpurchaseappointment_requestKeep the same event_id across retries: duplicate requests are not counted twice.
Events API
Server-to-server conversions
The secret key always stays on your server. After activating the source, you will receive the credentials and instructions required to sign each request.
// Keep the secret key in your backend only.
// Use the source credentials to sign every request.
sendWefidoEvent({
event: "purchase",
eventId: order.eventId,
consent: order.analyticsConsent,
occurredAt: new Date().toISOString()
})Built-in privacy
No events before consent
- Consent, version and timestamp are required.
- Stop sending immediately after withdrawal.
- Do not send directly identifying data.
