What is this Charge on my Credit Card?

What is this Charge on my Credit Card?

I have a charge on my statement for Gravity Forms, can you explain what this is for?How Do I See My License?How Can I Get A Refund?How Can I Get More Info?

I have a charge on my statement for Gravity Forms, can you explain what this is for?
Gravity Forms is the pre-eminent WordPress plug-in to enable web professionals and website administrators to add simple or complex forms to their WordPress websites, as well as to integrate submissions from those forms to a host of external services. This helpful article explains what Gravity Forms is in a little more detail.

​If you have been billed for Gravity Forms, then you have purchased or renewed one of our licenses. Our licenses renew annually, and you can see our license plans and payment amounts on this page.
How Do I See My License?
If you know the email address your license was purchase under, you can view your license details, including what sites it is being used on and the transaction history by logging in to your account.
See also this help page for articles on your Gravity Forms account page.
How Can I Get A Refund?
A refund can be requested from within your account. See this guide.
How Can I Get More Info?
We have a host of quick-read help guides on this very website. Try starting here for articles about your license and account.
If you do not know the email address the license was purchased against, you can contact our support team here. We will require details about the purchase method used, so please include:

date of purchase
first 3 digits and final 4 digits of the credit card used.
name on the card

Zapier Add-On Related Articles and Tutorials

Zapier Add-On Related Articles and Tutorials

SummaryGravityForms.comZapier.comOther Sites

Summary
This document contains a quick reference list of articles and tutorials from websites external to our documentation site which may help you get the most out of the Gravity Forms Zapier Add-On.
Make sure you peruse the Zapier section of our documentation site also.
GravityForms.com

What is possible with Gravity Forms and Zapier?
Supercharge your WordPress Forms with 1,000+ Apps and Services
Sending Form Entries to Google Sheets
Updating Spreadsheets from Form Entries in WordPress
Sending Form Entries to Google Calendar
Uploading Files to Google Drive from WordPress
Sending Product Information to Google Sheets using Zapier
Sending List Field and Product Data As Arrays to Zapier

Zapier.com

Gravity Forms Integrations
Gravity Forms Integration Help & Support

Other Sites

Zapier – Creating Pipedrive Deals via Gravity Forms
Send Gravity Forms Submissions to GoToWebinar
Automatically Create Base CRM Leads from Gravity Forms
Sending New Emails via SendGrid for New Gravity Forms Submissions
Asking for signatures from HelloSign for new Gravity Forms submissions

Why did the Stripe Feed Subscription Name Change?

Why did the Stripe Feed Subscription Name Change?

With Gravity Forms Stripe Add-On version 3.7.2 and greater you may occasionally notice the value of the Subscription Name setting on your Stripe feed changes to include additional numbers and underscores.
This can happen when the add-on finds a plan already exists in Stripe with an ID that matches the current feed configuration and one of the following scenarios is encountered:

The plan amount does not match the submission amount
The plan currency code does not match the submission currency code
The plan billing cycle does not match the feed billing cycle

When the add-on determines the existing plan is not suitable for the submission being processed it appends the current date and time formatted with underscores (e.g. _2020_07_29_10_27_39) to the feed Subscription Name and updates the feed in the database. It then creates a new plan in Stripe based on the updated feed configuration. This change ensures that the customer is billed correctly.

Zoho CRM European Hosted Accounts

Zoho CRM European Hosted Accounts

Sample IssuesIssue Sample 1Issue Sample 2

As of Zoho CRM version 1.7, it is no longer necessary to use the filters below if your account is hosted in the EU.

Only follow the directions below if you are using a version previous to Zoho CRM Add-On 1.7. It is highly recommended that the latest version of Zoho CRM is downloaded, because along with the changes to handle accounts hosted in the EU, the update uses Zoho CRM』s new API Version 2.0. API Version 1.0 is deprecated and its end-of-life date is 12/31/2019.

