Author Sources and Website Embeds

Use Author Sources when a reader submits a form on an author-owned website page and ReviewLead should store the lead, source attribution, deliver an optional requested resource, or send a separate optional Review & Lead invitation.

KDP-sensitive reminder: do not place ReviewLead URLs, public keys, source keys, or thin email-capture form links directly inside Kindle book content. Use soft, optional wording and keep review requests separate from reader resources.

What Author Sources Do

An Author Source represents one page or form on the author's website, for example a book-specific reader bonus page, newsletter signup page, contact form, or other website form.

The author website page should contain real page content: book context, author branding, what the reader is requesting, and consent/privacy language.
If the page asks for name, email, or other personal information, do not treat it as automatically safe for direct Kindle-book linking. KDP guidance restricts links to web forms that request customer information.
ReviewLead works behind the page by receiving the form submission, validating the source, storing the lead, and routing according to the selected follow-up action.

Policy-Safe Wording for KDP Authors

Use specific, reader-friendly terms instead of vague phrases like companion resource or salesy phrases like claim your bonus. For a health-related book, a clearer label is Printable Trackers and Reader Tools.

Safer examples

Optional printable trackers and reader tools are available on the author website.
Visit the author website for printable trackers, reader tools, book updates, and related notes.
Optional: enter your details if you would like the author to email printable trackers and reader updates. No review is required, expected, or rewarded.

Avoid

Claim your bonus by entering your email.
Enter your email to unlock the reader tools.
Leave a review to receive the bonus.
Scan this Kindle book QR code to submit your email.

Create an Author Source

In ReviewLead, open Author Sources.
Click Add Author Source.
Enter a clear Source Name, such as Book A Reader Bonus Page.
Confirm the generated Source Key. It should be lowercase and page-specific, such as book-a-reader-bonus.
Choose the Source Type: Reader Bonus Resource, Newsletter Signup, Contact Form, or Other Website Form.
Choose the Follow-up Action: Capture lead only, Deliver resource, Send Review & Lead funnel invitation, or both. Resource delivery requires an active Lead Capture funnel with a configured resource and email-link delivery. Review invitations require an active Review & Lead funnel. They are not tied to the optional marketing checkbox on the author form.
Enter an HTTPS author website page URL in Website URL. ReviewLead authorizes the exact registered hostname, treats www as equivalent, and accepts any path on that host. Register subdomains separately.
Set the source to Active when the author website page is ready to receive submissions.

Public Key, Source Key, and Embed Snippet

Public Key: identifies the Author Source record without requiring seller login. It is copied from the Author Source card and included as a hidden form field named public_key.

Source Key: identifies the specific page/form route for that seller. It is included as a hidden form field named source_key.

Source URL: should be the reader's live author-owned page URL. It is included as source_url so the API can validate the hostname when browser headers are missing.

Click Embed Snippet on the Author Source card to copy one integration option. The visible reader fields are name, email, required consent, optional marketing consent, and the submit button.

Which Snippet Should You Use?

Choose one integration path per author website page. Do not paste multiple form snippets on the same page.

Existing designed form integration: use this when the author website already has a designed form and you only need to connect that form to ReviewLead. Add the hidden fields, make sure the form has the required ID, and paste the generated JavaScript submit handler after the form.
WordPress, Hostinger, Webflow, Framer, Carrd, or plain HTML: use the JavaScript Embed in a Custom HTML, Embed Code, or Code Embed block where the form should appear. This creates the visible form for the author.
Next.js / React / Vercel: use the React component snippet when a developer, technical website manager, or AI website builder can create a component file, import it, and render it on the author website page.
Advanced developer option - Custom API integration example: use this only as an example payload for custom backend, serverless, or fully custom form handlers. It is not a complete drop-in form.

Where to Put the Code on the Website

Put the snippet on the author-owned page where readers are supposed to submit the form. Do not put the keys or ReviewLead API URL inside the book text. If this page requests name/email, avoid presenting it as a direct Kindle-book link; use it for author website traffic, launch emails, ARC campaigns, newsletters, and other reader campaigns where consent is clear.

WordPress: add a Custom HTML block on the specific page and paste the JavaScript embed. If WordPress strips the script, use an admin account with permission to add unfiltered HTML or a trusted code snippet plugin such as WPCode.
Hostinger Website Builder: add an Embed Code element on the specific page, click Enter code, paste the snippet, save, and update/publish the website. Use page-level Embed Code for the visible form, not only a site-wide head script field.
Webflow: add a Code Embed element where the form should appear, paste the snippet, save, and publish. Webflow custom code embeds require an eligible paid site or workspace plan.
Framer: use the Embed component for page-level embed code, or use page-specific Custom Code when the form is already built elsewhere and only the script handler is needed.
Carrd: requires Pro Standard or higher for custom code. Add an Embed element, set Type to Code, choose inline placement for a visible form, paste the snippet, and publish.
Shopify: use a custom page template, Custom Liquid section, or theme developer workflow to place the form on the intended page. Shopify themes may need the HTML and JavaScript split into the theme's supported Liquid/custom code structure.
Vercel, Netlify, and custom sites: paste the generated JavaScript embed into the page component or static HTML. If the site already has its own form, use the API payload example and send a JSON POST to ReviewLead.

Testing Checklist

Publish the author website page after pasting the snippet.
Open the live page in a normal browser tab, not only the website builder preview.
Submit a test name and email through the visible form.
In ReviewLead, open Leads and confirm the lead appears with Author Source attribution.
In Author Sources, confirm Last Submission updated for that source.
After submit, the reader gets a confirm your email message, not an immediate resource download and not a Continue button. Reminders follow if they do not confirm.
After they confirm, they open the mapped Review or Lead funnel with name and email filled in. Resource download still happens on the funnel thank-you step, then the existing download-link email is sent. ReviewLead never auto-redirects from the author website.
If submission fails, confirm the Author Source is Active, the website URL domain matches the live page domain, the copied public_key and source_key were not edited, and the page uses HTTPS.

Source Statuses and Lifecycle

Draft: configure and copy integrations; public submissions are rejected.
Active: accepts validated submissions and queues configured actions.
Paused: stops new submissions while preserving configuration and history.
Archived: is the required first step before deleting a used source. Historical Leads and Analytics keep immutable source attribution after deletion.
A linked funnel cannot be changed or deleted while an active source depends on it. Remap or pause the source first; remove every source reference before deleting the funnel.
A website form submission proves the reader came through a configured source page. It does not prove they read the book.