Try our plataform
Common Connector Questions Guide

Index

Facebook

#1 – Most common reasons for discrepancies between metrics from integrations and Facebook Ads reports

Breakdown

Due to how certain metrics are calculated by Facebook (some unique metrics are based on sampled data – learn more here), when summing up data obtained with breakdowns, the result may be different from that obtained without breakdowns.

See more about breakdowns in the Facebook connector documentation.

To check if your integration has breakdowns, simply locate it on Kondado's Integrations page, access it, and click on "Details". On the right side of the screen, you'll find the integration properties.

If you want to directly compare Facebook reports with your integrations data, we recommend not configuring them with breakdowns. Note that once an integration has already been configured with breakdowns, you'll need to create a new one without them for comparison.

Period

The period defines the granularity of the metric_date column. It's useful for better measurement of some "count distinct" type metrics that may be different in a monthly sum (with daily granularity) compared to the month's total (with monthly granularity).

Campaign structure levels

Facebook ads have three structure levels: Campaign, ad set, and ad. When comparing data with your Facebook reports, the data must be at the same structure level as in Facebook.

For example, summing metrics from all ad sets of a campaign will probably not yield the same result as the campaign view (not broken down by ad set) for the same period in the Facebook Manager.

This occurs because Facebook's unique metrics don't duplicate users, so if the same user was impacted by 2 different ad sets in the same campaign, they'll be counted in both ad sets, but in the consolidated campaign view, they'll only be counted once.

Attribution settings

Facebook's attribution configuration determines the time period during which, after being impacted by an ad, a user's actions can be attributed to it. For example, a user may be impacted by an ad on Monday, convert on Wednesday, and have the conversion attributed to the ad if the attribution window is 3 days.

For your integration data to be consistent with your Facebook reports, it's important that it has the same attribution (or update) window as your Facebook configuration. If your configuration in Facebook is different from the attribution window used in your Kondado integration, it will impact the values of the result and conversion metrics, for example.

The update window is configurable when creating your integration in Kondado and can be changed at any time through an advanced edit.

To know which attribution/update window is being used in your integration, just enter it and click on "Details", the information will be within "Properties".

Metric version

Some metrics – especially in the "Actions" tables – have multiple versions (for example "Purchase", "Omni Purchase" or "Onsite Conversion Purchase") that sound similar but may represent different measurement methodologies. Check which metric best meets your needs and the value you're comparing in the documentation.

#2 – Difference between the "page_fans" metric and the number of followers in Facebook Page Metrics integration

In the new Facebook page experience, there are two indicators of users who can support your page: those who follow the page and those who like it. Users who like the page can choose to also follow it or not.

The "page_fans" metric indicates the total number of users who liked a page, but doesn't necessarily indicate the number of users who follow it. Read more about this here.

#3 – Difference between the "metric_date" field in Page Metrics integration and dates in Facebook reports

Due to timezone differences between data reported by Facebook on the platform (which is done in Pacific timezone) and via API, there will be a 2-day difference between the platform date and the date obtained through integration.

#4 – When a page doesn't appear for selection when creating the Facebook connector

In step 5 of the Facebook connector creation tutorial, all pages linked to the user that are available for use with Kondado integrations will be shown.

If a page is not selected in this step, it won't be possible to extract data (ads or organic) from it through our integrations. When a page is not listed on this screen, it's probably because the logged-in user doesn't have the necessary permissions for that page. Check your permissions for the page and try again. If the problem persists, contact us through the Kondado app.

Remember that even if you only want to create ad integrations, the user used for connector authentication must have page access permission for the page where the ads are running.

#5 – About Facebook Results data

Through the Facebook API, it's not possible to reflect the "Results" field data shown in the Business Manager interface in this same format. However, since the results are conversions, this data can be obtained through metrics from the Actions table.

For example, when a campaign's result is the number of leads obtained, this value can be retrieved through one of the Actions table metrics related to leads (such as "lead" or "offsite_conversion.fb_pixel_lead").

To better understand how the Actions table works and the available "action_types", check this section in our Facebook documentation.

We also have this tutorial showing how to pivot data from Facebook Actions tables and explaining a bit more about how it works.

#1 – Most common reasons for discrepancies between data from integrations and Google Ads reports

