HELP needed for 1st Ad Creation - Destination URL question. (14)
HELP needed for 1st Ad Creation - Destination URL question.
Hey guys,
So I was going about creating my first ad when I encountered this error on the FB ad platform "You've selected an object that cannot be promoted. Please choose a different object."
Now I understand that this is because the URL I put in as my destination URL contains prosper tracking ID and all, so it's a clear affiliate tracking URL, and that's why FB blocked me from creating an ad around it.
My question is if I go ahead and point it toward www.mydatingsite.com with a double meta refresh going to the affiliate link, won't FB find out and ban my account? And on top of it, since I'm promoting BE2, aren't I supposed to be putting the name of the dating service in my ad text. If I do put BE2 in my ad text and then point the URL to www.mydatingsite.com, won't that raise any flags?
What's the best way for me to put in a destination URL that FB would be cool with, while not violating their guidelines and still being able to get the affiliate ad linked to.
In need of guidance. Forgive the noobness.
I ran into the same problem with my links from PeerFly. What I wound up doing was creating a static html page with an iframe of the affiliate link. Even with the prosper link this works for Facebook.
The html file on your server will look like this:
<html>
<head>
[whatever head stuff you need here, such as title tag, etc.]
</head>
<body>
<iframe src="[your affiliate link]" style="overflow:hidden;height:100%;width:100%" height="100%" width="100%">
<p><a href="[your affiliate link]">Click here! (Your browser does not support iframes)</a></p>
</iframe>
</body>
</html>
Okay great. Yeah I read a post on iframing affiliate offers by luke from peerfly, but wasn't sure how faceboook would feel about that.
Did you mention the products name in your ad text even though it was pointing to your own site? Or did you just not mention any product name? In my case its a dating offer.
Assuming the offer is FB compliant, iFraming is not the greatest way to go. It is more sensible to link to an intermediary redirect file that controls the flow of traffic. This adds little time to the redirect process and you can pass traffic on to any URL afterward, you just need very minimal PHP coding knowledge. The way I typically do it with Facebook is by linking to a file called index.php (e.g. in domain.com/offer/angle/index.php) and having two of them which I swap after approval (rename via FTP), like so:
APPROVAL STAGE:
index.php -> all visitors -> offer URL
indexreal.php -> XX -> Affiliate URL
-> Non/XX -> offer URL
AFTER APPROVAL:
index.php -> renamed indexapp.php
indexreal.php -> renamed index.php
This way you will not get any problems during ad creation because the ad URL sends everything directly to the offer page. Why make things complicated and use archaic iframes...
Thanks for that. When you say XX and NON/XX are you saying that you're only sending a portion of your traffic to the affiliate URL from FB. Or are you saying that FB visitors see the affiliate URL and non facebook see the offer URL?
Alright just submitted the ad with your redirect method. Fingers crossed.
Originally Posted by fatstacks01
Originally Posted by fatstacks01
I was under the impression that his method was better (but not essential) since it prevents ad reviewers from getting bounced to the wrong places (eg. lousy offer walls). Didn't think FB was outright against any kind of affiliate offers, even the legit ones?!
@archer9 - this will depend on whether your affiliate network does geo-redirects on traffic coming to a offer from outside its target countries. Some networks will just let any global traffic through to the offer, which means FB reviewers don't get redirected and your ad doesn't get disapproved. Other networks will redirect, and that's when FB reviewers get upset.
Zeno's approach is a rather clever hack designed to avoid network redirects, make sure everyone sees the same offer, and thus avoid FB getting its panties in the proverbial bunch.
So, you're correct, but don't underestimate FB's willingness to swing the banhammer over the slightest offence. Personally I would recommend taking great pains to avoid sending FB reviewers to an offer wall.
(At least, that's my understanding - Zeno, please feel free to correct if I've gotten anything wrong there!)
Yup, gotta avoid them stupid out-of-geo redirects by aff networks. Frankly, networks should just get rid of them, or at least turn them off across all offers for any affiliate who requests it. Even if they do it's important to have FB ads pointing to a URL that you control - so you can, if unplanned events occur, redirect traffic elsewhere or modify redirection in some way. There are circumstances where you don't need this of course, e.g. suitable tracking system, or if you're direct with an advertiser + using an API client then maybe you won't need to, but that's not the case for most.
Originally Posted by zeno
No, they can come from lots of places, but most often the US.
FYI almost all US Facebook review clicks that come from new submitted ads and edits have ISP = Facebook, OS = Linux (and Chrome v28) and ISP = Joyent, OS = Windows XP (and IE 8). I use these two conditions in MobAffTracker to filter out virtually all clicks that come from ad submission so they don't mess with the real user data. The OS here suggests that the ads are automatically reviewed via virtual machines, or perhaps reviewers sit there with VMs that automatically load ad links for them.
Thanks for the clarification, caurmen and zeno.
Home > Paid Traffic Sources > Facebook & Instagram