Introduction

In LoftyWorks, the "source" is a very important piece of data associated with each and every contact that exists in the system. "Source" refers to where the contact originated (e.g.Rightmove, Zoopla, etc.). This source can be used to filter contacts, track ROI for specific sources, and even establish contact routing within LoftyWorks to distribute based on specific sources. Some sources can be customised and other sources are built into LoftyWorks by default. Source names can have up to 100 characters. This article will explain how LoftyWorks selects the sources for contacts. 

Summary

• Adding Contacts Manually
• CSV Import
• Email Parsing
• API
• UTM Settings
• Editing Sources
• Source Customisation
• Facebook/Google Registration

Adding Contacts Manually

If a contact is added manually via the Contacts page in LoftyWorks, the source will default to "Other". However, this can be changed when adding the contact or later as necessary. See Add a Contact.(link)

There is a permission that will allow an account admin to restrict users from changing a contact's source. By default, this permission is ON for all LoftyWorks users. When the permission is OFF, the Source field is greyed out for all contacts this user can see.

For more information, see Team Permissions for company-type accounts or Enterprise Permissions for Enterprise accounts.

CSV Import

When a user imports a CSV document into LoftyWorks (see Contact Import), the contact source is typically available as a column/field in the actual CSV that is then matched as the source (see screenshot below). However, if this field is not present, the source defaults to "CSV Import".

Email Parsing

If a contact comes in through the mail parser, which is the majority of all contact sources (see Contact Capture Sources), the source will be the name of the service where the contact originated. For a list of these names, as they will appear in LoftyWorks, you can reference the following section under Personal Settings > Contact Settings > Contact Capture> Contact Capture Settings:

API

The contact source should always be pre-defined in the code that connects any direct API integration to LoftyWorks. If not, the source will be "Other".

UTM Settings

UTM is used to tag contacts and better monitor campaign ROI. Users can add UTM codes to URLs and have that data added to contacts automatically as they are brought into LoftyWorks. Google's Campaign URL Builder is a useful way to set these up. 

There are three different parts to how this works:

1. Import utm_source as contact sources. This is ON by default and cannot be turned off. If a contact registers via a campaign or URL with an associated "utm_source", that source will be assigned to the contact automatically. A new source will be created if it does not already exist.
2. Import utm_campaign as contact tags. If a contact registers via a campaign or URL with an associated "utm_campaign", that campaign will be recorded for that contact automatically as a tag. A new tag will be created if it does not already exist.
3. Import utm_content as contact tags. If a contact registers via a campaign or URL with an associated "utm_content", that content will be recorded for that contact automatically as a tag. A new tag will be created if it does not already exist.

To edit or set this up, navigate to Personal Settings > Contact Settings > Tags  > UTM Settings:

Editing Sources

All sources are located under Company Settings > Contact Settings > Sources. Some sources cannot be edited, but they can be hidden or deleted and replaced. This is the page that would be used to mass update a source. 

When a Source is deleted, it must be replaced on any contacts that the Source was connected to.

Source Customisation

This feature allows users to customise the Source for contact capture providers. To access, navigate to Personal Settings → Contact Settings → Contact Capture → Contact Capture Settings:

Here, the Source that appears on the Contact profile can be updated to any source that has been created in the CRM:

When changing the Source, the user must confirm on the pop-up: