Home > Questions and Answers > Traffic Source Questions

Facebook campaign (5)


10-22-2011 03:14 PM #1 consumercpa (Member)
Facebook campaign

Hey,

Okay so I'm trying to do some internal traffic through Facebook and have a question. I read the Facebook campaign walk through that I received in an email and tried to follow it using my own niche. But I have a question. How do you get Facebook to approve your ad if your putting a CPA tracking URL and it just goes to the offer?


10-22-2011 08:24 PM #2 zeno (Administrator)

Quote Originally Posted by consumercpa View Post
Hey,

Okay so I'm trying to do some internal traffic through Facebook and have a question. I read the Facebook campaign walk through that I received in an email and tried to follow it using my own niche. But I have a question. How do you get Facebook to approve your ad if your putting a CPA tracking URL and it just goes to the offer?
You want to avoid going straight to an affiliate URL as their geo-redirection will screw you over (i.e. FB reviewers get bounced to something dodgy if not in X country).

I would use a domain of yours, e.g. a tracking domain, and point to a php file which then carries out a redirect. I set mine to send people to my affiliate link if they are from the appropriate countries and directly to the offer page URL if they are from anywhere else, thus avoiding the networks geo-redirection issues.

Assuming you have your own server, get geoip installed - http://ctrtard.com/code/blazing-geo-...n-your-server/. I'm using the Apache mod_geoip extension rather than the php one but they basically do the same thing. If you have good hosting then get them to install it for you.

Once that is done you can send your adverts to http://domain.com/campaign/index.php, or whatever. Then that index.php will be a redirect file. This is what mine looks like using the mod_geoip extension:

Code:
<?php

    $country = getenv(GEOIP_COUNTRY_NAME);
    $country_code = getenv(GEOIP_COUNTRY_CODE);

switch($country_code) {
case 'FR':
header('Location: http://www.france.com');
exit;
case 'DE':
header('Location: http://www.germany.com');
exit;
case 'NZ':
header('Location: http://www.derp.co.nz');
exit;
case 'US':
header('Location: http://www.google.com');
exit;
default: // exceptions
header('Location: http://www.offer-lander-url.com');
exit;
} 
?>
Just realised I don't need the "$country = getenv(GEOIP_COUNTRY_NAME);" in there but meh that's what happens when you are rewriting other files.

There is also a simple georedirect php script available but i do not recommend it - it went down during a campaign i had running so was no redirecting properly, i am seriously lucky i caught it early on! It is available here - http://www.trafficplusconversion.com...ed-on-country/

Lastly, you can do a very simple redirect based on browser language, which is very simple but won't guarantee you consistently accurate redirects. I can't seem to find how i used to do this since i replaced all my scripts with mod_geoip stuff.


10-22-2011 08:54 PM #3 consumercpa (Member)

I see, I know PHP so not an issue. Thanks for the code. There is one thing I'm still confused about though. Will Facebook will approve a URL that redirects to the actual campaign landing page? I thought it was against their TOS.


10-22-2011 09:37 PM #4 zeno (Administrator)

No it's fine. Firstly they do realise tracking is a must and that often requires going through a tracking domain first. The only time this can be an issue is with things like dating where the user has to end up at the same domain as is in the advert URL. I'm not sure how well a simple php redirect works in this instance as I use an API platform with it's own redirection/tracking service which they permit completely, and it displays in the advert URL to the user - so it would say track.apiplatform.com, then redirects elsewhere. Since it's and API platform they have different standards.

With redirects what they dislike is users being redirected differently depending on where they are from - so if they check on the campaign from a German IP they expect to go to the exact same page they get to from the US. Your redirect is actually giving them exactly what they want! Wherever they access it from they get quickly bounced to the offer page so what do they care? They could use live http headers or a web console to watch the redirects but does it really matter if in those few seconds they jump through 2 URLs or a couple of tracking domains? Cloaking is another ball game though, there you are trying to selectively redirect FB reviewers and that is a) more difficult and b) the destination for real users is different to what they are sent to, hence against their ToS.


10-23-2011 03:56 PM #5 consumercpa (Member)

Quote Originally Posted by zeno View Post
No it's fine. Firstly they do realise tracking is a must and that often requires going through a tracking domain first. The only time this can be an issue is with things like dating where the user has to end up at the same domain as is in the advert URL. I'm not sure how well a simple php redirect works in this instance as I use an API platform with it's own redirection/tracking service which they permit completely, and it displays in the advert URL to the user - so it would say track.apiplatform.com, then redirects elsewhere. Since it's and API platform they have different standards.

With redirects what they dislike is users being redirected differently depending on where they are from - so if they check on the campaign from a German IP they expect to go to the exact same page they get to from the US. Your redirect is actually giving them exactly what they want! Wherever they access it from they get quickly bounced to the offer page so what do they care? They could use live http headers or a web console to watch the redirects but does it really matter if in those few seconds they jump through 2 URLs or a couple of tracking domains? Cloaking is another ball game though, there you are trying to selectively redirect FB reviewers and that is a) more difficult and b) the destination for real users is different to what they are sent to, hence against their ToS.
Got it, makes sense. Thanks!


Home > Questions and Answers > Traffic Source Questions