Tracking crypto staking rewards can be difficult. With assets spread across different wallets, chains, and exchanges, manually consolidating data is a messy, time-consuming process. This makes it tedious and hard to accurately track performance or make informed decisions.

This free Crypto Staking Rewards Calculator Google Sheets Template is designed to solve this problem. It automatically calculates your true effective APY from various advertised rates, projects future earnings, and analyzes your performance in real-time using live crypto market data powered by the CoinGecko API. Whether you’re staking major assets like Solana and Ethereum or long-tail on-chain tokens, this template gives you a clean, visual way to calculate your staking rewards, track its performance, and make smarter compounding decisions.

What Are Crypto Staking Rewards and Why Should You Track Them?

Crypto staking rewards are the earnings you receive for participating in a blockchain’s security and operations. In networks that use a Proof of Stake (PoS) consensus mechanism, you lock up your cryptocurrency, a process called staking, to help validate transactions and secure the network. In return for this service, the network compensates you with rewards, similar to earning interest in a traditional savings account.

Tracking these rewards is crucial for several reasons:

Performance Monitoring: Tracking allows you to calculate the actual Annual Percentage Yield (APY) on your staked assets. For example, if you’re staking Solana (SOL), your rewards are paid in SOL. The value of those rewards fluctuates with the market, and only by tracking both the quantity of SOL received and its price over time can you understand your true return on investment.
Compounding Strategy: Visualizing your earnings helps you make informed decisions about compounding. By seeing how re-staking your rewards impacts your total holdings, you can build a more effective strategy for exponential growth.

Prerequisites

Before you start, ensure the following requirements are met to use the template effectively:

A Google Account:
You’ll need a Google account to open, copy, and use the template in Google Sheets. This allows you to save your own version.
CoinGecko Google Sheets Add-on:
This template uses the official CoinGecko Google Sheets add-on to fetch live and historical crypto prices directly into your sheet using the =COINGECKO() function.
A CoinGecko API Key:
Required to fetch live crypto prices. The free Demo API key is sufficient to get started, while a Pro plan offers higher rate limits for more frequent data refreshes. You can follow our guide to get your free Demo API key.

How to Use the Free Staking Rewards Tracker Google Sheets Template

This section provides a clear, step-by-step guide on how to integrate and use the Staking Rewards Calculator template effectively. Follow these instructions to set up the CoinGecko add-on, log your staking activity, and track your rewards and performance over time.

Setting up the CoinGecko Add-on

First, connect the template to the CoinGecko Google Sheets add-on to enable live and historical price data within the spreadsheet. To get started, install the add-on and configure your API credentials (Subscription Level and API Key) by following the setup guide.

Once configured, all =COINGECKO() formulas across the template will automatically fetch the required data. You don’t need to modify any formulas or configure scripts manually.

Refreshing Crypto Price Data

Now that the CoinGecko add-on is configured, your data will be fetched automatically through the =COINGECKO() formulas across the template, allowing you to retrieve crypto data directly (e.g., =COINGECKO("id:bitcoin") for individual tokens) without any manual setup.

However, Google Sheets may cache results for a short period of time. If you need the most up-to-date prices, you can manually refresh all data in your sheet. Keep in mind that more frequent refreshes will consume your API call credits faster. If you run into rate limits, consider upgrading to a paid API plan for higher call credits and rate limits.

Once the add-on status is Live, you can start customising the template by adding the tokens you want to track in the following section.

Adding Coins to the Template

The template tracks the top 1000 cryptocurrencies by market cap by default using the =COINGECKO("top:1000") function. To track other assets, such as specific on-chain tokens, you can add them manually in the Add Coins sheet. The information required depends on whether the asset is listed on CoinGecko or is an on-chain token tracked on GeckoTerminal.

For Coins found on CoinGecko, set the Source to CoinGecko and enter its API ID. You can find the API ID on any individual coin page on the CoinGecko website.

For Onchain Tokens, set the Source to GeckoTerminal, select the Network ID (for example, bsc for BNB Chain), enter the Token Name and Token Contract Address. To find the Network ID and Token Contract Address, head to the individual token page on GeckoTerminal:

