I have one thing to make intelligent modal window with facebook like box. Intelligence is in not disturbing first time visitor and all visitors that has liked my FB page. Step by step logic is:
Check cookie, if visitor is here for first time, create cookie with visit time and do nothing.
If visitor returned to site after minimum 24 hours, check if logged in user has liked my FB page. If yes, do nothing.
If returned visitor does not liked my FB page in past, dim browser and display modal (popup) window with facebook like box.
If visitor close modal window without liking FB page, set cookie to do not disturb him anymore.
Sorry for my english. I'm dummy programmer, If you can help me to do this in PHP (for Wordpress as plugin), or if you thing that same plugin exist, please send me a link and I will buy this plugin.
Thank you.
Related
I am completely new to Google Tag Manager. I have gotten it installed on my site, and it is working to count the number of clicks on the register button.
However, what I really want to do is this:
A user lands on the page. I want to place a tracking cookie for the user, and then log the page view along with the tracking cookie ID.
The user then clicks the register button. I then want to track the click event along with the tracking cookie ID.
By including the tracking cookie information, I can then easily see that User A landing on the Page at 10:00, and then at 10:02 Clicked on the Register Button.
It gives a clear picture of what happened on the site. My goal is to drive people to the site through adwords, but I then need to see exactly what happened with these people and how long they were on the site.
Can I do this with GTM/Google Analytics? If so, how? If not, is there some other tool for this?
Take a look at the User Explorer report in Google Analytics.
I am developing a website by using ASP.NET.
I have a page where users can put advertisements to my website. So he has to select the location , ad category type the contact details and post the ad. So after finishing it he has to press the button Proceed.
Then I hope to took him to a new page which showing him how exactly his ad will show in my website. So if he has to do some modifications he can go back and again he has to press the Proceed button after editing it. If he satisfied he can confirms the ad an then the records should add to my database.
So I am wondering where to temporary keep these data and show in the page?
My idea is to store these details in sessions or in cache. I think session will be good. But people are saying that you should avoid using sessions at all cost because it eat ups the memory in server. What I am going to display are not critical data. So I dont want any security regarding the data. So tell me what is the best way to show user's entered data in a another page temporally until user confirm it?
The homepage of my Wordpress site is set to display my latest posts.
I also created a landing page which includes a form for users to fill out for a free consultation.
How can I make it so that when first-time users go to the homepage, they will be redirected to the landing page? (But clicking on my site logo should still take them back to my regular homepage showing my latest posts.)
After users have filled out the "get a free consultation" form on my landing page, we would create a cookie or something so that whenever they next visit the homepage, they will just see the regular homepage with latest posts - not see the landing page any more.
Is there a way to write a code for this?
Thanks in advance!!!
setcookie() is probably a good option.
if(!$_COOKIE["been_here_before"]) {
setcookie("been_here_before", true);
header('Location: /consultation'); // Your free consultation page
}
The way to achive this is a little bit more complicated.
The best practice for this is to have your form in an overlay on the homepage, the user sees the form when accessing your website but has an option to close that layer (exemple:"already fiiled the form..."). After the user submits the form or clicks "close" then set a session variable that will be used so the user won't receive the overlay again in that session. An website that does that is this one which asks the user to register for the newsletter. If the user is already register then he can click "Already registerd?" (=Sunteti deja înregistrat?) and the overlay disapears for that session.
If the form submision is mandatory for all users to get access to the website, then force them to login in the landing page. Here is an example for that.
I am looking to place many Facebook like buttons on a page which i want they to allow me to post to facebook wall of the user who logins through them. Can some one point me on where to find this workflow for .NET. I wish the user clicks on a Like button log ins then with the access token post to wall the content. later if he clicks on other like button it will just post to wall: image test,...
Is this possible? whew can i find code example?
thanks in advance
I am having two GA reporting problems with a site I manage that I am not sure how to solve:
The site is showing up as a referrer to its own domain in GA reports.
My goal completions (sales conversions on 3rd party off-domain
ecommerce cart) are all showing the site's domain as "source" when I
obviously want to see the true "referers" who are sending traffic
that results in goal completions.
My thoughts on potential reasons why this could happening:
I am using absolute paths for internal links, like this:
<a href="http://example.com/contact.html">
as opposed to
<a href="/contact.html">
Could this be it? Users often do click around internally before they purchase.
Also, on several high traffic pages, I am using javascript history backlinks, like this ::
go back
Lastly, I'm doing a 301 redirect on "add to cart" traffic clicks so that
http://example.com/add_to_cart
redirects to:
http://paymentprocessor.com/ugly_url/cart_page.html
(Although this is an external 3rd party domain, my GA code still fires there)
Any guesses why I am experiencing the issues stated at the top here? ... thank you to all you GA wizards.
UPDATE UPDATE UPDATE
Thanks Eduardo for the great answer.
Thought I might share that now for href text links to 3rd party ecomm site I am tracking events with jquery via class, so my _gaq.push to track both the click event and copy the cookie data over from my site to the third party site looks like this:
$('a.index_addtocart_smallest').click(function(){
_gaq.push(['_trackEvent', 'Outbound Links', 'index_addtocart_smallest', 'buy_click'],['_link', 'ssl.thirdpartyecom.net/order/']);
});
And when I use the form action "add to cart" submit in the HTML look like this:
<form action="http://example.com/add_to_cart" method="post" onsubmit="that=this;_gaq.push(['_trackEvent','Outbound Links','index_big_buy_button', 'buy_click'],['_linkByPost', this]);setTimeout(function() { that.submit() }, 100);return false;">
... to track the event, and post the existing cookie to third party server, while adding a delay to the click to make sure it is captured by GA.
In my case I am using the asynchronous syntax for Tracking Between a Domain and a Sub-Directory on Another Domain: https://developers.google.com/analytics/devguides/collection/gajs/gaTrackingSite#domainAndSubDirectory
In your case it's very clear that the problem is with the cart. When you redirect the user to your cart domain he lands on a new domain and lose access to the cookies that he was using on your site. Because GA needs to create a new set of cookies on the cart site it also creates a new visitor id and a new visit, that visit will be a self referral because that's where the visitor is coming from from GA point of view.
Google Analytics keeps state on cookies, __utm*. So when changing domains we need to copy the cookies from the domain you are currently in to the domain you are moving to. The google analytics API offers some methods to implement this. This is often known as "cross-domain tracking" or "multiple domain tracking". Google Analytics documentation offers a good explanation on how to implement it. You can also search Stack Overflow for several questions related to cross-domain tracking, people seem to have a hard time getting it right.
You are free to use absolute or relative links, it makes no difference for Google Analytics at all.
Javascript redirects are usually ok. Even though there are cases where they certainly make things a little bit more difficult your use case of a back button is fine and should not be causing any problems at all. Of course if the javascript redirect changes the domain you are in you are back to the same issue and needs to implement cross-domain tracking.
Sometimes internal referrers are legitimate. One example of legit self referrals: When a user visits a page on your site and stay there for over 30 min, then navigates to a second page. In that case after the 30 minutes the visit expires and when he navigates to that second page a new visit is created. This new visit will be a self referral and the second page will be considered a landing page. That might seem odd at first, but this is a self referral and it's usually fine.