# Integrations Connect Search Console and GA4, alerts, publish destinations, trackers, document tools, warehouses and single sign-on. Source: https://praised.co/docs/integrations Updated: 2026-10-14 Integrations connect Praised to Google data, an alerts channel, publishing tools, a team tracker, document tools and a sign-in provider. Google data is set up in Data sources; the rest is in Settings. ## Integrations by plan | Integration | Where | Plans | | --- | --- | --- | | Search Console and Google Analytics 4 | Data sources | Every plan | | Trackers: Linear, Jira, Asana, GitHub | Settings › Delivery › Trackers | Pro, Scale, Agency, Enterprise | | Document tools: Notion, Google Docs | Settings › Delivery › Document tools | Pro, Scale, Agency, Enterprise | | Single sign-on: OIDC, SAML, SCIM | Settings › Access › Single sign-on | Pro, Scale, Agency, Enterprise | | Personal API keys and connected apps | Settings › Access | Pro, Scale, Agency, Enterprise | | Warehouses: BigQuery, Snowflake, Amazon S3 | Settings › Delivery › Warehouses | Enterprise | Only an Owner connects, changes or removes an integration. Other members read the same rows, with the controls marked Owners only. [Plans, prices and limits](pricing) ## Search Console and Google Analytics 4 Choose Data sources in the rail, under Set up. The Google card lists Search Console and Google Analytics 4. Other members read a note that an Owner connects these. Where the card offers Connect with Google, Search Console connects by signing in with Google: read-only, and only Search Console. Then pick the property and choose Use property. The other way, for both sources, is a service-account key. Enter the property, then paste the key as JSON and choose Connect. For Search Console, the property looks like sc-domain:yourcompany.com, or https://yourcompany.com/ for a URL-prefix property. For GA4, the property is the numeric Property ID under Admin › Property details. Give the service account access first: Restricted access under Settings › Users and permissions in Search Console, or Viewer on the GA4 property. The key is encrypted at rest and never shown again. ### After connecting After connecting, Praised pulls the last 28 days, then syncs every connected workspace once a day. Sync now pulls the data again on demand. Google’s own data arrives one to two days late, and each sync replaces the recent window to pick up late rows. Visits from AI tools like ChatGPT are read from referrers. Visits without a referrer cannot be identified, which makes the figure a lower bound. Choosing a different property sets the old property’s rows aside, kept. Choosing the old property again brings them back. Disconnect stops the daily sync and forgets the key. Data already synced stays in the workspace. ### AI crawler logs Data sources also lists the access-log feeds that report AI crawler visits, each with whether the feed is receiving. Set one up starts the WordPress plugin or the copy-paste worker; Test connection checks a feed. ## Alerts Settings › Delivery › Alerts sends alerts to an email address, or to everyone in the workspace when the address is blank, and to a Slack or webhook URL. A saved webhook URL is never shown again; the field stays blank unless you are replacing the URL. ## Publish destinations Settings › Delivery › Publish destinations lists where a finished piece is sent. Configure or Connect sets one up; Disconnect removes one. | Destination | What happens | | --- | --- | | GitHub pull request | Opens a pull request on the site’s repository. Its own review and checks decide what merges | | WordPress | Pushes the pages to the WordPress site as drafts, published in WordPress’s own editor | | Sanity | Creates the pages as draft documents in the Sanity dataset | | Contentful | Creates the pages as unpublished entries in the Contentful space | | Webhook | Posts the piece to an address, signed for the receiver to verify | | Download | A file to open, send on or paste in by hand | A destination’s credential goes to the server once, is stored encrypted, and never comes back. The row lists recent sends. ## Trackers, document tools and warehouses Trackers receive work items, sent from a work item’s drawer. Document tools receive scheduled reports, delivered as pages. Warehouses receive each day’s readings as rows in the customer’s own BigQuery, Snowflake or Amazon S3. ## Single sign-on Settings › Access › Single sign-on sets up OIDC or SAML for an email domain. Configure one of the two for a domain, not both. Each domain needs proof first: a member with a confirmed address at that domain. Invite someone at the domain, have them confirm their email, then claim the domain. A domain already claimed by another workspace is refused. Once a domain is claimed, people who sign in with an address at that domain are sent to the identity provider. The same row creates a SCIM token for the identity provider. The token is shown once, and a new token stops the previous one at once. [Team members and roles](team) ## API keys and AI tools Personal API keys and Connected apps link Claude, ChatGPT, Cursor and other AI tools to the workspace. [MCP server](mcp) [Export and share](export-share) ## Agency client workspaces In an agency’s client workspace, the outbound connections are set up by the agency. [Agency guide: client workspaces and reports](agency) ## When something goes wrong When a sync fails, the source shows “Last sync failed” with Google’s reason. Fix the access in Google, then choose Sync now. When the connection status cannot be read, the screen says the status could not be checked. A failed read never shows a source as disconnected. A refusal that names the plan means the integration is not on the current plan. Compare plans from Billing & plan.