Args

%{
  "account_id" => "106160",
  "data" => %{
    "account_insight_agent_id" => "62e3b1cf-db85-43c3-82f1-0205b271a4b3",
    "insights" => [
      %{
        "action_plan" => "Treat the Loops result as a **hypothesis**, not a proven account-specific insight. First, instrument the lifecycle events needed to measure it: **Signed Up / First Login**, **Completed Onboarding** or your core activation event, and **Used [Key Feature]** for the feature you want to drive. Then create matching Appcues goals with conversion windows aligned to the use case — Appcues recommends roughly **7–14 days for onboarding** and **3–7 days for feature nudges**  .",
        "actions" => [],
        "cta_text" => nil,
        "entity_id" => nil,
        "entity_type" => nil,
        "expected_impact" => "Once tracking is restored, you’ll be able to measure whether early messaging actually lifts activation and retention instead of relying on an external aggregate claim.",
        "finding" => "The Loops insight is directionally useful, but this Appcues account cannot currently confirm or extend it. There are **0 tracked event names in the last 365 days**, and your enabled goals are **not tied to first login, feature adoption, or month-2 retention**. Appcues guidance is explicit that event tracking powers Goals, experiments, targeting, and analytics, and that an implementation is incomplete without events  .",
        "outcomes" => ["activation", "retention"],
        "priority" => "high",
        "title" => "You can’t validate the Loops retention claim in Appcues yet",
        "type" => "issue"
      },
      %{
        "action_plan" => "Do not try to copy the Loops statement literally by just blasting more banners. Instead, retire or deprioritize stale banner content for this use case and build a new early-lifecycle journey targeted to **new users in days 0–14**. Use the banner only for lightweight awareness if needed, and pair it with more action-oriented experiences that can actually drive product behavior.",
        "actions" => [],
        "cta_text" => nil,
        "entity_id" => "e5b8c37b-0fb6-4c93-ae00-94f710057d74",
        "entity_type" => "banner",
        "expected_impact" => "This shifts your setup from untargeted announcement content toward experiences that can influence activation and be measured against retention outcomes.",
        "finding" => "The only published web banner in this account is **“Sam Wedding”**, targeted to **samstuckless.ca/wedding.html**, set to show **every_time**, and has **no goals** attached. That means the current live banner strategy is not set up to reach new users in their first 14 days or measure adoption/retention outcomes. Separately, Appcues benchmark guidance says banners average only **0.32% CTR** and should be used for **FYIs, not critical conversions** .",
        "outcomes" => ["activation", "engagement", "retention"],
        "priority" => "high",
        "title" => "Your live content setup is not aligned to the Loops use case",
        "type" => "issue"
      }
    ]
  },
  "notification_id" => "8eca0cb0-c9a4-4cd1-9c4e-3c72261fe067",
  "workflow_key" => "insight-issue-added"
}

Meta

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