Custom codes in StockCrowd are tools you use to segment and analyse donations more efficiently. These codes let you categorise donations, and they are reflected in Notifications (webhooks) and in your transaction reports.

You can create custom codes at two levels: at organisation level, which applies to all your campaigns, or at campaign level, which applies only to that specific campaign.

There are two main types of custom codes you can set up depending on what you need: organisation-level codes and campaign-level codes. Each one has its own characteristics and a different scope.

At organisation level, you set up the codes from Register data: select Edit and go to the part where you can add the custom codes. This is the central place where you set the codes that will apply to several campaigns.

The settings screen is where custom codes are managed. This is the central admin area for your organisation-level codes.

To add a new code, click the cross icon (+) and assign the scope it will have. The scope determines where the code will appear: you can choose for it to appear on all campaigns and P2P pages (challenges), only on campaigns, or only on challenges. That way you have different scopes available depending on what you need.

This screen is where you select the scope of the code. The available options let you choose whether the code will apply to all campaigns, only to campaigns, or only to P2P pages.

Next, you assign the code name and the code value. The code name is what will appear as a heading in your reports, and the value is the content that will be reflected in donations.

This screen is where you write the code name and assign its value. This is the step where you define exactly what information each custom code will contain.

This use is ideal when you want all your campaigns to share the same code and value. It is especially useful for StockCrowd integrations with a CRM, or to tell donations that come from StockCrowd apart from donations from other sources.

If you leave the code value blank at organisation level, you have the flexibility to customise it in each campaign without having to write the code name again. You only need to add the value, so each campaign can have a different value while keeping the same code name.

Campaign-level codes are created in the same way as organisation-level codes, but the main difference is that they only apply to the specific campaign where you set them. For that reason, you cannot select the scope. To set them up, go into the campaign and then Content → General data, click Edit, and the option to configure the codes will appear.

The process for adding a new code is identical to the one you use at organisation level. One important point to remember is that codes already set up at organisation level appear by default in your campaigns, and you cannot edit or delete them from campaign level.

This screen shows the code configuration at campaign level. Organisation codes already appear there, and you can add extra codes specific to that campaign.

To change the value of a custom code that already exists in a campaign, follow the steps below:

Understanding how codes behave when you modify, add or delete them is key to keeping your data consistent. The behaviour depends on the level at which each code was created (organisation or campaign) and on its inheritance relationship.

When you create a code at organisation level, it is passed down automatically to the levels below (campaigns and their P2P pages), as long as that code does not already exist at that level. If you have already changed the value of a specific code in a campaign or challenge, the system respects that local setting: changes you make later at organisation level do not overwrite the value you defined locally.

Changing the value of a code does not alter historical data. To guarantee the integrity of your reports, the system saves a "mirror" copy of the code at the exact moment each transaction is created. That means that even if you change the value of a code later on, reports for earlier donations will still show the value that was in place when each payment was made. Only new donations will take the updated value.

Deleting a code at organisation level deletes it in cascade across all the campaigns and challenges linked to it. As for editing or deleting locally: if the code was originally created at campaign level, you can edit or delete it locally; but if the code comes from organisation level, that option is restricted locally. To change it, you have to do it from the Register data section of your organisation. This keeps the code structure consistent across the whole platform.

The scope of a code determines exactly where it will appear and where it can be used. Depending on the scope you select at organisation level, the code will be available in different places within your platform.

The available scopes are:

There is one important exception: when you create custom codes at campaign level and that campaign is a P2P campaign, you can assign the scope. The options in that case are for the code to appear only in the Marketplace, only on the P2P pages of that campaign, or in both.

This screen shows the scope options specific to a P2P campaign. You can select whether you want it only for the Marketplace, for the P2P pages of that campaign, or for both, which gives you more control over where each code appears.

Custom codes, whether at organisation or campaign level, appear automatically in your reports. They are shown as columns with the code name, and the value assigned is the content that appears in the corresponding cells for each donation.

In your report, custom codes appear as extra columns. Each donation shows the corresponding code value in its row, so you can analyse the segmented information easily.

