WordPress Forms to Google Sheets & Excel – SheetLink

Changelog

1.15.0

• Fixed: partial refunds never reached your sheet, leaving the total overstated. WooCommerce only marks an order “refunded” when it is refunded in full, so a partial refund changed nothing SheetLink was listening for – the row kept the original amount and nothing indicated it was wrong. Because full refunds do change the status, the gap only ever swallowed partial ones. Refund rows now arrive for both, and carry the refunded amount, the running total refunded, the net amount kept, and whether the refund was partial.
• Fixed: the Airtable field-mapping help said the opposite of what happens. It stated that unmapped form fields “pass through”, which is only true when the mapping is empty or you have ticked the option below it. With a mapping set, unmapped fields are not sent – so people saw columns arrive blank in Airtable while the same submission was complete in their Google Sheet, and read it as data loss. Both the Airtable and Notion pages now say how many fields are mapped and state plainly that the rest are left out.
• Fixed: White-Label left the SheetLink name in the page headings. The menu was renamed but the Dashboard and Sync Rules headings still read “SheetLink Forms”, so a client handed a rebranded site saw the real product name at the top of the first page they opened.
• Fixed: the Post Type / ACF sync source was hard to find and its setup link went to the wrong page. “Configure rule” opened the dashboard rather than the rule editor, and the source was labelled “ACF: …” even on sites without ACF, so people looking for a post-type source concluded there wasn’t one. It now reads “Post Type: …” when ACF is not installed, and the button opens the rule editor.
• Fixed: the Retry Queue counted deliveries that had used all their attempts as still “pending retry”. They are now reported separately as failed permanently, since nothing further will be attempted for them.
• Fixed: retrying a failed delivery used the old receiver URL, even after you corrected it. The retry queue stored the address at the moment of failure and never re-read the rule, so the fix Webhook Health tells you to make had no effect – you corrected the URL, pressed Retry, and watched the same deliveries fail until they hit the retry limit. Retries now use the rule’s current receiver.
• Fixed: saving a rule with a non-Google Receiver URL looked like nothing happened. The error was displayed at the top of the page, above the fold on a long rule editor, so the Save button appeared dead. The message now also appears beside the button and highlights the field.
• Fixed: the Features screen and upgrade prompts still quoted the old add-on prices. Individual monthly prices and an “Agency Growth” tier that no longer exists were shown in the plugin – including on the message you see when a delivery is refused for lacking an add-on, which is the worst possible place to quote a price nobody can pay. Everything now names the plan that includes the feature, matching sheetlinkwp.com/pricing.
• Renamed in the interface: CRM Fan-Out is now Multi-CRM Routing, and Advanced Routing is now Multi-Destination Routing, matching the names used on the website and in your licence. Nothing to reconfigure – settings, licences and rules are unaffected.
• Added: the Features screen now shows Form Abandonment’s live state – how many partial submissions are held and when they will be sent – because they are deliberately held until a visitor has been inactive for 30 minutes, and a feature you cannot see working is indistinguishable from one that is broken.
• Added: Analytics now says it starts counting from the moment you switch it on, instead of showing a page of zeros on a site that has been taking submissions all day.
• Fixed: Two-Way Sync was sending SheetLink’s own bookkeeping columns back into WordPress. If your sheet had ever been written to by an out-of-date Apps Script, that script added _sheetlink_ping, rule_id and ping_at columns to it – and every later edit sent those columns back as though you had typed them. Updating the script stops new junk rows but cannot remove columns already created, so this kept happening after the apparent fix. Those three are now filtered out on the way in. Your attribution columns and the WooCommerce event marker still come through, since they describe the row rather than SheetLink’s plumbing.
• Fixed: an out-of-date Google Apps Script could add a junk row to your sheet every hour, and the health check called it healthy. Older versions of the script do not recognise SheetLink’s hourly health check and treat it as a form submission, so they append a row to your sheet roughly 720 times a month. Webhook Health only looked at whether the script replied, not what it said, so it reported the rule as reachable throughout. It now identifies which version of the script your sheet is running and tells you plainly when the script is writing those rows, with the exact steps to replace it. If you copied our template sheet, you are likely affected – check SheetLink Forms -> Webhook Health.
• Changed: a visitor’s campaign is now credited for 30 days instead of 90. When someone arrives from an ad, SheetLink remembers the campaign so a form filled in later still credits the click that earned it. Ninety days meant a single click could be credited for every lead from that browser for three months, including ones that later arrived from search or typed your address in directly – which quietly overstates what your ads produced. Thirty days matches Google Ads’ own default. Sites with long sales cycles can raise it (up to Google’s 90-day limit) with the sheetlink_attribution_ttl_days filter.
• Changed: on opt-in sites, click IDs and campaign data are now only recorded for visitors who accept marketing cookies. If your consent plugin is set to opt-in (the default in the EU and UK), a visitor who declines – or who has not answered the banner yet – now has their submission saved without attribution. Their click ID would otherwise have been written to your sheet and uploaded to Google as an offline conversion for advertising measurement they did not agree to. Expect fewer attributed conversions than leads on these sites: this is the change causing it, not a fault. Sites set to opt-out are unaffected except that an explicit refusal is now honoured, and sites with no consent plugin are unaffected entirely. Both behaviours are available via the sheetlink_attribution_consent filter, and the Conversions screen states which rule is in force on your site.
• Note for sites using a page cache: consent is now checked in the visitor’s own browser rather than trusted from the page HTML. This matters because caches share one stored copy across visitors, and often across query strings too – with W3TC’s “Cache URI with query string variables” enabled, a request for one campaign URL is served the copy generated for a different one. Without this, a page first generated for a visitor who had accepted could have caused the next visitor to be treated as having accepted as well.
• Added: campaign tracking now respects your cookie consent banner. If your site runs a consent plugin that supports the WordPress Consent API, the campaign cookie is only stored for visitors who accept marketing cookies, and it waits if they answer after the page loads. Sites with no consent plugin are unaffected and keep working exactly as before. Tracking parameters on the link a visitor actually clicked are still recorded either way – the consent step covers storing their campaign for later, not the link they arrived on. The Dashboard says which of these applies to your site.
• Fixed: UTM and click-ID attribution now reaches your sheet on the one-click Google connection. Visitor source was always captured and sent, but this connection method never created columns for it, so it was written nowhere – while the classic Apps Script method had always recorded it. A submission that arrives with utm_source, gclid and the rest now gets those columns, added only when a visit actually carries them, so a sheet never fills with empty attribution headers. If your sheet’s header was already fixed before this release, the columns are appended the next time a submission carries them.
• Fixed: choosing a Google Sheet did not stick. Creating or picking a sheet only filled in the form on screen – the choice was not saved until you pressed Save, and the next step in setup (creating a rule) navigated away first. The page then said “No sheet chosen yet” even though the spreadsheet existed in your Drive, and you had to pick it again. Creating or picking a sheet now saves it immediately.
• Fixed: saving the Google Sheets screen can no longer blank the destination sheet.
• Fixed: finishing setup the one-click way now counts as finishing setup. Only the wizard’s own last step marked a site as set up, and the one-click route deliberately ends on the Google Sheets screen instead – so a fully configured site stayed flagged as never-set-up, and the first-run wizard could reappear after an unrelated deactivate and reactivate months later. Creating a rule against a connected sheet now completes setup, whichever route you took to get there.
• Improved: the one-click Google route no longer loses your answers. It finishes on the Google Sheets screen rather than in the wizard, and now carries your form plugin and rule name with it, pre-filled, with a note explaining where you are. Previously both were discarded and you retyped them.
• Improved: the welcome screen described the manual Apps Script route as the only path. It now leads with one-click Google, with Apps Script as the optional alternative it actually is – and the progress step is labelled “Connect Google” rather than “Google Script”.
• Added: the Lead Inbox is now part of SheetLink Forms. Every submission becomes a lead you can own, answer and qualify – including the ones that never reached your sheet – with a response-time clock, notes, assignment and reports. It was previously a separate plugin; it is now built in, like every other add-on, and appears under SheetLink Forms when your licence includes it.
• If you installed the separate “SheetLink Lead Inbox” plugin, nothing breaks: SheetLink Forms leaves it in charge while it is active, and you can deactivate and delete it whenever you like. Your leads, notes and settings live in the same place either way and are not touched.
• Note on removal: deleting SheetLink Forms does not delete your leads. They are your records of real people you have spoken to, so they are kept unless you explicitly opt into deletion.

