Ingest Labs

Analyze marketing data in chat

Category: Marketing
Primary Subcategory: Marketing & Commerce Data Integration

Integration details

Description

Ingest Labs connects ChatGPT to your production Ingest Labs account over MCP so you can query marketing analytics and inspect Tag Manager configuration. Sign in with the same portal account used on console.ingestlabs.com. After choosing an organization, use Insights tools for Attribution, Ad spend and ROAS, user events, Traffic Quality insights, and Tag Manager tools to list or change providers, tags, and data elements.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Marketing
Primary Subcategory: Marketing & Commerce Data Integration
Secondary Subcategories: None listed
Brand: Ingest Labs
Access: Account required
First tracked: 2026-09-04
Tool count: 26
Geography: US

ChatGPT Plugin Discovery Score

ChatGPT Plugin discovery is coming soon

ChatGPT can surface a Plugin when it matches a user's request.Your Plugin Discovery Score measures how often yours appears.

No spam. Unsubscribe any time.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competing in ChatGPT Marketing & Commerce Data Integration

View Category

Listed in alphabetical order

Primary Subcategory

AdzviserComing soonGet notified

CatchrComing soonGet notified

Coupler.ioComing soonGet notified

DataslayerComing soonGet notified

FaradayComing soonGet notified

Ingest LabsComing soonGet notified

Tools

26 tools agents can invoke

Create a new data element in a project. Data elements define how data is captured from the page/server for use in tags.
Create a new provider (integration/extension) in a project. The intended flow is to GET an existing provider from a template/reference project, adapt the resource_params (e.g. remap data_element ids to the destination project), and POST the adapted definition here.
Create a new qualification criteria. The intended flow is to GET a QC from a reference project and POST the adapted definition (remapping any DE refs in qualification_criteria attributes to destination-project IDs).
Create a new tag under a provider. Tags define tracking/measurement configurations with resource parameter mappings.
Delete a data element from a project.
Run an Insights query against IDL dashboard data. Requires confirmed vendor_id (list_vendors if org unknown — never invent) and context_id plus at least one dimension or metric id from get_insights_schema. Provide interval_suffix (m|h|d|w) when selecting a dimension with dim_typ dt. Filters are dimension-only. Provide date_preset (uses vendor timezone) OR both from/to epoch seconds — not both. media_tags requires project_id (list_projects if project unknown). Always pass user_question with the user's original wording and query_intent explaining this query's role in answering it.
Get full details of a single data element by ID, including type-specific config (jsv.fn for JSV, mp_data_layer for MPDL, urlp for URLP, etc.). Use when list_data_elements does not surface enough detail (e.g. when copying a custom JSV DE).
Get dimensions, metrics, mandatory filters, and classifications for a context_id from list_insights_contexts. Requires confirmed vendor_id (list_vendors if org unknown). Use dimension and metric **ids** (not display names) in execute_insights_query. Do not invent field ids.
Get details of a specific project
Get details of a specific provider including its resource parameters and data element mappings
Get details of a specific provider template including its resource parameters schema
Get full details of a single qualification criteria by ID, including the qualification_criteria attribute list and record_trigger for EVENT-type QCs.
Get details of a specific tag by ID, including its parameter mappings and configuration
List all data elements in a project. Data elements are the data fields/variables that tags use for their parameter mappings. NOTE: this returns metadata only — for type-specific config (e.g. JSV script body, MPDL config), use get_data_element.
List available Insights query contexts (MCP catalog) for a product. Requires a confirmed vendor_id — if the organization was not specified or is ambiguous, call list_vendors first and confirm selection (never invent vendor_id). After scope is known: list_insights_contexts → get_insights_schema → execute_insights_query. Pick context_id from name/description/keywords (attribution, facebook ads, google ads, ga4, sessionized events, tqs, media tags, etc.).
List all projects for a vendor. Call when project is required (Tag Manager tools or product media_tags) but project is unspecified or ambiguous. Present project name + project_id and ask the user to choose if more than one matches. Requires a confirmed vendor_id from list_vendors or the user.
List all available provider templates for a project. Templates define the structure and parameters for integrations like Meta CAPI, GA4, etc.
List all providers (integrations/extensions) in a project
List all qualification criteria (QC) in a project. QCs define the conditions that fire tags (e.g. event-driven, page-match, custom).
List all tags in a project. Tags are the tracking/measurement configurations attached to providers.
List all vendors/organizations the authenticated user can access. Call before Insights or Tag Manager tools when organization is unspecified, ambiguous, or not yet confirmed in the session. Present name + vendor_id and ask the user to choose if more than one org matches; auto-pick only when there is exactly one vendor or the user already locked a vendor in this conversation. Never invent vendor_id.
Health check — returns pong with server timestamp
Report a problem noticed while using IngestLabs MCP tools (bugs, wrong data, confusing schemas, missing capability, performance). Call when a tool failed unexpectedly, returned incorrect/unusable results, or the API shape blocked completing the user’s task. Do not use for normal empty results or user mistakes. Requires confirmed vendor_id.
Update an existing data element. Sends a PATCH with the full data element definition.
Update an existing provider. First GET the provider, then POST the full provider definition back with changes. The API uses POST (not PATCH) for updates.
Update an existing tag. Sends a PATCH with the full tag definition.

Ingest Labs FAQ

How do I improve a ChatGPT Plugin's discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are Ingest Labs alternatives on ChatGPT?

As of 2026-09-04, Ingest Labs competes with Adzviser, Catchr, Coupler.io, Dataslayer, Faraday, Feedoptimise, Funnel, Improvado AI Agent, InsightfulPipe, Lytical, Master Metrics, Polar Analytics, Quanti IA, Windsor.ai in ChatGPT Marketing & Commerce Data Integration, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.