IntegrationsWebsite snippet
Website snippet + Monthwrap

Social & websites reporting

Website form leads in your client report.

Use the Monthwrap website snippet to capture supported form submissions from sites that do not use the WordPress plugin.

AvailableSite installation
Inside the monthly reportSample data
Northside Digital / Parkside Studio

A form submission, kept in context

Recorded form leads24Illustrative monthly count
Contact detailEmail or phoneAt least one is required
SourceWebsite formKept with the lead record
Visitor submitsQuote form
Snippet capturesContact fields
Client receivesLead record
Report explainsMonthly result

A recorded submit event is not confirmation of form delivery, a qualified opportunity or a completed booking.

Fictional agency example · a supported website form

Website snippet, at a glance.

Connect with
Site installationAdd the client’s snippet to the website and check that its forms are being captured.
Updates
Supported form submissions are sent when the form event occurs.
Earlier months
Capture starts after installation. Earlier form submissions are not reconstructed.
In your report
Supported website form leads.

Built around your client’s questions

The inquiry should not disappear into a separate inbox.

For agencies supporting custom websites and non-WordPress sites.

A brochure site or custom landing page can generate valuable inquiries without a CRM connection. If the agency only reports traffic, those contacts can disappear from the monthly conversation. The website snippet offers a lightweight way to record supported form submissions against the correct client.

Add the client’s snippet to the site, test the forms visitors use and bring the captured leads into the report alongside traffic and campaign results. The snippet records contact fields and form context; it is not a replacement for the website’s form handler, inbox or booking system. Keep qualification and sales outcomes separate.

Choose the numbers that matter

What Website snippet
brings to the report.

Supported website form leads. Choose the relevant figures, add comparisons where the data supports them, and explain what changed.

01

Supported form submissions

The snippet observes browser form-submit events containing an email address or phone number. Test each important form because custom JavaScript widgets and embedded forms may behave differently.

02

Contact details

A lead can include the available name, email and phone fields. The capture is intentionally limited rather than copying everything a visitor enters into the page.

03

Form and page context

The form name and page address help the agency understand where the inquiry originated. Use that context when reviewing records without exposing unnecessary personal information in the report.

04

Source check-ins

The snippet checks in when visitors load the site, helping indicate that it is installed. A check-in is not an external uptime measurement or evidence that every form was delivered successfully.

For your next client report

A custom service website

Add form leads to a report that already contains website traffic and search results. Explain the difference between visits, submitted inquiries and bookings confirmed by the business.

Arrange the report in your own layout

Read it from the client’s side

See the complete
local growth report.

A full fictional agency report, with the work delivered, the numbers behind it and the plan for next month. Use its structure to plan your own mix of sources and client results.

Open the sample report

Make the connection

From Website snippet
to the right client.

Add the client’s snippet to the website and check that its forms are being captured.

Connection methodSite installationAvailabilityAvailableYour connected account’s API permissions and plan apply.
  1. 01

    Create the website source

    Add the correct client website in Monthwrap and use the snippet supplied for that site. The source is associated with the configured website address.

  2. 02

    Install it on the site

    Add the supplied script through the website’s supported code-insertion route. Confirm that it appears on the pages containing the forms you intend to record.

  3. 03

    Test a real form path

    Submit an agreed test inquiry containing contact details, then confirm it appears in the correct client workspace. Also verify the form’s own delivery path independently.

Know what each
number means.

Browser form coverage varies

A cross-domain embedded form or a custom widget may not expose a normal submit event to the page. Use a supported integration or webhook when the snippet cannot observe the form reliably.

Inquiry does not mean sale

The snippet does not confirm email delivery, qualify the contact or know whether a job was booked. Review spam and repeated contacts before using the records in a client summary.

Before you connect

A few useful
answers.

Is the snippet a replacement for the WordPress plugin?

No. The WordPress plugin captures supported website work as well as form leads. The snippet is a narrower option for supported form submissions on sites without that plugin.

Does it collect passwords or full form messages?

The snippet skips forms containing password fields and looks for contact information rather than copying all form content. Review the client’s form setup and privacy disclosures before enabling collection.

Can I use a webhook for an unsupported form?

Yes. A form backend or automation can send an agreed lead payload to the client’s Monthwrap webhook. That provides a separate, testable route when browser-side form capture is not suitable.

Start with your next client report

The data has a source.
The story has your name.

Bring your sources together, choose your layout and add the context your client needs.

Start free trial

14-day free trial. No card needed.

Make yourself comfortableMore about cookies and browser storage