Skip to main content

POWr Metrics Defined

The launch of volcano (new on-boarding flow) on September 4th 2018 introduced some changes to what we store about users in the DB.

This includes Weebly and Jimdo users.

When a user first adds a plugin to a page they will have

  • 'backup_content: nil'
  • 'content: nil'
  • 'saved: false'

I.e they see default content and nothing is saved to the db.

When a user makes any change in the popup editor, their app is immediately considered 'saved'. That is, as soon as a user starts editing an app in the popup editor it has:

  • 'backup_content' (draft content)
  • 'content' (live content which will always match draft content)
  • 'saved: true'

If a user returns to the popup editor to make changes later, their changes will be immediately published. That is, on every change both backup_content with content will be updated.

Standalone​

In standalone, when a user first opens the page they will have

  • 'backup_content: nil'
  • 'content: nil'
  • 'saved: false'

I.e they see default content and nothing is saved to the db.

In standalone, when a user starts editing a new plugin they will have:

  • 'backup_content: set to store the changes they have made'
  • 'content: nil'
  • 'saved: false'

Once they click 'Add to Site' they will have:

  • 'backup_content'
  • 'content' (this is synced from 'backup_content' on click so is the same as backup_content)
  • 'saved: true'

If a user goes back and edits an app in standalone, they will have:

  • 'backup_content' => which will be updated with the new changes they just made
  • 'content' (but it will not match 'backup_content until they click 'Publish')
  • 'saved: true'

Any user (in popup editor or standalone) is considered 'active' if their plugin ID has been loaded on a non-POWr.io domain within the last 3 days (stored as 'last_viewed_at').

New possibilities​

  • We now know if a user edited an app but didn't 'save' (by clicking 'Add to Site'). These users would have 'backup_content' but no 'content' or 'saved' status.
    • N.B. A lot of these users won't have signed in already, so not possible to target them unless they auto login e.g. through Shopify.
  • We have information about feature usage in 'backup_content'. It's possible to know what a user actually changed.
  • We can target users who have an active app, edited but didn't publish new changes ('active' users where 'backup_content' does not equal 'content').

[section below added by Teddy, needs review]

Other definitions

Additional terms that are useful in this context 02/25/2020: *POWr-By-Platform and POWr-By-App Definitions

New Saved Apps - Clicking "Add to site" makes the app have a status of "saved". App does need to have backupcontent at this point. App does not need to have content at this point. Example flow: _1) User hits tutorial lander, loads app standalone, clicks "Add to site" (without customizing app) 2) User is on a create first platform (like Jimdo, Joomla, WordPress) and adds an embed code to site. Clicking "Edit" immediately saves the app (and also adds backup_content and content)

URL Exists Apps - For this to be counted on this dashboard, the app has to be saved. In the app's model, an app can have a last_viewed_url even when the app is not saved yet (install first flows). We filter some URLs based on what's on this list: https://www.powr.io/admin/last_viewed_url_filters

Ever Active Apps - The user loaded their app (either on standalone or the app view) anytime after the first 24 hours of the app having been created. In this dashboard, we only look at apps that were created in last 30 days. If there is a delay in becoming active, the app would never appear as active on this dashboard.

3 Day Active Apps - Apps that have a last_viewed_at in last 3 days (time when this dashboard was loaded). last_viewed_at gets set immediately, so any app created in the last 3 days will be included in this number.

30 Day Active Apps - Apps that have a last_viewed_at in last 30 days (time when this dashboard was loaded).(Not just apps created in the last 30 days but all apps). last_viewed_at gets set immediately, so any app created in the last 30 days will be included in this number. App does not need to have backup_content, content, or a status of saved to be included here.

Apps With Backup Content - All apps created in last 30 days that have backup_content (does not need to have content or a status of saved).An app gets backup_content the second the user edits anything in the settings (for example, select a template or change design). In Wix, an app gets backup_content, content, and a status of saved if the user publishes the page on which the app was embedded. The app does NOT immediately get backup_content. When a user opens the app settings, they immediately get backup_content and a status of saved.

New Subscriptions - This might need some updates; current logic seems pretty jank. This currently looks at related_apps and distributes subscription across multiple platforms if the user has different external_id_types for different apps.

Other Definitions: Install-first - In specific platforms the app is installed before any backup_content, content, or saved status is created. For these platforms, when a user begins to edit the app in popout settings all three fields are updated, and saved = true.

Platforms with install first flow:

  • Weebly
  • Jimdo
  • WordPress (only some install flows)
  • Joomla (only some install flows)
  • Bookmark
  • Webydo

https://docs.google.com/spreadsheets/d/1q1NVVsdn_-ZvFQZ2B5S7HFvQQnhprOd3bqVE2VSdnTY/edit#gid=0

04/22/2019: URL Exists - If an app has a last_viewed_url Ever Active - If an app's last_viewed_at > created_at + 1.day. This means that the app had activity past the initial create date Three Day Active - If an app's last_viewed_at > 3.days.ago. Note: this can get inflated if there are a lot of new apps getting created. Thirty Day Active - If an app's last_viewed_at > 30.days.ago. Mainly for external showcase.

last_viewed_at - gets set as soon as the plugin is viewed on a page --> this will change to “as soon as the plugin is loaded anywhere” last_viewed_url - gets set once we have a URL that is definitely not an editor url (we can blacklist URLs we want to ignore) --> this will stay the same

“active” on most of our dashboards = there is a last_viewed_url AND a last_viewed_at date from less than 3 days ago.

View url​

This is the url that renders the app as the end-user sees it, as if it was installed on a website.

a user can fully interact with an app in its view url, i.e. submitting a form or completing a payment

Unclaimed app​

An app that is not associated with a user

  • 'app.owners: nil'

When an unclaimed app is viewed on an installed page or using its view url, it will display with an overlay and a button to sign up and claim the app.

Unclaimed app at view url

Form Response Dashboard​

Dashboard where form responses can be viewed.

This page also contains links to download excel, download csv, and delete all responses.