Data doesn't match between the Source, Coupler preview, and Destination

When pulling data from a Source app, you see that you get different values in the Coupler.io preview (aka "Data sets" step), or in the Destination app after import.

---

General suggestions

To understand where the issue is - in raw data, destination settings, used template, etc. - compare the following to understand where the mismatch starts:

• Your original data in the Source app <> data you get in the Destination after Coupler.io import

• Your original data in the Source app <> Preview in Coupler.io ("Data sets" step)

• Preview in Coupler.io ("Data sets" step) <> data you get in Destination after Coupler.io import

Data mismatch between Source <> Coupler.io preview ("Data sets" step)

Mind that the data shown in the Coupler.io preview ("Data sets" step) is the same data Coupler.io receives from your source app API. If the data in the Data Set doesn't match what you see in your source, please ensure the dataset you're looking at in your source app matches the settings you used in the "Sources" step.

For example, consider reviewing these settings:

• Dates - you must select the same dates in your source UI and in Coupler.io Source settings

• Same data entity - you must select the same data entity or report type - e.g., if you are checking the campaign-level stats in your source UI, you must also fetch the campaign-level data in your Coupler.io Source settings

• Same columns - you must check the same columns in your source UI and in Coupler.io

• Date aggregation - make sure to select the same date aggregation (Split by) setting in Coupler. E.g. you may be checking daily results in Coupler.io and monthly/totals in Facebook Ads;

• Filters you applied both in the "Source" step and "Data sets" step (filter feature) - make sure to select the same filters applied in the UI and on the filters applied in Coupler

• other settings are the same.

Please note that the Coupler.io preview ("Data sets" step) shows the first 500 rows returned by the source app's API only, and you must consider this when comparing the data on the source UI and on the preview.

Data mismatch between Source <> Destination

If you see a data mismatch between your Source UI and the Destination app after import with Coupler.io:

1. Make sure you are looking at the correct destination file. E.g. you might have selected one sheet/report as your destination in Coupler.io, but are looking at a different sheet/report for the result

• Open your data flow >> Run >> follow the green "View results" button after the run is successful. This will open the correct destination file.

2. Open your data flow >> Edit >> go to "Data sets" step >> check if the data there matches your Source data or not.

• If the data in the "Data sets" step is correct (matches your Source data) >> check the settings used in your Destination. E.g. if it's a Looker Studio report you're looking at, make sure you're looking at the same dates, metrics, etc.

• If data in Data sets is not correct (matches your data in Destination and doesn't match your Source data) >> then it's a case with data mismatch between Source <> Coupler.io preview (aka "Data sets" step). Check the corresponding steps from the above section.

---

Facebook Ads data source

ROAS metric mismatch

There may be a case with getting a higher ROAS metric value in Facebook Ads UI than in Coupler.io imported data.

It might happen when using a different attribution window in Coupelr.io settings, than you use in Facebook Ads.

From ROAS Ad Rules - Marketing API - Documentation - Meta for Developers :

"This attributes all mobile app purchase values within 7 days of users who clicked on the ad in the lookback window, excluding the most recent 7 days since they include immature data. If the user clicked on the ad yesterday, we do not include that user in the ROAS computation, since they still have 6 days of potential purchases.

Check what attribution setting you are using and make sure it matches the one you use in FB Ads:

---

Tableau data source

Not all tabs/sheets/graphs are pulled

Due to the specifics of the Tableau API, when pulling data from the Tableau view (dashboard), the alphabetically first worksheet (tab/sheet/graph) from this view will be pulled.

E.g.:

The first worksheet we see in the selected view is "Control Activity Type".

However, the first worksheet alphabetically is "Activities Total". As such, data pulled with Coupler.io will match data from the "Activities Total" tab:

Columns are returned as rows, under columns "Measure Names" and "Measure Values"

Tableau API returns CSV data. Coupler.io just converts it to JSON, and that's how it is displayed in the destination further.

Because of it, you may see columns from Tableau shown as rows in Coupler.io, grouped under columns "Measure Names" and "Measure Values".

As a workaround, you may aggregate data in the needed way in the Destination. E.g.: create a Pivot table in a destination spreadsheet, with 'Measure Names' as Columns and 'Measure Values' as Values:

---

TikTok Organic data source

TikTok Organic API has several data incompleteness and data discrepancy cases, which may affect how you see data in TikTok UI vs after it's pulled from it.

Day-level data latency

Offline data (such as likes , and audience_countries ) usually have a delay of 24-48 hours (UTC Time).

Reference from TikTok API docs:

Latencies for data fields of /business/get/ and /business/video/list/ fall into two categories: no latency, and day-level latency.

- No latency: Real-time data (such as username , and share_url ) usually have no latency.

- Day-level data latency: Offline data (such as likes , and audience_countries ) usually have a delay of 24-48 hours (UTC Time).

Data incompleteness

Reference from TikTok API docs:

Q1: When I set the start_date to a certain date (for instance a date in July) in /business/get/, why do I only see profile data from some time later (for instance August) onwards?

A: It might be due to the following reason:

The data you can get from /business/get/ depends on the availability of corresponding TikTok Analytics data in the app and at https://www.tiktok.com/analytics. In this case, it's likely that the TikTok account enabled TikTok Analytics only some time after the start_date you set. Therefore, any profile data prior to the actual date when TikTok Analytics is enabled won't be available through the API.

Data discrepancy

Reference from TikTok API docs:

Q1: Why does the shares in /business/video/list/ show more shares than the share count displayed on the TikTok web UI?

A: It might be due to the following reason:

The share count displayed in the shares field from /business/video/list/ corresponds to the number of shares shown in the For You feed on the TikTok mobile app. It includes both external shares and internal shares sent to friends using the "Send to friends" button. In contrast, the share count displayed on the TikTok web UI only includes external shares. For example, if a video is shared externally 30 times and shared with friends within the TikTok app 20 times, the value of shares from the API will be 50, but the share count displayed on the TikTok web UI will be 30.

---

If you can't identify the data mismatch reason after going through the above troubleshooting steps, contact our support team with the following information:

• Your Coupler.io data flow ID (link);

• Screenshots from the source UI showing the filters (date filters or other settings) applied and the data you're expecting to also get from Coupler.io;

• If possible, share your destination file with the data imported with Coupler.io.