Installing JunkGate

1. Add the snippet

Paste this just before the closing </body> tag on the page with your contact form, using the site key from your dashboard.

<script src="https://junkgate.com/jg.js"
        data-key="YOUR_SITE_KEY"></script>

That is the whole installation. JunkGate finds the forms on the page and takes care of each submission as it is sent.

2. Confirm it is working

Submit your own form once. It should behave exactly as it always has. Open your dashboard and the submission will be listed with what happened to it.

Your site starts in watch-only, so nothing is held. You are watching the filter make decisions, not letting it act on them yet.

3. Review, release, and switch protection on

The control loop after installation, and there is no step in it we take for you.

Watch the enquiries arrive in your dashboard with what would have happened to each one. Nothing is held yet.
Switch protection on when it looks right on your own traffic.
Release anything kept out in one click. The original notification goes out again, exactly as it was written.
Mark junk that got through, and JunkGate takes that correction into account on your site from then on.

What it does, and what bounds each of the two mistakes: what it does.

Options

Attribute	What it does
`data-key`	Required. Your site key.
`data-forms`	A CSS selector, if you only want specific forms protected. Defaults to every form on the page.
`data-jg-success`	Put this on a form, pointing at your own success element, and we will show yours instead of a default message.

Protecting your inbox as well

Contact forms are not the only way junk arrives. Each site can also have a private forwarding address.

Copy the forwarding address from your dashboard.
Add one forwarding rule in your own mail client pointing at it.
Genuine mail arrives as normal. Junk waits in your dashboard.

We never ask for your mailbox password, and we never connect to your mail account. You forward to us, which means you stay in control and can stop it at any moment by deleting that one rule.

Straight about where this one is up to: the mailbox side is built and is not switched on yet, so the forwarding address is not in dashboards today. The contact form protection above is live now. We will say so here on the day that changes, rather than claiming it early.

Sending your own submissions

If you run a custom backend rather than an HTML form, post to the endpoint directly and use the deliver field in the response to decide what to do.

POST https://junkgate.com/v1/submit
Content-Type: application/json

{
  "key":     "YOUR_SITE_KEY",
  "name":    "Sarah Nguyen",
  "email":   "sarah@example.com",
  "subject": "Quote request",
  "message": "Do you service commercial vans?"
}

The response is always a 200, even if something on our side went wrong, because a problem of ours must never surface as a broken form on your site.

{ "ok": true, "id": "…", "deliver": true }