Merge branch 'main' into facebook_conversions_api

Author: elenaperezrioja

code_blocks/getting-started/installation/android_1.groovy

@@ -1 +1 @@
-implementation 'com.revenuecat.purchases:purchases:7.0.0'
+implementation 'com.revenuecat.purchases:purchases:8.14.0'

code_blocks/getting-started/installation/android_3.groovy

@@ -1,2 +1,2 @@
-implementation 'com.revenuecat.purchases:purchases:7.0.0'
-implementation 'com.revenuecat.purchases:purchases-store-amazon:7.0.0'
+implementation 'com.revenuecat.purchases:purchases:8.14.0'
+implementation 'com.revenuecat.purchases:purchases-store-amazon:8.14.0'

docs/integrations/third-party-integrations/discord.mdx

@@ -35,13 +35,13 @@ You need to configure your Discord server to authorize a webhook to post to your
 
 Once you've set up a webhook in your Discord server. Enter the details into the Discord Integration section of your [dashboard](https://app.revenuecat.com).
 
-![](https://github.com/RevenueCat/revenuecat-docs/assets/287089/7764e4de-b9ea-4060-9a59-af0c959bebb0 "Discord integration setup")
+![](/images/7764e4de-discord-integration-setup-af0c959bebb0.png "Discord integration setup")
 
 :::success
 You're all set! RevenueCat will start sending events into Discord!
 :::
 
-![](https://github.com/RevenueCat/revenuecat-docs/assets/287089/07cde5bd-e440-47d0-a219-aceaac4fd516 "Discord message example")
+![](/images/07cde5bd-discord-message-example-aceaac4fd516.png "Discord message example")
 
 ## Sample Events
 

docs/integrations/third-party-integrations/intercom.mdx

@@ -55,6 +55,10 @@ The Intercom integration tracks the following events:
 
 ![](/images/25cc36c-Screen_Shot_2019-01-25_at_1.46.51_PM_b8eb5641f04c97f97d7b550e3f612af0.png "Screen Shot 2019-01-25 at 1.46.51 PM.png")
 
+4. Click **Authorize access**. If you have multiple workspaces, click the workspace name and choose the workspace you want to connect this RevenueCat project to. Also ensure the correct data host region is selected.
+
+![](/images/intercom_authorization_screen.png)
+
 ### 2. Set Event Names
 
 Once your account is connected, you can configure the event names that we'll send to Intercom. If you leave any field blank, we'll just use our default names.

docs/integrations/webhooks.md

@@ -32,7 +32,7 @@ With webhooks integrated, you can:
 7. Select if the webhook events should be sent only for one app or for all apps of the project
 8. (Optional) Filter the kinds of events that should be sent to the webhook URL.
 
-![](https://github.com/RevenueCat/revenuecat-docs/assets/14286938/6a07a8cf-0696-4a2f-8546-7d9cd735e95d)
+![](/images/6a07a8cf-webhook-integration-7d9cd735e95d.png)
 
 :::info Best Practices: Webhook authorization
 We recommended setting an authorization header value via the RevenueCat dashboard. When set, RevenueCat will send this header in every request. Your server can use this to authenticate the webhooks from RevenueCat.
@@ -54,7 +54,7 @@ For webhook event types and fields, see [here](/integrations/webhooks/event-type
 
 You can test your server side implementation by purchasing [sandbox subscriptions](/test-and-launch/sandbox) or by issuing test webhook events through [RevenueCat's dashboard](http://app.revenuecat.com).
 
-![](https://github.com/RevenueCat/revenuecat-docs/assets/14286938/ad2c8e64-12ba-4ee1-9bf0-c841349f3b7e)
+![](/images/ad2c8e64-webhook-testing-c841349f3b7e.png)
 
 When testing with sandbox purchases, the `environment` value will be `SANDBOX`. RevenueCat itself does not have sandbox and production environments, so this value is only determined by the type of transaction received from the store. The same customer in RevenueCat can have both sandbox and production transactions associated with their account.
 

docs/integrations/webhooks/event-flows.md

@@ -97,7 +97,7 @@ Immediate changes occur:
 - On the Google Play Store, for all proration modes except `DEFERRED` (ie. all proration modes starting with `IMMEDIATE`)
 - For immediate product changes in Stripe. Please note: The `RENEWAL` event may show the same `purchased_at_ms` as the original subscription (ie. t₀), because that is how Stripe represents the status of the subscription after the product change.
 
-![immediate product change flow](https://github.com/RevenueCat/revenuecat-docs/assets/14286938/461fc856-60c5-4a9b-b568-22ef7295e212)
+![immediate product change flow](/images/461fc856-immediate-product-change_22ef7295e212.png)
 
 ### Product Change at Period End
 
@@ -110,7 +110,7 @@ Changes at period end occur:
 - On the Google Play Store, for the proration mode `DEFERRED`
 - For scheduled product changes in Stripe
 
-![product change at end of period flow](https://github.com/RevenueCat/revenuecat-docs/assets/14286938/6441cc2b-aef9-4c45-8477-e5154829756a)
+![product change at end of period flow](/images/6441cc2b-product-change-at-end-of-period-e5154829756a.png)
 
 ## Other
 

docs/service-credentials/creating-play-service-credentials.mdx

@@ -32,7 +32,7 @@ To enable the Developer and Reporting APIs for your Google Cloud Project, you’
 3. Go to the [Google Play Android Developer API page](https://console.cloud.google.com/apis/library/androidpublisher.googleapis.com) and the [Google Play Developer Reporting API page](https://console.cloud.google.com/apis/library/playdeveloperreporting.googleapis.com) in Google Cloud Console.
 4. Click **Enable**. (This will say **Manage** when it is enabled.)
 
-![steponeGIFv2](https://github.com/RevenueCat/revenuecat-docs/assets/112121235/97660d3a-b963-4b1e-8be0-d5bc28080b33)
+![steponeGIFv2](/images/97660d3a-create-play-service-credentials-step-1.gif)
 
 After enabling the API, you will be redirected to your Google Cloud API page. From there, if you do not have credentials, you will need to create these following the prompt. You'll want to select that you are using the Google Play Android Developer API. Note that you'll want to generate these with either the owner of the project or a user that has the permissions from step 3 enabled in Google Play Console.
 
@@ -94,7 +94,7 @@ All other choices are yours - the other boxes can be checked or unchecked accord
 
 Select invite user at the bottom of the page, and send the invite. You'll then be redirected to '**Users and Permissions**', where you should see your newly created account as active.
 
-![stepthreeGIF](https://github.com/RevenueCat/revenuecat-docs/assets/112121235/1bebe299-60db-4001-9329-0250324edb12)
+![stepthreeGIF](/images/1bebe299-create-play-service-credentials-step-3.gif)
 
 ### 4. Enter the Credentials JSON in RevenueCat
 

docs/test-and-launch/debugging.mdx

@@ -99,7 +99,7 @@ Note: The debug UI won't compile for release builds, so you'll need to disable t
 
 ### Android
 
-![RevenueCat Android Debug UI](https://github.com/RevenueCat/revenuecat-docs/assets/808417/108f3d64-96d1-4bd7-b926-70c6676931be)
+![RevenueCat Android Debug UI](/images/108f3d64-revenuecat-android-debug-ui-96d1-4bd7-b926-70c6676931be.png)
 
 In order to use the overlay, you need to include the debug view library which is available on Maven and can be included via Gradle. Currently, this is only available as a Jetpack Compose Composable.
 

docs/tools/customer-center/customer-center-flutter.mdx

@@ -5,9 +5,6 @@ slug: customer-center-flutter
 hidden: false
 ---
 import { sdkVersions } from '@site/src/components/CustomerCenter/CustomerCenterSDKTable';
-import OverviewPartial from './_customer-center-installation-overview.mdx';
-
-<OverviewPartial />
 
 ## Installation
 

docs/tools/customer-center/customer-center-integration-android.mdx

@@ -6,13 +6,6 @@ hidden: false
 ---
 import { sdkVersions } from '@site/src/components/CustomerCenter/CustomerCenterSDKTable';
 
-import YouTubeEmbed from '@site/src/components/YouTubeEmbed';
-import OverviewPartial from './_customer-center-installation-overview.mdx';
-
-<YouTubeEmbed videoId="yraB5gQCUPE" title="Integrating the Customer Center" />
-
-<OverviewPartial />
-
 ## Installation
 
 [![Release](https://img.shields.io/github/release/RevenueCat/purchases-android.svg?style=flat)](https://github.com/RevenueCat/purchases-android/releases)