If your Zoho CRM account is hosted in the EU you will need to configure the add-on to use different endpoints by adding some code snippets to your theme functions.php file or a custom functionality plugin.
1234567add_filter( 'gform_zoho_accounts_api_url', function() {return 'https://accounts.zoho.eu';} ); add_filter( 'gform_zoho_api_url', function() {return 'https://crm.zoho.eu/crm/private/';} );
Sample Issues
Issue Sample 1
Hi, I am trying to Authenticate the Zoho CRM addon and using my Zoho login details. Everytime I save my email and password, it says 「the user does not exist.」 Even when I try to use the Authentication token option, it has a red 『x』 next to the field and doesn』t register the token. This is not allowing me to create a feed and keeps bringing me back to the settings.
Issue Sample 2
I』m experiencing some trouble with setting up the Zoho CRM add-on. I』ve downloaded and activated the add-on one site within a multisite. When I enter the credentials for Zoho I get an error that the user doesn』t exist. I』m certain the user does exist in Zoho, because I』m able to login to Zoho with this user. I』ve enabled debugging and debugged the code locally, but I keep getting this response. I』ve updated the Gravity Forms plugin in the local environment, but this didn』t help.

What To Do If You Suspect a Security Issue

What To Do If You Suspect a Security Issue

Determining if you have a threatCleaning up a compromised sitePreventing security issues

We take security issues very seriously and want to make sure that any security concerns are appropriately addressed in a timely manner. In this article, we will take a look at identifying a legitimate security concern and what to look for before submitting a ticket to support.
Note: This article is not intended for security researchers reporting a code vulnerability. For technical details on identifying code vulnerabilities, you may review our article on security practices in Gravity Forms.
Determining if you have a threat
If you have a security threat, many times it will be quite blatant but can sometimes be a bit subtle. Here are a few things to look for:

If any part of your site has been abruptly replaced with other content you do not recognize, your site has likely been hacked.
Suddenly being unable to log into your WordPress admin dashboard is another sign that your side may be compromised.
Check for unknown plugins. Some attacks will install plugins with clever names to hide their true intent.
If you have Webmaster Tools enabled, most times Google will alert you of possible malware on your site. Check your email for any alerts that may have been sent regarding a security issue.
Check the pages on your site. Many times when a site is compromised, links will be injected within either the footer or within the main content itself.
If you are accepting payments, check to ensure that any payment gateway information is indeed yours. If the payment information has changed, it』s a sure sign that your site has been compromised.

Cleaning up a compromised site
If your site has been compromised, it can sometimes be quite difficult to completely track it down. Here are a few things that can help you clean up a site after it has been compromised:

If possible, restore from the earliest possible backup. This will ensure that you have a clean copy of your files rather than attempting to track down the issue which can take quite a while. Always back up your site early and often as this is your best defense against a catastrophic issue.
Install iThemes Security and use the security scanner included with it. Often times, iThemes Security can easily locate malicious files hiding deep inside your WordPress installation.
Restore your WordPress core files with a fresh copy. As it is a good practice to never modify your WordPress core files and instead build a plugin that makes the changes you need, replacing your WordPress core files with a fresh copy can often make an impact if malicious software has modified them.
Reinstall any plugins and themes you may be using. Doing so will make sure you have a clean copy. Although most data should be stored in the database, be sure to create a backup first just in case anything goes wrong.
Change any passwords used to access your content. This includes your WordPress admin user passwords, FTP credentials, database credentials, and cPanel passwords. If you』re having trouble making those changes, your web host should be able to easily make the change for you.

Preventing security issues

Keep all of your plugins, themes, and WordPress core updated at all times. A large number of sites are compromised due to out of date plugins, themes, or WordPress core every day. Keeping everything up to date is your best defense against attacks.
Use secure passwords. Often times, the password being used is the weakest link in the chain. Passwords should be completely random and contain a mixture of upper-case and lower-case letters, numbers, and symbols.
Use security plugins for added protection. iThemes Security does a great job of preventing common attacks before they happen as well as BruteProtect will help prevent against brute force attacks.
Using secure, well-known plugins minimizes security risks as they are regularly updated and vulnerabilities are discovered rather quickly and before they are discovered by the public.

Using the Zapier Add-On

Using the Zapier Add-On

IntroductionPre-RequisitesQuick Getting StartedSetting up the Zapier Add-OnZapier Actions and TriggersZapsZapier HelpWhat Can You Do with Zapier and Gravity Forms?

