For a business whose real sales live in Power BI. Kunads compares what Google and Meta claim with what actually sold — so it needs the net sales, once a day. Two ways: a daily flow (about an hour to set up), or a CSV export once a month. Nothing is installed in your Power BI and Kunads never changes anything in it.
kimp_); it is shown once.Runs every morning and re-sends the last 60 days, so returns and late edits are corrected — an order sent again is updated, never doubled. Sending an order again updates it. Needs one Power Automate Premium licence for the person who owns the flow (the HTTP step is a premium connector, about $15 a month).
EVALUATE
SELECTCOLUMNS (
SUMMARIZECOLUMNS (
'Sales'[OrderNumber],
'Sales'[OrderDate],
'Sales'[Status],
FILTER ( ALL ( 'Sales'[OrderDate] ), 'Sales'[OrderDate] >= TODAY () - 60 ),
"Net", SUM ( 'Sales'[NetRevenue] ) -- net of VAT, shipping and returns
),
"id", 'Sales'[OrderNumber],
"date", 'Sales'[OrderDate],
"status", 'Sales'[Status],
"value", [Net]
)
-- one row per ORDER (its lines summed), the last 60 days every morning,
-- so a return made weeks later still corrects its orderhttps://app.kunads.ai/api/import.Authorization = Bearer kimp_YOUR_KEY, and Content-Type = application/json.{"orders": } and put First table rows from step 2 (Dynamic content) after the colon. In code view it reads like this; Kunads reads Power BI's [id]-style column names as they are:{
"orders": @{outputs('Run_a_query_against_a_dataset')?['body/firstTableRows']}
}{"ok": true, "stored": …}. In Kunads the orders appear on the account within a minute.The full field list and other ways to send data: the import guide.