I am trying out the Facebook connector for retargeting a custom audience. The documentation and the reality do not match entirely. Maybe someone has an idea to use.
I would like to try out the feature by using a finite customer list in FB, containing email addresses (more than 20, I know). I have an ad using this audience, it is reviewed and OK.
In Audiencestream, in the connector setup, Action tab, the Custom audience must be selected. On the other hand it says 'Audiences created from customer files are not displayed'. Hmm...
In the documentation provided you recommend that audience is created from the Connector, which I did. I however never got the small check mark in the connector setup. I then added the customer file in FB.
So my question is, how should I understand the required field for the custom audience in the connector, which cannot be displayed since it is based on a customer file. How is the connection then made to FB? Can I even expect this to work?
I am not the best person to answer this, @james_hartley might be able to provide more. Here is what I know.
If you create an Audience in FB absent of Tealium, FB automatically hashes the email addresses etc and essentially treats those audiences separately from website traffic. So there is a conflict between our API usage and sending data in to the Customer File type of Audience. Therefore, we hid those types of Audiences to avoid customer issues. So it seems like those need to be managed separately, but Jim can speak more to that.
OK let's hope that your colleague will be able to jump into this thread, @dan_george.
If FB internally hashes the email addresses in the customer file I can clearly see a potential risk that no match will be found with the connector 'poking' FB. I did try another type of audience in FB in the first run, but I never managed to get it to work. With a customer file there is a much more clear relation, at least during initial tests.
Talked to a Digitial Strategy and he states that you'll need create Audiences from Website data and that will allow the data flow. Or create the audience from our connector. The customer file option, I believe, allows you to upload additional data on those users, but AudienceStream cannot post data using that option.
I think that pretty much sums up what you're seeing, right?
I guess that brings up the issue where you state you created an audience within AudienceStream but it's not showing up as an option, is that still occurring?
Thanks for digging into this. However, when I again read the documentation provided here these things don't add up. This is what it says about custom audiences in the connector setup:
"On the Facebook site, you will have the option to create audiences based on a customer list, website traffic, or app activity. For this example, create your audience based on a customer list. It is also worth noting that in order to use your custom audience, it must contain a minimum of 20 entries. If your audience has been created successfully, a small "check" icon should now appear beside the button."
That whole section needs a review since I have the feeling that the author mixes the two different approaches to the creation of the custom audience, either from the Connector setup or from within Facebook.
I will test what you suggest, not using a customer file audience, and see if I can get it to work.
We'll definitely take a look at the documentation @per_lundqvist and get it updated. We apologize for the inconvenience and thank you for pointing it out to us.
Regarding the audience that you've created, you can use the dashboard reports in AS to see how many times the action has triggered to see if you've reached over 20. I state this because sometimes audiences are created with criteria where only internal personnel are targeted at first so your co-workers may have tested too soon.
Also, I believe the ad slots are auctioned, right? Meaning you could have been outbid? If I remember correctly when we setup our initial tests with Google we had to set our cost per ad really high just so we could verify it was working. Not sure if that's the case here, just food for thought.