Troubleshooting: Data doesn't match between Source-Coupler preview-Destination

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

1. General suggestions
2. Facebook Ads data source
3. Tableau data source
4. TikTok Organic data source

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 Destination after Coupler.io import
• Your original data in the Source app <> Preview in Coupler.io (aka "Transformations" step)
• Preview in Coupler.io (aka "Transformations" step) <> data you get in Destination after Coupler.io import

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

Mind that the data shown in the Coupler.io preview (aka "Tranformations" step) equals the data Coupler.io receives from your source app API. If data in Tranformations 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 Coupler.io "Data Source" step. E.g.:

- dates (you must select the same dates in your source UI and in Coupler.io Source settings);

- same data entity (you must select same data entity -  e.g. same report type - in your source UI and in Coupler.io Source settings);

- same columns (you must check the same columns in your source UI and in Coupler.io);

- other settings are the same. E.g. when pulling data from Facebook Ads, check that the "attribution window" and "split by" settings used in Coupler.io match the "attribution window" and "split by" settings you use in Facebook Ads. E.g. you may be checking daily results in Coupler.io and monthly/totals in Facebook Ads;

- etc.

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 importer >> Run >> follow the green "View results" button after the run is successful. This will open the correct destination file. 

2. Open your importer >> Edit >> go to "Tranformations" step >> check if the data there matches your Source data or not.

• If data in Transformations 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 Transformations 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 "Transformations" step). Check the corresponding steps from the above section. 

Facebook Ads data source 

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 window you are using and make sure it matches the one you use in FB Ads:

Tableau data source

1. Not all tabs from Tableau are pulled 

Due to the specifics of 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:

2. Tableau columns are returned as rows in Coupler.io, 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 TokTok 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).

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.