AMC standard vs custom queries: what Amazon actually offers

In short: Amazon calls them instructional queries, no-code templates and solutions: ready-made queries and templates in the use case library of the AMC interface. "Standard query" is not an Amazon term but the colloquial shorthand. Your own query in AMC-SQL is the counterpart: you need it when your question is not covered by a template.

What Amazon means by "standard queries"

The search term "AMC standard queries" leads into the AMC interface but not to an Amazon feature with that name. Amazon uses three labels in its documentation: "Amazon-authored SQL queries, also known as instructional queries (IQs), no-code Templates, and Solutions designed by our experts". These three objects live in the Use Case library, the Use Cases tab of the AMC console. Amazon links that library explicitly only for users of the AMC interface, so the content of the templates is visible only when signed in.

The term "standard query" is still worth keeping: it describes the distinction that exists in the interface. A ready-made query from the library is a query someone else wrote, usually Amazon itself. An own query is one you formulate in AMC-SQL and adapt to your advertising job. The mistake the search query carries is the assumption that there is a centrally maintained collection of queries under a fixed name. That collection does exist, it is just called something else.

The three routes to an analysis

Before you write a query, check whether one of the ready-made variants already answers your question. Amazon structures the choice in three stages, and each stage shifts work from you to Amazon.

RouteWhat you getWhat it costs
no-code templateA ready-made query without code: you pick parameters and start the run.No SQL, but you are locked to the fields and filters of the template.
Instructional query (IQ)A SQL query written by Amazon that you can look at as a template and adapt.You read Amazon SQL and still have to check whether filters and time frame fit.
Own query in AMC-SQLYour query across the tables and fields of your instance, freely parameterizable.You need AMC-SQL knowledge and maintain the query yourself.

The practical difference is control. A no-code template delivers a result within minutes that you never wrote yourself and therefore cannot fully explain. An own query costs more effort, but then you know every line. The "standard or custom" question is therefore not a matter of taste but of how binding the result has to be.

Our assessment: use a ready-made template when you ask a question Amazon has already been asked often. Write your own when you need a custom metric, a custom time frame or a join with your first-party data. See the guide on AMC SQL with AI if you would rather not write the query by hand.

When you need your own AMC-SQL query

There are three triggers for the switch to an own query. First a metric that no template covers, for example your own revenue model or a definition of a "qualified customer". Second a time frame the template does not provide, for example a rolling window instead of a calendar month. Third data that only exists in your instance: signals you uploaded yourself appear in no Amazon template.

A fourth trigger is less visible: the question of whether a template fits your advertising job at all. Amazon ships the library for common use cases, not for every business model. Before you turn the result of a template into a decision, check which filters it sets and which fields it outputs.

  • **Define metrics.** A custom definition, for example an incremental contribution margin, cannot be delivered by a template you do not know.
  • **Set time frames freely.** Own queries set their own window; templates come with a fixed interval.
  • **Join first-party data.** Uploaded signals live in your instance and appear in no Amazon query.
  • **Make the result traceable.** If you have to justify a decision, you should be able to show the query.

Custom parameters: one query, many analyses

Amazon solves the repetition case with custom parameters. When you define a workflow you can create parameters whose values you pass on each run instead of hard-coding them in the query. Each parameter knows a defaultValue that you can overwrite at execution time with parameterValues. That keeps one query reusable for time frame, campaign filter or ASIN selection without editing the text every time.

For advertisers that is the difference between a query that is rewritten every month and a workflow you parameterize and put in the scheduler. The price is one line of documentation per parameter: if nobody later remembers what value defaultValue had, that is the place where a report silently turns wrong.

The aggregation thresholds apply to every query

One point is easily missed with ready-made templates: the aggregation thresholds apply to every analysis, no matter whether the query comes from Amazon or from you. A column of level LOW may only be output if the row contains at least two distinct users. Levels MEDIUM and HIGH require at least one hundred distinct users. VERY HIGH, such as user_id, may never appear in the final SELECT and cannot be filtered with literal values either.

In practice that means a template can return rows whose dimensions are empty. Amazon calls them NULL rows and recommends checking the share of NULL values before you discard them or make the query coarser. Anyone who adopts a ready-made template unchecked adopts these filter rules unseen.

For the column postal_code, Amazon gives the example that a filter with literal values is not allowed: "For example, postal_code falls into this category and this filter is not allowed: WHERE postal_code in (10001, 10011)." For the same reason user_id must not be filtered with literal values. A query that compares such literal values is rejected.

How to decide before the first query

A robust process starts with the question, not with the query. First formulate the decision that will be made at the end, then write down which metric and time frame it needs. Only then is it worth opening the use case library: you are then looking for a question rather than for a piece of SQL you have to understand.

  • **Formulate the decision.** What is to be decided at the end? Budget, audience or a report to third parties?
  • **Note metric and time frame.** Without both figures the analysis is not unambiguous.
  • **Check the library.** Is there a template that delivers exactly this metric in exactly this time frame?
  • **Verify the result.** Check filters, units and NULL rows before the value carries a decision.
  • **Only then customise.** Add what is missing via a custom parameter instead of copying the query.

For getting started, the sandbox is worth it: it contains synthetic signals with the same structure and statistics as real AMC data. Testing a query there costs no budget and answers the question whether your filter even delivers the desired result. How that works exactly is in the guide to the AMC sandbox. You check the metrics themselves against the schema reference before you move a query into the instance.

Frequently asked questions

What are AMC standard queries?

That is not an official Amazon term. Amazon documents instructional queries (IQs), no-code templates and solutions in the use case library of the AMC interface. People usually mean these ready-made queries and templates when they say "standard queries". According to Amazon the content of the templates is only available in the interface, so checking them from outside is not possible.

When do I need my own AMC-SQL query?

When no template covers your question: a custom metric, a custom time frame, uploaded first-party signals, or the obligation to justify the result to third parties. A good test is whether you can explain the template’s answer. If you do not know its filter and field structure, the own query is the more reliable route.

Do the aggregation thresholds apply to ready-made templates too?

Yes. The thresholds are a property of the data and the output, not of the query. A row with fewer than two distinct users may not output a LOW column, MEDIUM and HIGH require one hundred users. A ready-made template can therefore return NULL rows whose dimensions are missing. Check the result before you use the value further.

What are custom parameters and when do they help?

Custom parameters are placeholders you create when defining a workflow and fill with values on each run. Each parameter has a defaultValue that you can overwrite via parameterValues. That keeps one query reusable for changing time frames, campaigns or ASIN selections without editing the query text.

Where do I find the ready-made queries?

In the Use Cases tab of the AMC interface. Amazon links the use case library explicitly only for users of the AMC interface, so you see the content of the templates only when signed in. Via the workflows API you create your own queries and parameters; there is no public list of the templates with SQL text.

Sources: Amazon Ads API: Manage a workflow (Use Case library, custom parameters) · Amazon Ads API: Aggregation threshold in AMC · Amazon Ads API: How AMC works (retrieved 2026-11-17)

Keep reading: Writing AMC SQL with AI · AMC cheat sheet · AMC sandbox