Report attribution type

When comparing data from reports within Google Ads with data integrated by Kondado, it's important to note that while the tool's reports can have two types of attribution (conversion-based attribution or click-based attribution), the data that Kondado reads and integrates is exclusively click-based attribution. Read more about these attribution types here.

Dimensions that may filter results

In some cases, certain dimensions may filter results. For example, using a keyword-type dimension will cause video ads not to be returned.

Date dimension

Some metrics may show discrepancies if compared using different date dimensions, such as comparing the same ad using the 'Month' dimension (with monthly granularity) versus using the 'Date' dimension (with daily granularity).

This occurs because some metrics only count distinct users. For example, the same user may perform an activity on a given ad several times during the same month, but will only be counted once in the monthly view (month dimension), and will be counted for each day of activity in the daily view.

Correct use of metrics, dimensions, and reports

The Google Ads API provides a wide variety of report types for different purposes, and each one has multiple dimensions and metrics available to choose from. See the main links below:

– List of all reports, metrics, and dimensions available in Google Ads integrations with their descriptions.

– Example of how to build an integration to get the main ad statistics from Google Ads.

#2 – About the combination of metrics and dimensions in Google Ads reports

Some metrics and dimensions cannot be combined, so during the integration creation process, the list of possible metrics and dimensions will be constantly reloaded for a few seconds until all possible options are shown. Our backend will automatically filter out metrics and dimensions that are incompatible with your selection.

#3 – Full or incremental integrations with update window

The integration can be full or incremental, depending on the selected dimensions. The dimensions that will make the integration incremental are: Date, Week, Month, Quarter, and Year. If the integration is incremental, we recommend configuring an update window to ensure data retroactively updated by Google is also updated in your destination.

Check our documentation about savepoint and update window.

#4 – About extracting Performance Max campaign data in Google Ads reports

Performance Max campaigns don't have ad groups. Therefore, they won't be returned in integrations that use ad group or ad dimensions, or reports that contain these breakdown fields.

#5 – About extracting "Demand Gen" and Discovery campaign data in Google Ads reports

"Demand Gen" (Generation) campaigns with product feeds are not yet available for reading due to Google Ads API limitations.

Google Analytics

#1 – Most common reasons for discrepancies between metrics from integrations and Google Analytics reports

Date dimensions and period

Metrics that count distinct values (for example, "distinct users") behave differently if you use a "day" dimension versus a "month" dimension. For example, let's say the same user accessed your website on the 1st and 15th of the month. If you use a "day" dimension, they'll be counted as one distinct user on each of those dates; if you sum them up, you'll get 2, but if you use a "month" dimension, that same user will be counted only once, as they're a single distinct user within that month.

Data sampling

For GA accounts with high data volume, there may be differences between values obtained by integration and those viewed in the tool. This occurs due to sampling that GA does when sending data via API for very large volumes.

Correct use of metrics and dimensions

The GA API provides multiple possible metrics and dimensions, some with subtle differences between them, so it's important to make sure the metric or dimension you selected when creating your integration is the correct one for your analysis.

To know which metrics and dimensions to use, you can use this exploration tool created by Google:

– Here's the list of metrics and dimensions: https://ga-dev-tools.google/dimensions-metrics-explorer/

– Here you can test metrics and dimensions before creating your integration: https://ga-dev-tools.google/query-explorer/

The tools provided above for listing and selecting dimensions and metrics are very useful, but in rare cases may generate "false positives" – indicating that a given combination of metrics and dimensions is compatible when it isn't. If you receive an error when running the integration, try removing some selected fields and creating a new integration to identify which one may be causing the issue.

API latency

The Google Analytics API and its web interface may not be in total sync at certain times. Kondado integrations extract data from the GA API, and in these cases may show results slightly different from those viewed on the GA web interface.

Instagram

#1 – Extracting organic and ad data from Instagram

Only organic data is returned in this connector. To get ad data, you should use the Facebook connector, which also brings Instagram ad data.

#2 – Most common reasons for discrepancies in follower metrics

Demographic dimensions not available for all users

Not all Instagram users provide demographic data such as city, country, age, gender, among others. This means that when counting followers segmented by any of these dimensions, the sum will likely be lower than the total number of followers, since some users don't have this data registered.

