Google Data Manager MCP for full first-party data activation

Google Data Manager MCP connects Google's first-party data activation API to Claude, ChatGPT, Cursor, and other compatible AI clients through Markifact. It can prepare and send conversion events or audience membership updates and check how each request was processed.

Yes. Four tools write conversion, event, or audience data, while the request-status tool reads processing results. Every write can be validated first and waits for approval before Markifact sends it.

The current tools are data_manager_upload_offline_conversions, data_manager_ingest_events, data_manager_ingest_audience_members, data_manager_remove_audience_members, and data_manager_get_request_status.

Yes. Upload one conversion or bulk rows from a workflow data source. Supply the Google Ads account and conversion action, then include conversion time plus a GCLID, email, or phone for matching.

Yes. Use bulk mode with rows from a previous Google Sheets step. Supported values include account IDs, conversion action, GCLID, email, phone, event time, conversion value, currency, order ID, and event source.

Event ingestion supports Google Ads conversion actions, Campaign Manager 360 or DV360 Floodlight activities, and Google Analytics measurement IDs or Firebase app IDs.

Yes. Define several destinations in one request and either send every event to all of them or use destination references to route specific events to specific products.

Events can include timestamps, source, transaction ID, GCLID, GBRAID, WBRAID, DCLID, enhanced-conversion user data, value, currency, conversion count, consent, cart items, custom variables, event name, user properties, device or location data, and supported analytics identifiers.

Yes. Add members to Google Ads Customer Match lists, DV360 advertiser or partner audiences, Google Ad Manager audience links, and supported data-partner destinations.

Yes. Remove members using the same identifier type that was originally ingested. This supports suppression lists, consent withdrawals, churn handling, and lifecycle audience updates.

Raw emails and E.164 phone numbers are normalized and SHA-256 hashed before sending. Supported names and address fields used in user-data matching are normalized and hashed too. Pre-hashed HEX or BASE64 identifiers can also be supplied.

Yes. Set ad-user-data and ad-personalization consent at request level, or provide consent on individual events or members where supported. Customer Match uploads also require confirmation that the advertiser accepts Google's Customer Match terms.

Yes. Conversion, event, audience-add, and audience-remove tools support validation-only mode. Google checks the request and returns errors without ingesting or removing records.

Markifact automatically batches large payloads. Google accepts up to 2,000 events per event-ingestion request and up to 10,000 audience members per audience request.

Each ingest or removal response can return a request ID. Use data_manager_get_request_status to retrieve per-destination processing states plus warning and error counts and their reasons.

Yes in the MCP workflow. Markifact shows the destination, record counts, consent, and proposed operation before execution, then waits for your approval. Validation-only runs help surface problems before that approval.

No. Google Data Manager and its API are Google products. Markifact is a third-party hosted MCP server that exposes authorized Data Manager operations inside compatible AI clients and marketing workflows.

No custom API client or hosted MCP server is required. Connect Google Data Manager to Markifact with OAuth, add Markifact to your AI client, and use the five available tools.

Any compatible remote MCP client can use Markifact's hosted server, including Claude, ChatGPT, Cursor, VS Code, and other clients that support authenticated MCP connections.