Author Sources and Website Embeds

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.

Create an Author Source

1. In ReviewLead, open Author Sources.
2. Click Add Author Source.
3. Enter a clear Source Name, such as Book A Reader Bonus Page.
4. Confirm the generated Source Key. It should be lowercase and page-specific, such as book-a-reader-bonus.
5. Choose the Source Type: Reader Bonus Resource, Newsletter Signup, Contact Form, or Other Website Form.
6. Choose the Follow-up Action. Use Capture lead only to store the lead without a target funnel. Use Send Review & Lead Funnel link only when you also select an active Review & Lead funnel.
7. Enter the exact HTTPS author website page URL in Website URL. ReviewLead derives the allowed domain from this URL and rejects submissions from a different domain.
8. Set the source to Active when the author website page is ready to receive submissions.

Public Key, Source Key, and Embed Snippet

Which Snippet Should You Use?

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

1. 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.
2. 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.
3. 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 book page.
4. 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

1. Publish the author website page after pasting the snippet.
2. Open the live page in a normal browser tab, not only the website builder preview.
3. Submit a test name and email through the visible form.
4. In ReviewLead, open Leads and confirm the lead appears with Author Source attribution.
5. In Author Sources, confirm Last Submission updated for that source.
6. 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.

Current Limits and Pending Work

• Real external-site testing still requires a live author website page. The in-app snippet generator has been tested, but the full website-to-ReviewLead submission should be verified once the page is ready.
• Automated follow-up email sending for Send Review & Lead Funnel link is still a pending development phase. Until that is complete, the capture route can store leads and return routing information, but the automated email workflow is not the final production behavior.
• A website form submission proves the reader came through a configured source page. It does not prove they read the book.