Tag: logs reports

Failed leads API injection

The “Failed Leads API injection” feature allows you to track leads that were not successfully injected into your CRM.

When a lead is rejected, the system automatically generates an entry in the logs; it provides detailed information about the failed injection; and includes the reason why the injection failed.

Why does leads injection fails

There are multiple reasons for a lead coming via API to fail being injected in aNinja. Here are the reasons that we log in Settings > logs. Leads injection could fail due to:

  • Duplicate Emails
  • Missing required fields (contact_name)
Failed leads API injection due to duplicate Emails

In Settings > Global Settings, if the following rule is enabled,

“Do not add new Leads via api if Lead with similar email already exists (avoids duplicates)”

when a lead is added via API, the system first checks if the lead already exists in the CRM.

It compares the email address of the new lead with the existing leads in the system.

If the system identifies an existing lead with a similar email address, it does not add the new lead to avoid duplication. Subsequently, it generates an entry in Logs, providing the reason of the failed lead injection.

Failed lead API injection due to missing required field

The contact name is the only required field for a successful lead creation. And the system creates the lead in reference to the contact name and saves the lead data.

If the lead data coming through API is missing the contact name, it does not create a new lead; and it generates an entry in Logs with the reason of failed lead injection.

Accessing the Failed leads API injection Logs

  • Click on “Failed leads API injection” from the toolbar

Failed leads API injection due to duplicate emailsIn this table, you can view:

  • ID: A sequential number
  • Reason: The reason for which the lead failed to inject
  • Data: The source of the lead that failed to inject
  • Created: The date & time this record was created – failed to inject.

By providing clear and detailed information about rejected leads, you can quickly identify the failed leads injection and address the issue.

aNinja Activities Logs

It’s important to have a clear understanding of all the activities and interactions that occur on your aNinja account. aNinja provides a helpful solution in the form of activity logs reports, allowing you to conduct audits whenever necessary.

Specifically, the logs report feature provides a comprehensive overview of all incoming and outgoing calls, emails, and texts, and the triggers you’ve launched. Additionally, you can easily view the failed leads API injection.

Accessing aNinja Activities Logs reports

Activities Logs

  • Calls
    • You can see the details of the incoming and outgoing calls, including the lead ID, duration and date of the calls.
    • You can also listen to the recordings of the conversations.
  • Emails
    • Here are saved all the details on the incoming and outgoing emails, including the sequences and their statuses.
  • Texts
    • You can see the details of the incoming and outgoing texts, including the sequences and their statuses.
  • Audit Log
    • As an admin user, this option allows you to see the activity of the users in searching for leads using smartlists or from the top navigation bar, and the lead view that the users opened.
  • Failed leads API injection
    • You can identify any leads that failed to import into your aNinja account via API for duplicate emails.