Forms & landing pages under your own brand
With embeddable forms on your own site and hosted landing pages on your own (sub)domain, you place the intake of your platform exactly where your visitors already are. White-label from the first field to the confirmation: your colours, your domain, your brand.
The difference is under the hood. With every submission we record the consent at the moment itself: the opt-in text, the version and the timestamp together form an airtight consent record. At the same time we capture the provenance automatically: UTM parameters, source, campaign, landing page and referrer travel along into your flow and your audit trail.
Two ways to collect, one result
Embed a form in your existing page or publish a complete landing page on your own domain. Whichever you choose: the request comes in the same verifiable way, with consent and provenance included.
Embeddable forms
Paste one small script or an iframe onto your own website, landing page or CMS and the OXIAE form appears seamlessly between your own content. No redirect, no unfamiliar domain: visitors simply stay with you.
Hosted landing pages
Would rather not build your own page? Publish a complete landing page on your own (sub)domain, with your headline, copy, imagery and form. Live fast, no developer needed, and SSL is on by default.
Under your own brand
You set the colours, font, logo, button style and thank-you text yourself. Visitors see your brand, not OXIAE’s. White-label from the first field to the confirmation.
Multi-step & conditional
Split long requests across multiple steps and show only relevant fields based on earlier answers. Fewer drop-offs, cleaner data and requests that arrive complete right away.
Bot & spam protection
Invisible bot detection, honeypot fields and rate-limiting keep automated junk out of your flow, without bothering your real applicants with annoying puzzles.
Consent at the source
We capture the opt-in text, its version, the timestamp and the source the moment someone submits. That creates an airtight consent record, with no reconstruction after the fact.
Provenance that writes itself
You do not have to set anything up manually. When a visitor arrives via an ad, email or link, the form captures the full marketing context and ties it inextricably to the request.
That way you know for every request exactly which campaign, which ad and which landing page delivered it, so you can steer your publishers and buying on what really performs instead of on a gut feeling.
- Full UTM set, referrer and landing page per request.
- Automatic linking to the right label and the right campaign.
- Traceable in the audit trail, down to a single request.
Captured automatically on submit
Source
google-ads
Campaign
legal-aid-q2
utm_medium
cpc
utm_content
ad-b
Landing page
apply.yourbrand.com/start
Referrer
google.com
Label
yourbrand-legal
Device
mobile · iOS
From form to request in your flow
From the first field a visitor fills in to a verified request in your lead flow, in five steps, without intervention and without export.
Visitor arrives
Someone clicks your ad or link and lands on your own page or subdomain. The UTM parameters, referrer and landing page are recognised and stored straight away.
Form is filled in
With multi-step or conditional forms the visitor only sees relevant fields. Validation at the source makes sure email, phone and postcode are correct before submission is possible.
Consent recorded
On submission we record the opt-in text, the version, the timestamp and the source. That forms the airtight consent record that stays attached to the request.
Bot & spam check
Invisible bot detection, honeypots and rate-limiting filter out automated junk. Only real requests flow through.
Straight into your flow
The request goes in real time to verification, matching and routing, and, if you want, straight into your CRM, with provenance and consent included.
Fully under your own brand
White-label is not a logo in a corner. From the domain in the address bar to the thank-you page: visitors see your brand and stay in your world. OXIAE runs invisibly in the background.
Your own house style
Set the primary colour, font, corner radius and button style. The form automatically adopts your brand feel, without you having to write any CSS.
Your own (sub)domain
Publish on apply.yourbrand.com instead of an OXIAE URL. You point a single DNS record once and we handle the certificate.
Your own copy & languages
You decide the headline, intro, field labels, validation messages and thank-you page. Offer the same form in multiple languages for different audiences.
More than just forms under your own brand?
Discover how you manage labels, domains, branding and portals fully white-label.
Embedding is two lines
Paste the snippet onto your own page and your form is live. The visitor’s provenance is recognised and sent along automatically, so you do not have to build anything for it.
<!-- Paste this on your own page; provenance is captured automatically -->
<div data-oxiae-form="frm_8f21"></div>
<script src="https://forms.oxiae.com/embed.js" async></script> Validation and instant flow-through
A form that only collects is half a solution. OXIAE checks the request at the source and then lets it flow through immediately to verification, matching and routing, without export, without copy-paste work.
Validation at the source
Email, phone and postcode are checked instantly for format and plausibility. You enforce required fields, patterns and lengths before a request can even be submitted.
Instant flow-through
The moment someone submits, the request enters your flow in real time: verification, matching and routing. No intermediate step, no export, no copy-paste work.
Straight to your CRM
Push accepted requests, including provenance and consent, to your CRM via our webhooks or REST API.
Insight per form
See per form and landing page how many requests come in, where drop-offs occur and which campaign delivers the most.
Consent at the source is stronger than reconstruction after the fact
Permission you only try to trace later is not permission you can demonstrate. A log line that says “there was a checkbox” does not hold up if you cannot show which text was there and when someone accepted it.
That is why OXIAE records consent at the moment itself. The exact opt-in text, its version, the timestamp, the IP and the source URL are attached inextricably to the request. If you change the text later, the version number moves with it, so for every request you can demonstrate exactly what someone said yes to.
{
"consent": {
"given": true,
"text": "I give permission for yourbrand.com and affiliated partners to contact me by phone and email about my request.",
"text_version": "v3-2026-02",
"timestamp": "2026-06-26T11:18:42Z",
"ip": "84.12.x.x",
"source_url": "https://apply.yourbrand.com/start",
"method": "explicit-opt-in-checkbox"
},
"provenance": {
"source": "google-ads",
"campaign": "legal-aid-q2",
"utm_medium": "cpc",
"utm_content": "ad-b",
"landing_page": "https://apply.yourbrand.com/start",
"referrer": "https://www.google.com/"
}
} Collecting at the source vs. standalone forms
What it delivers when consent and provenance travel along by default, instead of something you hope to be able to reconstruct afterwards.
Frequently asked questions about forms & landing pages
The questions we get most often from teams that want to collect requests under their own brand.
Can I keep my existing form?
Yes. You have three options. Use the OXIAE form embedded in your own page, publish a complete hosted landing page, or keep your current form and send the submissions to OXIAE via the API or a webhook. In that last case you pass the opt-in text, the timestamp and the provenance yourself, so the consent record stays airtight there too.
How exactly is consent recorded?
The moment someone submits, we store the exact opt-in text, along with the version of that text, the timestamp, the IP address, the source URL and the method (for example an explicit opt-in checkbox). Together that forms an airtight consent record that is inextricably attached to the request and traceable in the audit trail. If you later change the text, the version number moves with it, so you can always demonstrate what someone said yes to at the time.
Can the form be on my own domain and in my own house style?
Yes, that is exactly the starting point. Embedded forms sit literally on your own page. Hosted landing pages you publish on your own subdomain, for example apply.yourbrand.com, by pointing a single DNS record once; we handle the SSL certificate. You set the colours, font, logo and copy yourself, so visitors see your brand and not OXIAE’s.
Are multilingual forms possible?
Absolutely. You can set field labels, validation messages, the opt-in text and the thank-you page per language and offer the same form in multiple languages. The opt-in text is recorded as its own version per language, so even for applicants in another language you can demonstrate exactly which text was shown.
How do you stop spam and bots?
We combine invisible bot detection, honeypot fields, per-IP rate-limiting and optional challenges only on suspicious behaviour. Validation at the source also filters out impossible email addresses and phone numbers. Real applicants notice none of this; automated junk never even enters your flow.
Which provenance is captured automatically?
All UTM parameters (source, medium, campaign, content, term), the referrer, the full landing-page URL, the assigned label and basic device information. You do not have to set anything up manually for this: as soon as a visitor arrives via an ad or link, that context travels along into the request and the audit trail.
How quickly am I live?
An embedded form or hosted landing page is often live within an hour: choose a template, set your house style and fields, place the opt-in text and publish. Activating your own subdomain takes a little more time because of DNS propagation, usually within a day.
Rather build it yourself via the API?
In the documentation you will find the form schema, the embed options, the consent field model and example code to connect your own form.
Requests under your own brand
Collecting at the source pays off
Collect requests under your own brand
Book a demo and see how forms and landing pages deliver consent and provenance by default.