Sources in Element451

Be familiar with Sources in Element451 before continuing.

In these examples, we'll create Custom Sources and automatically apply them to contacts when needed. These Sources will then be visible in the Sources Dashboard, and can be exported in batch when repeating on Source.

In this example, we'll add a Custom Source to each student that attended a college fair. We'll assume that you've tracked Event attendance using the Event's module, and already have an event for this particular college fair.

Define a "College Fair" Source Code and add Source Segments for the Fair. Add additional Source Segments for each Fair.

Create a workflow rule to automatically assign the "College Fair" Source Code to a student once they register for the event.

Set Step Condition: Use the "DOES NOT HAVE" operator on the Sources (All Properties) filter to ensure that the rule only applies to students who don't already have the College Fair Source associated with their contact. This prevents adding the same Source twice.

Specify the Rule Step Action: In the workflow action settings, choose "Add custom source to user." Then, select the appropriate "Source Alias" (e.g., "College Fairs") and "Source Code Segment" (e.g., "Roosevelt HS").

Expand this Rule with more steps for each College Fair attended.

In this example, we'll create a Custom Source for a contact based on the UTM values in their Form Submission URL.

Note that Form Submission activities capture the URL of the page at which the Form was submitted, including marketing data such as UTMs that were appended to the URL of the page. Learn more about Form Submission activities and Embedding Forms.

In this example, we'll assume that you're running an ad on Instagram for a psychology program. You've configured the ad in Meta Ads Manager and have added UTM parameters to the destination URL of your ad. The URL is to an Element451 Page with an Element451 Form embedded.

This is a logical exercise we're we'll determine how to represent UTM values as Custom Sources in Element451. Keep in mind, Element451 Source's only have two levels or hierarchy, while UTMs can have up to five (Source, Medium, Content, Campaign, Term). Decide which two UTMs to save as the Source.

In this example, we'll use the utm_source value as the Source Name, and the utm_campaign value as the Source Segment.

With our Source Name and Source Segment decided, we'll create a Source Name for "Instagram" and a Source Segment for "Psychology Retargeting", plus any other campaigns we may be running.

Create a workflow rule that assigns a Source Code based on the UTM data of the form submission URL. The Rule can be triggered by a form submission or by joining a Segment.

Set Rule Conditions: The step should only apply the Source if the contact has a Form Submission with specific UTM values and if the contact does not already have a Source of the same kind. Use to filters to reflect this:

Specify the Rule Step Action: If the conditions are met, the step should apply the Source to the contact.

Expand this Rule with more steps for each UTM Source and UTM Campaign you wish to track.

In this example, we'll add a Custom Source to contacts whose information was purchased from a vendor, such as College Board. We'll assume that the vendor has sent us a .csv data file and we've already created an Import Task for this file.

Define a Source Code for "Purchased List" and create Source Segments for each list provider. For example, "Cappex", "College Board", "EAB" and so on.

Map Calculated Columns at the bottom of the mapping tab to apply the Source Code and Source Segment GUIDs based on the list provider. For example, adding "training.taxonomy.4119735" to the formula of the Source Segment column will assign the College Board Source Segment to the contact.