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.

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.

Submitted+ attributionStoredbefore any sendMeta CAPIGoogle AdsWebhookEmail
delivery_log · sub_8f3a91c4partial → resolved
  • deliveredMeta CAPIattempt 1 · 12:04:38.512

    {"events_received":1,"fbtrace_id":"AbC…"}

  • deliveredGoogle Adsattempt 1 · 12:04:38.641

    {"results":[{"gclid":"EAIaIQ…","conversionAction":"…/3391"}]}

  • failedWebhookattempt 1 · 12:04:38.702

    504 Gateway Timeout · retrying in 30 s

  • deliveredWebhookattempt 2 · 12:05:09.114

    200 {"status":"ok","id":"7741"}

  • skippedTikTok Events · 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 builder

Everything you need to create forms that convert.

The attribution is the reason to switch. This is the part that has to be as good as what you already use.

Fleet enquirystep 2 of 3
TextEmailPhoneNumberDateSelect+3 more
Work emailemail

required

Companytext

required

Fleet sizeselect
shown if · role is Operations
Drag-and-drop builder
nine field types, dropped exactly where you want them
Multi-step forms
split a long form into steps people finish
Conditional logic
a field appears only when it applies
Custom themes
accent, logo, radius, scheme, background – the font inherits from your page
Embedding
a script tag on any site, or a React component
Submission management
answers, attribution and delivery per lead, with CSV export
Analytics
volume, top sources and campaigns, delivery health

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

Want this pointed at your own campaigns?

Accounts open soon, and the list decides the order.

Join the waiting list

Setup

From first field to full attribution in minutes.

No developer, no tag manager, no deploy. If you can paste a script tag into your site, everything below happens on its own.

  1. Build your form

    01
    Fields, steps and logic in the builder. Minutes, and nobody has to open an editor.
  2. Paste one embed

    02
    A script tag and a div, anywhere on the page. No tag manager, no build step, no deploy.
  3. Eflios captures attribution

    03
    UTMs and click IDs read on first load and persisted, before any navigation can eat them.
  4. Conversions reach your platforms

    04
    Meta, Google Ads and your CRM, server-side and deduped – with a log of every attempt.

Works on

WebflowFramerWordPressNext.jsPlain HTML

That’s the product, limits included.

If it’s a fit, the only thing left is to be early.

Join the waiting list

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

Asked before anyone asks about price

Isn’t this just GTM and a webhook?

You can build it: a dataLayer push, a server-side GTM container, PII hashing, event IDs that dedupe against the pixel, a retry queue, and somewhere to look when a lead doesn’t arrive. That’s the agency setup this is priced against. The difference isn’t capability – it’s that nobody has to maintain it.

Do I have to replace the form I already have?

Yes, and that’s the point: capture has to start when the page loads, not at submit, so Eflios renders the form. The font inherits from your page and you set the accent, so it reads as part of the site rather than as an embed.

Will it work on Webflow or Framer without a developer?

That’s the primary target, not a compatibility note. Two lines, pasted in. The form renders in a shadow root so your CSS can’t reach into it and its CSS can’t leak out, and containers a page builder injects late still render – exactly once.

What about consent and GDPR?

Capture waits for analytics consent; marketing destinations fire only on marketing consent. The consent state is stored on the submission, so a destination that correctly didn’t fire reads as a skip with its reason rather than a failure. Eflios is the processor; you stay the controller.

What happens if Meta is down when a lead comes in?

Nothing happens to the lead. It’s committed to the database before any destination is called. Delivery runs from a queue with retries, the log shows “attempt 2 of 5” rather than a silent pending, and you can re-fire by hand.

Early access

Three fields, a pixel ID, one snippet – once accounts open.

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.