Page View Clarification

Plasmic Studio Questions
1

We use built-in analytics to count the number of unique views across any page of your website featuring a Plasmic design. This only applies to content delivered via the Headless API, not codegen.

So, does this mean,

  1. if I assemble my website with custom components in the plasmic studio, if it passes the monthly limit, i can not publish newer versions, but next month, when it resets, i can publish the next version? Is this subject to change in the future?

  2. are those page views unique per person or just unique overall, in the sense, if I log in the morning, and in the afternoon, those count as two separate times, and if I go from one page to the other, such as home to dashboard does that count as 2 views?

  3. Are these unique per project?

  4. If I self-host website, how does it track?

  5. I have an existing codebase, can i upload and host it on plasmic cloud, or only self host. Plan is to make components at the dev level, and have non developers come and assemble the actual website?

    Thanks in advance! Currently deciding tech for our workflows, wanted to understand how whether plasmic would work for our usecase.

1 Like
2

Hi @rayan_sheikh , welcome to the Plasmic Community!

Could you share where you found the “We use built-in analytics to count the number of unique views…” quote?

  1. /2./3. Currently we are not enforcing any page view limits, but this is subject to change. We will likely to switch to bandwidth based limits in the future.

  2. Self-hosting your website while using either 1) codegen or 2) loader with static site generation is optimal in terms of bandwidth consumption.

  3. With an existing codebase using registered components, you are required to self-host and cannot use Plasmic Hosting.

3

Hi @jason !
Thanks for the response.
Found it on the Frequently Asked Questions in the pricing page

image
image1920Ă—1213 71.3 KB

So, functionality wise, I can create an app on the Plasmic Studio, create custom code components if required, upload them and be able to use them in the website, and that can be hosted via Plasmic.

But if I have an existing codebase, and I choose to use Plasmic to create components and embed them in my website, then I have to self host?

Thanks!

1 Like
4

So, functionality wise, I can create an app on the Plasmic Studio, create custom code components if required, upload them and be able to use them in the website, and that can be hosted via Plasmic.

If there are custom code components involved, then it must be self-hosted.

But if I have an existing codebase, and I choose to use Plasmic to create components and embed them in my website, then I have to self host?

if you have an existing codebase (so you must already be self-hosting), then you can embed Plasmic content in it.