- How do I submit a webform using API or Postman?
Follow these steps to submit your webform programmatically:
Retrieve landing page IDs
Get the pageId, siteId, and parentPageId from your webform.
Add database and publish
Make sure your webform is associated with a database and the landing page is published. Copy the webform URL (for example: https://www.pages08.net/example-page/).
Set up your API request in Postman
Method: POST
URL: Your webform URL
Body: x-www-form-urlencoded
Include: formSourceName, siteId, pageId, parentPageId, and any other required form fieldsSubmit your request
Click Send in Postman.
Verify submission
Check the database to confirm the record was inserted.
Common mistake: Omitting siteId, pageId, or parentPageId prevents record insertion. The API will still return 200 OK with "Your request has been processed" even if the record is not inserted.
- Why isn't my custom confirmation page showing when I use reCAPTCHA with Double Opt-In?
With Double Opt-In, Acoustic automatically generates a confirmation page. Imported custom forms don't fully trigger the double opt-in flow, so the system defaults to a basic confirmation page.
How to fix it:
- Use an Acoustic standard form as the base.
- Hide the system-generated form with CSS.
- Place your custom HTML form above it.
- Ensure your form fields match Acoustic's field names/IDs.
- Set the standard form as default and update its confirmation page to your custom page.
What this achieves: End users see your custom form with reCAPTCHA and are routed to your custom confirmation page while maintaining Double Opt-In functionality.
- Why is my Meta Description missing from my published landing page?
When using custom HTML in your landing page, the Meta Description entered in the Page Information section may not appear in the published page source. This happens because custom HTML overrides the default behavior.
The solution:
Add the Meta Description dynamically using a script in your landing page's body tag.
Example:
<meta name="description" content="Learn more."> <script> // Insert meta dynamically let head = document.getElementsByTagName('HEAD')[0]; let meta = document.createElement('meta'); meta.name = 'description'; meta.content = 'Description text goes here'; head.appendChild(meta); </script>How to add the script:
Go to your landing page → Source View → paste the script inside the
<body>section → Publish the page.Verify the Meta Description:
Open the landing page in your browser. Right-click → Inspect → check inside the
<head>section. You should now see:<meta name="description" content="Description text goes here">This ensures your Meta Description tag is properly added to the published landing page even with custom HTML.
- What are better alternatives for tracking form submissions?
Option 1: Hidden field with JavaScript
Add a hidden date field to each form and auto-populate it with the submission date.
Option 2: Profile updates via a program
Use a program to update a database field when forms are submitted.
Both approaches create a dedicated "Last Form Submission Date" field you can segment on more accurately.
- Can I use scoring or lead alerts with Forms Composer?
No, Forms Composer does not directly support scoring or lead alerts.
Workaround:
You can replicate this functionality using a program:
- Create a program with the entry criteria set to "submitted web form."
- Select the relevant web form and configure the program to immediately exit the contact.
- In the lead alert section, use the "enters program" option to trigger the alert.
- Why am I getting a "Please add a submit tag to your form" error?
This error appears because one or more
<form>tags in your landing page HTML do not include a submit button. Without a submit button, users cannot submit the form.How to fix it:
- Review your landing page HTML code.
- For each
<form>tag, ensure it contains a submit element:<input type="submit">or<button type="submit">. - Place the submit tag before the closing
</form>tag.
Example:
<form action="/submit-form" method="post"> <input type="text" name="firstName" /> <input type="email" name="email" /> <input type="submit" value="Submit" /> </form>
Tip: If your page has multiple forms, check each one individually to make sure a submit button is present.
- Why don't One-way opt-in SMS campaigns appear in Forms Composer?
One-way opt-in SMS campaigns don't appear in Forms Composer because it only supports campaigns that require explicit confirmation—such as Two-way or Double opt-in campaigns.
Resolution:
Use a Two-way or Double opt-in campaign if you want SMS opt-ins collected via forms.
One-way opt-in campaigns must be handled through bulk import or API, since they don't require explicit confirmation and cannot be selected in Forms Composer.
This ensures all SMS opt-ins collected via forms are explicit and compliant.