Introduction
The Gravity Forms Zapier Add-On allows you to integrate Gravity Forms with over 200+ (and counting) online services. Zapier enables you to automate tasks between other online services such as Salesforce, Basecamp, GMail, and over 200 more.
Capture data via a Gravity Form that automatically creates a lead in Salesforce, a new row in a Google Spreadsheet, and a new calendar event in Google Calendar. All from the same single form submission.
The Gravity Forms Zapier Add-On does not replace our existing add-ons such as MailChimp, Campaign Monitor, etc. but does provide you with a way to integrate with services that we may not already support via official Add-Ons. Just as we consider Gravity Forms a swiss army knife for WordPress, Zapier is a swiss army knife for Gravity Forms.
In order to use the Gravity Forms Zapier Add-On you must have a Zapier account. Zapier is a paid service and pricing is based on volume and usage. You can find more about Zapier pricing here.
Unlike most Gravity Forms Add-Ons, the majority of the setup involved in integrating with Zapier will occur on the Zapier side via their customer dashboard. This does mean if you are having an issue with a Zap you have created in Zapier not behaving the way you expected, you may need to contact Zapier support for assistance for issues that occur within their Zapier Dashboard, Zap setup, and behavior.
Pre-Requisites

Download and install the add-on
A Zapier account
Signing up can be done quickly and easily and includes a 14-day free trial which gives you access to every regular and premium app. After the free trial, you can continue to use the free plan or select one of the available premium plans.
SSL Certificate Installed and Configured
Website Accessible to the Internet. The new authentication from Zapier to Gravity Forms uses REST API so your website must be accessible to Zapier.

Quick Getting Started

Create a Zapier REST API Connection under Forms, Settings, REST API. Save the Consumer Key and Consumer Secret for step 2.
Create a Zapier App Connection to Gravity Forms in MyApps. You will use the Consumer Key and Consumer Secret from step 1
Create a Gravity Form to send information to Zapier.
Create a Zap under your Zapier account to connect to the form you created. You』ll use the Gravity Forms connection created in Step 2.

Setting up the Zapier Add-On
Use this reference to configure your Zapier Application Connection to Gravity Forms
Zapier Actions and Triggers
You can use your Gravity Forms as both a Zapier trigger and as a Zapier action.
In both cases, the set-up process is done completely from within your Zapier account.
Zaps
To start sending data between Zapier and your forms, create a Zap as normal from within your Zapier account. You』ll be using the Gravity Forms connection.

Zapier Help
Most of your configuration with Gravity Forms and Zapier will take place within your Zapier account. If you run into issues, and you』ve confirmed that Zapier is communicating with the REST API connection in Gravity Forms, you can reach out to Zapier for assistance. You can check out their help documentation here.
What Can You Do with Zapier and Gravity Forms?
Zapier has 2000+ of Web Applications that can potentially integrate with Gravity Forms. Check out some of the most popular Zaps that you can use to work with Gravity Forms and these applications.

Create rows in Google Sheets for new Gravity Forms submissions
Use this Zap
Add contacts to Hubspot from new Gravity Forms entries
Use this Zap
Create HubSpot contacts from new Gravity Forms submissions
Use this Zap
Create Salesforce leads with new Gravity Forms submissions
Use this Zap
Create Google Calendar events from new Gravity Forms submission
Use this Zap

See more

Gravity Forms

integrations

powered by Zapier

Webhooks Change Log

Webhooks Change Log

1.5 | 2021-05-061.4 | 2020-09-101.3 | 2020-05-131.2 | 2019-04-251.1 | 2017-08-231.0 | 2017-08-08

1.5 | 2021-05-06

Fixed an issue that prevents saving feed settings for a request URL that contains encoded values.
Fixed an issue where the add-on icon is missing on the Form Settings page for Gravity Forms 2.5.
Fixed an issue where script tags are being output above the document head element.

1.4 | 2020-09-10

Added support for Gravity Forms 2.5.

1.3 | 2020-05-13

Added translations for Hebrew, Hindi, Japanese, and Turkish.
Added security enhancements.
Updated stylesheets to use minified versions.
Fixed a PHP error which could occur when using the https_local_ssl_verify filter with WP 5.1+.

1.2 | 2019-04-25

