Included Data or Connected Provider? Read GTM Integration Claims Before Building a Stack

An integration listing does not, by itself, mean the provider's data is included in your GTM platform subscription. It may describe included data access, a connector that uses your existing provider account, or a route for sending your own data into the platform. Establish which arrangement applies to the specific workflow before budgeting the stack.

The distinction matters even when the same vendor appears in more than one place. A platform can include a defined data capability powered by a provider while also supporting a separate connection to your own subscription. Neither arrangement automatically gives you the provider's full standalone product, every dataset, or unlimited usage.

What can an integration logo mean?

A logo tells you there is some relationship or supported capability. The surrounding setup instructions explain what the buyer receives and what the buyer must supply. Read the data description, connection requirements, and commercial terms together.

Included does not necessarily mean free, unlimited, or usable outside the platform. Connected does not necessarily mean an extra subscription is required: your company may already hold the needed entitlement. The task is to identify the commercial and operational dependency, then check whether your organization already satisfies it.

What do Unify's actual source cards say?

The Unify use-case library distinguishes sources marked Included with Unify from those marked Your connection or You connect. The three inspected workflows below show why those labels should be read at the workflow level.

These are documentation examples, not results from a customer deployment. Their sample accounts and numbers are labeled illustrative on the source pages; they are not evidence of enrichment accuracy, conversion, or return on investment.

The practical reading is narrow. The research-only workflow documents an included research path. The category-research workflow combines included intent with optional customer-supplied context. The product-usage workflow supplies contact data but depends on the customer's product events and CRM. A source card is not a promise that every listed tool must be purchased, or that every possible use of that provider is bundled.

Do not infer that connecting all the logos is a prerequisite. Read the selected workflow's setup and confirm which connections are required, optional, or alternative routes for your intended implementation.

Can the same provider be both included and connected?

Yes. Unify's 6sense integration guide describes both out-of-the-box visitor identification powered by 6sense and other providers, and a connection using an existing 6sense subscription. The customer-owned path uses an API key; the guide notes that API access may need enabling.

That distinction prevents two budgeting mistakes: buying a separate account for a capability already covered by your platform agreement, or assuming the platform includes all the functionality of a provider whose logo appears in its catalog. Confirm the exact capability, not just the provider name.

G2 provides a clear example of customer-owned access. The G2 integration guide says to connect an existing subscription using an API token. The connector is the access route; it is not a statement that a G2 subscription is supplied.

For product events, the dependency is different again. The PostHog guide requires a project already collecting events and permission to configure destinations. It describes forwarding selected events and mapping person and company attributes. An integration cannot supply historical events your product never collected, and a missing identity field cannot become reliable account context simply because the connection succeeds.

Which costs and permissions remain separate?

Build the budget around the complete workflow rather than a count of connected logos. Use the following as a proposed purchasing checklist; the answers depend on your plan and agreement.

• Platform entitlement: the feature, dataset, or workflow enabled for your workspace, including any limits.
• Provider entitlement: any external subscription and the API or data package required for the customer-owned connection.
• Usage: enrichment credits, API calls, processed events, exports, or other billable units named in the relevant agreement.
• Permissions: who can authorize the account and whether the credential can read the required data or write the intended updates.
• Operating work: mapping, testing, monitoring, credential maintenance, and ownership when a connection stops working.

A successful login answers only part of the permissions question. Confirm that the authorized account can access the particular data needed by the workflow. Likewise, an included source does not establish how much usage remains in your workspace. Obtain the plan-specific answer before committing to a production volume.

Keep data rights separate from connectivity. Ask where results may be stored, who may access them, and what retention or export restrictions apply under your agreements. A working sync does not expand the rights granted by a source contract.

How should a buyer record the distinction?

Create one record per capability and workflow, rather than one row per vendor. That lets a provider appear under an included capability and a separate customer-owned connection without a contradiction. Use the blank template below when reviewing an actual workflow.

Keep credentials themselves out of the record; store only their owner and the approved reference to your credential system. Separate a documented capability from a test result. A source card can support the first; a controlled run in your configured workspace is needed for the second.

What should you verify before building the stack?

Choose one real workflow and define the minimum output that makes it useful. Trace every required field back to its source. Mark unresolved entitlements explicitly, then ask the vendor to confirm them against your proposed plan.

Next, run a controlled test with records you are authorized to use. Check whether the required fields arrive, which source supplied them, whether account matching works, and whether the measured usage agrees with the billing model. Test a missing permission or unavailable source as well: the workflow should expose missing evidence rather than treating it as a negative buying signal.

For CRM-dependent outreach, verify exclusions and ownership before allowing enrollment. The guide to HubSpot sync tools for outbound covers the separate question of how CRM behavior affects execution. Entitlement establishes access; configuration determines how the workflow uses that access.

Start with the Unify workflow closest to your team's goal, inspect its included and connected sources, and bring the remaining plan-specific questions to your evaluation. That gives you a concrete stack decision with dependencies you can explain and test.

Frequently asked questions

Does a native integration include the provider's data subscription?

Not necessarily. Native describes the connection experience. Read the entitlement and setup instructions to establish whether the platform supplies the data or uses your existing account.

Does included data mean unlimited usage?

No. Included access can still have plan limits or consumption charges. Confirm the dataset, billable unit, allowance, and restrictions in your agreement.

Why would one provider appear under both included and connected sources?

The platform may supply a defined capability powered by that provider while also supporting your own subscription for a separate access path. Evaluate each capability independently.

Do I need every tool shown on a workflow card?

Do not assume so. Check the workflow's setup instructions and confirm which connections are required, optional, or alternatives for the data you intend to use.