Product Naming Inside Hyros

This document will cover generally how products are named and tagged inside Hyros, and provide a few specific details regarding more common scenarios with some of the most used integrations.

How are Sales and Products named in Hyros from integrations?

The most common scenario is that Hyros integrates directly with your sales processor, checkout software or store, and that we receive sales directly from these softwares via the integration.

Each specific software can be slightly different, but as a general rule:

Hyros will name the product sent to us using the product name sent with the sale by the software you have integrated with.

If there is no name present with the sale sent, then Hyros will use the value of the sale and the integration that it came from to create the tag and sale.

As an example, if a product called “my sale” is sold and processed via Stripe and you have integrated Stripe with Hyros, then providing Stripe sends us the name with the sale inside Hyros the sale will be created with the following information:

Tag = “$my-sale”
Name = “my sale”.

(As you may notice typically the $sale tag associated with the sale corresponds with the name of the product sold as well in Hyros).

If the integration does not send Hyros the name with the event, then we will use the name of the integration + value like this, assuming the value of the sale is $100:


Each integration can be slightly different, here are some examples of some of the most common cases:


By default Hyros will use the nickname field of the specific product sold to automatically generate the name.

If you go to a customer and find the events and logs, you’ll be able to find if there is a nickname field with data here:


If this is not happening, then you can use the product description instead by following this guide:

Customize product names in Hyros sent from Stripe

Hyros will typically use the “nickname” field inside your product for the name, however Stripe may not send this consistently with events. If you notice in Hyros that products are not always being named correctly, you can follow these steps to use the product description as the name instead.

1. Navigate to your stripe integration at

2. toggle on the option to “use charge description as name”

3. Navigate to your stripe account

4. Under the “products” tab, find the product you want to edit and click here and select “edit product”

5. Under “price information” click “Additional options”

6. Then enter the name under the “price description” field as shown here.

Hyros will use whatever is entered here as the product name if the name is not already picked up from the standard “nickname” field.

7. Click “Save product” to ensure the changes are saved.


Changing the way you name your products inside Stripe will create brand new product tags and names in Hyros for future sales, it will not update the pre-existing sales inside Hyros.



Products are typically named and tagged depending on the specific product name Shopify sends us with each event.

Please take in mind this means that different variations of the same product will be marked as different products, because Shopify sends us a different name with each variation.

Also, if you have multiple stores and some of your products are names exactly the same within multiple stores, you can activate this option to add the store name to the tag so Hyros will be able to distinguish the products:

If this is toggled on, if you had a sale of a product named “my sale” and a store named “my store” then the $sale tag of the product sold would be “$my-store-my-sale”.


Zapier or API

The sale will typically be labelled as “$API-{ProductName}”

For example, if the product sold is called “my sale” and it’s sent via the api or zapier, providing you are sending the name with the event, then it will be called/tagged as follows:

Tag = “$Api-my-sale”

Name = Api my sale

Please take in mind that the name is based on the specific name field that you set either inside Zapier or in the API connection that you create.

If it’s not being named how you would expect please check how you have setup these connections first.