Args

%{
  "account_id" => "99992",
  "data" => %{
    "account_insight_agent_id" => "21cccd01-c7a9-46cc-a091-d4773131130d",
    "insights" => [
      %{
        "action_plan" => "Rebuild this pin before continuing to scale it. Use a more stable placement target, narrow targeting to the exact page/state where the finance nav item is reliably present, and replace the generic label with copy that names the feature or benefit. If a rebuild cannot happen immediately, pause the pin to stop wasted impressions and error volume.",
        "actions" => [
          %{
            "cta" => "Run",
            "prompt" => "Use the product_support agent and the unpublish_experience tool to unpublish the published experience with ID 472627a8-a0b2-4f7b-8529-201a464d444a named '021224_PY_ALL_TAG-finanzas-nuevo-plugin-ALL'. This is a persistent web pin currently live and should be unpublished to stop production delivery while its selector and copy are reviewed.",
            "title" => "Unpublish broken finance nav pin",
            "undo_prompt" => "Use the product_support agent and the publish_experience tool to republish the experience with ID 472627a8-a0b2-4f7b-8529-201a464d444a named '021224_PY_ALL_TAG-finanzas-nuevo-plugin-ALL'."
          }
        ],
        "cta_text" => "Review pin",
        "entity_id" => "472627a8-a0b2-4f7b-8529-201a464d444a",
        "entity_type" => "pin",
        "expected_impact" => "Reducing delivery errors should recover reach quality and make clicks more meaningful, improving engagement and adoption of the finance plugin.",
        "finding" => "The **finance plugin nav pin** was seen by **21,194 users** in the last 30 days, but recorded only **3 completions** and **30,322 errors**. Its live setup uses **every-time frequency**, broad site targeting, and a tiny nav-attached label that only says **“Nuevo”**, giving users almost no context about why they should click.",
        "outcomes" => ["adoption", "engagement"],
        "priority" => "high",
        "title" => "Finance plugin pin is generating more errors than engagement",
        "type" => "issue"
      },
      %{
        "action_plan" => "Tighten this experience to the exact product area where the destination exists reliably, then relaunch with clearer message text that explains what changed or what users gain. Consider using a banner or short modal for the initial announcement, then reserve a pin for persistent wayfinding only after the feature is familiar.",
        "actions" => [
          %{
            "cta" => "Run",
            "prompt" => "Use the product_support agent and the unpublish_experience tool to unpublish the published experience with ID 5e1ca45e-d94c-4b4f-a62b-c3d443b50cfc named '020326_PY_ALL_TAG-Destacados-nuevo-plugin-ALL'. This is a persistent web pin currently live and should be unpublished while its targeting, selector, and copy are reworked.",
            "title" => "Unpublish low-signal rewards pin",
            "undo_prompt" => "Use the product_support agent and the publish_experience tool to republish the experience with ID 5e1ca45e-d94c-4b4f-a62b-c3d443b50cfc named '020326_PY_ALL_TAG-Destacados-nuevo-plugin-ALL'."
          }
        ],
        "cta_text" => "Review pin",
        "entity_id" => "5e1ca45e-d94c-4b4f-a62b-c3d443b50cfc",
        "entity_type" => "pin",
        "expected_impact" => "A clearer first-touch message and narrower targeting should cut error volume and improve qualified click-through to the Rewards area.",
        "finding" => "The **Destacados / Rewards plugin pin** logged **11,997 sees**, only **3 completions**, and **40,788 errors** in the last 30 days. It is configured to show **every time** across **two domains** and, like other underperforming pins in this account, uses a minimal **“Nuevo”** badge without enough context to earn a click.",
        "outcomes" => ["adoption", "engagement"],
        "priority" => "high",
        "title" => "Rewards nav pin is overserving but not driving clicks",
        "type" => "issue"
      },
      %{
        "action_plan" => "Shorten the first message to one clear value proposition and one primary CTA, then move the detailed explanation or video to a follow-up step or destination page. Cap frequency so users are not re-prompted on every dashboard visit, and add a goal tied to the intended action so you can measure whether the launch is actually activating usage.",
        "actions" => [],
        "cta_text" => "Review flow",
        "entity_id" => "837039a1-aa09-4f33-932c-97233ba35e70",
        "entity_type" => "flow",
        "expected_impact" => "Simplifying the launch message and reducing repeat exposure should lower skips and improve activation for the new feature.",
        "finding" => "The new **high demand mode Portal** modal has **794 sees**, **0 completions**, and **744 skips** in its first days live — a **93.7% skip rate**. The experience is a **single long modal** with multiple paragraphs, a GIF, inline links, **every-time frequency**, and **no goals**, which creates a lot of reading demand before users reach a meaningful action.",
        "outcomes" => ["activation", "adoption", "engagement"],
        "priority" => "high",
        "title" => "High demand mode launch modal is being skipped almost immediately",
        "type" => "issue"
      },
      %{
        "action_plan" => "Keep the audience logic, but change the experience format or message. For a financial offer, test a clearer banner or modal that names the benefit directly instead of a generic badge, then retain a pin only as a secondary reminder. Also review the current attachment point to ensure the pin appears only when the finance navigation element is present.",
        "actions" => [],
        "cta_text" => "Review pin",
        "entity_id" => "9b241ea7-0421-4bc8-ba04-52907a604ee7",
        "entity_type" => "pin",
        "expected_impact" => "A clearer offer message should increase qualified engagement from eligible users and improve adoption of Advance Payouts.",
        "finding" => "The **Advance Payouts** pin reached **15,051 users** in the last 30 days with **0 completions** and **13,986 errors**. It targets admins and finance users with an available offer, but still relies on a small overlay that only says **“Nuevo”** and shows **every time**, making it easy to ignore and vulnerable to page-state mismatches.",
        "outcomes" => ["activation", "adoption"],
        "priority" => "medium",
        "title" => "Advance Payouts pin has reach but almost no usable interaction",
        "type" => "issue"
      }
    ]
  },
  "notification_id" => "62870b86-e81a-4a28-a321-6b40db4e3c7a",
  "workflow_key" => "insight-issue-added"
}

Meta

%{"orig_scheduled_at" => 1776771997171069, "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+2c7a309d) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+2c7a309d) 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+2c7a309d) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+2c7a309d) 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+2c7a309d) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+2c7a309d) 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+2c7a309d) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+2c7a309d) 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+2c7a309d) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+2c7a309d) 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