A Query String is a text string containing parameters in key-value format, placed at the end of a URL after the question mark (?). It is used to pass additional information to a web server, such as search criteria, filters, identifiers or data for a web page.

With this feature, custom codes can be updated from a URL. As long as the code has the "Updatable" option ticked, the default value given to a code can be overwritten if the URL contains a parameter with a different value. This gives you the flexibility to change values dynamically depending on the source of your traffic.

This is the configuration of a custom code with the "Updatable" option ticked. It means that the value of this code can change depending on the parameters you add to the URL.

This feature applies at both organisation and campaign level, and it is especially useful for identifying where donations come from in marketing campaigns. You achieve this through the code passed in the URL from the Query String, which lets you track exactly where each donation comes from.

This is a normal campaign URL with no additional parameters:

That URL is a standard campaign address. It is the base URL you will use as your starting point.

But to use this Query String feature, you need to modify the URL by adding a parameter after the question mark. This lets you customise your tracking according to your traffic source.

Let's say the same URL is going to be used on social networks such as Instagram and Facebook. With this technique you will be able to identify where donations come from, because the URL will contain the parameter you added, which is specific to each social network.

Instagram:

This URL includes a parameter specific to Instagram. When you use this URL on Instagram, you will know that the donations arriving through this link come from that platform.

Facebook:

This URL contains a different parameter for Facebook. When you share this link on Facebook, the code will capture a different value, which lets you identify donations from that social network specifically.

Even if other organisations help you spread the word about your campaign, you can add different parameters to find out which of the organisations helping you share the campaign each donation came from. This is useful for collaborations and for thanking your partners for their help.

At report level, you can view all this data and identify exactly where each donation comes from. The code captured in the Query String appears in your reports, giving you a complete analysis of where your donations come from.

In your report, the Query String values appear in the custom code column. This lets you identify quickly which source sent each donation.

You can also view these codes in Notifications (webhooks). Notifications let you see changes and new donations with their corresponding parameters in real time.

In notifications you have the full details of each transaction, including the custom code from the Query String. This is especially useful for integrations and for monitoring donations by source in real time.

Custom codes give you much finer control over your donations and let you adapt the information completely to your specific needs. This is a powerful tool for understanding and optimising your fundraising efforts.

A custom code at organisation level applies to all the campaigns within your organisation, which is useful for keeping things consistent and for global analysis. A code at campaign level applies only to one specific campaign, so you can have more tailored codes for the particular needs of that campaign. Organisation codes appear automatically in all campaigns and you cannot edit them at campaign level.

You can use the Query String feature to track donations from different sources. You need to create a custom code marked as "Updatable" and then add specific parameters to your campaign URL. For example, you can use ?source=instagram for Instagram and ?source=facebook for Facebook. Each donation will capture the value you included in the URL, so you can identify exactly where each donation came from in your reports and notifications.

If you leave the code value blank at organisation level, you have the flexibility to customise it in each campaign without having to write the code name again. You only need to fill in the value in each campaign where you use it. This is a practical way to reuse code names with different values depending on the campaign.

Changing the value of a code does not modify the donations you have already received. The system keeps the value the code had at the moment of each transaction, thanks to a "mirror" copy that is saved when each donation is created. That is why historical reports are not affected when you change a value. Only new donations will take the updated value.

Custom codes appear automatically in your reports as extra columns, where you have the values assigned for each donation. They also appear in notifications (webhooks) if you use integrations with other systems. The specific place where the donor sees or interacts with the code depends on the scope you selected: on all campaigns and P2P pages, only on campaigns, or only on P2P pages.

You cannot edit or delete the codes you set up at organisation level from campaign level. Organisation codes appear by default in all campaigns (according to their scope) and are read-only. If you need to change an organisation code, you have to do it from the Register data section of your organisation. You can, however, create extra codes specific to campaign level, and those you can edit or delete.

The new value of a custom code is not saved unless you confirm it with the confirmation icon (✓) before clicking Save changes. To change the value of a campaign code, go to General data, click Edit to enable editing, write the new value, click the confirmation icon (✓) so that it is registered and, finally, click Save changes.