Creating the data source
Requirements
- The profiles used must have at least 100 followers
- The Instagram accounts to be integrated must be of the Business type - personal accounts will not be integrated
- Instagram profiles must be linked to a Facebook page
- The user who registers the data source must have an Owner, Administrator or Editor role on the Facebook page
Instructions
2. Click on “New data source”
3. And then in the data sources search bar look for the Instagram data source and select it
4. Name your data source and click “Continue with Facebook”
ATTENTION: In addition to pop-up blockers, some antiviruses can also prevent the “Continue with Facebook” button from being displayed. So, if you are already using the chrome browser and with an incognito window and the button is still not appearing, disable your antivirus for a few moments and reload the page for the button to appear. Reactivate your antivirus after finishing the process
5. Enter the login information of the Facebook account linked to the Instagram account you want to extract data from and click “Login”
In case your Facebook page is not linked to the Instagram account, follow the tutorial to do it after this step by step
The Facebook user needs to have an Owner, Admin or Editor role for the Facebook page that is connected to Instagram
6. Click on “Continue as…”
7. If you have more than one business account linked to Facebook, it will ask you which accounts and pages you want to use with Kondado. Select and click “Next”
8. On the permissions page, leave them all marked as “Yes” and click on “Finish
9. And then click “Ok” to go back to the Kondado platform
10. Now the linked account and expiration date fields will be filled in, then click on “Save” to save the data source information
11. Now just test the connection to ensure that the access data are all correct and that the Kondado application is able to connect with the source. With the connection operational, the data source is ready to be used in a pipeline.
Pipelines
Summary
Relationship chart
Click to expand
Audience performance
- This object brings data about the current situation of the followers (audience) of your account
- It is possible to configure this pipeline to store a daily history of the read data using the "Keep history" parameter. This storage works like "snapshots" and does not allow retrieving data from before the integration was created or from days when the integration did not run
Replication type: Incremental
Parameters:
- Profiles: Filter the profiles that should be replicated. Leave it empty to replicate all
- Keep history: Indicates whether a daily history of the data should be stored. Track it through the metric_date field
Relationships:
Instagram Audience Insights - Demographic data about followers (gender, age, location)
| Campo | Tipo | |
|---|---|---|
|
date |
[en] Date on which the data was read (UTC). Available only if the pipeline is configured to keep history |
|
|
text |
[en] Kondado ID for the profile |
|
|
text |
[en] Profile username |
|
|
text |
[en] Metric category. Various metrics referring to different categories will be returned, so this field is needed to filter what you want - audience_city: audience city. In this case, metric_key will come with cities and metric_value with the count; audience_country: country of followers. In this case, metric_key will come with countries and metric_value with the count; audience_gender_age: Gender+age group. In this case, metric_key will come with the gender+age group (e.g., 'M.35-44' for males aged 35 to 44) and metric_value with the count |
|
|
text |
[en] The group to which metric_value refers, see the 'metric' field for more details |
|
|
float |
[en] Count of followers pertaining to a metric_key - see the 'metric' field for more details |
Daily profile performance
This object brings data on the daily performance of a given profile
If you are receiving null values in all columns of this pipeline, follow these instructions to resolve the issue
Only the last 2 years of data dare made available by Instagram
Replication type: Incremental with update window
Parameters:
- Update window (days): How many days previous to the savepoint the data can still be refreshed
- Profiles: Filter the profiles that should be replicated. Leave it empty to replicate all
- Read start date (Savepoint): Initial data replication date
Relationships:
Instagram Account Daily Insights - Daily metrics for profile performance
| Campo | Tipo | |
|---|---|---|
|
text |
[en] Kondado ID for the profile |
|
|
date |
[en] Date to which the metrics refer |
|
|
text |
[en] Profile username |
|
|
float |
[en] Total number of new followers per day - returns data up to 30 days back, bringing null if outside this period. Data from more recent days will be returned as zero and will be filled as the savepoint is updated and the data becomes available from Instagram (this effect is controlled with update window). No data is returned for profiles with less than 100 followers |
|
|
float |
[en] Total number of times the account`s media objects were viewed |
|
|
float |
[en] Total number of unique views of the account's media objects |
Media
Media are reels, photos, videos, stories, albums, etc. This object will bring basic information about a given medium, such as its caption and publication
NOTE 1: Due to Instagram limitations, this object only returns the 10,000 most recent media.
NOTE 2: Due to Instagram limitations, stories are only available for 24 hours. This means that if your pipeline is performed during this availability period, the data will be integrated and will remain at its destination.
If no media is being returned or you are receiving null values, follow these steps to troubleshoot the issue
Replication type: Incremental with update window
Parameters:
- Update window (days): How many days previous to the media creation date can it still be refreshed
- Profiles: Filter the profiles that should be replicated. Leave it empty to replicate all
- Read start date (Savepoint): Initial media creation date to replicate the data
Relationships:
Instagram Media - Posts, reels, and stories with their metadata
| Campo | Tipo | |
|---|---|---|
|
text |
[en] Media ID |
|
|
text |
[en] Profile ID |
|
|
text |
[en] Profile username |
|
|
timestamp |
[en] Creation date of the media in UTC |
|
|
float |
[en] Like count - excludes sponsored activity. Returns 0 if the account has set to hide likes |
|
|
text |
[en] Owner's media ID |
|
|
boolean |
[en] Boolean indicating whether comments are enabled |
|
|
text |
[en] Post link |
|
|
text |
[en] Post text. The '@' symbol will not be returned. The text will be treated for removal/replacement of characters not conforming to the ANSI standard |
|
|
text |
[en] Thumbnail URL of the media - available only for videos |
|
|
float |
[en] Comment count |
|
|
text |
[en] Media type (IMAGE, CAROUSEL_ALBUM, VIDEO, etc) |
|
|
text |
[en] Platform where the media is published. Can be AD, FEED, STORY, or REELS. |
|
|
boolean |
[en] Boolean indicating if the media is a story |
|
|
text |
[en] Media code, part of the permalink |
|
|
text |
[en] Media image/video URL |
Media performance
This object will bring information about the consolidated performance (total period) of your media
It is possible to configure this pipeline to store a daily history of the read data using the "Keep history" parameter. This storage works like "snapshots" and does not allow retrieving data from before the integration was created or from days when the integration did not run
NOTE 1: Due to Instagram limitations, media with less than 5 views won't be returned.
NOTE 2: Due to Instagram limitations, stories are only available for 24 hours. This means that if your pipeline is performed during this availability period, the data will be integrated and will remain at its destination.
If no media is being returned or you are receiving null values, follow these steps to troubleshoot the issue
Replication type: Incremental with update window
Parameters:
- Update window (days): How many days previous to the media creation date can it still be refreshed
- Profiles: Filter the profiles that should be replicated. Leave it empty to replicate all
- Keep history: Indicates whether a daily history of the data should be stored. Track it through the metric_date field
- Read start date (Savepoint): Initial media creation date to replicate the data
Relationships:
Instagram Media Insights - Engagement metrics for media posts, stories, and reels
| Campo | Tipo | |
|---|---|---|
|
date |
[en] Date on which the data was read (UTC). Available only if the pipeline is configured to keep history |
|
|
text |
[en] Media ID |
|
|
text |
[en] Kondado ID for the profile |
|
|
text |
[en] Owner's media ID |
|
|
timestamp |
[en] Creation date of the media in UTC |
|
|
boolean |
[en] Boolean indicating whether comments are enabled |
|
|
text |
[en] Post link |
|
|
text |
[en] Post text. The '@' symbol will not be returned. The text will be treated for removal/replacement of characters not conforming to the ANSI standard |
|
|
text |
[en] Thumbnail URL of the media - available only for videos |
|
|
text |
[en] Media code, part of the permalink |
|
|
text |
[en] Media image/video URL |
|
|
text |
[en] Media type (IMAGE, CAROUSEL_ALBUM, VIDEO, etc) |
|
|
text |
[en] Platform where the media is published. Can be AD, FEED, STORY, or REELS. |
|
|
boolean |
[en] Boolean indicating if the media is a story |
|
|
text |
[en] Profile username |
|
|
float |
[en] Total number of taps to view the next photo or video in a story |
|
|
float |
[en] Total number of taps to view the previous photo or video in a story |
|
|
float |
[en] Total number of times someone exited the story |
|
|
float |
[en] Total number of swipes in a story |
|
|
float |
[en] Total number of replies (comments) on the story. The value does not include replies from users in the European Economic Area (EEA). If the story was created by a user in the EEA, the returned value will be zero |
|
|
float |
[en] The number of times your content has been played or displayed. Content includes reels, posts, and stories |
|
|
float |
[en] Total number of unique Instagram accounts that viewed the media - excludes sponsored activity |
|
|
float |
[en] Total number of unique Instagram accounts that saved the media - excludes sponsored activity |
|
|
float |
[en] The number of likes, saves, comments, and shares minus the number of dislikes, removals of saves, and deleted comments. If a story: number of replies and shares |
|
|
float |
[en] Number of accounts that started following the profile |
|
|
float |
[en] Number of comments on the post |
|
|
float |
[en] Number of likes on the post |
|
|
float |
[en] Number of profile visits |
|
|
float |
[en] The number of shares of your post |
Profiles
- If any profile you are connected to is not being returned or even the columns are coming with almost all null values, follow these instructions to solve the problem
- It is possible to configure this pipeline to store a daily history of the read data using the "Keep history" parameter. This storage works like "snapshots" and does not allow retrieving data from before the integration was created or from days when the integration did not run
This pipeline is free
Replication type: Incremental
Parameters:
- Profiles: Filter the profiles that should be replicated. Leave it empty to replicate all
- Keep history: Indicates whether a daily history of the data should be stored. Track it through the metric_date field
Instagram Profiles - Business and creator profile information
| Campo | Tipo | |
|---|---|---|
|
date |
[en] Date on which the data was read (UTC). Available only if the pipeline is configured to keep history |
|
|
text |
[en] Kondado's internal ID for this profile |
|
|
text |
[en] ID of the associated Facebook page |
|
|
text |
[en] Profile username |
|
|
text |
[en] Profile name |
|
|
text |
[en] Profile website URL |
|
|
text |
[en] Profile bio text |
|
|
float |
[en] Total number of Instagram users following the user |
|
|
float |
[en] Total number of Instagram users the user follows |
|
|
float |
[en] Total number of media published on the user |
Notes
Linking your Instagram account to the Facebook page
1. On Facebook, on your page, click on “Settings”:
2. In page settings, then click on “Instagram”:
3. Click on “Connect Account”:
4. Enter your Instagram login information and click “Login”:
5. Click on “Analyze Connection” and click on “Continue” until you reach the Instagram authentication page (to do this process you need to be the owner of the page):
6. Enter your Instagram login information:
7. Your Facebook page will be linked to Instagram.
Troubleshooting Permissions
First, check that the requirements listed on the beginning of this tutorial are met.
If they are and you are still unable to obtain the data of a given profile, this could be due to a data source failure on the Facebook side and you will need to go through Kondado's authorization process again:
1) Log in to your Facebook account which is connected to the Instagram profile page
3) Find the Kondado icon, select it and click Remove
4) Go to Kondado platform > Data source > find your Instagram data source and click the rightmost switch button to disable it
5) Follow the instructions to add a new Instagram data source
6) Try creating a new pipeline with the new data source created above
7) If you have another Kondado Facebook or Instagram data source, the above process will remove the permission that was previously granted to Kondado and you will need to reauthorize the other data sources. In this case, just access them > EDIT > Authorize button > Authorization process > Save
8) If the problem still persists, it may be necessary to recreate the link between Instagram and Facebook:
9) Follow the steps on "Linking your Instagram account to the Facebook page" section located above to reconnect Instagram and Facebook
⚠️ Meta Compliance Notice
Kondado’s Facebook and Instagram integrations comply with Meta’s Developer Policies (https://developers.facebook.com/devpolicy/ and https://developers.facebook.com/terms/)
Data obtained from Meta APIs (such as ad metrics, lead forms, and page insights) is intended solely for analytics and reporting within the advertiser’s own account or their authorized agency.
It is strictly prohibited to use this data to create or enrich individual profiles, perform retargeting, share it with third parties, or use it in any way not authorized by Meta.
Violation of these rules may result in suspension or termination of the user’s account.
- Part of this documentation was automatically generated by AI and may contain errors. We recommend verifying critical information