Args

%{
  "account_id" => "220741",
  "data" => %{
    "account_insight_agent_id" => "9376c815-4a88-48d7-bb83-c0a1d6bafd05",
    "insights" => [
      %{
        "action_plan" => "Update the pin titles to the standard spellings:\n1. Change **\"Click Thru Rate\"** to **\"Click Through Rate\"**\n2. Change **\"View Thru Rate\"** to **\"View Through Rate\"**\n\nIf your team intentionally prefers informal ad-tech shorthand, keep them as-is; otherwise standardizing the terms will make the labels look more polished and consistent.",
        "actions" => [],
        "cta_text" => "Review pins",
        "entity_id" => "49971ba9-5ae0-4662-912c-aded274d2f3d",
        "entity_type" => "pin",
        "expected_impact" => "Cleaner terminology in live UI copy and fewer trust-damaging spelling distractions for end users.",
        "finding" => "I reviewed all **9 published experiences** and found **2 live pins** with likely spelling issues in English copy:\n\n- **Click Thru Rate** — experience name uses **\"Thru\"** instead of the standard **\"Through\"**. Review it here: [Click Thru Rate](https://studio.appcues.com/pins/49971ba9-5ae0-4662-912c-aded274d2f3d/analytics)\n- **View Thru Rate** — experience name uses **\"Thru\"** instead of **\"Through\"**. Review it here: [View Thru Rate](https://studio.appcues.com/pins/8e96feef-4855-4635-903b-4cc57f239b21/analytics)\n\nThese may be intentional shorthand, but in product copy they read more like misspellings than accepted UI terminology.",
        "outcomes" => ["engagement"],
        "priority" => "medium",
        "title" => "Two live rate-explainer pins use nonstandard “Thru” spelling",
        "type" => "issue"
      },
      %{
        "action_plan" => "Revise the tooltip copy to **\"Calculated by dividing view-throughs by impressions.\"**\n\nYou may also want to align the experience title at the same time so both the title and body use the same standard phrasing.",
        "actions" => [],
        "cta_text" => "Review tooltip copy",
        "entity_id" => "8e96feef-4855-4635-903b-4cc57f239b21",
        "entity_type" => "pin",
        "expected_impact" => "More professional terminology and clearer alignment with common advertising metric language.",
        "finding" => "The published pin **View Thru Rate** contains tooltip text that likely has a spelling/usage issue:\n\n- Current phrase: **\"Calculated by dividing view throughs by impressions.\"**\n- Review it here: [View Thru Rate](https://studio.appcues.com/pins/8e96feef-4855-4635-903b-4cc57f239b21/analytics)\n\nIn English ad-measurement terminology, **\"view-throughs\"** is typically hyphenated. Because this is specialized terminology, I treated it as a likely typo/standardization issue rather than a guaranteed error.",
        "outcomes" => ["engagement"],
        "priority" => "medium",
        "title" => "One live pin tooltip likely needs hyphenation for “view-throughs”",
        "type" => "issue"
      }
    ]
  },
  "notification_id" => "1081a4b9-c35a-42f2-8085-04eb7028e850",
  "workflow_key" => "insight-issue-added"
}

Meta

%{"orig_scheduled_at" => 1776799185702904, "structured" => true}

Errors

** (Knock.ApiKeyMissingError)   The api_key setting is required to make requests to Knock.
  Please configure :api_key in config.exs, set the KNOCK_API_KEY
  environment variable, or pass into a new client instance.

    (knock 0.5.0) lib/knock/client.ex:65: Knock.Client.new/1
    (customer_api 1.21.0+a640f45e) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+a640f45e) lib/customer_api/jobs/publish_notification_job.ex:93: CustomerApi.Jobs.PublishNotificationJob.do_publish/4
    (oban_pro 1.6.12) lib/oban/pro/worker.ex:1156: Oban.Pro.Worker.process/3
    (oban 2.20.3) lib/oban/queue/executor.ex:145: Oban.Queue.Executor.perform/1
    (oban 2.20.3) lib/oban/queue/executor.ex:77: Oban.Queue.Executor.call/1
    (elixir 1.19.5) lib/task/supervised.ex:105: Task.Supervised.invoke_mfa/2
    (elixir 1.19.5) lib/task/supervised.ex:40: Task.Supervised.reply/4

