Appearance
Submissions & outputs
Submission outputs define what happens when a user clicks a submit button: PDF quotation, confirmation email, webhook POST, and/or postMessage to the parent page. Outputs are linked to templates for PDF layout.
Where to configure
Manager → Configurations → product → Submission & tracking → Data Submissions
Concepts
| Term | Description |
|---|---|
| Submission output | A named configuration grouping one template and multiple buttons |
| Template | PDF/email layout (managed under Settings → Templates) |
| Button | A labeled submit action the user sees on the info step |
| Triggers | Per-button toggles: PDF, email, webhook, postMessage |
Each product can reference an output via output_id on the cart/submission config.
Button triggers
| Toggle | Effect |
|---|---|
| Generate quotation PDF | Creates landing page URL returned in API response |
| Send confirmation email | Email to customer with quotation link |
| POST to a URL | Webhook JSON POST |
| PostMessage | postMessage to parent window |
Buttons can mix triggers. Example integrations:
- Quote request: PDF + email + webhook to CRM
- Add to cart: webhook + postMessage only (no contact fields)
- Iframe thank-you redirect: postMessage only
No-contact / cart buttons
When a button has PDF and email disabled, the submit flow skips contact validation and quotation creation. It still fires webhooks and postMessage with cart.action payloads.
Use this for “Add to cart” or “Send configuration to ERP” without collecting name/email.
Client submit payload
On submit, the form sends (among other fields):
javascript
{
buttonId: '...',
output_id: '...',
templateId: '...',
items: [ /* cart configurations */ ],
first_name, last_name, email, phone, // when required
total_price,
product_id,
dealer_id,
language
}The API resolves the button from output_id + buttonId and runs the enabled triggers.
Templates & JavaScript embed
Templates control PDF content. The configurator JavaScript embed (inject) does not load a separate template file on the host site — the live UI comes from Configurator styles in Manager.
Connection flow:
- User configures product in inject/iframe UI (styles from Manager).
- User reaches info step and clicks a button defined in Data Submissions.
- Client calls add-quote API with
output_id,buttonId,templateId. - Server generates PDF using the template linked to the output (if enabled).
- Webhook/postMessage fire according to button toggles.
For GTM analytics on the host page, use inject mode + Analytics & GTM.
Finished message
Optional custom text shown after submit (finished_message) can be set on the button or output.