1.14.9

• Added: a way past “Approval required” when connecting Excel Online. Many Microsoft 365 organizations require an administrator to approve an app before anyone can connect it, so business users saw an approval wall instead of a sign-in screen with nothing on this end to do about it. The Excel Online page now provides a link you can send to whoever administers your Microsoft 365 tenant: they approve SheetLink Forms once for the whole organization, and everyone connects normally after that. They need no SheetLink licence and no login on your site.
• Improved: if Microsoft blocks the connection for that reason, the page you land on now explains why and carries the same link, instead of only saying sign-in did not complete.

1.14.8

• Renamed: the Multi-Node Routing add-on is now Multi-Destination Routing. Same add-on, same price, same settings – the new name says what it does: route one submission to several destinations with priority order and fallback webhooks. Nothing to reconfigure; existing licences and rules are unaffected.
• Improvement: the license key field no longer names a specific key format. Keys are validated by the licensing service, so paste whatever key your purchase email delivered.
• Documentation: clarified an internal code comment in the Excel destination about where the license gate is enforced.

1.14.7

• Security: the Two-Way Sync page displayed a live credential in plain text. The page printed the sync secret that authorises incoming sheet updates, so anyone who saw the screen – a screenshot, a support ticket, a screen-share – could post fabricated row updates to your site. It is no longer rendered; an administrator can reveal it on demand instead. If you have ever shared a screenshot of that page, contact support to reissue your licence key, which changes the secret.
• Fixed: “Recent incoming updates” said “No updates received yet” forever if you use the Google connection. Only the Apps Script route wrote to that table. Sites using the one-click Google connection were syncing edits correctly the whole time, but the page gave no evidence of it, so a working setup looked broken. Entries now record which mechanism delivered them and the table shows it.
• Improved: the Two-Way Sync page now describes the mechanism your site actually uses. If Google is connected it reports that the sync is active, how often it checks, when it last read the sheet, and when it will check next – and it is honest that WordPress cron only runs when someone visits the site, so a quiet site checks less often than the interval suggests. The Apps Script instructions are demoted to “not needed on this site” rather than presented as the setup path.
• Improved: a site with an active licence but no Two-Way Sync add-on now says so. Previously only a missing licence warned, so an unentitled site looked correctly configured while every incoming edit was rejected.
• Added: a warning against running the Apps Script and the Google connection on the same sheet. Both deliver to the same place, and with both live an edit can be applied twice.

