Integrations

Connect the sources your analysis needs.

Integrations bring the data needed to check your brand’s visibility into the workspace. Start with the searches and answers you want to observe, then check which connections are available for your account.

AI Reputation ManagerWorkflow

Your brand · plans and responsibilities

PlanEvidenceVerification

From evidence to review

  1. To review

    Check the cited source

    Compare the cited information with current documentation.

    Product
  2. Draft

    Clarify compatibility

    Prepare an update with references and reasons for the changes.

    Marketing
  3. Awaiting approval

    Define the follow-up check

    Agree on a period and sample for reviewing answers after the action.

    Brand owner

A saved proposal remains distinct from an action carried out. Approval applies to the version reviewed and the owner’s permissions.

What you get

Connectors with clear responsibilities.

Tracking a question on Google requires a search-results source. Analysing an AI answer requires an enabled model or collection service. Each connection retains source, date and market so you can distinguish results across channels.

Reading path
  1. Source format
  2. Normalised fields
  3. Preserved context

What you get

Availability you can verify.

Before enabling a connection, check coverage, permissions and expected usage. A configured integration does not grant access to all provider content: the workspace uses only capabilities enabled for your project.

What makes an integration usable
VerificationPractical questionEvidence required
Access and coverageDoes the plan cover these channels, markets and periods?Actual API access and a documented provider scope.
Usage rightsWhich information may we store, display and process?Permissions and expiry dates for each intended use, including AI and export.
Operational testingHave collection, errors, costs and revocation been tested?Tests against the real service and controls that distinguish unavailability from an absence of results.

Guided connections

Your tools. Your context.

Connect a Google property to view your website’s data alongside its observed presence. Search Console shows impressions, clicks, CTR and average position; Analytics shows sessions, users and engaged sessions for the selected period.

When the connection is enabled, authorize your Google account and choose the brand’s property. Read the daily values and the latest retrieval date. If a source is not active, its report remains unavailable; you can still consult the other analyses already in the workspace.

Choose the source

Choose the data to read: organic results, website clicks, sessions or brand mentions.

Authorise the property

Select the correct account and check the permissions the service requires.

Check the scope

Confirm the property, market and available data before using the analysis.

Capabilities and permissions

Connected does not mean unlimited.

An account may allow reports to be read without authorising content changes. A contract may permit analysis of a source without granting the right to republish its text.

The integration model distinguishes the service’s capabilities, the account’s access and the requested operation. All three checks must align before proceeding. Read-only access is preferred for website data; any external action requires specific permissions. Read access never automatically enables publication, messages or spending.

Three checks before an operation
LevelWhat it establishesIllustrative example
ServiceWhich capabilities are implemented and tested.Report collection may be supported without a publishing connector.
AccountWhich data and properties are authorised.Access to one Analytics property does not grant access to the others.
OperationWhich action is permitted in the current context.Reading a report does not authorise a campaign or a charge.

Sources and uses

The right connection for each capability.

Organic search requires results tied to a query, market and device. AI answers require questions, a model and a collection method. Press, social media and forums add content with specific coverage and rights: each source addresses a different part of the question.

The Google connections provided in the workspace cover Analytics, Search Console and Google Ads reports. Bing searches are part of organic result collection. Press, social media and forums require a contracted and activated source; no content is collected from these channels before activation.

Distinct perspectives
  1. SERPs: results by query
  2. AI: answers by question
  3. Properties: authorised data

Related paths

Check your brand’s presence, compare results or choose content improvements: continue with the feature you need.

From question to action

From the question to checking the outcome: context, sources, hypotheses and action plans in the TrustInsider analytical workflow.

Read

Find the right answer

Find guides, FAQs and methodology to clarify indicators, coverage and access, with dedicated routes for data requests.

Read
Connect your existing tools · trustinsider