diff --git a/src/content/docs/components/extractors/social/facebook/index.md b/src/content/docs/components/extractors/social/facebook/index.md index 0804538a0..1563525a3 100644 --- a/src/content/docs/components/extractors/social/facebook/index.md +++ b/src/content/docs/components/extractors/social/facebook/index.md @@ -62,7 +62,7 @@ posts created by a Facebook Page. Each post contains fields such as `caption`, ` and `type`. The fields parameter in such case is `caption,message,created_time,type`. - **Fields/Endpoint Nesting** --- - Posts can contain comments and these can be included in the *fields* as well: `caption,message,created_time,type,comments{message,created_time,from}`. The comma separated list in between the curly brackets `{}` specifies fields of the "nested" [comment](https://developers.facebook.com/docs/graph-api/reference/comment) field/endpoint for each post (feed endpoint). This way, more endpoints can be nested and there is no limit of nesting levels. If you wanted to include likes of posts comments,the fields parameter would be: `caption,message,created_time,type,comments{message,created_time,from,likes{name,username}}`. + Posts can contain comments and these can be included in the *fields* as well: `caption,message,created_time,type,comments{message,created_time,from}`. The comma separated list in between the curly brackets `{}` specifies fields of the "nested" [comment](https://developers.facebook.com/docs/graph-api/reference/comment) field/endpoint for each post (feed endpoint). This way, more endpoints can be nested and there is no limit of nesting levels. If you wanted to include likes of posts comments, the fields parameter would be: `caption,message,created_time,type,comments{message,created_time,from,likes{name,username}}`. - **Fields Parametrization** --- Each field can be parametrized by a dot following a parameter/modifier name and a value in brackets. diff --git a/src/content/docs/components/extractors/social/index.md b/src/content/docs/components/extractors/social/index.md index ea40b8132..1dc44507b 100644 --- a/src/content/docs/components/extractors/social/index.md +++ b/src/content/docs/components/extractors/social/index.md @@ -12,4 +12,5 @@ The following data source connectors allow access to data from social networks: - [Facebook Pages](/components/extractors/social/facebook/) - [Instagram](/components/extractors/social/instagram/) - [YouTube](/components/extractors/social/youtube/) +- [YouTube Reporting](/components/extractors/social/youtube-reporting/) - And [more](https://components.keboola.com/components) diff --git a/src/content/docs/components/extractors/social/instagram/index.md b/src/content/docs/components/extractors/social/instagram/index.md index 3876c693a..618e7bfff 100644 --- a/src/content/docs/components/extractors/social/instagram/index.md +++ b/src/content/docs/components/extractors/social/instagram/index.md @@ -17,7 +17,7 @@ the configuration process is almost identical to configuring the [Facebook](/com ## Configuration Before you begin, make sure you have a Facebook page, a role on that page, and an Instagram account. The Facebook -page needs to be [connected to the Instagram Business Account](https://developers.facebook.com/docs/instagram-api/getting-started#connect). +page needs to be [connected to the Instagram Business Account](https://developers.facebook.com/docs/instagram-platform/instagram-api-with-facebook-login/get-started/). [Create a new configuration](/components/#creating-component-configuration) of the **Instagram** connector. Then click **Authorize Account** to [authorize the configuration](/components/#authorization) with a Facebook account @@ -58,14 +58,14 @@ the output table name will be `foo_insights`. ### Endpoint The *Endpoint* option describes a significant URL part of the request made to the Facebook Instagram API. The absolute URL is in the following form: `https://graph.facebook.com//`. -A typical example would be the [media](https://developers.facebook.com/docs/graph-api/reference/instagram-media). +A typical example would be the [media](https://developers.facebook.com/docs/instagram-platform/instagram-graph-api/reference/ig-media). If left empty, the *Endpoint* option references data of the Instagram Business Account itself, which in fact -refers to the [user](https://developers.facebook.com/docs/graph-api/reference/instagram-user) endpoint. +refers to the [user](https://developers.facebook.com/docs/instagram-platform/instagram-graph-api/reference/ig-user) endpoint. ### Fields The *Fields* option describes data returned from the endpoint. Typically, it is a comma-separated list of fields, but it also can be used to parametrize the fields and nest more endpoints into it. -The [media](https://developers.facebook.com/docs/graph-api/reference/instagram-media) endpoint returns all +The [media](https://developers.facebook.com/docs/instagram-platform/instagram-graph-api/reference/ig-media) endpoint returns all media objects created by an Instagram account. Each media object contains fields such as `caption`, `comments_count`, `created_time` and `like_count`. The fields parameter in such case is `caption,comments_count,created_time,like_count`. diff --git a/src/content/docs/components/extractors/social/youtube-reporting/index.md b/src/content/docs/components/extractors/social/youtube-reporting/index.md index aa75158aa..91d6d59c7 100644 --- a/src/content/docs/components/extractors/social/youtube-reporting/index.md +++ b/src/content/docs/components/extractors/social/youtube-reporting/index.md @@ -95,7 +95,7 @@ the [YouTube Reporting API documentation](https://developers.google.com/youtube/ ## Functionality Notes - The component uses the [YouTube Reporting API](https://developers.google.com/youtube/reporting/v1/reports/) to - create and run reports that measure the results of YouTube advertising campaigns. + create and run reports that give insights into the performance of your YouTube content. - All reports are downloaded incrementally and "upserted" into the destination table. - **IMPORTANT:** The reporting service creates standardised reports every 24 hours. Each report type has one job associated with it. Multiple report versions may be associated with a single job. Each report covers data for one 24-hour period. More than one report may be