1.14.6

• Improved: the setup wizard no longer walks you through an Apps Script you do not need. If you have already connected Google with one click, the “Google Script” step is gone and the remaining steps renumber – previously the wizard asked you to deploy a script and then told you on the very next screen that there was nothing else to set up.

1.14.5

• Fixed: “Fields: 0” again, this time on Send Test. The 1.14.4 fix only reached the path a real form submission takes; Send Test still reported zero. Since Send Test is how most people confirm a rule works, that was the number most people saw.

1.14.4

• Fixed: the Sync Log said “Fields: 0” on deliveries that wrote several columns. Since 1.14.0 you no longer type column names, so the count had nothing left to count and reported zero. It now reports what was actually written to the row.
• Improved: Send Test now confirms itself next to the button. The confirmation only appeared at the top of the page, so on a long list of rules a successful test could look like nothing happened – and a retried test writes another real row to your spreadsheet.

1.14.3

• Fixed: Send Test never tested the Excel mirror. It ran and reported the Airtable and Notion mirrors but skipped Excel entirely – no notice, no Sync Log row, no row in your workbook – so a working Excel mirror and a broken one looked exactly the same. Excel is now included, and reports like the others.
• Fixed: an Excel mirror that is switched on but not finished being set up now says so. It used to skip in silence, which looked identical to having no Excel mirror at all.
• Fixed: the workbook picker could come up empty on a brand-new Microsoft 365 account. Microsoft’s file search needs time to index a newly created OneDrive and returns an error until it has; SheetLink now falls back to listing the files in your OneDrive so you can pick a workbook straight away.