Follower data by demographic metrics available only for the top 45 results

For demographic metrics like city, country, among others, only the top 45 categories of each are returned. For example, for city, only the number of followers from the top 45 cities with the most followers will be returned.

Profiles with fewer than 100 followers

Data from users with fewer than 100 followers is not counted in audience metrics (fields like follower_count, online_followers, or other audience-related fields).

follower_count and online_followers metrics available only for the last 30 days

The online_followers and follower_count metrics are available via API only for the last 30 days.

Delay in metric availability via Instagram API

Some data used to calculate follower metrics may have a delay of a few days before being made available via the Instagram API.

#3 – When media is not returned in Media and Media Statistics integrations

If you're missing some type of media in your Instagram integration, consider the following factors:

  • The Instagram API may remove data older than 2 years, making it impossible to extract that data;
  • Instagram integrations only bring organic media. To get ad data, you should use the Facebook connector, which also brings Instagram ad data;
  • Due to Instagram API limitations, the "Media" integration only brings the 10,000 most recent media;
  • Due to Instagram limitations, stories are available for only 24 hours. This means that if your integration runs during this availability period, the data will be included; if not, the stories will already have expired;
  • Due to Instagram limitations, in the Media Statistics integration, media with fewer than 5 views won't be returned;
  • If no media is being returned or you're receiving null values, follow these instructions to solve the problem.

#4 – Solving permission problems

First, verify that the requirements listed here are met.

If they are and you're still unable to get data from a given profile, this may be due to a connection failure on Facebook's side and you'll need to redo the authorization process. Follow these steps:

  1. Log in to your Facebook account that is connected to the Instagram profile page
  2. Access the connections settings page at https://www.facebook.com/settings?tab=business_tools
  3. Find the Kondado icon, select it, and click Remove
  4. Access Kondado platform > Connectors > find your Instagram connector and click the switch button on the right to disable it
  5. Follow the instructions to add a new Instagram connector
  6. Try creating a new integration with the new connector created above

If you have other Facebook or Instagram connectors from Kondado, the above process will remove the permission previously granted to Kondado and you'll need to reauthorize the other connectors. In this case, just go to connectors, disable and re-enable each of them.

If the problem persists, you may need to recreate the link between Instagram and Facebook:

  1. Follow the steps described in the "Disconnect Your Facebook Page and Instagram Account" section of this Facebook article
  2. Follow these steps to reconnect Instagram and Facebook

LinkedIn

#1 – Most common reasons for discrepancies in LinkedIn Ads integration data

Demographic segmentation

To protect user privacy, LinkedIn Ads demographic metrics are approximations, mainly impacting impression, click, and conversion numbers. Because of this, you may see slight discrepancies between numbers shown in the tool interface and those integrated by Kondado.

Additionally, the same user can fit into more than one category of the same demographic, being counted twice. For example, a user may have the title of CEO and Founder of a company, or work for companies of different sizes, etc. Read more about this here.

#2 – Most common reasons for discrepancies in LinkedIn organic integration data

Maximum daily data query period

Due to LinkedIn API limitations, the maximum query period for organic data is 1 year (365 days) for the daily period.

Delays in data availability via LinkedIn API

The LinkedIn API documentation warns of some delays that may occur in data availability, such as:

– Followers: 2-day delay relative to the current follower situation;
– Likes and comments: Up to 48-hour delay for comment and like counting.

RD Station

#1 – Tips about discrepancies between integration data and the RD Station tool

  • If you notice that some contact isn't being sent to your destination table, we recommend verifying that all conversion events are being correctly sent to the integration URL (see step 16 of the connector tutorial);
  • Only conversion events in RD Station cause leads to be sent to the webhook and thus integrated to your destination. If you want lead information to be updated in your destination even when there's no conversion, you'll need to integrate a lead update event (follow this tutorial here);
  • Webhook data is sent to your destination only from the moment the webhook is saved. To send contacts that are already registered in your RD Station account (historical load), just click here and follow our tutorial;
  • Some RD dashboard indicators are calculated differently. For example, the dashboard's Lead count shows all visitors who had at least one conversion in the period, which may include leads created in previous periods. See Meaning of each metric in RD Station reports and Explanation of RD Station dashboard indicators.