Sources (under Source Codes in the Data module) are a great way to track where your leads come from, helping you make decisions about where to invest recruitment time and energy in future seasons. On this page, we will go over how Source Codes work as a data source and what that means for your imports and segments.

Fundamentals of Source Codes

When you are pulling a segment filtering for Source Codes, you might notice that there are two properties: Sources Alias and Sources Alias List.

Sources Alias filters for the Source based on its title or name, such as "College Board" or "Open House." Sources Alias List filters for the Source based on its taxonomy or GUID, such as "abc.taxonomy.1234567." The taxonomy or GUID is different from the "Code" you see when you create the Source Code in the Data module; the GUID is automatically generated by Element451 and you do not need to know what it is for successful imports and exports.

In the past, creating a segment using Sources Alias List would pull anyone who had that Sources Alias List (GUID) and/or the corresponding Sources Alias (name). In order to clean up Source data, Sources Alias List now only filters for the GUID.

How to Import and Export Sources

Due to this change, it is now more important than ever that you import Source data correctly, automatically mapping the Source Code name to its GUID. This way, you can ensure that all of your imported data appears when you filter using Sources Alias List. To successfully import Source data with the corresponding GUID, be sure to use the relevant automapping. Be sure to map to "Sources - Source Code (Alias) - Custom" for Source Codes and "Sources - Source Code Segment - Custom" for Source Code segments. See the sample export below.

Note that this will only work properly if the Source Code and Source Code Segments already exist in the Data module. ˆYou can learn more about adding Source Codes here.

How to Create Segments and Capture All Source Code Data

If you have imported Source data using just the name - and not mapping to the corresponding GUID - it is recommended that you use both Sources Alias and Sources Alias List when creating a segment using existing Source data. An example of how to effectively use Sources Alias with a text filter is shown below. Note that the values are separated by a "|."

Note: If you do not want to use both Sources Alias and Sources Alias List each time you filter for Source Codes and would instead rather clean up the Source Code data, you can add the Source Code GUID to data points currently missing it. You can first export a segment of users for which the field exists but does not have a value. You can then import that segment using the system automapping described above.

Note 2: All of this information also applies respectively to Source Code Segments, which are subsets of Source Codes.

Did this answer your question?