Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Every Online Actions form has a section in the "Basics" step called "Track Your Efforts". Audubon uses this section to record important information about the form submissions and the people who made the submission. This is done using "Source Codes" and "Activist Codes". Source Codes are the most important, so we will start there.

Source Codes are for Financial Information (among other things)

In EveryAction, Source Codes are special: they brand any new contact applying a Source Code marks a new record with the details of the interaction — specifically, that it was this person's first interaction with our systems. The Source Code Glossary can tell you more about how that works, but here we'll talk about something else they do: act as a carrier for finance information for any time a submission has with a dollar amount associated with it.

To do this, Source Codes are configured with two sort of "sub-codes" you're probably more familiar with: General Ledger Fund Codes and Solicitation Codes. Each contribution form or ticketed event form MUST have a Source Code configured with containing both of these, or the form's submissions won't be able to sync with Audubon's financial systems.

So if you're setting up an online contribution form or ticketed event form, there's some particular information Audubon's Finance department need before we can set up a source code for you. Each type is outlined in our article about online form code requirements.

Tickets that cost money must have that money properly coded. This is so that the money will go to the proper program, and so our reporting to the IRS is accurate. It also helps to gather the information you'll need for transparency to the ticket-buyer about tax-deductibility. 

Here is the breakdown of what's needed for each type of event. Please send to; the info will be routed to the proper authorities. In three days or less, I will then respond with a new Source Code for you to use on your ticket form.

A Note About Solicitation Codes

To create a Source Code for paid tickets I also need to enter something called a "Solicitation Code". I have asked upwards of 40 people to provide proof of one of these codes being used in practice, and no one has been able to provide such proof. 

Still, if I don't use one, it breaks the sync. So I can just use a random one if you don't care about Solicitation Codes.

Fundraising Events

These are usually events where the ticket price has a significant portion that is a donation, rather than cost. What we need for these is:
  • Event name, date, and location
  • The General Ledger Fund Code for the DONATION component of tickets (e.g. 1-111-4000-10-60020)
  • The project code for the event (e.g. SE0001)
  • Solicitation Code, or an acknowledgement that you don't care about them
  • The total cost of all ticket and/or sponsorship levels (please do NOT send details about the benefits of each level)
  • The fair market values (FMV) of all ticket and/or sponsorship levels

Since events always cost money, fundraising events will always have FMVs for each ticket or sponsorship level. If they don't, it's one of those:

Non-Fundraising, Program-Type Events that Cost Money

Anything that costs money but isn't a donation is "program fees" or "earned income" or what have you. So for these, we only need:
  • Event name, date, and location
  • The General Ledger Fund Code for the earned income component of tickets  (e.g. 1-111-4000-10-61041)
  • Solicitation Code, or an acknowledgement that you don't care about them
  • The total cost of any tickets offered

Unfortunately, due to some rigidness in our financial systems, Audubon can't support additional donations on ticket forms for earned-income program-type non-fundraising events at this time.

Free Program-Type Events

If you want to make a ticket form to let people get free tickets to some event you're throwing, we need:Nothing, because nothing goes into our sensitive financial systems

Activist Codes are for Flagging Interests and Affiliations

Let's say you have an online registration form for a program at the Silver Bluff center in South Carolina training people how to be beach stewards to stop people and their pets from disturbing beach-nesting birds. There's a lot of things you can say about a person who submits this form:

  • They're affiliated with Audubon South Carolina
  • They're affiliated with the Silver Bluff Center
  • They're interested in volunteering for Audubon
  • They're interested in Audubon's coastal programs
  • They want to be a beach steward (but haven't necessarily done it yet)
  • They might be some kind of robot who hacks forms

For each one of these statements, there's an Activist Code. By adding these activist codes in the appropriate part of the "Track Your Efforts" section, you're ensuring that any submitter gets flagged with each of these.

If you think there should be an activist code and you can't find it — or, just to see what's going on — check out the list of all of the activist codes Audubon currently uses (as of never, this page doesn't exist yet). If you see something there and don't see it as an option in the "Track Your Efforts" section, email to request it — we probably need to expose it to your committee.