What this article shows you
Use a connected account as a live source, then turn what StefanBrain finds into a decision or finished deliverable. You normally do not need to choose a tool. Name the result, the connected source, the scope, and what StefanBrain should produce. The goal is not more analysis. It is a clearer decision, a stronger next step, or a handoff your team can use.Practical use cases
Find objections worth addressing
Group repeated concerns from reviews or support conversations so you can
decide what to answer in ads, landing pages, and customer education.
Find where performance needs attention
Compare two periods and surface the campaigns, pages, or products most
likely to explain the change, so your team knows where to investigate first.
Prioritize landing pages for review
Pair analytics with page context to find high-traffic pages where a mismatch
may be limiting conversion, then focus CRO work on the strongest candidates.
Choose evidence-backed creative tests
Combine customer language, performance evidence, and an approved brand
document into hypotheses so the creative team starts from observed patterns
instead of assumptions.
Create an actionable handoff
Turn the latest approved brief into a checklist, meeting brief, or client
handoff so the next person knows what to do and which source supports it.
Prepare a focused weekly review
Compare recent performance with the prior period and create a concise brief
of the changes, questions, and decisions the team should discuss.
Watch the walkthrough
Members with access to an enabled connector can use its data in Chat. To run
a request on a schedule, like the weekly review near the end of the
walkthrough, open Schedule in the sidebar.
See how connected company data can support research, analysis, briefs, and better decisions. Duration: 7:22.
How connectors fit into a workflow
A connector supplies current data or an external action. It does not replace the other context that makes the result useful.A repeatable connector workflow
1
Choose the evidence and the deliverable
Start with one decision or output. Name the connected source and the part of
that source StefanBrain should inspect.A strong request usually includes a date range, product, campaign, account,
document, or other useful boundary.
2
Confirm the intended account in Chat
Open a Chat, open Connectors, and confirm the intended account is on.If you have personal and company accounts for the same provider, name the
company and account in your request. This prevents a useful answer from
being built from the wrong source.
3
Run a read-only evidence pass
Ask StefanBrain to retrieve and organize the evidence before asking it to
change anything.Replace the provider, account, product, and requested evidence with the
source you actually use.
4
Check the evidence before the recommendation
Confirm the response names the source, time period, filters, and records or
entities behind its conclusion.If something is missing, narrow the follow-up instead of asking for a full
restart.
5
Turn the finding into finished work
Once the evidence checks out, ask for the next useful result.The follow-up inherits the established Chat context, so it should say what
to keep, what to change, and what result comes next.
Practical prompt patterns
Find where paid performance needs attention
Use this to separate a broad account change from a campaign-level issue and decide what the media buyer should inspect first.Find which landing pages are worth reviewing first
Use this to focus CRO effort on high-traffic pages where the conversion gap may create the strongest opportunity to learn.Give the creative team a usable test plan
Use this to turn approved strategy and current evidence into one brief the creative team can act on without rebuilding the context.Prepare for the weekly media review
Use this to surface the important changes before the meeting, so the team can spend its time deciding what to investigate or change.Team and permission boundaries
Every member can schedule requests. Open Schedule in the sidebar to run a connector request you use often on a set day and time. Team access shares the connected provider account as a whole. It does not create folder-level, property-level, or resource-level limits inside that account. The connection owner controls team access and the Team tool-permission profile. For Meta, shared read and analysis access is separate from publishing. Can publish ads starts off for each teammate and must be enabled by the connection owner. Use a narrower provider account when the full connected account contains more than the team should access.Common mistakes and troubleshooting
The answer used the wrong account
The answer used the wrong account
Confirm the intended account is on under Connectors, then name the
provider, company, and account in the next request.
The answer is broad but not useful
The answer is broad but not useful
Add a date range, entity, comparison, deliverable, and decision. Ask for the
evidence behind each conclusion.
A write action asks for approval
A write action asks for approval
Read the proposed action and target. Choose Approve once only when the
change is intended, or ask the connection owner to adjust the permission.
Do not approve a broader action to unblock a read-only job.
The connection needs attention
The connection needs attention
Open Connectors and check the account. Only the connection owner can
reconnect a shared account.
The request tries to analyze too much at once
The request tries to analyze too much at once
Start with one period, product, campaign group, property, folder, or review
slice. Expand only after the first evidence set is complete.