Skip to content
Ordyum

Docs · WordPress

Ordyum Lead Capture for WordPress

Every form submission and paid WooCommerce order reaches Ordyum with the campaign that brought it. Connect in one click, no Zapier and no code.

Download plugin 2.0.0Start free trial

Ordyum Lead Capture

Version 2.0.0

Requirements

WordPress
6.5+
PHP
7.4+
WooCommerce (optional)
8.0+
Tested up to
WordPress 7.1

What it does

Every lead arrives with its source

  • Six form plugins

    Contact Form 7, WPForms, Elementor Pro, Gravity Forms, Ninja Forms and Fluent Forms. Only the ones installed on the site appear as switches in the panel.

  • WooCommerce orders

    Paid orders become customers with the campaign that brought them. Optionally a won deal per order, which Ordyum sends to Google Ads and Meta as an offline conversion. Works with HPOS and the block checkout.

  • Ad attribution

    UTM parameters (including utm_id), gclid, gbraid, wbraid, fbclid and the _fbp/_fbc cookies, kept 90 days in first-party cookies, plus landing page and referrer. Without the Meta pixel, _fbc is created from fbclid.

  • No lead is lost

    If Ordyum can’t be reached, the lead or order is queued and retried by WP-Cron with backoff. The same idempotency key is reused, so retries never create duplicates.

Installation

Connected in three steps

  1. 1

    Install and activate

    Download the zip. In WordPress go to Plugins → Add New → Upload Plugin, choose the file and activate “Ordyum Lead Capture”.

    Download plugin (.zip)
  2. 2

    Connect with Ordyum

    Open Ordyum in the WordPress left menu and click Connect with Ordyum. Sign in to Ordyum and choose the workspace that should receive the leads.

  3. 3

    Back, already connected

    WordPress comes back connected: Ordyum creates an API key just for this site, named “WordPress · your-domain”. Send a test form and the lead shows up in Contacts.

Prefer an API key?

Open “Use an API key instead”, paste a key with write access (Ordyum → Settings → Integrations → API keys) and click Verify. The key is only saved if Ordyum accepts it. Agencies with their own Ordyum server can change the address there too.

Disconnecting

Disconnect in the plugin revokes the site’s key in Ordyum. You can also revoke it from Ordyum → Settings → Integrations → Connected websites.

Website chat

Since version 1.8 the plugin can also show the Ordyum chat. Turn it on in Ordyum → Settings → Assistant, then switch on “Show the Ordyum chat on this site” in the plugin. No code to paste.

About the website chat

Chat hidden by your theme?

The chat is isolated from your theme’s styles, but some themes, page builders or popups use very aggressive CSS or stacking that can still cover it. If the bubble doesn’t appear:

  • Clear your cache and optimisation plugins (minify or “delay JavaScript”) and exclude chat.js from them.
  • Check that no cookie banner, sticky footer or popup sits on top of the bottom corner, or move the chat to the other side in its settings.
  • If it still doesn’t show, look for custom CSS targeting #ordyum-chat or every div on the page, and remove it.

Data

What gets sent

  • Mapped automatically

    Name, email, phone, company and message are recognised by their label in English, Spanish and French. Every other field arrives as a custom field.

  • From each order

    The buyer’s billing name, email, phone and company, the order lines and total, and the attribution saved at checkout.

  • Never sent

    Password, file, consent and captcha fields. Gravity Forms spam entries are skipped. Mention Ordyum as a processor in the site’s privacy policy.

Developers

Filters

Adjust or skip what the plugin sends from your theme or a small plugin.

ordyum_should_send
(bool $send, array $context, array $fields)
Return false to skip a form.
ordyum_lead_payload
(array|null $payload, array $context, array $fields)
Adjust the lead payload or return null to skip it.
ordyum_should_send_order
(bool $send, WC_Order $order)
Return false to skip an order.
ordyum_order_payload
(array|null $payload, WC_Order $order)
Adjust the order payload (POST /v1/orders) or return null to skip it.
Example: skip a form and tag the rest
// functions.php
add_filter('ordyum_should_send', function ($send, $context) {
    // Newsletter form: not a lead.
    return (string) $context['form_id'] === '42' ? false : $send;
}, 10, 2);

add_filter('ordyum_lead_payload', function ($payload, $context) {
    if ($payload) {
        $payload['source'] = 'landing-implants';
        $payload['custom']['landing_variant'] = 'b';
    }
    return $payload;
}, 10, 2);

$context contains integration, form_id and form_name. The old ordium_* filter names still run, before the ordyum_* ones.

Something not arriving?

The plugin panel lists the last leads and orders sent and explains connection errors in plain words. If it’s still stuck, write to us with the site address.

What’s new in the pluginHelp and support

Your clients’ leads deserve better than a spreadsheet.

Set up your agency, your first client and its API key in two minutes. Connect a form and watch the first lead arrive.

Start free trial Talk to sales

No card required · Cancel anytime · Or try the demo without signing up