1.14.2

• Fixed: checkboxes that could not be switched off. Unticking a WooCommerce event, or a conditional routing rule, appeared to save and then came back ticked. The browser sent the right value; it was misread on arrival, so the setting was always stored as enabled. Anything you had tried to switch off has been running all along.
• Fixed: opening the WooCommerce screen and pressing Save switched on all six event types, whether or not you ticked them. Events left enabled with no Receiver URL are switched off automatically on update, since they could never have sent anything. An enabled event that has a URL is left exactly as it is.

1.14.1

• Fixed: the setup wizard could not be opened at all. Every visit to it returned “Sorry, you are not allowed to access this page”, including the automatic redirect a new site is sent through immediately after activating the plugin. The page was registered under the main SheetLink menu and then hidden from the sidebar, which left WordPress unable to resolve it. Present since 1.9.4.
• Fixed: the one-click Google route could not finish the wizard. After connecting a Google account, the last step still demanded an Apps Script “Receiver URL” and refused to save without one, so anyone taking the one-click route left the wizard with no sync rule and nothing was ever delivered. That step now recognises the connection, and the Apps Script field is hidden entirely rather than shown and ignored.
• Fixed: an empty Receiver URL on the classic Apps Script route reported that the address “does not look like” a valid URL, when nothing had been typed. It now says what to do instead, including the one-click option.
• Fixed: the wizard’s own stylesheet, script and documentation link stopped loading when the page moved.

1.14.0

• Fixed: Google Sheets deliveries failed with “No form fields are mapped” for most form plugins. SheetLink matched your sheet’s column headers against each form field’s internal key, and several plugins use generated keys – Formidable emits things like kzn0j, Ninja Forms name_1512... – so a column called “Email” matched nothing and the row was never written. Columns are now matched on the field’s label as well, which is what you actually name your columns after. Gravity Forms and WPForms were unaffected because they happen to key by the label already.
• Added: you no longer type column names. Connect a spreadsheet, point a form at it, and the first submission writes the header row for you, taken from that form’s own fields. Existing setups are untouched – if you have already configured columns, they keep being used.
• Added: each form now gets its own tab. A tab has a single header row, so two forms with different fields could never share one – the second form’s answers landed under the first form’s columns. Your first rule keeps using the tab you picked; any additional form gets its own, named after the rule.
• Added: the Google Sheets screen now tells you when a connected spreadsheet has no form pointed at it, and lets you create that rule right there. Connecting a sheet writes its header row, which looked finished while nothing was actually being sent.
• Improvement: seeded column headers use readable labels (“First Name”) rather than internal names (“names.first_name”, “name-1”) for Formidable, Ninja Forms, Forminator, Everest Forms, Fluent Forms, WPForms, WS Form and Divi.

1.13.1

• Change: the plugin now contacts sheetlinkwp.com for licence activation and entitlement checks, instead of siteanswerai.com – a legacy domain the API happened to be hosted under. Nothing to do on your side, and older installs keep working because the old address forwards to the new one. If you listed siteanswerai.com as a data processor in your privacy notice, update it to sheetlinkwp.com.
• Change: the Primary Destinations add-on (previously “Excel Primary Destination”) now covers Excel Online, Airtable and Notion. One add-on for all three. If you already own Excel Primary, your existing licence unlocks the other two at no extra cost – nothing to do.
• Removed: a long-unreachable legacy Airtable/Notion delivery path inside the Integrations Bundle. It could not be configured from any shipped rule editor, and Airtable and Notion have been free built-in destinations with proper per-rule field mapping since 1.9.4. If a rule from a very old build still references it, an admin notice now points you to the built-in destination instead of the delivery failing quietly.
• Improvement: corrected pricing and add-on descriptions that implied Airtable and Notion were part of the paid Integrations Bundle. They are free core destinations; only using one as your sole destination is paid.

