Skip to main content

Lead metadata

Attach your own key/value data to a demo session — campaign attribution, CRM record ids, partner codes. It appears on the lead in the Showdini dashboard, in the new-lead email, in the PDF report, and in the lead.report_generated webhook payload under metadata.

With the embed widget​

Pass a metadata object. No prefix needed.

<script>
  Showdini.init({
    demoId: "YOUR_DEMO_ID",
    container: "#showdini-demo",
    metadata: { crm_id: "8842", partner: "acme" },
  });
</script>

To pick up campaign params from the page the widget is embedded on, opt in with forwardPageParams. Only the well-known tracking params below are read, and anything you pass in metadata explicitly takes precedence.

Showdini.init({
  demoId: "YOUR_DEMO_ID",
  container: "#showdini-demo",
  forwardPageParams: true,
});

On the demo URL​

In an iframe or a plain link, prefix each param with meta_:

https://demo.showdini.ai/start/YOUR_DEMO_ID?embedded=true&meta_crm_id=8842&meta_partner=acme

That arrives as { "crm_id": "8842", "partner": "acme" } — the prefix is stripped.

Tracking params need no prefix​

Ad platforms and email tools append these to your destination URL themselves, so they are captured as-is:

utm_source, utm_medium, utm_campaign, utm_term, utm_content, gclid, fbclid, msclkid, ttclid, li_fat_id

A link you have already tagged for a campaign works untouched:

https://demo.showdini.ai/start/YOUR_DEMO_ID?utm_source=google&utm_campaign=spring-launch

Any other unprefixed param is ignored. If both meta_utm_source and a bare utm_source are present, the prefixed one wins.

Limits​

Metadata is capped at 20 keys, 64 characters per key, and 512 characters per value. Keys may contain letters, numbers, _, . and -; other characters are stripped. Anything over the limits is dropped silently — a malformed tracking param will never stop a visitor from starting your demo.

Do not put sensitive personal data in metadata

Metadata is not intended for personal or confidential information.