Newsletter Content analytics¶

See how your newsletters perform: site-wide totals, the best and worst performing newsletters, one newsletter's totals and day-by-day series, and the products its tiles earned their traffic on.

Every figure comes back three times. known covers recipients Hello Retail could identify, unknown covers the rest, and total covers both together. Nothing else in Hello Retail splits its analytics this way, and it exists to answer one question: did personalizing the content beat not personalizing it. Report the pair rather than the total alone.

Each side carries opens, clicks, orders and revenue, plus the derived click-through rate (clicks/opens), conversion rate (orders/opens) and average order size (revenue/orders). total sums the counts and recomputes the rates from those sums, so a handful of identified recipients can't outweigh thousands of unidentified ones.

An open is only counted once the recipient's mail client loads images, and plenty of clients never do. Clicks can therefore exceed opens and a rate can pass 100%. That's a measurement artifact, not a broken number.

Campaign types, and what a row is¶

The campaignType argument takes the same three values everywhere, and they decide what one row means:

There's no TEMPLATE. An Auto campaign configuration never serves a tile itself, so it has no figures of its own; each newsletter it sends is filed under AUTO. To judge an Auto campaign as a whole, rank its sends and read the trend. Newsletter Content campaigns explains the relationship.

Tips & tricks¶

Pick the card that matches what you're doing. Each prompt is ready to paste into your assistant.

Show my website's Newsletter Content performance for the last 30 days, then list the top 10 newsletters by revenue.

For my last five newsletters, compare the known-recipient CTR with the unknown-recipient CTR and tell me whether personalization is paying off.

What share of my visitors can Hello Retail identify, and is that limiting my newsletter performance?

Show the daily opens, clicks and orders for Newsletter Content campaign <CAMPAIGN ID> over the last 30 days.

Which products earned the clicks in Newsletter Content campaign <CAMPAIGN ID>, and are any of them getting views but no clicks?

Find my worst-performing newsletter, read its recommendation strategy, and preview a version that leads with recently viewed products.

newsletterContent_getAnalyticsTotals¶

Get the site-wide Newsletter Content totals for a customer website: opens, clicks, orders and revenue with the derived rates, summed over every campaign of the chosen kind, for identified recipients, unidentified ones and both together.

identifiedVisitorPercentage is the share of the website's visitors Hello Retail can identify, read at the end of the window. It's a standing measurement of the tracking setup rather than something that accumulates over the period.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "newsletterContent_getAnalyticsTotals",
    "arguments": {
      "websiteUuid": "<string>"
    }
  }
}

{
  "campaignType": null,
  "known": {
    "opens": 100,
    "clicks": 30,
    "conversions": 5,
    "revenue": 300.0,
    "clickThroughRate": 0.3,
    "conversionRate": 0.05,
    "averageOrderSize": 60.0
  },
  "unknown": {
    "opens": 400,
    "clicks": 20,
    "conversions": 5,
    "revenue": 200.0,
    "clickThroughRate": 0.05,
    "conversionRate": 0.0125,
    "averageOrderSize": 40.0
  },
  "total": {
    "opens": 500,
    "clicks": 50,
    "conversions": 10,
    "revenue": 500.0,
    "clickThroughRate": 0.1,
    "conversionRate": 0.02,
    "averageOrderSize": 50.0
  },
  "identifiedVisitorPercentage": 25.0
}

newsletterContent_getAnalyticsGrouped¶

Rank the newsletters of a customer website by a performance metric. Sort descending (default) for the best performers, ascending for the worst.

Ranking reads one side of the split at a time, because the two are stored as separate counters: audience picks which one sortBy orders on. Every row still carries both sides, so a campaign that ranks well on one and badly on the other is visible in the answer. A campaign deleted since is left out, since the per-campaign tools would refuse its id.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "newsletterContent_getAnalyticsGrouped",
    "arguments": {
      "websiteUuid": "<string>",
      "campaignType": "AUTO",
      "sortBy": "REVENUE",
      "limit": 10
    }
  }
}

