📎Product metadata
Please ensure you copy and paste the metadata tags exactly as shown in our guides to avoid any mistakes.
Residential Product
✅Onboarding a residential productOxylabs
torchlabs_product
torchlabs_elite
data_gb
Private
torchlabs_product
torchlabs_premium
data_gb
Packet Stream
torchlabs_product
torchlabs_basic
data_gb
Smart Proxies
torchlabs_product
torchlabs_smart
data_gb
IP Royal
torchlabs_product
torchlabs_iproyal
data_gb
Brightdata
torchlabs_product
torchlabs_brightdata
data_gb
Geonode
torchlabs_product
torchlabs_geonode
data_gb
X Residential
torchlabs_product
torchlabs_planx
data_gb
Netnut
torchlabs_product
torchlabs_netnut
data_gb
More soon..
Example:
This is an example of the packet stream product. The first field input torchlabs_product (this tag helps us identify the products that you make for the proxy dashboard vs other products on your Stripe account), and the second field is torchlabs_basic which is used to identify the Packetstream API
The next example is the quantity of the actual price section. In the below example, the customer will see a product on the dashboard for 15 GB of the Killer Basic plan for $140. We use the data_gb metadata tag to identify the quantity that is required to be delivered. If this tag is incorrect then they will not get any data delivered. In the field next to the data_gb we have the actual quantity in gigabytes, in this case, 15 GB (only put the value and not the letters GB - again referring to this example, it will be just 15)
Data center Product
✅Adding data center productsThe following metadata is used as a unique identification so that you can allocate products under the different metadata titles. The metadata names with daily/weekly / monthly are just going to be a unique identification whereas you do not need to consider their literal meaning when allocating the metadata. You can use any of the metadata names for any product.
Product 1
torchlabs_product
torchlabs_datacenter_daily
amount
Product 2
torchlabs_product
torchlabs_datacenter_weekly
amount
Product 3
torchlabs_product
torchlabs_datacenter_monthly
amount
Product 4
torchlabs_product
torchlabs_datacenter_extra1
amount
Product 5
torchlabs_product
torchlabs_datacenter_extra2
amount
Product 6
torchlabs_product
torchlabs_datacenter_extra3
amount
Product 7
torchlabs_product
torchlabs_datacenter_extra4
amount
Product 8
torchlabs_product
torchlabs_datacenter_extra5
amount
Product 9
torchlabs_product
torchlabs_datacenter_extra6
amount
Product 10
torchlabs_product
torchlabs_datacenter_extra7
amount
Product 11
torchlabs_product
torchlabs_datacenter_extra8
amount
Product 12
torchlabs_product
torchlabs_datacenter_extra9
amount
Product 13
torchlabs_product
torchlabs_datacenter_extra10
amount
Product 14
torchlabs_product
torchlabs_datacenter_extra11
amount
Product 15
torchlabs_product
torchlabs_datacenter_extra12
amount
Product 16
torchlabs_product
torchlabs_datacenter_extra13
amount
Product 17
torchlabs_product
torchlabs_datacenter_extra14
amount
Product 18
torchlabs_product
torchlabs_datacenter_extra15
amount
Product 19
torchlabs_product
torchlabs_datacenter_extra16
amount
Product 20
torchlabs_product
torchlabs_datacenter_extra17
amount
Product 21
torchlabs_product
torchlabs_datacenter_extra18
amount
Product 22
torchlabs_product
torchlabs_datacenter_extra19
amount
Product 23
torchlabs_product
torchlabs_datacenter_extra20
amount
Example
This is an example of Datacenter product. The first field inputs torchlabs_product (this tag helps us identify the products that you make for the proxy dashboard vs other products on your Stripe account), and the second field is torchlabs_weekly which is used to identify a unique product.
There is some confusion regarding the terminology behind daily, weekly, and monthly on the metadata - These actually mean nothing. It is only used to differentiate between all the data center products. They can be used interchangeably as well. For example, if you are selling Yeezysupply daily proxies, you can use any of the 3 metadata tags
The next example is the quantity of the actual price section. In the below example, the customer will see a product on the dashboard for 100 Killer ISPs for $300. We use the amount metadata tag to identify the quantity that is required to be delivered. If this tag is incorrect then they will not get any data delivered. In the field next to the amount we have the actual quantity in units, in this case, 100 ISPs (only put the value and not the letters ISP - again referring to this example, it will be just 100)
Account Product
✅Adding account productsProduct 1 - 9
torchlabs_product
torchlabs_accounts
amount
You can repeat the above metadata for up to 9 products.
Example:
This is an example of an Account product. The first field inputs torchlabs_product (this tag helps us identify the products that you make for the proxy dashboard vs other products on your Stripe account), and the second field is torchlabs_accounts which is used to identify an accounts product.
The next example is the quantity of the actual price section. In the below example, we are using the accounts tab to sell ISP subnets but you can sell whatever you want such as Gmails and FLX accounts. In our example, the customer will see a product on the dashboard for 254 Killer ISPs for $400. We use the amount metadata tag to identify the quantity that is required to be delivered. If this tag is incorrect then they will not get any data delivered. In the field next to the amount we have the actual quantity in units, in this case, 254 ISPs (only put the value and not the letters ISP - again referring to this example, it will be just 254) - Again you can do this with anything not just ISPs.
Last updated
Was this helpful?