Using AFL UTM Tracker – not parsing to Google Sheets

when you manually open gravity entry and click “send to Google” button , plugin will send all fields
but problem is with auto submission , your utm plugin saves utm data at the end and plugin sends to google first

Thanks for the prompt response. I also queried with AFL, they suggested the same issue.

‘Ask CRMPerks to allow all add-ons to have finish processing the form input data during submission stage before posting to Google Sheet.

Best if they can follow like all the Gravity Forms official add-ons which uses the Notification stage.

1. Form submission stage.
2. Confirmation stage.
3. Notification stage.

Can’t remember if stage 2 or 3 comes earlier.

And if they use the Gravity Forms Add-on Framework, you also wouldn’t need to create the hidden fields.’

Appreciate this is one user request, but is this likely to be a change you will make in the future to your add-on?

Hey @shilldiy,

We will get back to you soon.

Thank You – Sam

Great thanks and appreciated ??

Your welcome

Hi everyone, sorry that we got confuse with the terminology of Notification stage which used by Fluent Forms.

Gravity Forms uses the Feed terminology. Notification is just for email notification.

To give a little background on the AFL UTM Tracker flow:

1. During the gform_entry_created action hook, the AFL UTM Tracker plugin saves the attribution data into the entry meta and also process any dynamically populate hidden field. Since this is an action hook and not a filter hook, the connector plugin could not access the updated data when submitting to Google Sheet.

https://docs.gravityforms.com/gform_entry_created/

2. During the gform_entry_post_save filter hook, the AFL UTM Tracker plugin populates and return the updated $lead variable with the attribution data so that any processes can later access the attribution data.

https://docs.gravityforms.com/gform_entry_post_save/

To solve @shilldiy issue, the Connector plugin would need to submit to Google Sheet during the Feed Processor stage or any stage after it. We know this is not an easy decision to make and we leave it up to you.

Feel free to suggest any solution that we can take on our codes as well.

On the side note, just to clear things up, our email to shilldiy did not begin with “Ask CRMPerks to allow all add-ons…” as posted above.

Instead it began with “I would recommend CRMPerks to allow all add-ons..”

Thanks both to the team at AFL and the team at CRM Perks for investigating this – wonderful if these two plugins work together.

Apologies on my part for any errors in messaging between the two plugin development parties on this post, they’ve both responded really quickly and professionally when raised so I’d just like to thank them in advance for their efforts (and hopeful resolution!).

TIA