Skip to content

Eflios Forms

Build forms that track everything.

Create and embed forms that capture every lead, UTM, and click ID. Send clean, server-side conversion data to Meta, Google, and your CRM.

Free tier at launch, no card. One email the day accounts open.

  • full attribution
  • server-side delivery
  • no developer
  • works on any website

Live product

Build the form. See everything it captures.

Edit the example or submit it. The answers change; the attribution captured on first load stays attached.

Request a fleet demoeditable

Interactive preview only. Nothing is sent or stored.

live_submissionwaiting for submit

Answers

email
jamie@northgate.co.uk
company
Northgate Logistics
fleet_size
40–100 vehicles

Captured before submit

read on first load
utm_source
google
utm_medium
cpc
utm_campaign
q3-uk-fleet
gclid
EAIaIQobChMI3vT6nZ2…
landing_page
/fleet-tracking
Edit the form: the answers change, while the attribution stays attached.

Moving to Eflios

Switch your form. Keep your website.

Start with one form on a page you already use. Recreate its fields, connect your destinations, and test the replacement before sending traffic.

Your current pageyourwebsite.com/contact

Your branding · Your content · Your URL

Let’s talk about your business.

Your existing form

Work email
Company

Use these fields as your migration checklist

Start with one landing page or enquiry form.

With Efliosyourwebsite.com/contact

Your branding · Your content · Your URL

Let’s talk about your business.

Fields recreated in Eflios

Work email
Company

Source + consent + delivery history attached

The form changes. Your website stays in place.

Illustrated migration. Recreate the form manually in Eflios; automatic form import and historical submission transfer are not included.
  1. 01

    Recreate your fields

    Use your current form as a checklist. Rebuild its fields, required answers, steps, and supported logic in Eflios.

  2. 02

    Connect your destinations

    Add credentials, select your Meta event or Google Ads conversion action, and connect your CRM through a webhook.

  3. 03

    Match and embed

    Match your accent and theme; the font inherits from your page. Add the loader to your site and replace the old form with the Eflios container.

  4. 04

    Check a test submission

    Connect your consent signals. Test with campaign parameters, navigate, submit, and inspect attribution and delivery before sending traffic.

What can I recreate in the builder?
Fleet enquirystep 2 of 3
TextEmailPhoneNumberDateSelect+3 more
Work emailemail

required

Companytext

required

Fleet sizeselect
shown if · role is Operations

Build with nine field types, multiple steps, and conditional field visibility. Set your accent, logo, radius, color scheme, and background.

Check any custom behavior in your current form before switching. Existing submissions stay with your previous provider; export them there if you need an archive.

Webflow, Framer, and WordPress need access to custom code or an embed block. A site administrator may need to help with consent or restrictive security settings.

Embed onWebflowFramerWordPressNext.jsPlain HTML

Delivery

Every conversion delivered – and accounted for.

The lead is stored before anything is sent, then each platform gets its own attempt, its own retries and its own line in the log.

Submission + attribution

Lead stored first

Delivery runs separately

  • Meta CAPI
  • Google Ads
  • Webhook
  • Email
Example delivery logpartial → resolved
  • deliveredMeta CAPIattempt 1
    View response details

    12:04:38.512

    {"events_received":1,"fbtrace_id":"AbC…"}
  • deliveredGoogle Adsattempt 1
    View response details

    12:04:38.641

    {"results":[{"gclid":"EAIaIQ…","conversionAction":"…/3391"}]}
  • failedWebhookattempt 1
    View response details

    12:04:38.702

    504 Gateway Timeout · retrying in 30 s
  • deliveredWebhookattempt 2
    View response details

    12:05:09.114

    200 {"status":"ok","id":"7741"}
  • skippedTikTok Events–
    View response details

    12:04:38.301

    marketing consent not granted
Every attempt kept, with the platform’s own response. The skipped row is correct behavior – consent was not granted, so it says so instead of reporting a failure.

Server-side delivery

Sent from our servers, not the visitor’s browser. An ad blocker or a dropped cookie doesn’t decide whether the conversion arrives.

Automatic retries

A platform that’s down gets tried again, with backoff. The lead is already safe while that happens.

A log for every conversion

Every attempt, the platform’s own response, and the reason anything didn’t fire. Re-send by hand if you want to.

The difference

Most forms capture the lead. Eflios keeps what brought it.

What arrives
Standard:Form answers
Eflios:Answers and full attribution
Source capture
Standard:Can disappear during navigation
Eflios:Preserved from first visit
Conversion signal
Standard:Browser event
Eflios:Clean server-side delivery
After submit
Standard:Unknown delivery status
Eflios:Logged, retried and verified

Price

Free while you evaluate. €39 when it has to perform.

Capture, submissions, webhooks, email and the delivery log are free. The paid line starts where the money is: server-side conversions to Meta and Google Ads.

Free

€0

100 / mo

Starter

€39/mo

1,000 / mo

Pro

€99/mo

10,000 / mo

The comparison isn’t a free form builder. It’s the €500–2,000 an agency charges to set server-side conversion tracking up once. Full comparison, caps and overage

Join the waiting list

Questions

Form attribution, setup, and delivery explained.

Eflios Forms combines lead capture, consent-aware attribution, and server-side conversion delivery. For a practical walkthrough of lost campaign parameters, read why forms lose gclid and fbclid—and how to check yours.

Do I need to replace my existing form?

Yes. Eflios renders the form and manages its attribution and delivery together. Recreate your fields in the builder, then replace the form embed on your existing page. Your website does not need a rebuild. Automatic form import and historical submission migration are not included.

What attribution does Eflios capture with a lead?

Eflios captures supported UTM parameters, click IDs such as gclid and fbclid, the landing page, and referrer after analytics consent. First- and last-touch context stays attached to the submission. Missing identifiers or journeys before consent cannot be reconstructed.

How do UTMs survive navigation before a form submission?

The Eflios loader reads available campaign parameters when it runs after analytics consent and persists them before later navigation. The form reads that captured information at submission time, even when the contact page URL no longer contains the original parameters. Install the loader on the pages where visitors arrive, not only on the final form page.

How does Eflios connect forms to Meta and Google Ads?

Connect your destination credentials and choose a standard or custom Meta CAPI event, or a Google Ads conversion action. Eflios sends eligible submissions from the server with consent checks, retries, and delivery logs. Meta browser and server events use a shared event ID for deduplication. Meta CAPI and Google Ads are included from the Starter plan.

Can I send leads to my CRM?

Yes, through a webhook. Connect it to your CRM directly where supported, or use Make or Zapier to map the submission fields. Native HubSpot and Salesforce integrations are not included in the launch product.

Can I use Eflios Forms on Webflow, Framer, or WordPress?

Yes, where your site plan and permissions allow custom scripts and an embed container. Add the loader to the site, place the form container on your page, and connect your consent signals. Match your theme and test a submission before publishing the replacement.

What happens when a visitor declines consent?

The form can still accept a submission. Attribution capture requires analytics consent, and marketing destinations require marketing consent. Consent state is stored with the submission; a destination skipped for consent is shown with its reason.

What happens if a destination fails?

The submission is stored before delivery begins. Transient destination failures are retried with backoff, while the delivery log records attempts and responses. You can inspect a failed delivery and retry it manually; a platform failure does not remove the stored lead.

Early access

Bring your first form to Eflios.

Forms is built; signups aren’t open yet. Leave your email and you’ll get one message the day they are.

  • email only
  • no newsletter
  • deleted on request
  • no card

One email when Eflios opens – nothing else, no newsletter. Ask us any time and the entry is deleted.