Posts
Dynamic URLs
When URLs are keywords or other parameters, you can use the corresponding options when entering funnel or conversion goal URL’s addresses. There are three types available, as showing below.
Exact Match
This option requires that the URLs entered as your funnel or conversion goal match the URLs shown in the reports exactly - there can be no dynamic session identifiers, for example.
Head Match
If your URL is always the same for this step of your funnel, but is followed by unique session or user identifiers, use the Head Match filter and leave out the unique values.
For example, if the URL for a particular user is;
' www.yoursite.com/checkout.cgi?page=1&id=9982251615 ' but the ' id ' varies for every other user, enter 'www.yoursite.com/checkout.cgi?page=1 ' and select Head Match as your Match Type.
Regular Expression Match
Uses regular expressions to match your URLs. This is useful when the stem, trailing parameters, or both can vary between users. For example, if a user could be coming from one of many subdomains, and your URLs use session identifiers, use regular expressions to define the constant element of your URL.
For example,
Identical URLs Across Multiple Steps
You may also 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.yoursite.com/sign_up.cgi
Step 2 (Accept Agreement): www.yoursite.com/sign_up.cgi
Step 3 (Finish): www.yoursite.com/sign_up.cgi
To get around this, you can call the _trackPageview function within each step (probably within an onload event), as shown below.
Then set up each step of your funnel to be;
http://www.yoursite.com/funnel_G1/step1.html
http://www.yoursite.com/funnel_G1/step2.html
http://www.yoursite.com/funnel_G1/step3.html
The path/filename argument need not represent an existing path or filename. The argument to _trackPageview simply provides a made-up pagename to which Google Analytics can attach pageviews.
Important Note:
1. Please ignore the spaces between codes.
2. If your pages include a call to _trackPageview, _setAllowLinker _trackTrans(), your Analytics tracking code must be placed in your HTML code above any of these calls. In these cases the tracking code can be placed anywhere between the opening tag and the JavaScript call.
When URLs are keywords or other parameters, you can use the corresponding options when entering funnel or conversion goal URL’s addresses. There are three types available, as showing below.
Exact Match
This option requires that the URLs entered as your funnel or conversion goal match the URLs shown in the reports exactly - there can be no dynamic session identifiers, for example.
Head Match
If your URL is always the same for this step of your funnel, but is followed by unique session or user identifiers, use the Head Match filter and leave out the unique values.
For example, if the URL for a particular user is;
' www.yoursite.com/checkout.cgi?page=1&id=9982251615 ' but the ' id ' varies for every other user, enter 'www.yoursite.com/checkout.cgi?page=1 ' and select Head Match as your Match Type.
Regular Expression Match
Uses regular expressions to match your URLs. This is useful when the stem, trailing parameters, or both can vary between users. For example, if a user could be coming from one of many subdomains, and your URLs use session identifiers, use regular expressions to define the constant element of your URL.
For example,
' page=1 ' will match
' making.example.com/checkout.cgi?page=1&id=002, ' as well as
' marketing.example.com/checkout.cgi?page=1&language=fr&id=19. '
' making.example.com/checkout.cgi?page=1&id=002, ' as well as
' marketing.example.com/checkout.cgi?page=1&language=fr&id=19. '
Identical URLs Across Multiple Steps
You may also 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.yoursite.com/sign_up.cgi
Step 2 (Accept Agreement): www.yoursite.com/sign_up.cgi
Step 3 (Finish): www.yoursite.com/sign_up.cgi
To get around this, you can call the _trackPageview function within each step (probably within an onload event), as shown below.
pageTracker._trackPageview(" /funnel_G1/step1.html "); pageTracker._trackPageview(" /funnel_G1/step2.html "); pageTracker._trackPageview(" /funnel_G1/step3.html ");
Then set up each step of your funnel to be;
http://www.yoursite.com/funnel_G1/step1.html
http://www.yoursite.com/funnel_G1/step2.html
http://www.yoursite.com/funnel_G1/step3.html
The path/filename argument need not represent an existing path or filename. The argument to _trackPageview simply provides a made-up pagename to which Google Analytics can attach pageviews.
Important Note:
1. Please ignore the spaces between codes.
2. If your pages include a call to _trackPageview, _setAllowLinker _trackTrans(), your Analytics tracking code must be placed in your HTML code above any of these calls. In these cases the tracking code can be placed anywhere between the opening tag and the JavaScript call.
