January 22, 2026

eBay + Google Sheets: seller metrics without digging

Lisa Granqvist Partner Workflow Automation Expert

Get a free AI assessment → ⬇️ Use template

Your weekly “seller health” check starts simple. Then you’re hunting for the right eBay report, clicking through menus, copying identifiers, and hoping you’re looking at the same evaluation cycle as last week.

Marketing leads trying to protect campaign performance feel it first. So do store owners managing account risk, and ops managers who just want a clean scoreboard. This eBay metrics automation puts the numbers in Google Sheets without the scavenger hunt.

Below is the workflow, what it fixes, and how you can use it to turn “metrics day” into a quick glance instead of a half-hour ritual.

How This Automation Works

See how this solves the problem:

n8n Workflow Template: eBay + Google Sheets: seller metrics without digging

Click to explore

flowchart LR

    subgraph sg0["MCP Metrics Gateway Flow"]
        direction LR
        n0@{ icon: "mdi:play-circle", form: "rounded", label: "MCP Metrics Gateway", pos: "b", h: 48 }
        n1@{ icon: "mdi:web", form: "rounded", label: "Fetch Service Metrics", pos: "b", h: 48 }
        n2@{ icon: "mdi:web", form: "rounded", label: "Retrieve Standards List", pos: "b", h: 48 }
        n3@{ icon: "mdi:web", form: "rounded", label: "Fetch Standards Detail", pos: "b", h: 48 }
        n4@{ icon: "mdi:web", form: "rounded", label: "Get Listing Traffic Data", pos: "b", h: 48 }
        n3 -.-> n0
        n2 -.-> n0
        n4 -.-> n0
        n1 -.-> n0
    end

    %% Styling
    classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
    classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
    classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
    classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
    classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
    classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
    classDef disabled stroke-dasharray: 5 5,opacity: 0.5
    class n0 trigger
    class n1,n2,n3,n4 api

The Challenge: Seller metrics are scattered and time-sensitive

Seller service metrics are the kind of numbers you don’t notice until you really need them. A spike in “late shipment” or a dip in customer service score can quietly drag down visibility, limit selling privileges, or create extra support overhead. The painful part is the checking: you log into eBay, dig through the right area, pick the correct evaluation type, then repeat it again for the next view. Do this weekly and you’re burning attention on navigation instead of decisions. Honestly, it’s easy to miss trends when the data lives in a few different places.

The friction compounds. Here’s where it breaks down.

Teams end up checking metrics less often because it feels like “one more portal” to visit.
People copy numbers into spreadsheets by hand, which means typos and inconsistent week labels are almost guaranteed.
Evaluation cycles and program details get mixed up, so you compare the wrong periods and draw the wrong conclusions.
When leadership asks “what changed,” you waste time re-running lookups instead of showing a trend line.

The Fix: An eBay metrics gateway that your sheet can call

This workflow turns eBay’s Seller Service Metrics API into a simple “gateway” you can query consistently. It exposes four key operations (customer service metric, seller standards profile list, seller standards profile detail, and listing traffic report) through a single MCP server endpoint, then uses HTTP requests to pull the right data from https://api.ebay.com. The clever part is parameter handling: the workflow is built for AI agents (via $fromAI() placeholders), so values like evaluation type, metric type, program, and cycle can be supplied cleanly without you hand-mapping every field. Once the API response is returned, you can route it into reporting, alerts, or a Google Sheets update workflow so your weekly review is one place, one view.

The workflow starts when an AI agent (or another automation) calls the MCP endpoint. n8n then picks the right API operation, fetches the metrics from eBay, and returns the full data structure. From there, you use Google Sheets as the “single page” to review weekly movement and spot problems early.

What Changes: Before vs. After

What This Eliminates

Impact You’ll See

Manually hunting through eBay screens for the right metric view.
Copying IDs, program names, and evaluation cycles into notes to reuse later.
Re-checking the same standards profile just to confirm “nothing changed.”
Switching between multiple pages to compare service metrics and traffic signals.

Most teams get weekly checks down to about 5 minutes.
Cleaner trend tracking because each pull follows the same query pattern.
Fewer “false alarms” from comparing mismatched cycles or programs.
Faster escalation when something slips, since the data is already captured.
One reporting surface in Google Sheets that’s easy to share internally.

Real-World Impact

