Per the original question we would like to pass Query Parameters and Referrer URL on form submission. We can do hidden fields with a timestamp appended, that isn't an issue. We have built all our form fill behaviors based on triggering from query parameters and referrer url because they work so cleanly with the form fill triggering system for initial routing. Relying on hidden fields makes us subject to race issues.
I may have misunderstood earlier points in the thread so I'll restate. The proposition to solve this issue would be to instead use hidden fields with appended timestamps, and then trigger off of Data Value Change and Person is Created. My understanding is handling the routing via that method would eliminate the race conditions. Please correct me if I'm incorrect here.
The issue we're in is that it would be a significant task to restructure away from referrer and query parameters. As a due diligence task I'm vetting any other options. If the iframe method is a miserable way to handle this, and I shouldn't consider it as an option then let me know and I'll take it off the table. I'll certainly take Sanford's word for it hah.
As for the original issue. We can restructure our form fill logic, but I'm very open to any other options you can think of for customizing Query Parameters and Referrer URL.
Appreciate the help Sanford!
... View more
@SanfordWhiteman In your reply you mentioned an iframed page that submits the form. I'm experimenting with having forms submit via an iframe, but I'm not having much luck so far. Would you have any links, examples, etc? If not could you briefly explain the process?
Thanks in advance!
... View more
Thanks very much for your response Sanford.
Three questions on that process:
So I'm understanding correctly, the timestamp would ensure that every submission (including those with the same values) would trigger a data value change. Does appending the timestamp trigger any other effects?
In the case where we use Data Value Change, does that also trigger on a new form submission? From our experience we've noticed that net new records might inconsistently trigger a value change on form submission unless a flow is used.
We would like to continue using the Trigger system to keep our program enrollment clean, but in this case we would need to check both the query string (in your example it would be a custom field with the query string and a timestamp), in some cases we would also check the referrer and in others we would need to check what page the embedded form was submitted from. We've ran into timing issues using filters and fields not being populated in time to route correctly. Otherwise using two triggers together are viewed as an OR statement. Any tips?
Example, triggers and filter where we've noticed inconsistencies in timing where data is available yet to filter:
Example, triggers together are viewed as or statements:
... View more
We use a universal form setup. For example we use a single content form for all content downloads for easier management. When a visitor completes a form fill we use the Referrer URL and Query string to understand what content piece was downloaded, and the UTMs in the query string for attribution.
Currently we're using session cookies to preserve UTM parameters, and when a user views a page with a marketo form we rewrite the URL history to include the UTMs in the query string. We do this so we're able to use the form-fill triggers to analyze the query string and funnel the contact for appropriate attribution routing.
We are passing custom hidden fields for UTMs and a custom referrer full URL, but we've had more success relying on Querystring in the trigger for initial routing.
However, having the history rewrite to include the full query string is problematic. For example, we're considering having a newsletter signup form in the footer of all pages and thus the saving querystring data would populate on all pages which is unsightly. It can cause analytics inconsistencies in some cases. etc.
Is there manual way to populate a form's querystring value with data we provide? Same question for referrerURL.
... View more