Added "gform_webhooks_post_request" action.
Added GPL to plugin header.
Added support for delaying feed processing until after payment has been successfully completed using the PayPal Standard Add-On.
Added support for feed duplication.
Added support for using the {admin_ajax_url} and {rest_api_url} merge tags in the Request URL setting.
Updated logging statement.
Updated Plugin URI and Author URI to use https.

1.1 | 2017-08-23

Fixed data from selected fields not being included in the request.

1.0 | 2017-08-08

It's all new!

WordPress, Gravity Forms, and GDPR Compliance

WordPress, Gravity Forms, and GDPR Compliance

What Is GDPR?What Tools Can Help Me With Gravity Forms and GDPR Compliance?Collecting ConsentData RequestsGDPR PluginsFurther Questions and Answers Related To Personal DataCan I prevent the IP address being saved in the entry?Can I encrypt the field values before they are saved to the entry?Can I prevent Gravity Forms saving the entries to the database?Can the user view or edit their own submissions?Are the entries sent to gravityforms.com or other related domains?Does Gravity Forms set any cookies?

What Is GDPR?

On May 25, 2018, new regulations went into place within the European Union (EU) regarding treatment of customer data, known as General Data Protection Regulations (GDPR). There are many references available online, you can find one such overview here. We are not going to try and explain the implications or the interpretation of what is required, that is the realm of lawyers and consultants, but we do want to highlight some WordPress and Gravity Forms related tools that may be of interest here.

What Tools Can Help Me With Gravity Forms and GDPR Compliance?

Once again, we』re not lawyers so you』ll want to confirm this with a legal counsel or a subject matter expert as to what compliance means for you, but some of the following tools may prove useful.

Collecting Consent

Gravity Forms 2.4 introduced a Consent field amongst the Advanced Field types. You can review the field here.

If you are also using a feed based add-on with your form, such as MailChimp, you can configure conditional logic on the feed so it will only be processed if the user has checked a consent field. See the MailChimp Conditional List Subscriptions article for more details.

Data Requests

WordPress has added the Export Personal Data and Erase Personal Data tools. As of Gravity Forms 2.4, a new Personal Data tab has been added to the Form Settings to provide integration with these tools. See the article Personal Data Settings for more details.

GDPR Plugins

The following third-party plugins can help with GDPR compliance, and they have integrations for Gravity Forms:

WP GDPR Compliance by Van OnsThe GDPR Framework by Data443 Risk Mitigation, Inc. They also maintain an additional plugin for CCPA (California Consumer Privacy Act), CCPA FrameworkDouble Opt In for Gravity Forms by Albert Brückmann

Further Questions and Answers Related To Personal Data

Can I prevent the IP address being saved in the entry?

Yes. As of Gravity Forms 2.4, the new Personal Data tab on the Form Settings provides several settings to control which data is saved. Preventing the storage of IP Addresses is a checkbox option there. See the article Personal Data Settings for more details.

Can I encrypt the field values before they are saved to the entry?

We recommend the using the Encrypted Fields add-on by PluginOwl to configure encryption of the field values.

Can I prevent Gravity Forms saving the entries to the database?

It』s important to note that GDPR does not prohibit saving of personal data to the database, it just requires that you to gain consent before doing so.

While you can』t currently prevent Gravity Forms saving the entries you can use custom code or a third-party add-on to delete them during submission, after the notifications and add-on feeds are processed.

With Gravity Forms 2.4, you can set a Retention Policy to Retain, Trash, or Delete entries for a set number of days. This is available in the Personal Data tab in the Form Settings. On the Personal Data tab, you may also integrate with the WordPress Erase Personal Data tool and control what data is erased from the entry. See the article Personal Data Settings for more details.

Can the user view or edit their own submissions?

Allowing the user to view or edit their own submissions is not a built-in feature of Gravity Forms but is made possible by third-party add-ons such as GravityView by Katz Web Services, Inc..

As of Gravity Forms 2.4, the Personal Data tab of Form Settings allows you to integrate with the WordPress Export Personal Data tool and export chosen entry data to the customer.

Are the entries sent to gravityforms.com or other related domains?

No. Form submissions (entries) are saved to your sites WordPress database. The data would only leave your site if you configure a notification email or another add-on yourself to send it elsewhere.

Does Gravity Forms set any cookies?

