Embed & your data
How the embed integrates with your site and how to get your lead data out.
The embed is the integration
Mach Five Magnet doesn’t ask your site to talk to an API. The integration is the snippet itself:
<script src="https://machfivemagnet-saas.onrender.com/m5t/v5/coreSnippet?appguid=YOUR-MAGNET-ID" async></script>
When a visitor loads your page, the platform serves that script with your magnet’s current configuration (appearance, welcome hub, flows, A/B variants) already inside it. Save a change in the app and the next page load has it. There are no API keys on the page, no build step, and nothing to redeploy.
A few properties worth knowing:
- Domain allow-list. The script is only served to domains listed on the magnet, enforced server-side. A copied snippet does nothing on a domain you haven’t approved.
- Isolated rendering. The widget renders in a shadow root: your site’s CSS can’t break the magnet, and the magnet’s CSS can’t leak into your site.
- Nothing captured before completion. While a visitor is mid-conversation the script sends anonymous telemetry only (session id, step position, which CTA was picked). Answer values are sent once, when the visitor completes.
- Inline format additionally needs a mount point: place
<div data-m5m-inline></div>where the card should render.
Getting your data out
CRM sync
Leads sync to HubSpot, Salesforce, Zoho CRM, or HighLevel with the conversation attached, and qualified leads update their status in the CRM. Setup for each is under Integrations.
Webhook
Every captured and qualified lead is sent to an endpoint you choose as signed JSON, which is also how Zapier connects. Set it up in the app under Settings, then Notifications.
CSV export
The lead inbox has an Export CSV button. It exports the leads in your current filter (All, or a single status) with these columns:
first_name, last_name, email, phone, company, product_interest, lead_source, utm_source, utm_medium, utm_campaign, gclid, status
That file imports cleanly into a spreadsheet or a CRM’s lead-import tool.
Attribution on every lead
Each captured lead carries the campaign data the embed read from the visitor’s landing URL:
| Field | What it is |
|---|---|
utm_source, utm_medium, utm_campaign | Standard campaign parameters. |
gclid, gbraid, wbraid | Google Ads click identifiers. A lead with one of these came from a paid click. |
utm_term, utm_content | Also captured; stored as tags on the lead. |
The lead’s detail drawer shows its attribution, and leads from paid clicks are badged. The same fields drive the dashboard’s leads-by-campaign report and the ad-performance view.
Everything the visitor answered
Flow answers land on the lead as named fields (whatever step_columns you mapped in the flow builder), visible in the detail drawer. Leads also record which magnet captured them and, when an experiment is running, which A/B variant the visitor saw.
Roadmap
Note
Everything below is planned, not shipped.
- Public REST API: programmatic access to leads, magnets, and analytics.
If this would unblock you, tell us. It helps us order the list.