Hello,
I have lately been spending more time on FB camps and am breaking even, and making some profits on certain days.
My strategy so far is as follows:
1. Create camp with conversion goal of pre-lander views(Custom conversion view content with url of the prelander) - Once receive over 25, or more change goal to below
2. Update conversion goal to lander views(Custom conversion viewcontent with url of the lander) - Once receive over 25, or more change goal to below
3. Update conversion goal to actual conversion, this is the "Thank you page" (Custom conversion view content of url)
Throughout all this, I haven't done any specific targeting, if it is aimed at females I would just target females 18-60 and let FB do the rest as it finds out which segments convert best.
My problem is that with the network I'm working with, I can change the url names of the prelanders and landers through DNS settings (The network has template pre-landers and landers), but the "Thank you page" url seems to be the same for all offers. I am currently marketing the same product in a few different geo's but don't want to be mixing conversion goals up amongst the ad sets. So if Adset NL and Adset DE both trigger a conversion because someone visited the "Thank you page" but through Adset HR, would this have negative consequences? Or does FB keep them isolated somehow so Adset NL only triggers a conversion if someone clicked through THAT ad and landed on the "thank you page"?
Hello,
How are you today? Please connect with our Tech person on skype at Segun.dr , Segun Ketiku, he will help you with this.
Cheers.
The FB pixel is visitor-specific, so if someone arrives at the "thank you" page, it'll only trigger a conversion for that user path. If they arrived through Adset NL, it'll add a conversion on Adset NL, but not on Adset DE. If they arrive through Adset HR, it'll trigger a conversion there but not on Adset DE or Adset NL.
So, unless I'm misunderstanding the question, you should be fine - no need to worry about data cross-contamination.
Custom conversions should work the same way. They're still a per-visitor firing event.