Has anyone used BTBuckets to create segments based on search keywords or referrers and then automatically redirect these users to a more efficient landing page?
This can be very useful with pages that have a very high bounce rate for these origins.
Cheers!
UPDATE:
Please feel free to see the example I set up on my site (Brazilian lottery results site). My bounce rate has gone down more that 20 percentage points for this organic search term! Great success!
Once the page has loaded, notice the message on the top of the page recommending content (it only appears for users who searched for these specific terms: concurso loteria 985, and only on the home page).
Hamish - I was talking about organic search. We have a lot of terms that bring users to our home-page that I would love to send to a better performing landing-page. I believe that this can be considered a black-hat technique. What we are doing now is creating a DHTML pop-up suggesting the better content to users who performed these searches.
However, with referrers we are using the automatic redirect.
Can you quickly outline how you got the redirect to work? I setup everything according to the videos but the redirect doesnt do anything. I have tried everything with no success.
I am quite confused what the "Client-side Targeting Callback Code" is for. According to the video the redirect will work using the default tracking tag.
The redirect feature is quite simple and yes, it will work with the default tracking tag. What you need to do is create what we call a target code and choose one or more buckets to execute it.
Target codes are actions that you can take when an user is in a bucket. They will execute on the client-side, in this case, it will run on the user's browser. For example, if you setup a redirect to execute for all users in the Social Media bucket, every time they come to your site from Social Media sites, they will be redirected to the page you configure.
You can run this code automatically (default setting) or run it manually when need. Also you can select one or more url's on your site to run the code, so, only on those url's the code will run.
To help you further, can you provide us more information about the problem and url where the code should work?
I setup a bucket so any user that enters "www.exodus.co.uk" using the search term "walking holidays" from google.co.uk gets redirected to "www.exodus.co.uk/walking". Strangely enough the bucket I created isn't being filled even though I followed the criteria that's assigned to it and so did multiple people on other networks. If BTBuckets isn't assigning users to the bucket than it can't redirect them so I think that's where the issue is.
I setup the buckets using the firefox GA add-on BUT I logged into a different GA account that's not associated with "www.exodus.co.uk" (while using the correct API assigned to my account) since "exodus.co.uk" dont use GA. The reason I did this was so the add-on would create the correct code for me. This shouldn't be an issue should it? If the add-on is using the correct add-on it shouldn't matter what GA account I log into should it?
Strange that the default buckets work as they should but none of the buckets I created dont.
The problem is that you configured the buckets using the "visited a page" behavior. This kind of behavior is used for define a rule when the user reaches a url you configure, a url on your site.
However your goal is to profile users that came from search sources, so that means the referrer has to be a search site. In that case you should use the "came from" behavior, that means, anyone that cames from google and the search terms you select will be on that bucket. For an example I changed the last bucket to that behavior and everything is working now. Just do the same for the others and everything will work fine :-)
About the browser plugin, no matter with account you're using, our BTBuckets API key is linked to your BTBuckets account, so that information will be saved to your acount, the GA reports are the source for that no worries :-)
Please let me know if you have more questions.
BTBuckets Team
Oh I see now. In all fairness that's how the Firefox add-in setup the code. :)
I followed the redirect tutorial video that's on this site. I assumed it was correct since it setup Google, Yahoo and Bing. Who was I to question it :) But I do see where the mistake was now.
I put a bucket in my account named "testing123" if you would like to see how the add-on setup the redirect. It's the wrong code.
Also just noticed that there are now "+" between the keywords. The add-on setup "(google\.).+(&|\?)q=(italy\ climate)" but it appears that it should be "(google\.).+(&|\?)q=(italy\+climate)". I never added the "+" but it appears that they are now in all my buckets.
BTW just noticed that if I get redirected once and try another redirect bucket that should redirect me to a different page I keep getting sent to the first redirect page instead.
For example I setup a bucket that takes me to "exodus.co.uk/walking" when I search for "walking holidays" and another bucket that sends me to "exodus.co.uk/cycling" when I search for "cycling holidays". I was successfully sent to "exodus.co.uk/walking" when I searched for "walking holidays" but when I searched for "cycling holidays" I was once again redirected to "exodus.co.uk/walking" when I should have been redirected to "exodus.co.uk/cycling". This happens for other search terms as well. Seems the cookie sets the first redirect and ignores any redirects after that.
Another issue is when I type in "www.exodus.co.uk" in the address bar or click on the home link to take me to "www.exodus.co.uk" I am automatically sent to "www.exodus.co.uk/walking" even if I go to a different site to reset my last referrer.
Shouldn't the cookie rule be overwritten if a new target occurs and shouldn't the target be ignored if the user doesn't match the predefined conditions?
We'll check the plugin about the missing "+". About the redirect feature, it is to be used when an user enters a bucket and to make sure he/she will reach the right content, and it still active for the time you configured the bucket to be active for an user.
The BTBuckets is simple, yet powerful and allows you many options of actions and combine them. As you're testing many buckets and many redirects the behavior might be strange, but not all users will be on all those buckets you created at same time. The reason it redirects to the "/walking" is because that was the first bucket you get into, so as the redirect run, it can be only done once.
So you could make the bucket active for one day only on the bucket settings, that way the next day the user would be on the bucket anymore and will not be redirected. Also the targeting feature allows you to select one or more url's where it will execute, so you could setup it to run only on specific pages.
Please let me know if you have more questions
BTBuckets Team
I find that behaivior very strange when redirecting a user from the homepage to a more relevant landing page due to search engines choosing a less relevant landing page to send the user to. I understand the ideology behind it when redirecting the user from any other page besides the homepage because it makes the homepage inaccessible. The homepage is still a useful page for my users. I just deem a different landing page to be more relevant during certain situations.
Would be great if there was a checkbox for each target that told the system to only initial it once per user session. This would allow the webmaster the ability to push the user on entry without making parts of the site inaccessible or show a shadowbox once without the user having to see it multiple times if they return to the page.
Anyway keep up the great work and thanks for your help.
Thanks for your feedback, indeed have the ability to control how many times the target would run per user is a nice feature and we're working on that, soon you'll be able to have this control :-)