Google Ads Product Links: Check What Is Actually Connected

A linked account is not a running import

An agency opens Data Manager and sees the expected product name. Later, a client says the campaign has stopped receiving qualified leads. Both observations can be true. The account relationship may still exist while a particular file, connection or conversion destination has stopped working.

Google's Data Manager and Product Linking page brings connected products, pending requests and tag management into one place. That shared interface is useful, but it does not make every item the same kind of connection.

A Merchant Center relationship, an Analytics property link and a scheduled customer-data import do different jobs. Do not apply a CRM sync checklist to every product link, or assume that disconnecting a product is the only way to stop one import.

Ask what the connection is doing

Begin with a plain question: “What would stop if we removed this?” Trace an actual dependency rather than assigning a vague importance label to the whole platform.

Suppose a retailer uses one CRM source for a past-buyer audience and a separate qualified-lead conversion action. The buyer audience may still update while the lead import fails because its selected table changed. Reauthorizing the entire source could be unnecessary; deleting it would broaden the incident.

The useful handoff is specific: which account is connected, which data is selected, where it is used, and who can repair that particular setup. You do not need a standing weekly meeting for an otherwise stable connection. You do need enough context that the next person does not mistake a forgotten connection name for an unused business dependency.

Use the connection details before rebuilding anything

Google's connection management guide describes usage details, run history, schedules, mapping and credentials. Inspect the failed connection at that level. A successful run from last month does not prove this morning's data arrived.

Stopping a schedule, removing a usage, deleting a connection and disconnecting a source have different scopes. Google's documentation explicitly distinguishes these operations. Choose the one that matches the intended change; avoid deleting a shared source just to retire one audience.

For an access problem, establish whether the source still exists and whether the authorized credentials can read it. Google's connection diagnostics separates rejected credentials, missing sources and incompatible data. An expired credential and a renamed column call for different repairs.

Keep the handoff observable. If a client is taking ownership of a connection, verify the intended next run and destination with the new arrangement. Merely adding someone's email to a project document does not establish that they can access the source.

A broken link is not an automatic campaign pause

Imagine that an imported lead outcome is delayed while website purchases continue to arrive. Whether a campaign is affected depends on its actual goals and bidding configuration. The product name beside the connection does not establish that dependency.

First separate a delivery delay from a change in the customer's business. If the source has a backlog, find its extent and the supported recovery behavior before replaying data. If the source is healthy but the wrong event is selected for a campaign, reauthorizing the link will not fix the goal.

Likewise, an unfamiliar link deserves investigation, not immediate removal. It may support a report maintained by another team or an audience whose name has changed. Once its purpose is understood, retiring it can be straightforward. The reason should be that the connection is no longer needed—not that an old owner field is blank.

If a real outage is materially affecting bidding, assess a targeted response for the affected campaigns. A universal “pause everything until the roster is complete” rule would replace one poorly understood change with another.