Also known as: Inline Frame, Embedded Frame, iFrame Embed
Iframe Integration is the use of the HTML `<iframe>` (inline frame) element to embed one web document inside another. For a partner, it means dropping a broker-hosted page — a live pricing table, a registration form, a calculator, or a widget — into your own site so the visitor interacts with it without ever leaving your page.
The embedded document runs in its own browsing context: it loads independently, keeps its own scripts and styles, and is isolated from your page's code. You control where it sits and how big it is; the broker controls what it contains. Because the broker serves the content, they can bake your tracking ID straight into the embedded form's URL.
That isolation is the point. A visitor filling in a broker's embedded 1-step registration form is technically submitting to the broker's server — with full data security and compliance handled on the broker's side — while feeling like they never left your "Quick Start" page. When the form submits, the broker attributes the new account to your ID.
The trade-offs are performance and security: each iframe is a separate page load, and browsers restrict cross-origin iframes (via `X-Frame-Options` and Content-Security-Policy) so not every page can be embedded. Search engines also credit the framed content to its source domain, not yours.
You place an `<iframe src="...">` tag on your page pointing at a broker-hosted URL that already includes your affiliate parameter (for example `.../register?ib=12345`). The browser fetches that URL in a nested browsing context and renders it inside the frame's box.
The framed page and your page are separate origins, so they cannot read each other's data — a security boundary enforced by the same-origin policy. The broker can still attribute the lead because the tracking ID lives in the src URL and any cookie is set on the broker's own domain when the form submits.
Whether a page can be framed at all is decided by the source server, not you. If the broker sends `X-Frame-Options: DENY` or a restrictive `frame-ancestors` CSP directive, the iframe stays blank — which is why brokers publish specific embeddable URLs for partners. Your site must also serve over HTTPS, or browsers will block mixed or insecure framed content.
Take the broker's partner-approved iframe URL (form, widget, or calculator) that already carries your affiliate/IB ID.
Add `<iframe src="...">` into a custom-HTML block on the target page, setting width, height, and a title for accessibility.
Serve your site over HTTPS so browsers don't block the framed broker content as mixed content.
Use a fluid width and an aspect-ratio or JS resize so the frame reflows cleanly on mobile.
Submit a test registration and confirm it lands in your partner dashboard with the correct tracking ID.
Why it matters for partnership: Iframes let you host a broker's registration form or tools inside your own funnel, so visitors convert without a jarring redirect — and because the embed carries your tracking ID, every sign-up from it is attributed to you.
An IB builds a "Quick Start" landing page and embeds Exness's 1-step registration form via an iframe whose src carries the IB's partner ID. A visitor completes the form without ever leaving the page; the account is created on Exness's servers and auto-attributed to the IB. Because the embed cut the usual redirect step, the IB measures a noticeably higher form-completion rate than on its plain "Open account" button.
| Attribute | Iframe embed | Redirect link |
|---|---|---|
| User stays on your site | Yes | No |
| Attribution method | ID in src URL | ID in redirect URL |
| Page-speed impact | Higher (extra load) | Lower |
| Blocked by X-Frame-Options? | Possible | No |
| SEO credit for content | Source domain | N/A |
Always serve the host page over HTTPS and use only the broker's officially provided embeddable URL — arbitrary broker pages will refuse to load in an iframe because of their X-Frame-Options or CSP settings.
Stacking several heavy iframes on one page balloons load time and tanks Core Web Vitals, while a fixed-size frame that isn't made responsive breaks the layout on mobile — where most of your traffic actually is.
Search engines usually credit framed content to its source domain, not yours, so an iframe adds little ranking value. Use iframes for user experience and conversion, and rank with your own on-page content.
The broker's server likely sends X-Frame-Options: DENY or a restrictive Content-Security-Policy that blocks framing. Use only the embeddable URLs the broker provides to partners.
Very little. You paste a single `<iframe>` tag into a custom-HTML block, then adjust width and height. Getting it responsive is the only fiddly part.
Yes — the form submits to the broker's own server across an origin boundary your page can't read. Data handling and compliance sit with the broker, not you.
It can, because each iframe is a separate page load. Lazy-load it, limit the number per page, and keep non-critical embeds below the fold.
Your affiliate or IB ID must be present in the iframe's src URL. Run one test registration and confirm it appears in your partner dashboard before going live.