{
  "campaignType": "AUTO",
  "results": [
    {
      "campaignId": "<string>",
      "name": "2026-02-17 - Weekly newsletter",
      "campaignType": "AUTO",
      "known": { "opens": 100, "clicks": 30, "conversions": 5, "revenue": 300.0, "clickThroughRate": 0.3, "conversionRate": 0.05, "averageOrderSize": 60.0 },
      "unknown": { "opens": 400, "clicks": 20, "conversions": 5, "revenue": 200.0, "clickThroughRate": 0.05, "conversionRate": 0.0125, "averageOrderSize": 40.0 },
      "total": { "opens": 500, "clicks": 50, "conversions": 10, "revenue": 500.0, "clickThroughRate": 0.1, "conversionRate": 0.02, "averageOrderSize": 50.0 }
    }
  ]
}

newsletterContent_getAnalyticsForCampaign¶

Get one newsletter's totals over the window, for identified recipients, unidentified ones and both together.

The id may be any campaign that has served tiles, including one newsletter sent by an Auto campaign. An Auto campaign configuration itself never serves and has no figures of its own; add up its sends with newsletterContent_getAnalyticsGrouped, or list them with newsletterContent_listSentCampaignsForTemplate.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "newsletterContent_getAnalyticsForCampaign",
    "arguments": {
      "websiteUuid": "<string>",
      "campaignId": "<string>"
    }
  }
}

{
  "campaignId": "<string>",
  "name": "2026-02-17 - Weekly newsletter",
  "campaignType": "AUTO",
  "state": "LIVE",
  "known": { "opens": 100, "clicks": 30, "conversions": 5, "revenue": 300.0, "clickThroughRate": 0.3, "conversionRate": 0.05, "averageOrderSize": 60.0 },
  "unknown": { "opens": 400, "clicks": 20, "conversions": 5, "revenue": 200.0, "clickThroughRate": 0.05, "conversionRate": 0.0125, "averageOrderSize": 40.0 },
  "total": { "opens": 500, "clicks": 50, "conversions": 10, "revenue": 500.0, "clickThroughRate": 0.1, "conversionRate": 0.02, "averageOrderSize": 50.0 }
}

newsletterContent_getAnalyticsDailyForCampaign¶

Get one newsletter's day-by-day series, oldest first, with one row for every day in the window. Days without traffic read 0. The window can't exceed 366 days.

A newsletter's traffic is front-loaded: most recipients open within a day or two of the send, so a series that keeps climbing after that is usually a campaign still being sent, and one that spikes again later is usually a re-send. Orders are attributed on the day of the order, not the day of the click, so the orders line trails the clicks line.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "newsletterContent_getAnalyticsDailyForCampaign",
    "arguments": {
      "websiteUuid": "<string>",
      "campaignId": "<string>",
      "startDate": "2026-02-17",
      "endDate": "2026-03-18"
    }
  }
}

{
  "campaignId": "<string>",
  "name": "2026-02-17 - Weekly newsletter",
  "days": [
    {
      "date": "2026-02-17",
      "known": { "opens": 80, "clicks": 26, "conversions": 4, "revenue": 240.0, "clickThroughRate": 0.325, "conversionRate": 0.05, "averageOrderSize": 60.0 },
      "unknown": { "opens": 320, "clicks": 17, "conversions": 4, "revenue": 160.0, "clickThroughRate": 0.053, "conversionRate": 0.0125, "averageOrderSize": 40.0 },
      "total": { "opens": 400, "clicks": 43, "conversions": 8, "revenue": 400.0, "clickThroughRate": 0.1075, "conversionRate": 0.02, "averageOrderSize": 50.0 }
    }
  ]
}

newsletterContent_getAnalyticsProductsForCampaign¶

Get the products one newsletter earned its traffic on: per product, how many times its tile was shown, how many times it was clicked, and the orders that followed. Same table as the Products tab of the campaign's analytics page.

Orders come back split. A direct order is one placed on the product that was clicked; an indirect order is a different product bought in the same session. Both belong to the campaign, only the first belongs to the product.

Identified and unidentified recipients are summed here, unlike the other tools on this page, because the campaign's own figures already answer that split.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "newsletterContent_getAnalyticsProductsForCampaign",
    "arguments": {
      "websiteUuid": "<string>",
      "campaignId": "<string>",
      "sortBy": "CLICKS"
    }
  }
}

{
  "campaignId": "<string>",
  "name": "2026-02-17 - Weekly newsletter",
  "results": [
    {
      "productId": "<string>",
      "title": "<string>",
      "url": "<string>",
      "views": 420,
      "clicks": 38,
      "directConversions": 6,
      "indirectConversions": 2
    }
  ]
}