Enter app

Run it after launch

The forms are published and submissions are arriving. This is the part nobody writes a tutorial for: what to look at, what to ignore, and what actually needs you.

Steps
5
Plan
Any
Output
—
Mode
Console
The scenario
Two or three forms live on a small business site, quietly collecting. Somebody checks in once a week and wants to know in thirty seconds whether anything is wrong.
What you end up with
A reliable weekly routine, and the confidence to tell a state that needs you from one that does not.
You need
  • A form that has received at least one submission
  1. Connections

    Read the Connections home in thirty seconds

    The Connections home: the summary line above a grid of connection cards, each drawing its website, Webtzm and its Google output as a route with its state, what it can do and where it sends, and a footer with the one action each state needs; the Webtzm helper in the panel beside them. Open full size
    A card per connection. Its Needs review state is the only part demanding action, and its footer names the action.
    • The summary line above the cards — how many connections you have, how many need review and how many are paused.
    • Each card's state — Delivered, In delivery, Ready or Paused — and when it last delivered to its Google output.
    • Needs review on a card — the only state that ever needs you. Its footer names the one action that goes with it: Allow website, Reconnect Google or Review. Everything else is information.

    If no card reads Needs review, you are done. Close the tab. Account shows this month's accepted submissions against your plan's limit, and Analytics has the delivery chart and the status breakdown when you want more.

  2. Analytics

    Tell a retry from a failure

    The Submissions section of Analytics with a search box and form and status filters above rows in Delivered, In delivery and Needs review, with a Mark reviewed action on the row that needs review. Open full size
    One list, filterable by form and status. Only a row that needs review carries an action.
    StateWhat it meansWhat you do
    DeliveredThe record reached Google.Nothing.
    In deliveryAccepted, on its way.Nothing. Wait.
    Retry scheduledA temporary error, and another automatic attempt is already booked.Usually nothing. Fix a visible Google connection problem if there is one.
    Needs reviewDelivery stopped, with no further automatic attempt owed.Fix the cause, then Send again — or Mark reviewed if no retry can help.
    A submission that is retrying has not failed

    This is the single most useful distinction on the page. Retry scheduled means the work is still in hand. Needs review means it has stopped and is waiting for you. Treating the first as the second is how people waste an afternoon on a problem that was fixing itself.

    Behind those states, for delivery to your Sheet: a customer-specific temporary failure gets another automatic attempt while fewer than five customer-specific attempts have been made and the workspace still has retry allowance. Google-wide throttling and outages use a separate recovery window, so one provider incident does not consume your allowance.

  3. Analytics

    Open a submission that needs review

    A Needs review submission opened in place with View details, showing the reason Google gave, what it means for the record, a reference to quote with a Copy reference button, and a Mark reviewed action. Open full size
    View details opens the reason behind the state in place, and a reference you can quote to support.
    • Send again hands the same submission back to delivery. It does not create a duplicate record.
    • Mark reviewed is for the cases a retry cannot fix — it clears the item without pretending it was delivered.
    • A rejected submission is different, and has no retry: validation, verification and policy rejections never created an accepted submission in the first place. Correct the cause and let the visitor submit again.
  4. Connections

    Pause, change or remove a connection

    The Basics section of a paused connection's Setup: its name, its website, the switch that holds submissions from a website not on the list, and its status, Paused, with Resume. Open full size
    Open a card, then Setup in the panel: everything about the connection is there, section by section, and each saves as you change it.
    • Pause, under Status in the connection's Basics, when a campaign ends. The connection stops accepting and the form on your page starts saying so; Resume turns it back on.
    • Change anything else in the same Setup. If you change a setting the published form carries, Setup says the page needs the new code: copy it again from Get the form code and replace what you published.
    • Remove, at the end of Setup, when it is finished for good. What it already delivered stays in Google, and a removed connection frees an active slot on your plan.
  5. Account › Billing

    Know what your plan actually limits

    The billing view on the Free plan: the Free plan active status, the price, the Upgrade to Pro trial line, and the Free, Pro and Pro Scale plans side by side with their active-connection and monthly-submission limits. Open full size
    Billing is the account's source of truth for the plan, the interval, and the next charge or plan-change date.
    LimitFreeProPro Scale
    Active form connections350500
    Accepted submissions a month10010,000100,000
    OutputsSheet rowSheet row, Doc, PDF, JSON or emailAll Pro outputs
    What a connection can doAdd rowsAdd, change, remove or read rowsAdd, change, remove or read rows
    Monthly file budgetNo file fields10 GB50 GB

    Allowed-domain protection, anti-spam checks, duplicate protection, automatic delivery retries and delivery status are included on every plan, Free included.

    Checkout is hosted by Stripe

    Payment details are collected by Stripe, and Webtzm does not store full card numbers. Returning from Checkout does not grant Pro by itself — the Billing view updates once Webtzm has received and verified the billing event, which takes a moment. Do not start a second Checkout for the same purchase.

A weekly routine that takes a minute

  1. Open the Connections home and look for a card that reads Needs review. If there is none, stop here.
  2. If there is one, open Analytics, filter to Needs review, and read the first one's details.
  3. Fix the cause it names — most often a Google connection that was revoked, or an output that was deleted or moved.
  4. Send again, or Mark reviewed where nothing can be resent.
  5. Once a month, glance at Monthly accepted submissions under Account against your plan limit.
Turn on failure alerts and stop checking

With Email me when a delivery needs review switched on, under Delivery and alerts in each connection's Advanced, Webtzm emails you when delivery needs review. The routine above then becomes something you do when you get an email, rather than something you have to remember.

Where to go next

Something missing or wrong on this page? Tell support.