Pricing Structure for Configurator 360

[Marty700]

We have managed to get a sample Product embedded into our companies website so that potential customers can access and configure products to suit their needs

This setup works pretty well, although speed of the update seems to be a common user complaint (which hopefully we can work on improving)

One question that has now arisen is how exactly does the Pricing Structure work when the Configurator is embedded in our site

From my understanding when you visit our Product Page the embedded Configurator 360 is trigged, however the user may not even use the Configurator 360 service

The user may in fact only be browsing through Products, looking up Data Sheets and Product specific Litrature available on that web page

Does the action of simply "triggering" the Configurator 360, but not using, actually incure a Cloud Credit charge?

If so then we are a bit concerned that we may spend a heap of Cloud Credits for no real use of the Configurator 360 service

Are there any other Pricing Structures available when purchasing the Configurator 360 service from Autodesk

Thanks

Marty

[sanjay.ramaswamy]

Hi Marty,

Yes, the act of triggering the embedded Configurator 360 viewer will incur a cloud credit charge. We think there's value in your users being able to view, rotate, zoom your model in 3D, and not just in changing parameters.

If you'd rather not incur the charge until the user changes the model, then you'll need to change the logic on the webpage to show just a standard image and trigger the viewer only when explicitly requested by the user (a 'configure' button, a tabbed view, etc.)

Perhaps you can experiment with your current scheme for a certain amount of time and determine usage before changing it up?

Sanjay-