Say you do a weekly check across 4 views: customer service metric, standards profile list, a standards detail for your main program/cycle, and a listing traffic report. Manually, that’s often 10 minutes per view once you include navigation and double-checking context, so roughly 40 minutes every week. With this workflow running as a gateway, a sheet-driven pull can happen in a couple minutes (plus waiting for the API response), and you spend your time reviewing the trend line instead of “finding the page.” Over a month, that’s a couple hours back, and the data is more consistent.

Requirements

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
eBay Seller Service Metrics API for pulling seller standards and metrics.
Google Sheets to store weekly snapshots and trends.
eBay API credentials (get them from your eBay developer account/app keys).

Skill level: Intermediate. You’ll connect credentials and understand where your sheet should receive the results.

Need help implementing this? Talk to an automation expert (free 15-minute consultation).

The Workflow Flow

An AI tool (or another system) calls your MCP endpoint. The workflow is activated and provides a single URL you can use as the “front door” for seller metric requests.

The request is routed to the right operation. Based on what’s being asked for, n8n selects one of the four available API calls (customer service metric, seller standards list, seller standards detail, or listing traffic report).

eBay is queried with the right parameters. HTTP Request nodes call api.ebay.com, and values like metric type, evaluation type, program, and cycle are filled in automatically through AI-friendly placeholders.

The response is returned for reporting. You can pass the returned data into a Google Sheets update flow (often triggered by a weekly schedule or a Google Drive-based spreadsheet trigger) so the sheet becomes your weekly check-in.

You can easily modify the output mapping to write specific fields into your own sheet columns based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the MCP Trigger

This workflow starts when the MCP endpoint receives a request, which then exposes multiple HTTP tools for seller metrics retrieval.

Add the MCP Metrics Gateway node as the trigger.
Set the Path to -seller-service-metrics-api--mcp.
Confirm that MCP Metrics Gateway is the parent node for the HTTP tools and will expose them to MCP clients.

Tip: The MCP tools (Fetch Service Metrics, Retrieve Standards List, Fetch Standards Detail, Get Listing Traffic Data) are connected as AI tools to MCP Metrics Gateway, so all credentials should be configured at the tool nodes but invoked through the trigger.

Step 2: Connect eBay API Credentials

All HTTP tools use header-based authentication to access the eBay Analytics API.

Open Fetch Service Metrics and set Authentication to genericCredentialType with Generic Auth Type set to httpHeaderAuth.
Open Retrieve Standards List and set Authentication to genericCredentialType with Generic Auth Type set to httpHeaderAuth.
Open Fetch Standards Detail and set Authentication to genericCredentialType with Generic Auth Type set to httpHeaderAuth.
Open Get Listing Traffic Data and set Authentication to genericCredentialType with Generic Auth Type set to httpHeaderAuth.

Credential Required: Connect your genericCredentialType credentials (HTTP Header Auth) to each HTTP tool node listed above before testing.

Step 3: Set Up Seller Metrics Tools

Configure each HTTP tool to call the correct eBay endpoints and accept MCP-provided parameters.