** (Knock.ApiKeyMissingError)   The api_key setting is required to make requests to Knock.
  Please configure :api_key in config.exs, set the KNOCK_API_KEY
  environment variable, or pass into a new client instance.

    (knock 0.5.0) lib/knock/client.ex:65: Knock.Client.new/1
    (customer_api 1.21.0+a640f45e) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+a640f45e) lib/customer_api/jobs/publish_notification_job.ex:93: CustomerApi.Jobs.PublishNotificationJob.do_publish/4
    (oban_pro 1.6.12) lib/oban/pro/worker.ex:1156: Oban.Pro.Worker.process/3
    (oban 2.20.3) lib/oban/queue/executor.ex:145: Oban.Queue.Executor.perform/1
    (oban 2.20.3) lib/oban/queue/executor.ex:77: Oban.Queue.Executor.call/1
    (elixir 1.19.5) lib/task/supervised.ex:105: Task.Supervised.invoke_mfa/2
    (elixir 1.19.5) lib/task/supervised.ex:40: Task.Supervised.reply/4

** (Knock.ApiKeyMissingError)   The api_key setting is required to make requests to Knock.
  Please configure :api_key in config.exs, set the KNOCK_API_KEY
  environment variable, or pass into a new client instance.

    (knock 0.5.0) lib/knock/client.ex:65: Knock.Client.new/1
    (customer_api 1.21.0+a640f45e) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+a640f45e) lib/customer_api/jobs/publish_notification_job.ex:93: CustomerApi.Jobs.PublishNotificationJob.do_publish/4
    (oban_pro 1.6.12) lib/oban/pro/worker.ex:1156: Oban.Pro.Worker.process/3
    (oban 2.20.3) lib/oban/queue/executor.ex:145: Oban.Queue.Executor.perform/1
    (oban 2.20.3) lib/oban/queue/executor.ex:77: Oban.Queue.Executor.call/1
    (elixir 1.19.5) lib/task/supervised.ex:105: Task.Supervised.invoke_mfa/2
    (elixir 1.19.5) lib/task/supervised.ex:40: Task.Supervised.reply/4

** (Knock.ApiKeyMissingError)   The api_key setting is required to make requests to Knock.
  Please configure :api_key in config.exs, set the KNOCK_API_KEY
  environment variable, or pass into a new client instance.

    (knock 0.5.0) lib/knock/client.ex:65: Knock.Client.new/1
    (customer_api 1.21.0+a640f45e) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+a640f45e) lib/customer_api/jobs/publish_notification_job.ex:93: CustomerApi.Jobs.PublishNotificationJob.do_publish/4
    (oban_pro 1.6.12) lib/oban/pro/worker.ex:1156: Oban.Pro.Worker.process/3
    (oban 2.20.3) lib/oban/queue/executor.ex:145: Oban.Queue.Executor.perform/1
    (oban 2.20.3) lib/oban/queue/executor.ex:77: Oban.Queue.Executor.call/1
    (elixir 1.19.5) lib/task/supervised.ex:105: Task.Supervised.invoke_mfa/2
    (elixir 1.19.5) lib/task/supervised.ex:40: Task.Supervised.reply/4

** (Knock.ApiKeyMissingError)   The api_key setting is required to make requests to Knock.
  Please configure :api_key in config.exs, set the KNOCK_API_KEY
  environment variable, or pass into a new client instance.

    (knock 0.5.0) lib/knock/client.ex:65: Knock.Client.new/1
    (customer_api 1.21.0+a640f45e) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+a640f45e) lib/customer_api/jobs/publish_notification_job.ex:93: CustomerApi.Jobs.PublishNotificationJob.do_publish/4
    (oban_pro 1.6.12) lib/oban/pro/worker.ex:1156: Oban.Pro.Worker.process/3
    (oban 2.20.3) lib/oban/queue/executor.ex:145: Oban.Queue.Executor.perform/1
    (oban 2.20.3) lib/oban/queue/executor.ex:77: Oban.Queue.Executor.call/1
    (elixir 1.19.5) lib/task/supervised.ex:105: Task.Supervised.invoke_mfa/2
    (elixir 1.19.5) lib/task/supervised.ex:40: Task.Supervised.reply/4