lead-source-observability

Define lead source schemas and ingestion mappings for Anclora Nexus.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ToniIAPro73/Anclora-Nexus --skill lead-source-observability
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lead-source-observability
Source: https://github.com/ToniIAPro73/Anclora-Nexus/tree/main/.agent/skills/features/lead-source-observability
Command: npx skills add https://github.com/ToniIAPro73/Anclora-Nexus --skill lead-source-observability

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures comprehensive traceability of lead and customer sources within the Anclora Nexus system, crucial for understanding marketing effectiveness and customer acquisition channels.

Core Features & Use Cases

  • Schema Definition: Define and manage the schema for lead source attribution.
  • Ingestion Mapping: Map various lead sources including manual entries, web calls-to-action (CTAs), social media, imports, and referrals.
  • API Contract Management: Ensure consistent source attribution data across API integrations.
  • UI Display & Filtering: Enable clear display and filtering of lead sources in the user interface.
  • Use Case: When a new lead comes in from a specific social media campaign, this skill ensures it's correctly tagged with the campaign name, channel, and any other relevant details for accurate reporting.

Quick Start

Use the lead-source-observability skill to define the schema for tracking lead sources from social media campaigns.

Frequently Asked Questions about lead-source-observability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track lead source attribution for Anclora Nexus?

Lead source attribution for Anclora Nexus is achieved by implementing a schema with specific fields like source_system, source_channel, and captured_at to ensure full customer traceability for marketing campaigns.

What is lead source traceability and when do I need it?

Lead source traceability is the process of mapping customer acquisition channels to understand marketing effectiveness. You need it when defining or changing lead origin schemas, ingestion mappings, or API contracts for accurate source attribution.

How do I map ingestion sources for manual, web CTA, and social campaigns?

Map ingestion sources by applying specific ingestion mappings for manual entries, web calls-to-action, social media, imports, and referrals to correctly tag incoming leads with campaign details and channel data for accurate reporting.

Does lead source observability require a specific API contract version?

Yes, lead source observability requires adherence to a minimum API contract version 1, ensuring consistent source attribution data across integrations with mandatory fields like source_system, source_channel, and captured_at.

Can I filter lead sources by channel in the UI display?

Yes, the skill enables clear UI display and filtering of lead sources by applying the ingestion mapping schema to categorize incoming leads by source_channel for accurate reporting and marketing analysis.

What's the best way to handle social media campaign attribution data?

Handle social media campaign attribution by using the social+CTA ingestion mapping to tag incoming leads with the campaign name, channel, and relevant details for accurate source reporting within Anclora Nexus.