In Fetch Service Metrics, set URL to =https://api.ebay.com{basePath}/customer_service_metric/{{ $fromAI('customer_service_metric_type', 'Use this path parameter to specify the type of customer service metrics and benchmark data you want returned for the seller. Supported types are: ITEM_NOT_AS_DESCRIBED ITEM_NOT_RECEIVED', 'string') }}/{{ $fromAI('evaluation_type', 'Use this path parameter to specify the type of the seller evaluation you want returned, either: CURRENT – A monthly evaluation that occurs on the 20th of every month. PROJECTED – A daily evaluation that provides a projection of how the seller is currently performing with regards to the upcoming evaluation period.', 'string') }}.
In Fetch Service Metrics, enable Send Query and add a query parameter named evaluation_marketplace_id with value ={{ $fromAI('evaluation_marketplace_id', 'Use this query parameter to specify the Marketplace ID to evaluate for the customer service metrics and benchmark data. For the list of supported marketplaces, see Analytics API requirements and restrictions.', 'string') }}.
In Retrieve Standards List, set URL to =https://api.ebay.com{basePath}/seller_standards_profile.
In Fetch Standards Detail, set URL to =https://api.ebay.com{basePath}/seller_standards_profile/{{ $fromAI('program', 'This input value specifies the region used to determine the seller's standards profile. Supply one of the four following values, PROGRAM_DE, PROGRAM_UK, PROGRAM_US, or PROGRAM_GLOBAL.', 'string') }}/{{ $fromAI('cycle', 'The period covered by the returned standards profile evaluation. Supply one of two values, CURRENT means the response reflects eBay's most recent monthly standards evaluation and PROJECTED means the response reflect the seller's projected monthly evaluation, as calculated at the time of the request.', 'string') }}.
In Get Listing Traffic Data, set URL to =https://api.ebay.com{basePath}/traffic_report and enable Send Query.
In Get Listing Traffic Data, add query parameters: dimension = ={{ $fromAI('dimension', 'This query parameter specifies the dimension, or "attribute," that is applied to the report metric. Valid values: DAY or LISTING Examples If you specify dimension=DAY and metric=CLICK_THROUGH_RATE, the traffic report contains the number of times an item displayed on a search results page and the buyer clicked through to the View Item page for each day in the date range, as in: 12-06-17: 32, 12-07-17: 54, ... If you specify dimension=LISTING and metric=LISTING_IMPRESSION_STORE, the traffic report contains the number of times that listing appeared on the seller's store during the specified date range. For example, LISTING_IMPRESSION_STORE: 157 means the item appeared 157 times in the store during the date range.', 'string') }}, filter = ={{ $fromAI('filter', 'This query parameter refines the information returned in the traffic report. Configure the following properties of the filter parameter to tune the traffic report to your needs: date_range Limits the report to the specified range of dates. Format the date range by enclosing the earliest date and end date for the report in brackets ("[ ]"), as follows: [YYYYMMDD..YYYYMMDD] ...', 'string') }}, metric = ={{ $fromAI('metric', 'This query parameter specifies the metrics you want covered in the report. Specify a comma-separated list of the metrics you want included in the report. Valid values: CLICK_THROUGH_RATE ...', 'string') }}, and sort = ={{ $fromAI('sort', 'This query parameter sorts the report on the specified metric. The metric you specify must be included in the configuration of the report\'s metric parameter. Sorting is helpful when you want to review how a specific metric is performing, such as the CLICK_THROUGH_RATE. Reports can be sorted in ascending or descending order. Precede the value of a descending-order request with a minus sign ("-"), for example: sort=-CLICK_THROUGH_RATE.', 'string') }}.

Tip: The Flowpast Branding sticky note is optional and does not affect execution; keep it for documentation or remove it for a cleaner canvas.

Step 4: Review Execution Flow

The MCP trigger exposes each HTTP tool to clients; there is no parallel execution configured in this workflow.

Verify that MCP Metrics Gateway is connected as the parent tool node to Fetch Service Metrics, Retrieve Standards List, Fetch Standards Detail, and Get Listing Traffic Data.
Confirm each tool node’s inputs use $fromAI() expressions so MCP clients can supply parameters dynamically.

⚠️ Common Pitfall: If you hardcode values and remove $fromAI() expressions, MCP clients will no longer be able to pass parameters dynamically.

Step 5: Test and Activate Your Workflow

Validate the trigger and tool responses before turning the workflow on for production use.

Click Execute Workflow and invoke the MCP endpoint for MCP Metrics Gateway with test parameters.
Confirm successful responses from Fetch Service Metrics, Retrieve Standards List, Fetch Standards Detail, and Get Listing Traffic Data in the execution output.
Check for valid HTTP responses (200-series) and expected JSON payloads from the eBay Analytics API.
Toggle the workflow to Active once tests succeed to enable production use.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Watch Out For

eBay API credentials can expire or need specific permissions. If things break, check your eBay developer app keys and token status first.
If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.

Common Questions

How quickly can I implement this eBay metrics automation?

Usually within about 30 minutes once your eBay credentials are ready.

Can non-technical teams implement this seller metrics automation?

Yes. No coding is required, but someone should be comfortable connecting credentials and testing a request once.

Is n8n free to use for this eBay metrics automation workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in eBay API usage, which is typically covered under your eBay developer access rather than per-call billing.

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

How do I adapt this eBay metrics automation solution to my specific challenges?

You can tailor what gets written into Google Sheets by transforming the returned API JSON into the columns you care about (for example, focusing only on late shipment indicators or a single program/cycle). If you want different metrics, swap which endpoint you call by routing to a different HTTP Request tool in the gateway. Common customizations include storing weekly snapshots with a date stamp, alerting in Slack when a threshold is crossed, and pulling traffic report fields into a simple “top listings” tab.

Why is my eBay connection failing in this workflow?

