Skip to main content
Together
Sign in

Set up tracking codes

Tell Together which inbound donations count as Federal Campaign Account (FCA) money. Cap and disclosure totals downstream depend on this answer.

A tracking code is a free-text label that travels with a donation, usually from your CRM. NationBuilder stores it as the donation's tracking code; Raisely uses campaign codes the same way. Together cannot guess which codes are FCA-bound and which are not, so you flag the FCA ones here.

Before you start

You need:

If you have not connected a CRM yet, do that first at Settings -> Integrations. Together can sync without tracking codes; you can come back here later.

Steps

  1. Go to Settings -> Integrations. The FCA Donation Filtering card sits below the CRM connection cards (NationBuilder, Raisely).

    The Integrations settings page with fields for tracking codes used to classify fundraising sources.
    Settings > Integrations.

  2. For each source you care about (NationBuilder, Raisely, Gateway, Checkout link, Recommendation sets, Manual), configure two things:

    • Selected codes. The tracking codes from this source that count as FCA. Donations carrying any of these codes are FCA; everything else from this source is not.
    • Include no-code donations. A checkbox. When on, donations from this source with an empty tracking code are also treated as FCA. Often paired with a Selected codes list when your CRM does not stamp every donation with a code.

  3. Add codes one of two ways:

    • Click an Available code. Together lists every tracking code it has actually seen on a donation from that source. Click one to add it to Selected codes.
    • Type a code. Use the free-text input if you know about a code that has not yet appeared on a donation.

    Remove a Selected code by clicking the x on its chip. Removal saves immediately; adding does not (so you can stage several changes before saving).

  4. Click Save Changes.

    • If this is your first save (no prior FCA config), the save lands silently and new donations from now on are classified against the new rules.
    • If you previously saved any FCA config, Together opens a confirmation dialog warning that the change may re-classify donations that were already counted toward a disclosure period. The dialog gives you two choices:
      • Save Without Reviewing keeps prior disclosure totals intact.
      • Save & Review Disclosures triggers a sweep that re-evaluates already-flagged disclosure crossings against the new rules and reports how many disclosures it flagged for review.

How classification works

FCA-or-not is a derived value, not a column on the donation row. Every time Together reads a donation for cap or disclosure purposes, it runs the donation's source + tracking code through your current FCA rules and decides on the spot.

This means changing your FCA rules retroactively re-classifies every past donation. The change is immediate; there is no migration to wait for. The "Save & Review Disclosures" path only re-evaluates previously-recorded disclosure period totals against the new rules; the underlying donation classification updates the moment you save.

The "Save & Review Disclosures" dialog is your guardrail against quietly invalidating disclosures you have already filed. If your numbers have already gone to the AEC, choose Save Without Reviewing and talk to your compliance lead before triggering a recalculation pass.

A worked example

Your NationBuilder has two tracking codes you care about:

Your Raisely tags every campaign and you treat all of them as federal. Your direct Gateway donations come from your federal fund landing pages and never carry a code.

Configuration:

SourceSelected codesInclude no-code donations
NationBuilderFED_GENERALoff
Raiselyevery Raisely codeon (catch the rest)
Gateway(none)on

Result: every donation from Raisely or Gateway is FCA, NationBuilder donations with FED_GENERAL are FCA, everything else is not.

What to do next