Lockally

      Use your API key in the examples

      Replaces lk_live_… in the code samples on this site so you can copy and run them. It is stored in this browser only and is never sent anywhere, including to Ask AI.

      It will be visible on the page. Use a test key if you are sharing your screen or taking screenshots.

      Complaint handling

      A complaint is a recipient pressing “this is spam”. It is the most damaging signal in email, because it comes from the person you mailed rather than from a machine inferring something.

      What the platform does with one

      When a complaint report reaches us, in the standard ARF format that providers send:

      1. the complainant is suppressed immediately, with reason complaint;
      2. an existing unsubscribe or manual suppression for that address is upgraded to complaint, which is the stronger, reputation-bearing reason;
      3. a delivery event is recorded against the original message;
      4. it feeds the complaint rate the reputation engine watches.

      The ingestion endpoint is armed, signature-verified, and idempotent, so a provider re-sending a report does not double-count.

      What this means for you

      You cannot see your complaint rate here, and neither can we. The usual advice to keep complaints below 0.1% is correct and currently unverifiable on this platform.

      Complaints still cost you, whether or not we can see them. The provider sees them, and acts on them by foldering or rejecting your mail. The absence of a feedback loop removes your visibility, not the consequence.

      So watch the things that correlate instead. Your bounce rate, your provider-side reputation where you can read it, and your own engagement data. See Monitoring.

      Reducing complaints

      The mechanisms are the ordinary ones, and they are all upstream of us:

      • Make unsubscribing easier than complaining. A visible link and a working one-click header. Most spam-button presses are a failure to find the exit. See Unsubscribe management.
      • Send what was expected. A complaint usually means “I did not ask for this”, or “I asked for something else”.
      • Do not mail dormant recipients indefinitely. Engagement decays and complaints follow.
      • Keep the sender identity stable. A recognisable From name and address reduce the “who is this” reflex.

      Google is a special case

      Google does not operate a per-complaint feedback loop for ordinary senders, so Gmail complaints will never appear here however many enrolments complete. Postmaster Tools’ aggregate spam rate is the substitute, it is per domain, and you verify your own domain to read it. That makes it the one complaint signal available to you today, which is why Monitoring leans on it.

      If you run your own feedback loop

      If you are enrolled with a provider directly and can forward ARF reports, they can be delivered to our ingestion endpoint and are processed exactly as described above, or emailed to a collector address we will give you. Ask support: that configuration is per deployment rather than self-service.