1.13.0

• Security: stored API tokens are no longer written into the settings page’s HTML. The Airtable, Notion, Meta CAPI and SMS (Twilio) screens pre-filled their credential field with the saved token. The browser masked it visually, but it sat in the page source in cleartext – readable by anyone who can view source on that screen, by browser extensions, and by anything that captures the page. The field now renders empty with a masked “Currently set” hint: leave it blank to keep the stored token, or tick Remove the stored value to delete it. If you have entered an API token on any of those screens, consider rotating it.
• New: Airtable and Notion can now be a rule’s primary destination. Previously they could only mirror a successful Google Sheets delivery, which meant you had to set up a Google Sheet you did not want – and if that Sheets delivery ever failed, the Airtable write never happened either. A rule can now deliver straight to Airtable or Notion with no Google Sheets configuration at all. Pick it from the Primary destination dropdown in the rule editor. Requires the Primary Destinations add-on, which covers all three; the free Airtable, Notion and Excel mirror modes are unchanged and stay free.
• New: primary deliveries to Airtable and Notion use the full delivery pipeline – the automatic retry queue (throttling and provider outages retry; a bad token or unknown column does not, because retrying cannot fix those), save-time validation of your credentials, and destination-aware health checks. Mirror deliveries never had retries.
• Fix: failed deliveries to Excel, Airtable and Notion logged a blank error. The Sync Log recorded the correct status and HTTP code but discarded the explanation, so a failure showed up with an empty Error column. The provider’s actual message is now kept.
• Fix: the Sync Log’s Fields count now reflects what was actually written to the destination rather than how many fields arrived from the form – relevant for Airtable and Notion, which only send mapped fields.

1.12.4

• Fix: Contact Form 7 submissions now sync even when the notification email fails. SheetLink captured CF7 submissions on the hook that fires only after CF7’s email is sent successfully, so on a site with broken or unconfigured SMTP not a single submission ever reached the spreadsheet – precisely the situation a spreadsheet is supposed to protect you from. Capture now happens after CF7 finishes its own validation, acceptance, spam and file checks but before the email is attempted, so delivery no longer depends on your mail server. Spam and aborted submissions are still excluded, exactly as before.
• Improvement: rows created by the Send Test button are now labelled “Test” in the Sync Log. Previously a test send and a real form submission produced identical log rows, so a green row proved the destination worked but not that a real submission had ever arrived – awkward when debugging a live site.

1.12.3

• Fix: Airtable and Notion no longer reject every submission when your form has more fields than your table has columns. Airtable refuses the entire record if any field name is not a real column, so a five-field form writing to a three-column table failed 100% of the time with “Unknown field name” – losing the lead. When you have set up a field mapping, only the mapped fields are sent. A new Unmapped fields checkbox on the Airtable and Notion screens restores the old behavior if every one of your form fields has a matching column. With no mapping configured, all fields are still sent, so a table whose column names match your form field names keeps working with no setup.
• Fix: an enabled-but-unconfigured mirror now says so. If Airtable or Notion was switched on but missing its token, Base ID, or table name, the plugin skipped it silently – no Sync Log row – which looked exactly like the feature being broken. It now logs a failed row naming precisely which setting is missing.
• Fix: the Airtable table-name field is now also protected from browser autofill (the token and Base ID fields were covered in 1.12.2).

1.12.2

