When a lead is captured in MetaLocator, if the page was loaded with UTM URL parameters in place, those codes will be saved with the lead. There is no special configuration to implement this strategy.
For more information on how to use UTM codes, and what they are for, see here.
For example, if the page on your site where the locator is installed is yourwebsite.com/locator/, then the same page with UTM parameters would be yourwebsite.com/locator/?utm_source=newsletter&utm_medium=web&utm_campaign=2023_sale
If a lead is then captured by the locator on that page, it will be found in MetaLocator's Lead section with the same UTM codes as shown below:
These UTM codes have also been added to the PaaS API response and the lead bulk export file, found under Leads > All Leads > Export.
Passing UTM Codes to MetaLocator
UTM codes are traditionally for inbound data source tracking and will be automatically taken from the URL of the page on which the MetaLocator interface is installed. To programmatically pass UTM parameters to the MetaLocator Interface, they can be passed as deep linking parameters.
For example, if the page on your site where the locator is installed is yourwebsite.com/locator/, then the same page with forced UTM parameters would be yourwebsite.com/locator/?ml___utm_source=newsnetter&ml___utm_medium=web&ml___utm_campaign=2025_sale
Like all deep linking parameters, these can also be provided via JavaScript as follows:
var ml___params = {
'utm_source':'newsletter',
'utm_medium':'web',
'utm_campaign':'2025_sale'
};
In the case where both URL parameters and ml___params values are provided, the URL parameters will be preferred.