1
0
-1

Im looking at the transaction trend under the Analytics banner.
Just curious, what is the definition of "conversion rate"?
I understand completed transactions, and median completion time but not conversion rate.

 

Attachment to support question above:

conversion.jpg

    CommentAdd your comment...

    4 answers

    1.  
      2
      1
      0
      1. John Theriault
        The conversion rate is the percentage of submissions completed by users. This is calculated by reporting on the number of number of forms opened vs. the number of forms submitted. You can report on this on a form by form basis.
      CommentAdd your comment...
    2.  
      2
      1
      0

      John Theriault - is it possible to get a better conversion calculation?

      If for instance the customer opens the form link you sent a few times but for whatever reason could not start... let's say 4 and then on the the 5 time actually went through and submitted the form. The conversion calculation would pick this up as 5 requests but only having 1 submission. Which when reviewing conversion, this implies that it was 5 customers opening a form but only 1 actually submitting.

      Is there a better way to calculate conversion... say looking at a URL param as an identifier? So if the identifier is he same, it treats it as the same form being opened - so 1 request.  

        CommentAdd your comment...
      1.  
        1
        0
        -1

        Hey guys... I've implemented a solution... thought I share as it may prove useful for others (wink)

        I have an identifier for each form that is generated and sent out - a url param. In turn, I got the Avoka form to send out 2 events to Google Analytics (GA):

        • form rendered - send each time the form is requested
        • form submitted - send only on successful submission

        In GA, these events are logged against the identifier... so a form can be requested multiple times... that's OK. It will only increment the "form rendered" event. Importantly, this will be logged to the specific URL, which as mentioned is keyed by this param... so treated as the same form. Once / if submitted, the "form submitted" event will be fired and again logged against this identifier.

        Calculating the conversion is then a breeze: 

        Total the number of forms sent... this will be the unique urls keyed by the param identifier... and then the following:

        form submitted / apps sent
         = conversion rate

        Hope this helps others (smile)



          CommentAdd your comment...
        1.  
          1
          0
          -1

          Avoka Transact v4.3.2 (release notes) measures bounce rate as well as conversion rate, where a bounce is when a user lands on a form and takes no action before closing it.

          Alternatively, the the Google Analytics Widget is very easy to implement on a form for page level analytics. Using this tool, you have a little more control on how your reports can be customised, but it can be a bit of a steep learning curve for someone who hasn't used it before - you really need to find a GA expert to build the reports to meet your requirements, but there is a lot of power in how these can be configured. Avoka can also integrate forms with other Analytics providers with some client services effort, but this also requires an external expert in analytics.

            CommentAdd your comment...