Custom codes in StockCrowd are tools you use to segment and analyze donations more efficiently. These codes allow you to categorize donations and are reflected in Notifications (webhooks) and contribution reports.

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

There are two main types of custom codes you can configure according to your needs: organization-level codes and campaign-level codes. Each one has specific characteristics and different scopes.

At the organization level, you configure the codes from Registration Data, selecting Edit and going to the section where you can add custom codes. This is the central location where you establish codes that will apply to multiple campaigns.

In the configuration screen, you see the interface where custom codes are managed. This is the central administration zone for your organization-level codes.

To add a new code, you must click on the plus icon and assign the scope it will have. The scope determines where the code will appear: you can choose for it to appear in all campaigns and P2P pages (challenges), only in campaigns, or only in challenges. This way, you have different scopes available according to your needs.

In this screen, you select the scope of the code. The available options allow you to 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. This name is what will appear as a header in the reports, and the value is the content that will be reflected in donations.

In this screen, 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 campaigns to share the same code and value. This is especially useful for StockCrowd integrations with a CRM or to differentiate donations that come from StockCrowd from other sources.

If at the organization level you leave the code value blank, you have the flexibility to customize it in each of your campaigns without having to write the code name again. You only need to add the value, allowing each campaign to have a different value while maintaining the same code name.

Campaign-level codes are created in the same way as organization-level codes, but the main difference is that they only apply to the specific campaign in which you set them. For that reason, you cannot select the scope. To configure them, you access the campaign, select Content, then 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 the organization level. An important point to remember is that codes already configured at the organization level will appear by default in campaigns and you cannot edit or delete them from the campaign level.

In this screen you see the configuration of codes at the campaign level. Organization codes already appear here, and you can add additional codes specific to this campaign.

Understanding how codes behave when you modify, add, or delete them is key to maintaining data consistency. The behavior depends on the level at which each code was created (organization or campaign) and its inheritance relationship.

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

Modifying the value of a code does not alter historical data. To ensure report integrity, the system saves a "mirror" copy of the code at the exact moment each transaction is created. That is, even if you change the value of a code later, donation reports from earlier will continue to show the value that was in effect when each payment was made. Only new donations will take the updated value.

Deleting a code at the organization level deletes it in cascade in all associated campaigns and challenges. As for local editing or deletion: if the code was originally created at the campaign level, you can edit or delete it locally; but if the code comes from the organization level, that option is restricted at the local level. To change it, you must do it from the Registration Data section of your organization. This maintains the integrity of the code structure across the entire platform.

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

The available scopes are:

There is an important exception: when you create custom codes at the campaign level and that campaign is of P2P type, then you can assign the scope. The options in this case are that the code appears only in the Marketplace, only in the P2P pages of that campaign, or in both options.

In this screen you see the scope options specific to P2P campaign. You can select if you want it only for the Marketplace, for the P2P pages of this campaign, or for both options, giving you greater control over where each code appears.

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

In your report, you see how custom codes appear as additional columns. Each donation shows the corresponding code value in its row, allowing you to easily analyze segmented information.

A Query String is a text string that contains parameters in key-value format, located 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 functionality, custom codes are updatable from a URL. Whenever the code has the "updatable" option marked, the default value that was set for a code can be overwritten if the URL contains a parameter with another value. This gives you flexibility to change values dynamically depending on your traffic source.

Here you see the configuration of a custom code with the "updatable" option marked. This means that the value of this code can change depending on the parameters you add to the URL.

This functionality applies at both the organization and campaign levels and is especially useful for identifying the source of donations in marketing campaigns. You achieve this through the code via URL from the Query String, allowing you to track exactly where each donation comes from.

This is a normal campaign URL without additional parameters:

The URL you see here is a standard campaign address. This is the base URL you will use as a starting point.

But to use this Query String functionality, you must modify the URL by adding a parameter after the question mark. This allows you to personalize tracking according to your traffic source.

Suppose the same URL will be used for social networks like Instagram and Facebook. With this technique, you will be able to identify where donations come from, since the URL will contain the parameter you added and that is specific to each social network.

Instagram:

This URL includes a parameter specific to Instagram. By using this URL on Instagram, you will know exactly that donations coming 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 that will allow you to identify donations from that specific social network.

Even if other organizations help you spread the campaign, you can add different parameters to know which organization that is helping you share the campaign each donation comes from. This is useful for collaborations and for thanking your partners for their help.

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

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

Also at the Notifications (webhooks) level, you will be able to view these codes. Notifications allow you to see in real time the changes and new donations with their corresponding parameters.

In Notifications, you see complete details of each transaction including the custom code from the Query String. This is especially useful for integrations and for real-time monitoring of donations based on their origin.

Custom codes allow you to have much finer control of your donations and completely adapt the information to your specific needs. This is a powerful tool for understanding and optimizing your fundraising efforts.

A custom code at the organization level applies to all campaigns within your organization, which is useful for maintaining consistency and performing global analysis. A code at the campaign level applies only to a specific campaign, allowing you to have more customized codes for particular needs of that campaign. Organization codes automatically appear in all campaigns and you cannot edit them at the campaign level.

You can use the Query String functionality to track donations from different sources. You must 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, allowing you to identify exactly where each donation came from in your reports and notifications.

If you leave the code value blank at the organization level, you have the flexibility to customize it in each of your campaigns without having to write the code name again. You only need to complete 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.

No. The system preserves the value the code had at the time 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 automatically appear in your reports as additional columns, where you see the assigned values for each donation. They also appear in notifications (webhooks) if you use integrations with other systems. The specific location where the donor sees or interacts with the code depends on the scope you selected: in all campaigns and P2P, only in campaigns, or only in P2P pages.

No, you cannot edit or delete codes that you configured at the organization level from the campaign level. Organization codes appear by default in all campaigns (according to their scope) and are read-only. If you need to change an organization code, you must do it from the Registration Data section of your organization. However, you can create additional codes specific to the campaign level that you can edit or delete.