Gravity Forms does not set any cookies on the front-end of the site. It does set a cookie on the entry detail page in the admin when an admin views the entry and checks the show empty fields checkbox, that cookie is named gf_display_empty_fields.

How Poll Results Work and Why They May Be Delayed

How Poll Results Work and Why They May Be Delayed

How Poll Results Are GeneratedResults Calculation Cron JobCan I Accelerate The Hourly Cron Job?

How Poll Results Are Generated
Each time a poll form submission occurs, results are processed. Those processed results are then displayed to the user. The results are then cached until another submission triggers them to need to be rebuilt again.
In some rare cases, when there are thousands of submissions on a particular poll, the results may not be able to be generated quickly, and thus the results displayed may be behind the actual submissions.
Results Calculation Cron Job
If results take longer than five seconds to generate, a cron is created which will attempt to rebuild the results hourly. Once the cron is created, it will attempt every hour to complete the result generation.
Simply giving some time for the results to be generated will allow the data to once again become accurate.
Can I Accelerate The Hourly Cron Job?
Yes. With a bit of custom code, you can adjust the cron task to run more often. For example, a failure could attempt twice an hour rather than hourly. The snippet below will do that.
add_filter( 'gform_polls_cron_schedule', 'cron_add_twice_hourly' );
function cron_add_twice_hourly() {
// Adds once weekly to the existing schedules.
$schedule['twicehourly'] = array(
'interval' => 1800, // number of seconds in the interval
'display' => __( 'Twice Hourly' )
);
return $schedule;
}

Note: After inserting this snippet, you will need to deactivate and reactivate the Polls Add-On to reschedule an existing task.

Zapier Change Log

Zapier Change Log

4.1.14.1 | 2021-05-044.0 | 2021-02-233.3 | 2020-05-203.2 | 2019-09-253.1 | 2018-10-223.0 | 2018-05-072.1.7 | 2018-03-202.1.6 | 2018-03-162.1.5 | 2018-01-312.1.4 | 2017-10-022.1.3 | 2017-05-092.1.2 | 2017-04-262.1.1 | 2017-03-122.1 | 2017-01-052.0 | 2016-08-311.9 | 2016-07-011.8 | 2015-08-181.7 | 2015-04-201.6 | 2015-03-301.4 | 2014-02-031.1 | 2013-08-14

4.1.1

Updated the gform_zapier_request_body filter to be called within GF_Zapier::get_body so that it can be applied both when processing feeds and responding to API requests.

4.1 | 2021-05-04

Added support for displaying real entry data for the selected form when configuring a Zap.
Added support for using admin labels instead of front end labels for the entry data returned when configuring a Zap.
Fixed an issue where API instructions are not visible on the add-on settings page when using Gravity Forms 2.5.
Fixed an issue where feeds get deleted and recreated when the Zap is deactivated and reactivated.
Updated the Use Admin Labels setting on the feed configuration page to be disabled. The setting is now configured on zapier.com.
Removed the add new button from the feeds list page.

4.0 | 2021-02-23

Added support for the Gravity Forms Integration App on Zapier v2.0.
Added an add-on setting to toggle the display of Zapier Feeds in the form settings. On sites with legacy feeds created for the Zapier v1.0 integration, this setting is enabled by default, displaying all the feeds. On sites with no legacy feeds, this setting is off by default so the feeds will not be displayed.
Fixed compatibility issues in PHP 8.
Updated the feed settings to restrict editing of feeds created in the Zapier v2.0 integration to Admin Labels and Conditional Logic.
Updated the add-on to use the Gravity Forms Add-On Framework.

3.3 | 2020-05-20

Added translations for Hebrew, Hindi, Japanese, and Turkish.
Fixed an issue where the entry and payment dates were being formatted before being sent to Zapier.

3.2 | 2019-09-25

Added support for triggering Zapier feeds after a successful delayed payment (we originally did it only for PayPal). This fixed an issue where feeds are triggered before payments received when using Stripe Checkout.
Added gform_zapier_request_body filter to allow the request body sent to Zapier to be modified.
Fixed notice in gform_zapier_use_stored_body filter processing.
Fixed the shipping line item being included in the request body when the shipping field is hidden by conditional logic.
Fixed PHP 7.3 warnings when the feed is populating the request body for a form with multiple product fields.

3.1 | 2018-10-22