Most of the time it’s expired or incorrect eBay credentials. Regenerate your token (or confirm the right environment and scopes), then update the credential in n8n and re-run a single request. It can also be a wrong base path or missing required parameters like program/cycle for the standards detail call.

What’s the capacity of this eBay metrics automation solution?

If you self-host n8n, there’s no fixed execution limit (it mainly depends on your server). On n8n Cloud, capacity depends on your plan’s monthly executions, and this workflow typically uses one execution per request.

Is this eBay metrics automation better than using Zapier or Make?

Often, yes, because this workflow acts like a reusable “API gateway” with more flexible branching and request handling than most plug-and-play zaps. n8n also gives you the self-hosting option, which matters if you want to run lots of checks without worrying about task pricing. Zapier or Make can still be fine if your needs are simple and you only want a lightweight sheet update. The deciding factor is usually how many endpoints you need and how much control you want over parameters. If you want a second opinion, Talk to an automation expert.

Once your seller metrics land in one sheet, the weekly review becomes routine, not a project. Set it up once and use the time you get back to actually improve the numbers.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

{
"id": null,
"meta": {
"instanceId": "662ffeecce2f37e12d3aa027708b53c8801252ee1d7631973526afc0d94ff3e5",
"templateId": null,
"templateCredsSetupCompleted": null
},
"name": "Automated Seller Metrics MCP Service",
"tags": [],
"nodes": [
{
"id": "flowpast-topbar-5572",
"name": "Flowpast Branding",
"type": "n8n-nodes-base.stickyNote",
"position": [
0,
20
],
"parameters": {
"color": 7,
"width": 1020,
"height": 80,
"content": "## Flowpast.com | Automation Workflow Library\n**\ud83d\udcd6 Full tutorial & setup guide:** flowpast.com"
},
"typeVersion": 1
},
{
"id": "a468724a-7f22-4f1e-ace6-1df1ef769430",
"name": "MCP Metrics Gateway",
"type": "@n8n/n8n-nodes-langchain.mcpTrigger",
"position": [
920,
180
],
"webhookId": "331c2016-a632-4d45-9a64-4a9c0e27ad1d",
"parameters": {
"path": "-seller-service-metrics-api--mcp"
},
"typeVersion": 1
},
{
"id": "d151f9a6-cb8b-4904-870d-48078825edc4",
"name": "Fetch Service Metrics",
"type": "n8n-nodes-base.httpRequestTool",
"position": [
640,
120
],
"parameters": {
"url": "=https://api.ebay.com{basePath}/customer_service_metric/{{ $fromAI('customer_service_metric_type', 'Use this path parameter to specify the type of customer service metrics and benchmark data you want returned for the seller. Supported types are: ITEM_NOT_AS_DESCRIBED ITEM_NOT_RECEIVED', 'string') }}/{{ $fromAI('evaluation_type', 'Use this path parameter to specify the type of the seller evaluation you want returned, either: CURRENT – A monthly evaluation that occurs on the 20th of every month. PROJECTED – A daily evaluation that provides a projection of how the seller is currently performing with regards to the upcoming evaluation period.', 'string') }}",
"options": [],
"sendQuery": true,
"authentication": "genericCredentialType",
"genericAuthType": "httpHeaderAuth",
"queryParameters": {
"parameters": [
{
"name": "evaluation_marketplace_id",
"value": "={{ $fromAI('evaluation_marketplace_id', 'Use this query parameter to specify the Marketplace ID to evaluate for the customer service metrics and benchmark data. For the list of supported marketplaces, see Analytics API requirements and restrictions.', 'string') }}"
}
]
},
"toolDescription": "Use this method to retrieve a seller's performance and rating for the customer service metric. Control the response from the getCustomerServiceMetric method using the following path and query parameters: customer_service_metric_type controls the type of customer service transactions evaluated for the metric rating. evaluation_type controls the period you want to review. evaluation_marketplace_id specifies the target marketplace for the evaluation. Currently, metric data is returned for only peer benchmarking. For more detail on the workings of peer benchmarking, see Service metrics policy.\n\nParameters:\n- Path parameters:\n  \u2022 customer_service_metric_type (required) - Use this path parameter to specify the type of customer service metrics and benchmark data you want returned for the seller. Supported types are: ITEM_NOT_AS_DESCRIBED ITEM_NOT_RECEIVED\n  \u2022 evaluation_type (required) - Use this path parameter to specify the type of the seller evaluation you want returned, either: CURRENT – A monthly evaluation that occurs on the 20th of every month. PROJECTED – A daily evaluation that provides a projection of how the seller is currently performing with regards to the upcoming evaluation period.\n- Query parameters:\n  \u2022 evaluation_marketplace_id (required) - Use this query parameter to specify the Marketplace ID to evaluate for the customer service metrics and benchmark data. For the list of supported marketplaces, see Analytics API requirements and restrictions."
},
"typeVersion": 4.2
},
{
"id": "acc71602-9565-47f5-8cc2-08ebea1e9289",
"name": "Retrieve Standards List",
"type": "n8n-nodes-base.httpRequestTool",
"position": [
360,
260
],
"parameters": {
"url": "=https://api.ebay.com{basePath}/seller_standards_profile",
"options": [],
"authentication": "genericCredentialType",
"genericAuthType": "httpHeaderAuth",
"toolDescription": "Call retrieves all the standards profiles for the associated seller. A standards profile is a set of eBay seller metrics and the seller's associated compliance values (either TOP_RATED, ABOVE_STANDARD, or BELOW_STANDARD). A seller's multiple profiles are distinguished by two criteria, a \"program\" and a \"cycle.\" A profile's program is one of three regions where the seller may have done business, or PROGRAM_GLOBAL to indicate all marketplaces where the seller has done business. The cycle value specifies whether the standards compliance values were determined at the last official eBay evaluation or at the time of the request."
},
"typeVersion": 4.2
},
{
"id": "d7498287-45e6-418c-811e-24c1fa310916",
"name": "Fetch Standards Detail",
"type": "n8n-nodes-base.httpRequestTool",
"position": [
680,
330
],
"parameters": {
"url": "=https://api.ebay.com{basePath}/seller_standards_profile/{{ $fromAI('program', 'This input value specifies the region used to determine the seller's standards profile. Supply one of the four following values, PROGRAM_DE, PROGRAM_UK, PROGRAM_US, or PROGRAM_GLOBAL.', 'string') }}/{{ $fromAI('cycle', 'The period covered by the returned standards profile evaluation. Supply one of two values, CURRENT means the response reflects eBay's most recent monthly standards evaluation and PROJECTED means the response reflect the seller's projected monthly evaluation, as calculated at the time of the request.', 'string') }}",
"options": [],
"authentication": "genericCredentialType",
"genericAuthType": "httpHeaderAuth",
"toolDescription": "Call retrieves a single standards profile for the associated seller. A standards profile is a set of eBay seller metrics and the seller's associated compliance values (either TOP_RATED, ABOVE_STANDARD, or BELOW_STANDARD). A seller can have multiple profiles distinguished by two criteria, a \"program\" and a \"cycle.\" A profile's program is one of three regions where the seller may have done business, or PROGRAM_GLOBAL to indicate all marketplaces where the seller has done business. The cycle value specifies whether the standards compliance values were determined at the last official eBay evaluation (CURRENT) or at the time of the request (PROJECTED). Both cycle and a program values are required URI parameters for this method.\n\nParameters:\n- Path parameters:\n  \u2022 cycle (required) - Period covered by the returned standards profile evaluation. Supply one of two values, CURRENT means the response reflects eBay's most recent monthly standards evaluation and PROJECTED means the response reflect the seller's projected monthly evaluation, as calculated at the time of the request.\n  \u2022 program (required) - Input value specifies the region used to determine the seller's standards profile. Supply one of the four following values, PROGRAM_DE, PROGRAM_UK, PROGRAM_US, or PROGRAM_GLOBAL."
},
"typeVersion": 4.2
},
{
"id": "20a7bbe4-faf8-4703-ac5a-4d5346a17f9f",
"name": "Get Listing Traffic Data",
"type": "n8n-nodes-base.httpRequestTool",
"position": [
0,
470
],
"parameters": {
"url": "=https://api.ebay.com{basePath}/traffic_report",
"options": [],
"sendQuery": true,
"authentication": "genericCredentialType",
"genericAuthType": "httpHeaderAuth",
"queryParameters": {
"parameters": [
{
"name": "dimension",
"value": "={{ $fromAI('dimension', 'This query parameter specifies the dimension, or \"attribute,\" that is applied to the report metric. Valid values: DAY or LISTING Examples If you specify dimension=DAY and metric=CLICK_THROUGH_RATE, the traffic report contains the number of times an item displayed on a search results page and the buyer clicked through to the View Item page for each day in the date range, as in: 12-06-17: 32, 12-07-17: 54, ... If you specify dimension=LISTING and metric=LISTING_IMPRESSION_STORE, the traffic report contains the number of times that listing appeared on the seller's store during the specified date range. For example, LISTING_IMPRESSION_STORE: 157 means the item appeared 157 times in the store during the date range.', 'string') }}"
},
{
"name": "filter",
"value": "={{ $fromAI('filter', 'This query parameter refines the information returned in the traffic report. Configure the following properties of the filter parameter to tune the traffic report to your needs: date_range Limits the report to the specified range of dates. Format the date range by enclosing the earliest date and end date for the report in brackets (\"[ ]\"), as follows: [YYYYMMDD..YYYYMMDD] The maximum range between the start and end dates is 90 days, and the earliest start date you can specify is two years prior to the current date, which is defined as 730 days (365 * 2), not accounting for Leap Year. The last date for which traffic data exists is a value called lastUpdatedDate. eBay returns an error if you specify a date range greater than 90 days, or the start date is after the lastUpdatedDate. If the specified end date is beyond the lastUpdatedDate, eBay returns data up to the lastUpdatedDate. Required: Always listing_ids This filter limits the results to only the supplied list of listingId values. You can specify to 200 different listingId values. Enclose the list of IDs with curly braces (\"{ }\"), and separate multiple values with a pipe character (\"|\"). This filter only returns data for listings that have been either active or sold in last 90 days, and any unsold listings in the last 30 days. All listings must be the seller's and they must be listed on the marketplace specified by the marketplace_ids filter argument. marketplace_ids This filter limits the report to seller data related to only the specified marketplace ID (currently the filter allows only a single marketplace ID). Enclose the marketplace ID in curly braces (\"{ }\"). Valid values: EBAY_AU EBAY_DE EBAY_GB EBAY_US EBAY_MOTORS_US Required if you set the dimension parameter to DAY. traffic_source Limits the report to either Promoted Listings items or non-Promoted Listings (organic) items. Valid values are ORGANIC and PROMOTED_LISTINGS. Enclose the list of values with curly braces (\"{ }\"), and separate multiple values with a pipe character (\"|\") The default is both values. Example filter parameter The following example shows how to configure the filter parameter with the marketplace_ids and date_range filters: filter=marketplace_ids:{EBAY_US},date_range:[20170601..20170828] Note: You must URL encode all the values you supply in the filter parameter, as described in URL parameters.', 'string') }}"
},
{
"name": "metric",
"value": "={{ $fromAI('metric', 'This query parameter specifies the metrics you want covered in the report. Specify a comma-separated list of the metrics you want included in the report. Valid values: CLICK_THROUGH_RATE The number of times an item displays on the search results page divided by the number of times buyers clicked through to its View Item page. Localized name: Click through rate LISTING_IMPRESSION_SEARCH_RESULTS_PAGE The number of times the seller\\'s listings displayed on the search results page. Note, the listing might not have been visible to the buyer due to its position on the page. Localized name: Listing impressions from the search results page LISTING_IMPRESSION_STORE The number of times the seller\\'s listings displayed on the seller\\'s store. Note, the listing might not have been visible to the buyer due to its position on the page. Localized name: Listing impressions from your Store LISTING_IMPRESSION_TOTAL The total number of times the seller\\'s listings displayed on the search results page OR in the seller\\'s store. The item is counted each time it displays on either page. However, the listing might not have been visible to the buyer due to its position on the page. This is a combination of: LISTING_IMPRESSION_SEARCH_RESULTS_PAGE + LISTING_IMPRESSION_STORE. Localized name: Total listing impressions LISTING_VIEWS_SOURCE_DIRECT The number of times a View Item page was directly accessed, such as when a buyer navigates to the page using a bookmark. Localized name: Direct views LISTING_VIEWS_SOURCE_OFF_EBAY The number of times a View Item page was accessed via a site other than eBay, such as when a buyer clicks on a link to the listing from a search engine page. Localized name: Off eBay views LISTING_VIEWS_SOURCE_OTHER_EBAY The number of times a View Item page was accessed from an eBay page that is not either the search results page or the seller\\'s store. Localized name: Views from non-search and non-store pages within eBay LISTING_VIEWS_SOURCE_SEARCH_RESULTS_PAGE The number of times the item displayed on the search results page. Localized name: Views on the search results page LISTING_VIEWS_SOURCE_STORE The number of times a View Item page was accessed via the seller\\'s store. Localized name: Views from your Store LISTING_VIEWS_TOTAL Total number of listings viewed. This number sums: LISTING_VIEWS_SOURCE_DIRECT LISTING_VIEWS_SOURCE_OFF_EBAY LISTING_VIEWS_SOURCE_OTHER_EBAY LISTING_VIEWS_SOURCE_SEARCH_RESULTS_PAGE LISTING_VIEWS_SOURCE_STORE. Localized name: Total views SALES_CONVERSION_RATE The number of completed transactions divided by the number of View Item page views. Equals: TRANSACTION / LISTING_VIEWS_TOTAL Localized name: Sales conversion rate TRANSACTION The total number of completed transactions. Localized name: Transaction count', 'string') }}"
},
{
"name": "sort",
"value": "={{ $fromAI('sort', 'This query parameter sorts the report on the specified metric. The metric you specify must be included in the configuration of the report\\'s metric parameter. Sorting is helpful when you want to review how a specific metric is performing, such as the CLICK_THROUGH_RATE. Reports can be sorted in ascending or descending order. Precede the value of a descending-order request with a minus sign (\"-\"), for example: sort=-CLICK_THROUGH_RATE.', 'string') }}"
}
]
},
"toolDescription": "Report that details the user traffic received by a seller's listings. A traffic report gives sellers the ability to review how often their listings appeared on eBay, how many times their listings are viewed, and how many purchases were made. The report also returns the report's start and end dates, and the date the information was last updated. When using this call: Be sure to URL-encode the values you pass in query parameters, as described in URI parameters. See the request samples below for details. You can only specify a single metric in the sort parameter and the specified metric must be listed in the metric parameter of your request. Parameter names are case sensitive, but metric names are not. For example, the following are correct: sort=LISTING_IMPRESSION_TOTAL sort=lisitng_impression_total metric=lisitng_impression_total However, these are incorrect: SORT=LISTING_IMPRESSION_TOTAL SORT=lisitng_impression_total Metric=lisitng_impression_total For more information, see Traffic report details.\n\nParameters:\n- Query parameters:\n  \u2022 dimension (optional) - Query parameter specifies the dimension, or \"attribute,\" that is applied to the report metric. Valid values: DAY or LISTING Examples If you specify dimension=DAY and metric=CLICK_THROUGH_RATE, the traffic report contains the number of times an item displayed on a search results page and the buyer clicked through to the View Item page for each day in the date range, as in: 12-06-17: 32, 12-07-17: 54, ... If you specify dimension=LISTING and metric=LISTING_IMPRESSION_STORE, the traffic report contains the number of times that listing appeared on the seller's store during the specified date range. For example, LISTING_IMPRESSION_STORE: 157 means the item appeared 157 times in the store during the date range.\n  \u2022 filter (optional) - Query parameter refines the information returned in the traffic report. Configure the following properties of the filter parameter to tune the traffic report to your needs: date_range Limits the report to the specified range of dates. Format the date range by enclosing the earliest date and end date for the report in brackets (\"[ ]\"), as follows: [YYYYMMDD..YYYYMMDD] The maximum range between the start and end dates is 90 days, and the earliest start date you can specify is two years prior to the current date, which is defined as 730 days (365 * 2), not accounting for Leap Year. The last date for which traffic data exists is a value called lastUpdatedDate. eBay returns an error if you specify a date range greater than 90 days, or the start date is after the lastUpdatedDate. If the specified end date is beyond the lastUpdatedDate, eBay returns data up to the lastUpdatedDate. Required: Always listing_ids This filter limits the results to only the supplied list of listingId values. You can specify to 200 different listingId values. Enclose the list of IDs with curly braces (\"{ }\"), and separate multiple values with a pipe character (\"|\"). This filter only returns data for listings that have been either active or sold in last 90 days, and any unsold listings in the last 30 days. All listings must be the seller's and they must be listed on the marketplace specified by the marketplace_ids filter argument. marketplace_ids This filter limits the report to seller data related to only the specified marketplace ID (currently the filter allows only a single marketplace ID). Enclose the marketplace ID in curly braces (\"{ }\"). Valid values: EBAY_AU EBAY_DE EBAY_GB EBAY_US EBAY_MOTORS_US Required if you set the dimension parameter to DAY. traffic_source Limits the report to either Promoted Listings items or non-Promoted Listings (organic) items. Valid values are ORGANIC and PROMOTED_LISTINGS. Enclose the list of values with curly braces (\"{ }\"), and separate multiple values with a pipe character (\"|\") The default is both values. Example filter parameter The following example shows how to configure the filter parameter with the marketplace_ids and date_range filters: filter=marketplace_ids:{EBAY_US},date_range:[20170601..20170828] Note: You must URL encode all the values you supply in the filter parameter, as described in URL parameters.\n  \u2022 metric (optional) - Query parameter specifies the metrics you want covered in the report. Specify a comma-separated list of the metrics you want included in the report. Valid values: CLICK_THROUGH_RATE The number of times an item displays on the search results page divided by the number of times buyers clicked through to its View Item page. Localized name: Click through rate LISTING_IMPRESSION_SEARCH_RESULTS_PAGE The number of times the seller's listings displayed on the search results page. Note, the listing might not have been visible to the buyer due to its position on the page. Localized name: Listing impressions from the search results page LISTING_IMPRESSION_STORE The number of times the seller's listings displayed on the seller's store. Note, the listing might not have been visible to the buyer due to its position on the page. Localized name: Listing impressions from your Store LISTING_IMPRESSION_TOTAL The total number of times the seller's listings displayed on the search results page OR in the seller's store. The item is counted each time it displays on either page. However, the listing might not have been visible to the buyer due to its position on the page. This is a combination of: LISTING_IMPRESSION_SEARCH_RESULTS_PAGE + LISTING_IMPRESSION_STORE. Localized name: Total listing impressions LISTING_VIEWS_SOURCE_DIRECT The number of times a View Item page was directly accessed, such as when a buyer navigates to the page using a bookmark. Localized name: Direct views LISTING_VIEWS_SOURCE_OFF_EBAY The number of times a View Item page was accessed via a site other than eBay, such as when a buyer clicks on a link to the listing from a search engine page. Localized name: Off eBay views LISTING_VIEWS_SOURCE_OTHER_EBAY The number of times a View Item page was accessed from an eBay page that is not either the search results page or the seller's store. Localized name: Views from non-search and non-store pages within eBay LISTING_VIEWS_SOURCE_SEARCH_RESULTS_PAGE The number of times the item displayed on the search results page. Localized name: Views on the search results page LISTING_VIEWS_SOURCE_STORE The number of times a View Item page was accessed via the seller's store. Localized name: Views from your Store LISTING_VIEWS_TOTAL Total number of listings viewed. This number sums: LISTING_VIEWS_SOURCE_DIRECT LISTING_VIEWS_SOURCE_OFF_EBAY LISTING_VIEWS_SOURCE_OTHER_EBAY LISTING_VIEWS_SOURCE_SEARCH_RESULTS_PAGE LISTING_VIEWS_SOURCE_STORE. Localized name: Total views SALES_CONVERSION_RATE The number of completed transactions divided by the number of View Item page views. Equals: TRANSACTION / LISTING_VIEWS_TOTAL Localized name: Sales conversion rate TRANSACTION The total number of completed transactions. Localized name: Transaction count\n  \u2022 sort (optional) - Query parameter sorts the report on the specified metric. The metric you specify must be included in the configuration of the report's metric parameter. Sorting is helpful when you want to review how a specific metric is performing, such as the CLICK_THROUGH_RATE. Reports can be sorted in ascending or descending order. Precede the value of a descending-order request with a minus sign (\"-\"), for example: sort=-CLICK_THROUGH_RATE."
},
"typeVersion": 4.2
}
],
"active": false,
"shared": [],
"pinData": [],
"settings": {
"timezone": "America/New_York"
},
"createdAt": null,
"updatedAt": null,
"versionId": null,
"isArchived": false,
"staticData": null,
"connections": {
"Fetch Standards Detail": {
"ai_tool": [
[
{
"node": "MCP Metrics Gateway",
"type": "ai_tool",
"index": 0
}
]
]
},
"Retrieve Standards List": {
"ai_tool": [
[
{
"node": "MCP Metrics Gateway",
"type": "ai_tool",
"index": 0
}
]
]
},
"Get Listing Traffic Data": {
"ai_tool": [
[
{
"node": "MCP Metrics Gateway",
"type": "ai_tool",
"index": 0
}
]
]
},
"Fetch Service Metrics": {
"ai_tool": [
[
{
"node": "MCP Metrics Gateway",
"type": "ai_tool",
"index": 0
}
]
]
}
},
"triggerCount": 0
}