[ic] Receipt.html and URL Parameters

[Ron Phipps]

> From: interchange-users-bounces at icdevgroup.org [mailto:interchange-users-
> bounces at icdevgroup.org] On Behalf Of Dan Bergan
> Sent: Thursday, March 23, 2006 8:28 AM
> 
> Ron Phipps wrote:
> >> From:  Kevin Walsh
> >> Sent: Thursday, March 23, 2006 7:22 AM
> >>
> >> Dan Bergan <dan at berganconsulting.com> wrote:
> >>
> >>> Mike Heins wrote:
> >>>
> >>>> It's actually easy. Just use this intead of [process] and mv_todo
> >>>> on the checkout form:
> >>>>
> >>>> 	<form action="[process href=receipt]" method="POST">
> >>>>
> >>>> 	<input type="hidden" name="mv_action" value="refresh">
> >>>>
> >>>>
> >>>>
> >>> Thanks for the tip, Mike.
> >>>
> >>> But, this shows "receipt" even if there are errors on the checkout
> >>> form.  Is there a way to have Interchange only show "receipt" in the
> URL
> >>> when the checkout is successful?
> >>>
> >>>
> >> A quick hack could be to wrap the "etc/receipt.html" so that the entire
> >> page body (not the template parts) is saved in a scratch variable.  At
> >> the end of the page, [bounce] to "receipt" (which would be in the
> "pages"
> >> directory instead of "etc", this time).  On the new
> "pages/receipt.html",
> >> simply display the template and the new scratch.
> >>
> >> As I said, it's a quick and dirty hack, but it should work - in theory.
> :-
> >> )
> >>
> >
> > This is exactly what we had to do to get the google code to work
> correctly.
> > This is really an issue with Google's api, they should allow you to pass
> the
> > page name in their script so that it does not have to rely on the url in
> the
> > browser.
> >
> > -Ron
> >
> >
> >
> I assume you are talking about Google Analytics (which is what I'm
> trying to use as well).  I did some searching and I finally came upon
> this (which seems like the best solution) from Google's site:
> 
> You may wish to track visitors' progress through a funnel which has the
> same URL for each step. For example, your sign up funnel might look like
> this:
> 
>     * Step 1 (Sign Up) - www.mysite.com/sign_up.cgi
>     * Step 2 (Accept Agreement) - www.mysite.com/sign_up.cgi
>     * Step 3 (Finish) - www.mysite.com/sign_up.cgi
> 
> To get around this, you can call the urchinTracker Javascript function
> within each step (probably within an onload event), as follows:
> 
>     urchinTracker("/funnel_G1/step1.html")
>     urchinTracker("/funnel_G1/step2.html")
>     urchinTracker("/funnel_G1/step3.html")
> 
> Then, set up each step of your funnel to be:
> 
>     http://www.mysite.com/funnel_G1/step1.html
>     http://www.mysite.com/funnel_G1/step2.html
>     http://www.mysite.com/funnel_G1/step3.html
> 
> Note that the path/filename argument to urchinTracker() need not
> represent an existing path or filename. The argument to urchinTracker
> simply provides a made-up pagename to which Google Analytics can attach
> pageviews.
> 
> So, I think that is a better solution than getting everyone to change
> how HTTP works!  ;-)
> 
> Thanks again for everyone's ideas -
> Dan

Thanks for the information!  I was taking the info I had received from an
SEO, looks like they didn't have all the details of urchintracker.  I'll
give it a try, thanks again.

-Ron