Added the gform_zapier_products filter.
Updated data sent to Zapier to include extra entry properties and the form ID.
Fixed missing product fields.

3.0 | 2018-05-07

Added line item support for list field and product fields.

2.1.7 | 2018-03-20

Fixed issue when trying to get random choices on an empty array.

2.1.6 | 2018-03-16

Fixed an issue where feeds could, in some situations, be processed following PayPal payment when not selected as delayed on the PayPal feed.

2.1.5 | 2018-01-31

Added GPL to plugin header.
Updated Plugin URI and Author URI to use https.

2.1.4 | 2017-10-02

Fixed feeds not running when the form is embedded in an admin page or a front-end page via an Ajax request.

2.1.3 | 2017-05-09

Added security enhacements.
Fixed code styles.

2.1.2 | 2017-04-26

Added support for the Gravity Forms 2.2+ System Status page.

2.1.1 | 2017-03-12

Added the gform_zapier_use_stored_body filter.

2.1 | 2017-01-05

Added support for the gform_is_delayed_pre_process_feed filter.
Updated strings for translations.
Updated Zapier Feeds table to be responsive.
Fixed issue where Zapier did not appear alphabetical in the Settings list.

2.0 | 2016-08-31

Added the gform_zapier_sample_field_value filter for overriding the sample data sent when configuring the zap or updating the form.
Updated to format entry date.
Fixed an issue with the 'Use Admin Labels' setting on new zaps appearing to reset when saving a valid zap.
Fixed PHP warning which could occur if the multiselect field only had one choice configured.

1.9 | 2016-07-01

Added support for sending the field admin label to Zapier, if available.
Added GFZapier::process_feed( $feed, $entry, $form ) for processing a single feed.
Updated to send the form title, entry id, entry date, user ip and source url.
Updated minimum Gravity Forms version to 1.9.10.
Updated to send dummy values to Zapier when saving the feed/form instead of empty values.
Updated to skip display only fields when preparing the zap body array.
Updated to use the field title when preparing the zap body if the field doesn't have a label.
Updated minimum Gravity Forms version to 1.9.
Updated to support Gravity Forms 2.0 changes to the PayPal Standard integration.
Fixed an issue where field values in the body array would be overridden if another field used the same label.
Fixed PHP notices on the edit feed page related to the conditional logic field and value settings.
Fixed an issue with the feed conditional logic value drop down for choice based fields.
Fixed GF_Field array access/object notation notice with Gravity Forms 2.0.
Fixed an issue with the PayPal Standard integration.

1.8 | 2015-08-18

Added the gform_zapier_feed_conditional_logic filter enabling the feed conditional logic rule to be overridden during submission, allowing multiple rules to be defined.

1.7 | 2015-04-20

Added text domain/path to header.
Fixed an issue with multi-input fields and the dummy data sent to Zapier when first configuring a zap or updating the form.
Fixed a low severity security vulnerability in the admin area which could be exploited by authenticated users with form administration permissions.
Fixed an issue with conditional logic evaluation when processing feeds delayed by the PayPal Standard add-on.

1.6 | 2015-03-30

Added Spanish (es_ES) translation.
Added ability to delay sending to Zapier until a payment is received if PayPal Standard is also being used.
Updated POT file.
Updated to not send entries marked as spam to Zapier.
Fixed an issue with the zap body being prepared even if the form does not have a feed.
Fixed a warning for multi-row Likert fields when the zap body is being prepared.
Fixed a warning related to how Gravity Forms 1.9 handles inputs for fields such Email, Date and Time.
Fixed notice thrown when using extract in certain PHP versions.
Fixed the functions used by the mwp_premium_update_notification and mwp_premium_perform_update hooks so that the new_version element in the array returns Zapier's version instead of Gravity Forms.
Fixed strict notice thrown when viewing the list of Zaps for a form.

1.4 | 2014-02-03

Added POT file.
Added entry meta to field list.
Added the gform_zapier_field_value hook so the value can be modified before sending to Zapier.
Fixed issue where the anti-spam honeypot being active was causing data to not be passed to Zapier.
Fixed notices.

1.1 | 2013-08-14

Updated how multi-input fields (checkboxes, name, address) are handled so that users can map to the "parent" field (in addition to being able to map to the individual inputs).