Knowledge Base/Product Documentation/Known Issues & Bugs

PlannedDoneNot planned

Cost data inaccurate or unavailable for certain engines

Colin Murphy
suggested this on March 23, 2010 13:51

Updated 7/30/10

SingleFeed's tracking system is able to track clicks and orders.  However, cost information we have to get from the shopping engines.  Every day they send us this data for all of our customers.  Because we are relying on their data, it makes it more difficult to integrate into our system (particularly matching the cost to the appropriate product) and we aren't always able to accomplish this.  We are working on improving our matching process and providing this information consistently.

This means that you will see "0.00" or "N/A" in the SingleFeed Reports "Cost" column. You may also notice that the "Avg CPC" and "ROAS" columns are blank, as they are reliant on the data in the "Cost" column. 

We are currently working on a two phase project to enhance the SingleFeed reports to include cost data.

The first phase of this project will be to include cost data on your "reporting by engine" report for the engines that are currently able to supply us with this information (those engines are Shopzilla, NexTag, Shopping.com, Become, Smarter, Pronto). We hope to have this completed in the next few months.

The second phase of the project will be to include cost data more granularly for these engines, on the "reporting by product" report. There is no current ETA on when this feature will be launched.

 

Comments

User photo
Colin Murphy
SingleFeed

This issue is resolved.  If you are still not seeing cost data for a given engine, please file a support ticket and let us know.  It could mean that the shopping engine is not providing us with the appropriate cost information for your account. If you have recently activated SingleFeed tracking, please allow several days for cost data to appear. 

November 29, 2010 16:44.
User photo
Joonas Y.
SingleFeed

Updated 5/17/11

Product level cost data is now available! Please review our FAQs for common questions and solutions.

May 17, 2011 15:50.
Topic is closed for comments