Question 1

How is this different from the Salesforce (Sales Cloud) connector?

Accepted Answer

Sales Cloud is for CRM data — accounts, opportunities, contacts. Marketing Cloud is a separate Salesforce product for email marketing, journeys, and audience management. They have different APIs, different auth, and different data models. Many orgs use both, and Ana can query each independently or join them.

Question 2

Can Ana send emails or trigger journeys?

Accepted Answer

By default the connector is read-only. Admins can grant write scopes during installed package setup if you want Ana to start journeys, update audience members, or send transactional emails. Most teams start read-only and expand write access deliberately.

Question 3

Does this work with multi-tenant accounts?

Accepted Answer

Yes. The installed package can be scoped to specific business units within a Marketing Cloud parent account. You can set up multiple TextQL connectors, one per business unit, to keep data isolated for different teams or brands.

Question 4

How are audience segments returned?

Accepted Answer

Ana can query data extensions, audience filters, and journey audience snapshots. For very large audiences, Ana paginates and aggregates server-side rather than streaming millions of rows. You can also export to a warehouse table for deeper analysis.

Question 5

How is OAuth secured?

Accepted Answer

Server-to-server OAuth tokens are encrypted at rest in TextQL's credential vault and refreshed automatically. Ana's Python sandbox sees only sanitized helpers — never the raw client secret or access token.