Big Sea

Hey Thomas,

That is a very curious issue. I have heard of only instances of a few additional Gravity Forms plugins causing conflicts… but not in which it just flat out prevents a form from sending data to HubSpot.

Have you turned on debug for my script and checked the error log for possible causes?

Add define('GF_HUBSPOT_DEBUG', true); to your wp-config.php and try a test submission… You’ll find an error log in wp-content/uploads/gf-hubspot.log

Hopefully that provides some insight, especially on whether or not the script is running at all.
-Chris.

Hey Dozkaynak,

When this is configured, the “HubSpot Feed” section of Gravity Forms is the ONLY area where an individual form is managed for listening to HubSpot. If you delete the form, you do not have to worry about WordPress sending any more data to HubSpot for that form…

However, since this plugin is a 1-1 relationship of a HubSpot form, anyone who submits directly to the form on HubSpot, will still show up there.

If your question is more about that you want to revoke the PLUGIN’s access to your HubSpot, you can visit HubSpot > Settings > Your Integrations, and you can manage your HubSpot for Gravity Forms integration there (only option is to “uninstall” which is to revoke its access to ALL Gravity Forms forms)

Hey gorillatyler,

I’m going to take a moment to try to make sure when this happens that it does not utterly break the front end… However, it’s up to HubSpot to trust the tokens that we’re given them… the tokens expire about every 8 hours, so the fact that it fails after a MONTH (vs a quarter of a day)… it’s hard to understand why HubSpot would have a problem with the token we’re providing when it’s the same as when we refresh with larger frequency.

We renew about every 7.5 hours (If the authorization token has a refresh time of 8 hours, we work to send the refresh_token at least 30 minutes prior expiration)…

I’ll keep trying to replicate this issue, but as you’ve noted, and that thread included also seems to imply, there’s something larger and unresolved at play.

Hey lsilver,

We’ll look into adding this at a later date. Currently it’s not in the plan, but that’s a good idea.

Hey ivcatalina,

This issue does not sound like it has anything to do with our plugin. Best of luck in resolving it. I would suggest checking out Stack Overflow, and the Gravity Forms documentation.

You do look like you’re on the right path here, you need to write a gravity forms hook upon completion to update the dg_application folder upon complete.

https://docs.gravityforms.com/gform_after_submission/

Good Luck!

Hey Brandon,

Good idea, and it’s something that we do want to do. Perhaps I can find some time this week or next to get it up there for future development.

-Chris.

Hey Croakey88,

Whenever we’ve encountered this issue, it’s been due to a need to re-create the form in HubSpot… weird, but it resolves the issue. Previous support requests on this channel, and a few others, all mention this.

Hope that helps. I do want to resolve this issue on our end better, but unfortunately it’s ridiculously difficult to pin down.

Hey mktgessentails,

“HubSpot for WordPress” is a deprecated plugin that is no longer managed by HubSpot… They have people switched over to using “HubSpot Tracking Code for WordPress” https://www.ads-software.com/plugins/hubspot-tracking-code/ instead, but if there’s a conflict there, I definitely need to take a look.

Can you confirm the plugin you were using that was conflicting?

Also, if you went to Forms > Settings > HubSpot you could’ve enabled the tracking code via there, instead of manually entering it.

Thanks for the update. I will have to take a look and see if those plugins have new conflicts.

Thanks,
-Chris.

Hey pagetopixel,

Sorry about this, I could’ve sworn I answered you earlier this week… the forms send, by default, the form name and current page, and you are given an opportunity to override it.

This is part of the “HSContext” which sends the cookie, and some context for HubSpot to determine if the user is new or not, and where they’re coming from.

You have two “apply_filter” functions accessible to you at that point.

'pageUrl'   => apply_filters( 'gf_hubspot_context_url', site_url() ),
'pageName'  => apply_filters( 'gf_hubspot_context_name', rgars($form, 'title') ),

Can you clarify where the “collected forms” are that you’re referring to? I will look into manipulation based on the “Lead Source” but I wasn’t aware that it was something I could manipulate during form submissions.

Unfortunately, this plugin does not migrate EXISTING form submissions.

That could be something we have in mind for a future implementation.

I would suggest an export of the form entries, cleaning up the spreadsheet… there’s bound to be tools out there for importing CSVs

https://knowledge.hubspot.com/getting-started-with-hubspot-v2/how-to-import-a-list-of-leads-and-contacts-into-your-account

??

That’s a very good question,

I’d be curious how to implement it. Unfortunately that’s not in the cards right now (priority is implementing oAuth 2.0 which HubSpot is switching to soon)…

My guess would be to look at the hooks for the Partial Entries addon, and during the “save” action for that, trigger my HubSpot submission call as well. Unfortunately that’s dependent on a flexible plugin on GF’s part (which might be the case).

We’ll have to look into that for the future.

Jann and Trey,

I’ll look into this. However, it’s likely that HubSpot is starting to drop API handling in favor of oAuth. I will be dropping API in newer versions as well.

Jann, are you using API Authentication as well?

Hey heavymark,

Yea, there’s a cache of about 15 minutes, I believe. We’re working on implementing HubSpot’s oAuth 2.0, so I’ll look into clearing out the cache during Feed maintenance, to keep that list fresh.

Thanks for the heads up.

Hey,

Can you please confirm by going to the Forms in HubSpot, and clicking the Submissions number? (Contacts > Forms from the top navigation)

We had noticed that the submissions would still show “0” even though there were indeed submissions.

Also, the API Key method of connectivity is highly discouraged by HubSpot. I would recommend you using the oAuth connection instead, as it’s more secure and reliable.