Hi guys, I just wanted to find out the best way for setting up a camp on FB with
I set up my

I then put my standard FB pixel code into the cake aff network for that specific offer under testing a tracking, pixel html. But now not sure how that integrates back to FB. How do I set up a custom conversion on FB, which requires a specific url, such as a "mysite.com/thankyou" page which has my pixel on it? The one way is to just wait for a conversion and see which url generated it I guess.
I've subsequently edited the traffic source to the below which is supposedly dynamic tokens. My understanding is that I can then use the same link for all ads and I will be able to see which ads actually converted in

Thanks, I realised after that first post that there are dynamic tokens. Surely it's possibly to just use that one link which will then let
I have set up custom conversions on my prelander that fire "add to card" conversions when someone clicks through to the offer but wanted to get more detailed feedback also about which FB users actually ended up converting. I'm assuming that the ones that actually converted would be a better custom audience to target too?
Ok great thanks, just wanted to confirm that those dynamic tokens would do the job I wanted them to do.
Ok so you are saying I should just concentrate on users clicking through my lander, to the offer as they are potential conversions, and not worry about actual conversions when talking about the pixel and custom audience creation? Thanks
First things first, make sure your pixel works right when traffic starts coming in by checking its Pageview and/or custom conversion events from your Ads Manager and how that number corresponds with what you see on your tracker. For instance, ALWAYS Pageview number will be higher from an Add2Cart event since ALL visitors to your landing page trigger a Pageview event with Facebook but only those who click your CTA or however else you've defined an Add2Cart event will trigger s such.
Next, all you care is that you've made your unique links on each creative on your PEditor as discussed above.
Pretty much set now. As traffic coming in then you can see from your tracker what exactly converts and where and can start optimizing accordingly
Ok great it looks like pixel is working fine.
But the tinyurl which corresponds to my tracking link is not working:
http://track.xxxxx.com/21a46dee-da0c-409b-84fd-1d6f9b9bd9e7?Source {{site_source_name}}&placement={{placement}}&ad_id ={{ad.id}}&adset.id={{adset.id}}&campaign.id={{cam paign.id}}&ad.name={{ad.name}}&adset.name={{adset. name}}&campaign.name={{campaign.name}}![]() The tracker just shows the token I used and not the actual information. Not sure if that's because of tinyurl not passing headers or what. |
Im using FFlux instead of
For instance, BEFORE you paste edit on PEditor edit it as such:
http://track.xxxxx.com/21a46dee-da0c...b9bd9e7?Source {{site_source_name}}&placement=Mobile&ad_id ={{ad.id}}&adset.id={{adset.id}}&campaign.id={{cam paign.id}}&ad.name=ad3&adset.name=Male1829&campaign.name=iPhone7Sweden
Editing the rest of the info in the link as well, you get the idea. The combination of the above parameters will be identifying uniquely where exactly your visitors are coming from. Now put that fucker in
Thanks, I ending up running it with my standard tracking link as the url and the fields put in the variable fields below such as adid= {{adset.id}} which worked.
But now all of a sudden after the camp running for about 24 hours and getting a conversion, so I know it's working, my ads are not delivering anymore. When I try re-activate them I get this error: Not sure what that is about?
| This item could not be published because ADNAME caused an error when publishing. |
Screenshot?
Traced the problem to my URL... Seems it has been blocked for whatever reason. The offer page url is fine as I can put it in the See more url link and preview it fine but my actually tracking link and my landing page, both on same domain but different sub domains, gets this message.


Yeah, this happens. Either your domain is flagged already which means you should get a new domain and add a CNAME record to point to your flagged domain or it means FB has flagged one of the other domains in your redirection chain, probably the final destination domain.
Solve this by either iframing the destination domain within a Clean domain (at least neutral MyWOT score) or temporarily change the redirection path to a high quality green MyWOT domain from within your tracker UNTIL your creatives successfully pass FB review (from pending review -> to active mode, preferrably with some initial impressions) and then edit the path back from tracker to "dirty" mode
It's strange as my domain is neutral on WOT, the offer page is also neutral but I do see it has an outlink on the offer page to a credit score type of site which is flagged. Could this be the reason?
It has been working fine for the past few days so not sure why it suddenly had a problem as surely it could have picked up the outgoing url's when I first put the tracking link in?
Also if I bait and switch Landing pages surely it will trigger an issue when the end url changes again? As it picked it up this time a number of days of running the offer.
Is your tracking domain different from your landing page domain? Have you ever sent traffic directly to the offer from this tracking domain?
My tracking domain is track.mydomain.com and my LP is realestateleads.mydomain.com so both on same domain. I've done this for ages now with every vertical such as freevouchers.mydomain.com, iphonex.mydomain.com and never been sure if this was a bad idea or not. It was just convenient and saved buying new domains for different topics.
I don't think I've sent direct, just to my pre-lander and then onwards with the typical track.mydomain/click url.
Yeah, it's not really recommended you do that for several reasons, including performance, loading speed and domains getting blacklisted. The 5 or 10 bucks you "save" on domains is NOTHING compared to what you could be losing in terms of the above. I frequently get .club domains from Namecheap, less than $1 each, FB does not seem to have a problem with those.
In your case, your tracking domain getting blacklisted on facebook will also blacklist your landing page domain too, not good. Now you would need to CNAME the tracking domain and update landing page domain from within your tracker when you setup your landing page with a clean domain. Fix that and you should be good2go!
Ok thanks will get a new domain, or 2. I am using AWS s3 for hosting along with NsOne.
Is there anything I need to do in future to prevent this from happening? I testing out my tracking domain now to netflix.com as the lander and it still blocks it but I can use the offer page and it is fine with the link. What caused the domain to be flagged and surely it will cause the new domain to be flagged as well in the near future? Could it be by putting my pixel code in the cake platform? Could my lander have been manually reviewed and flagged for being too much of Flog?
I suggest you get two different domains, one for the landing page that will rarely actually need to be on a new domain again and one that you will CNAME your flagged tracking domain to.
I am not sure exactly what causes domains to be flagged but IME people reporting the ad, posting negative emoticons on the post etc., aka social feedback, gets the domains flagged with FBook where, even if your account not banned, your visitors might start seeing an intermediate FB page where it "warns" them that they are about to get redirected to an unsafe/malicious site. That alone kills your ROI even if your campaigns still running. I do not have a definitive way to figure out when exactly this happens but I usually can tell from a sudden drop in ROI and comments under my post of people complaining this is a virus.
Pixel on the aff network might have something to do with it, I do not do that so I do not know, tho I suspect it would not be the first of my concerns. Same with manual reviews, I would not be too worried about that right now, I believe your priority is to pass by auto-FB bots crawling your flagged links. Just don't do anything "extreme" till you get your ads some initial impressions
Ok thanks I just bought some domains now, but I remember reading that I shouldn't use fresh domains, under 2 weeks old, on FB?
My relevancy scores are between 7 and 8 for my ads and don't think they got too many comments, but obviously don't know if people reported them.
My FB page still has the tinyurl which goes through my original tracking link and is working fine. FB doesn't block it when I click on it so I'm not sure if they are just blocking it at the ad level and not on the actual page.
I have used domains time and again less than 24hrs after purchasing them on FB, no issues IME. It usually blocks it for SOME users, not all of them, it's weird I know, they do it like when they roll out a new feature and make it available only to a random pool of people first to beta test it. Same thing when a domain gets blacklisted. SOME users will get this warning, not the entire pool of your audience
Ok great I will run it soon then and cross fingers it doesn't happen again. I can't imagine how annoying it must be actually doing BH on FB when this is how it is with WH