Track Site Interactions with Source Codes

Source codes create and function within a session and in conjunction with constituent registrations. The session starts when a visitor arrives at your website and ends when the visitor leaves. If a visitor interacts with site content where you defined source code and then registers as a constituent during the same session, the system tracks the visitor's activity and records the source code in Constituent360.

With source codes, you can:

• Understand where your constituents come from

• Understand what drives actions on your site

• Identify affinity groups or partners online who drive constituents to your site

• Determine cost effectiveness of banner ads hosted on external sites

• Evaluate what sections of your site are most effective at driving users to take action

Yes, Luminate Online automatically tracks some interactions. These include:

• Donations

• Action Alerts

• Survey responses

• TeamRaiser registrations

• eCommerce purchases

• Event RSVPs

• Ticket sales

• Site registrations

You can find statistics for these here:

Interaction	Available Reports
Donation	Fundraising Analysis Report Donations by Source Report
Action Alert	Advocacy Analysis Report Alert Respondent Report
TeamRaiser registration	Participant Registration Report
eCommerce	Orders by Source Code Report

Source codes and subsource codes are similar in that they're both used to track information about a constituent, but subsource codes are an optional secondary value used to help distinguish one source from another.

For example, if an eCommerce store offers digital music downloads on demand, you might choose Digital Music as the value for the source code. You can use subsource codes to identify the departments the constituent viewed or purchase, and you might choose Classical and Pop as the subsource codes.

Example 1

You configure source and subsource codes for your store with subcategories of Mugs, Hats, and Books. A visitor purchases a hat and then leaves your site without registering. No source or subsource code values are recorded for the visitor and the session ends. If the visitor returns an hour later and registers, the source and subsource code values for the hat-purchase interaction are not recorded because the purchase occurred in a different session.

Example 2

A visitor registers as a constituent with your site but leaves with no further interaction and the session ends. When that constituent logs in two weeks later, their activity is now recorded and associated with their profile in Constituent360. The source and subsource code values associated with their first interaction, purchasing a hat in your online store, are recorded in Constituent360.

Example 3

A visitor registers as a new constituent but does not interact with your site. No source code is associated with the registration process, which means no source or subsource code values are recorded for the new constituent. Even if the visitor submits an action alert that has its own default source and subsource codes, no values will be recorded.