How can I manage my cost when integrating the Slazzer REST API with user generated content ?

There are several ways to use the Slazzer API, one of them being user-generated content. 

User-generated content use cases

Here are examples of user-generated content use cases. 

  • Design tools and image editing softwares 
  • Online stores having product customization tools, allowing users to upload images of themselves and placing them on the product 
  • Social media applications, messengers, and platforms 
  • Photo booths & events
  • PR/Advertising campaigns with engaging content 

There’s something common with all these user-generated content cases – Users dictate the quantity of images to process. This allows for highly innovative products and integrations but carries a risk – If users decide the number of images to be processed, they decide how many Slazzer credits are required. 

Defining the Average User

It is important to define an average user’s behavior to ensure a positive return on investment (ROI). Depending on the application, the use case, and how often you integrate Slazzer, usage might be different. The primary question here is – How many pictures does an average user process?

This can be concluded via user research or with an assumption, followed by verifying and adapting it as you move ahead. 

Calculate ROI

Once you know the number of images processed by an average user, the cost and ROI can be based on that number. 

For example, if you expect 5 images per user for an online store, calculate the cost per user and set the same according to the conversion rate (number of users purchasing a product after processing images). Besides, calculate the profit margin to conclude the ROI. 

Limit and Monitor Costs 

If the calculation and user patterns lead to a positive ROI, there is simply no reason to be wary. More users will lead to more processing of images, thus raising the cost. However, an increase in revenue should cover the costs. 

To prevent product abuse, we suggest the following. 

  • Keep the API Confidential – Keep your API in a confidential environment, such as the server.
  • Limit Requests Per User – It is best to limit requests from untrusted users, which will also help analyze the number of images processed by every individual. 
  • Monitor Your Usage – Keep track of the credit usage in account settings. Transaction logs and charts will allow reviewing historical usage and identify patterns. 

Still got questions about calculating the ROI? Feel free to contact us