# Metricanic

> Set up campaign tracking, record conversions, understand reports, and connect Metricanic to your tools.

- [Metricanic documentation](https://docs.metricanic.com/index.md): Launch your first campaign, connect conversions, and understand where your traffic earns money.
- [How Metricanic works](https://docs.metricanic.com/start/overview.md): Understand how campaigns connect traffic, destinations, costs, and conversions.
- [Create your first campaign](https://docs.metricanic.com/start/first-campaign.md): Build a simple redirect campaign and verify a visit and conversion from start to finish.
- [Choose a tracking mode](https://docs.metricanic.com/tracking/modes.md): Decide whether the tracker or your page should receive the visitor first, and understand what that changes.
- [Tracking domains](https://docs.metricanic.com/tracking/domains.md): Connect a dedicated subdomain and verify DNS, certificate, and tracking readiness.
- [Campaigns](https://docs.metricanic.com/tracking/campaigns.md): Connect a traffic source, tracking mode, costs, events, and destinations in one campaign.
- [Campaign costs](https://docs.metricanic.com/tracking/costs.md): Choose a visit cost model and understand how event costs affect total spend.
- [Traffic sources](https://docs.metricanic.com/tracking/traffic-sources.md): Capture ad click IDs, prices, and campaign parameters from incoming traffic.
- [Affiliate networks](https://docs.metricanic.com/tracking/affiliate-networks.md): Connect an offer's click ID parameter with the network's conversion callback.
- [Offers](https://docs.metricanic.com/tracking/offers.md): Add destination URLs, preserve attribution, and choose how offers enter a campaign.
- [Landing pages and tracking scripts](https://docs.metricanic.com/tracking/landings.md): Install landing tracking and connect offer buttons with a click URL or data-dtp-link, so clicks and conversions belong to the right visit.
- [Protect a landing page](https://docs.metricanic.com/tracking/landing-protection.md): Make a PHP landing open through your campaign link and reject requests without a valid tracker key.
- [Rotators and traffic rules](https://docs.metricanic.com/tracking/rotators.md): Choose destinations with ordered rules, weighted paths, landings, and offers.
- [URL macros](https://docs.metricanic.com/tracking/url-macros.md): Pass visit and event values between traffic sources, pages, offers, and postbacks.
- [Decide what counts as a conversion](https://docs.metricanic.com/conversions/goals.md): Model leads, purchases, and other funnel stages so conversion totals and revenue answer the right business question.
- [Send incoming events](https://docs.metricanic.com/conversions/incoming-events.md): Connect a site or affiliate network to a tracked visit, pass payout and transaction IDs, and verify the event in reports.
- [Send conversions back to a traffic source](https://docs.metricanic.com/conversions/postbacks.md): Send conversions and revenue to another platform, send a percentage such as 50% with event cost, and verify the delivered amount.
- [Record event revenue, cost, and value](https://docs.metricanic.com/conversions/revenue-and-cost.md): Choose fixed or incoming payout, model an event expense, and understand which amounts change campaign profit.
- [Find what drives campaign performance](https://docs.metricanic.com/reports/overview.md): Move from campaign profit to countries, devices, and offers, then use individual records to explain unexpected results.
- [Understand report metrics](https://docs.metricanic.com/reports/metrics.md): Choose the right denominator, calculate campaign performance, and distinguish zero, missing data, and unique visitors.
- [Create a metric for your funnel](https://docs.metricanic.com/reports/custom-metrics.md): Build formulas for approval rate, units per order, or profit per visit, then validate their format and calculation scope.
- [Choose dates, filters, and sorting](https://docs.metricanic.com/reports/filters-and-dates.md): Keep report scope consistent, understand late conversions, and isolate the traffic segment you want to compare.
- [Mark segments for follow-up](https://docs.metricanic.com/reports/tags.md): Use persistent campaign tags to remember promising, uncertain, or costly traffic segments while you analyze reports.
- [Reconcile campaign spending](https://docs.metricanic.com/reports/cost-corrections.md): Replace estimated campaign cost with a known amount for closed days, understand the allocation, and restore original costs.
- [Connect Google Ads](https://docs.metricanic.com/integrations/google-ads.md): Connect the Google account that will receive your tracked conversions, then choose an offline conversion action.
- [Send conversions to Google Ads](https://docs.metricanic.com/integrations/google-ads-postbacks.md): Map a Google Ads route to the right campaign goal and verify the conversion from ad click to upload.
- [Connect an AI agent](https://docs.metricanic.com/integrations/ai-agents.md): Give Claude read-only access to campaign setup and reports, with enough context to interpret the numbers correctly.
- [Create automation rules](https://docs.metricanic.com/automation/rules.md): Turn repeated report checks into tags on traffic parameter values, while keeping the advertising decision in your hands.
- [Choose a rule schedule](https://docs.metricanic.com/automation/schedules.md): Balance detection speed and conversion delay by choosing the evaluation window, run frequency, and recent traffic exclusion.
- [Account and timezone](https://docs.metricanic.com/account/profile.md): Keep your account details current and choose the reporting timezone that matches the comparisons you make.
- [Account security](https://docs.metricanic.com/account/security.md): Change your sign-in password and understand which credentials control account, API, AI, and landing access.
- [Manage API keys](https://docs.metricanic.com/account/api-keys.md): Give each integration its own scoped credential, verify it, and replace it without losing access unexpectedly.
- [Subscription and usage](https://docs.metricanic.com/account/billing.md): Understand your event allowance, choose when a plan change takes effect, and keep payment and access in sync.
- [Find why visits or clicks are missing](https://docs.metricanic.com/troubleshooting/no-visits-or-clicks.md): Test one visitor journey, separate arrival from offer clicks, and locate missing tracking requests or lost context.
- [Find why a conversion is missing](https://docs.metricanic.com/troubleshooting/no-conversions.md): Follow one order from its stored click ID through the incoming request, event rule, report date, and outgoing delivery.
- [Reconcile numbers between systems](https://docs.metricanic.com/troubleshooting/discrepancies.md): Compare like-for-like traffic, conversions, spending, and dates before deciding whether a difference is a tracking failure.
- [Start with the API](https://docs.metricanic.com/api-reference/introduction.md): Build a report export or tracking integration using Metricanic's supported public API and verify the result step by step.
- [Authenticate API requests](https://docs.metricanic.com/api-reference/authentication.md): Verify the key, workspace, and scope before connecting your application to Metricanic.
- [Query reports and inspect events](https://docs.metricanic.com/api-reference/reports-and-events.md): Choose aggregate reports for performance analysis and cursor-based event queries for investigating individual tracking outcomes.
- [Handle API errors](https://docs.metricanic.com/api-reference/errors.md): Separate invalid requests, missing access, conflicts, and temporary failures so your integration takes the right next step.
- [Archive and restore entities](https://docs.metricanic.com/api-reference/archive-and-restore.md): Retire tracking entities without erasing them, resolve dependency conflicts, and restore campaigns in a publishable state.
- [Who am I](https://docs.metricanic.com/api-reference/endpoints/who-am-i.md): Identifies the caller. Works with both Bearer tokens and panel sessions. The primary connectivity and auth smoke check for integrations. For Bearer callers returns the key id and label the token was issued for.
- [List campaigns](https://docs.metricanic.com/api-reference/endpoints/list-campaigns.md): Public campaign list using the canonical campaign response shape.
- [Create campaign](https://docs.metricanic.com/api-reference/endpoints/create-campaign.md): Creates a campaign using a domain-oriented public contract. Campaigns attach to an existing rotator with `destination.mode=use_rotator`. Create or edit rotators through the rotator API.
- [Get campaign](https://docs.metricanic.com/api-reference/endpoints/get-campaign.md): Returns a single campaign in the canonical campaign shape.
- [Update campaign](https://docs.metricanic.com/api-reference/endpoints/update-campaign.md): Partially updates campaign-level fields. PATCH may switch to an existing rotator using `destination.mode=use_rotator`. Creating a new rotator after campaign creation should use the rotator API followed by this PATCH.
- [Archive campaign](https://docs.metricanic.com/api-reference/endpoints/archive-campaign.md): Archives the campaign. Archived campaigns stop being served and can be restored via POST /api/v1/campaigns/restore.
- [List goals](https://docs.metricanic.com/api-reference/endpoints/list-campaign-goals.md): Returns the campaign goal rule hierarchy - prioritized rules with conditions and per-goal actions (payout, cost, conversion and postback flags). Read-only in public API v1. Goal rules are managed in the panel.
- [Archive campaigns](https://docs.metricanic.com/api-reference/endpoints/archive-campaigns-bulk.md): Archives multiple campaigns by id. Ids are de-duplicated. The operation is all-or-nothing: if any id is unknown the request fails with 404 and `details.missing` lists the unknown ids.
- [Restore campaigns](https://docs.metricanic.com/api-reference/endpoints/restore-campaigns-bulk.md): Restores previously archived campaigns by id. Ids are de-duplicated. The operation is all-or-nothing: if any id is unknown the request fails with 404 and `details.missing` lists the unknown ids. Runtime republish is scheduled automatically when required.
- [List landings](https://docs.metricanic.com/api-reference/endpoints/list-landings.md): Lists landings of the tenant ordered by creation time.
- [Create landing](https://docs.metricanic.com/api-reference/endpoints/create-landing.md): Creates a landing and returns its id.
- [Get landing](https://docs.metricanic.com/api-reference/endpoints/get-landing.md): Returns a single landing of the tenant by id.
- [Update landing](https://docs.metricanic.com/api-reference/endpoints/update-landing.md): Partially updates a landing. Only provided fields change.
- [Delete landing](https://docs.metricanic.com/api-reference/endpoints/delete-landing.md): Archives the landing (soft delete). Fails with 409 while the landing is used by a rotator stream. Restore later via POST /api/v1/landings/restore.
- [Archive landings](https://docs.metricanic.com/api-reference/endpoints/archive-landings-bulk.md): Archives multiple landings by id. Ids are de-duplicated. The operation is all-or-nothing: if any id is unknown the request fails with 404 and `details.missing` lists the unknown ids.
- [Restore landings](https://docs.metricanic.com/api-reference/endpoints/restore-landings-bulk.md): Restores previously archived landings by id. Ids are de-duplicated. The operation is all-or-nothing: if any id is unknown the request fails with 404 and `details.missing` lists the unknown ids.
- [List offers](https://docs.metricanic.com/api-reference/endpoints/list-offers.md): Lists offers of the tenant, including the linked affiliate network reference.
- [Create offer](https://docs.metricanic.com/api-reference/endpoints/create-offer.md): Creates an offer and returns its id.
- [Get offer](https://docs.metricanic.com/api-reference/endpoints/get-offer.md): Returns a single offer of the tenant by id.
- [Update offer](https://docs.metricanic.com/api-reference/endpoints/update-offer.md): Partially updates an offer. Only provided fields change.
- [Delete offer](https://docs.metricanic.com/api-reference/endpoints/delete-offer.md): Archives the offer (soft delete). Fails with 409 while the offer is used by a rotator stream. Restore later via POST /api/v1/offers/restore.
- [Archive offers](https://docs.metricanic.com/api-reference/endpoints/archive-offers-bulk.md): Archives multiple offers by id. Ids are de-duplicated. The operation is all-or-nothing: if any id is unknown the request fails with 404 and `details.missing` lists the unknown ids.
- [Restore offers](https://docs.metricanic.com/api-reference/endpoints/restore-offers-bulk.md): Restores previously archived offers by id. Ids are de-duplicated. The operation is all-or-nothing: if any id is unknown the request fails with 404 and `details.missing` lists the unknown ids.
- [Query reports](https://docs.metricanic.com/api-reference/endpoints/query-reports.md): Returns aggregate performance grouped by your chosen dimensions. Use it to compare campaigns, destinations, and traffic segments. Filter and sort the results to investigate a specific question.
- [List rotators](https://docs.metricanic.com/api-reference/endpoints/list-rotators.md): Lists rotators of the tenant ordered by creation time.
- [Create rotator](https://docs.metricanic.com/api-reference/endpoints/create-rotator.md): Creates a rotator and returns its id. Routing rules are managed in the panel. Inspect them via GET /api/v1/rotators/{id}/rules.
- [Get rotator](https://docs.metricanic.com/api-reference/endpoints/get-rotator.md): Returns a single rotator of the tenant by id.
- [Update rotator](https://docs.metricanic.com/api-reference/endpoints/update-rotator.md): Partially updates a rotator. Only provided fields change. Returns the updated entity.
- [Archive rotator](https://docs.metricanic.com/api-reference/endpoints/archive-rotator.md): Archives the rotator. Restore later via POST /api/v1/rotators/restore.
- [Get rotator rules](https://docs.metricanic.com/api-reference/endpoints/get-rotator-rules.md): Returns rotator routing rules ordered by priority: rule conditions plus weighted streams of landings and offers. Read-only in public API v1. Rules are managed in the panel.
- [List rotator paths](https://docs.metricanic.com/api-reference/endpoints/list-rotator-paths.md): Lists rotator paths - stable stream identities that attribute traffic to a stream across rule edits.
- [Archive rotators](https://docs.metricanic.com/api-reference/endpoints/archive-rotators-bulk.md): Archives multiple rotators by id. Ids are de-duplicated. The operation is all-or-nothing: if any id is unknown the request fails with 404 and `details.missing` lists the unknown ids.
- [Restore rotators](https://docs.metricanic.com/api-reference/endpoints/restore-rotators-bulk.md): Restores previously archived rotators by id. Ids are de-duplicated. The operation is all-or-nothing: if any id is unknown the request fails with 404 and `details.missing` lists the unknown ids.
- [List traffic sources](https://docs.metricanic.com/api-reference/endpoints/list-traffic-sources.md): Lists traffic sources of the tenant, including click id / cost parameter mapping and source postback settings.
- [Create traffic source](https://docs.metricanic.com/api-reference/endpoints/create-traffic-source.md): Creates a traffic source and returns its id.
- [Get traffic source](https://docs.metricanic.com/api-reference/endpoints/get-traffic-source.md): Returns a single traffic source.
- [Update traffic source](https://docs.metricanic.com/api-reference/endpoints/update-traffic-source.md): Partially updates a traffic source. Only provided fields change. Returns the updated entity.
- [Delete traffic source](https://docs.metricanic.com/api-reference/endpoints/delete-traffic-source.md): Archives the traffic source (soft delete). Fails with 409 while the traffic source is used by campaigns. Restore later via POST /api/v1/traffic-sources/restore.
- [Archive traffic sources](https://docs.metricanic.com/api-reference/endpoints/archive-traffic-sources-bulk.md): Archives multiple traffic sources by id. Ids are de-duplicated. The operation is all-or-nothing: if any id is unknown the request fails with 404 and `details.missing` lists the unknown ids.
- [Restore traffic sources](https://docs.metricanic.com/api-reference/endpoints/restore-traffic-sources-bulk.md): Restores previously archived traffic sources by id. Ids are de-duplicated. The operation is all-or-nothing: if any id is unknown the request fails with 404 and `details.missing` lists the unknown ids.
- [List affiliate networks](https://docs.metricanic.com/api-reference/endpoints/list-affiliate-networks.md): Lists affiliate networks of the tenant.
- [Create affiliate network](https://docs.metricanic.com/api-reference/endpoints/create-affiliate-network.md): Creates an affiliate network and returns its id.
- [Affiliate network detail](https://docs.metricanic.com/api-reference/endpoints/get-affiliate-network.md): Returns a single affiliate network.
- [Update affiliate network](https://docs.metricanic.com/api-reference/endpoints/update-affiliate-network.md): Partially updates an affiliate network. Only provided fields change. Returns the updated entity.
- [Delete affiliate network](https://docs.metricanic.com/api-reference/endpoints/delete-affiliate-network.md): Archives the affiliate network (soft delete). Fails with 409 while the network has active offers. Restore later via POST /api/v1/affiliate-networks/restore.
- [Archive affiliate networks](https://docs.metricanic.com/api-reference/endpoints/archive-affiliate-networks-bulk.md): Archives multiple affiliate networks by id. Ids are de-duplicated. The operation is all-or-nothing: if any id is unknown the request fails with 404 and `details.missing` lists the unknown ids.
- [Restore affiliate networks](https://docs.metricanic.com/api-reference/endpoints/restore-affiliate-networks-bulk.md): Restores previously archived affiliate networks by id. Ids are de-duplicated. The operation is all-or-nothing: if any id is unknown the request fails with 404 and `details.missing` lists the unknown ids.
- [List events](https://docs.metricanic.com/api-reference/endpoints/list-events.md): Raw event stream for inspection and debugging - visits, landing page clicks, conversion events and outbound postbacks. Uses cursor pagination: pass meta.nextCursor back via the cursor parameter while hasMore is true. Rows include request-level fields (requestIp, requestUa, requestReferer) captured f…

## OpenAPI Specs

- [openapi.public](/openapi.public.yaml)