- reposting this as a single thread following @caurmen recommendation that people might find this useful -
Note: CPVLab will come out with a documentation (or probably a better way to this) soon from what I understand.
Here's how you import FB Reports into CPVLab to properly build them and know if you are making the monies 
1) Go to CPVLab > Ad Spend Report Templates and build a new template that looks like this:

Note: in the Assign Template To field, if you haven't already set up Facebook as a traffic source in CPVLab, you need to do it:
Go to: Settings > Traffic Sources and add it there.
2) Make sure when you're creating your camps in FB (or change them after, if you want to try this on existing camps) your ad names (In FB) are the same name you include in your &keyword=EDIT token.
For example:
In Facebook, one of my ads is called : AD001 then I'll add that same name in my CPVLab URL:
http://yourtracker.com/base.php?z=00...hfksdjhfksdjhf&keyword=AD001
3) Go to FB Reports and set it up like this and export it:

PRO TIP: most likely you'll be running lots of camps. You can Filter By > Choose Campaign and select only those that you'll like to include in the report!
4) In CPVLab go to > Upload Reports and upload the .csv file you just downloaded from FB

Important: If the report you downloaded from FB is from today, make sure you select the SAME date in CPVLab or it won't work. Always make sure both the dates on FB and the Report are the same.
Also, make sure you select the FACEBOOK REPORT TEMPLATE.
Upload ad visualize your report with accurate CPC, EPC, ROI, etc.
Hope it helps!
Exactly what I was looking for. Just made the switch to CPV lab and that was bugging me that there was no documentation for this. Thanks
There are a lot of things in CPVLab that a someone starting out might find very confusing (I still haven't figured out half of the power of CPVLab) but their support is fantastic. Just shoot them an email and in less than 48 hours, I'm sure you'll get an answer with a very detailed explanation.
Excellent stuff! Thanks!
This one's going in the newsletter.