Learn how to effectively use Custom Fields within your Campaign to enhance tracking capabilities.

Found a mistake? Is there a missing topic? Hard to read? Let us know

Custom fields allow you to add custom UTM Parameters (tracking tags) for each of your campaigns. This enhances how you track sources of supporter traffic in detail.

đź”— For information on how to add UTM parameters to links for the Checkout modal and Campaign Pages, visit our dedicated support article.

​
Create a Custom Field for Your Campaign

Custom fields can be created individually for each campaign by navigating to the Settings tab within a campaign. To create a new campaign with identical custom fields to an existing one, leverage the Campaign Cloning option.

Under Name, specify the identifier for the custom field (e.g., “donor_traffic_source”).

⚠️ Avoid using “Element” as a custom field name, as this term is reserved for Givetly’s internal tracking. Use the Element type field to track the Element source.

Decide if you’d like a Default value. For example, set “email_marketing” as a default if most supporters come from email but you’re interested in tracking others. Default values can also be specified for particular Elements.

Custom field names must be alphanumeric, with no spaces, capped at 50 characters for names and 200 for values. There’s no limit to the number of custom fields per campaign.

ℹ️ Custom field values will persist within a user’s session, displaying each time a supporter donates.

​
Where Values from Custom Fields Appear

Custom field information can be accessed in various locations:

  • Donation records: Within the Donations tab in the dashboard. Each donation includes a Custom fields subsection.
  • Exports: Include custom field data when exporting, as part of the custom export template.
  • Integrations: Custom field names appear in integration mapping rules.

⚠️ Custom field values may not appear in the URL, but will always be recorded in the Dashboard.

​
Example Use Cases

​
Example 1

Context: A campaign uses multiple channels: social media, influencer collaboration, and email.

Task: Identify which channel brings the most supporters to the campaign’s Checkout modal.

Create the Custom Field: Name the custom field “traffic_channel” with “organic” as a default value. URL examples:

  • mycharity.com/?traffic_channel=smm
  • mycharity.com/?traffic_channel=influencer
  • mycharity.com/?traffic_channel=email
  • Default: mycharity.com/?traffic_channel=organic

Result: Track donations’ origins through the Donations tab and export this data.

​
Example 2

Context: Campaign partners with a hotel chain, matching donations for valid membership card numbers.

Task: Record membership numbers in the CRM for verification and donation matching.

Create the Custom Field: Create a field (e.g., “member_number”). No Default Value is needed. Example URL:

  • mycharitycampaign.com/?member_number=1234567

Result: Membership numbers can be viewed linked to donations and exported as needed.

​
URL API

Custom fields are compatible with the URL API for dynamic value assignments. Example usage:

https://ropsi.org?form=DonateNow&appeal_code=fy2023

In this example, a custom field, appeal_code, is set to fy2023 using the URL API.

Employer MatchingDesignations in Campaigns