Powerlily can collect leads through branded hosted forms, embedded forms, or a lightweight capture script attached to a form already on your website. Each method creates the same lead record while preserving its intake channel and available attribution.
Choose the right intake method
- Hosted form: use a permanent Powerlily form URL. This is the quickest option and uses the form’s selected theme.
- Embedded form: place the Powerlily form inside your website. Powerlily still renders and processes the form.
- Website capture: keep your existing website form and add Powerlily’s capture snippet. The script observes a normal form submission and sends recognised fields to Powerlily.
- REST API: use the API when a custom application or JavaScript-only form needs direct control over the submission.
Create a lead form
- Open Leads, then open the lead settings or forms area.
- Create a form and give it a clear internal name for the offer, territory, campaign, or website where it will be used.
- Choose the theme and customer-facing heading, instructions, confirmation copy, and other available presentation settings.
- Build the field list.
- Choose the routing rule.
- Activate the form when it is ready to receive submissions.
You can maintain several forms for different campaigns without forcing every lead through one question set.
Build the field list
Forms can combine standard contact fields with custom questions. Supported patterns include text and long-text answers, choices, statements, dates, currency, addresses, and file uploads.
- Enable only the fields that are useful for this intake path.
- Mark a field required when the submission should be rejected without it.
- Use clear labels, placeholders, and help text.
- Use conditional visibility to show follow-up questions only when an earlier answer makes them relevant.
- Review phone and consent wording before collecting permission for service or marketing text messages.
Powerlily stores a snapshot of the form’s question schema on each submitted lead. Renaming or rebuilding the form later does not rewrite the questions associated with older responses.
Configure routing
Each form can use one of three routing modes:
- Unassigned: create the lead without an owner for manual triage.
- Specific teammate: send every submission to one eligible user.
- Round robin: rotate submissions through a selected pool while retaining the next position between submissions.
Only users who can access leads should be included in the routing pool. Branch and record-scope rules still apply after assignment.
Use the hosted form
Open or copy the form’s permanent URL and test it in a private browser window. Confirm that required fields, conditional questions, theme, confirmation message, routing, and lead creation work as intended before sharing the link.
Embed the Powerlily form
Use the provided embed code when you want the Powerlily form to appear inside an existing page. The loader passes the page URL, referrer, UTM parameters, and supported advertising click identifiers into the embedded form so they can be stored with the lead.
After installation, test the embed at the desktop and mobile widths used by your website. If you listen for the embed’s completion event to trigger analytics, verify that the event fires only after a successful submission.
Capture an existing website form
Website capture is useful when your current form already has the correct design and behaviour. Add the capture snippet and token shown in Powerlily to the page containing the form.
The script recognises common name, email, phone, address, and message fields from their type, name, identifier, autocomplete value, label, or placeholder. For unusual markup, add the documented data-powerlily-field attribute to identify the field explicitly. Unmapped scalar fields can be retained as captured answers for review.
Important limitation
The capture script listens for a genuine browser form-submission event. Some single-page applications use a button click and send data entirely through custom JavaScript without submitting the form. Use the REST API for those forms if the capture script does not receive the event.
Attribution retained with the lead
Depending on the intake method and information available, Powerlily can retain:
- Landing page URL
- Referring page
- UTM campaign parameters
- Supported advertising click identifiers
- Lead form and form snapshot
- Intake channel
- The lead’s reported or assigned source
The intake channel and source are separate. For example, a lead may arrive through an embedded form while its source is recorded as Google Ads.
Spam, origin, and duplicate controls
- Hosted and embedded forms use a honeypot, with optional CAPTCHA protection when enabled and configured.
- Capture tokens identify the receiving company and can be restricted to approved website origins.
- Captured fields are bounded before storage.
- Rapid repeated capture submissions can be suppressed.
- A new lead whose email matches an existing company lead is flagged as a possible duplicate.
Test before launch
- Submit a real test from the final website page.
- Confirm the lead appears with the expected intake channel and source.
- Check the contact fields, custom answers, landing page, referrer, and campaign values.
- Confirm the correct owner, branch, and territory.
- Test validation, file uploads, confirmation behaviour, and consent capture where applicable.
- Submit twice and confirm your duplicate-handling behaviour is understandable to the sales team.
When a submission is missing
- Confirm the form is active and lead collection is enabled.
- Verify the embed or capture code is installed on the page being tested.
- Check the capture token and allowed origins.
- Use a genuine form submission rather than an unsupported JavaScript-only button flow.
- Review required fields, CAPTCHA configuration, and browser errors.
- Confirm the assigned user is still eligible to receive leads.
