In performance marketing, it is often helpful or necessary to pass parameters to the flow and the visitor's response, such as
gclid to identify and track the user. These parameters are usually found in the URL, e.g.
heyflow.id/myflow?utm_source=Google&utm_campaign=spring01. This URL contains the following two parameters:
With Heyflow, passing these parameters from the URL is quite simple.
To enable UTM parameters head over to the Settings page of your heyflow. On the Tracking tab, make sure the Pass URL parameters option is on.
Important: The query string like
?utm_source=Google&utm_campaign=spring01 must follow the path, e.g.
heyflow.id/myflow?utm_source=Google&utm_campaign=spring01. The (optional) screen anchor, e.g.
#start must be the last element of the URL:
If you have embedded your flow on another page, you have to complete one more step – shown below.
If you have embedded your heyflow on a website, you may want to pass all the parameters of the parent website to the heyflow.
For example, your heyflow could be embedded on your landing page
my-website.com and the parameter could be passed in the URL, e.g. like this:
With our website integration script, URL parameters from the parent page, can be automatically passed to your heyflow. You can find the setting Pass URL parameters for each website provider. Activate this option and (re-)insert the script onto your website (the attribute
pass-parameters should now be included in the
<heyflow> code snippet).
If you have both settings activated, 1) in the heyflow tracking setting and 2) in the website embedding settings, the URL parameters of the parent website will be automatically sent along with the response of each flow visitor.
Bonus: Manually add URL parameters to embedded Heyflow
Another method to add URL parameters to your (embedded) heyflow, is to define them in the
<heyflow> tag directly, via the
url-parameters attribute like so:
The URL parameters defined here in the tag will be added to those passed read the URL.
url-parameters attribute must be filled when the heyflow is initialized. Updating the attribute after the heyflow has been loaded will not pass updated parameters.