Name (On-Chain) can be found in the token info page.
The Network ID is found in the URL path (e.g., bsc in https://www.geckoterminal.com/bsc/pools/0xaead6bd31dd66eb3a6216aaf271d0e661585b0b1)
Token Contract Address for the base token is listed in the pool details.

After adding assets, the template automatically fetches the required data using the =COINGECKO() formulas (e.g., the top 1000 coins by market cap using =COINGECKO("top:1000")).

If you need to update prices instantly, open the CoinGecko sidebar and click “Refresh All Data” to force-refresh all values, as Google Sheets may cache results temporarily.

Your newly added assets will appear in the Available Coins sheet, starting from row 1002, directly below the default Top 1000 list. Once added, you only need to register a coin once for it to remain available for selection in your Staking Log. If a coin doesn’t appear, verify the Source, CoinGecko ID, Network ID, and Token Contract Address, then refresh the data.

Logging Your Staking Positions

Once the template is set up, you can start recording your positions in the Staking Log sheet. This is where you will log every new staking action’s lifecycle to accurately monitor your portfolio’s performance and value over time.

When starting a new position, fill in the initial staking details like the Stake Date, Staked Qty, and the platform’s advertised Staking Rate. The Stake Status will automatically show as active. When you are ready to close the position, return to that same row to enter the Unstake Date and the Unstaked Price (the asset’s price on the day you unstaked). The sheet will then automatically calculate your realized profit for that position.

Analyzing the Staking Rewards Dashboard

Once your positions are logged, head to the Staking Rewards Dashboard Sheet to review your performance. All charts and summary tables automatically update whenever a new position is added or when live market data refreshes. The dashboard will automatically recalculate and display your most recent realized and unrealized profit or loss, portfolio analytics, and future growth projections.

The sheet provides a comprehensive overview of your staking portfolio and is split into two main sections:

Staking Rewards Dashboard: This provides a snapshot of your overall staking health. It separates your active and historical performance to show how your earnings change over time and which assets have been most profitable.
- Balance Overview: A performance chart that visualizes your cumulative profit over time. It starts at zero and grows as you close positions and record realized gains, with a final point showing your total unrealized profit to date.
- Holding’s Distribution: A pie chart that visually breaks down your total active staking portfolio. It shows the percentage allocation of each cryptocurrency you are staking based on their current dollar value.
- Staking Coins Analytics: A summary table of all your closed positions. It details the final Position Value, net profit/loss and total holding duration, providing a clear history of your performance.
Staking Rewards Calculator: This is an interactive projection tool for strategic planning on a single asset. To generate a projection, navigate to Row 5 (from Column “N” onwards) and input the required parameters. You will need to select an active coin, the staking platform, and the hold duration (e.g., Year, Month). The dashboard will then calculate the projected results.
- Final Projected Quantity: Based on the specified duration of hold and the effective APY rate for the specific staking platform, the scorecard will display the final projected quantity for the respective asset at the end of the projected date.
- Projected Value in USD (Based on current price): The dashboard then provides the valuation of the projected quantity based on the current price of the asset as well as the net profit.
- Automated Projection Table: The dashboard instantly generates a week-by-week forecast for the selected coin or token with an Active position. It shows the projected growth in your total coin quantity and its potential future dollar value. This forecast is based on the average Effective APY for the specified coin and staking platform. This helps you visualize future earnings and make informed decisions about your staking strategy.

Creating a Crypto Staking Rewards Calculator in Google Sheets

Creating a crypto staking rewards calculator in Google Sheets involves three main components: a live data source for fetching crypto prices, a structured log for recording all staking positions, and an automated dashboard for calculating performance.

To build one, you would need to integrate these components:

Live Crypto Market Data: Live prices are essential for real-time valuations. This can be achieved by using the CoinGecko Google Sheets add-on to pull data from the CoinGecko API. This method allows you to retrieve data for a vast range of crypto assets directly into your sheet and set up automatic data refreshes using time-based triggers.
Structured Staking Log: You need a dedicated sheet to record every staking position. This log should include clear fields for the stake date, coin, quantity, staking rate (APR or APY), and compounding frequency. This structured data forms the foundation for all automated calculations.
Dynamic Analysis Dashboard: Create a dashboard that automatically aggregates and visualizes your log data. This typically involves using pivot tables and charts to create summary tables for active and closed positions, track cumulative profits, and project future earnings from active stakes.

How to Pull Real-Time Crypto Market Data into Google Sheets?

You can pull real-time crypto market data into Google Sheets using two different approaches, depending on your preferred level of control and customization.

Option 1 (Recommended): Using the CoinGecko Add-on

The simplest way is to use the official CoinGecko Google Sheets add-on with the =COINGECKO() function. This method is fully integrated into the template and allowing you to fetch live crypto prices directly, including on-chain tokens (e.g., =COINGECKO("base:0x1111111111166b7fe7bd91427724b487980afc69"), without any coding or manual setup.

Option 2 (Advanced): Using Apps Script

For users who require more flexibility, you can fetch data directly from the CoinGecko API using Google Apps Script. This approach gives you fine-grained control over the request parameters, such as specifying dates, currencies, and endpoints, as well as how the returned data is structured and used within your sheet. This involves creating custom functions (such as ImportJSON) to call specific API endpoints and retrieve market data into your sheet.

Step 1: Create an ImportJSON Script

First, create the main function that will fetch and parse the data.

Open your Google Sheet and navigate to ‘Extensions’ and select ‘Apps Script’ – a new tab will appear.

On the left panel, select ‘< > Editor’ and add a new script using the ‘+’ button. Copy and paste the following importJSON script, and save the script as ‘ImportJSON’. This importJSON script is a versatile one that will allow you to import data in many different ways.

/====================================================================================================================================
ImportJSON by Brad Jasper and Trevor Lohrbeer

Version: 1.5.0
Project Page:
Copyright: (c) 2017-2019 by Brad Jasper
(c) 2012-2017 by Trevor Lohrbeer
License: GNU General Public License, version 3 (GPL-3.0)
http://www.opensource.org/licenses/gpl-3.0.html

A library for importing JSON feeds into Google spreadsheets. Functions include:
ImportJSON For use by end users to import a JSON feed from a URL
ImportJSONFromSheet For use by end users to import JSON from one of the Sheets
ImportJSONViaPost For use by end users to import a JSON feed from a URL using POST parameters
ImportJSONAdvanced For use by script developers to easily extend the functionality of this library
ImportJSONBasicAuth For use by end users to import a JSON feed from a URL with HTTP Basic Auth (added by Karsten Lettow)
For future enhancements see

For bug reports see

Changelog:

1.6.0 (June 2, 2019) Fixed null values (thanks @gdesmedt1)
1.5.0 (January 11, 2019) Adds ability to include all headers in a fixed order even when no data is present for a given header in some or all rows.
1.4.0 (July 23, 2017) Transfer project to Brad Jasper. Fixed off-by-one array bug. Fixed previous value bug. Added custom annotations. Added ImportJSONFromSheet and ImportJSONBasicAuth.
1.3.0 Adds ability to import the text from a set of rows containing the text to parse. All cells are concatenated
1.2.1 Fixed a bug with how nested arrays are handled. The rowIndex counter wasn’t incrementing properly when parsing.
1.2.0 Added ImportJSONViaPost and support for fetchOptions to ImportJSONAdvanced
1.1.1 Added a version number using Google Scripts Versioning so other developers can use the library
1.1.0 Added support for the noHeaders option
1.0.0 Initial release
*====================================================================================================================================*/
/**
* Imports a JSON feed and returns the results to be inserted into a Google Spreadsheet. The JSON feed is flattened to create
* a two-dimensional array. The first row contains the headers, with each column header indicating the path to that data in
* the JSON feed. The remaining rows contain the data.
* * By default, data gets transformed so it looks more like a normal data import. Specifically:
*
* – Data from parent JSON elements gets inherited to their child elements, so rows representing child elements contain the values
* of the rows representing their parent elements.
* – Values longer than 256 characters get truncated.
* – Headers have slashes converted to spaces, common prefixes removed and the resulting text converted to title case.
*
* To change this behavior, pass in one of these values in the options parameter:
*
* noInherit: Don’t inherit values from parent elements
* noTruncate: Don’t truncate values
* rawHeaders: Don’t prettify headers
* noHeaders: Don’t include headers, only the data
* allHeaders: Include all headers from the query parameter in the order they are listed
* debugLocation: Prepend each value with the row & column it belongs in
*
* For example:
*
* =ImportJSON("http://gdata.youtube.com/feeds/api/standardfeeds/most_popular?v=2&alt=json", "/feed/entry/title,/feed/entry/content",
* "noInherit,noTruncate,rawHeaders")
* * @param {url} the URL to a public JSON feed
* @param {query} a comma-separated list of paths to import. Any path starting with one of these paths gets imported.
* @param {parseOptions} a comma-separated list of options that alter processing of the data
* @customfunction
*
* @return a two-dimensional array containing the data, with the first row containing headers
**/
function ImportJSON(url, query, parseOptions) {
return ImportJSONAdvanced(url, null, query, parseOptions, includeXPath_, defaultTransform_);
}
/**
* Imports a JSON feed via a POST request and returns the results to be inserted into a Google Spreadsheet. The JSON feed is
* flattened to create a two-dimensional array. The first row contains the headers, with each column header indicating the path to
* that data in the JSON feed. The remaining rows contain the data.
*
* To retrieve the JSON, a POST request is sent to the URL and the payload is passed as the content of the request using the content
* type "application/x-www-form-urlencoded". If the fetchOptions define a value for "method", "payload" or "contentType", these
* values will take precedent. For example, advanced users can use this to make this function pass XML as the payload using a GET
* request and a content type of "application/xml; charset=utf-8". For more information on the available fetch options, see
* https://developers.google.com/apps-script/reference/url-fetch/url-fetch-app . At this time the "headers" option is not supported.
* * By default, the returned data gets transformed so it looks more like a normal data import. Specifically:
*
* – Data from parent JSON elements gets inherited to their child elements, so rows representing child elements contain the values
* of the rows representing their parent elements.
* – Values longer than 256 characters get truncated.
* – Headers have slashes converted to spaces, common prefixes removed and the resulting text converted to title case.
*
* To change this behavior, pass in one of these values in the options parameter:
*
* noInherit: Don’t inherit values from parent elements
* noTruncate: Don’t truncate values
* rawHeaders: Don’t prettify headers
* noHeaders: Don’t include headers, only the data
* allHeaders: Include all headers from the query parameter in the order they are listed
* debugLocation: Prepend each value with the row & column it belongs in
*
* For example:
*
* =ImportJSON("http://gdata.youtube.com/feeds/api/standardfeeds/most_popular?v=2&alt=json", "user=bob&apikey=xxxx",
* "validateHttpsCertificates=false", "/feed/entry/title,/feed/entry/content", "noInherit,noTruncate,rawHeaders")
* * @param {url} the URL to a public JSON feed
* @param {payload} the content to pass with the POST request; usually a URL encoded list of parameters separated by ampersands
* @param {fetchOptions} a comma-separated list of options used to retrieve the JSON feed from the URL
* @param {query} a comma-separated list of paths to import. Any path starting with one of these paths gets imported.
* @param {parseOptions} a comma-separated list of options that alter processing of the data
* @customfunction
*
* @return a two-dimensional array containing the data, with the first row containing headers
**/
function ImportJSONViaPost(url, payload, fetchOptions, query, parseOptions) {
var postOptions = parseToObject_(fetchOptions);

if (postOptions["method"] == null) {
postOptions["method"] = "POST";
}
if (postOptions["payload"] == null) {
postOptions["payload"] = payload;
}
if (postOptions["contentType"] == null) {
postOptions["contentType"] = "application/x-www-form-urlencoded";
}
convertToBool_(postOptions, "validateHttpsCertificates");
convertToBool_(postOptions, "useIntranet");
convertToBool_(postOptions, "followRedirects");
convertToBool_(postOptions, "muteHttpExceptions");

return ImportJSONAdvanced(url, postOptions, query, parseOptions, includeXPath_, defaultTransform_);
}
/**
* Imports a JSON text from a named Sheet and returns the results to be inserted into a Google Spreadsheet. The JSON feed is flattened to create
* a two-dimensional array. The first row contains the headers, with each column header indicating the path to that data in
* the JSON feed. The remaining rows contain the data.
* * By default, data gets transformed so it looks more like a normal data import. Specifically:
*
* – Data from parent JSON elements gets inherited to their child elements, so rows representing child elements contain the values
* of the rows representing their parent elements.
* – Values longer than 256 characters get truncated.
* – Headers have slashes converted to spaces, common prefixes removed and the resulting text converted to title case.
*
* To change this behavior, pass in one of these values in the options parameter:
*
* noInherit: Don’t inherit values from parent elements
* noTruncate: Don’t truncate values
* rawHeaders: Don’t prettify headers
* noHeaders: Don’t include headers, only the data
* allHeaders: Include all headers from the query parameter in the order they are listed
* debugLocation: Prepend each value with the row & column it belongs in
*
* For example:
*
* =ImportJSONFromSheet("Source", "/feed/entry/title,/feed/entry/content",
* "noInherit,noTruncate,rawHeaders")
* * @param {sheetName} the name of the sheet containg the text for the JSON
* @param {query} a comma-separated lists of paths to import. Any path starting with one of these paths gets imported.
* @param {options} a comma-separated list of options that alter processing of the data
*
* @return a two-dimensional array containing the data, with the first row containing headers
* @customfunction
**/
function ImportJSONFromSheet(sheetName, query, options) {
var object = getDataFromNamedSheet_(sheetName);

return parseJSONObject_(object, query, options, includeXPath_, defaultTransform_);
}
/**
* An advanced version of ImportJSON designed to be easily extended by a script. This version cannot be called from within a
* spreadsheet.
* * Imports a JSON feed and returns the results to be inserted into a Google Spreadsheet. The JSON feed is flattened to create
* a two-dimensional array. The first row contains the headers, with each column header indicating the path to that data in
* the JSON feed. The remaining rows contain the data.
*
* The fetchOptions can be used to change how the JSON feed is retrieved. For instance, the "method" and "payload" options can be
* set to pass a POST request with post parameters. For more information on the available parameters, see
* https://developers.google.com/apps-script/reference/url-fetch/url-fetch-app .
*
* Use the include and transformation functions to determine what to include in the import and how to transform the data after it is
* imported.
*
* For example:
*
* ImportJSON("http://gdata.youtube.com/feeds/api/standardfeeds/most_popular?v=2&alt=json",
* new Object() { "method" : "post", "payload" : "user=bob&apikey=xxxx" },
* "/feed/entry",
* "",
* function (query, path) { return path.indexOf(query) == 0; },
* function (data, row, column) { data[row][column] = data[row][column].toString().substr(0, 100); } )
*
* In this example, the import function checks to see if the path to the data being imported starts with the query. The transform
* function takes the data and truncates it. For more robust versions of these functions, see the internal code of this library.
*
* @param {url} the URL to a public JSON feed
* @param {fetchOptions} an object whose properties are options used to retrieve the JSON feed from the URL
* @param {query} the query passed to the include function
* @param {parseOptions} a comma-separated list of options that may alter processing of the data
* @param {includeFunc} a function with the signature func(query, path, options) that returns true if the data element at the given path
* should be included or false otherwise.
* @param {transformFunc} a function with the signature func(data, row, column, options) where data is a 2-dimensional array of the data
* and row & column are the current row and column being processed. Any return value is ignored. Note that row 0
* contains the headers for the data, so test for row==0 to process headers only.
*
* @return a two-dimensional array containing the data, with the first row containing headers
* @customfunction
**/
function ImportJSONAdvanced(url, fetchOptions, query, parseOptions, includeFunc, transformFunc) {
var jsondata = UrlFetchApp.fetch(url, fetchOptions);
var object = JSON.parse(jsondata.getContentText());

return parseJSONObject_(object, query, parseOptions, includeFunc, transformFunc);
}
/**
* Helper function to authenticate with basic auth informations using ImportJSONAdvanced
*
* Imports a JSON feed and returns the results to be inserted into a Google Spreadsheet. The JSON feed is flattened to create
* a two-dimensional array. The first row contains the headers, with each column header indicating the path to that data in
* the JSON feed. The remaining rows contain the data.
*
* The fetchOptions can be used to change how the JSON feed is retrieved. For instance, the "method" and "payload" options can be
* set to pass a POST request with post parameters. For more information on the available parameters, see
* https://developers.google.com/apps-script/reference/url-fetch/url-fetch-app .
*
* Use the include and transformation functions to determine what to include in the import and how to transform the data after it is
* imported.
*
* @param {url} the URL to a http basic auth protected JSON feed
* @param {username} the Username for authentication
* @param {password} the Password for authentication
* @param {query} the query passed to the include function (optional)
* @param {parseOptions} a comma-separated list of options that may alter processing of the data (optional)
*
* @return a two-dimensional array containing the data, with the first row containing headers
* @customfunction
**/
function ImportJSONBasicAuth(url, username, password, query, parseOptions) {
var encodedAuthInformation = Utilities.base64Encode(username + ":" + password);
var header = {headers: {Authorization: "Basic " + encodedAuthInformation}};
return ImportJSONAdvanced(url, header, query, parseOptions, includeXPath_, defaultTransform_);
}
/** * Encodes the given value to use within a URL.
*
* @param {value} the value to be encoded
* * @return the value encoded using URL percent-encoding
*/
function URLEncode(value) {
return encodeURIComponent(value.toString());
}
/**
* Adds an oAuth service using the given name and the list of properties.
*
* @note This method is an experiment in trying to figure out how to add an oAuth service without having to specify it on each
* ImportJSON call. The idea was to call this method in the first cell of a spreadsheet, and then use ImportJSON in other
* cells. This didn’t work, but leaving this in here for further experimentation later.
*
* The test I did was to add the following into the A1:
* * =AddOAuthService("twitter", "https://api.twitter.com/oauth/access_token",
* "https://api.twitter.com/oauth/request_token", "https://api.twitter.com/oauth/authorize",
* "", "", "", "")
*
* Information on obtaining a consumer key & secret for Twitter can be found at https://dev.twitter.com/docs/auth/using-oauth
*
* Then I added the following into A2:
*
* =ImportJSONViaPost("https://api.twitter.com/1.1/statuses/user_timeline.json?screen_name=fastfedora&count=2", "",
* "oAuthServiceName=twitter,oAuthUseToken=always", "/", "")
*
* I received an error that the "oAuthServiceName" was not a valid value. [twl 18.Apr.13]
*/
function AddOAuthService__(name, accessTokenUrl, requestTokenUrl, authorizationUrl, consumerKey, consumerSecret, method, paramLocation) {
var oAuthConfig = UrlFetchApp.addOAuthService(name);
if (accessTokenUrl != null && accessTokenUrl.length > 0) {
oAuthConfig.setAccessTokenUrl(accessTokenUrl);
}

if (requestTokenUrl != null && requestTokenUrl.length > 0) {
oAuthConfig.setRequestTokenUrl(requestTokenUrl);
}

if (authorizationUrl != null && authorizationUrl.length > 0) {
oAuthConfig.setAuthorizationUrl(authorizationUrl);
}

if (consumerKey != null && consumerKey.length > 0) {
oAuthConfig.setConsumerKey(consumerKey);
}

if (consumerSecret != null && consumerSecret.length > 0) {
oAuthConfig.setConsumerSecret(consumerSecret);
}

if (method != null && method.length > 0) {
oAuthConfig.setMethod(method);
}

if (paramLocation != null && paramLocation.length > 0) {
oAuthConfig.setParamLocation(paramLocation);
}
}
/** * Parses a JSON object and returns a two-dimensional array containing the data of that object.
*/
function parseJSONObject_(object, query, options, includeFunc, transformFunc) {
var headers = new Array();
var data = new Array();

if (query && !Array.isArray(query) && query.toString().indexOf(",") != -1) {
query = query.toString().split(",");
}
// Prepopulate the headers to lock in their order
if (hasOption_(options, "allHeaders") && Array.isArray(query))
{
for (var i = 0; i 1 ? data.slice(1) : new Array()) : data;
}
/** * Parses the data contained within the given value and inserts it into the data two-dimensional array starting at the rowIndex.
* If the data is to be inserted into a new column, a new header is added to the headers array. The value can be an object,
* array or scalar value.
*
* If the value is an object, it’s properties are iterated through and passed back into this function with the name of each
* property extending the path. For instance, if the object contains the property "entry" and the path passed in was "/feed",
* this function is called with the value of the entry property and the path "/feed/entry".
*
* If the value is an array containing other arrays or objects, each element in the array is passed into this function with
* the rowIndex incremeneted for each element.
*
* If the value is an array containing only scalar values, those values are joined together and inserted into the data array as
* a single value.
*
* If the value is a scalar, the value is inserted directly into the data array.
*/
function parseData_(headers, data, path, state, value, query, options, includeFunc) {
var dataInserted = false;
if (Array.isArray(value) && isObjectArray_(value)) {
for (var i = 0; i 1) {
removeCommonPrefixes_(data, row);
}

data[row][column] = toTitleCase_(data[row][column].toString().replace(/[/_]/g, " "));

}

if (!hasOption_(options, "noTruncate") && data[row][column]) {
data[row][column] = data[row][column].toString().substr(0, 256);
}
if (hasOption_(options, "debugLocation")) {
data[row][column] = "[" + row + "," + column + "]" + data[row][column];
}
}
/** * If all the values in the given row share the same prefix, remove that prefix.
*/
function removeCommonPrefixes_(data, row) {
var matchIndex = data[row][0].length;
for (var i = 1; i = 0;
}
/** * Parses the given string into an object, trimming any leading or trailing spaces from the keys.
*/
function parseToObject_(text) {
var map = new Object();
var entries = (text != null && text.trim().length > 0) ? text.toString().split(",") : new Array();

for (var i = 0; i ‘CoinGecko’ > ‘View Error Logs’ to access the debug logs and view the returned error code and message.

Once you’ve identified the issue, here are a few common problems along with quick ways to fix them.

API Rate Limit (Error 429)
This happens when the free CoinGecko Demo API hits its request limit. Wait a few minutes before refreshing again, or switch to a Pro API key for uninterrupted updates. If you receive other error codes, refer to the full list of CoinGecko API status codes to troubleshoot them.
Missing or Incorrect Coin Data
If a coin’s data doesn’t appear after refreshing:
- Check that the Coin ID or Contract Address in the AddCoins sheet is correct.
- Make sure the Source and Network ID fields are filled in properly.
- Refresh again after fixing the entry.
API Key or Endpoint Issues
If your data isn’t loading or you’re seeing errors such as 401 or 403, try reconnecting your CoinGecko API key within the add-on settings and ensure your subscription level is correctly configured.
Data Not Updating or Showing Older Prices
Google Sheets may cache formula results temporarily. To refresh your data, open the CoinGecko sidebar and click “Refresh All Data” to force-update all =COINGECKO() formulas.

For more detailed troubleshooting steps and a list of common errors, refer to the Error Debugging Guide.

Further Enhancements

You can further enhance this crypto staking rewards calculator template to better suit your analysis style. Here are a few ideas that leverage other CoinGecko API endpoints:

Fetch Historical Price Data
Pull Historical Prices for specific coins for more in-depth performance analysis. You can follow our guide on how to pull crypto historical data in Google Sheets and visualize long-term trends.
Add OHLC (Open, High, Low, Close) Data
If you want more granular price insights, consider fetching OHLC data for each coin. Check out our step-by-step guide on how to pull crypto OHLC data into Google Sheets.
Add a Crypto Portfolio Tracker
This staking rewards tracker shares many core components with a full crypto portfolio tracker. You can expand its functionality to monitor all your holdings, both staked and liquid assets held across multiple wallets and exchanges, by following our guide on how to create a crypto portfolio tracker in Google Sheets.
Create a Crypto Exit Strategy Planner
Just as this template helps you project future staking rewards, a crypto exit strategy planner can help you plan for future market movements. Consider building one to add profit-taking and stop-loss levels for your liquid assets. Check out our step-by-step guide on how to build a crypto exit strategy planner in Google Sheets.
Build a Crypto Tax Calculator
Since staking rewards can be taxable events, keeping a clean record with this template is a great first step. You can also use the data from your staking log to calculate capital gains using a dedicated crypto tax calculator. For a complete guide, see our article on how to create a crypto tax calculator in Google Sheets.

Conclusion

A staking rewards tracker is one of the most effective tools for understanding your true performance and optimizing your compounding strategy. This free Crypto Staking Rewards Calculator Google Sheets Template, powered by the CoinGecko API, provides a simple yet powerful way to log all your staking positions and analyze your performance. Because it’s built in Google Sheets, your tracker is accessible online across all your devices, ensuring you can manage your staking portfolio anytime, anywhere.

The integrated dashboard gives you a clear snapshot of your active positions and historical earnings, while the Dynamic Staking Projection Tool helps you forecast future growth and make informed compounding decisions.

Consider subscribing to a paid API plan if you require more frequent data updates, higher call credits, or access to exclusive endpoints beyond the Demo API’s limits.

Crypto Staking Rewards Calculator in Google Sheets (Free Template)

What Are Crypto Staking Rewards and Why Should You Track Them?

Prerequisites