• Fix: Airtable and Notion deliveries no longer fail silently. When a mirror write was rejected – most often an invalid or mistyped access token – the plugin discarded the error: no entry in the Sync Log, nothing in the retry queue, no notice. That made a broken credential look exactly like a feature that was never running. Every Airtable and Notion attempt is now recorded in the Sync Log, on success and on failure, with the provider’s own error message.
• Fix: the Excel mirror now records successful writes too (it previously only surfaced failures, as an admin notice).
• Fix: Send Test now tests what your rule actually does. It sends through the rule’s real destination – so it works for Google Sheets (OAuth) and Excel rules instead of only classic Apps Script rules – and it also exercises your Airtable and Notion mirrors, reporting each one. A mirror failure now fails the test instead of showing a misleading all-clear.
• Fix: a saved field mapping could be silently reverted. If a Google account token renewal happened at the same moment you saved a rule’s field mapping, the renewal wrote back older settings and discarded the mapping – leaving the rule failing with “No form fields are mapped to the sheet columns”. Renewal now only touches the token.
• Fix: saving an empty field mapping now warns that deliveries will fail, instead of reporting a plain “saved” for a rule that cannot deliver.
• Security/UX: the Airtable Base ID and access-token fields (and the Notion token field) now resist browser password-manager autofill, which could quietly overwrite your Base ID with a saved username and break every write.

1.12.1

• Improvement: Excel deliveries retry when the workbook is open in the desktop Excel app. A workbook locked by desktop Excel (the most common real-world Excel failure) previously failed permanently; it now retries automatically with a clear message, and succeeds once the file is closed.
• Improvement: Excel writes to the same workbook are serialized. Simultaneous submissions (or a retry batch overlapping a new submission) no longer race each other into Microsoft’s same-workbook write conflict.
• Improvement: Microsoft throttling responses are respected. When Microsoft asks SheetLink to wait (HTTP 429/503 Retry-After), the retry queue now waits at least that long instead of retrying on its own schedule.
• Improvement: weekly Microsoft connection keepalive. Microsoft silently expires connections after ~90 days of inactivity; a weekly background refresh keeps a quiet site’s Excel connection alive indefinitely.
• Improvement: Microsoft connections now remember their home tenant, which makes token refresh more reliable for work/school accounts (including guest accounts in another organization).
• Fix: a token refresh finishing at the same moment as a settings save can no longer discard the new Microsoft credentials.

1.12.0

• New: One-click Google Sheets connect. Connect a Google account and write submissions straight to a Google Sheet – no Apps Script, no pasting a script, no webhook URL. Create a new sheet in one click, or pick an existing one with Google’s own file picker. SheetLink only ever sees the sheets it creates for you or that you pick – never the rest of your Google Drive. The classic Apps Script method is unchanged and still available.
• New: Per-rule field mapping for the one-click Google Sheets destination. Map each form field to a sheet column on the settings page. Columns you leave unmapped are filled automatically when a column header matches a form field name.
• Improvement: newly created sheets get a labeled header row automatically, and rows are appended beneath it.
• Fix: the one-click Google Sheets destination no longer writes a blank row when nothing is mapped – it reports a clear, actionable error instead of silently logging a success.

1.11.4

• Fix: queued retries now use the same HTTP transport as first deliveries. A retried Apps Script delivery previously followed Google’s redirect and re-sent the request to the redirect endpoint, which rejects it – logging an HTTP 400 “failure” even though the first hop had already written the row (and each retry could write a duplicate). Retries now treat the redirect as the success it is, and a redirect to a Google sign-in page is a non-retryable configuration error with a clear message.
• Improvement: the Apps Script setup instructions now explain how to update a deployed script. Saving code in the Apps Script editor does not change what the web app runs: you must publish it via Deploy > Manage deployments > edit > Version: “New version”. The instructions warn that the Version dropdown pre-selects the old version, and that “New deployment” creates a second URL instead of updating the existing one. This distinction has cost real users real hours.

1.11.3

• Fix: WS Form submissions now capture field values. The integration listened with the wrong number of hook arguments, so every WS Form delivery arrived …